MKC83LA211 · Mooney M20C
Mooney M20C · Accident: partial loss of engine power (mechanical failure) en route
From Davenport Municipal Airport (DVN) to Augusta Municipal Airport (3AU)
Event
- NTSB case
- MKC83LA211
- 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
- 0
- 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 M20C
- 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
- N4057N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Davenport Municipal Airport (DVN), Davenport, IATo Augusta Municipal Airport (3AU), AGUSTA, KS
- Aircraft age
- Not recorded
- 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
- En route · cruise
- First occurrenceThe 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
- Partial loss of engine power (mechanical 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
- Engine assembly, other › Failure, total
- Engine assembly, push rod › Bent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE EN ROUTE, THE PLT ENCOUNTERED A PROGRESSIVE, PARTIAL POWER LOSS. AT 1ST THE ENG BEGAN RUNNING ROUGH, THEN THE MANIFOLD PRESSURE DROPPED TO 15 INCHES (18 INCHES HAD BEEN SET FOR CRUISE). HE HEARD A CLICKING NOISE & STARTED A DESCENT FROM HIS CRUISE ALT OF 8500 FT. HE BEGAN A PRECAUTIONARY LANDING. WHEN HE SAW THAT THE WIND WOULD CARRY THE ACFT BEYOND THE FIELD HE HAD SELECTED, HE USED WHAT AVAILABLE POWER HE HAD TO CROSS OVER A ROAD & A POND, AND TO AVOID A TRANSMISSION LINE. HOWEVER, HE WAS UNABLE TO AVOID A FENCE. THE PLT STATED THAT THE ACFT TORE THRU A FENCE, JUST BEFORE TOUCHDOWN. AN INVESTIGATION REVEALED THAT THE #4 EXHAUST PUSHROD WAS BENT & THE HOUSING WAS BROKEN.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MKC83LA211
- Event ID
- 20001214X44645
- Case number
- MKC83LA211
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 7f3893139f94b4bcc13bacf490c5c931626b4599fd7e0bae35ed8b6720271c5a; retrieved 2026-09-23T21:25:43.047Z.