FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN15FA316 · Beech V35B B

26 Jul 2015 · Colbert, OK, United States

Beech V35B B · Accident: loss of engine power (total) en route

From Jackson County Airport/Reynolds Field (JXN) to Fort Worth Spinks Airport (FWS)

Report a problem

Event

NTSB case
CEN15FA316
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
2 · 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 V35B B

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
N252G
Operator
Unknown
Onboard fatalities
Unknown
Route
From Jackson County Airport/Reynolds Field (JXN), Jackson, MITo Fort Worth Spinks Airport (FWS), Fort Worth, TX
Aircraft age
About 36 years (built 1979)
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 · cruise
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
Substantial

Cause areas

  • Aircraft › Aircraft systems
  • Personnel issues › Task performance

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

NTSB narrative

The airplane was in level cruise flight on the second leg of a cross-country flight when the engine lost power. The pilot declared an emergency with air traffic control (ATC) and requested the nearest airport. As the airplane was descending through 8,360 ft mean sea level (msl), the ATC controller told him that there was an airport (Airport A) at his 12-o'clock position and about 15 nautical miles (nm) away. However, there was another airport (Airport B) that was about 7.5 nm away that the controller did not tell the pilot about at this time.

The pilot responded that he had partial power and would see if he could make it to Airport A. He then asked for and received a vector to Airport A. About 2 minutes later, as the airplane descended through 6,023 ft msl, the pilot asked the controller if there was something closer, and the controller told him that there was another airport (Airport B) at his 3- to 4-o'clock position and 10 nm away. The pilot requested a turn toward Airport B, the controller told the pilot to turn right and proceed direct, and the airplane turned 90° right toward Airport B. Airport B was actually about 8.2 nm away.

About 2 minutes later, as the airplane descended through 4,260 ft msl, the controller advised the pilot that there was a private airstrip about 1 mile behind him. The airstrip was actually 10 nm away. The pilot replied, "wish I knew where that was ..." The controller then provided the pilot with runway information for Airport B. The pilot responded, "where's that private strip?" The controller responded, "it's not close enough for you to get to." As the airplane descended through 3,370 ft msl, the controller then gave the pilot his position and distance to Airports A and B. There were no further transmissions from the pilot.

Radar data showed that the airplane made a 180° right turn to the south. About 2 minutes later, the airplane made a 270° left turn and rolled out on a westerly heading. At the last radar contact, the airplane was westbound at 700 ft msl. The terrain elevation in the area was about 660 ft msl. The airplane impacted trees and then the ground. The site was surrounded by fields suitable for a forced landing, and it is likely that if the pilot had selected one of these fields as his landing site, the damage to the airplane and severity of injuries to the occupants would have been minimized.

Postaccident examination revealed that the left fuel tank was full, and the fuel quantity in the right tank could not be determined due to impact damage. The fuel selector valve handle was positioned between the left and right tank detent positions. Fuel selector continuity was established for each detent by blowing air through the valve. No air flowed through the valve when the fuel selector was positioned as found between the right and left tank detents. No preimpact failures or malfunctions with the airframe or engine were found that would have precluded normal operation.

The pilot's autopsy revealed that he had severe coronary heart disease including atherosclerosis of the coronary arteries. The posterior descending coronary artery was found to have about 90% stenosis and the left main, left anterior descending, and right coronary arteries had about 25% stenosis. Given that there was active radio contact between the pilot and ATC and no mention by the pilot of chest pain, shortness of breath, weakness, or palpitations, it is unlikely that his heart disease contributed to the accident.

Toxicology tests showed the pilot used rosuvastatin, a prescription medication in the class of medications called statin antilipemic agents that is used to reduce blood cholesterol and triglyceride levels. The rosuvastatin was found in the pilot's urine but not in his blood.

It is likely that while switching tanks during cruise flight, the pilot inadvertently moved the fuel selector to the as-found intermediate position such that it blocked fuel to the engine, which resulted in fuel starvation and a loss of engine power. The Pilot's Operating Handbook (POH) listed "Fuel Selector Valve – SELECT OTHER TANK (Check to feel detent)" as the first item in the emergency procedure for an engine failure. Thus, it is likely that, when the engine lost power, the pilot failed to properly position the selector so that fuel could be restored and a restart possible.

At the time that the pilot reported the engine failure to ATC, the airplane was 15.8 nm from Airport A, 7.5 nm from Airport B, and 6.2 nm from the private airstrip. According to radar data, the airplane traveled a total distance of about 7.9 nm from the point at which the pilot reported the engine failure to the accident site. The POH states that, with the landing gear and flaps retracted, cowl flaps closed, propeller at low rpm, and maintaining an airspeed of 105 kts, the airplane's glide distance is about 1.7 nm per 1,000 ft of altitude above the terrain. If the controller had provided accurate information to the pilot about the location of the nearest airports as required by Federal Aviation Administration ATC procedures and if the pilot had immediately acted on that information, based on the radar data, the pilot might have been able to glide to and land at Airport B or the private airstrip.

Probable cause

The pilot's failure to properly position the fuel selector, which resulted in a total loss of engine power due to fuel starvation. Contributing to the severity of the accident was the pilot's failure to select an appropriate location for a forced landing, which resulted in the airplane impacting trees. Contributing to the accident was the air traffic controller's failure to provide the pilot accurate information on nearby emergency airport and airfields and the pilot's failure to properly follow the airplane's emergency procedures in the Pilot's Operating Handbook that would have led him to properly position the fuel selector and restore fuel flow to the engine.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN15FA316
Event ID
20150726X81208
Case number
CEN15FA316
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: 401ca23cb688afb75e075ea27a2df6e6fbcff5c1912971779cf19c74ea5dfa36; retrieved 2026-09-14T19:46:28.016Z.