FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09LA362 · Mooney M20C

22 Jul 2009 · Elma, WA, United States

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

From Olympia Regional Airport (KOLM) to Olympia Regional Airport (KOLM)

Report a problem

Event

NTSB case
WPR09LA362
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
1 · all aircraft and ground
Ground fatalities
Unknown
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 M20C

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
N6422U
Operator
Donald C Mead · private individual
Onboard fatalities
Unknown
Route
From Olympia Regional Airport (KOLM), Olympia, WATo Olympia Regional Airport (KOLM), Olympia, WA
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
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
Destroyed

Cause areas

  • Aircraft › Aircraft power plant

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane was returning to its home airport following an aerial observation mission. A witness reported that the airplane was making a clattering noise as it flew over her home and commented that it sounded as if it was running out of oil. The witness estimated the airplane to be 100-150 feet above ground level. A second witness reported that the airplane descended into the tree canopy and collided with power transmission lines. Post accident examination of the engine revealed extensive thermal and impact related damage. The main bearings exhibited erosion and copper was visible. A large hole was observed in the engine crankcase above the number four cylinder bay and mechanical damage was observed to the area surrounding the cylinder. The number four connecting rod remained attached to the piston; however, the connecting rod was separated from the crankshaft at the base of the yoke. Fragments of the associated connecting rod cap and corresponding bolt were found within the engine oil sump; only residual oil (less than one quart) was observed within the sump along with debris, which was consistent with main bearing material and had obscured the oil pickup screen. Two fractures were found on the connecting rod near the end of the rod. The first noted was a fatigue fracture that initiated at the crankshaft end connecting rod journal surface just below the boss for the connecting rod bolt/nut. On the opposite side of the connecting rod, in a similar location, a second fracture was identified. The fracture was the result of mechanical overload and initiated at the connecting rod journal surface. The connecting rod bolt fracture surface exhibit features consistent with mechanical overload. The lack of engine oil found in the crankcase is believed to have contributed to the main bearing erosion; however, it was not determined if the bearing erosion was the initiating event.

Probable cause

A total loss of engine power during cruise flight due to the fatigue failure of the number 4 cylinder connecting rod.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09LA362
Event ID
20090722X33920
Case number
WPR09LA362
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, coordinates. 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: 4ac94a2f49bdd5dbd42225fe2ebbcabd3c9ff1e82bb27ec7b6f0e397575a5aaa; retrieved 2026-09-13T20:22:50.803Z.