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.
Sebastian, FL
The pilot stated that due to other traffic ahead in the airport traffic pattern, he purposely entered a high right base leg for runway 10, a 3,199-foot-long asphalt runway. The airplane remained high during the approach and the pilot attempted to land on the last one-half of the runway; however, the airplane was also too fast as the pilot had selected only 10 degrees of flap extension. The airplane subsequently touched down near the end of the runway, traveled over an approximate 500-foot grass area beyond the end of the runway, and struck a fence before coming to rest upright. Examination of the airplane by a Federal Aviation Administration inspector revealed substantial damage to the firewall. The inspector did not observe any preimpact mechanical malfunctions with the airplane, nor did the pilot report any. The recorded wind near the accident site, about the time of the accident, was from 040 degrees at 7 knots.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
The pilot stated that due to other traffic ahead in the airport traffic pattern, he purposely entered a high right base leg for runway 10, a 3,199-foot-long asphalt runway. The airplane remained high during the approach and the pilot attempted to land on the last one-half of the runway; however, the airplane was also too fast as the pilot had selected only 10 degrees of flap extension. The airplane subsequently touched down near the end of the runway, traveled over an approximate 500-foot grass area beyond the end of the runway, and struck a fence before coming to rest upright. Examination of the airplane by a Federal Aviation Administration inspector revealed substantial damage to the firewall. The inspector did not observe any preimpact mechanical malfunctions with the airplane, nor did the pilot report any. The recorded wind near the accident site, about the time of the accident, was from 040 degrees at 7 knots.