Aircraft near Las Vegas, NV — 2012-04-27
- Date
- 2012-04-27
- Location
- Las Vegas, NV, USA
- Fatalities
- 0
- Phase of flight
- Approach
Probable cause
Federal Aviation Administration procedures that do not ensure separation in the event of a go-around during simultaneous independent runway operations on runways that do not physically intersect but whose flight paths intersect.
NTSB narrative
The flight crew of an Airbus A320, operated by an air carrier, was conducting a visual approach to runway 25L while a Learjet 60 (LR60) was simultaneously cleared for takeoff from runway 19L. The pilot of the A320 elected to execute a go-around and came into hazardous proximity with the LR60 as it departed runway 19L. After the pilot of the A320 executed the go-around, neither local controller was able to provide control instructions to separate the two aircraft. The closest proximity of the two aircraft was approximately 0.3 nautical miles laterally and 100 feet vertically. The two aircraft were being controlled by different tower controllers, who were simultaneously routing aircraft to land on runway 25L and to depart from runway 19L--nonintersecting, converging runways whose flight paths intersect. This procedure was not prohibited by the Federal Aviation Administration (FAA), and there were no FAA-prescribed separation minima or procedures for air traffic controllers to follow when conducting simultaneous independent converging runway operations in the event a pilot elected to execute a go-around. This resulted in the aircraft going around coming into close proximity with the departure aircraft where the flight paths intersected.
Analysis
- Primary failure mode
- Human factors
- First missed decision gate
- ATC coordination to prevent conflict during simultaneous operations.
NTSB coding
- Near midair/TCAS alert/loss of separation · Initial climb
Evidence available
- ATC audio
- ADS-B / radar
- 4 docket documents
Docket documents4
Related mishaps
- DIAMOND AIRCRAFT IND INC DA20-C1
2023-12-09 · North Las Vegas, NV