CEN19LA199 · Zenair CH750 STOL
Zenair CH750 STOL · Accident: loss of engine power (total) en route
From Kentucky Dam State Park Airport (M34) to Mayfield Graves County Airport (M25)
Event
- NTSB case
- CEN19LA199
- 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
Zenair CH750 STOL
- Aircraft type
- Zenair CH750
- 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
- N170MV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Kentucky Dam State Park Airport (M34), Calvert City, KYTo Mayfield Graves County Airport (M25), Mayfield, KY
- Aircraft age
- About 3 years (built 2016)
- 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 · descent
- Defining eventThe 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 (total)
- 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
- Aircraft › Aircraft power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a personal flight the airplane had a total loss of engine power while in a descent. The pilot was unable to restart the engine and a forced landing was completed to rough terrain, during which the airplane landed hard and nosed over. The airplane sustained substantial damage to the forward fuselage, left wing, and rudder.
Flight and engine data recovered from a primary flight display (PFD) established that about 38 seconds after the pilot reduced engine power to descend the exhaust gas temperature (EGT) for cylinder Nos. 1 and 3 began to decrease rapidly. During the next 45 seconds, the EGT decreased 335°C and 461°C for the No. 1 and No. 3 cylinders, respectively. However, in contrast, during the same 45 second period, the EGT for cylinder Nos. 2 and 4 increased about 60ºC. The EGT for cylinder Nos. 2 and 4 also began to decrease rapidly when the fuel pressure dropped as low as 7.5 pounds per square inch. The engine stopped rotating about 10 seconds before the PFD ceased recording data, at which time the EGT was about 90°C and 210° for cylinder Nos. 1 and 3 and cylinder Nos. 2 and 4, respectively. The final data recorded showed the airplane in a right turn about 60 feet above the ground, and in a 542 feet per minute descent at 48 knots indicated airspeed.
Examination of the fuel system did not reveal any evidence of a mechanical failure. Neither wing tank contained any recoverable fuel; however, the airplane sat inverted several days before it was recovered to an upright position. The pilot stated the left and right fuel tanks contained about 11 gallons and 9 gallons, respectively, before the first flight of the day. Based on recovered PFD data and the expected fuel consumption rate of 7.9 gallons per hour at 2,700 rpm, the engine likely used about 11 gallons of fuel before the accident. The pilot stated that most of the flight was flown using fuel from the left tank and that the loss of engine power had occurred a few minutes after he switched to the right fuel tank. At the accident site, the fuel selector switch was found positioned to use fuel from the left tank; however, it is possible that the pilot switched fuel tanks during his troubleshooting after the loss of engine power.
Additionally, as discussed previously, the EGT for cylinder Nos. 2 and 4 initially continued to increase despite the rapid decrease of EGT for cylinders Nos. 1 and 3, which suggests fuel was still present for engine combustion at that point. Therefore, it is unlikely that fuel exhaustion occurred during the flight.
An engine examination revealed the No. 3 exhaust valve was stuck open. A borescope inspection of the No. 3 cylinder did not reveal any mechanical issues or interference between the piston and the stuck exhaust valve. A borescope inspection of the crankshaft and camshaft did not reveal any anomalies or mechanical damage.
The airplane was equipped with an experimental reciprocating engine equipped with an electronic fuel injection and ignition system. The engine control unit (ECU) continuously controls the air-fuel mixture and ignition timing based on readings from multiple sensors, including a crankshaft position sensor that provides the engine speed and position of each cylinder’s piston and valves. It is likely that the stuck No. 3 exhaust valve adversely affected cylinder compression, engine timing, and fuel delivery to the cylinders.
Probable cause
A stuck exhaust valve that resulted in a loss of engine power and a forced landing to rough terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN19LA199
- Event ID
- 20190630X22854
- Case number
- CEN19LA199
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: c40949657eaa77d845744f020b68af996f3fcdc2e2f1158164c2eb1b6250fdca; retrieved 2026-09-16T09:20:51.267Z.