 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Salt lake center controller reported routing confusion due to two aircraft using the same squawk code.
| Attributes | |
| ACN | 1607009 |
| Time | |
| Date | 201901 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZLC.ARTCC |
| State Reference | UT |
| Aircraft 1 | |
| Make Model Name | A319 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | B737-800 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 16 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X was in canada's airspace squawking the wrong code of XXXX. Code XXXX was assigned to aircraft Y who was already in my airspace. When I went to track up aircraft X I did a 'track pick XXXX'. This moved the track from where aircraft Y was and moved it up into canada's airspace to the XXXX code there. I was busy and did not realize that this track was moved from the actual aircraft Y who was approximately 175 miles south of aircraft X. I realized that this is the wrong call sign and drop the track. Since it was over 150 miles away the track did not go back to where aircraft Y actually was. I started a track for aircraft X and when he came over I assigned him his code of XXXZ and it paired. Aircraft Y flew through my airspace without a track for over 100 miles without me even noticing it. As the intruder target approached the next sector they happened to notice it and started a track and initialized the inquiry as to what happened.somehow a track should not be allowed to be moved off an existing target to a target in canada's airspace and if it does it should be able to go back to its original target once dropped from the wrong target.
Original NASA ASRS Text
Title: Salt Lake Center Controller reported routing confusion due to two aircraft using the same squawk code.
Narrative: Aircraft X was in Canada's airspace squawking the wrong code of XXXX. Code XXXX was assigned to Aircraft Y who was already in my airspace. When I went to track up Aircraft X I did a 'track pick XXXX'. This moved the track from where Aircraft Y was and moved it up into Canada's airspace to the XXXX code there. I was busy and did not realize that this track was moved from the actual Aircraft Y who was approximately 175 miles south of Aircraft X. I realized that this is the wrong call sign and drop the track. Since it was over 150 miles away the track did not go back to where Aircraft Y actually was. I started a track for Aircraft X and when he came over I assigned him his code of XXXZ and it paired. Aircraft Y flew through my airspace without a track for over 100 miles without me even noticing it. As the intruder target approached the next sector they happened to notice it and started a track and initialized the inquiry as to what happened.Somehow a track should not be allowed to be moved off an existing target to a target in Canada's airspace and if it does it should be able to go back to its original target once dropped from the wrong target.
Data retrieved from NASA's ASRS site 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.