FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10LA465 · Mooney M20C

21 Sept 2010 · Visalia, CA, United States

Mooney M20C · Accident: loss of engine power (partial) during takeoff

From Visalia Municipal Airport (VIS) to Visalia Municipal Airport (VIS)

Report a problem

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

Event

NTSB case
WPR10LA465
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 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
N6090Q
Operator
Unknown
Onboard fatalities
Unknown
Route Narrative disagrees
From Visalia Municipal Airport (VIS), Visalia Municipal, CATo Visalia Municipal Airport (VIS), Visalia Municipal, CA
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
Takeoff
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 (partial)
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 applied full engine power, took off, and climbed to about 300 feet above the runway. The engine suddenly lost partial power, and the pilot elected to return to the airport for a forced landing. The airplane’s altitude was insufficient to complete the turn, and the airplane impacted the ground adjacent to the departure runway, substantially damaging the right wing. An examination of the engine revealed that the retention mechanism for the bottom No. 3 spark plug failed and the spark plug had blown out of its cylinder. Its failure appeared related to excessive wear and the loosening over time of the Heli-Coil insert. According to the Federal Aviation Administration, evidence of the Heli-Coil’s loosening would not, necessarily, have been apparent to a mechanic during routine maintenance.

Probable cause

A partial loss of engine power during takeoff, which resulted from the failure of the spark plug retention mechanism.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10LA465
Event ID
20100921X52702
Case number
WPR10LA465
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: 9cce04ddb9eda590602547166c182c7b4b067b538fa2d478140f365d9c488e16; retrieved 2026-09-15T15:18:27.988Z.