Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

April 18, 2016 · Piper PA28 161 · N151DC

Okeechobee, FL

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
April 18, 2016
Injury Outcomes
1 injury (1 minor injury)
Location
Okeechobee, FL
Aircraft
Piper PA28 161 (2001)
Tail Number
N151DC
Operator
Flightsafety International
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
ERA16LA164

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.

NTSB 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.

Full Narrative

On April 18, 2016, about 1530 Eastern daylight time, a Piper PA-28-161, N151DC, was substantially damaged when it was involved in an accident near Okeechobee, Florida. The pilot sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 solo instructional flight. The operator reported that, when the airplane was about 3,000 ft mean sea level, the engine suddenly started to run roughly accompanied by “abnormal” noises. The engine instruments remained in the normal range. The pilot attempted to troubleshoot the problem by performing the “engine roughness” checklist without success. Shortly after, the pilot contacted the Miami Air Route Traffic Control Center and reported the problem, and a controller suggested that the pilot proceed to the St Lucie County International Airport (FPR), Fort Pierce, Florida, where emergency services would be standing by. However, about 10 seconds after completing the checklist, the engine lost all power. The pilot then established the best glide speed and chose a private grass strip for 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 touching down, the airplane skidded and subsequently impacted farm equipment and other obstacles, and it then came to rest against a building. A review of the engine’s maintenance records revealed that it had accrued 10,382.8 total flight hours and 2,600.8 hours since the last overhaul. The engine manufacturer’s recommended time between overhaul was 2,400 hours. Postaccident examination of the airplane revealed that it had sustained substantial damage to the fuselage and tail section and that the wings had been sheared off. During postaccident examination of the engine, a hole was found in the crankcase above the No. 2 cylinder. Metal was found in most of the folds of the oil filter material and in the Nos. 3 and 4 cylinders, and ferrous and nonferrous materials were found throughout the crankcase. During a subsequent compression check, the No. 3 cylinder’s compression was excessively low, The No. 3 piston would not move when the crankshaft was manually rotated. After the No. 3 cylinder was removed, only the connecting rod and piston pin were found. The No. 3 cylinder’s interior was extensively damaged. Metallurgical examination of the No. 3 piston revealed that it was fractured and that it had two fatigue cracks emanating from the outer face of a lubricating hole in a groove for a compression ring. (See figure 1, which is a photograph showing the two fatigue cracks in the No. 3 piston in relation to the lubricating hose and compression ring groove. The white arrows indicate the general direction of the fatigue crack propagation.) 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. Figure 1. Photograph showing the No. 3 piston’s two fatigue cracks in relation to the lubricating hole and compression ring groove and the general direction of the fatigue propagation.

Flight

Event TypeAccident
Event Time15:30 EDT
Nearest Airport0nm
Flight Plan FiledVFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA28 161
Tail NumberN151DC
Aircraft CategoryAir
DamageSubstantial
OperatorFlightsafety International
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · 0-320 SERIES · Reciprocating · 160
Seats4

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 23 · First Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind60° @ 9 kt, gusting 18 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point55
Altimeter30.15 inHg
Observation Time19:35
Weather SourceWFAC

Appendix: Source Data