LAX89FA275 · Mooney M20F
Mooney M20F · Accident: in flight collision with object on approach
From Bellingham International Airport (BLI) to an unrecorded destination
Event
- NTSB case
- LAX89FA275
- 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
- 4 · 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
- Instrument 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
- CFSAB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bellingham International Airport (BLI), Bellingham, WATo 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 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
- 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
- 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); Wire, transmission
- 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 › VFR flight into imc, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FLIGHT HAD DEPARTED LIVERMORE ON 8/18 FOR AN EXTENDED TRIP. WHILE THE PILOT WAS AWAY, LAWRENCE LIVERMORE LABORATORY HAD INSTALLED ELECT TRANSMISSION LINES ON 200-FT TOWERS ON HILLS 6 MI EAST OF THE ARPT. THE LINES CROSSED A HIGHWAY AND WERE ABOUT 300-400 FT ABOVE THE VALLEY FLOOR. ACCORDING TO LOCAL PILOTS, WHEN FOG OR LOW CEILINGS COVERED THE ARPT, IT IS COMMON PRACTICE TO OVERFLY THE ARPT IN AN EASTERLY DIRECTION UNTIL THE GROUND IS VISIBLE, DESCEND, AND REVERSE COURSE UNDER THE CLOUDS FOLLOWING THE HIGHWAY WESTWARD TO THE ARPT. THE MAIN WRECKAGE WAS FOUND 300 YARDS WEST OF THE LINES AND NORTH OF THE HIGHWAY. THE RIGHT WING TIP WAS TORN FROM THE WING, AND WAS LOCATED UNDER THE LINES. GROUND WITNESSES STATED THE SKY WAS OVERCAST AND ESTIMATED THE CEILING AS 200 FT.
Probable cause
THE PILOT'S DECISION TO CONDUCT LOW LEVEL NIGHT FLIGHT UNDER LOW CEILINGS. CONTRIBUTING FACTORS WERE: THE DARK NIGHT, LOW CEILING, AND HIGH OBSTRUCTIONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX89FA275
- Event ID
- 20001213X29137
- Case number
- LAX89FA275
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1989-08-23.
- API snapshot SHA-256: a9de80a27e3d38c82217027e236bc028cdab3dfce3265bbe14ee213ad5a9884d; retrieved 2026-09-21T03:11:10.714Z.