FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI84FA369 · Piper PA-28RT-201 PA-28RT-20

29 Aug 1984 · Muncie, IN, United States

Munci Aviation Piper PA-28RT-201 PA-28RT-20 · Accident: loss of engine power during initial climb

From Delaware County Johnson Field (MIE) to Dayton-Wright Brothers Airport (MGY)

Report a problem

Event

NTSB case
CHI84FA369
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
3 · 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-28RT-201 PA-28RT-20

Aircraft type
Piper PA-28
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
N4355N
Onboard fatalities
Unknown
Route
From Delaware County Johnson Field (MIE)To Dayton-Wright Brothers Airport (MGY), Dayton, OH
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
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

  • Reason for occurrence undetermined

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

NTSB narrative

WITNESSES REPORTED THAT WHEN THE ACFT WAS TAKING OFF, THE ENG SOUNDED 'ROUGH & WAS BACKFIRING.' THEY OBSERVED THE ACFT CROSS THE DEPARTURE END OF THE RWY AT A LOWER ALT & SLOWER SPEED THAN WHAT THEY CONSIDERED AS NORMAL. THEY SAW THE ACFT'S WINGS ROCK, THEN OBSERVED THE ACFT TO ENTER A STEEP LEFT TURN BACK TOWARD THE ARPT. WHILE TURNING, THE GEAR EXTENDED AS THE ACFT WAS APPROACHING TO CROSS OVER A TREELINE. SHORTLY AFTER THAT, THE LEFT WING HIT A TREE (73 FT AGL), THEN THE ACFT CRASHED & WAS DEMOLISHED BY FIRE. DURING THE INVESTIGATION, AN EXAM OF THE WRECKAGE AND A TEARDOWN OF THE ENG DID NOT REVEAL THE REASON FOR THE POWER LOSS. BOTH FRONT SEAT OCCUPANTS WERE RATED PLTS. THE OCCUPANT IN THE LEFT FRONT SEAT DID NOT HAVE A CURRENT BFR, BUT THE RIGHT FRONT SEAT PLT WAS A CERTIFIED FLT INSTRUCTOR.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record CHI84FA369
Event ID
20001214X40613
Case number
CHI84FA369
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: 46d7e3b18c6bb318794b813663ea32a5f04b8aff1dc4f05ca14fbf04592c5c00; retrieved 2026-09-21T05:22:04.441Z.