LAX98LA136 · Beech M35
Beech M35 · Accident: total loss of engine power (non-mechanical) on approach
From Jack Northrop Field Hawthorne Municipal Airport (HHR) to North Las Vegas Airport (VGT)
Event
- NTSB case
- LAX98LA136
- 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 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
- N9703R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jack Northrop Field Hawthorne Municipal Airport (HHR), Hawthorne, CATo North Las Vegas Airport (VGT), NV
- 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 management, improper
- Pilot in command › Fuel supply, not selected
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While on approach to the destination airport from a cross-country flight, the tower instructed the pilot to turn left to a downwind for landing. After completing the left turn the engine quit about pattern altitude. The pilot reported that he switched tanks several times in an unsuccessful attempt to get a restart. The fuel selector was found in the auxiliary fuel tank position. Recovery personnel removed about 18 gallons of fuel from the right fuel tanks, 2 gallons from the auxiliary and 16 from the right main tank. The left fuel tanks were ruptured. The estimated flight time from departure to North Las Vegas is 1.5 hours, and according to the engine manufacturer, the estimated fuel consumption at 75 percent power would be 24.375 gallons for that time.
Probable cause
fuel starvation due to the pilot's improper fuel management and his failure to select the fullest tank for landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX98LA136
- Event ID
- 20001211X09889
- Case number
- LAX98LA136
- 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: 27b2e09385621f28623551010117167faf5e9eff97b6fc3520c2ebea40a4c5d1; retrieved 2026-09-21T20:52:01.820Z.