Accident Cessna 414 N8132Q,
ASN logo
ASN Wikibase Occurrence # 243730
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Thursday 8 October 2020
Time:11:15
Type:Silhouette image of generic C414 model; specific model in this crash may look slightly different    
Cessna 414
Owner/operator:Sierra AE LLC
Registration: N8132Q
MSN: 414-0032
Year of manufacture:1997
Total airframe hrs:6377 hours
Engine model:Continental TSIO-520
Fatalities:Fatalities: 0 / Occupants: 7
Aircraft damage: Destroyed
Category:Accident
Location:North Palm Beach County General Aviation Airport (F45), FL -   United States of America
Phase: Take off
Nature:Private
Departure airport:North Palm Beach County Airport, FL (F45)
Destination airport:Claxton-Evans County Airport, GA (CWV)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
On October 8, 2020, about 1115 eastern daylight time, a Cessna 414, N8132Q, was substantially damaged when it was involved in an accident at North Palm Beach County General Aviation Airport (F45), West Palm Beach, Florida. The private pilot and six passengers sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The copilot, who was seated in the right seat, reported that after an uneventful run-up and taxi, the pilot, who was seated in the left seat, initiated the takeoff. The airplane remained on the runway past the point at which takeoff should have occurred and the copilot observed the pilot attempting to pull back on the control yoke but it would not move. The copilot then also attempted to pull back on the control yoke but was also unsuccessful. Observing that the end of the runway was nearing, the copilot aborted the takeoff by reducing the throttle to idle and applying maximum braking. The airplane overran the runway into rough and marshy terrain, where it came to rest partially submerged in water.

Postaccident examination of the airplane and flight controls found no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. Specifically, examination of the elevator flight control rigging, in addition to functional checks of the elevator, confirmed continuity and normal function. Additionally, the flight control lock was found on the floor near the rudder pedals on the left side of the cockpit. Due to a head injury sustained during the accident, the pilot was unable to recall most of the events that transpired during the accident. The pilot did state that he typically removed the control lock during the preflight inspection and that he would place it in his flight bag. He thought that a shoulder injury may have led to the control lock missing the flight bag, and why it was found behind the rudder pedals after the accident.

Review and analysis of a video that captured the airplane during its taxi to the runway showed that the elevator control position was similar to what it would be with the control lock installed. While the pilot and copilot reported that they did not observe the control lock installed during the takeoff, the position of the elevator observed on the video, the successful postaccident functional test of elevator, and the unsecured flight control lock being located behind the pilot’s rudder pedals after the accident suggest that the control anomaly experienced by the pilots may have been a result of the control lock remaining inadvertently installed and overlooked by both pilots prior to the takeoff.

According to the airframe manufacturer’s preflight and before takeoff checklists, the flight control lock must be removed during preflight, prior to engine start and taxi, and the flight controls must be checked prior to takeoff. Regardless of why the elevator control would not move during the takeoff, a positive flight control check prior to the takeoff should have detected any such anomaly. It is likely that the pilot failed to conduct a flight control check prior to takeoff. Further, the pilot failed to abort the takeoff at the first indication that there was a problem. Although delayed, the copilot’s decision to take control of the airplane and abort the takeoff likely mitigated the potential for more severe injury to the occupants and damage to the airplane.

Probable Cause: 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.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ERA21LA011
Status: Investigation completed
Duration: 2 years and 2 months
Download report: Final report

Sources:

https://www.wptv.com/news/region-n-palm-beach-county/small-plane-crashes-near-north-palm-beach-county-general-aviation-airport
https://nbc-2.com/news/2020/10/08/small-plane-carrying-7-people-crashes-in-north-palm-beach-county/
https://cbs12.com/news/local/plane-crashes-during-takeoff-in-north-palm-beach
https://www.wrtv.com/news/local-news/bartholomew-county/columbus-family-injured-in-palm-beach-county-florida-plane-crash-identified

NTSB
https://flightaware.com/live/flight/N8132Q
https://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=N8132Q

https://photos-e1.flightcdn.com/photos/retriever/22613dc7144fe12642d9c8a7bf394918c272ef3f (photo)
https://www.aircraft.com/aircraft/1295541/n8132q-1970-cessna-414

Location

Images:





Photos: NTSB

Revision history:

Date/timeContributorUpdates
08-Oct-2020 16:20 gerard57 Added
08-Oct-2020 16:45 gerard57 Updated [Time, Aircraft type, Phase, Source]
08-Oct-2020 17:39 Captain Adam Updated [Operator, Total occupants, Location, Phase, Nature, Source, Narrative]
08-Oct-2020 18:27 RobertMB Updated [Registration, Cn, Operator, Total fatalities, Other fatalities, Location, Phase, Nature, Departure airport, Destination airport, Source, Narrative]
08-Oct-2020 18:29 RobertMB Updated [Narrative]
08-Oct-2020 18:30 RobertMB Updated [Total fatalities]
08-Oct-2020 19:29 Geno Updated [Source, Narrative]
09-Oct-2020 06:55 Captain Adam Updated [Location, Narrative]
09-Oct-2020 22:52 RobertMB Updated [Destination airport, Source, Narrative]
10-Oct-2020 06:23 Anon. Updated [Source]
04-Nov-2020 11:40 Anon. Updated [Source, Narrative]
12-Jan-2021 01:08 Captain Adam Updated [Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org