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.
Crystal River, FL
The pilot stated the approach as well as the landing flare/touchdown at Crystal River Airport, was normal, but about 50 feet after the initial touchdown the airplane suddenly veered to the left. The aircraft departed the left side of the runway, crossed a grass median and taxiway, coming to rest in a ditch, incurring structural damage. An FAA inspector who responded to the accident stated that the accident airplane made tire skid marks 3000 feet down the runway in the vicinity of a taxiway entrance/exit to the runway, and an examination of the accident aircraft's brake system revealed no anomalies.
The pilots failure to maintain directional control during the landing rollout, which resulted in the airplane departing the runway and incurring damage.
On May 8, 2004, about 1400 eastern daylight time, a Beech A23A, N3659Q, registered to and operated by a private individual, veered off the runway during landing rollout at Crystal River Airport, Crystal River, Florida, while on a Title 14 CFR Part 91 personal flight. Visual meteorological conditions prevailed, and no flight plan was filed. The aircraft received substantial damage and the private-rated pilot and one passenger were not injured. The flight originated the same day, from Pilot Country Airport, Spring Hill, Florida, about 1250. The pilot stated that while landing at Crystal River Airport, after a normal landing flare/touchdown and initial rollout, about 50 feet beyond his touchdown point the airplane suddenly veered to the left, departing the runway. He stated that he attempted to use the right brake and nose wheel steering to control the airplane, but it seemed that the right brake either "locked up" or provided no braking at all, and the airplane exited the runway incurring damage. An FAA inspector who responded to the accident, stated that the airplane departed the runway at about 3,000 feet down the landing runway in the vicinity of a taxiway entrance/exit to the runway. He further stated that after the airplane departed the runway, it impacted a runway sign, crossed a grass median and a taxiway, and came to rest in a ditch about a 100 yards from the runway. The inspector further stated that he examined the accident aircraft's brake system, and no anomalies were found.