37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 487692 |
Time | |
Date | 200010 |
Day | Wed |
Local Time Of Day | 1801 To 2400 |
Place | |
State Reference | FL |
Altitude | msl single value : 25000 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zjx.artcc |
Operator | other |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Route In Use | enroute : other oceanic |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller radar : 16 controller time certified in position1 : 16 |
ASRS Report | 487692 |
Person 2 | |
Affiliation | government : military |
Function | controller : radar |
Qualification | controller : military controller : radar |
Events | |
Anomaly | airspace violation : entry non adherence : published procedure |
Independent Detector | other controllera other controllerb |
Resolutory Action | controller : issued advisory none taken : anomaly accepted |
Supplementary | |
Problem Areas | Flight Crew Human Performance Airspace Structure ATC Human Performance |
Primary Problem | Ambiguous |
Air Traffic Incident | Operational Deviation |
Narrative:
I was about to be relieved at R58 (st augustine) sector when I noticed a limited data block in warning area 158A at 25000 ft. The warning area was only active to 5000 ft and I owned 6000 ft and above. I called sealord to see if they knew who the target was and they said it was a flight (probably a B1 bomber) returning to warner-robbins. I asked the controller if he knew that I owned the airspace and he said something online that was unreadable. I asked again who and what was going on and he then began to point the aircraft out to me. I accepted the pointout. I then asked sealord what they showed the warning area active to, he said at or below 5000 ft. This seems to be happening on a more frequent bases where there is some confusion as to what airspace is active and what is not active. We are running air carrier and other aircraft through this airspace when we own it.
Original NASA ASRS Text
Title: AFTER COORD WITH MIL FAC, ZJX RADAR CTLR DETERMINES A MIL ACFT IS OPERATING OUTSIDE OF AN ACTIVE WARNING AREA.
Narrative: I WAS ABOUT TO BE RELIEVED AT R58 (ST AUGUSTINE) SECTOR WHEN I NOTICED A LIMITED DATA BLOCK IN WARNING AREA 158A AT 25000 FT. THE WARNING AREA WAS ONLY ACTIVE TO 5000 FT AND I OWNED 6000 FT AND ABOVE. I CALLED SEALORD TO SEE IF THEY KNEW WHO THE TARGET WAS AND THEY SAID IT WAS A FLT (PROBABLY A B1 BOMBER) RETURNING TO WARNER-ROBBINS. I ASKED THE CTLR IF HE KNEW THAT I OWNED THE AIRSPACE AND HE SAID SOMETHING ONLINE THAT WAS UNREADABLE. I ASKED AGAIN WHO AND WHAT WAS GOING ON AND HE THEN BEGAN TO POINT THE ACFT OUT TO ME. I ACCEPTED THE POINTOUT. I THEN ASKED SEALORD WHAT THEY SHOWED THE WARNING AREA ACTIVE TO, HE SAID AT OR BELOW 5000 FT. THIS SEEMS TO BE HAPPENING ON A MORE FREQUENT BASES WHERE THERE IS SOME CONFUSION AS TO WHAT AIRSPACE IS ACTIVE AND WHAT IS NOT ACTIVE. WE ARE RUNNING ACR AND OTHER ACFT THROUGH THIS AIRSPACE WHEN WE OWN IT.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.