BFO93LA064 · Beech E18S
Skydive Greene Beech E18S · Accident: total loss of engine power (non-mechanical) during initial climb
From I20 to an unrecorded destination
Event
- NTSB case
- BFO93LA064
- 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 E18S
- Aircraft type
- Beechcraft 18
- 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
- N665M
- Operator
- Skydive Greene
- Onboard fatalities
- Unknown
- Route
- From I20To not recorded
- 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
- Initial climb
- First occurrenceThe 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
- Total loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. 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
- Fluid, fuel › Exhaustion
- Pilot in command › Aircraft preflight, inadequate
- Pilot in command › Fuel supply, inadequate
Approximate · Estimated position: the centre of Xenia, OH, the place the record names. Not the accident site.
NTSB narrative
SHORTLY AFTER TAKEOFF, BOTH ENGINES LOST POWER. THE PILOT SAID HE SELECTED DIFFERENT FUEL TANKS, BUT COULD NOT RESTART THE ENGINES. HE SUBSEQUENTLY MADE A WHEELS-UP FORCED LANDING IN A FIELD BELOW HIS FLIGHT PATH. THE PILOT STATED THAT HE HAD PERFORMED A PREFLIGHT INSPECTION AND THAT THERE WAS 4.1 GALS IN BOTH THE FRONT LEFT AND RIGHT MAIN FUEL TANKS. EXAMINATION OF THE AIRPLANE AFTER THE ACCIDENT REVEALED A COMBINED TOTAL OF ABOUT 5 GALS IN THE FORWARD LEFT AND RIGHT TANKS. THE OTHER FOUR TANKS WERE EMPTY. THE PILOT STATED THAT HE HAD LOST TRACK OF THE FLIGHTS FLOWN THAT DAY AND DID NOT VISUALLY CHECK THE FUEL. HE ALSO STATED THAT HE '...RAN THE AIRPLANE OUT OF FUEL.' ACCORDING TO BEECH, ALL FUEL IN THE AIRPLANE IS USABLE EXCEPT FOR A COMBINED 6 GALS IN THE LEFT AND RIGHT FORWARD TANKS.
Probable cause
INADEQUATE PREFLIGHT BY THE PILOT, WHICH RESULTED IN FUEL EXHAUSTION DUE TO AN INADEQUATE SUPPLY OF FUEL.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO93LA064
- Event ID
- 20001211X12296
- Case number
- BFO93LA064
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: f928e3cc89633a48b553cd3bde4b4bb935d7713d260f38e150beec84e98bc433; retrieved 2026-09-23T02:08:39.397Z.