FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR18TA223 · Zenair ZENITH STOL CH750

11 Aug 2018 · Napa, CA, United States

Zenair ZENITH STOL CH750 · Accident: powerplant system/component malfunction/failure en route

From Napa County Airport (APC) to Napa County Airport (APC)

Report a problem

Event

NTSB case
WPR18TA223
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 ZENITH STOL 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
N328SK
Operator
Unknown
Onboard fatalities
Unknown
Route
From Napa County Airport (APC), Napa, CATo Napa County Airport (APC), Napa, CA
Aircraft age
About 4 years (built 2014)
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
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
Powerplant system/component malfunction/failure
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 › Fluids/miscellaneous hardware
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot/owner was conducting a flight in the experimental amateur-built airplane with a pilot-rated passenger, who was a potential buyer. The pilot reported that they flew in the local area for about 20 minutes, and then smoke entered the cockpit. The pilot declared an emergency and headed toward the departure airport. Within 1-2 minutes, the engine lost all oil pressure and then lost total power.

The pilot initially attempted to glide to the airport but, because it was too far away, decided to land on a road atop a nearby levee. The airplane touched down normally, but due to wind, the left wingtip struck the ground; the airplane spun, veered off the levee, and sustained substantial damage to the wing and fuselage.

The engine exhibited some impact-related damage but did not exhibit any external evidence of nonimpact-related damage. The engine was devoid of lubricating oil, and significant oil residue was observed on the muffler and the lower fuselage. Postaccident examination indicated that the source of the oil was via the seal for the engine case drive penetration of the starter ring gear, located just above the muffler. The oil exited via this seal and produced smoke when it contacted the hot muffler.

The engine control unit (ECU) was removed and shipped to the engine manufacturer's facility, where it was installed on a testbed engine. That engine operated normally with the accident ECU installed.

The engine was disassembled and examined in detail. All four pistons displayed evidence of significant erosion damage consistent with detonation, with at least one piston eroded to the point that it could no longer seal against the cylinder wall. A common cause of detonation is using a lower octane fuel than specified by the manufacturer. The damage was consistent with the use of fuel with octane rating(s) significantly below that required for the engine. Although the pilot did not specify the octane rating of the fuel that he used, it is likely that he used fuel below the required octane rating.

At least one piston was eroded to the point that it allowed cylinder combustion gasses to enter and pressurize the engine crankcase. This crankcase pressurization forced the engine oil past the starter ring gear drive seal and out of the engine, which resulted in the exhaustion of the engine oil and a subsequent complete loss of engine power. The pilot-provided maintenance records did not include any entries that documented maintenance activities, including oil changes. Had the pilot conducted regular inspections and maintenance, it is possible that the detonation-caused internal engine damage would have been detected before the accident flight.

Probable cause

The pilot's use of fuel below the required octane rating, which caused engine detonation and damage and subsequently led to oil exhaustion and a total loss of engine power in flight. Contributing to the accident was the pilot's inadequate service/maintenance of the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR18TA223
Event ID
20180811X71550
Case number
WPR18TA223
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. 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: 3a88c8210a7fcbcb4c8b731ecee92f797fd7592cadaec19d8a114983e118083c; retrieved 2026-09-16T08:04:49.449Z.