CEN17LA184 · Mooney M20E
Mooney M20E · Accident: flight instrument malfunction/failure during landing
From Battle Creek Executive Airport at Kellogg Field (BTL) to Dowling, MI
Event
- NTSB case
- CEN17LA184
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Mooney M20E
- Aircraft type
- Mooney M20
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N9265M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Battle Creek Executive Airport at Kellogg Field (BTL), Battle Creek, MITo Dowling, MI
- Aircraft age
- About 51 years (built 1966)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Flight instrument malfunction/failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft systems
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17LA184
- Event ID
- 20170515X72152
- Case number
- CEN17LA184
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: f1808e2923118ce1e349527259f789c8faaca9c703dae0628bd7506c736b543c; retrieved 2026-09-16T05:17:10.606Z.