No fatalities

8 Oct 2020: CESSNA 414 (N8132Q) — Sierra AE, LLC — West Palm Beach, FL

West Palm Beach, FL, United States

On 8 Oct 2020, a CESSNA 414 (registration N8132Q) operated by Sierra AE, LLC was involved in an aviation accident near West Palm Beach, FL. No fatalities were reported. Investigators recorded the probable cause as: The pilot’s inadequate preflight inspection during which he failed to detect a flight control abnormality, and his failure to expediently abort the takeoff, which resulted in the co-pilot performing a delayed aborted takeoff and the subsequent runway overrun. This summary draws on records from NTSB; 12 related events involving the same aircraft type or operator are linked below.

SourcesNTSBPrimary reportUpdated 1778583330Data APIEditorial standards

On October 8, 2020, a Cessna 414 (N8132Q) was substantially damaged after an aborted takeoff at North Palm Beach County General Aviation Airport. Two pilots and five passengers sustained serious injuries. The control lock was found behind the rudder pedals.

Accident Overview

On October 8, 2020, at about 1115 eastern daylight time, a Cessna 414, registration N8132Q, was substantially damaged during a takeoff accident at North Palm Beach County General Aviation Airport (F45) in West Palm Beach, Florida. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The two private pilots and five passengers aboard sustained serious injuries.

Preflight and Takeoff Sequence

According to the multiengine-rated private pilot seated in the right front seat (copilot), after engine start and taxi, the pilot performed a runup and did not note any irregularities. During taxi onto the runway, the copilot checked the takeoff trim setting, which gave him a view of the pilot's control yoke; he did not see the control lock. The pilot then applied brakes, advanced throttles to full power, and released brakes to begin the takeoff roll. Shortly into the roll, the copilot felt a slight shudder that seemed to come from the controls but lasted only a moment. As the airplane continued down the runway, the copilot realized it should have rotated; the airspeed indicator showed about 10 to 15 mph past "blueline" (119 mph), but the airplane remained on the runway and continued accelerating. The copilot looked at the pilot, who was looking down and trying to move the control yoke. The copilot also attempted to pull back on the yoke but could not move the controls. He aborted the takeoff by pulling the throttles to idle and applying maximum braking. He estimated the speed was between 120 and 130 knots at that point.

Accident Sequence and Aircraft Condition

The airplane came to rest about 450 feet beyond the departure end of runway 14. Tire skid marks from the left and right main landing gear were visible departing the right side of the runway near the runway 32 numbers. The marks continued through grass and mud for 575 feet before the airplane impacted a dirt mound with the right wing. The airplane then spun around and came to rest nose-down in a marshy area, partially submerged in about 5 feet of water. The fuselage, wings, and empennage sustained substantial damage.

Control Lock Examination

During post-accident examination, the control lock was found on the left side of the cockpit under the far-left rudder/brake pedal. It showed no signs of damage. The control lock was approximately 12 inches long, consisting of a metal rod in a "seven" shape that slid into the control yoke on one end, with a red and yellow streamer attached to the opposite end. The stabilizer/elevator assembly was torn from its attachments during impact, but both sides remained attached at their respective locations, and the elevator control rigging was intact and operational. The control lock holes on both yokes had no elongation or damage. Examination of the elevator flight control rigging and functional checks confirmed continuity and functionality; no pre-impact anomalies were noted.

Pilot Statements

The pilot reported performing the preflight, taxi, and runup per the checklist, with nothing unusual. He stated he always removes the control lock per the checklist and, when the controls appeared jammed during the takeoff roll, he looked down and saw no control lock in place. He said that when he removes the control lock, he puts it in his flight bag, but a shoulder injury might have caused the lock to miss the bag, leading to its location behind the rudder pedals. Due to a head injury, he remembered no additional details.

During a follow-up interview, the copilot stated he could not recall whether the pilot left the control lock installed during preflight or attempted to remove it during the takeoff roll.

Video Evidence

Witness and airport surveillance videos were analyzed. One witness video showed the airplane taxiing on the ramp; still images indicated the elevator was in a trailing-edge-down position with the elevator horns above the horizontal stabilizer. An exemplar airplane with a control lock installed showed a similar elevator position, though exact comparison was not possible from the still images. A third video showed the airplane accelerating down the runway; review determined the airplane was passing through 100 knots with about 1,800 feet of runway remaining (total runway length 4,300 feet). Airport security footage showed the airplane proceeding along the last third of the runway, departing the right side before colliding with a mound and disappearing from view.

Performance Data

Airplane performance data indicated that the airplane should have taken off at 2,185 feet down the 4,300-foot runway. The weight and balance were within center of gravity and weight limitations.

Checklists

According to the manufacturer's preflight and before-takeoff checklists, the flight control lock must be removed prior to engine start, and flight controls must be checked prior to takeoff.

Contributing factors

Inadequate inspectionPilot