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.
St. Petersburg-Clearwater, FL
The pilot said that before he departed, he tested the airplane’s brakes and they functioned normally. He then departed, made one circuit in the traffic pattern, and landed about 500 to 1,000 ft beyond the first intersection located at the approach end of the 9,730-ft-long runway. The pilot said the brakes were not working during the landing roll-out and he was unable to stop or slow on the remaining runway. The pilot veered the airplane off the left side of the runway, traveled another 1,800 ft and impacted the airport’s perimeter fence resulting in substantial damage to the airplane’s fuselage. A postaccident examination of the airplane’s brakes revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation at the time of the accident.
The pilot’s inability to stop the airplane on the available runway, which resulted in a runway excursion and collision with an airport perimeter fence.
The pilot said that before he departed, he tested the airplane’s brakes and they functioned normally. He then departed, made one circuit in the traffic pattern, and landed about 500 to 1,000 ft beyond the first intersection located at the approach end of the 9,730-ft-long runway. The pilot said the brakes were not working during the landing roll-out and he was unable to stop or slow on the remaining runway. The pilot veered the airplane off the left side of the runway, traveled another 1,800 ft and impacted the airport’s perimeter fence resulting in substantial damage to the airplane’s fuselage. A postaccident examination of the airplane’s brakes revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation at the time of the accident.