Accident Mooney M20E N5608Q,
ASN logo
ASN Wikibase Occurrence # 177573
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Saturday 4 July 2015
Time:08:10
Type:Silhouette image of generic M20P model; specific model in this crash may look slightly different    
Mooney M20E
Owner/operator:Private
Registration: N5608Q
MSN: 660
Year of manufacture:1965
Total airframe hrs:2799 hours
Engine model:Lycoming IO-360-A1A
Fatalities:Fatalities: 1 / Occupants: 1
Aircraft damage: Substantial
Category:Accident
Location:McNary Field Airport (KSLE), Salem, OR -   United States of America
Phase: Landing
Nature:Private
Departure airport:Salem, OR (SLE)
Destination airport:Salem, OR (SLE)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
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.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: WPR15FA208
Status: Investigation completed
Duration:
Download report: Final report

Sources:

NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=5608Q

Location

Revision history:

Date/timeContributorUpdates
04-Jul-2015 19:27 Geno Added
04-Jul-2015 21:11 ez4unm Updated [Total fatalities, Phase]
06-Jul-2015 04:15 ez4unm Updated [Source, Narrative]
06-Jul-2015 15:51 Geno Updated [Registration, Cn, Operator, Phase, Source, Damage, Narrative]
16-Jul-2015 03:02 Geno Updated [Time, Nature, Departure airport, Source]
21-Dec-2016 19:30 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
01-Dec-2017 15:03 ASN Update Bot Updated [Departure airport, Destination airport, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org