 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Slc controller expressed concern regarding the similar sounding flight numbers that led to confusion with regard to aircraft identity.
| Attributes | |
| ACN | 1068601 |
| Time | |
| Date | 201302 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | SLC.Airport |
| State Reference | UT |
| Aircraft 1 | |
| Make Model Name | Regional Jet 700 ER/LR (CRJ700) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Taxi |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Regional Jet 700 ER/LR (CRJ700) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Taxi |
| Flight Plan | IFR |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
I was working lcc in a north operation. I had the straight out automatic releases while local control west had the turn automatic releases. I had the strip for flight abcd on the nsign departure (straight out). Without scanning the asde-X initially; I told flight abcd to line up and wait (luaw). When the aircraft responded and started to move; I was looking at the asde-X and noticed in the tag that it said pbo which would indicate he was on the pecop departure (turn) and that the call sign didn't match it was flight agcd. I asked the pilot which he was and he replied flight agcd. I went over to ground control; got the correct strip; got a release from lcw for the turn departure and cleared the aircraft for take off. The ground controller reported to me that the aircraft in question had been calling himself and answering to flight abcd. It should be noted also that there was a flight abcg. All of these aircraft ended up leaving within minutes of each other. Recommendation; airline company may want to consider looking through their call signs and changing those that are similar or at least those that are similar and are scheduled to depart close together.
Original NASA ASRS Text
Title: SLC Controller expressed concern regarding the similar sounding flight numbers that led to confusion with regard to aircraft identity.
Narrative: I was working LCC in a North operation. I had the straight out automatic releases while Local Control West had the turn automatic releases. I had the strip for Flight ABCD on the NSIGN departure (Straight Out). Without scanning the ASDE-X initially; I told Flight ABCD to Line Up and Wait (LUAW). When the aircraft responded and started to move; I was looking at the ASDE-X and noticed in the tag that it said PBO which would indicate he was on the PECOP departure (TURN) and that the call sign didn't match it was Flight AGCD. I asked the pilot which he was and he replied Flight AGCD. I went over to Ground Control; got the correct strip; got a release from LCW for the turn departure and cleared the aircraft for take off. The Ground Controller reported to me that the aircraft in question had been calling himself and answering to Flight ABCD. It should be noted also that there was a Flight ABCG. All of these aircraft ended up leaving within minutes of each other. Recommendation; Airline Company may want to consider looking through their call signs and changing those that are similar or at least those that are similar and are scheduled to depart close together.
Data retrieved from NASA's ASRS site as of July 2013 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.