N9265M accident

NTSB CEN17LA184 · 2017-05-15 · Dowling, MI

Docket — crew, injuries and powerplant

Summary

The private pilot stated that, during the flight, the airspeed indicator displayed a lower than normal airspeed. The pilot landed the airplane at an intermediate airport to drop off a passenger, then continued to his home airport, a privately-owned, 2,000-ft-long turf runway. During the first attempted landing, the airplane would not "settle," and the pilot initiated a go-around. During the second landing, the airplane floated again, consistent with a higher-than-indicated airspeed, and the pilot "forced" the airplane onto the runway. The airplane porpoised and continued off the runway, hitting trees, a fence, and a pole, resulting in substantial damage. During postaccident examination, the remains of an insect were found in the pitot tube. A functional test of the airspeed indicator revealed no anomalies. It is likely that the inaccurate airspeed indications were due to the contamination of the pitot static system, which subsequently resulted in a high approach and landing speed and subsequent runway overrun.

Full narrative

On May 15, 2017, about 1330 eastern daylight time, a Mooney M20E airplane, N9265M, was substantially damaged when it impacted trees, a fence, and a pole, while landing at a private grass airstrip near Dowling, Michigan. The private pilot was not injured. The personal flight was conducted under the provisions of 14 Code of Federal Regulations Part 91 without a flight plan. Visual meteorological conditions prevailed for the flight that departed W K Kellogg Airport (BTL), Battle Creek, Michigan, and was en route to the private airstrip.According to the pilot, during the flight the airspeed indicator did not indicate as high as it normally would. He landed uneventfully at BTL to drop off a passenger and then continued to the private airstrip (2,000 feet by 120 feet, grass) for a full-stop landing. While on final approach, the pilot decreased airspeed to 70 miles per hour (mph); however, the airplane would not settle so he initiated a go around. During the second attempt to land, the pilot decreased airspeed to 60 mph, but the airplane still would not land. The pilot stated that he "forced" the airplane to land.

During touchdown the airplane porpoised and continued off of the runway hitting trees, a fence, and a pole. According to the Federal Aviation Administration inspectors who responded to the accident, the left main landing gear and nose gear collapsed. The right wing sustained substantial impact damage to the leading edge and the spar. The pitot tube separated from the airplane and could not be functionally tested.

During the examination of the pitot static system debris was recovered from the pitot tube that appeared organic in nature, consistent with the remains of an insect. A functional test of the airspeed indicator revealed no anomalies that would have precluded normal operation.

Probable cause

Innacurate airspeed indications due to contamination of the pitot-static system with insect remains, which resulted in a high approach and landing speed and subsequent runway overrun. The National Transportation Safety Board determined the probable cause of this accident.

Circumstances

Event type
Accident
Highest injury
None
Weather conditions
Visual Meteorological Cond
Light condition
Day
Sky condition
NONE
Ceiling (ft)
0
Visibility (sm)
10
Wind direction
160
Wind speed (kt)
5
Temperature (F)
70
Nearest airport
Private
Distance from field
0.0
Airport elevation
930

Aircraft

RegistrationMakeModelDamageFAR part
N9265M — — SUBS 091

Sequence of events

#OccurrencePhase
1 Landing-flare/touchdown Flight instrument malf/fail defining Cruise
2 Landing-landing roll Collision with terr/obj (non-CFIT) Cruise

Findings

Finding
Aircraft-Aircraft systems-Navigation system-Pitot/static system-Related operating info cause
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Airspeed-Related operating info cause