37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 516065 |
Time | |
Date | 200106 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | navaid : vxv.vortac |
State Reference | IN |
Altitude | msl single value : 21000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : ztl.artcc |
Operator | common carrier : air carrier |
Make Model Name | Brasilia EMB-120 All Series |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller limited radar : 17 controller military : 0 controller non radar : 18 controller radar : 17 controller supervisory : 0.25 |
ASRS Report | 516065 |
Person 2 | |
Affiliation | government : faa |
Function | controller : radar |
Events | |
Anomaly | non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : investigated |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Intra Facility Coordination Failure |
Narrative:
I was working the ZTL north departure sector by myself. Traffic volume was light to moderate, but complexity was moderate or higher due to numerous sits unrelated to the airspace violation. During this period of time, I failed to handoff the aircraft to the next sector until it had already entered their airspace by 5-10 mi. The computer function which will sometimes initiate an automated handoff did not activate in this situation. I observed the situation during a scan of all aircraft in the sector, then I immediately initiated a computerized handoff to the sector and called them to verbally coordinate as well. When the supervisor questioned the receiving controller, they advised that they were aware of the aircraft since before it entered their airspace, and they were providing separation for the aircraft, but they were too busy to call me and alert me to the situation.
Original NASA ASRS Text
Title: ZTL CTLR INITIATES LATE COORD WHEN OBSERVING AN ACR ENTER ANOTHER CTLR'S AIRSPACE WITHOUT A COMPLETED HDOF.
Narrative: I WAS WORKING THE ZTL N DEP SECTOR BY MYSELF. TFC VOLUME WAS LIGHT TO MODERATE, BUT COMPLEXITY WAS MODERATE OR HIGHER DUE TO NUMEROUS SITS UNRELATED TO THE AIRSPACE VIOLATION. DURING THIS PERIOD OF TIME, I FAILED TO HDOF THE ACFT TO THE NEXT SECTOR UNTIL IT HAD ALREADY ENTERED THEIR AIRSPACE BY 5-10 MI. THE COMPUTER FUNCTION WHICH WILL SOMETIMES INITIATE AN AUTOMATED HDOF DID NOT ACTIVATE IN THIS SIT. I OBSERVED THE SIT DURING A SCAN OF ALL ACFT IN THE SECTOR, THEN I IMMEDIATELY INITIATED A COMPUTERIZED HDOF TO THE SECTOR AND CALLED THEM TO VERBALLY COORDINATE AS WELL. WHEN THE SUPVR QUESTIONED THE RECEIVING CTLR, THEY ADVISED THAT THEY WERE AWARE OF THE ACFT SINCE BEFORE IT ENTERED THEIR AIRSPACE, AND THEY WERE PROVIDING SEPARATION FOR THE ACFT, BUT THEY WERE TOO BUSY TO CALL ME AND ALERT ME TO THE SIT.
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.