Mooney M20E accident near Salem, Oregon, July 4, 2015
On July 4, 2015 at about 3:10 pm local time, a 1965 Mooney M20E, registered N5608Q, was substantially damaged in an accident during landing (flare/touchdown) near Salem, Oregon (Mcnary Field). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 4, 2015 · about 3:10 pm local time
- Place
- Salem, Oregon · Mcnary Field · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Mooney M20E, built 1965 · all M20Es on the register
- Registration
- N5608Q · no longer on the register · serial 660
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Abnormal runway contact during landing (flare/touchdown) defining event
- Attempted remediation/recovery during landing (aborted after touchdown)
- Aerodynamic stall/spin during approach (VFR go-around)
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Not attained/maintained
- cause Personnel issues › Action/decision › Action › Delayed action › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Not attained/maintained
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 500 hours in all; 500 in this make and model
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 2,799.1 hours
- Last inspection: annual inspection, June 4, 2015; 114 hours since
- Maximum gross weight: 2,575 lb
- Seats: 4
- Landing gear: retractable
- Engine: Lycoming IO-360-A1A (piston); 114 hours total
- Fire on the ground
The flight
- Departed from: SLE Salem OR at 2:00 pm
- Destination: SLE Salem OR
- Flight plan: none
- Runway 34, 5,145 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 300° at 3 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 68°F (20°C), dew point 50°F (10°C)
- Altimeter: 29.87 inHg
- Observation at 2:56 pm from SLE, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
12 documents, released by the NTSB on July 7, 2016. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Witness Statements | PDF, 3 pages | View Download |
| 2 | Accident Site Mite | PDF, 1 page | View Download |
| 3 | Weather Data | PDF, 1 page | View Download |
| 4 | Records of Conversation | PDF, 6 pages | View Download |
| 5 | Mooney Pilot Operating Handbook Information | PDF, 3 pages | View Download |
| 6 | Excerpts from Maintenance Records | PDF, 8 pages | View Download |
| 7 | Summary of Airframe and Engine Examinations | PDF, 5 pages | View Download |
| 8 | Salem Police Department Report | PDF, 23 pages | View Download |
| 9 | Statement of Party Representatives to NTSB Investigation | PDF, 2 pages | View Download |
| 10 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
| 11 | Toxicological Report | PDF, 1 page | View Download |
| 12 | Photo Array of Accident Site | PDF, 4 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
