CHI97LA009 · Hayes LANCAIR 235 LANCAIR 23
Hayes LANCAIR 235 LANCAIR 23 · Accident: total loss of engine power (mechanical failure) en route
From Charles B. Wheeler Downtown Airport (MKC) to an unrecorded destination
Event
- NTSB case
- CHI97LA009
- 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
Hayes LANCAIR 235 LANCAIR 23
- Aircraft type
- Hayes LANCAIR 235
- 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
- N90WH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Charles B. Wheeler Downtown Airport (MKC)To 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 · 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 (mechanical failure)
- 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 exhaustion
- 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 › Exhaustion
- Fuel system, carburetor › Excessive flow/output
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated he took off with 8 to 10 gallons of fuel which should have been enough for approximately 1 1/2 hours of flight time. Fifteen minutes after takeoff, he noticed the fuel sight gauge was indicating a low level of fuel. He reversed course to head back to the airport. He stated that fuel exhaustion occurred eight minutes later. The airplane was substantially damaged during the off airport landing in a field. Inspection revealed a total of one cup of fuel between both wing tanks and the fuel level in the center tank was below the pick-up line level. The pilot stated he later tested the fuel system and discovered that the carburetor float valve was stuck in the open position.
Probable cause
a stuck carburetor float valve which resulted in excessive fuel flow and ultimately fuel exhaustion. A factor related to the accident was the rough terrain on which the forced landing was made.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI97LA009
- Event ID
- 20001208X06855
- Case number
- CHI97LA009
- 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: 76df67aea65b31c3c0fd6c4d9c71ce3f0de4e87895f276e22e8da6ed2e7aea51; retrieved 2026-09-22T20:57:25.256Z.