FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI93LA360 · Beech 35

11 Sept 1993 · Marshfield, MO, United States

Beech 35 · Accident: total loss of engine power (non-mechanical) en route

From Quincy Regional Airport Baldwin Field (UIN) to Texarkana Regional Airport (Webb Field) (TXK)

Report a problem

Event

NTSB case
CHI93LA360
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 35

Aircraft type
Beechcraft 35
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
N650V
Operator
Unknown
Onboard fatalities
Unknown
Route
From Quincy Regional Airport Baldwin Field (UIN), Quincy, ILTo Texarkana Regional Airport (Webb Field) (TXK), Texarkana, AR
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 · cruise
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 starvation
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

  • Fuel system, selector/valve › Failure, total

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE FLIGHT ORIGINATED AT WAUNAKEE, WISCONSIN, AND HAD AN INTENDED DESTINATION OF TEXARKANA, ARKANSAS. THE PILOT MADE AN INTERMEDIATE STOP IN QUINCY, ILLINOIS, AND TOPPED OFF BOTH FUEL TANKS. EN ROUTE FROM QUINCY TO TEXARKANA, THE PILOT ATTEMPTED TO SWITCH FROM THE RIGHT TO THE LEFT FUEL TANKS, AND THE FUEL TANK SELECTOR HANDLE BROKE OFF. THE ENGINE EXPERIENCED A LOSS OF POWER DUE TO FUEL STARVATION. THE PILOT MADE A FORCED LANDING IN A FIELD NEAR MARSHFIELD, MISSOURI. THE AIRPLANE STRUCK A PARKED SNOW PLOW DURING LANDING ROLL.

Probable cause

fuel exhaustion due to the failure of the fuel tank selector valve handle which prohibited the pilot from switching to a tank containing fuel.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI93LA360
Event ID
20001211X13373
Case number
CHI93LA360
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: 508b843435f29016283f2b74869a962f9a0463d47b102b8dca8a6a6f199397c5; retrieved 2026-09-21T22:48:50.869Z.