FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN16FA011 · Beech G35

13 Oct 2015 · Eaton, CO, United States

Beech G35 · Accident: loss of control in flight on approach

From Lyons-Rice County Municipal Airport (LYO) to Greeley–Weld County Airport (GXY)

Report a problem

Event

NTSB case
CEN16FA011
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
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 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
N394CW
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lyons-Rice County Municipal Airport (LYO), Lyons, KSTo Greeley–Weld County Airport (GXY), Greeley, CO
Aircraft age
About 59 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
Approach
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 control in flight
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 › Fluids/miscellaneous hardware
  • Personnel issues › Task performance

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

NTSB narrative

The commercial-rated pilot and passenger (who owned the airplane) were conducting a cross-country business flight. Several witnesses reported observing the accident airplane overhead; one witness stated that the engine made a "sputtering" sound like it was running out of gas. She stated that airplane was flying north and then turned west when it began to "nose dive" out of sight. A review of the radar data revealed that the airplane approached the destination airport from the southeast and proceeded north, tracking above the runway about 400 ft above ground level (agl). The airplane then climbed to 900 ft agl and continued northbound. About 8 miles north of the destination airport, the airplane was about 1,100 ft agl and then entered a left turn and descended. The last radar point showed the airplane on a southwest heading and about 350 ft agl. The airplane impacted the ground with its left wing low, cartwheeled to the right, and came to rest upright in a harvested corn field. The main wreckage was found about 460 ft southwest of the last radar point.

The accident airplane likely encountered low-level wind shear and clear air turbulence and a wind shift that switched from a gusting headwind to a gusting tailwind in a short amount of time.

The right main fuel tank, which the selector valve indicated was selected at the time of the accident, was found empty and was not breached. The engine carburetor did not contain any fuel. A postaccident examination of the engine and airframe did not reveal any preimpact mechanical malfunctions or anomalies that would have precluded normal operation.

The pilot reported that the main tanks were full and the tip tanks were empty, so it is likely that the airplane contained 60 gallons of fuel before departure. The radar data revealed that the accident flight was 3 hours 16 and minutes long. Based on the accident flight, the engine would have consumed about 40 gallons of fuel from initial taxi to the accident site. This should have left about 20 gallons remaining in the tanks, which would have been enough to fly to the destination airport in addition to reserve fuel. The accident airplane was equipped with a single fuel quantity indicator gauge for the six fuel tanks; only one tank could be monitored at any given time. Switches on the instrument panel allowed the pilot to select which tank to monitor on the gauge. The pilot and airplane's new owner had limited experience in the airplane and with the airplane fuel indicating system, so they likely had the fuel indicator selected to another fuel tank and did not appropriately monitor the level of fuel in the right main tank, which was selected to feed the engine. Based on witness statements and the evidence obtained on-scene, it is likely that the engine was starved of available fuel. Once engine power was lost, the pilot then failed to maintain control of the airplane while flying in gusting wind and low-level wind shear conditions.

Probable cause

The pilot's loss of airplane control in gusting wind conditions and low-level wind shear, following a loss of engine power due to fuel starvation. Contributing to the accident was the pilot’s failure to properly monitor the fuel level inflight because of his unfamiliarity with the fuel system.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN16FA011
Event ID
20151013X50647
Case number
CEN16FA011
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: fa2075302d902ae4315c222428c298efc185ef0c0588cde30f458e1556a1bd7e; retrieved 2026-09-14T21:32:42.146Z.