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.
Mesa, AZ
The pilot reported that, he intended to do touch-and-goes in the local traffic pattern. While on the downwind leg, the air traffic controller cleared him to land. During the landing roll, past the halfway point on the runway, he increased the engine power to full to takeoff and told the controller that he was doing a "go-around". The controller immediately instructed him to exit the runway on to the last taxiway so the pilot "cut the entire power", applied brakes and full right rudder, but the airplane skidded, exited the runway and impacted a concrete barrier. The airplane sustained substantial damage to the forward, lower fuselage. The flight safety officer reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The pilot added that he wanted to do touch and goes but did not accurately communicate his intentions to the air traffic controller.
The pilot's decision to abort a go-around with insufficient runway remaining to safely stop the airplane, which resulted in a loss of control, runway excursion and impact with a concrete barrier.
The pilot reported that, he intended to do touch-and-goes in the local traffic pattern. While on the downwind leg, the air traffic controller cleared him to land. During the landing roll, past the halfway point on the runway, he increased the engine power to full to takeoff and told the controller that he was doing a "go-around". The controller immediately instructed him to exit the runway on to the last taxiway so the pilot "cut the entire power", applied brakes and full right rudder, but the airplane skidded, exited the runway and impacted a concrete barrier. The airplane sustained substantial damage to the forward, lower fuselage. The flight safety officer reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The pilot added that he wanted to do touch and goes but did not accurately communicate his intentions to the air traffic controller.