WPR16FA095 · Mooney Aircraft CORP. M20K
Mooney Aircraft CORP. M20K · Accident during takeoff
From Woodland State Airport (W27) to Renton Municipal Airport (RNT)
Event
- NTSB case
- WPR16FA095
- 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
- 1 · 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 Aircraft CORP. M20K
- 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
- N97119
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Woodland State Airport (W27), Woodland, WATo Renton Municipal Airport (RNT), Renton, WA
- Aircraft age
- About 35 years (built 1981)
- 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
- Miscellaneous/other
- 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 oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The pilot and two passengers boarded the airplane for a personal cross-country flight. After a normal engine run-up, the pilot began the takeoff roll on the 1,953-ft-long runway. According to the pilot, the airplane lifted off after a ground roll of about 1,250 ft, climbed to about 35 ft above ground level, but then stopped accelerating. The pilot then lowered the nose and discovered that the airplane was just above the ground and seconds from impacting a berm. However, video of the takeoff showed that the airplane became airborne after a ground roll of about 1,933-ft, about 20 ft from the end of the runway. Further, according to the witness who took the video, the airplane attained a maximum altitude of only about 4 ft before it touched down in the grass beyond the runway end. The airplane impacted the airport's perimeter fence located about 375 ft from the end of the runway and then collided with the 9-ft-tall berm.
A sound spectrum analysis of the video's audio channel showed that the propeller rpm was about 2,430 during takeoff, which was about 270 rpm below the expected maximum rpm of 2,700. Examination of the propeller governor showed that the unit was set to a maximum rpm of about 2,600, which was about 100 rpm below the manufacturer's specified setting. In addition, during engine test cell runs with a fixed-pitch club propeller, the maximum engine rpm was increased 100 rpm, from 2,640 to 2,740, by retiming the magnetos from an improper setting to the manufacturer's specified setting. Regardless, the propeller governor would have inhibited the engine from reaching rated power, thus it is likely that the propeller governor resulted in a takeoff rpm below maximum rpm.
The pilot reported that before departure, he calculated that the airplane's gross weight was about 2,864 pounds (lbs) and the takeoff ground roll would be about 1,250 ft. Postaccident calculations revealed that the airplane's gross weight was about 2,978 lbs, which exceeded the airplane's maximum gross weight by 78 lbs. The airplane's zero-wind ground roll at its maximum gross weight of 2,900 lbs was about 1,350 ft, and may have been longer due to the higher gross weight. Although the pilot's calculations indicated a safe takeoff was possible, the airplane did not perform as expected, likely due to the engine not achieving maximum rpm and the pilot's exceedance of the airplane's maximum gross weight. The pilot should have been sensitive to the short runway length and closely monitored the airplane's performance. If the pilot had recognized promptly that the airplane was not performing as expected, given the distance from the runway end to the fence and the berm that the airplane impacted, adequate distance would likely have been available to safely abort the takeoff. Additionally, if the pilot had designated a go/no-go runway liftoff point, this would have helped him detect the performance deficiency. However, the pilot did not recognize that the airplane was not performing as expected until the airplane was near the runway end and the impact with the berm could not be avoided.
The pilot seated in the left front seat and the passenger seated in the right front seat were restrained with lap and shoulder belts and survived with compression fractures of the lumbar spine and extremity injuries, demonstrating that this accident was survivable for occupants who were properly restrained. The compression fractures sustained by the front seat occupants are typically caused by vertical loading from below while in a seated position; in this case, likely from the airplane striking the berm in a nose-high attitude.
The passenger seated in the left rear seat was likely restrained only by a lap belt and sustained fatal injuries to his brain and spinal cord. It could not be determined if the rear seat passenger's cervical spine injuries were primarily from hyperflexion or hyperextension. The head rests had been removed from all seats in the airplane, and the rear passenger received a significant posterior scalp laceration that was consistent with hyperextension of his neck over the low back of his seat. This hyperextension could have been prevented by the presence of a head rest at an appropriate height on his seat but would not have been prevented by his use of the available shoulder harness. The rear passenger's cervical spine injuries may also have been caused by hyperflexion of his neck over the pilot's seat back and could have been prevented by his use of the available shoulder harness and/or the presence of a head rest on the pilot's seat. Thus, it is likely that the appropriate use of head rests and shoulder restraints would have mitigated the severity of the rear seat passenger's injuries.
Probable cause
The pilot's delay in recognizing that the airplane was not performing as expected and aborting the takeoff, which resulted in collision with a berm beyond the end of the runway. Contributing to the accident were the pilot's exceedance of the airplane's gross weight and the underperformance of the engine due to governor setting and magneto timing deficiencies. Contributing to the severity of the rear passenger's injuries was his decision to forego use of his shoulder harness and/or the absence of head rests.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR16FA095
- Event ID
- 20160421X94028
- Case number
- WPR16FA095
- 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. 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: dc5f6c5e3e51379cfe393e10c1252095158bee93da4d705dffdedc0c89e8b51c; retrieved 2026-09-14T21:44:51.088Z.