CEN15FA374 · Beech 35 B33
Beech 35 B33 · Accident: loss of engine power (total) on approach
From Florence Regional Airport (FLO) to Memorial Field Airport (HOT)
Event
- NTSB case
- CEN15FA374
- 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 35 B33
- 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
- N9704Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Florence Regional Airport (FLO), Florence, SCTo Memorial Field Airport (HOT), Hot Springs, AR
- Aircraft age
- About 52 years (built 1963)
- 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 final
- 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
- Loss of engine power (total)
- 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 › Aircraft oper/perf/capability
- Not determined › Not determined
- 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 private pilot was conducting a cross-country flight and had departed about 5.5 hours before the accident. The pilot originally filed a flight plan that covered 689 nautical miles (nm); however, he had to divert because of weather, so he changed his destination airport. When he neared the destination, he was cleared for the RNAV/GPS runway 4 approach and reported that he had the airport in sight. The total distance traveled was 722 nm. A witness stated that the pilot reported that he intended to circle for an approach to runway 31 and that he saw the airplane circling south of the airport. Shortly thereafter, the airplane impacted trees and terrain in an inverted, nose-down attitude, and the airplane's cabin was almost completely consumed by a postimpact fire.
A postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. Additionally, the propeller and propeller spinner damage was consistent with no engine rotation during the impact.
The airplane was equipped with two fuel tanks, one in each wing, and a fuel selector with positions for selecting the left or right fuel tank with an additional position for turning off the fuel flow. There was no position available for drawing fuel from both tanks simultaneously. The fuel selector valve was not observed, and the determination of which tank was selected could not be determined. Although the departure fuel quantity could not be determined, calculations indicated that, if the airplane had full fuel tanks at the time of departure, it would have had an endurance of about 6.5 hours with an additional 45 minutes reserve fuel capacity at a reduced power setting. It could not be determined how much fuel was onboard the airplane at the time of the impact.
A weather system was approaching the airport at the time of the accident, and lightning was recorded in the distance. It is possible that the pilot became distracted during the instrument approach by the approaching weather system and may not have selected the fullest fuel tank for the approach. This could have led to fuel starvation and a loss of engine power while he was maneuvering to land. Because the quantity of fuel before takeoff or the quantity remaining in each fuel tank at the accident site could not be determined, a loss of power due to fuel exhaustion could not be ruled out. Based on the available evidence, the engine lost power for a reason that could not be determined. Subsequently, the pilot likely attempted to extend the airplane's glide to reach the runway and exceeded its critical angle-of-attack, which resulted in an aerodynamic stall and loss of control.
Probable cause
The loss of engine power for reasons that could not be determined during postaccident examination of the accident site or based on the available information and the pilot's failure to maintain adequate airspeed and his exceedance of the airplane's critical angle-of-attack after the engine power loss, which led to an aerodynamic stall and loss of control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN15FA374
- Event ID
- 20150823X51533
- Case number
- CEN15FA374
- 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. 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: 4348ddeb0be0f43800bf55d16929aea971b7d2de1234edc20d72061c301e6d4b; retrieved 2026-09-14T21:29:00.958Z.