Aviation Accident Summaries

Aviation Accident Summary ERA16LA171

Foley, AL, USA

Aircraft #1

N3372Q

CESSNA 421

Analysis

The private pilot of the twin-engine airplane departed on the personal flight. During the takeoff roll, all indications were normal. When the airplane accelerated to between 75 and 80 knots, the pilot pulled back on the yoke slowly, and the airplane began to climb. After he raised the landing gear, the pilot noticed that the airplane was not continuing to climb and that the airspeed was 80 knots; he then heard the stall warning horn. The airplane impacted trees about 1/4 mile from the runway, caught fire, and was destroyed; the pilot egressed with minor injuries. The airplane's published minimum control speed was 86 knots and the break ground and climb speed was 106 knots. Given that information, it is likely that the pilot's attempt to rotate and climb the airplane below 80 knots resulted in the airplane being unable to gain altitude and climb above trees at the end of the runway.

Factual Information

On April 26, 2016, at 1424 central daylight time, a Cessna 421B, N3372Q, was destroyed when it impacted trees and terrain in Foley, Alabama. The private pilot sustained minor injuries. Visual meteorological conditions prevailed, and no flight plan had been filed for the flight from Foley Municipal Airport (5R4), Foley, Alabama, to West Georgia Regional Airport (CTJ), Carrollton, Georgia. The personal flight was conducted under the provisions of 14 Code of Federal Regulations Part 91. During a postaccident interview with a Federal Aviation Administration Inspector, the pilot recounted that he taxied out and lined up for takeoff on the runway. With brakes on, he cycled the propellers and they "checked good." The magneto check at 1,500 rpm was also "good," as were the oil pressure and oil temperature. The pilot then ensured that the fuel selectors were position to both main fuel tanks, the throttles were full, mixtures were all the way forward, the fuel boost pumps were on low, and the propellers were all the way forward. He selected the flaps to the takeoff position and released the brakes. During the takeoff roll, everything was "normal" (temperatures and pressures were "in the green"), and when the airplane had accelerated to 75-80 knots, the pilot pulled back on the yoke slowly, and the airplane began to climb. The pilot raised the landing gear and noticed that the airplane wasn't climbing. He looked at the airspeed indicator, which indicated 80 knots. The pilot heard the stall warning and pulled back on the yoke. He then shut the boost pumps off and lowered the flaps before a hard impact. After impact, the pilot found himself upside down. He released his seat belt, saw fire and went to the back of the airplane. He opened the aft hatch and rolled forward, landing flat on his back. Two men then helped him up and led him to a nearby building. When asked about the performance of the airplane's engines the pilot stated, "the engines were operating fine and I screwed up." Review of the normal takeoff checklist for the airplane revealed that the minimum control speed was 86 knots, and the break ground and climb out speed was 106 knots. A witness stated that during the takeoff from runway 18, the airplane left the ground at the departure runway end, just clearing the airport's perimeter fence. The airplane was unable to gain sufficient altitude to clear the trees less than ¼ of a mile south of the runway. The airplane began hitting tree tops, and impacted a large oak tree with the left wing, then spun into two other large oak trees 30 feet to the southwest. The airplane then flipped over, hit the ground, exploded and was consumed by fire. The pilot jumped from the rear entry door and landed on his back. The pilot refused medical attention and sustained burns and a cut to his left hand.

Probable Cause and Findings

The pilot's failure to obtain proper takeoff speed before breaking ground, which resulted in the airplane’s failure to gain altitude and a collision with trees and terrain.

 

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