FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MKC87LA058 · Cessna 175

7 Mar 1987 · Tipton, MO, United States

Cessna 175 · Accident: total loss of engine power (mechanical failure) en route

From H21 · Camdenton, MO to M010 · Liberty, MO

Report a problem

Event

NTSB case
MKC87LA058
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

Cessna 175

Aircraft type
Cessna 175
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
N7135M
Operator
Unknown
Onboard fatalities
Unknown
Route
From H21 · Camdenton, MOTo M010 · Liberty, MO
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
Total 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 › Overtemperature
  • Engine assembly, push rod › Brittle fracture
  • Fluid, oil › Starvation

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PILOT STATED THAT, FIFTEEN MINUTES INTO THE FLIGHT, WHILE AT CRUISE THE ENGINE OIL PRESSURE BEGAN DROPPING AS THE OIL TEMPERATURE ROSE. WHILE ATTEMPTING TO REACH SEDALIA, MISSOURI TO PERFORM A PRECAUTIONARY LANDING, OIL BEGAN COVERING THE AIRCRAFT'S WINDSHIELD AND, SHORTLY THEREAFTER THE ENGINE EXPERIENCED A TOTAL LOSS OF POWER, ACCORDING TO THE PILOT. THE AIRCRAFT WAS FORCED TO LAND ON A MUDDY CORNFIELD WHERE THE MAIN LANDING GEAR DUG IN UPON TOUCHDOWN CAUSING THE AIRCRAFT TO NOSE OVER. A POST-ACCIDENT ENGINE TEARDOWN INSPECTION BY THE OPERATOR REVEALED THAT THE #2 ENGINE CYLINDER PUSHROD HAD FRACTURED AND HAD EXITED THROUGH THE ENGINE BLOCK.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MKC87LA058
Event ID
20001213X30525
Case number
MKC87LA058
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: fa4c907c81cf460dd3bab6173da6ff9210f0af818d80e58fe70ef764961ca272; retrieved 2026-09-22T01:04:04.840Z.