CEN10CA296

NTSB accident investigation · Mooney M20M · Port Clinton, OH · June 4, 2010

Accident · Minor injuriesData collectionFinal report
Date
June 3, 2010, 20:00 local (Jun 4, 2010, 00:00 UTC)
Place
Port Clinton, OH
Injuries
1 minor, 1 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N1054BMooney M20M
Defining event
Takeoff: Collision during takeoff/land
Weather
Visual (VMC) · Dusk
Status
Completed · report December 20, 2010
Report
Approved by Office Director
NTSB office
Central Region
Parties
Federal Aviation Administration - Cleveland FSDO
FAA report
20100603034949A
Case key
76210

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot’s delayed decision to abort the landing and his failure to properly reconfigure the airplane during the aborted landing attempt.

Findings · 9

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Action: delayed actionPersonnel issues › Action/decision · PilotMooney M20M: 2 casesAll aircraft: 894 casesProbable cause
Use of equip/info: use of equip/systemPersonnel issues › Task performance · PilotMooney M20M: 2 casesAll aircraft: 1,391 casesProbable cause
Propeller system: propeller controlling systemAircraft › Aircraft propeller/rotor · Incorrect use/operationMooney M20M: 1 caseAll aircraft: 25 casesProbable cause
Engine fuel and control: fuel control/carburetorAircraft › Aircraft power plant · Incorrect use/operationMooney M20M: 1 caseAll aircraft: 195 casesProbable cause
Flight control system: tE flap control systemAircraft › Aircraft systems · Incorrect use/operationMooney M20M: 1 caseAll aircraft: 74 casesProbable cause
Landing gear system: gear extension and retract sysAircraft › Aircraft systems · Not used/operatedMooney M20M: 2 casesAll aircraft: 416 casesProbable cause
Wind: variable windEnvironmental issues › Conditions/weather/phenomena · Effect on operationMooney M20M: 1 caseAll aircraft: 113 cases
Wind: tailwindEnvironmental issues › Conditions/weather/phenomena · Awareness of conditionMooney M20M: 2 casesAll aircraft: 594 cases
Object/animal/substance: tree(s)Environmental issues › Physical environment · Contributed to outcomeMooney M20M: 1 caseAll aircraft: 933 cases

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot reported that when the flight was 15-20 miles south of the airport, the airport’s automated weather station broadcast indicated that the surface winds were light and out of the west. However, subsequent broadcasts indicated that the wind was from the north and then out of the south. The pilot canceled his instrument clearance before entering a left downwind for runway 18 (4,001 feet by 75 feet). He stated that after turning onto final approach he applied full landing flaps and deployed the speed brakes in order to bleed off some excessive airspeed. As the airplane passed over the 1,000 foot runway distance marker, he recognized that the airplane was landing downwind. The pilot stated that the airplane touched down after crossing midfield, after which he briefly applied brake pressure before deciding to abort the landing attempt. He kept the airplane on the runway as it accelerated, rotating and achieving liftoff toward the end of the runway. The airplane then impacted one of the 18-inch high runway end identifier lights located at the departure threshold. The pilot stated that after liftoff the engine did not appear to be producing maximum power and that there was a continual drop in airspeed. The pilot was unable to establish an adequate climb, so he made a left turn in an attempt to avoid some trees and an elevated roadway. The airplane continued to lose airspeed as it descended into a tree line located about 1,000 feet off the end of the runway. The pilot noted that the lack of engine power was likely the result of an improper propeller and/or mixture control setting during the aborted landing. The pilot also noted that he did not retract the wing flaps and landing gear during the aborted landing attempt. He further stated that his delayed decision to abort the landing contributed to the accident. A postaccident inspection did not reveal any preaccident anomalies that would have prevented the normal operation of the airplane or its engine. Local weather stations indicated that the prevailing wind was an onshore breeze from the north between 2 and 7 knots.

Factual narrative

The pilot reported that when the flight was 15-20 miles south of the airport, the airport’s automated weather station broadcast indicated that the surface winds were light and out of the west. However, subsequent broadcasts indicated that the wind was from the north and then out of the south. The pilot canceled his instrument clearance before entering a left downwind for runway 18 (4,001 feet by 75 feet). He stated that after turning onto final approach he applied full landing flaps and deployed the speed brakes in order to bleed off some excessive airspeed. As the airplane passed over the 1,000 foot runway distance marker, he recognized that the airplane was landing downwind. The pilot stated that the airplane touched down after crossing midfield, after which he briefly applied brake pressure before deciding to abort the landing attempt. He kept the airplane on the runway as it accelerated, rotating and achieving liftoff toward the end of the runway. The airplane then impacted one of the 18-inch high runway end identifier lights located at the departure threshold. The pilot stated that after liftoff, the engine did not appear to be producing maximum power and that there was a continual drop in airspeed. The pilot was unable to establish an adequate climb, so he made a left turn in an attempt to avoid some trees and an elevated roadway. The airplane continued to lose airspeed as it descended into a tree line located about 1,000 feet off the end of the runway. The pilot noted that the lack of engine power was likely the result of an improper propeller and/or mixture control setting during the aborted landing. The pilot also noted that he did not retract the wing flaps and landing gear during the aborted landing attempt. He further stated that his delayed decision to abort the landing contributed to the accident. A postaccident inspection did not reveal any anomalies that would have prevented the normal operation of the airplane or its engine. Local weather stations indicated that the prevailing wind was an onshore breeze from the north between 2 and 7 knots.

Aircraft

Registration
N1054B
Reported as
Mooney M20M
Category
Airplane
Serial number
27-0317
Airframe hours
780
Engine
Lycoming TIO-540-AF1B, 300 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Bonita Resources Inc.
Registered owner
Bonita Resources Inc.
Airworthiness certificate
Standard, Normal
Last inspection
Annual · June 3, 2009
Departed
KOSU · Columbus, OH
Destination
KPCW · Port Clinton, OH
Flight plan
IFR
Airport
KPCW · Carl R Keller Field Airport, runway 18, 4,001 × 75 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
60
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 3, With waivers/limitations
Last flight review
May 23, 2010
Seat
Left
Flight hours
2,189 total · 408 in this make and model · 2,100 as pilot in command · 28 in the last 90 days · 16 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Dusk
Wind
320° at 7 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
79 °F, dew point 61 °F
Altimeter
29.76 inHg
Observed at
KTDZ, 28 nm away

Docket · 4

The files NTSB released with the investigation on September 8, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports. 1.9 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.