OPS10IA015 · Cessna 208B
Cessna 208B and Southwest Airlines Boeing 737-7H4 · Incident: near midair/TCAS alert/loss of separation during landing
Event
- NTSB case
- OPS10IA015
- 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
- Event fatalities
- Unknown
- 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 · Cessna 208B
- Aircraft type
- Cessna 208
- 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
- N992FE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Flagstaff Pulliam Airport (FLG), Flagstaff, AZTo Phoenix Sky Harbor International Airport (PHX), Phoenix, AZ
- 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 135: Air Taxi & Commuter
- 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
- Landing · flare/touchdown
- Defining eventThe 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 midair/TCAS alert/loss of separation
- 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 737-7H4
- Aircraft type
- Boeing 737
- 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
- N742SW
- Operator
- Southwest Airlines
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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
- Taxi · into takeoff position
- Defining eventThe 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
- Airport occurrence
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While holding in position after being issued a takeoff clearance, the Boeing 737 captain noticed the Cessna 208 overflying his position and landing in front of him on runway 25R. The Cessna pilot was given clearance to land on runway 25L but instead landed on runway 25R, missing the 737 by about 50 feet. The pilot of the Cessna 208 noted having difficulty seeing the runway due to the setting sun beyond the departure end of runway 25R. Furthermore, he did not state whether or not he was able to make visual contact on final approach with the Boeing 737 that was holding in position in front of him on the runway.
Probable cause
The Cessna 208 pilot’s failure to identify the correct landing runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record OPS10IA015
- Event ID
- 20100317X00948
- Case number
- OPS10IA015
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates, damage. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2010-03-20.
- API snapshot SHA-256: cbb08e0cd8deed6dbcfa80c2f290b4ed307cc1dff5c5af21dd4af6d6eaf87468; retrieved 2026-09-13T18:16:03.591Z.