Aviation Accident Summaries

Aviation Accident Summary WPR18LA166

Plant City, FL, USA

Aircraft #1

N13RF

CESSNA 421C

Analysis

During takeoff on a night aerial observation flight, the pilot reported that the airplane did not accelerate adequately, and he chose to abort the takeoff. The airplane continued off the end of the runway and came to rest in a field about 750 ft past the departure end, resulting in substantial damage to the wings and fuselage. Examination revealed that the left engine turbocharger compressor air duct was disconnected from the throttle body. The right engine's engine-driven fuel pump was contaminated with water and debris and would not produce normal pressures and flow; however, whether these anomalies were present at the time of the accident or occurred as a result of or after the accident could not be determined. There were no other anomalies observed that would have precluded normal engine operation. Review of performance information revealed that, given the airplane's weight and atmospheric conditions at the time of the accident, the pilot had adequate runway available to accelerate the airplane to a decision speed, abort the takeoff, and stop on the remaining runway. Airport surveillance video revealed that the pilot did not activate the pilot-controlled runway lighting before takeoff, and tire skid marks on the runway were consistent with heavy braking within the last 200 ft of the runway's paved surface. The circumstances of the accident are consistent with the pilot's delayed decision to abort the takeoff. The pilot's failure to activate the runway lighting system before takeoff likely contributed to the accident by reducing his ability to judge the airplane's acceleration with respect to the runway distance remaining and abort the takeoff in a timely manner upon recognizing an anomaly.

Factual Information

HISTORY OF FLIGHTOn June 11, 2018, about 0140 eastern daylight time, a Cessna 421C, N13RF, sustained substantial damage when it was involved in an accident at Plant City Airport (PCM), Plant City, Florida. The airline transport pilot sustained minor injuries and the passenger was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 aerial observation flight. According to the pilot, during the takeoff roll, the airplane did not accelerate adequately, and he elected to abort the takeoff. The airplane continued past the departure end of the runway, across a road, and came to rest in a grass field. Review of airport surveillance video indicated that the pilot did not activate the airport's pilot-controlled runway lighting before takeoff. AIRCRAFT INFORMATIONThe Pilot's Operating Handbook (POH) Engine Failure During Takeoff checklist (Speed Below 100 knots or Gear Down) stated to "close throttles immediately and brake as required" during an aborted takeoff. The handbook recommended discontinuing the takeoff for rough engine operation, unequal power between engines, and sluggish engine acceleration. The operator reported that the airplane's gross weight at the time of the accident was 6,870 lbs. At that weight, the airplane's takeoff distance was about 1,673 ft and the accelerate-stop-distance was about 3,040 ft; therefore, about 910 ft of runway should have remained during the aborted takeoff. According to the POH, the accelerate-stop-distance is defined as, "the distance required to accelerate an airplane to a specified speed and, assuming failure of an engine at that instant that speed is attained, to bring the airplane to a stop." The accelerate-stop distance assumed engine failure at the engine failure speed and idle power and maximum braking after engine failure. AIRPORT INFORMATIONThe Pilot's Operating Handbook (POH) Engine Failure During Takeoff checklist (Speed Below 100 knots or Gear Down) stated to "close throttles immediately and brake as required" during an aborted takeoff. The handbook recommended discontinuing the takeoff for rough engine operation, unequal power between engines, and sluggish engine acceleration. The operator reported that the airplane's gross weight at the time of the accident was 6,870 lbs. At that weight, the airplane's takeoff distance was about 1,673 ft and the accelerate-stop-distance was about 3,040 ft; therefore, about 910 ft of runway should have remained during the aborted takeoff. According to the POH, the accelerate-stop-distance is defined as, "the distance required to accelerate an airplane to a specified speed and, assuming failure of an engine at that instant that speed is attained, to bring the airplane to a stop." The accelerate-stop distance assumed engine failure at the engine failure speed and idle power and maximum braking after engine failure. WRECKAGE AND IMPACT INFORMATIONExamination of the accident site by a Federal Aviation Administration inspector revealed that the airplane came to rest upright about 750 ft from the edge of the runway threshold. Skid marks from the braking of both main tires were observed beginning in the runway overrun. Both tires made impressions in the grass and dirt that continued from the end of the runway to the main wreckage. The fuselage and vertical stabilizer displayed damage consistent with impact with the fences. The nose gear had collapsed, and the flaps were in the retracted position. Both main tires displayed wear consistent with heavy braking. Fuel was observed leaking from the wings at the accident site. Examination of the airframe and engines revealed braking system and flight control continuity. All the engine components and accessories were present. The crankshafts were manually rotated by hand at the propellers and internal continuity was established through both engines. The combustion chamber of each cylinder was examined using a borescope and normal operational conditions were observed. The examination revealed that a turbocharger compressor air duct was disconnected from the throttle body component on the No. 1 (left) engine. No other additional anomalies were discovered during the examination that would have precluded normal operation. The engines were sent to the manufacturer for detailed examination and test runs. The engines were fitted with a test propeller and an oil and fuel source. Additionally, the No. 1 engine was fitted with a temporary starter adapter. The No. 1 engine started normally and was run at various power settings for several minutes, including at full power, with no anomalies noted. A magneto check revealed no anomalies. With the turbocharger compressor air duct disconnected from the throttle body, the No. 1 engine was started again and run; a power loss was observed. The manifold pressure indicated data similar to a naturally aspirated (non-turbocharged) engine. When the throttle was initially retarded, the engine rpm increased, consistent with a more efficient fuel/air mixture. The No. 2 (right) engine initially failed to rotate during start and the starter motor was replaced. During the next attempt, the engine started normally but would only operate while being primed. The engine-driven fuel pump was removed and examined. Examination revealed that the fuel pump was contaminated with water and organic substances, and that its internal components were corroded and seized, which resulted in the fracture of the drive coupling. Assembly holes in the rubber diaphragm were observed. The pump vanes were corroded and frozen to the pump housing. The pump's internal parts were removed, cleaned, reassembled, and the pump was bench tested, during which the pump failed to produce normal pressures and flow. The source of the fuel pump contamination could not be determined. The engine-driven fuel pump from the No. 1 engine was installed, and the No. 2 engine started normally and was run at various power settings for several minutes, including at full power, with no anomalies noted. The throttle was rapidly advanced from idle to full power, and the engine performed normally with no hesitation, stumbling, or interruption.

Probable Cause and Findings

The pilot's delayed decision to abort the takeoff, which resulted in a runway overrun. Contributing to the accident was an engine anomaly for reasons that could not be determined based on the available information, and the pilot's failure to activate the runway lighting system before takeoff.

 

Source: NTSB Aviation Accident Database

Get all the details on your iPhone or iPad with:

Aviation Accidents App

In-Depth Access to Aviation Accident Reports