GAA18CA020
2017-10-22 · Pottsville, Pennsylvania, United States · None · 1 aircraft · Status: Completed
Airport ZER
Aircraft involved
Probable cause & findings
The failure of the right rudder cable and subsequent loss of directional control during landing.
Factual narrative
The pilot reported that, during approach, the automatic weather observation station at the destination airport reported that the wind was from 170° at 12 knots. He added that there was "very massive choppy wind, including what could have been windshear, updrafts, and downdrafts". During the landing roll on runway 11, a wind gust blew the airplane off the runway to the left. The pilot attempted to recover, but the airplane impacted a ditch. The airplane sustained substantial damage to the fuselage and right wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The Federal Aviation Administration (FAA) inspector reported that, during a postaccident examination, the rudder cable that passed along the left side of the fuselage was separated into three pieces. The rudder cable was covered in debris, which contained red fibers. The rudder cable was splayed and exhibited signatures consistent with tension overload. The airplane's illustrated parts catalog contained a diagram, titled "Rudder Control System Installation". This diagram displayed the cable along the left side of the fuselage cross over the right side of the airplane, in the tailcone section, and connect to the right side of the rudder horn, which provided right rudder authority. The airplane's most recent inspection was an annual, conducted 6 months prior to the accident flight. The FAA inspector interviewed the mechanic who performed the most recent annual inspection. During the interview, the mechanic reported that, during inspections, he uses manufacturer data and the FAA advisory circular, AC 43.13-1B. He further reported, multiple times, that he should probably "tighten up" his inspections. The FAA's advisory circular, AC 43.13-1B, titled "Acceptable Methods, Techniques, and Practices – Aircraft Inspection and Repair", contains a section titled "Cable System Inspection", which stated: "Aircraft cable systems are subject to a variety of environmental conditions and deterioration. Wire or strand breakage is easy to visually recognize. Other kinds of deterioration such as wear, corrosion, and/or distortion are not easily seen; therefore, control cables should be removed periodically for a more detailed inspection. At each annual or 100 hour inspection, all control cables must be inspected for broken wires strands. Any cable assembly that has one broken wire strand located in a critical fatigue area must be replaced." It further stated: "Close inspection in these critical fatigue areas, must be made by passing a cloth over the area to snag on broken wires. This will clean the cable for visual inspection, and detect broken wires if the cloth snags on the cable." The pilot reported that, during approach, the automatic weather observation station at the destination airport reported that the wind was from 170° at 12 knots. He added that there was "very massive choppy wind, including what could have been windshear, updrafts, and downdrafts." During the landing roll on runway 11, a wind gust blew the airplane off the runway to the left. The pilot attempted to recover, but the airplane impacted a ditch. The airplane sustained substantial damage to the fuselage and right wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The Federal Aviation Administration (FAA) inspector reported that a postaccident examination revealed that the rudder cable that passed along the left side of the fuselage was separated into three pieces. The rudder cable was covered in debris, which contained red fibers. The rudder cable was splayed and exhibited signatures consistent with tension overload. The airplane's illustrated parts catalog contained a diagram titled, "Rudder Control System Installation," which displayed the cable along the left side of the fuselage cross over the right side of the airplane, in the tailcone section, and connect to the right side of the rudder horn, which provided right rudder authority. The airplane's most recent inspection was an annual, which was conducted 6 months before the accident flight. The FAA inspector interviewed the mechanic who performed the most recent annual inspection, and the mechanic reported that, during inspections, he used manufacturer data and FAA Advisory Circular, AC 43.13-1B, "Acceptable Methods, Techniques, and Practices – Aircraft Inspection and Repair." He further reported, multiple times, that he should probably "tighten up" his inspections. AC 43.13-1B contained a section titled, "Cable System Inspection," which stated the following: "Aircraft cable systems are subject to a variety of environmental conditions and deterioration. Wire or strand breakage is easy to visually recognize. Other kinds of deterioration such as wear, corrosion, and/or distortion are not easily seen; therefore, control cables should be removed periodically for a more detailed inspection. At each annual or 100-hour inspection, all control cables must be inspected for broken wire strands. Any cable assembly that has one broken wire strand located in a critical fatigue area must be replaced." It further stated the following: "Close inspection in these critical fatigue areas, must be made by passing a cloth over the area to snag on broken wires. This will clean the cable for visual inspection, and detect broken wires if the cloth snags on the cable." It is likely that the red fibers found on the rudder cable were from a red cloth used to inspect the rudder cable during the annual inspection. It is also likely that, sometime during the flight or landing sequence, the right rudder cable separated, which subsequently restricted the pilot's ability to recover from the loss of control during landing. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Aircraft-Aircraft systems-Flight control system-Rudder control system-Failure - C
- — Environmental issues-Conditions/weather/phenomena-Wind-Windshear-Effect on operation
- — Environmental issues-Conditions/weather/phenomena-Wind-Updraft-Effect on operation
- — Environmental issues-Conditions/weather/phenomena-Wind-Downdraft-Effect on operation
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Attain/maintain not possible
Verbatim from NTSB's published report. Source file
NTSB_2017_GAA18CA020.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (stall, loss of control). All research papers
- NTSB Aircraft Accident Reports 2010 · Accident report Loss of Control on Approach — Colgan Air Flight 3407
Colgan Air 3407 / Continental Connection (Q400) Buffalo NY, February 12, 2009 — 50 fatalities. Definitive investigation of the Colgan 3407 stall-stick-pusher crash on approach to Buffalo.
- Semantic Scholar 2016 · Article (Interacción) Trajectory Recovery System: Angle of Attack Guidance for Inflight Loss of Control
This paper describes the design and development of an ecological display to aid pilots in the recovery of an In-Flight Loss of Control event due to a Stall (ILOC-S).
- NASA NTRS 2026 · Conference Paper Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER) A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- SKYbrary (Eurocontrol) 2024 · SKYbrary article Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
- Semantic Scholar 2024 · Article (International Conference on Networking and Services) Risk Assessment of Loss of Control In-Flight Trajectories for Urban Air Mobility Safety
In Urban Air Mobility (UAM), maintaining a minimum separation between aircraft is a safety requirement, which becomes challenging amidst congested air traffic and off-nominal conditions, such as Loss …