CHI06LA069 · Zilz Zenith CH801
Zilz Zenith CH801 · Accident: loss of engine power en route
From Greensfield Airport (M71) to Moscow Mills, MO
Event
- NTSB case
- CHI06LA069
- 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
- Unknown
- 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
Zilz Zenith CH801
- Aircraft type
- Zilz ZENITH CH801
- 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
- N143ZT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Greensfield Airport (M71), Moscow Mills, MOTo Moscow Mills, 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
- Loss of engine power
- 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; Utility pole; Tree(s)
- 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
- Cooling system › Inadequate
- Fluid, fuel › Starvation
- Fuel system › Vapor lock
- Owner/builder › Acft/equip, inadequate design
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The experimental amateur-built airplane contacted trees and a power pole during an off-airport forced landing following a loss of engine power. The pilot said the airplane was on its third flight since he finished building it. The purpose of the flight was to test and record engine performance at various power settings. He stated that during the flight the fuel pressure dropped below 2 pounds per square inch (psi) and the engine stopped running. He stated he was able to restart the engine, but it failed to produce power. The pilot turned toward the airport, but he did not have enough altitude to make it back, so he elected to land in a pasture with a row of trees bordering the edge of the field. The pilot stated he did not see the power lines above the trees until he was at an altitude, which was insufficient to clear the lines. He elected to fly through the tree line in order to avoid contacting the power lines. The airplane contacted a power line pole and trees prior to coming to rest in the field. Inspection of the engine and airplane failed to reveal any failure/malfunction which would have resulted in the loss of engine power. The pilot reported that he believes the loss of engine power was a result of vapor lock. He reported the gascolator is located near one of the exhaust pipes and that the loss of power occurred during a flight condition, which would have created reduced cooling through the engine cowling and increased exhaust temperatures.
Probable cause
A loss of engine power due to inadequate design of the engine compartment which resulted in inadequate engine cooling and fuel starvation due to vapor lock. Factors associated with the accident were the utility pole and trees which were contacted during the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06LA069
- Event ID
- 20060120X00100
- Case number
- CHI06LA069
- 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, coordinates. 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: 6d4c4217bc29b4640f396db5153b1559a7039dfeff2c4e2440a85f877f55c281; retrieved 2026-09-22T05:09:24.739Z.