 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Tower supervisor described an unauthorized runway crossing that resulted in a go around event; noting similar call signs were involved.
| Attributes | |
| ACN | 1003819 |
| Time | |
| Date | 201204 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Skyhawk 172/Cutlass 172 |
| Flight Phase | Taxi |
| Route In Use | None |
| Flight Plan | VFR |
| Person 1 | |
| Function | Oceanic |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Ground Conflict Critical Deviation - Procedural Clearance Ground Incursion Runway |
Narrative:
[Air carrier flight] [aircraft X] cleared to land on runway 4R. C172 [aircraft Y] [cleared to land] on runway 4L. [Another] C172 [aircraft Z]; holding short of runway 4R at taxiway F. Local control cleared [aircraft Y] for take off on runway 4L. A squelch was heard on the read back possibly indicating that another aircraft was transmitting. [Aircraft Y] began take off roll and [aircraft Z] entered runway 4R with [air carrier X] within 1/2 mile final. Local assist advised local control that [aircraft Z] was moving. Local control advised [air carrier X] to go around. Subsequently the asde-X alarm advised that runway 4R was occupied; go around. Pilot [aircraft Z] reported that she read back what she thought was her clearance and proceeded on the runway and was not aware of the traffic on final. I do believe that the call signs of the aircraft were similar. The controller should have let the two aircraft know that there were similar sounding call signs on frequency and that they should use caution. I think also that after hearing the squelch when the aircraft read back the take off clearance that the controller should have verified that the take off clearance was for [aircraft X] only.
Original NASA ASRS Text
Title: Tower Supervisor described an unauthorized runway crossing that resulted in a go around event; noting similar call signs were involved.
Narrative: [Air carrier flight] [aircraft X] cleared to land on Runway 4R. C172 [aircraft Y] [cleared to land] on Runway 4L. [Another] C172 [aircraft Z]; holding short of Runway 4R at Taxiway F. Local Control cleared [aircraft Y] for take off on Runway 4L. A squelch was heard on the read back possibly indicating that another aircraft was transmitting. [Aircraft Y] began take off roll and [aircraft Z] entered Runway 4R with [air carrier X] within 1/2 mile final. Local Assist advised Local Control that [aircraft Z] was moving. Local Control advised [air carrier X] to go around. Subsequently the ASDE-X alarm advised that Runway 4R was occupied; go around. Pilot [aircraft Z] reported that she read back what she thought was her clearance and proceeded on the runway and was not aware of the traffic on final. I do believe that the call signs of the aircraft were similar. The Controller should have let the two aircraft know that there were similar sounding call signs on frequency and that they should use caution. I think also that after hearing the squelch when the aircraft read back the take off clearance that the Controller should have verified that the take off clearance was for [aircraft X] only.
Data retrieved from NASA's ASRS site as of July 2013 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.