37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 518316 |
Time | |
Date | 200107 |
Day | Thu |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : tys.airport |
State Reference | IN |
Altitude | msl single value : 33000 |
Environment | |
Weather Elements | Thunderstorm |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : ztl.artcc |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : handoff position |
Qualification | controller : radar |
Experience | controller limited radar : 19 controller non radar : 19 controller radar : 19 controller supervisory : 0.25 controller time certified in position1 : 15 |
ASRS Report | 518316 |
Person 2 | |
Affiliation | government : faa |
Function | controller : radar |
Events | |
Anomaly | airspace violation : entry inflight encounter : weather non adherence : published procedure other spatial deviation |
Independent Detector | atc equipment other atc equipment : radar other controllera |
Resolutory Action | controller : issued new clearance controller : separated traffic flight crew : took precautionary avoidance action |
Consequence | faa : investigated |
Supplementary | |
Problem Areas | Weather Flight Crew Human Performance ATC Human Performance Airspace Structure |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Inter Facility Coordination Failure Intra Facility Coordination Failure |
Narrative:
Air carrier X was sbound transitioning from ZID to ZTL airspace. During a period of high volume and moderate to high complexity, ZID initiated an automated handoff to ZTL. Because we were so busy, the handoff was not accepted promptly and ZID initiated a voice line call to accomplish the handoff. The radar controller at the ZTL receiving sector answered the call and told the ZID controller to put air carrier X on a 205 degree heading (for traffic) and to advise us if the aircraft was unable (due to proximity of WX west of the aircraft). The ground track was approximately 165 or 170 degrees at that time. A short time later (45-90 seconds, I think), the ZID controller called back. Since I was working the radar associate position, I did not immediately answer the line, preferring that the radar controller or the coordinator/tracker take the call, since I was not 'up-to-date' on the radar situation. When neither of the other controllers on the sector took the call, I answered the line when the ZID controller called a second time. The ZID controller advised that the aircraft could not turn to a 205 degree heading. I attempted to quickly scan the radar situation and determine an alternate plan. After a brief period of indecision (5-8 seconds or S0, I told the ZID controller to turn the aircraft left to a 115 degree heading). Since the aircraft was very close to the sector boundary and the automated handoff had still not been completed, I accepted the handoff. The aircraft subsequently entered our airspace 'deviating for WX,' and not on a heading of 115 degrees. I do not know if the ZID controller failed to issue the clearance, or the pilot failed to comply with it. Note: because we were severely understaffed, management was unable to allow me time away from the position to complete this report until more than 6 hours later. Consequently, my recollections are not as clear as they might have been.
Original NASA ASRS Text
Title: ZTL ASSOCIATE HDOF CTLR ATTEMPTS TO RESOLVE WX RELATED ACR DEV WITH ZID AND ZTL RADAR CTLR WITHOUT RESOLUTION BTWN THE 2 FACILITY CTLRS AND THE ACR.
Narrative: ACR X WAS SBOUND TRANSITIONING FROM ZID TO ZTL AIRSPACE. DURING A PERIOD OF HIGH VOLUME AND MODERATE TO HIGH COMPLEXITY, ZID INITIATED AN AUTOMATED HDOF TO ZTL. BECAUSE WE WERE SO BUSY, THE HDOF WAS NOT ACCEPTED PROMPTLY AND ZID INITIATED A VOICE LINE CALL TO ACCOMPLISH THE HDOF. THE RADAR CTLR AT THE ZTL RECEIVING SECTOR ANSWERED THE CALL AND TOLD THE ZID CTLR TO PUT ACR X ON A 205 DEG HDG (FOR TFC) AND TO ADVISE US IF THE ACFT WAS UNABLE (DUE TO PROX OF WX W OF THE ACFT). THE GND TRACK WAS APPROX 165 OR 170 DEGS AT THAT TIME. A SHORT TIME LATER (45-90 SECONDS, I THINK), THE ZID CTLR CALLED BACK. SINCE I WAS WORKING THE RADAR ASSOCIATE POS, I DID NOT IMMEDIATELY ANSWER THE LINE, PREFERRING THAT THE RADAR CTLR OR THE COORDINATOR/TRACKER TAKE THE CALL, SINCE I WAS NOT 'UP-TO-DATE' ON THE RADAR SIT. WHEN NEITHER OF THE OTHER CTLRS ON THE SECTOR TOOK THE CALL, I ANSWERED THE LINE WHEN THE ZID CTLR CALLED A SECOND TIME. THE ZID CTLR ADVISED THAT THE ACFT COULD NOT TURN TO A 205 DEG HDG. I ATTEMPTED TO QUICKLY SCAN THE RADAR SIT AND DETERMINE AN ALTERNATE PLAN. AFTER A BRIEF PERIOD OF INDECISION (5-8 SECONDS OR S0, I TOLD THE ZID CTLR TO TURN THE ACFT L TO A 115 DEG HDG). SINCE THE ACFT WAS VERY CLOSE TO THE SECTOR BOUNDARY AND THE AUTOMATED HDOF HAD STILL NOT BEEN COMPLETED, I ACCEPTED THE HDOF. THE ACFT SUBSEQUENTLY ENTERED OUR AIRSPACE 'DEVIATING FOR WX,' AND NOT ON A HDG OF 115 DEGS. I DO NOT KNOW IF THE ZID CTLR FAILED TO ISSUE THE CLRNC, OR THE PLT FAILED TO COMPLY WITH IT. NOTE: BECAUSE WE WERE SEVERELY UNDERSTAFFED, MGMNT WAS UNABLE TO ALLOW ME TIME AWAY FROM THE POS TO COMPLETE THIS RPT UNTIL MORE THAN 6 HRS LATER. CONSEQUENTLY, MY RECOLLECTIONS ARE NOT AS CLR AS THEY MIGHT HAVE BEEN.
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.