CHI94LA225 · Beech K35
Beech K35 · Accident: total loss of engine power (non-mechanical) en route
From Ionia County Airport (Y70) to an unrecorded destination
Event
- NTSB case
- CHI94LA225
- 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 K35
- 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
- N153C
- Operator
- Richard J. Van Lente · private individual
- Onboard fatalities
- Unknown
- Route
- From Ionia County Airport (Y70), Ionia, MITo 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
- En route · climb to 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
AFTER COMPLETING THREE PRACTICE INSTRUMENT APPROACHES, THE PILOT PREPARED TO RETURN TO HIS DEPARTURE AIRPORT WHEN THE AIRPLANE EXPERIENCED A LOSS OF ENGINE POWER. THE PILOT INITIATED EMERGENCY PROCEDURES AND ATTEMPTED TO RETURN TO THE AIRPORT TO MAKE A FORCED LANDING. AFTER REALIZING THAT HE WOULD NOT BE ABLE TO MAKE IT BACK TO THE RUNWAY, THE PILOT LEVELED THE WINGS AND RAISED THE NOSE IN PREPARATION FOR IMPACT WITH THE GROUND. AFTER IMPACT, THE AIRPLANE SKIDDED TO REST. POSTACCIDENT INSPECTION REVEALED THE FUEL SELECTOR TO BE IN THE LEFT INBOARD POSITION. VISUAL INSPECTION OF THE FUEL TANK REVEALED THE TANK WAS LOW TO EMPTY. ALL TANKS WERE INTACT AND THERE WAS NO EVIDENCE OF A FUEL SPILL AT THE SCENE.
Probable cause
the pilot's improper fuel tank selection resulting in fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI94LA225
- Event ID
- 20001206X01693
- Case number
- CHI94LA225
- 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: b5fdca820c4b6fc4cc9413c6bcb414c8164f89703d0748fbb027f8f9d35a3e12; retrieved 2026-09-21T22:34:52.712Z.