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.
Benson, AZ
The pilot stated that, as he taxied the trike onto the runway and toward the centerline, it encountered a lateral crack across the runway pavement, which caused a noticeable and sharp movement through the foot controls; he felt no other anomalies. He lined the trike on the runway centerline and began the takeoff roll. The trike struck another crack and veered to the right. He attempted to correct back to the runway centerline without success. The trike rolled up on its left side, causing damage to the left wing's keel tube, the control A-frame, left leading edge spar, and sail cloth. The pilot reported to the Federal Aviation Administration (FAA) that he wanted to go out on one last flight before the runway was closed for repairs. According to the FAA airworthiness inspector who responded to the accident, the crack in the runway that the trike traversed was about 4 to 5 inches wide and at least 1 to 2 inches deep. The city commenced planned runway repairs several days after the accident.
The pilot's inadequate evaluation of the runway condition and failure to maintain directional control during takeoff.
The pilot stated that as he taxied onto the runway and toward the centerline, the trike encountered a lateral crack across the runway pavement, which caused a noticeable and sharp 'wiggle' through the foot controls; he felt no other anomalies. He lined the trike on runway centerline and readied the trike for takeoff. During the takeoff roll, the trike struck another crack, and began to veer to the right. He attempted to correct back to the runway centerline without success. The trike rolled up on its left side, causing damage to the left wings' keel tube, the control A-frame, left leading edge spar, and sail cloth. The pilot reported to the Federal Aviation Administration (FAA) that he wanted to go out on one last flight before the runway was closed for repairs. According to the FAA airworthiness inspector who responded to the airport, the crack in the runway that the trike traversed was about 4 to 5 inches wide and at least 1 to 2 inches deep. The city commenced planned runway repairs on November 1, 2010.