 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZAU controller described similar call sign event that resulted in an uncoordinated descent into an adjacent sector's airspace.
| Attributes | |
| ACN | 865038 |
| Time | |
| Date | 200912 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZAU.ARTCC |
| State Reference | IL |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 145 ER&LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | EMB ERJ 145 ER&LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance |
Narrative:
I had both air carrier XXXX and air carrier xxyx on frequency inbound to ord. I was unaware of similar call signs at the time I issued a descent clearance to air carrier XXXX to FL250. After the clearance was issued and read back by air carrier xxyx; air carrier XXXX questioned the clearance and advised I had similar call signs on frequency. I tried to get air carrier xxyx to maintain altitude but he had already started his descent in cleveland centers airspace. I called the ZOB sector to advise what happened and then got the aircraft on frequency to the appropriate altitudes. Recommendation; similar call signs are always a risk. I am not sure why I didn't realize they were both on frequency but I didn't. Even when questioned by the correct pilot; and I realized the mix up; I still didn't hear clearly the correct call sign. Our frequencies are not always crystal clear and the voice inflections of pilots and controllers can easily make air carrier XXXX sound like air carrier xxyx. We will always have similar call signs in this business; I guess the best recommendation would be to be as alert to this possibility as one could be so it doesn't bite you.
Original NASA ASRS Text
Title: ZAU Controller described similar call sign event that resulted in an uncoordinated descent into an adjacent sector's airspace.
Narrative: I had both Air Carrier XXXX and Air Carrier XXYX on frequency inbound to ORD. I was unaware of similar call signs at the time I issued a descent clearance to Air Carrier XXXX to FL250. After the clearance was issued and read back by Air Carrier XXYX; Air Carrier XXXX questioned the clearance and advised I had similar call signs on frequency. I tried to get Air Carrier XXYX to maintain altitude but he had already started his descent in Cleveland Centers airspace. I called the ZOB sector to advise what happened and then got the aircraft on frequency to the appropriate altitudes. Recommendation; similar call signs are always a risk. I am not sure why I didn't realize they were both on frequency but I didn't. Even when questioned by the correct pilot; and I realized the mix up; I still didn't hear clearly the correct call sign. Our frequencies are not always crystal clear and the voice inflections of pilots and controllers can easily make Air Carrier XXXX sound like Air Carrier XXYX. We will always have similar call signs in this business; I guess the best recommendation would be to be as alert to this possibility as one could be so it doesn't bite you.
Data retrieved from NASA's ASRS site as of April 2012 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.