FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN15FA060 · Bellanca 17-30A

30 Nov 2014 · Boonville, MO, United States

Bellanca 17-30A · Accident: fuel starvation on approach

From Spirit of St Louis Airport (SUS) to Charles B. Wheeler Downtown Airport (MKC)

Report a problem

Event

NTSB case
CEN15FA060
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

Bellanca 17-30A

Aircraft type
Bellanca 17
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
N6629V
Operator
Unknown
Onboard fatalities
Unknown
Route
From Spirit of St Louis Airport (SUS), Chesterfield, MOTo Charles B. Wheeler Downtown Airport (MKC), Kansas City, MO
Aircraft age
About 44 years (built 1970)
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
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
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Task performance

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

NTSB narrative

The commercial pilot was on a cross-country flight when the airplane encountered deteriorating weather conditions. A surviving passenger reported that the pilot decided to divert to a nearby airport. The airplane experienced a loss of engine power in the airport traffic pattern shortly after the pilot extended the landing gear during the base-to-final turn. The pilot was able to restore engine power briefly by advancing the throttle, but the engine quickly experienced a total loss of power. The passenger stated that the airplane entered an aerodynamic stall about 250 ft above the ground. The airplane subsequently impacted terrain in a near-level attitude. The pilot likely failed to maintain adequate airspeed following the loss of engine power, which resulted in the airplane exceeding its critical angle of attack and a subsequent aerodynamic stall at a low altitude.

A postaccident examination did not reveal any mechanical malfunctions that would have precluded normal engine operation; however, the right main fuel tank was void of any usable fuel, and the left main fuel tank contained about 1.5 gallons of usable fuel. Additionally, no fuel was recovered from the supply line connected to the fuel manifold valve, and only trace amounts of fuel were recovered from the engine-driven fuel pump outflow line. A first responder reported that the main fuel selector was positioned to draw fuel from the auxiliary fuel tanks. Although placarded for use during level flight only, both auxiliary fuel tanks contained sufficient fuel to maintain coverage over their respective outlet ports during maneuvering flight, and would have provided fuel to the engine. As such, it is likely that the main fuel selector was positioned to draw fuel from the right main fuel tank when the airplane initially experienced a loss of engine power due to fuel starvation. The pilot then likely switched to the right auxiliary fuel tank while attempting to restore engine power; however, there was likely insufficient time and altitude to re-establish fuel flow to the engine.

Although the airplane had experienced an alternator malfunction during the previous flight, a possible charging system failure would not have affected engine operation during the accident flight.

Probable cause

The pilot's failure to maintain adequate airspeed during a forced landing following a total loss of engine power due to fuel starvation, which resulted in the airplane exceeding its critical angle of attack, and an aerodynamic stall at a low altitude. Contributing to the accident was the pilot’s improper fuel management.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN15FA060
Event ID
20141130X22258
Case number
CEN15FA060
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: c8ab96fd692bd11156253563bdcebfa7b957fa851c11c42878f97dbc2cb3b63a; retrieved 2026-09-14T17:29:12.500Z.