WPR15FA208 · Mooney M20E
Mooney M20E · Accident: abnormal runway contact during landing
From Salem-Willamette Valley Airport/McNary Field (SLE) to Salem-Willamette Valley Airport/McNary Field (SLE)
Event
- NTSB case
- WPR15FA208
- 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
- 0
- 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 M20E
- 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
- N5608Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Salem-Willamette Valley Airport/McNary Field (SLE), Salem, ORTo Salem-Willamette Valley Airport/McNary Field (SLE), Salem, OR
- Aircraft age
- About 50 years (built 1965)
- 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
- Landing · flare/touchdown
- 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
- Abnormal runway contact
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The private pilot was attempting to land the airplane after conducting a local flight. A witness reported that he observed the airplane approach from the south for landing and that the approach looked normal. He added that the engine power sounded normal with the throttle being reduced as the airplane glided down to the runway. The airplane touched down, and shortly thereafter, the tail dipped down toward the runway, and the nose pitched up. The airplane then began a series of "ballooning oscillations," and each time the nose pitched up, the ballooning became more severe. During the third oscillation, the airplane descended nose first, impacted the runway, and then appeared to be launched about 6 to 8 ft into the air. The witness reported that the engine sound increased but that it sounded as if it were running at low rpm. The witness added that the pilot appeared to regain control of the airplane and that it remained airborne about 10 to 12 ft above runway. Another witness reported that it remained airborne for a distance of about 1,000 ft, entered a shallow climb at a low airspeed, and then reached an altitude of about 100 ft. Another witness reported that, shortly thereafter, he observed the airplane make a gradual left turn, which was followed by an increasing left bank, before it stalled and impacted terrain. A postcrash fire consumed the wreckage. A postaccident examination of the airplane and engine revealed no anomalies that would have precluded normal operation.
Based on the witnesses' statements, it is likely that the approach was shallow or that the pilot was not managing airspeed control, which resulted in the airplane porpoising down the runway. It is also likely that the pilot realized too late that the airplane was not in the proper attitude and applied excessive back-elevator pressure, which exacerbated the bounces; the third porpoise likely resulted in the propeller striking the runway; however, it is unknown whether the damage to the propeller would have affected the ability of the airplane to climb and maintain airspeed. When the pilot eventually applied power to execute the aborted landing, the airspeed was likely close to stall speed. His subsequent initiation of the turn at a low altitude resulted in the airplane exceeding its critical angle-of-attack and a subsequent stall with insufficient altitude from which to recover.
Probable cause
The pilot's unstabilized approach and delayed remedial action, which resulted in a porpoise during landing. Also causal to the accident was the pilot’s exceedance of the airplane's critical angle-of-attack during the subsequent aborted landing, which resulted in a low altitude stall/spin.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR15FA208
- Event ID
- 20150704X24851
- Case number
- WPR15FA208
- 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: 545edbce4994345509183a27fbf6f9bd581eab3623907f0def58f3875bfb6d70; retrieved 2026-09-14T19:45:39.234Z.