FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12TA323 · Aero Commander 500 S

23 Jul 2012 · Elko, NV, United States

Aero Commander 500 S · Accident: fuel exhaustion on approach

From Elko Regional Airport (EKO) to Elko Regional Airport (EKO)

Report a problem

Event

NTSB case
WPR12TA323
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
Government
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

Aero Commander 500 S

Aircraft type
Aero Commander 500
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
N535SA
Onboard fatalities
Unknown
Route
From Elko Regional Airport (EKO), Elko, NVTo Elko Regional Airport (EKO), Elko, NV
Aircraft age
About 40 years (built 1972)
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
Public Aircraft
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 › Action/decision

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

NTSB narrative

The flight mission was to provide airborne coordination for an aerial fire suppression effort. The pilot was a company employee, and the other crewmember, who was not functioning as a pilot, was an employee of the Bureau of Land Management (BLM).

Although the pilot was required by the company to remain present for the duration of the airplane fueling before the flight, he did not do so. A design peculiarity of the fuel quantity system prevented in-cockpit determination of the actual fuel quantity once the fuel level rose above a value that was 21 gallons below the actual maximum capacity. Only a visual inspection of the tank would enable determination of the actual fuel quantity above that level or whether the tank was completely full. The pilot reported that he began the flight with full fuel, but there was no evidence that he visually checked the fuel level. Therefore, it is possible that the flight began with as much as 21 gallons less than the pilot believed. After takeoff, the pilot radioed to his dispatch center that he had 4 hours 30 minutes of fuel on board. Company rules and the exclusive-use contract with the BLM required the pilot to comply with Federal Aviation Administration regulations that precluded departure without a 30-minute fuel reserve.

The fire was located about 15 minutes (still air) flight time from the base airport, but the return flight would be subject to a headwind of about 10 knots. Exclusive of the 30-minute fuel reserve requirement for the beginning of the flight, there were no mission-specific or other factors that dictated the pilot's turnback time. About 4 hours 15 minutes after departure, with the airplane fuel quantity gauge indicating 0 gallons of fuel, the pilot turned back to base. Shortly thereafter, both engines lost power due to fuel exhaustion, and the pilot conducted a forced off-airport landing.

The company's and BLM's guidance differed in several aspects regarding the flight planning, briefing, and communication requirements. Due in part to those differences, the two crewmembers did not conduct any preflight briefing, or any in-flight communications, regarding fuel status. Neither of the two was required to, and they did not, establish a minimum fuel value which, when reached, would require them to depart the operating area and return to base.

The fuel quantity system had been calibrated about 14 months before the accident, and postaccident examination of the airplane did not reveal any mechanical problems that would have resulted in premature fuel exhaustion. The pilot reported that he relied on his time and fuel consumption calculations instead of the cockpit fuel quantity gauge to determine the fuel remaining and his turnback time. His calculations were based on starting the flight with full fuel tanks, and a nominal flight-planning fuel consumption rate, neither of which could be verified after the accident. Postaccident calculated fuel consumption rates for the flight were in the same range as both recent historical data from the accident airplane and the manufacturer's published values.

Although the pilot could have used the fuel gauge in addition to his calculations to determine the remaining fuel, he chose not to. The more conservative risk management approach would have been to turn back to base when the fuel gauge reached the minimum value necessary to complete the flight safely. In addition, neither of the crewmembers explicitly determined and communicated a minimum fuel quantity value that mandated a return to base, and none of their guidance explicitly recommended or required them to do so.

Probable cause

A loss of power due to fuel exhaustion. Contributing to the accident were the pilot's failure to comply with required fueling procedures and the pilot's poor decision-making in not monitoring his fuel gauge and turning back when it reached minimum fuel.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12TA323
Event ID
20120723X90207
Case number
WPR12TA323
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2012-07-24.
  • API snapshot SHA-256: d01ecd29bc9d5c2683cc8e1b8fbf273efbb307645c6ad553086eb03699f5c622; retrieved 2026-09-15T19:03:51.190Z.