FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13CA373 · Beech 200

25 Jun 2013 · Wheeling, IL, United States

Tennair Beech 200 · Accident: fuel exhaustion on approach

From Springfield Robertson County Airport (M91) to Chicago Executive Airport (PWK)

Report a problem

Event

NTSB case
CEN13CA373
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
0
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 200

Aircraft type
Beechcraft 200
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
N92JR
Operator
Tennair
Onboard fatalities
Unknown
Route
From Springfield Robertson County Airport (M91), Springfield, TNTo Chicago Executive Airport (PWK), Wheeling, IL
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
Approach · IFR final 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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Before departure, the pilot performed fuel calculations and determined that he had enough fuel to fly to the intended destination. While enroute the pilot flew around thunderstorms. On arrival at his destination, the pilot executed the instrument landing system approach for runway 16. While on short final the right engine experienced a total loss of power. The pilot switched the fuel flow from the right tank to the left tank. The left engine then experienced a total loss of power and the pilot made an emergency landing on a road. The airplane received substantial damage to the wings and fuselage when it struck a tree. A postaccident examination revealed only a few gallons of unusable fuel in the left fuel tank. The right fuel tank was breached during the accident sequence but no fuel smell was noticed. The pilot performed another fuel calculation after the accident and determined that there were actually 170 gallons of fuel onboard, not 230 gallons like he originally figured. He reported no preaccident mechanical malfunctions that would have precluded normal operation and determined that he exhausted his entire fuel supply.

Probable cause

The pilot's improper fuel planning and management, which resulted in a loss of engine power due to fuel exhaustion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13CA373
Event ID
20130626X21452
Case number
CEN13CA373
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 2013-06-26.
  • API snapshot SHA-256: c5d8a44b63fc15835278103e49c094fb514b9e8fde97565e0da6f4b4174214fd; retrieved 2026-09-15T22:00:22.400Z.