MIA95IA243 · Piper PA-28-161
Piper PA-28-161 · Incident: partial loss of engine power (mechanical failure) en route
From 34J to an unrecorded destination
Event
- NTSB case
- MIA95IA243
- 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
- Incident
- 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-28-161
- 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
- N150ER
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 34JTo 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
- En route · climb to 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
- None
Cause areas
- Engine assembly, piston › Failure
- Engine assembly, piston › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During an instructional flight, the flight instructor (CFI) retarded the throttle to idle to simulate an engine failure. The exercise was discontinued at about 500 feet with application of full power. While climbing through about 1,100 feet, the engine suddenly began to run rough, and the tachometer indicated 2,000 rpm. Attempts to restore engine power were unsuccessful. The CFI took the controls and landed uneventfully at a nearby airport. Examination of the engine revealed that a piston and piston pin in the #2 cylinder had failed. Metallurgical examination of the failed components revealed that both failed due to fatigue. The failed components had accumulated about 316.9 hours since installation during a major engine overhaul.
Probable cause
fatigue failure of the piston assembly (piston and piston pin).
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA95IA243
- Event ID
- 20001207X04544
- Case number
- MIA95IA243
- 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, damage. 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: 40cc992159f9bd244b7573c0bd480b859c845eab20b7cc07cfb148062a31ea7e; retrieved 2026-09-22T23:17:14.628Z.