FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI94LA328 · Mooney M20E

14 Sept 1994 · Plymouth, MI, United States

Mooney M20E · Accident: total loss of engine power (mechanical failure) en route

From Coleman A. Young Municipal Airport (DET) to Canton-Plymouth-Mettetal Airport (1D2)

Report a problem

Event

NTSB case
CHI94LA328
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 M20E

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
N6944U
Operator
Unknown
Onboard fatalities
Unknown
Route
From Coleman A. Young Municipal Airport (DET), Detroit, MITo Canton-Plymouth-Mettetal Airport (1D2), Canton, MI
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

  • Pilot in command › Maintenance, modification, improper
  • Pilot in command › Operation with known deficiencies in equipment, initiated

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

NTSB narrative

THE PILOT STATED THAT HE NOTED THAT THE AIRPLANE HAD DEVELOPED AN OIL LEAK IN THE OIL COOLER. HE ISOLATED THE LEAK BY CAPPING THE OIL LINES FROM THE ENGINE TO THE COOLER AND INITIATED A FLIGHT. HE REPORTED THAT AFTER ABOUT TEN MINUTES OF FLIGHT THE OIL PRESSURE DROPPED TO ZERO AND HE WAS ATTEMPTING A FORCED LANDING WHEN THE ENGINE BEGAN RUNNING ROUGH AND SHORTLY THEREAFTER SUFFERED A TOTAL LOSS OF POWER.

Probable cause

the pilot's improper (maintenance) modification and his initiating an operation with known deficiencies in equipment

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI94LA328
Event ID
20001206X02213
Case number
CHI94LA328
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: 13abfc9814a3d3cdd240dbfcf91d4b562eb02ed1e1133e3175b4071c3e96fe0a; retrieved 2026-09-23T00:39:24.273Z.