FTW97LA149 · Beech D35
Beech D35 · Accident: total loss of engine power (non-mechanical) on approach
From Tulsa Riverside Airport (RVS) to Bartlesville Municipal Airport (BVO)
Event
- NTSB case
- FTW97LA149
- 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 D35
- 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
- N940MD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tulsa Riverside Airport (RVS), Tulsa, OKTo Bartlesville Municipal Airport (BVO)
- 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 · VFR pattern downwind
- 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
- Fluid, fuel › Starvation
- Pilot in command › Fuel tank selector position, improper
Approximate · Estimated position: the centre of Bartlesville, OK, the place the record names. Not the accident site.
NTSB narrative
While en route, the owner/pilot switched the fuel selector to the right fuel tank, and observed that the fuel gauge indicated about 1/2 full. During a downwind entry for the runway, the engine sputtered and lost power. A forced landing was made in a field west of the runway. During the landing flare, the left wing struck the ground, then the nose hit. An FAA inspector reported that the pilot had positioned the fuel selector to the right tank; however, he had left the fuel tank indicator (gauge) at the left tank position. The gauge was indicating 1/2 full, and the left fuel tank was about 1/2 full. The right fuel tank was empty. The pilot had recently purchased the airplane and was not familiar with the fuel indicator gauge switch, which had to be positioned to the fuel tank being used in order to indicate fuel remaining in that tank.
Probable cause
the pilot's selection of an empty fuel tank, which resulted in fuel starvation and loss of engine power. A factor relating to the accident was: the pilot's lack of familiarity with the aircraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW97LA149
- Event ID
- 20001208X07703
- Case number
- FTW97LA149
- 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: 4fbf611ddb23619eee1ac49d871c6f0f632918814b68b8973f280006322f0342; retrieved 2026-09-21T21:28:51.054Z.