Cessna 414 N8132Q
8 October 2020 · West Palm Beach, Florida, United States · Serious injuries
Summary
On 8 October 2020 at about 15:15 local time, a Cessna 414 registered N8132Q, operated by Sierra AE, LLC, was involved in an accident near West Palm Beach, Florida, United States. 7 people were on board and 7 were seriously injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 15:15
- Classification
- Accident
- Location
- West Palm Beach, Florida, United States
- Nearest airport
- North Palm Beach County Genera (F45)
- Coordinates
- 26.8405, -80.2172
- Aircraft
- Cessna 414
- Registration
- N8132Q
- Category
- Airplane
- Year built
- 1997
- Engines
- 2
- Operator
- Sierra AE, LLC
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Unknown → Claxton
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Day
- NTSB number
- ERA21LA011
People
7 people were seriously injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 7 | 0 | 7 | 0 | 0 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
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.
Quoted verbatim from the NTSB record.
Other Cessna 414 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 30 Aug 2020 | Cessna 414 | Ray, Michigan, United States | - | Minor injuries | - |
| 28 Jan 2021 | Cessna 414 | Guerrero Negro, Mexico | - | No injuries | - |
| 3 Feb 2019 | Cessna 414 | Yorba Linda, California, United States | - | Fatal | 1 |
| 29 Oct 2019 | Cessna 414 | Colonia, New Jersey, United States | - | Fatal | 1 |
| 19 Jun 2022 | Cessna 414 | Monongahela, Pennsylvania, United States | Ertel Caiolinn Chelsea | No injuries | - |
| 12 Apr 2022 | Cessna 414A | Herzogenaurach, Germany | - | No injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 19 Aug 2020 | Piper PA32 | Tallahassee, Florida, United States | - | Minor injuries | - |
| 25 Jun 2020 | Bell 206 | Coconut Creek, Florida, United States | Hmc Lift Llc | Serious injuries | - |
| 15 Jun 2020 | Piper PA46 | Williston, Florida, United States | - | No injuries | - |
| 3 May 2020 | Airbus Helicopters AS350 | Clewiston, Florida, United States | MacNeil Aviation LLC | No injuries | - |
| 30 Jan 2020 | Piper PA28 | Naples, Florida, United States | Apflight Llc | No injuries | - |
| 31 Dec 2020 | Cessna 501 | Opa Locka, Florida, United States | Interstellar Air LLC | No injuries | - |