MKC82FA110 · Bellanca 17-30
Bellanca 17-30 · Accident: total loss of engine power (non-mechanical) en route
From Charles B. Wheeler Downtown Airport (MKC) to Spirit of St Louis Airport (SUS)
Event
- NTSB case
- MKC82FA110
- 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
- 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
Bellanca 17-30
- 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
- N6656V
- Operator
- John M. Lindhorst · private individual
- Onboard fatalities
- Unknown
- Route
- From Charles B. Wheeler Downtown Airport (MKC), Kansas City, MOTo Spirit of St Louis Airport (SUS), St. Louis, MO
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Total loss of engine power (non-mechanical)
- 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
- 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
- Fluid, fuel › Starvation
- Pilot in command › Fuel supply, inattentive
- Pilot in command › Fuel tank selector position, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT STATED HE DID NOT REFUEL OR VISUALLY VERIFY FUEL QUANTITY PRIOR TO DEPARTING KANSAS CITY. THE FLT TO ST. LOUIS WAS ON THE LEFT TANK. AS THE ACFT APPROACHED THE COLUMBIA, MO VOR AT AN ALTITUDE OF 3000 FT MSL THE ENG FAILED. THE PILOT STATED HE ESTABLISHED A GLIDE, CHANGED THE FUEL SELECTOR TO THE RIGHT TANK, FUSELAGE TANK, LEFT TANK, THEN RIGHT TANK. DURING THIS TIME HE WAS REQUIRED TO HOLD THE ELECT FUEL PUMP TO THE ON POSITION. THIS SWITCH IS SPRING LOADED TO THE OFF POSITION. HE WAS UNABLE TO RESTART THE ENG & SELECTED A GOLF COURSE FOR LANDING. HE TURNED DURING HIS APPROACH TO AVOID GOLFERS ON THE FAIRWAY & CRASHED ON A PAVED STREET. THE LEFT & FUSELAGE TANKS WERE EMPTY. THE RIGHT TANK CONTAINED ABOUT 4-5 INCHES OF FUEL. THE LEFT FUEL TANK QUANTITY SENDING UNIT WAS FOUND ERRATIC, PRODUCING AN INFINITE THEN ZERO RESISTANCE THROUGH ITS TRAVEL FROM FULL TO EMPTY.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MKC82FA110
- Event ID
- 20020917X03875
- Case number
- MKC82FA110
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 7af660d5923bc186af8bef02dfab4f19c54b387779975f0951e0f77db241911d; retrieved 2026-09-21T18:12:38.635Z.