MKC83FA214 · Beech C35
Beech C35 · Accident: total loss of engine power (non-mechanical) on approach
From Charles B. Wheeler Downtown Airport (MKC) to an unrecorded destination
Event
- NTSB case
- MKC83FA214
- 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
Beech C35
- 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
- N5843C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Charles B. Wheeler Downtown Airport (MKC), Kansas City, MOTo not recorded
- 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
- Approach · VFR pattern final
- 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 system, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT REPORTED THAT WHEN HE WAS ON FINAL APCH TO LAND, THE ENG QUIT RUNNING & HE WAS UNABLE TO GLIDE TO THE RWY. REPORTEDLY, THE ACFT TOUCHED DOWN IN A VACANT LOT ABOUT 75 FT SHORT & 15 FT BELOW THE LEVEL OF THE END OF THE RWY. AFTER TOUCHING DOWN, IT CONTINUED ACROSS A DITCH, A ROAD, ANOTHER DITCH, WENT THRU A BARBED WIRE FENCE, CONTINUED UP A BANK & STOPPED AT THE APCH END OF THE RWY. AN EXAM OF THE ACFT REVEALED THERE WS APRX 5 GAL OF FUEL REMAINING IN THE RIGHT FUEL TANK, BUT ONLY ABOUT 3/4 OF A PINT IN THE LEFT TANK. THE FUEL SELECTOR WAS FOUND POSITIONED TO THE LEFT TANK & THE FUEL QUANTITY GAGE WAS SWITCHED TO THE RIGHT TANK. ALL FUEL LINES WERE INTACT & ALL CONNECTIONS WERE TIGHT. NO EVIDENCE OF FUEL SIPHONING WAS FOUND. ALSO, THE ENG RAN SATISFACTORILY DURING AN OPERATIONAL CHECK AFTER THE ACCIDENT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MKC83FA214
- Event ID
- 20001214X44638
- Case number
- MKC83FA214
- 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: 81d9a5407d561de5d70dd1dd85e6aad01502ce1c6af823e37e786528062fa3ea; retrieved 2026-09-21T17:47:49.859Z.