 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Los angeles center controller reported a problem with similar sounding call signs. Reporter was supposed to be talking to one aircraft; while another aircraft with a different company name was actually on the frequency responding to the reporter.
| Attributes | |
| ACN | 1394555 |
| Time | |
| Date | 201610 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZLA.ARTCC |
| State Reference | CA |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Boeing Company Undifferentiated or Other Model |
| 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) 8.0 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X was in level flight eastbound to denver at FL310. Aircraft Y checked on my frequency. I thought it was aircraft Z who checked on. I was not supposed to be talking to aircraft Y; in fact; sector 35 had radar on aircraft Y over tbc. I was supposed to be talking to aircraft Z. I notice the aircraft Z is starting to descend right into aircraft X. I tell aircraft Z to maintain flight level 320. The entire time I am talking to aircraft Z ; aircraft Y is answering. I don't even see aircraft Y until finally in the interaction he says he is over tbc. That's when myself and the D side figured out what was going on. Aircraft Z had taken aircraft Y's clearances from denver center; and aircraft Y had taken the wrong clearances from denver center as well. Aircraft X reported that aircraft Z was in fact descending and he did receive a resolution advisory (RA) but did not have to respond to the RA. It's hard to describe all the details of this scenario. The only way to get the full picture will be to review the situation and see it and hear it as it all plays out. I'm not sure what recommendations I would have for this one. It was basically the perfect storm with the similar sounding call signs; and the way the entire situation rolled out. We got lucky that aircraft Z did not hit aircraft X.
Original NASA ASRS Text
Title: Los Angeles Center Controller reported a problem with similar sounding call signs. Reporter was supposed to be talking to one aircraft; while another aircraft with a different company name was actually on the frequency responding to the reporter.
Narrative: Aircraft X was in level flight eastbound to Denver at FL310. Aircraft Y checked on my frequency. I thought it was aircraft Z who checked on. I was not supposed to be talking to aircraft Y; in fact; Sector 35 had radar on aircraft Y over TBC. I was supposed to be talking to aircraft Z. I notice the aircraft Z is starting to descend right into aircraft X. I tell aircraft Z to maintain flight level 320. The entire time I am talking to aircraft Z ; aircraft Y is answering. I don't even see aircraft Y until finally in the interaction he says he is over TBC. That's when myself and the D Side figured out what was going on. Aircraft Z had taken aircraft Y's clearances from Denver Center; and aircraft Y had taken the wrong clearances from Denver Center as well. Aircraft X reported that aircraft Z was in fact descending and he did receive a Resolution Advisory (RA) but did not have to respond to the RA. It's hard to describe all the details of this scenario. The only way to get the full picture will be to review the situation and see it and hear it as it all plays out. I'm not sure what recommendations I would have for this one. It was basically the perfect storm with the similar sounding call signs; and the way the entire situation rolled out. We got lucky that aircraft Z did not hit aircraft X.
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.