ERA13FA256 · Piper PA-32R-300 32R-768045
Flebo Air Piper PA-32R-300 32R-768045 · Accident: powerplant system/component malfunction/failure during an emergency descent
From Apalachicola Regional Airport (AAF) to Greenville Downtown Airport (GMU)
Event
- NTSB case
- ERA13FA256
- 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
- 2 · 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 PA-32R-300 32R-768045
- Aircraft type
- Piper PA-32
- 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
- N4489F
- Operator
- Flebo Air
- Onboard fatalities
- Unknown
- Route
- From Apalachicola Regional Airport (AAF), Apalachicola, FLTo Greenville Downtown Airport (GMU), Greenville, SC
- Aircraft age
- About 37 years (built 1976)
- 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
- Emergency descent
- 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
- Powerplant system/component malfunction/failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft power plant
- Aircraft › Fluids/miscellaneous hardware
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A review of air traffic control information revealed that, during the cross-county flight, the pilot requested clearance for a precautionary landing at a nearby airport due to a low oil pressure indication. Shortly after the flight was cleared for landing, the pilot reported that the engine had lost total power. The pilot advised the air traffic controller that he could not make it to the airport and requested to land at a military base that was closer to his current position. The pilot was cleared to land at the military base; however, he never established radio contact with the military base tower. The airplane crashed about 0.8 mile northeast of the base in a heavily wooded swamp, and a postcrash fire ensued.
An examination of the engine revealed that the crankcase was fractured in the areas of the Nos. 4, 5, and 6 cylinders, that the camshaft was fractured, and that the Nos. 4, 5, and 6 connecting rods were separated from the crankshaft. The Nos. 1 and 2 connecting rod bearings and the Nos. 2 and 3 main bearings exhibited wiping, scoring, and extrusion signatures consistent with oil starvation. Although review of maintenance records revealed that Federal Aviation Administration airworthiness directives for the replacement of the oil cooler hose and the oil filter converter plate gasket were not accomplished, extensive postcrash fire and heat damage to the engine components precluded a determination of the cause of the oil starvation.
Probable cause
A total loss of engine power due to oil starvation for reasons that could not be determined due to extensive postcrash fire and heat damage to the engine components.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13FA256
- Event ID
- 20130527X93911
- Case number
- ERA13FA256
- 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, coordinates. 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: 2805ccddcfcc9a8b4b5a9f0206bfdca082e4968a7eaa6c6bbcedd94e7d45b496; retrieved 2026-09-14T15:57:17.980Z.