FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16LA164 · Piper PA28 161

18 Apr 2016 · Okeechobee, FL, United States

FlightSafety International Piper PA28 161 · Accident: loss of engine power (total) en route

From Naples Municipal Airport (APF) to Vero Beach Regional Airport (VRB)

Report a problem

Event

NTSB case
ERA16LA164
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
Unknown
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 PA28 161

Aircraft type
Piper PA28
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
N151DC
Onboard fatalities
Unknown
Route
From Naples Municipal Airport (APF), Naples, FLTo Vero Beach Regional Airport (VRB), Vero Beach, FL
Aircraft age
About 15 years (built 2001)
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
Defining eventThe 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 (total)
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

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft power plant
  • Environmental issues › Physical environment

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

NTSB narrative

The operator reported that the pilot was conducting a cross-country, solo instructional flight. When the airplane was about 3,000 ft mean sea level, the engine suddenly started running roughly accompanied by “abnormal” noises. The pilot attempted to troubleshoot the problem by performing the “engine roughness” checklist to no avail. About 10 seconds after completing the checklist, the engine lost all power. The pilot then established the best glide speed, chose a private grass strip for a forced landing, and conducted the “engine power loss in flight” checklist without success. Once committed to landing, he conducted the “power off landing checklist.” After the airplane touched down about halfway down the grass strip it skidded and subsequently impacted farm equipment and other obstacles, and it then came to rest against a building. The airplane sustained substantial damage to the fuselage and tail section, and the wings were sheared off. Examination of the engine revealed that there was a hole in the crankcase above the No. 2 cylinder, consistent with a catastrophic engine failure, and that the No. 3 piston had failed. Metallurgical examination of the No. 3 piston revealed that two fatigue cracks had emanated from the outer face of a lubricating hole, which resulted in the piston failing, ancillary damage to the cylinder and engine, and a subsequent total loss of engine power. The areas outside of the fatigue crack regions and fracture faces exhibited a rough texture and on-slant planes consistent with overstress separation. The reason for the initiation and propagation of the fatigue cracks could not be determined. Even though the engine was 200 hours past the manufacturer’s recommended time before overhaul limit, it could not be determined if that contributed to the fatigue cracking.

Probable cause

The failure of the No. 3 piston due to fatigue cracking, which resulted in a total loss of engine power and subsequent forced landing, during which the airplane impacted obstacles.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16LA164
Event ID
20160419X94234
Case number
ERA16LA164
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 41c4df9442b41460215b8f159cf03929e9bc2da83a05f30e629d236f4e0b820a; retrieved 2026-09-16T03:18:36.903Z.