FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR21LA249 · Mooney M20F

27 Jun 2021 · Marion, MT, United States

Mooney M20F · Accident: collision during takeoff/landing during initial climb

From an unrecorded airport to Kalispell City Airport (S27)

Report a problem

Event

NTSB case
WPR21LA249
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
Event fatalities
Unknown
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 M20F

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
N9613M
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Kalispell City Airport (S27), Kalispell, MT
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
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
Collision during takeoff/landing
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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 › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The pilot was departing at the time of the accident. At the beginning of the short field takeoff, he held the brakes as he advanced the throttle to 2,650 rpm. He then released the brakes and began the takeoff roll. The airplane was about 1,600 ft down the runway when the pilot attempted to rotate, but the airplane did not accelerate as the pilot had anticipated after he rotated about midfield. A witness observed the airplane in a nose-high attitude about this time. As it was too late to abort the takeoff, he turned left to avoid a tree-lined hill at the end of the runway and obstacles to the right of the runway. He also engaged the power boost (turbocharger) at this time, which yielded little improvement in the airplane’s performance. The airplane was unable to gain sufficient altitude to clear trees so the pilot leveled the wings prior to the impact. According to the pilot, the airplane had been underpowered during previous takeoffs and exhibited sudden slight drops in rpm; however, postaccident examination of the engine did not reveal any anomalies that could have precluded normal operation. The pilot stated that the engine appeared to function normally on the day of the accident but suggested that the propeller governor may have contributed to a performance deficiency as it had not been serviced for the past 30 years (or since the last major engine overhaul 30 years ago). A functional test and disassembly of the governor revealed low performance output and excessive leakage due to pitting of the pilot valve. However, the loss in pressure output is not likely to have affected the propeller’s pitch attitude during the takeoff attempt. Performance computations were consistent with the pilot’s and demonstrated that a successful rotation and transition into a climb for a midfield takeoff was attainable. A witness observed the airplane in a nose-high attitude after rotation. While the airspeed at which the pilot rotated is unknown, the airplane’s nose-high attitude suggests the airplane was not accelerating, thus inhibiting its transition out of ground effect. The investigation also found that the pilot did not properly engage the power boost (turbocharger) at the beginning of the takeoff as required by the flight manual. As the power boost is recommended at high elevation airports, like the pilot’s departure airport, the additional manifold pressure and engine power is likely to have increased the engine’s overall performance. The evidence suggests that the accident was due to the pilot’s improper rotation during takeoff, which resulted in a runway overrun and an impact with terrain. Contributing to the accident was the pilot’s improper management of the turbocharger during a takeoff from a high-altitude airport, which reduced the engine’s maximum performance during the ground run. The airplane also had sufficient distance to stop had the pilot selected an earlier point to abort the takeoff.

Probable cause

The pilot’s improper rotation during takeoff from a high-altitude airport and his failure to abort the takeoff, which resulted in an impact with trees and terrain. Contributing to the accident was the pilot’s improper management of the turbocharger, which reduced the engine’s maximum performance during the ground run.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR21LA249
Event ID
20210628103359
Case number
WPR21LA249
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, cause areas. 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: e6a6e3db7ad849ef1f014e2ffa5fda332bbfc5e16db5c59c37c918dc785514ef; retrieved 2026-09-16T14:13:36.705Z.