 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Savannah TRACON controller reported the tower departed an aircraft with the wrong flight plan and beacon code due to similar call signs.
| Attributes | |
| ACN | 1623654 |
| Time | |
| Date | 201903 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | SAV.TRACON |
| State Reference | GA |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Departure |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1.0 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I was working approach and the tower launched an aircraft and scanned down an aircraft X flight strip. I received the strip and looked over it and saw the call sign; type; and first fix. I continued to work other aircraft in my airspace and eventually aircraft Y called on departure. I radar identified him and issued 10;000 feet and cleared direct. At this point I was only observing the call sign on my radar display. The tower scanned the wrong strip but the aircraft were on similar departure routes. It was not known to me that it was the wrong aircraft for the strip until approximately 30 minutes later when there was an issue with an aircraft being released ten minutes early. Aside from the initial scan of the strip after print out; the only difference in the two flight plans that affect us directly was one number in the call sign. As controllers we can maybe do better double checking call signs on flight strips. This was a unique situation that began in the tower. Local control missed it but the pilot also did not bother to correct the controller on the call sign mix up.
Original NASA ASRS Text
Title: Savannah TRACON Controller reported the Tower departed an aircraft with the wrong flight plan and beacon code due to similar call signs.
Narrative: I was working approach and the Tower launched an aircraft and scanned down an Aircraft X flight strip. I received the strip and looked over it and saw the call sign; type; and first fix. I continued to work other aircraft in my airspace and eventually Aircraft Y called on Departure. I radar identified him and issued 10;000 feet and cleared direct. At this point I was only observing the call sign on my radar display. The Tower scanned the wrong strip but the aircraft were on similar departure routes. It was not known to me that it was the wrong aircraft for the strip until approximately 30 minutes later when there was an issue with an aircraft being released ten minutes early. Aside from the initial scan of the strip after print out; the only difference in the two flight plans that affect us directly was one number in the call sign. As controllers we can maybe do better double checking call signs on flight strips. This was a unique situation that began in the Tower. Local Control missed it but the pilot also did not bother to correct the controller on the call sign mix up.
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.