FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN26LA069 · Cessna 172D

19 Dec 2025 · Post, TX, United States

Cessna 172D · Accident: fuel starvation en route

Report a problem

Event

NTSB case
CEN26LA069
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 172D

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
N2536U
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 62 years (built 1963)
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 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot was delivering a recently purchased airplane for a friend and decided to land for fuel. While in the landing pattern the engine lost all power. The pilot immediately turned toward the runway, switched the fuel selector valve from both to the left tank position, then to the right tank, and back to both while he attempted to restart the engine, without success. The pilot conducted a forced landing to a field. During the landing the airplane struck and came to rest in Mesquite trees about 100 yards north of the airport. The airplane sustained substantial damage to the right wing outer leading edge, the left leading edge of the horizontal stabilizer, the firewall, and the fuselage lower skin. After the accident, the pilot checked the fuel level. When he removed the first fuel cap, he noticed the sound of air rushing into the fuel tank. Further examination by the FAA revealed dry, hard dirt consistent with a Mud Dauber nest blocking the fuel tank vent tube. They also found the right fuel cap vent was deteriorated and inoperative and the left fuel cap was not a vented cap. The FAA stated about 6 gallons total fuel remained in both right and left fuel tanks. The airplane did not have a current annual inspection.

Probable cause

The pilot’s failure to see the blockage in the fuel tank vent tube during the preflight inspection which resulted in the loss of engine power due to fuel starvation. Contributing to the accident was the deterioration of the right fuel cap vent to the point where it was inoperative.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN26LA069
Event ID
20251229202218
Case number
CEN26LA069
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: 217743ed022ae4c20751b7b886eed5ba6615fb71eedbdc73645b1fc85714a88c; retrieved 2026-09-16T20:37:56.400Z.