FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16CA277 · Cessna 172

29 Jun 2016 · Gray, GA, United States

Cessna 172 · Accident: loss of engine power (total) en route

From Marion County Airport - Brown Field (APT) to Macon Downtown Airport (MAC)

Report a problem

Event

NTSB case
ERA16CA277
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 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
N288GB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Marion County Airport - Brown Field (APT), Jasper, TNTo Macon Downtown Airport (MAC), Macon, GA
Aircraft age
About 54 years (built 1962)
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
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
Loss of engine power (total)
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 commercial pilot, his passenger, and his 80- to 100-lb dog were on a cross-country flight and had just leveled off at 2,500 ft when the engine suddenly stopped producing power. The pilot was unable to restart the engine and made a forced landing to a field. During the landing, the airplane struck a tree and a fence, which resulted in substantial damage to the firewall, fuselage, and wings.

Postaccident examination of the airplane revealed the right fuel tank had 15 gallons of fuel in it and that the left tank was empty. The fuel selector valve was found between the "left" and "both" tank positions. The front right seat had been removed before the flight to accommodate the pilot's dog, who sat on the floor during the flight. The pilot said he departed with the fuel selector valve in the "both" position, but during the flight, the dog must have inadvertently moved the valve's handle toward the "left" tank position, which resulted in the loss of engine power due to fuel exhaustion. A functional check of the fuel selector valve revealed no mechanical issues, and the valve seated securely into each detent. The pilot reported that there were no mechanical deficiencies with the engine that would have precluded normal operation.

Probable cause

The pilot's failure to properly manage the available fuel supply, which resulted in a total loss of engine power due to fuel starvation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16CA277
Event ID
20160801X62810
Case number
ERA16CA277
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: 40e6a74757e844e5c4be6c1c7c0cdec9be350d899bb5c876198e145e52c042bc; retrieved 2026-09-16T03:43:45.798Z.