CEN20LA380 · Beech 35 G35
Beech 35 G35 · Accident en route
From Fort Stockton Pecos County Airport (FST) to Canyon Lake Airport (34TS)
Event
- NTSB case
- CEN20LA380
- 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 35 G35
- 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
- N4636D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fort Stockton Pecos County Airport (FST), Fort Stockton, TXTo Canyon Lake Airport (34TS), Canyon Lake, TX
- Aircraft age
- About 64 years (built 1956)
- 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
- 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
- Unknown or undetermined
- 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
- Tree(s)
- 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 › Aircraft power plant
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the airplane’s engine lost all power shortly after he switched fuel tanks in preparation for landing. Attempts to restart, which included selecting the other fuel tanks, were unsuccessful. The airplane was damaged when it struck trees and terrain during the subsequent forced landing.
Postaccident examination of the airplane’s engine and fuel system failed to reveal a reason for the reported loss of engine power.
Based on available evidence, the accident was the result of a total loss of engine power for a reason that could not be determined based on available information.
Probable cause
The total loss of engine power for a reason that could not be determined based on available information.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20LA380
- Event ID
- 20200907X52020
- Case number
- CEN20LA380
- 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, 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: 275419e27a8e9f790fa613c7f64024c9252ba194ab4f15aaa83c059b770eb788; retrieved 2026-09-16T13:00:09.963Z.