LAX99LA009 · Cessna 182P
Cessna 182P · Accident: in flight collision with object on approach
From Sedona Airport (SEZ) to E69
Event
- NTSB case
- LAX99LA009
- 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
- Accident
- 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
- 0
- 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
- General aviation
- 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
Cessna 182P
- Aircraft type
- Cessna 182
- 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
- N1938M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sedona Airport (SEZ), Sedona, AZTo E69
- 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 91: General Aviation
- 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 go-around
- 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
- In flight collision with object
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Directional control, not maintained
- Pilot in command › Proper alignment, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane drifted off of the runway, collided with a boulder and overturned during a go-around following a bounced landing. The pilot and his passengers were returning to their home airport after flying out for breakfast. As the airplane entered the traffic pattern, the pilot noticed men and equipment on the runway. He asked UNICOM to clear the runway. The men vacated the runway but parked the equipment in close proximity to the pavement edge, approximately 1,000 feet down from the approach end of the runway. The pilot flew a slightly high approach in order to avoid landing prior to the men and equipment. After bouncing the landing, the pilot attempted to go around. The airplane drifted off the runway and struck a boulder, which sheared off the nose wheel and strut. It continued to slide on its nose for a short distance before the nose dug in and it nosed over onto its back. The pilot said there was no mechanical malfunction or failure of the airplane or its systems prior to the accident.
Probable cause
the pilot's failure to maintain runway alignment during a go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX99LA009
- Event ID
- 20001211X11288
- Case number
- LAX99LA009
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 7c360d09595da137c819691e4adff1e96c4afacd0f0cc4b535b48e28dbe7dbac; retrieved 2026-09-21T20:40:22.121Z.