CEN19FA236 · Beech 95B55 T42A
Beech 95B55 T42A · Accident: fuel exhaustion on approach
From Fond du Lac County Airport (FLD) to Chadron Municipal Airport (CDR)
Event
- NTSB case
- CEN19FA236
- 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
- 3 · 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 95B55 T42A
- Aircraft type
- Beechcraft 55
- 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
- N8910U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fond du Lac County Airport (FLD), Fond Du Lac, WITo Chadron Municipal Airport (CDR), Chadron, NE
- Aircraft age
- About 54 years (built 1965)
- 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 · VFR pattern final
- 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, not marked as estimated; no uncertainty radius is established.
NTSB narrative
After a 10-minute engine-running ground delay, the pilot and two passengers departed on a 640 nautical mile (nm) cross-country flight in a multiengine airplane. A witness at the destination airport reported that the airplane entered the traffic pattern and was turning on a left base leg when the airplane nosed straight down and did not pull up. Another witness near the accident site reported that she heard an engine “sputter” as if it lost power. The airplane descended into a tree line and impacted the ground 0.25 nm north of the intended runway.
Postaccident examination of the wreckage revealed that the propeller blades for both engines did not exhibit any rotational signatures, which is consistent with the engines not producing power at the time of impact. Disassembly and examination of each engine did not reveal any mechanical malfunctions that would have precluded normal operation.
Further examination revealed that the airplane’s fuel tanks were all breached, and there was no odor of fuel at the accident site and no fuel blighting around the wreckage. The fuel system contained a minimal amount of fuel. The fuel quantity transmitters, were which likely original to the airplane, were measured for proper resistance during range of travel; of the 19 different electrical resistance checks, only 3 were within the manufacturer’s specified limits. The fuel transmitters with improper resistances would have likely provided false readings to the fuel gauges. The airplane’s maintenance records did not contain any logbook entries related to the fuel gauges or transmitters.
In addition, the airplane’s fuel flow indicator, which required the pilot to input the initial fuel amount on board the airplane, had sustained extensive damage; thus, its preaccident operating condition could not be determined, and it did provide reliable information. If the pilot was using the fuel flow indicator as the main fuel quantity indication and input the wrong amount of fuel into the unit before takeoff, then he would have had inaccurate fuel quantity indication throughout the flight.
The pilot’s flight planning navigation logs show that he intended to depart with 134 gallons of fuel, which should have been adequate, even with the ground delay before departure, to reach the destination airport. The airplane was fueled 2 days before departure; the line service employee who fueled the airplane had noted that the auxiliary tanks were already full and stated that the pilot likely wasn’t present for the fueling. Based on the available evidence, it is likely that the pilot did not verify the fuel quantity before he departed on the accident flight and departed with less fuel than he had planned for, which resulted in a total loss of engine power due to fuel exhaustion.
Probable cause
The pilot's failure to ensure adequate fuel was on board before departing and his in-flight fuel management, 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 CEN19FA236
- Event ID
- 20190724X83313
- Case number
- CEN19FA236
- 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: d04a3e41eb2b780ec059ec806b14b891a190da66560d9a5ee75ec5a43c4c2a0b; retrieved 2026-09-15T07:02:23.742Z.