FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12LA422 · Mooney M20J

28 Jun 2012 · Mc Kinnon, TN, United States

Mooney M20J · Accident: loss of engine power (total) on approach

From M33 · Gallatin, TN to Houston County Airport (M93)

Report a problem

Event

NTSB case
ERA12LA422
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
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 M20J

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
N174JB
Operator
Unknown
Onboard fatalities
Unknown
Route
From M33 · Gallatin, TNTo Houston County Airport (M93), Mc Kinnon, TN
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 · VFR pattern downwind
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
  • Personnel issues › Task performance

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

NTSB narrative

The pilot was conducting a formation flight when the airplane’s engine experienced a loss of power. The pilot and his instructor then conducted a forced landing to a runway and landed long, with the airplane departing the surface and coming to rest in a field. Post accident examination revealed that the number three piston connecting rod cap separated from the piston connecting rod when the hardware came loose and the connecting rod disconnected during flight. Maintenance records showed that the engine had been overhauled several years prior to the accident. It is likely that the mechanic did not properly install the connecting rod bolts and nuts, which resulted in the number three piston connecting rod disconnecting during flight, and subsequent loss of engine power.

Probable cause

The separation of the piston connecting rod from the crankshaft due to inadequate installation from a mechanic, resulting in a total loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12LA422
Event ID
20120629X90208
Case number
ERA12LA422
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. 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: af1dd5ea2ac91af409e3780a0917361c0cb9a347a085bf8dc265dbe9f57803d7; retrieved 2026-09-15T18:40:15.831Z.