ATL87LA172 · Mooney M20A
Mooney M20A · Accident: total loss of engine power (mechanical failure) en route
From Burke Lakefront Airport (BKL) to W66 · MIDLAND, VA
Event
- NTSB case
- ATL87LA172
- 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
Mooney M20A
- 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
- N8391E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Burke Lakefront Airport (BKL), Cleveland, OHTo W66 · MIDLAND, VA
- 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 · climb to 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
- Total loss of engine power (mechanical failure)
- 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
- Fuel exhaustion
- 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
- Fluid, fuel › Exhaustion
- Fuel system, strainer › Leak
- Other maintenance personnel › Maintenance, installation, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT STRUCK A FENCE DURING A FORCED LDG, FOLLOWING A LOSS OF ENGINE PWR IN FLIGHT. THE PLT REPORTED THAT HE HAD TOPPED OFF BOTH MAIN FUEL TANKS PRIOR TO DEPARTURE. ABOUT 10 MINUTES AFTER DEPARTURE AT ABOUT 4000 FT MSL, HE SMELLED FUEL FUMES IN THE COCKPIT. HE OBSERVED THAT THE FUEL LEVEL GAUGE FOR THE TANK IN USE WAS INDICATING 1/2 FULL. THE ENGINE COMPLETELY LOST POWER SHORTLY THEREAFTER. EFFORTS TO RESTART THE ENGINE BY TURNING ON THE BOOST PUMP AND SWITCHING TANKS WERE UNSUCCESSFUL. POST-CRASH EXAM OF THE ACFT BY THE FAA REVEALED EVIDENCE OF A FUEL GASCOLATOR LEAK. THE GASCOLATOR GASKETS APPEARED TO BE HOMEMADE. NO PROBLEMS WERE FOUND TO EXIST IN THE REST OF THE FUEL SYSTEM OR THE ENGINE. THE ACFT HAD ACQUIRED 2 HRS FLT TIME SINCE THE LAST ANNUAL, WHICH WAS ACCOMPLISHED 3 WEEKS BEFORE THE ACCIDENT. THE MECHANIC WHO PERFORMED THE ANNUAL REPORTED THAT HE HAD DISASSEMBLED AND CLEANED THE GASCOLATOR PRIOR TO COMPLETING THE INSPECTION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL87LA172
- Event ID
- 20001213X31100
- Case number
- ATL87LA172
- 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: 8bb23980f7cf4e6df95916487751b5969b9aa1c935254e83cad2a33dbf4d075e; retrieved 2026-09-22T00:50:20.534Z.