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.
Akron, CO
The pilot reported that, while flying over the grass runway, it appeared "rough but serviceable." During landing, he found the surface was extremely rough with tall weeds. During the subsequent departure, acceleration was "less than normal" due to the vegetation. When the airplane reached the pilot's planned abort point for the runway, he realized that he had misjudged the abort point. He initially thought his selected abort point was about 800 to 1,000 ft before the end of the runway, but it was about 100 to 200 ft before the end of the runway. The airplane overran the runway, crossed a road, and struck a barbed wire fence. The airplane sustained substantial damage to the fuselage and left wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The Federal Aviation Administration Airport Facility Directory for the accident airport, in part, stated: "[Runways] not recommended for [takeoff or landing]."
The pilot’s improper preflight planning that did not identify the unserviceable runway; his subsequent decision to attempt to takeoff from the rough, grassy runway; and his selection of an abort point with insufficient runway remaining, which resulted in a runway overrun.
The pilot reported that, while flying over the grass runway, it appeared "rough but serviceable". During landing, he found the surface was extremely rough with tall weeds. During departure, acceleration was "less than normal" due to the vegetation. When the airplane reached the pilot's planned abort point, the pilot realized that he had misjudged the abort point for the runway. He initially thought his selected abort point was about 800 to 1,000 ft before the end of the runway, but, was about 100 to 200 ft before the end of the runway. The airplane overran the runway, crossed a road, and struck a barbed wire fence. The airplane sustained substantial damage to the fuselage and left wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The Federal Aviation Administration Airport Facility Directory for the accident airport, in part stated: "[Runways] not recommended for [takeoff or landing]."