CEN23FA074 · Beech M35
Beech M35 · Accident: fuel starvation on approach
From Stuttgart Municipal Airport / Carl Humphrey Field (SGT) to Drake Field (FYV)
Event
- NTSB case
- CEN23FA074
- 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
- 1 · 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
- N673V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Stuttgart Municipal Airport / Carl Humphrey Field (SGT), Stuttgart, ARTo Drake Field (FYV), Fayetteville, AR
- Aircraft age
- About 63 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 · VFR pattern downwind
- 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
- Destroyed
Cause areas
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot departed on the first leg of the trip with the airplane fully fueled and two passengers onboard. After about an hour flight, the pilot landed at the destination airport and dropped off both passengers. The airplane was not fueled at that time. The pilot departed as the sole occupant to return to the initial airport. About 18 miles from the destination airport, the airplane entered a gradual descent as it remained on course. About 6 minutes later, the airplane entered a descending left turn that continued until the available position data ended. The airplane impacted trees and terrain about 3 miles from the airport. The accident site was in a wooded area adjoining an open field. A witness heard the airplane as it approached and recalled that the engine sounded as if it was going to lose power but then “revved up really high.” This cycle occurred 3 or 4 times over a span of 10 – 15 seconds. The engine then seemed to stop; however, he was unsure if the airplane had descended behind a ridgeline. He did not hear the impact nor was he able to see the airplane. Postaccident airframe and engine examinations did not reveal any preaccident mechanical malfunctions or failures that would have precluded normal operation. The airplane was equipped with 2 25-gallon main fuel tanks and 2 10-gallon auxiliary fuel tanks. The fuel selector valve had settings for the left main tank, the right main tank, and the auxiliary tanks. The main fuel tanks were selected individually. Both auxiliary tanks fed simultaneously when selected. Excess (unburned) fuel from the engine was returned to the selected main fuel tank or, if the auxiliary tanks were selected, to the left main fuel tank. The fuel tank caps were securely installed, and each tank appeared to be intact. About 15 gallons and 10 gallons of fuel were recovered from the left and right main fuel tanks, respectively. Both the left and right auxiliary fuel tanks contained minimal fuel. Data recovered from an onboard electronic engine display unit revealed that the pilot departed on the initial leg of the trip with the left fuel main fuel tank selected. About midflight, the pilot changed to the auxiliary fuel tanks. Upon departure on the accident flight, the pilot had the right main fuel tank selected. About 14 minutes before the accident, the pilot selected the auxiliary fuel tanks to supply the engine. About 2 minutes before the accident, the useable fuel contained in the auxiliary tanks was exhausted, and the engine lost power due to fuel starvation. The pilot most likely selected the left main fuel tank in an effort to restore engine power. Useable fuel was available in both the left and right main fuel tanks when the engine lost power. The pilot was likely maneuvering toward an open field for a forced landing under a clear night sky and rising full moon. However, the airplane did not have sufficient altitude to reach the field. It could not be determined whether the night lighting conditions hindered the pilot’s attempted forced landing.
Probable cause
The pilot’s mismanagement of the airplane’s fuel system, which resulted in fuel starvation and a loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23FA074
- Event ID
- 20230107106548
- Case number
- CEN23FA074
- 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, coordinates, cause areas. 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: 63f16db7a234bfc723966fe300961b560955a24bcb9ea6311a1af2d438a1f799; retrieved 2026-09-15T07:55:49.631Z.