FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16LA007 · Piper PA28R 200

9 Oct 2015 · Savannah, GA, United States

Piper PA28R 200 · Accident: fuel exhaustion on approach

From Jacksonville Executive at Craig Airport (CRG) to Savannah Hilton Head International Airport (SAV)

Report a problem

Event

NTSB case
ERA16LA007
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

Piper PA28R 200

Aircraft type
Piper PA28
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
N9312N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Jacksonville Executive at Craig Airport (CRG), Jacksonville, FLTo Savannah Hilton Head International Airport (SAV), Savannah, GA
Aircraft age
About 46 years (built 1969)
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
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

According to flight service station records, the private pilot had planned a cross-country flight that was expected to be about 465 miles long and to take about 3 hours 15 minutes. The first two-thirds of the flight were uneventful, but the pilot diverted to an alternate airport because the passenger needed a rest stop. He did not purchase fuel at the diversion airport and resumed the flight. According to air traffic control records, while on final approach to the destination airport, an air traffic controller noted that the airplane was low after turning onto the final leg of the traffic pattern and advised the pilot to check his altitude; the pilot did not respond. The airplane then departed controlled flight and crashed. Neither the pilot nor the passenger could recall any events leading up to the accident.

Examination of the wreckage found damage characteristics to the propeller and engine that were indicative of a loss of engine power; however, no preimpact mechanical malfunctions were found. Both fuel tanks were found compromised, but no evidence of fuel was found at the accident site. At the time of the power loss, the airplane had flown a total of about 3 hours 30 minutes. Airplane performance data revealed that the engine consumed about 10 gallons per hour, not including fuel used during taxi, takeoff, and climb. Given that the airplane did not have any fuel on board, it likely was not filled to its total capacity of 50 gallons at departure. Further, the unplanned landing increased the amount of fuel the airplane would have burned, and the pilot likely did not account for this while managing the fuel in flight. Given the evidence, it is likely that the loss of engine power resulted from fuel exhaustion. Further, once the engine lost power, the pilot did not maintain adequate airspeed and exceeded the airplane's critical angle-of-attack on approach to the airport, which resulted in an aerodynamic stall.

Probable cause

The pilot's inadequate preflight fuel planning and in-flight fuel management, which resulted in fuel exhaustion and a total loss of engine power during approach. Contributing to the accident were the pilot’s failure to maintain adequate airspeed and his exceedance of the airplane’s critical angle-of-attack, which resulted in an aerodynamic stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16LA007
Event ID
20151010X52624
Case number
ERA16LA007
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2015-10-10.
  • API snapshot SHA-256: 0620d5740c37484defeb5cfdb4d9f6a2c860bedbcd347c1327deed9b49af00b2; retrieved 2026-09-16T02:52:42.791Z.