FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA26LA092 · Cessna 172P

9 Jan 2026 · Flemington, GA, United States

Cessna 172P · Accident: fuel related during initial climb

Report a problem

Event

NTSB case
ERA26LA092
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 172P

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
N96493
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
Not recorded
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
Initial climb
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 related
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 › Aircraft power plant
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Shortly after takeoff, during the initial climb, the pilot stated that he perceived that the airplane’s engine noise was louder than normal. After ensuring that the pilot and passenger side windows were closed and locked, he decided that he would decrease the engine throttle slightly to diagnose the sound. When the pilot reached for the throttle, he inadvertently grabbed the mixture control, and after pulling it back, the engine lost power completely. The pilot attempted to restart the engine twice, but both attempts were unsuccessful. As the airplane was approaching a tree line, and only at an altitude of about 300 ft above the ground, the pilot decided to turn back to a field that was near the end of the runway. The pilot subsequently landed the airplane off-airport, and during the landing roll the nose landing gear encountered a rut. The airplane subsequently nosed over, resulting in substantial damage to the airplane’s rudder and wings. The pilot reported that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.

Probable cause

The pilot’s inadvertent manipulation of the mixture control, which resulted in a total loss of engine power during initial climb and a subsequent forced lading.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA26LA092
Event ID
20260113202290
Case number
ERA26LA092
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: 733c01b754581dc1c1190e0bcd9e1361c41ffa97957734c6d55af5e72b53d5e6; retrieved 2026-09-16T20:40:14.816Z.