CEN10FA007 · Beech 100
Beech 100 · Accident: fuel exhaustion en route
From Wiley Post Airport (PWA) to Fort Worth Meacham International Airport (FTW)
Event
- NTSB case
- CEN10FA007
- 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
- Visual Meteorological Cond
Beech 100
- Aircraft type
- Beechcraft 100
- 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
- N2TX
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wiley Post Airport (PWA), Oklahoma City, OKTo Fort Worth Meacham International Airport (FTW), Fort Worth, TX
- 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
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot added fuel to the multi-engine airplane prior to departure. While en route to the destination airport, the pilot noted that the fuel gauges indicated that the right main-tank appeared to be almost empty and the left tank appeared half full. The pilot initiated the crossfeed procedure in an effort to supply fuel to both engines from the left main tank. Shortly after beginning the crossfeed procedure, both engines experienced a total loss of power. The pilot notified air traffic control (ATC) and selected a field to perform a forced landing. Prior to touchdown, the right engine produced a surge of power and, in response, the airplane rolled to the left. The surge abruptly ended and the pilot continued the forced landing by lowering landing gear and extending the flaps. The airplane impacted the ground, coming to rest in an open field. A postimpact examination did not reveal any anomalies with the airframe or engine that would have precluded normal operation. Although both fuel tanks were ruptured, the accident scene did not contain a large amount of residual fuel. A small fuel slick was found on the surface of a nearby pond; however, the grass area underneath both wings did not contain dead grass; this would have been expected if there was more than a negligible amount of fuel in the tanks at time of impact.
Probable cause
The loss of engine power due to fuel exhaustion as a result of the pilot's inadequate fuel management.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10FA007
- Event ID
- 20091006X65657
- Case number
- CEN10FA007
- 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: aa36073fbabaa824c2989512f23fd4516dc5bd5efcb31b8c77eadcc3bda6ecd6; retrieved 2026-09-15T13:23:18.282Z.