FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA20LA327 · Mooney M20R

9 Sept 2020 · Weston, FL, United States

Mooney M20R · Accident: loss of engine power (total) en route

From Wing South Airpark (FA37) to Fort Lauderdale Executive Airport (FXE)

Report a problem

Event

NTSB case
ERA20LA327
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 M20R

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
N120GX
Operator
Unknown
Onboard fatalities
Unknown
Route
From Wing South Airpark (FA37), Naples, FLTo Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, FL
Aircraft age
About 14 years (built 2006)
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
Defining eventThe 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
Loss of engine power (total)
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

  • Aircraft › Aircraft power plant

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot completed a multi-day cross-country trip on the day prior to the accident flight during which he noted an increase in the engine’s oil consumption. The purpose of the accident flight was a planned trip for a scheduled oil change, where he also intended to ask the maintainer about the oil consumption. Prior to departing on the accident flight, he performed a preflight inspection and noted that the engine oil level was about 6.5 quarts. While in cruise flight about 20 minutes after departure, the engine lost all power. The pilot performed a successful forced landing to the right shoulder of an interstate highway, where the airplane came to a stop. As the pilot and passenger prepared to disembark, a truck struck the airplane’s left wing from behind, resulting in substantial damage to the wing. The pilot reported that the oil level after the accident was between 6 and 6.5 quarts.

A review of data recorded by the airplane’s avionics system revealed that during two previous legs of the cross-country trip the oil pressure began to gradually decrease and fluctuate about midway through each flight. During the last leg, the oil pressure decreased continuously throughout the entire flight. During the accident flight, the oil pressure remained in the green range until just prior to the loss of engine power.

During the most recent annual inspection, the engine oil was noted as excessively dirty and contaminants (“gunk”) were found in the oil filter pleats. Contaminated oil is commonly caused by an excessive interval between oil changes and/or excessive wear of the piston rings, neither of which appear to have occurred in this case. The oil change intervals were consistently within the manufacturer’s specifications and there was no significant loss of cylinder compression (a potential indicator of piston ring wear) noted during the last annual inspection. There were no anomalies noted with the oil and no debris noted in the oil filter during the following oil change, which was the last change before the accident flight.

Although the damage to the engine components was consistent with thermal damage due to a lack of lubrication, given the reported oil quantity after the accident and during the previous trip, as well as the gradual decreases in the recorded oil pressure on the previous flights, it is unlikely that the damage resulted from too little oil in the sump. The gradually decreasing oil pressure during the previous flights suggests a possible problem with the oil pump, an oil leak or restriction, or excessive oil temperature, no evidence of which was found during the examination. It is possible that the overheating and subsequent damage to the bearings began during one of the previous flights when the oil pressure decreased. The reasons for the decreased oil pressure and the increased oil consumption could not be determined.

The engine had never been overhauled, and at the time of the accident had reached just over half of the recommended operating hours between overhauls. However, it was 14 years old, which is 2 years past the recommended calendar time between overhauls. Had the engine been overhauled at the recommended calendar time, it is likely that the issue with the lubricating system could have been addressed or prevented.

Probable cause

A total loss of engine power because of the overheating and failure of the connecting rod bearings due to a lack of lubrication for reasons that could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA20LA327
Event ID
20200918X02045
Case number
ERA20LA327
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 3c9ef200b9ecd7ae98d6b6f7333619a97c930694b28ed2fce16142295c0a6a6b; retrieved 2026-09-16T13:03:49.396Z.