FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24LA211 · Piper PA32 300

8 May 2024 · Apopka, FL, United States

Piper PA32 300 · Accident: loss of engine power (partial) en route

From Orlando Executive Airport (ORL) to Bartow Executive Airport (BOW)

Report a problem

Event

NTSB case
ERA24LA211
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
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 PA32 300

Aircraft type
Piper PA32
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
N908DK
Operator
Unknown
Onboard fatalities
Unknown
Route
From Orlando Executive Airport (ORL), Orlando, FLTo Bartow Executive Airport (BOW), Bartow, FL
Aircraft age
About 51 years (built 1973)
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
  • Personnel issues › Task performance

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

NTSB narrative

After departing, the pilots initiated a climb to 2,500 ft mean sea level (msl), during which the engine began to run “rough.” One of the pilots noticed that two cylinders had stopped producing power and he asked the pilot/owner to look up the common traffic advisory frequency for the closest airport. An emergency radio transmission was made and the pilot/owner noticed that two more cylinders had stopped producing power and the airplane was unable to maintain altitude. The other pilot identified an area and performed a forced landing, during which the left wing struck a tree and sustained substantial damage. Postaccident review of engine data for the flight showed that the exhaust gas temperatures (EGT) of the Nos. 2, 3, 4, and 6 cylinders dropped excessively. These drops in EGT and subsequent loss of cylinder head temperatures (CHT) were consistent with the cylinders failing to produce power. Additionally, the data showed that the oil temperature reached a maximum of 231° F (the engine manufacturer’s maximum permitted oil temperature was 245° F). Postaccident examination of the airplane found the thermostatic oil cooler bypass valve in the oil filter adapter was not seating properly and was allowing hot oil to partially bypass the oil cooler, increasing the temperature of the engine. When the oil filter adapter was replaced, the engine was successfully test run according to manufacturer’s standard power and leak engine run test. The test also revealed that the engine airflow limit was below the designated range, which would result in the engine having slightly less power and a richer fuel/air mixture. The spark plugs were dark in color, which was also consistent with excessively rich fuel air/mixture engine operation. The airplane was also based and operated in an area that typically experienced high ambient temperatures and was operated using leaded fuel; two factors that could contribute to an increased rate of oil contaminant accumulation. An examination of the engine exhaust valve stems found buildup of carbon on the combustion side of the exhaust guides in five cylinders. Given this information, the rich mixture and elevated oil temperature likely led to the buildup of carbon and coked oil that resulted in the sticking of multiple exhaust valves during the accident flight. The pilot/owner reported that there had been three previous events during which the engine lost power in the cylinders; each time the engine was returned to service by the maintenance provider. Historical data from the engine monitoring device showed cylinder behavior consistent with the accident flight. Specifically, during those flights, the oil temperatures were near or in excess of the engine manufacturer’s limit. Maintenance personnel reported they had not reviewed at the historical engine data during troubleshooting or before returning the airplane to service. It is possible that if maintenance personnel reviewed the engine data they could have identified the high oil temperature trend and correlated it to the multiple losses of power in individual cylinders. Additionally, a review of the airplane’s maintenance logbooks revealed that the engine was 15 years past the manufacturer’s recommended time between overhaul. There was no evidence that an engine manufacturer service bulletin related to determining exhaust valve and guide condition was complied with, nor, based on the logbooks and date of overhaul, is it likely that improved design exhaust valve guides were installed on the engine. Had the valve guide inspections called for in the service bulletin been complied with, it is likely that the oil coking and carbon buildup, that were the likely result of the rich engine operation and high oil temperature, would have been detected and addressed before resulting in the losses of power that were observed on the accident and previous flights.

Probable cause

A partial loss of engine power due to sticking exhaust valves. Contributing to the accident was maintenance personnel’s failure to use available engine data while troubleshooting a known engine issue and maintenance personnel’s failure to comply with inspections called out in a relevant service bulletin.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24LA211
Event ID
20240508194224
Case number
ERA24LA211
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: e3e44215155868a366053cd3414df1d2d4dae524d995a863d3877506a30bb396; retrieved 2026-09-16T18:44:42.580Z.