WPR18TA223

NTSB accident investigation · Zenair Zenith Stol CH750 · Napa, CA · August 11, 2018

Accident · No injuriesFinal report
Date
August 11, 2018, 10:56 local (17:56 UTC)
Place
Napa, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N328SKZenair Zenith Stol CH750
Defining event
Enroute: Powerplant sys/comp malf/fail
Weather
Visual (VMC) · Day
Status
Completed · report June 3, 2020
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
FAA
FAA report
20180811010949A
Case key
98073

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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.

Findings · 5

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Fluids: fuelAircraft › Fluids/misc hardware · Incorrect use/operationKemnitzer Stephen R ZENITH STOL CH750: 1 caseAll aircraft: 1,695 casesProbable cause
Use of equip/infoPersonnel issues › Task performance · PilotKemnitzer Stephen R ZENITH STOL CH750: 1 caseAll aircraft: 111 casesProbable cause
Fluids: oilAircraft › Fluids/misc hardware · Fluid levelKemnitzer Stephen R ZENITH STOL CH750: 1 caseAll aircraft: 174 casesProbable cause
Engine fuel and controlAircraft › Aircraft power plant · Incorrect service/maintenanceKemnitzer Stephen R ZENITH STOL CH750: 1 caseAll aircraft: 49 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

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.

Factual narrative

Detonation Chapter 7 of the FAA publication Pilot's Handbook of Aeronautical Knowledge (PHAK) presented the following information regarding detonation: Detonation is an uncontrolled, explosive ignition of the fuel-air mixture within the cylinder's combustion chamber. It causes excessive temperatures and pressures which, if not corrected, can quickly lead to failure of the piston, cylinder, or valves. In less severe cases, detonation causes engine overheating, roughness, or loss of power. Detonation is characterized by high cylinder head temperatures and is most likely to occur when operating at high power settings. Common operational causes of detonation are: - Use of a lower fuel grade than that specified by the aircraft manufacturer - Operation of the engine with extremely high manifold pressures in conjunction with low rpm - Operation of the engine at high power settings with an excessively lean mixture - Maintaining extended ground operations or steep climbs in which cylinder cooling is reduced Detonation may be avoided by following these basic guidelines during the various phases of ground and flight operations: - Ensure that the proper grade of fuel is used. - Use an enriched fuel mixture, as well as a shallow climb angle, to increase cylinder cooling during takeoff and initial climb. - Avoid extended, high power, steep climbs. - Develop the habit of monitoring the engine instruments to verify proper operation according to procedures established by the manufacturer. General FAA records indicated that the airplane was built by the pilot, and received its initial airworthiness approval in 2014. The airplane was equipped with a Belgian ULPower brand 350iS series piston engine that was rated at 130 horsepower. Engine Fuel The ULPower Operating Manual (OM) for the engine stated that "regular unleaded automotive fuel…should be used to operate" the engine. The OM specified minimum octane rating values of 98 RON, 90 MON, or 94 AKI. "RON" and "MON" are two different methods and indices for determining the octane value. "AKI" stands for anti-knock index, and is the arithmetic mean of RON and MON. In the United States, the octane ratings posted by automotive fuel vendors are AKI values. Predominant US AKI values range from 87 to 93. A ULPower representative stated that the 93 AKI fuel in the US is acceptable for use in the engine. Finally, the OM also stated that "AVGAS 100 LL and/ or AVGAS UL91 may be used if regular fuel is not available." The pilot did not specifically report the fuel(s), or the octane rating(s) of those fuel(s), that he used in the engine. Logbook Information The pilot-provided maintenance records were neither current nor in compliance with applicable FAA regulations. The records lacked the FAA-required documentation that certified the completion of the FAA-required Phase 1 flight test period. The airframe log only contained a single entry, dated 2014, which appeared to be the original post-build airworthiness signoff for theairplane. Although the pilot reported that he had an engine logbook, he did not provide one to the investigation. The records that were provided by the pilot did not include any entries that documented any maintenance activities. Maintenance Information According to pilot-provided information, the most recent "100 hour" inspection was completed on April 1, 2017, and that at that time both the airplane and engine total time in service was 200.5 hours. The pilot reported to an FAA inspector that he had previously had "low compression problems" with the engine, and that he had sent the engine back to the manufacturer for replacement of several components, including all four cylinder heads, one cylinder, and all piston rings. The pilot did not provide any documentation or other substantiation of that assertion. The incomplete maintenance records precluded evaluation of the maintenance history of the engine. Engine Oil Changes Regular oil changes that include examination of the oil filter and oil sample analyses are common practices that are proven to provide early detection of unusual engine wear or deterioration. The pilot-provided records did not include any entries that documented any oil changes, oil filter examinations, or oil sample analyses. Pilot's Accident Accounts In his initial communications with the NTSB about the accident, the pilot reported that he believed that the high pitch attitude during the demonstration flight had caused the oil to be vented overboard via the oil breather assembly. In his subsequent written accident report to the NTSB, the pilot reported that "something broke in the engine and dumped oil into the muffler from the no.1 exhaust." On August 11, 2018, about 1056 Pacific daylight time, an experimental, amateur-built Zenith CH-750 airplane, N328SK, was substantially damaged during a forced landing near Napa County Airport (APC), Napa, California. The commercial pilot/owner and his pilot-rated passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions existed at APC about the time of the accident. The local flight had originated from APC about 25 minutes earlier. According to the pilot, who was also the builder of the airplane, the airplane was for sale, and the accident flight was a demonstration/familiarization flight for a potential buyer. The pilot reported that they flew in the local area for about 20 minutes, and then he handed airplane control to the potential buyer, who was in the right seat. The buyer wanted to see how slowly the airplane could fly, and decelerated to about 30 knots, which resulted in a significant airplane-nose-up pitch attitude. The airplane began "sinking," so the pilot/owner took back control and pushed the nose over to regain airspeed. Almost immediately smoke entered the cockpit. The pilot declared an emergency and headed towards APC. Within a minute or two, the engine lost all oil pressure,and then ceased developing power. The pilot initially attempted to glide to the airport, but then realized that the airport was too distant. He then decided to land on a road atop a nearby levee. The airplane touched down on the road, and the initial rollout was satisfactory. However, due to wind, the left wingtip struck the ground, and spun the airplane around. Due to the narrow width of the road and levee, the airplane then veered off the levee, and damaged the wing and fuselage. The airplane came to rest below the top of the levee, about 0.6 miles west of the APC runway 6 threshold. According to Federal Aviation Administration (FAA) information, about 1050 the pilot reported to the APC air traffic control tower (ATCT) local controller (LC) that he had an "oil pressure issue." The LC asked the pilot if he required any assistance, and the pilot replied in the negative. At 1055 the pilot re-contacted the LC, advising that he was having "more issues," but did not elaborate. The ATCT controller in charge (CiC) declared an emergency for the pilot. The pilot then radioed that he had lost all engine power and was attempting to reach runway 6. At 1056 the pilot advised the LC that he could not make the runway and was landing on a levee about 1/2 mile short of the runway. After the airplane came to rest, the pilot notified the LC of their situation. The 1054 APC automated weather observation included winds from 220° at 11 knots, visibility 10 miles, clear skies, temperature 23°C, dew point 14°C, and an altimeter setting of 29.98 inches of mercury. FAA records indicated that the pilot held a commercial pilot certificate with airplane single-engine land, rotorcraft-helicopter, and instrument airplane ratings. He also held a repairman experimental aircraft builder certificate valid for the accident airplane. According to information provided by the pilot, he had approximately 7,700 total hours of flight experience, including about 200 hours in the accident airplane make and model. His most recent flight review was completed in September 2017, and his most recent medical certificate was issued under the Basic Med program in April 2017. Examination of the airplane by an FAA inspector revealed that the wings and fuselage had sustained crush or buckling damage from the impact. The engine exhibited some impact-related damage, but it did not exhibit any visual evidence of any external non-impact related damage. The engine was found to be devoid of lubricating oil. Significant oil residue was observed on the muffler, and all along the lower fuselage. The source of the oil appeared to be in the region of the starter ring gear and its drive penetration of the engine case. The muffler was situated below the ring gear drive case penetration. The hour meter registered a total time of 200.8 hours. The engine was removed and shipped to the manufacturer's service facility in the US, where it was disassembled and examined in detail. All four pistons displayed evidence ofsignificant erosion damage, consistent with detonation. At least one piston was eroded to the point that it could no longer seal against the cylinder wall. The engine manufacturer's representative attributed this level of damage to the use of 87 octane (AKI) fuel. This piston damage would allow cylinder combustion gasses to enter and pressurize the engine crankcase, which in turn could force oil past any flexible seals and out of the crankcase. Specifically, pressurization of the crankcase could also force oil past the starter ring gear seal, out of the engine. The engine control unit (ECU) was removed and shipped to the engine manufacturer's facility in Belgium. The ECU internal programming was validated, and then the ECU was installed on a testbed engine. That engine operated normally with the accident ECU installed. Separately, and contrary to the pilot's unsubstantiated assertions that he had previously sent the engine back to the manufacturer for "low compression" problems, the manufacturer's records indicated no such event. Despite the fact that the engine was no longer under warranty, the engine manufacturer did provide the pilot with some replacement components at no charge. In addition, the sole US-based engine manufacturer's service center indicated that there were no records of that service center conducting any repair actions on that engine.

Aircraft

Registration
N328SK
Reported as
Zenair Zenith Stol CH750 (No Series)
Category
Airplane, amateur-built
Serial number
75-8975
Built
2014
Airframe hours
200
Engine
ULPower 350iS, 130 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Special, Experimental (Special)
Last inspection
100 hour · April 1, 2017
Departed
APC · Napa, CA
Destination
APC · Napa, CA
Airport
APC · Napa County

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
67
Injuries
None
Certificate
Commercial
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
BasicMed
Last flight review
September 21, 2017
Seat
Left
Restraint
3-point
Flight hours
7,700 total · 200 in this make and model · 7,500 as pilot in command · 15 in the last 90 days · 5 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
220° at 11 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
73 °F, dew point 57 °F
Altimeter
29.97 inHg
Observed at
APC, 1 nm away

Docket · 9

The files NTSB released with the investigation on February 28, 2020, on NTSB’s docket system: statements, records, photos and specialists’ reports. 7.7 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.