NYC08CA113 · Cessna 177B
Cessna 177B · Accident: fuel exhaustion on approach
From 68J · Tallahassee, FL to Quincy Municipal Airport (2J9)
Event
- NTSB case
- NYC08CA113
- 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 177B
- 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
- N49AF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 68J · Tallahassee, FLTo Quincy Municipal Airport (2J9), Quincy, FL
- 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
- 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
- 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
- Tree(s)
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that he was attempting a long cross-country flight, with a planned fuel stop at an airport about halfway to his intended destination. While en route to the planned fuel stop, the airplane consumed more fuel than planned due to greater than forecasted headwinds. The pilot also elected to fly at a lower than planned altitude, in order to avoid turbulence. Although the flight was consuming more fuel than planned, the pilot believed that an adequate amount of fuel remained to fly to the planned fuel stop and beyond. After landing uneventfully for the planned fuel stop, the pilot was informed that the airport fixed base operator had run out of fuel. The pilot then elected to depart, and refuel the airplane at an airport about 10 miles away. While on final approach to that airport, the engine lost all power, and the pilot performed a forced landing into trees. Examination of the wreckage revealed that approximately 3.5 total gallons of aviation fuel was recovered from the airplane's four fuel tanks. The examination did not reveal any preimpact mechanical malfunctions, nor did the pilot report any.
Probable cause
The pilot's inadequate in-flight decision by failing to refuel, resulting in fuel exhaustion and the loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC08CA113
- Event ID
- 20080324X00370
- Case number
- NYC08CA113
- 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: 9d47f8a6a8b7aeedc66a6de2525ab68f3b078248833189b45f1e3a48ee6b85cd; retrieved 2026-09-15T09:27:33.893Z.