CEN24LA019 · Cessna 172C
Cessna 172C · Accident: fuel exhaustion on approach
From Colonel James Jabara Airport (AAO) to Wichita Dwight D. Eisenhower National Airport (ICT)
Event
- NTSB case
- CEN24LA019
- 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
Cessna 172C
- Aircraft type
- Cessna 172
- 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
- N1413Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Colonel James Jabara Airport (AAO), Wichita, KSTo Wichita Dwight D. Eisenhower National Airport (ICT), Wichita, KS
- Aircraft age
- About 62 years (built 1961)
- 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 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that she filled the airplane with fuel before departure. After flying for about 4 hours, the engine lost power and she executed a forced landing on a road about 1.5 miles from the destination airport. During the landing roll, the airplane impacted two street signs and a power pole guy wire which resulted in substantial damage to the airplane’s left wing and fuselage. The pilot reported that there were no preaccident mechanical malfunctions or failures that would have precluded normal operation. Postaccident examination of the airplane revealed no anomalies with the fuel system; the fuel tanks were empty, and there was no evidence of a fuel leak. About 8 ounces of fuel were recovered from the gascolator. The pilot noted that verification of total fuel onboard before each departure and more accurate usage of the airplane’s performance charts could have prevented the accident.
Probable cause
The pilot’s inadequate preflight inspection and fuel planning and improper in-flight decision-making, which resulted in a total loss of engine power due to fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA019
- Event ID
- 20231023193286
- Case number
- CEN24LA019
- 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: c3065ac1a1464cf808286f6dd59a25a38bc82588f13d6a40b9aad1786b9dac2c; retrieved 2026-09-16T18:14:27.064Z.