Overall Trends
Total, fatal, and serious accidents in the selected range.
Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.
Fast key and full-text search with live filters, watches, and precise metadata.
Use quotes for exact phrase matches (for example "fuel selector valve").
Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.
Major cases, deep-report coverage, and investigation media across decades of NTSB history.
Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.
NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.
The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.
The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.
Pottsville, PA
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.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Attain/maintain not possible
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."