 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Dfw controller described operational deviation event when departure did not tag up; departure controller did not identification until 5 miles from the airport; claiming traffic complexity as causal.
| Attributes | |
| ACN | 792492 |
| Time | |
| Date | 200806 |
| Place | |
| Locale Reference | airport : dfw.airport |
| State Reference | TX |
| Altitude | msl single value : 2000 |
| Environment | |
| Flight Conditions | VMC |
| Weather Elements | Thunderstorm |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : dfw.tower |
| Operator | common carrier : air carrier |
| Make Model Name | Saab-Scania Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : initial climbout : intermediate altitude |
| Route In Use | departure sid : n/s |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : local |
| Qualification | controller : radar |
| Experience | controller limited radar : 25 controller military : 4 controller radar : 4 controller time certified in position1 : 14.5 |
| ASRS Report | 792492 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | non adherence : published procedure |
| Independent Detector | other controllera |
| Resolutory Action | none taken : detected after the fact |
| Supplementary | |
| Problem Areas | Navigational Facility ATC Human Performance Aircraft Flight Crew Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Deviation |
Narrative:
I was working the local control position combined with the coordinator position during a highly complex session and was distraction from noticing an SF34 from automatic acquiring. The session was complicated by numerous in trail restrs; a closed runway (runway 35C); delays; coordination with the tmc; departure controllers (for in trail releases off of satellite airports) and coordinating with a controller that was frustrating the session with 'grunts' when asked for releases (instead of approved or even improvised landline usage). Although the aircraft was specifically released by the satellite controller and he knew the aircraft was departing and the aircraft contacted him immediately upon departure; he failed to radar identify the aircraft or even question who the aircraft was until 5 mi from the airport. I believe this error was a case of improper staffing and although a frustrating experience it would have not happened if the proper position were staffed allowing me to watch my traffic instead of handling distrs.
Original NASA ASRS Text
Title: DFW CTLR DESCRIBED OPDEV EVENT WHEN DEP DID NOT TAG UP; DEP CTLR DID NOT ID UNTIL 5 MILES FROM THE ARPT; CLAIMING TFC COMPLEXITY AS CAUSAL.
Narrative: I WAS WORKING THE LCL CTL POS COMBINED WITH THE COORDINATOR POS DURING A HIGHLY COMPLEX SESSION AND WAS DISTR FROM NOTICING AN SF34 FROM AUTO ACQUIRING. THE SESSION WAS COMPLICATED BY NUMEROUS IN TRAIL RESTRS; A CLOSED RWY (RWY 35C); DELAYS; COORD WITH THE TMC; DEP CTLRS (FOR IN TRAIL RELEASES OFF OF SATELLITE ARPTS) AND COORDINATING WITH A CTLR THAT WAS FRUSTRATING THE SESSION WITH 'GRUNTS' WHEN ASKED FOR RELEASES (INSTEAD OF APPROVED OR EVEN IMPROVISED LANDLINE USAGE). ALTHOUGH THE ACFT WAS SPECIFICALLY RELEASED BY THE SATELLITE CTLR AND HE KNEW THE ACFT WAS DEPARTING AND THE ACFT CONTACTED HIM IMMEDIATELY UPON DEP; HE FAILED TO RADAR IDENT THE ACFT OR EVEN QUESTION WHO THE ACFT WAS UNTIL 5 MI FROM THE ARPT. I BELIEVE THIS ERROR WAS A CASE OF IMPROPER STAFFING AND ALTHOUGH A FRUSTRATING EXPERIENCE IT WOULD HAVE NOT HAPPENED IF THE PROPER POS WERE STAFFED ALLOWING ME TO WATCH MY TFC INSTEAD OF HANDLING DISTRS.
Data retrieved from NASA's ASRS site as of May 2009 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.