FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA23LA337 · Piper PA32 300

12 Aug 2023 · Haines City, FL, United States

Piper PA32 300 · Accident: fuel starvation en route

From Kissimmee Gateway Airport (ISM) to an unrecorded destination

Report a problem

Event

NTSB case
ERA23LA337
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
N898CP
Operator
Unknown
Onboard fatalities
Unknown
Route
From Kissimmee Gateway Airport (ISM), Orlando, FLTo not recorded
Aircraft age
About 48 years (built 1975)
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
Fuel starvation
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 systems

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported the purpose of the flight was to perform a local post-maintenance test flight. The pilot reported that during his preflight inspection, he manually checked all four fuel tanks and reported that he had sufficient fuel for the flight. The pilot reported that the taxi, engine runup, takeoff, and the initial climb were normal. The pilot reported that after beginning an en route climb, the engine power dropped to 1,200 rpm. The pilot attempted to restart the engine multiple times; however, engine power did not return and the pilot performed a forced landing. During the landing the airplane struck trees, resulting in substantial damage to the wings and the fuselage. Postaccident examination revealed that the air intake tube attached to the fuel servo inlet had a large hole in the tube, which would allow unfiltered air to enter the throttle body and the engine’s induction system. The fuel servo air inlet displayed signs of contamination; however, testing revealed that while there was contamination in the fuel servo’s air side metering chamber, the fuel servo was capable of normal operation on the test equipment. The examination of the rest of the airframe and the engine did not reveal any other anomalies that would have precluded normal operation. Data recovered from onboard avionics revealed that just before the loss of engine power, the fuel pressure and the fuel flow decreased to about 2 psi and 0.3 gallons per hour (gph) respectively. At the same time, all the engine’s exhaust gas temperatures (EGT) increased about 200°F before dropping to levels that were consistent with combustion no longer occurring within the engine cylinders. These indications were consistent with the engine being starved of fuel. The data further revealed that both auxiliary fuel tanks and the left main fuel tank had sufficient fuel; however, the right fuel quantity indicator was malfunctioning and reported 0 gallons. The pilot reported he knew that the right main fuel quantity was malfunctioning, which is why he always manually checked the fuel tanks before flight. Due to the malfunctioning right main fuel quantity indicator, and the right main fuel tank’s breach during the accident sequence, the amount of fuel in the right main fuel tank at the time of the loss of engine power could not be determined. The pilot reported that after the loss of engine power, he switched tanks twice in an attempt to restart the engine. Despite the pilot switching to a fuel tank that was reporting sufficient fuel, and turning on the airframe’s electrically driven fuel pump, the fuel pressure and fuel flow never returned to a level that would support engine operation.

Probable cause

A total loss of engine power due to fuel starvation for reasons that could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23LA337
Event ID
20230815192879
Case number
ERA23LA337
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, 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: 31e986cd9dd874ecb5ec249e272b8d51e818237272619efdb588bacc6b3b55bf; retrieved 2026-09-16T18:00:34.824Z.