Event CEN22LA251

Factual narrative

On June 2, 2022, about 1315 eastern daylight time, an experimental, amateur-built Trojan TA16 airplane, N36YR, was substantially damaged when it was involved in an accident near Ray, Michigan. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot, who was the owner and builder of the airplane, stated that the preflight, engine run-up, and takeoff were all normal. During the departure climb, the engine surged rapidly three times and then stopped producing power. The pilot scanned the cockpit instruments and noted that the tachometer displayed 0 rpm. The pilot turned the airplane back toward the runway while attempting to restore engine power. Unable to restore engine power or reach the runway, the pilot performed a forced landing, during which the airplane collided with small trees, resulting in substantial damage to the fuselage and wings. A postaccident examination of the engine found that the pistons in cylinders Nos. 1 through 5 were seized at the bearings connecting the piston arms to the crankshaft. Those bearings displayed signatures consistent with a lack of adequate oil lubrication and cooling. Reviewed data stored in the electronic flight instrument system did not provide indications of an impending oil system malfunction. The pilot reported that he purchased the engine as a “firewall forward” package. He speculated that the engine could have benefitted from additional oil cooling, such as a secondary oil cooler. The pilot, who was the builder of the experimental, amateur-built airplane, reported that shortly after takeoff the engine surged rapidly three times and then lost total power. The pilot turned the airplane back toward the airport to try to land on the runway. While maneuvering toward the airport, the pilot attempted to restore engine power, but was not successful. Unable make the runway, the pilot performed a forced landing to a rough field, during which the airplane sustained substantial damage to the fuselage and wings. A postaccident examination of the engine found that the bearings connecting the piston arms to the crankshaft were seized and displayed signatures consistent with a lack of oil lubrication and cooling. Reviewed data stored in the electronic flight instrument system did not provide indications of an impending oil system malfunction. The pilot stated that he purchased the engine as a “firewall forward” package and speculated that the engine could have benefitted from the installation of a secondary oil cooler. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

• — Aircraft-Aircraft power plant-Eng oil sys (airframe furnish)-(general)-Malfunction