FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12LA180 · Piper PA-32-260

14 Feb 2012 · Amory, MS, United States

Piper PA-32-260 · Accident: fuel exhaustion en route

From Umatilla Municipal Airport (X23) to Olive Branch Airport (OLV)

Report a problem

Event

NTSB case
ERA12LA180
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
Instrument Meteorological Cond

Piper PA-32-260

Aircraft type
Piper PA-32
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
N3688W
Onboard fatalities
Unknown
Route
From Umatilla Municipal Airport (X23), Umatilla, FLTo Olive Branch Airport (OLV), Olive Branch, MS
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
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
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot reported that he had topped off the airplane with 6 hours of fuel, based on a best economy mixture setting, for a planned 4-hour cross-country flight. While filing his instrument flight plan, the weather briefer advised the pilot of moderate icing along the route of flight at an altitude range that included the pilot's planned cruising altitude. Although the single-engine airplane was not certified or equipped for flight into known icing conditions, the pilot proceeded with the flight. While en route, about 200 miles from the destination airport, the airplane's engine began to run rough, and the pilot enriched the fuel mixture, which alleviated the problem and also resulted in an increased fuel burn from about 14 gallons-per-hour to about 18 gallons-per-hour. At that time, the airplane was over a large metropolitan area with an airport where the pilot could have made a fuel stop; however, the pilot did not stop. As the flight continued, he had to descend to lower and lower altitudes due to icing conditions.

About 4 hours into the flight, the pilot realized that he did not have enough fuel to reach his planned destination and attempted to divert to an airport that was 65 miles closer than the original destination airport. As an air traffic controller was providing vectors to the instrument landing system approach at the diversion airport, the pilot reported twice that he was concerned about fuel but did not declare an emergency. Even if the pilot had declared a fuel emergency, the controller’s actions would likely have been no different as he was limited in what he could do by the prevailing instrument meteorological conditions. About 5 minutes after the first report of low fuel, the pilot reported that he had a fuel problem for a third time and that the engine had lost all power. The controller then provided directions to an open field, but the airplane impacted a wooded area about 15 miles from the diversion airport.

The fuel tanks ruptured during the impact sequence, and no fuel odor was present at the accident site. Subsequent examination of the airframe and engine did not reveal any preimpact mechanical malfunctions. At the time of the power loss, the pilot had been flying for about 5 hours, which included flight at both the best economy and richer mixture settings. The airplane held 84 gallons of fuel and, and at the richer mixture setting, it had a fuel endurance of about 4 hours 40 minutes not including fuel needed for start, taxi, takeoff, and climb.

Probable cause

The pilot's inadequate preflight and in-flight planning and decision-making, including his inadequate weather evaluation and his delayed diversion to a closer airport, which resulted in a total loss of engine power due to fuel exhaustion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12LA180
Event ID
20120215X32300
Case number
ERA12LA180
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: d3013def446dc5d0905f5dcf2f95d8158e96f66d855d83d93c5029e07712b71d; retrieved 2026-09-15T17:15:13.738Z.