CEN23LA345 · Piper PA-28-181
Piper PA-28-181 · Accident: fuel exhaustion en route
From Boerne Stage Field (5C1) to Pearland Regional Airport (LVJ)
Event
- NTSB case
- CEN23LA345
- 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-28-181
- Aircraft type
- Piper PA-28
- 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
- N38483
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Boerne Stage Field (5C1), San Antonio, TXTo Pearland Regional Airport (LVJ), Houston, TX
- Aircraft age
- About 46 years (built 1977)
- 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
- 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 exhaustion
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot stated that in preparation for his solo cross-country flight, he reviewed his flight planning with his flight instructor. He said he flew to the destination airport, where he performed one approach and landing, followed by flight maneuvers north of the airport, and then landed. The pilot shut the airplane down to use the restroom. Prior to departure from the destination airport, he did not visually check the airplane fuel level through the fuel filler ports. During the return flight, he visually observed the fuel quantity and was decreasing rapidly, and he decided to land at an alternate airport. During the approach to the alternate airport, the engine sputtered and lost power. He landed the airplane with a tailwind and strongly applied the brakes to try to slow the airplane down as soon as possible. The airplane overran the runway and impacted a fence and construction equipment that resulted in substantial damage to both wings. Postaccident examination of the airplane revealed no useable fuel in the airplane fuel tanks.
Probable cause
The student pilot’s improper fuel management that resulted in fuel exhaustion, a total loss of engine power, and a subsequent forced landing and landing overrun at an alternate airport.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA345
- Event ID
- 20230803192784
- Case number
- CEN23LA345
- 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: aafda57671b6037c4a04391cb59faf3ee5b92f5c12fe97e0b48a3a00bfd7b7a6; retrieved 2026-09-16T17:57:20.516Z.