FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17LA190 · Beech M35

29 Aug 2017 · Lake Havasu City, AZ, United States

Beech M35 · Accident: fuel starvation on approach

From Hemet Ryan Airport (HMT) to Lake Havasu City Airport (HII)

Report a problem

Event

NTSB case
WPR17LA190
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 M35

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
N339Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hemet Ryan Airport (HMT), Hemet, CATo Lake Havasu City Airport (HII), Lake Havasu City, AZ
Aircraft age
About 57 years (built 1960)
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
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 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

  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The pilot was conducting a personal cross-country flight. The fuel selector was set to the left main fuel tank for takeoff and climbout. After reaching cruise altitude, he switched to the auxiliary tanks and later to the right main fuel tank. While in cruise flight, he also activated the two fuel pumps to transfer fuel from the tip tanks to the main tanks. When the airplane was about 4 miles from and 2,000 ft above the intended destination airport, the pilot switched to the left main fuel tank; the fuel-injected engine lost power, but the propeller continued to windmill. The pilot selected the landing gear down and attempted to restart the engine to no avail. The pilot determined that he would not make the runway and selected an open area as his landing target. He switched to the right main fuel tank, but the propeller continued only to windmill. The pilot then switched back to the left main tank and again could not start the engine. The airplane landed hard on flat desert terrain, which resulted in the nose landing gear collapsing and the fuselage buckling. The airplane slid upright to a stop.

On-site examination of the fuel tanks revealed that they were not breached; the left main fuel tank contained about 23 gallons of fuel, the right main tank contained about 20 gallons, and the auxiliary tanks and the tip tanks did not contain any fuel. Examination of the fuel system did not reveal any obvious reason for the engine power loss. Although the left main tank fuel pickup screen was found separated from its line, the line appeared clear and functional. The ports and chambers of the fuel selector valve were clear, and the valve was functional. The fuel selector valve handle position detents were worn so that proper selection of a fuel tank by tactile method alone was difficult or impossible, and the placard was worn to the point where the position marker for the left tank was absent. The engine was removed for examination and a test run, and there was no evidence of a mechanical anomaly that would have precluded normal operation.

Based on the pilot's reported sequence of events, the airplane examination, and the engine test run, it is likely that the pilot did not correctly position the fuel selector valve handle when he switched to the left tank for landing, which resulted in fuel flow interruption and power loss due to fuel starvation. The worn condition of the fuel selector valve made it susceptible to being mis-set, which would impede or terminate fuel flow to the engine. In addition, a fuel-injected engine can be more difficult and/or take longer to start after it is deprived of fuel. Due to the airplane's proximity to the ground, the pilot had limited time to troubleshoot or restart the engine.

Probable cause

The pilot's incorrect positioning of the fuel tank selector valve during a tank switch, which resulted in fuel starvation and a loss of engine power. Contributing to the accident was the worn condition of the fuel selector valve handle position detents and markings.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17LA190
Event ID
20170829X10731
Case number
WPR17LA190
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. 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: d954acd08015180333a542deb892c39d985115f0bf9c55116f4cbb8ef2db9e33; retrieved 2026-09-16T05:46:26.423Z.