37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1058694 |
Time | |
Date | 201301 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZJX.ARTCC |
State Reference | FL |
Aircraft 1 | |
Make Model Name | Fighter |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | None |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Stratolifter (C-135) |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | None |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
When I sat down at sector 35 the controller that I was relieving was talking with the supervisor about something. For my relief briefing; I was told that we were blocking W157A and W159A at or below FL430; the controlling agency; sealord was going home; and that there was an awacs aircraft out there working some fighters and a refueler. I thought all I had to do was block the airspace. The only other information at the sector was a sheet of paper titled; 'mission position daily log;' which had call signs; but no other useful information as far as I could discern. A couple of minutes after plugging in; sealord called me on the land line to hand off the awacs aircraft. I asked for clarification. He said that the center missions desk had told them that we would take the hand off on the awacs aircraft. This was news to me. I called my supervisor over; and told him what they were trying to do. He said; 'yeah. We're taking the hand off on the awacs aircraft.' so I took the hand off. The awacs aircraft checked on; and said that the guy in back of his airplane doing the controlling was call sign abcd. I thought that he was controlling the rest of the aircraft in the warning area. Several minutes later; awacs aircraft calls me up for a clearance to rtb. I wasn't sure what to do. After a little bit; I cleared him back to tik. On his way out of the area to the east; abcd called me back and told me that a KC135 would be looking for clearance to rtb shortly; and a single F-15 and a group of F-15s wanted to remain in the warning area to work. So now; the awacs aircraft is gone; and I don't know who is controlling the rest of the aircraft inside this warning area airspace; nor do I know what any body's clearance is inside. I've started a track on the KC135 and am waiting for him to call to rtb. But his flight plan shows him as a single ship; and I can see additional limited data blocks right with him. I can't even tell the altitudes apart. Meanwhile; I'm busy with my regular traffic in my sector; and I'm ranged out to try and see what's going on in this extra airspace. Eventually; the KC135 called up and requested clearance back to mcf. I'm reluctant because I still see limited data blocks right with him. My supervisor and the omic; are standing right behind me at this point. I turn to them and tell them that I'm not sure what to do here; and ask if they had any suggestions. All I got back was blank stares. So I asked the KC135 if he was clear of the other flights. He confirmed that the single F15 and the group of F15s flights were FL270 and above. He was at FL260. They were diverging and the limits showed altitude separation. The KC135 was encroaching on another sector's airspace. I figured I had to get him on a clearance at least before he got in to sector 58. So I cleared him back to mcf. I had no assurance that the fighter aircraft were going to remain separated; as I had no idea what they were doing; or what their clearance was. Shortly after; I was relieved for break and told my relief that there were fighters in the airspace; and to miss it. I didn't know who they would call to rtb. It was messed up. I never got briefed on anything prior. It seemed like a very unsafe situation to be put in to. I did what came to mind; but was unsure of what was really happening in the airspace. Not a good position to be in as a controller. It greatly complicated my task. And I didn't even have a d-side! Don't put controllers in that situation. Sealord should have stayed the extra hour to work that entire scenario. That situation should not have been allowed to ever happen.
Original NASA ASRS Text
Title: ZJX Controller described a very confused event when improperly briefed as to SEALORD activities in near by restricted areas; the reporter suggesting SEALORD personnel should have remained on duty longer for clarity.
Narrative: When I sat down at Sector 35 the Controller that I was relieving was talking with the Supervisor about something. For my relief briefing; I was told that we were blocking W157A and W159A at or below FL430; the controlling agency; SEALORD was going home; and that there was an AWACS aircraft out there working some fighters and a refueler. I thought all I had to do was block the airspace. The only other information at the sector was a sheet of paper titled; 'Mission Position Daily Log;' which had call signs; but no other useful information as far as I could discern. A couple of minutes after plugging in; SEALORD called me on the land line to hand off the AWACS aircraft. I asked for clarification. He said that the Center Missions Desk had told them that we would take the hand off on the AWACS aircraft. This was news to me. I called my Supervisor over; and told him what they were trying to do. He said; 'Yeah. We're taking the hand off on the AWACS aircraft.' So I took the hand off. The AWACS aircraft checked on; and said that the guy in back of his airplane doing the controlling was call sign ABCD. I thought that he was controlling the rest of the aircraft in the warning area. Several minutes later; AWACS aircraft calls me up for a clearance to RTB. I wasn't sure what to do. After a little bit; I cleared him back to TIK. On his way out of the area to the east; ABCD called me back and told me that a KC135 would be looking for clearance to RTB shortly; and a single F-15 and a group of F-15s wanted to remain in the warning area to work. So now; the AWACS aircraft is gone; and I don't know who is controlling the rest of the aircraft inside this warning area airspace; nor do I know what any body's clearance is inside. I've started a track on the KC135 and am waiting for him to call to RTB. But his flight plan shows him as a single ship; and I can see additional limited data blocks right with him. I can't even tell the altitudes apart. Meanwhile; I'm busy with my regular traffic in my sector; and I'm ranged out to try and see what's going on in this extra airspace. Eventually; the KC135 called up and requested clearance back to MCF. I'm reluctant because I still see limited data blocks right with him. My Supervisor and the OMIC; are standing right behind me at this point. I turn to them and tell them that I'm not sure what to do here; and ask if they had any suggestions. All I got back was blank stares. So I asked the KC135 if he was clear of the other flights. He confirmed that the single F15 and the group of F15s flights were FL270 and above. He was at FL260. They were diverging and the limits showed altitude separation. The KC135 was encroaching on another sector's airspace. I figured I had to get him on a clearance at least before he got in to Sector 58. So I cleared him back to MCF. I had no assurance that the fighter aircraft were going to remain separated; as I had no idea what they were doing; or what their clearance was. Shortly after; I was relieved for break and told my relief that there were fighters in the airspace; and to miss it. I didn't know who they would call to RTB. It was messed up. I never got briefed on anything prior. It seemed like a very unsafe situation to be put in to. I did what came to mind; but was unsure of what was really happening in the airspace. Not a good position to be in as a controller. It greatly complicated my task. And I didn't even have a D-Side! Don't put controllers in that situation. SEALORD should have stayed the extra hour to work that entire scenario. That situation should not have been allowed to ever happen.
Data retrieved from NASA's ASRS site as of July 2013 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.