FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN23LA396 · Cessna 172G

2 Sept 2023 · Neola, IA, United States

Cessna 172G · Accident: fuel exhaustion en route

From SKY · Sac City, IA to Council Bluffs Municipal Airport (CBF)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN23LA396
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

Cessna 172G

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
N1374F
Operator
Unknown
Onboard fatalities
Unknown
Route Possible conflict
From SKY · Sac City, IATo Council Bluffs Municipal Airport (CBF), Council Bluffs, IA
Aircraft age
About 57 years (built 1966)
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 · 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 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 the airplane was full of fuel before he departed for the cross-country flight. After flying for about 2 hours and 50 minutes, with a significant headwind, he decided to divert to an airport to refuel. During his attempt to refuel, it was discovered that the fuel pumps were out of order, and he did not see the active notice to airmen (NOTAM) for the out of order fuel pumps. The pilot calculated the fuel remaining in the airplane and departed for his destination. After flying for about 40 minutes, the engine lost power and he executed a forced landing on a road about 12 miles from the destination airport. During the landing, the airplane impacted a swale and nosed over adjacent to the road which resulted in substantial damage to the airplane’s fuselage and both wings. The pilot reported that there were no preaccident mechanical malfunctions or failures that would have precluded normal operation. The pilot noted that a more thorough flight planning and a more accurate use of the airplane’s performance charts could have prevented the accident.

Probable cause

The pilot’s inadequate 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 CEN23LA396
Event ID
20230905192997
Case number
CEN23LA396
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-03.
  • API snapshot SHA-256: 1ee1dc6410bafbb333bdd6d0b8aa9f33850f2604293e25a1c335e946e000e692; retrieved 2026-09-16T18:04:52.736Z.