CEN23LA415 · Piper PA-32-300
Piper PA-32-300 · Accident: fuel starvation on approach
From Columbia Regional Airport (COU) to an unrecorded destination
Event
- NTSB case
- CEN23LA415
- 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
- Event fatalities
- Unknown
- 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-32-300
- 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
- N4219T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Columbia Regional Airport (COU), Columbia, MOTo not recorded
- Aircraft age
- About 52 years (built 1971)
- 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
- Approach
- 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 › Fluids/miscellaneous hardware
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor stated that prior to beginning the instructional flight, he visually confirmed there was fuel in each fuel tank. He did not use a fuel dip stick when he checked the fuel level and approximated the fuel level as 17 gallons. He said the flight would have required 8 gallons of fuel. About 10 miles from the destination airport, with the fuel selector positioned to the right main fuel tank, the engine began to run rough. He then selected the right auxiliary fuel tank, and the engine began to run smoothly again. About 4 miles from the destination airport and during the approach for landing, the engine began to run rough again. He then selected the left auxiliary fuel tank, but engine power was not restored. With the engine at idle power, he tried to restore engine power by cycling through the remaining fuel tanks but was unsuccessful. He then performed a forced landing to a field, during which the engine ceased to operate. The airplane sustained substantial damage to the fuselage. Postaccident examination of the airplane revealed no leaks with the fuel system and no useable fuel was found in the left and right main fuel tanks. The flight instructor stated that after the accident, he checked the left auxiliary/tip tank and there was 7 gallon of fuel present. The examination revealed no failures or malfunctions with the airframe and engine that would have precluded normal airplane operation.
Probable cause
The flight instructor’s inadequate fuel management that resulted in fuel starvation and a total loss of engine power during an approach for landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA415
- Event ID
- 20230921193115
- Case number
- CEN23LA415
- 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: local date, investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2023-09-11.
- API snapshot SHA-256: 76dca9da0d7798dd66bf9cf5dbf98fe3b095ac1c6cab948a9627471cf16e180b; retrieved 2026-09-16T18:08:52.868Z.