FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW02LA096 · Mooney M20A

16 Mar 2002 · Norman, OK, United States

Mooney M20A · Accident: loss of engine power during initial climb

From University of Oklahoma Westheimer Airport (OUN) to Newton City-County Airport (EWK)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
FTW02LA096
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 M20A Possible conflict

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
N8390E
Operator
Unknown
Onboard fatalities
Unknown
Route
From University of Oklahoma Westheimer Airport (OUN), Norman, OKTo Newton City-County Airport (EWK), Newton, KS
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
Initial climb
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
Loss of engine power
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

  • Mixture control, cable › Loose part/bolt/nut/clamp/etc
  • Other maintenance personnel › Maintenance, installation, improper

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

NTSB narrative

During takeoff initial climb, approximately 800-900 feet agl, the engine lost power. With no options to land straight ahead, the pilot elected to make a right 180-degree turn back to the runway. The airplane's right wing struck the ground followed by the fuselage. The airplane slid upright into two parked airplanes that were tied down on the ramp. Examination of the aircraft revealed an improper clamp installed on the mixture cable that would not allow the mixture cable to extend to the full rich position.

Probable cause

Maintenance personnel's improper clamp installation on the mixture control cable, which resulted in a loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW02LA096
Event ID
20020319X00363
Case number
FTW02LA096
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: d48aa19dc4f0c0ce5d3479c0ee11606c4f3c0befc9a12c9a855c1188de2afbc8; retrieved 2026-09-21T19:45:49.683Z.