37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1628809 |
Time | |
Date | 201903 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | NEW.Airport |
State Reference | LA |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | None |
Flight Plan | VFR |
Person 1 | |
Function | Ground Supervisor / CIC |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 4.2 |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Ground Incursion Runway |
Narrative:
Aircraft X was inbound from the east assigned 36R by local control (local control.) a flight of 4 was inbound for the overhead maneuver 36L. The controller working local control called the flight traffic out to aircraft X; but misidentified their landing runway as 18L. Being controller in charge (controller in charge) as well as ground control (ground control); I pointed out the mistake. Local control keyed up and said 'correction; that's 36L.' I knew this was ambiguous and watched final in case aircraft X misunderstood and lined up for the wrong runway. When the last flight aircraft joined final for 36L out of the overhead; I thought it might be aircraft X because he was still distant and also a low wing aircraft. When I asked local control if it was aircraft X lined up for the wrong runway; he replied that it was not. I then turned my attention to briefing the next controller for ground control and controller in charge. A bit later; I found out that during the briefing aircraft X did in fact line up for the wrong runway after the flight landed; and had initiated a go around because local control had placed another aircraft on the runway in front of him.despite knowing the situation required extra attention; I trusted that local control would watch and handle it after I brought attention to the possibility. I could have delayed the briefing and monitored the situation through its end. However; as a tower team member responsible for several other areas of the operation; I also feel there are limits to the amount attention that can or should be given to other positions. I did have a conversation with that controller afterward and pointed out where the ambiguity came from.
Original NASA ASRS Text
Title: NEW Tower Controller reported that due to transmission ambiguity an aircraft lined up for the incorrect runway; causing a potential runway incursion; and go-around.
Narrative: Aircraft X was inbound from the east assigned 36R by LC (Local Control.) A flight of 4 was inbound for the overhead maneuver 36L. The controller working LC called the flight traffic out to Aircraft X; but misidentified their landing runway as 18L. Being CIC (Controller In Charge) as well as GC (Ground Control); I pointed out the mistake. LC keyed up and said 'Correction; that's 36L.' I knew this was ambiguous and watched final in case Aircraft X misunderstood and lined up for the wrong runway. When the last flight aircraft joined final for 36L out of the overhead; I thought it might be Aircraft X because he was still distant and also a low wing aircraft. When I asked LC if it was Aircraft X lined up for the wrong runway; he replied that it was not. I then turned my attention to briefing the next controller for GC and CIC. A bit later; I found out that during the briefing Aircraft X did in fact line up for the wrong runway after the flight landed; and had initiated a go around because LC had placed another aircraft on the runway in front of him.Despite knowing the situation required extra attention; I trusted that LC would watch and handle it after I brought attention to the possibility. I could have delayed the briefing and monitored the situation through its end. However; as a tower team member responsible for several other areas of the operation; I also feel there are limits to the amount attention that can or should be given to other positions. I did have a conversation with that controller afterward and pointed out where the ambiguity came from.
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.