 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZTL controller deleted a multiple data block only to discover an active data block with the same call sign had been dropped at another sector; stating companies should not file same call signs to the same airport.
| Attributes | |
| ACN | 947226 |
| Time | |
| Date | 201105 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZTL.ARTCC |
| State Reference | GA |
| Aircraft 1 | |
| Make Model Name | Light Transport Low Wing 2 Turboprop Eng |
| Operating Under FAR Part | Part 91 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I had a manual hand off call from cha approach about flight XXX to bhm. Was unable to flash. I looked him up and found him in my departure list. I dmed him but was unable due to duplicate flight plans. When he checked on I asked him to confirm his flight plan. He verified that he came from tys so I removed the strips on the other flight plan. Which was the same call sign going to the same airport (bhm) and dm'd him again. His data block popped up and everything worked fine. However; I was unaware that I had removed strips on an airborne aircraft in another sector with the same call sign; same destination; same time frame. Recommendation; ensure the company doesn't file same call signs to the same airport.
Original NASA ASRS Text
Title: ZTL Controller deleted a multiple data block only to discover an active data block with the same call sign had been dropped at another sector; stating companies should not file same call signs to the same airport.
Narrative: I had a manual hand off call from CHA Approach about Flight XXX to BHM. Was unable to flash. I looked him up and found him in my departure list. I DMed him but was unable due to duplicate flight plans. When he checked on I asked him to confirm his flight plan. He verified that he came from TYS so I removed the strips on the other flight plan. Which was the same call sign going to the same airport (BHM) and DM'd him again. His data block popped up and everything worked fine. However; I was unaware that I had removed strips on an airborne aircraft in another sector with the same call sign; same destination; same time frame. Recommendation; ensure the company doesn't file same call signs to the same airport.
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.