CEN22LA036 · Cessna 177
Cessna 177 · Accident: fuel exhaustion en route
From Guthrie-Edmond Regional Airport (GOK) to an unrecorded destination
Event
- NTSB case
- CEN22LA036
- 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 177
- Aircraft type
- Cessna 177
- 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
- N29615
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Guthrie-Edmond Regional Airport (GOK), Guthrie, OKTo not recorded
- Aircraft age
- About 53 years (built 1968)
- 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 · descent
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire
- 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
During a personal flight, the pilot was descending the airplane for landing and added throttle, but the engine did not respond. The pilot decided to make a forced landing, during which the airplane collided with power lines and terrain, resulting in substantial damage to the airplane. Postaccident examination of the airplane and engine found damage in the engine area that precluded documentation of the throttle cable’s full range of travel. Examination of the accident site found no evidence of fuel in the tanks, but fuel did not appear to have leaked from the tanks. The pilot reported that the airplane should have contained at least 10 gallons of fuel. Thus, the pilot’s fuel calculations could have been incorrect, resulting in fuel exhaustion. In addition, the airplane was operating in an area conducive for the formation of serious icing at glide power. However, the pilot stated that he applied carburetor heat and enrichened the mixture when he began descending. The postaccident airplane and engine examination revealed no preimpact anomalies that would have precluded normal operation. As a result, and based on the available evidence, the reason for the partial loss of engine power was most likely the result of fuel exhaustion.
Probable cause
The partial loss of engine power due to fuel exhaustion. Contributing was the pilot’s improper fuel planning.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22LA036
- Event ID
- 20211117104257
- Case number
- CEN22LA036
- 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 2021-10-31.
- API snapshot SHA-256: fdfa5d6df381c0f3c5601b1ec412aca210137e5f9ee644a7cb8bbcb7e2f2fff9; retrieved 2026-09-16T14:45:03.478Z.