FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MKC84FA195 · Piper PA-24-180

2 Jul 1984 · Osage Beach, MO, United States

Midwest Pilots Piper PA-24-180 · Accident: loss of engine power during initial climb

From Spirit of St Louis Airport (SUS) to an unrecorded destination

Report a problem

Event

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

Piper PA-24-180

Aircraft type
Piper PA-24
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
N5019P
Onboard fatalities
Unknown
Route
From Spirit of St Louis Airport (SUS), ST.LOUIS, MOTo not recorded
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
Initial climb
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
Loss of engine power
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Utility pole; Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Engine assembly › Undetermined
  • Pilot in command › Aborted landing, delayed
  • Pilot in command › Judgment, poor

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

NTSB narrative

WITNESS STATED ACFT TOUCHED DOWN MIDFIELD AND BOUNCED SEVERAL TIMES ON THE RWY. TWO WITNESSES HEARD POWER APPLIED AND THE ACFT LIFTED OFF 300 FT FROM THE END OF THE RWY. THEY STATED FLAPS WERE FULLY EXTENDED FOR THE TOTAL TRANSITION AND THE GEAR WAS RETRACTED ONLY AFTER THE FIRST SET OF POWER LINES. AT APRX 100 FT AGL THE ACFT BEGAN TO DESCEND AT WHICH TIME IT CONTACTED A UTILITY POLE FOLLOWED BY TREES. THE PLT STATED THE ENGINE DID NOT SEEM TO BE PRODUCING FULL POWER DURING THE CLIMB. HOWEVER, POST ACCIDENT INVESTIGATION OF THE ENGINE REVEALED NO MECHANICAL MALFUNCTIONS. THE PLT STATED THE LONG LANDING WAS MADE BECAUSE OF TURBULENCE ENCOUNTERED OVER THE TREES DURING THE APPROACH.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record MKC84FA195
Event ID
20001214X40406
Case number
MKC84FA195
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: 7127a68a54324d3eedcb090ec1d9c06026f12c9100c362ffed7288ff17330e99; retrieved 2026-09-21T17:33:19.953Z.