FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA21LA011 · Cessna 414

8 Oct 2020 · West Palm Beach, FL, United States

Sierra AE Cessna 414 · Accident: runway excursion during takeoff

From an unrecorded airport to Claxton Evans County Airport (CWV)

Report a problem

Event

NTSB case
ERA21LA011
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 414

Aircraft type
Cessna 414
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N8132Q
Operator
Sierra AE
Onboard fatalities
Unknown
Route
From not recordedTo Claxton Evans County Airport (CWV), Claxton, GA
Aircraft age
About 23 years (built 1997)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Takeoff · rejected takeoff
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Runway excursion
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

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.

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA21LA011
Event ID
20201008102116
Case number
ERA21LA011
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 80110c35c6c763e7619ea55ebf0a9e99f8733b5809d4043e9e39ac305c2b3e91; retrieved 2026-09-16T13:12:42.807Z.