FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12FA487 · Mooney Airplane COMPANY, INC. M20TN

27 Jul 2012 · Adrian, MI, United States

4th Wave Mooney Airplane COMPANY, INC. M20TN · Accident: inflight upset en route

From Wittman Regional Airport (OSH) to Washington Manassas Harry P. Davis Field (HEF)

Report a problem

Event

NTSB case
CEN12FA487
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 Airplane COMPANY, INC. M20TN

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
N411JL
Operator
4TH Wave
Onboard fatalities
Unknown
Route
From Wittman Regional Airport (OSH), Oshkosh, WITo Washington Manassas Harry P. Davis Field (HEF), Manassas, VA
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 · climb to cruise
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
Inflight upset
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
  • Not determined › Not determined
  • Personnel issues › Action/decision

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 reported that the airplane, with its autopilot engaged, experienced a "violent pitch-up" without warning while it was climbing through about flight level 180. Extreme forward yoke pressure (the pilot estimated between 100 and 150 pounds force) was required to keep the airplane from pitching up and stalling, so the pilot kept both hands on the yoke.

The Airplane Flight Manual contains emergency procedures for use in the event of an autopilot out-of-trim event; the third item on the checklist directs pilots to re-trim the pitch, if necessary, using the trim wheel. The pilot noted that he did not attempt to use the manual trim wheel to change the airplane's pitch attitude because that would have required him to release hand pressure on the control yoke. He was uncertain when or how the autopilot was disengaged. He declared an emergency and made a spiraling descent to lose altitude. He reported that he encountered multiple violent pitch up and down oscillations near the bottom of the descent; the pilot's seat was broken during one of the oscillations, which allowed the pilot to use his knees to apply forward yoke pressure. He stated that by using his knees to control the yoke, the airplane was "quasi-stable," pitch oscillations still occurred due to the lack of precise pitch control. While still having difficulty controlling the airplane's pitch with the electric nose pitch trim in the full up position, he prepared for an emergency landing. The pilot used his knees to provide forward yoke pressure as he landed the airplane about 450 feet short of the runway. The airplane's nose gear collapsed, the main landing gear were sheared off, and the airplane skidded about 900 feet before coming to rest to the left of the runway. The duration of the flight from the initial pitch up event to landing was about 27 minutes. Three separate examinations of the airplane's flight controls and autopilot system found no anomalies with the autopilot system or an explanation for the violent nose-pitch-up event. The Emergency Section of the Airplane Flight Manual (AFM) supplement for the autopilot stated that for an Autopilot Out of Trim emergency the pilot should: 1) disengage the autopilot 2) maintain/regain aircraft control, and 3) pitch trim...re-trim if necessary using the trim wheel.

Probable cause

An initial nose-pitch-up event and out-of-trim condition, the reason for which could not be determined because the examinations of the airplane did not reveal any anomalies that would have precluded normal operation. Contributing to the accident was the pilot’s failure to use the manual trim wheel to reset the pitch trim.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12FA487
Event ID
20120727X45750
Case number
CEN12FA487
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: 54a1a033023ab5d4d74fd65bdbcfaae3a8ed6aa9420af70247952ae17b89b7f4; retrieved 2026-09-15T19:06:35.643Z.