LAX90FA092 · Mooney M20F
Mooney M20F · Accident: in flight encounter with weather en route
From Sacramento Executive Airport (SAC) to Meadows Field (BFL)
Event
- NTSB case
- LAX90FA092
- 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
- 2 · 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 M20F
- 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
- N4093N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sacramento Executive Airport (SAC), Sacramento, CATo Meadows Field (BFL), Bakersfield, CA
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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 › Altitude, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE NON-INSTRUMENT RATED PILOT RECEIVED A WEATHER BRIEFING WHICH INDICATED THAT VFR FLYING ALONG HIS PROPOSED SOUTHBOUND ROUTE OF FLIGHT WAS NOT RECOMMENDED. THE PILOT FILED A VFR FLIGHT PLAN AND DEPARTED. AS THE PILOT FLEW SOUTHBOUND HE WAS OBSERVED BELOW THE BASE OF CLOUDS WHICH WAS AT 500 FEET AGL. SEVERAL MINUTES LATER THE PILOT ENCOUNTERED GROUND FOG WHICH REDUCED HIS VISIBILITY. A GROUND-BASED WITNESS REPORTED THAT HIS VISIBILITY AT THE CRASH SITE WAS 1/4 MILE. THE AIRPLANE COLLIDED WITH THE GROUND IN A NOSE LOW AND RIGHT WING LOW ATTITUDE.
Probable cause
THE PILOT FLEW INTO INSTRUMENT CONDITION, BECAUSE SPATIALLY DISORIENTATED AND COLLIDED WITH TERRAIN. FACTOR WAS FOGGY WEATHER CONDITIONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX90FA092
- Event ID
- 20001212X22581
- Case number
- LAX90FA092
- 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: 5193330da4b041bf2121af4ee74437bdaf6a8e393d2d17cbf8b74ed9f39a4655; retrieved 2026-09-21T02:57:16.258Z.