FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14FA035 · Beech C90

1 Nov 2013 · Springdale, AR, United States

J&G Aviation Beech C90 · Accident: fuel exhaustion during an emergency descent

From Pine Bluff Regional Airport, Grider Field (KPBF) to Springdale Municipal Airport (KASG)

Report a problem

Event

NTSB case
CEN14FA035
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
2 · 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

Beech C90

Aircraft type
Beechcraft 90
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
N269JG
Operator
J&G Aviation
Onboard fatalities
Unknown
Route
From Pine Bluff Regional Airport, Grider Field (KPBF), Pine Bluff, ARTo Springdale Municipal Airport (KASG), Springdale, AR
Aircraft age
About 32 years (built 1981)
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
Emergency descent
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
Destroyed

Cause areas

  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision
  • 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

As the airplane was descending toward its destination airport, the pilot reported to an air traffic controller en route that he needed to change his destination to a closer airport because the airplane was low on fuel. The controller advised him to land at an airport that was 4 miles away. Shortly after, the pilot contacted the alternate airport's air traffic control tower (ATCT) and reported that he was low on fuel. The tower controller cleared the airplane to land, and, about 30 seconds later, the pilot advised that he was not going to make it to the airport. The airplane subsequently impacted a field 3.25 miles southeast of the airport. One witness reported hearing the engine sputter, and another witness reported that the engine "did not sound right." Forty-foot power lines crossed the field 311 feet from the point of impact. It is likely that the pilot was attempting to avoid the power lines during the forced landing and that the airplane then experienced an inadvertent stall and an uncontrolled collision with terrain.

About 1 quart of fuel was observed in each fuel tank. No evidence of fuel spillage was found on the ground; no fuel stains were observed on the undersides of the wing panels, wing trailing edges, or engine nacelles; and no fuel smell was observed at the accident site. However, the fuel totalizer showed that 123 gallons of fuel was remaining. Magnification of the annunciator panel light bulbs revealed that the left and right low fuel pressure annunciator lights were illuminated at the time of impact. An examination of the airframe and engines revealed no anomalies that would have precluded normal operation.

About 1 month before the accident, the pilot had instructed the fixed-base operator at Camden, Arkansas, to put 25 gallons of fuel in each wing tank; however, it is unknown how much fuel was already onboard the airplane. Although the fuel totalizer showed that the airplane had 123 gallons of fuel remaining at the time of the crash, information in the fuel totalizer is based on pilot inputs, and it is likely the pilot did not update the fuel totalizer properly before the accident flight. The pilot was likely relying on the fuel totalizer instead of the fuel gauges for fuel information, and he likely reported his low fuel situation to the ATCT after the annunciator lights illuminated.

Probable cause

A total loss of power to both engines due to fuel exhaustion. Also causal were the pilot’s reliance on the fuel totalizer rather than the fuel quantity gauges to determine the fuel on board and his improper fuel planning.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14FA035
Event ID
20131101X04142
Case number
CEN14FA035
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: cb189b95170766970362c0afd9454fbb9d66693448cf5908911c44a2e2e3e809; retrieved 2026-09-14T16:06:35.340Z.