FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12LA294 · Cessna 172R

19 Apr 2012 · Richmond, KY, United States

Eastern Kentucky University Cessna 172R · Accident: fuel exhaustion en route

From Hisle Field (75KY) to I39 · Richmond, KY

Report a problem

Event

NTSB case
ERA12LA294
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 172R

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
N28BC
Onboard fatalities
Unknown
Route
From Hisle Field (75KY), Winchester, KYTo I39 · Richmond, KY
Aircraft age
About 12 years (built 2000)
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 · cruise
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 › Action/decision

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

NTSB narrative

The flight instructor reported that, after getting in the airplane, he asked the student pilot how much fuel was in each tank. The student pilot replied that 21.5 gallons of fuel were in one tank and 20 gallons of fuel were in the other tank. The student pilot reported dipping a "fuel stick" into the fuel tanks during the preflight to check the fuel levels. Although the flight instructor noticed that the fuel quantity indicators showed that 20 gallons of fuel were in one tank and 15 gallons of fuel were in the other tank, he did not question the fuel discrepancy. A review of security camera video revealed that the flight instructor did not supervise the student pilot's preflight inspection nor conduct a walk-around inspection.

After departure, the student pilot flew the airplane to another airport for a short- and soft-field training lesson. After 45 minutes of training, they departed for their home airport. Although the flight instructor noticed that the fuel gauges were reading low, he chose to continue the flight. Five miles north of the airport, the engine began sputtering, and the flight instructor took control of the airplane. He turned on the fuel pump and richened the fuel mixture, and the engine started running normally. He then decided to climb to get as much altitude as possible while continuing to fly to the airport. One minute later, the engine lost power. The flight instructor then unsuccessfully attempted to restart the engine. When he realized that the airplane would not make the runway, he decided to land in a field. During the approach and landing roll, the airplane struck power lines, and the right wing struck a tree and was substantially damaged.

Examination of the fuel tanks revealed that they were empty and that neither of them was breached. No evidence of fresh fuel staining or leakage was found above or below the wings or on the belly of the airplane. After adding 5 gallons of fuel to the left wing tank, the engine was started, and it ran normally. Examination of the fuel sticks used by the operator revealed that they did not have aircraft registration markings on them to verify if the correct fuel stick was onboard the correct aircraft and that one of the airplanes in the fleet with 20-gallon tanks had a 26.5-gallon fuel stick in the cockpit. It could not be determined whether the student pilot used the proper fuel stick during the preflight inspection. Examination of the operator's fueling pad and parking ramp revealed that they were significantly sloped. Examination of its fueling and parking procedures also revealed that the airplanes were being parked and serviced with the fuel selector valves in the "both" position. According to the airplane manufacturer, the airplane should be parked in a wings-level, normal ground attitude with the fuel selector in the "left" or "right" position to ensure maximum fuel capacity and minimize cross-feeding when refueling.

Probable cause

A total loss of engine power due to fuel exhaustion. Contributing to the accident was the flight instructor’s failure to supervise the student’s preflight inspection, his inadequate fuel management and preflight and in-flight fuel planning, and the operator’s inadequate fueling policies and procedures.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12LA294
Event ID
20120420X40144
Case number
ERA12LA294
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: f8979bc41ef298bbcbfabe9dc02d87b8b19f985d000ea8e440f9764111faa841; retrieved 2026-09-15T17:50:35.971Z.