37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1454647 |
Time | |
Date | 201706 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZDC.ARTCC |
State Reference | VA |
Aircraft 1 | |
Make Model Name | EMB ERJ 145 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Bombardier/Canadair Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 13 |
Person 2 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 26 |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
I was expecting aircraft X to check on frequency. However aircraft Y was the aircraft which actually checked on. I hadn't noticed different call sign nor was I expecting a similar sounding aircraft to check in; hence I descended aircraft Y to 21000 feet. A moment later aircraft X checked on frequency which caused suspicion and called up aircraft Y after hearing across the room another controller calling aircraft Y. I quick looked the sector and saw the event in progress. I told the controller I will stop aircraft Y at 29000 feet; promptly called close proximity traffic and after coordination I made a communication change to next controller sector.this was a similar sounding call sign event. By aircraft checking on frequency and not stating their assigned altitude didn't help me to recognize that incorrect call sign from expectation of another aircraft; still a recognition issue none the less.
Original NASA ASRS Text
Title: Center Controllers reported the wrong aircraft took a frequency change and descent clearance due to similar sounding callsigns.
Narrative: I was expecting Aircraft X to check on frequency. However Aircraft Y was the aircraft which actually checked on. I hadn't noticed different call sign nor was I expecting a similar sounding aircraft to check in; hence I descended Aircraft Y to 21000 feet. A moment later Aircraft X checked on frequency which caused suspicion and called up Aircraft Y after hearing across the room another controller calling Aircraft Y. I quick looked the sector and saw the event in progress. I told the controller I will stop Aircraft Y at 29000 feet; promptly called close proximity traffic and after coordination I made a communication change to next controller sector.This was a similar sounding call sign event. By aircraft checking on frequency and not stating their assigned altitude didn't help me to recognize that incorrect call sign from expectation of another aircraft; still a recognition issue none the less.
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.