 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZTL controller reported that two of the same company aircraft had similar sounding call signs and both aircraft responded to a climb clearance.
| Attributes | |
| ACN | 1419003 |
| Time | |
| Date | 201701 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZTL.ARTCC |
| State Reference | GA |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6 |
| Events | |
| Anomaly | Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
I was working radar at the hi rock sector; having just shortly before this event experienced another reported event. I pointed-out aircraft X and aircraft Y to the clark hill sector climbing reference their aircraft Z (at FL350). Both climbing aircraft were climbing well and requesting FL410 (and on similar routes before splitting into the q-route system). I did not notify the 2 aircraft of similar sounding call signs because the numbers were in no way similar; and they had been on the same 3 ZTL frequencies following each other. I applied merging target procedures between aircraft Y (the trailing aircraft) and aircraft Z and told the aircraft it would be 2 minutes for higher. Aircraft Y reported aircraft Z in sight. Moment's later; I climbed aircraft X to FL410. The read back was indecipherable and it was clear to me that both pilots had read back the clearance. As soon as their transmissions stopped; I keyed the microphone and said quickly '@ aircraft' read back that clearance; it was only for aircraft X. Aircraft Y; maintain FL340.' aircraft Y promptly read back 'maintaining FL340' and I think apologized. 1 minute later; targets of aircraft Y and aircraft Z appeared to merge. A minute after that; I climbed aircraft Y to FL410.it seems clear enough to me; that aircraft Y heard '[company name]' and a climb to his requested altitude and assumed the clearance was for him.I took action as quickly as I could to prevent an event. Perhaps something datacom can help fix.
Original NASA ASRS Text
Title: ZTL Controller reported that two of the same company aircraft had similar sounding call signs and both aircraft responded to a climb clearance.
Narrative: I was working Radar at the HI ROCK sector; having just shortly before this event experienced another reported event. I pointed-out Aircraft X and Aircraft Y to the CLARK HILL sector climbing reference their Aircraft Z (at FL350). Both climbing aircraft were climbing well and requesting FL410 (and on similar routes before splitting into the Q-Route system). I did not notify the 2 aircraft of similar sounding call signs because the numbers were in no way similar; and they had been on the same 3 ZTL frequencies following each other. I applied merging target procedures between Aircraft Y (the trailing aircraft) and Aircraft Z and told the aircraft it would be 2 minutes for higher. Aircraft Y reported Aircraft Z in sight. Moment's later; I climbed Aircraft X to FL410. The read back was indecipherable and it was clear to me that both pilots had read back the clearance. As soon as their transmissions stopped; I keyed the microphone and said quickly '@ aircraft' read back that clearance; it was only for Aircraft X. Aircraft Y; maintain FL340.' Aircraft Y promptly read back 'Maintaining FL340' and I think apologized. 1 minute later; targets of Aircraft Y and Aircraft Z appeared to merge. A minute after that; I climbed Aircraft Y to FL410.It seems clear enough to me; that Aircraft Y heard '[company name]' and a climb to his requested altitude and assumed the clearance was for him.I took action as quickly as I could to prevent an event. Perhaps something Datacom can help fix.
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.