LAX96FA294 · Mooney M20K
Mooney M20K · Accident: in flight encounter with weather en route
From Zamperini Field (TOA) to Shalz Field (CBK)
Event
- NTSB case
- LAX96FA294
- 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
- 1 · 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
Mooney M20K
- Aircraft type
- Mooney M20
- 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
- N4634H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Zamperini Field (TOA), Torrance, CATo Shalz Field (CBK), Colby, KS
- 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
- En route · cruise
- 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 encounter with weather
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aircraft control, uncontrolled
- Pilot in command › Incapacitation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was deviating for weather and reported cumulous buildups and electrical discharges with tops at and above his flight level. Radar data showed the aircraft ground track turning north as it began an unannounced descent. The descent continued until radar contact was lost. Witnesses reported seeing the aircraft break out of the overcast, making a series of random turns, climbs, and dives before it collided with the canyon wall. The aircraft collided with the canyon wall near Pima Point. Thunderstorms had developed along the route several hours sooner than forecast. Examination of recorded weather radar data disclosed that a level 6 thunderstorm with tops to 49,000 feet was present at the location and time of the accident. There was no record of the pilot requesting or receiving updated weather information after his final DUATS briefing 4 hours prior to the accident. No evidence of mechanical discrepancies were found during the wreckage examination.
Probable cause
due to an in-flight loss of control resulting from a probable incapacitation for unknown reasons. The loss of control occurred while the aircraft was being flown in close proximity to a level 6 thunderstorm. The failure of the pilot to obtain current weather information was a factor in this accident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX96FA294
- Event ID
- 20001208X06539
- Case number
- LAX96FA294
- 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: 92b61826c17d09b8a5a79f8dbaea77f285df43ca68cb1dc4d96c7c758cb1b931; retrieved 2026-09-20T23:14:46.908Z.