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.
Searcy, AR
The experimental amateur-built airplane sustained substantial damage during a forced landing following an in-flight rudder cable failure. The pilot stated, " As I made my turn south (Final) applying right rudder the right rudder cable broke. Because of pressure being applied to both rudder pedals I inadvertently applied left rudder causing the aircraft to go into a death spiral. I applied full right [ailerons] but continued to spiral after three to five rotations I used basic spin recovery and was able to level the aircraft and maintain minimal control at about 250 ft [above ground level]. I landed in an empty lot which was not quite long enough for roll out and came to rest in a ditch ... ." Examination of the failed cable revealed the ends of the separation were frayed.
The frayed rudder cable that failed during the turn to final. A factor was the ditch the airplane encountered during the forced landing.
On July 24, 2003, about 0930 central daylight time, an experimental amateur-built Murch Rotec Rally 3, N317RE, piloted by a private pilot, sustained substantial damage during a forced landing following an in-flight rudder cable failure near Searcy, Arkansas. The personal flight was operating under 14 CFR part 91. Visual meteorological conditions prevailed at the time of the accident. No flight plan was on file. The pilot reported no injuries. The local flight departed from Searcy Municipal Airport, near Searcy, Arkansas, and was maneuvering in the traffic pattern at the time of the accident. The pilot stated: It was a cool, calm summer morning for July in Arkansas. I departed Searcy Municipal Airport (SRC) at 9:30 AM. The departure was to the south. I made a right hand turn to the west. Remaining in the traffic pattern at 1250 ft [mean sea level] I made a second turn to the right heading north. Just after turning east (base) I heard on my radio that a twin Jet was on its way in for landings at Searcy. I slowed and lingered on base for separation. As I made my turn south (Final) applying right rudder the right rudder cable broke. Because of pressure being applied to both rudder pedals I inadvertently applied left rudder causing the aircraft to go into a death spiral. I applied full right [ailerons] but continued to spiral after three to five rotations I used basic spin recovery and was able to level the aircraft and maintain minimal control at about 250 ft [above ground level]. I landed in an empty lot which was not quite long enough for roll out and came to rest in a ditch ... . A Federal Aviation Administration inspector examined the rudder cable separation. The cable separation appeared frayed.