FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13FA217 · Cessna 172N

27 Apr 2013 · Dade City, FL, United States

Cessna 172N · Accident: loss of engine power (partial) en route

From Brooksville–Tampa Bay Regional Airport (BKV) to Treasure Coast International Airport (FPR)

Report a problem

Event

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

Cessna 172N

Aircraft type
Cessna 172
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
N5944J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Brooksville–Tampa Bay Regional Airport (BKV), Hernando County, FLTo Treasure Coast International Airport (FPR), Fort Pierce, FL
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
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 (partial)
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 power plant

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

NTSB narrative

During the accident flight, the exhaust gas temperature on the No. 3 cylinder began as the coldest and then transitioned to the hottest. Subsequently, the cylinder head temperature on the No. 3 cylinder also transitioned to the hottest. According to the pilot, the engine then began to run roughly, and he adjusted the throttle and mixture positions to gain control of the malfunctioning engine. During emergency communications with air traffic control, the engine lost all power, and the pilot conducted an emergency landing to a field.

Examination of the engine revealed that the No. 3 cylinder exhaust valve rocker arm stud had backed out of the cylinder, which prevented the exhaust valve from opening properly. Specifically, the loose rocker arm stud prevented the pushrod from depressing the exhaust valve far enough in to release exhaust from the cylinder, which damaged the intake valve pushrod and caused a complete loss of engine power. The No. 3 cylinder had been replaced about 14 months before the accident and had accumulated 480.9 hours since installation. It is likely that the rocker arm and nut assembly became loose over time; the initial torque value could not be determined.

Probable cause

The in-flight loosening of the No. 3 cylinder exhaust valve rocker arm stud, which resulted in a complete loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13FA217
Event ID
20130428X43611
Case number
ERA13FA217
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. 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: 3bca890011ca48c44d33592a2d3176de3eb8e08f25375d4656f5c0e78a520b3f; retrieved 2026-09-15T21:22:02.891Z.