FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17FA085 · Cessna 172

25 Jan 2017 · Jay, OK, United States

Cessna 172 · Accident: fuel starvation during takeoff

From Jay, OK to Grove Regional Airport (GMJ)

Report a problem

Event

NTSB case
CEN17FA085
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
1 · 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 172

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
N5639A
Operator
Unknown
Onboard fatalities
Unknown
Route
From Jay, OKTo Grove Regional Airport (GMJ), Grove, OK
Aircraft age
About 61 years (built 1956)
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
Takeoff
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
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 › Aircraft handling/service
  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Task performance

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

NTSB narrative

The private pilot was conducting a personal cross-country flight. Fuel records indicated that the pilot had purchased 9.56 gallons of fuel the day before the accident. A witness reported observing the pilot use fuel cans to add fuel to both airplane's fuel tanks. The witness saw the pilot taxi up and down the runway multiple times and subsequently depart; he then drove to the nearby airport (the pilot's intended destination) to pick up the pilot. When the pilot did not arrive, he reported the airplane missing. Responders tracked the emergency locator transmitter signal, and a helicopter pilot spotted the airplane in a field near a tree line.

Upon examination, the propeller blades did not exhibit any chordwise abrasions or leading edge nicks, consistent with the engine not producing power at the time of impact. The fuel system was found intact except for a separated line near the left fuel tank. About 6 gallons of a blue-colored liquid consistent with the smell and color of aviation gasoline (avgas) was recovered from the right fuel tank. About 2 gallons of liquid consistent with avgas was recovered from the left fuel tank. Each fuel tank could hold 21 gallons of fuel, of which 2.5 gallons was unusable. There was some liquid consistent with avgas found in the carburetor bowl and in the firewall-mounted strainer bowl. All found and recovered liquid samples were tested for water contamination, and no water contamination was observed. Observed airplane damage was consistent with impact with trees and inverted impact with terrain.

The fuel valve selector handle was found in the "right tank" position. However, no securing pin was installed in the selector handle, and during postaccident examination, pressurized air applied to the main fuel line at the firewall was observed discharging from the left tank's fuel line, which showed the selector valve fed the engine from the left tank. The engine operated normally during postaccident engine test runs. Based on the evidence, it is likely that the engine was starved of fuel when the fuel selector handle did not move the fuel selector valve to the desired position because the necessary securing pin was missing. The airplane's most recent annual inspection was completed about 8.5 years before the accident. The lack of routine maintenance on the airplane likely eliminated the necessary opportunities for the missing securing pin to be corrected.

Probable cause

The pilot's negligent maintenance of the airplane, which resulted in improper fuel management, fuel starvation, and a loss of engine power during takeoff due to a missing securing pin in the fuel selector handle, and a subsequent forced landing on unsuitable terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17FA085
Event ID
20170126X02237
Case number
CEN17FA085
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. 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: 182fa0cdcd643cfbcbc19a98385ec4df2478e4ac2b075559599741ddfe5ae200; retrieved 2026-09-15T05:58:14.780Z.