CEN17LA261 · Cessna 177
Cessna 177 · Accident: fuel exhaustion on approach
From Bolton Field (TZR) to Fulton County Airport (USE)
Event
- NTSB case
- CEN17LA261
- 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
- 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
- N3225T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bolton Field (TZR), Columbus, OHTo Fulton County Airport (USE), Wauseon, OH
- Aircraft age
- About 50 years (built 1967)
- 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 · VFR pattern final
- 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 › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The accident occurred during the third flight since the airplane had been filled with fuel. The student pilot and flight instructor stated that the engine lost power during the base leg to final approach to turn. The flight instructor took control of the airplane but had insufficient altitude to reach the runway, so he landed the airplane in a field just short of the runway where it contacted a ditch.
The airplane had been flown about 3 hours 45 minutes since it was last filled with fuel. The expected fuel consumption for the engine was 11.7 gallons per hour (gph) at 75% power and 10.14 gph at 65% power, which resulted in an endurance of about 3 hours 30 minutes or 4 hours 10 minutes, respectively. Postaccident examination of the airplane revealed 12 ounces of fuel remained in the fuel system, and there was no evidence of fuel leakage around the airplane. Given the fuel burn calculations and the evidence, it is likely that the flight instructor did not ensure that sufficient fuel was on board for the flight, which led to fuel exhaustion and the subsequent total loss of engine power.
Probable cause
The flight instructor’s inadequate preflight fuel planning, 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 CEN17LA261
- Event ID
- 20170710X64407
- Case number
- CEN17LA261
- 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. 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: 481b226b3c9fcc722f0fb4bdf364dfe57504070d5231034681e85985f4ed0f0a; retrieved 2026-09-16T05:31:28.945Z.