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.
Santa Barbara, CA
The pilot reported that, after aligning the airplane with the runway centerline and adding full power for takeoff, the airplane accelerated and then began to veer left. The pilot immediately added right rudder to correct for the deviation, but the airplane did not respond to the control input. He then reduced power to abort the takeoff, but, seeing runway signs in his path, he added full power again in an attempt to get airborne to avoid colliding with the signs. After becoming airborne, the airplane impacted a sign with its right main landing gear and right stabilator, which resulted in substantial damage to the airplane. Neither the pilot nor a Federal Aviation Administration inspector, who examined the airplane after the accident, reported any pre-impact mechanical malfunctions or anomalies.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
The pilot reported that after aligning the airplane with the runway centerline and adding full power, the airplane accelerated and then began to veer to the left. The pilot further said that he immediately added right rudder to correct for the deviation but the airplane did not respond to the control input. The pilot stated that he then elected to abort the takeoff, but seeing runway signs in his path he added full power again in an attempt to get airborne to avoid colliding with the signs. After becoming airborne the airplane impacted an airport sign with its right main landing gear and right stabilator, which resulted in substantial damage to the airplane. Neither the pilot nor a Federal Aviation Administration inspector, who examined the airplane after the accident, reported any pre-impact mechanical malfunctions or anomalies. The pilot added that he was using runway 25 at the time of the accident, that the wind was 250 degrees at 8 knots, and that there were no gust reported.