ATL82DA064 · Mooney M20F
Mooney M20F · Accident: total loss of engine power (mechanical failure) en route
From Greenville, KY to Muhlenberg County Airport (M21)
Event
- NTSB case
- ATL82DA064
- 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 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
- N6318Q
- Operator
- David E. Rabold · private individual
- Onboard fatalities
- Unknown
- Route
- From Greenville, KYTo Muhlenberg County Airport (M21), Bowling Green, KY
- 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
- Total loss of engine power (mechanical failure)
- 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
- Engine assembly, crankcase › Failure, partial
- Fluid, oil › Exhaustion
- Lubricating system, oil line › Chafed
- Lubricating system, oil line › Leak
- Other maintenance personnel › Maintenance, installation, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER LEVELING AT 2500 FT, OIL FUMES WERE NOTED, BUT NO ABNORMAL INDICATIONS WERE NOTED ON THE ENGINE GAUGES. THE PILOT SUSPECTED OIL HAD BEEN SPILLED DURING A REPAIR BEFORE TAKEOFF. A SHORT TIME LATER, THE ENGINE RPM BEGAN TO INCREASE & WAS ADJUSTED BY THE PILOT. SUBSEQUENTLY, THE ENGINE FAILED. DURING A FORCED LANDING, THE PILOT WAS UNABLE TO REACH A ROAD & LANDED IN A FIELD. THE MAIN GEAR FAILED AFTER HITTING A DITCH. THE RIGHT WING WAS DAMAGED AFTER CONTACTING THE GROUND & THE LEFT WING HIT A FENCE. AN EXAMINATION REVEALED THERE WAS OIL ALONG THE LEFT SIDE OF THE FUSELAGE. A HOLE WAS FOUND IN THE ENGINE CASE BETWEEN THE NUMBER 2 & 4 CYLINDERS. THE INLET OIL LINE TO THE OIL COOLER HAD CHAFED AGAINST THE EXHAUST STACK & WAS LEAKING. IT SHOULD HAVE BEEN ROUTED UNDER A HEAT SHIELD & AWAY FROM THE EXHAUST STACK. THE OIL LINE SHOULD HAVE BEEN A STANDARD, MEDIUM PRESSURE, STRATOFLEX HOSE (MIL-H-8794D) REINFORCED WITH A FIBER BRAIDS & A STEEL BRAID. THE INSTALLED HOSE HAD A SINGLE FIBER BRAID COVERING.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82DA064
- Event ID
- 20020917X01675
- Case number
- ATL82DA064
- 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: 2894eef5f288abb049a19752730c8275ae2420d2c55880d9e25a7296b8dfe062; retrieved 2026-09-24T03:36:53.683Z.