 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
P50 controller expressed concern regarding tower controller's failure to follow LOA; reference departure procedures; resulting in identify confusion with 2 departures.
| Attributes | |
| ACN | 674562 |
| Time | |
| Date | 200510 |
| Place | |
| Locale Reference | airport : phx.airport |
| State Reference | AZ |
| Altitude | msl single value : 7000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : p50.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | Regional Jet 200 ER&LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : initial |
| Route In Use | departure sid : maxxo |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tracon : p50.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : initial |
| Route In Use | departure sid : chily |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Qualification | controller : non radar controller : radar |
| Experience | controller non radar : 8 controller radar : 7 |
| ASRS Report | 674562 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : handoff position |
| Qualification | controller : non radar controller : radar |
| Experience | controller military : 5 controller non radar : 7 controller radar : 20 |
| ASRS Report | 674556 |
| Events | |
| Anomaly | non adherence : published procedure |
| Independent Detector | other controllera other controllerb |
| Resolutory Action | none taken : detected after the fact |
| Supplementary | |
| Problem Areas | ATC Human Performance FAA |
| Primary Problem | ATC Human Performance |
| Situations | |
| ATC Facility | procedure or policy : phx.tower procedure or policy : p50.tracon |
Narrative:
Air carrier X; a CRJ2; departed phx on a maxxo departure (southeast departure); checked on with the south departure controller. Aircraft is on wrong beacon code. South departure controller radar idents the aircraft and instructs air carrier X to reset the transponder to a correct code. In the meantime; air carrier Y departed behind the air carrier X on a chily departure (northwest departure). Air carrier Y assigned beacon code is 1 number different than the air carrier X. Air carrier Y mistakenly put air carrier X's code in his transponder and the data tag acquired as air carrier X. Air carrier X forgot to turn his transponder on; so it was then a primary target only. Air carrier Y checks onto my frequency; but since the data tag reads as air carrier X I don't know where or who air carrier Y is. We also failed to receive a flight strip via the efsts for the air carrier Y departure. The south departure controller thinks that the new air carrier X tag is the correct aircraft; not realizing that air carrier X is a primary target. We were able to determine that air carrier Y was on the wrong code; and correct that. The south departure controller also was able to then correctly tag and identify air carrier X. Causal factors: 1) tower failed to call the no-tag on air carrier X. 2) failure to receive a flight strip on air carrier Y. 3) south departure losing track of the primary target of air carrier X.
Original NASA ASRS Text
Title: P50 CTLR EXPRESSED CONCERN REGARDING TWR CTLR'S FAILURE TO FOLLOW LOA; REF DEP PROCS; RESULTING IN IDENT CONFUSION WITH 2 DEPS.
Narrative: ACR X; A CRJ2; DEPARTED PHX ON A MAXXO DEP (SE DEP); CHKED ON WITH THE S DEP CTLR. ACFT IS ON WRONG BEACON CODE. S DEP CTLR RADAR IDENTS THE ACFT AND INSTRUCTS ACR X TO RESET THE XPONDER TO A CORRECT CODE. IN THE MEANTIME; ACR Y DEPARTED BEHIND THE ACR X ON A CHILY DEP (NW DEP). ACR Y ASSIGNED BEACON CODE IS 1 NUMBER DIFFERENT THAN THE ACR X. ACR Y MISTAKENLY PUT ACR X'S CODE IN HIS XPONDER AND THE DATA TAG ACQUIRED AS ACR X. ACR X FORGOT TO TURN HIS XPONDER ON; SO IT WAS THEN A PRIMARY TARGET ONLY. ACR Y CHKS ONTO MY FREQ; BUT SINCE THE DATA TAG READS AS ACR X I DON'T KNOW WHERE OR WHO ACR Y IS. WE ALSO FAILED TO RECEIVE A FLT STRIP VIA THE EFSTS FOR THE ACR Y DEP. THE S DEP CTLR THINKS THAT THE NEW ACR X TAG IS THE CORRECT ACFT; NOT REALIZING THAT ACR X IS A PRIMARY TARGET. WE WERE ABLE TO DETERMINE THAT ACR Y WAS ON THE WRONG CODE; AND CORRECT THAT. THE S DEP CTLR ALSO WAS ABLE TO THEN CORRECTLY TAG AND IDENT ACR X. CAUSAL FACTORS: 1) TWR FAILED TO CALL THE NO-TAG ON ACR X. 2) FAILURE TO RECEIVE A FLT STRIP ON ACR Y. 3) S DEP LOSING TRACK OF THE PRIMARY TARGET OF ACR X.
Data retrieved from NASA's ASRS site as of January 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.