CEN18LA377

Factual narrative

On September 7, 2018, about 2103 central daylight time, a Piper PA-32 airplane, N33354, was substantially damaged during a forced landing near Roanoke, Texas. The pilot and two passenger sustained minor injuries, two passengers were not injured, and one passenger sustained serious injuries. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Night visual meteorological conditions prevailed and no Federal Aviation Administration (FAA) flight plan had been filed for the flight. The flight was originating at the time of the accident and was en route to Gulfport-Biloxi International Airport (GPT), Gulfport, Mississippi.According to the pilot, the airplane's engine started without hesitation or issue and the engine run-up, prior to takeoff was normal with no discrepancy in the magneto drop or instrument indications. Shortly after takeoff from runway 35 "the engine failed" and the pilot was not able to maintain altitude. He stated that the stall horn sounded, and he elected to land straight ahead. The airplane impacted the ground and came to rest at the base of several trees and bushes; both wings separated from the airplane and the fuselage came to rest on its left side. The pilot stated that after the accident he turned the fuel selector valve, the fuel pump, and the ignition switch to the "off" position. An examination of the engine revealed that the lower set of spark plugs and the upper right set of spark plugs exhibited worn out – severe signatures and normal to worn out signatures respectively when compared to the Champion Check-a-Plug chart. An engine test run was conducted. With the wings separated, the fuselage was strapped down to a trailer. The damaged propeller was removed, and a replacement propeller was installed. Additionally, a fuel can was connected to the electric driven fuel pump and a fuel line was then run to the engine driven fuel pump. Several attempts were made at starting the engine; however, after the lower spark plugs were replaced, the engine started without hesitation and ran at various power settings. The engine would not run when the right magneto was selected. An examination of the right magneto revealed that the coil had failed. The airplane was equipped with a JPI 900. Engine parameters downloaded from the unit illustrated expected exhaust gas temperatures and cylinder head temperatures consistent with the engine start, an engine run-up, and the increase in power for takeoff. The data also illustrated the increase in oil temperature, manifold pressure, rpm, and fuel flow, also consistent with the engine start, an engine run-up, and the increase in power for takeoff. The engine rpm and fuel flow drop off about 20 seconds before the end of the recording. The commercial pilot and five passengers departed on a personal night cross-country flight. According to the pilot, the engine start and run-up were uneventful. Shortly after takeoff, the engine lost total power, and the pilot was unable to maintain altitude. He conducted a forced landing, which resulted in substantial damage to the fuselage and wings. An engine examination revealed that the upper right spark plugs were in a worn-out normal condition and the lower spark plugs were in a worn-out severe condition. The lower spark plugs were replaced, and a test engine run was conducted; the engine started and ran without hesitation at various power settings. However, it was noted during the test that the engine would not run on the right magneto. Further examination of the right magneto found a failed magneto coil. Despite the failed coil on the right magneto and the spark plug condition, the engine ran at full power settings. No other anomalies were noted with the engine or fuel system that would have precluded normal operation. A failed magneto or the noted spark plug conditions would have resulted in a rough-running engine but not a complete loss of engine power as the pilot described. Thus, the reason for the total loss of power could not be determined. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

FAA avdata. C = Cause, F = Factor.

• C Not determined-Not determined-(general)-(general)-Unknown/Not determined - C