P50 CTLR EXPRESSED CONCERN REGARDING TWR CTLR'S FAILURE TO FOLLOW LOA; REF DEP PROCS; RESULTING IN IDENT CONFUSION WITH 2 DEPS.

Date: 2005-10 · Aircraft: Regional Jet 200 ER/LR (CRJ200) · Phase: initial_climb

Anomalies: deviation-discrepancy-procedural-published-material-policy

Synopsis

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.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.