United Air Lines EADS Socata A320 incident
EADS Socata A320 and American Airlines Boeing B757 · Incident: near collision between aircraft on approach
Narrative check · The NTSB narrative appears to contradict this record's date. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- OPS06IA004
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Aircraft 1 · EADS Socata A320
- Aircraft type
- Eads Socata A320
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- UNK
- Operator
- United Air Lines
- Onboard fatalities
- Unknown
- Route
- From Chicago O'Hare International Airport (ORD), Chicago, ILTo Las Vegas, NV
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 121: Air Carrier
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern final
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Near collision between aircraft
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Aircraft 2 · Boeing B757
- Aircraft type
- Boeing 757
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- UNK
- Operator
- American Airlines
- Onboard fatalities
- Unknown
- Route
- From Harry Reid International Airport (LAS), Las Vegas, NVTo Dallas Fort Worth International Airport (DFW), Dallas, TX
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 121: Air Carrier
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Initial climb
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Near collision between aircraft
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Atc clearance procedure › Inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On January 27, 2006, at 0044 UTC, a near midair collision occurred at McCarran International Airport, Las Vegas, Nevada, when UAL1547 was instructed to go around while on a visual approach to runway 19R and came into conflict with AAL1913 departing from runway 25R. UAL1547 made an evasive turn to the right to avoid a potential collision, and AAL1913 made a slight left turn. UAL1547 returned for landing at 0049, and AAL1913 continued to its destination. There was no reported damage to either aircraft, and no reported injuries to passengers or crew.
Probable cause
Deficient FAA procedures for separation of aircraft using converging runways, which failed to ensure that the tower controllers were able to provide adequate separation in the event of a go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record OPS06IA004
- Event ID
- 20080307X00282
- Case number
- OPS06IA004
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, damage. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-01-28.
- API snapshot SHA-256: 0346a5d4199af4f46278b4e464fbbf0bf3d01df5faecd6a5b512208156acba5d; retrieved 2026-09-18T14:55:39.080Z.