Accident Mooney M20F Executive 21 N9722M,
ASN logo
ASN Wikibase Occurrence # 145155
 
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:Thursday 19 April 2012
Time:11:30
Type:Silhouette image of generic M20P model; specific model in this crash may look slightly different    
Mooney M20F Executive 21
Owner/operator:Private
Registration: N9722M
MSN: 670199
Year of manufacture:1966
Total airframe hrs:4517 hours
Engine model:Lycoming IO-360 SER
Fatalities:Fatalities: 0 / Occupants: 3
Aircraft damage: Substantial
Category:Accident
Location:West of Houston County Airport - M93, McKinnon, TN -   United States of America
Phase: Initial climb
Nature:Private
Departure airport:Waverly, TN (0M5)
Destination airport:McKinnon, TN (M93)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The airplane was on approach to runway 8, a 3,000-foot-long runway. The airplane was high and fast, and the pilot attempted to perform a go-around; however, the airplane was not able to climb before impacting trees, located about 700 feet beyond the end of the runway. Examination of the airframe and engine did not reveal any mechanical malfunctions that would have precluded normal operation nor did the pilot report any. The airplane was found after the accident with the landing gear extended and the wing flaps in the full down position. Witnesses reported that the wind was from the west at 10 to 15 knots, at the time of the accident. In addition, the pilot reported that the wind had shifted from east to west and that he did not note the position of the airport wind sock prior to landing. He also stated that the 3,000 foot-long runway was the shortest runway he had attempted to land on. Had the pilot retracted the landing gear and the flaps during the attempted go-around, he should have been able to execute a successful go-around.
Probable Cause: The pilot's delayed decision to go-around after failing to recognize that he was attempting to land with a tailwind, and his failure to retract the landing gear and wing flaps for the go-around, which resulted in a collision with trees and terrain near the departure end of the runway.

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

Sources:

NTSB

Location

Revision history:

Date/timeContributorUpdates
19-Apr-2012 12:12 gerard57 Added
19-Apr-2012 13:48 Geno Updated [Time, Aircraft type, Registration, Cn, Location, Destination airport, Source, Narrative]
19-Apr-2012 13:55 Anon. Updated [Aircraft type, Registration, Cn, Location, Destination airport, Source, Narrative]
20-Apr-2012 08:28 RobertMB Updated [Time, Aircraft type, Registration, Cn, Location, Phase, Source, Narrative]
25-May-2012 22:34 Geno Updated [Time, Location, Phase, Source, Narrative]
13-Aug-2012 13:20 harro Updated [Source]
21-Dec-2016 19:28 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
27-Nov-2017 20:36 ASN Update Bot Updated [Cn, Other fatalities, 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