CHI90LA157 · Beech K-35
Beech K-35 · Accident: total loss of engine power (non-mechanical) en route
From Kenosha Regional Airport (ENW) to Manitowish Waters Airport (D25)
Event
- NTSB case
- CHI90LA157
- 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 K-35
- Aircraft type
- Beechcraft K-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
- N123AT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Kenosha Regional Airport (ENW), Kenosha, WITo Manitowish Waters Airport (D25), MANITOWISH, WI
- 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
- Pilot in command › Fuel tank selector position, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS EN ROUTE AT 4,000 FEET MSL ON CROSS COUNTRY FLIGHT WHEN HE EXPERIENCED TOTAL LOSS OF POWER. THE PILOT STATED THAT HE SWITCHED TANKS BUT COULD NOT RESTART THE ENGINE. HE MADE A PLANNED APPROACH FOR A FORCED LANDING AT AN AIRPORT. THE PILOT LOWERED THE LANDING GEAR PREMATURELY ON FINAL APPROACH, THEN RAISED IT WHEN HE SAW HE WAS GOING TO LAND SHORT OF RUNWAY. A GEAR-UP LANDING WAS MADE ON RESIDENTIAL STREET ADJACENT TO THE AIRPORT. THE AIRCRAFT SLID INTO A TREE AFTER LANDING. THE INVESTIGATION REVEALED NO FUEL IN THE ENGINE FUEL SYSTEM. THE LEFT MAIN TANK, WHICH THE PILOT WAS USING, AND BOTH TIP TANKS, WERE EMPTY. THE RIGHT MAIN TANK AND BOTH AUXILIARY TANKS WERE FULL.
Probable cause
FUEL MISMANAGEMENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI90LA157
- Event ID
- 20001212X23365
- Case number
- CHI90LA157
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1990-06-18.
- API snapshot SHA-256: 72062e897c4f3a2d69e00d34834e48fd6181344955156651908be2a8a5f5454b; retrieved 2026-09-21T23:51:14.158Z.