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.
Falcon, CO
The pilot reported that the main runway was closed at the airport, so he planned to make a short-field landing on a perpendicular 2,084-ft-long runway (runway 8). During landing, the airplane "ended up short," and he attempted to go around, but he did not add power fast enough. The airplane impacted a construction barrier near the runway threshold, and the left main landing gear separated. The airplane sustained substantial damage to the left horizontal stabilizer and empennage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. Archived NOTAMs for the date of the accident stated the following: RWY 15/33 CLSD; RWY 08 CLSD TO LDG; RWY 26 CLSD EXC FSL. The airport manager reported that runway 15/33 was closed due to construction and that they issued a NOTAM with the intention that pilots could take off on runway 8 and conduct only full-stop landings on runway 26 to avoid construction equipment.
The pilot's failure to maintain a proper approach path and his delayed decision to go around, which resulted in impact with a construction barrier before the runway. Contributing to the accident was the pilot's decision to land on a runway closed for landing.
The pilot reported that the main runway was closed at the high-altitude destination airport, so he planned to make a short-field landing on a perpendicular 2,084 ft runway. During landing, the airplane "ended up short.,." and he attempted to go around, but he did not add power fast enough. The airplane impacted a construction barrier near the runway threshold and the left main landing gear separated. The airplane sustained substantial damage to the left horizontal stabilizer and empennage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The airport's automated weather observation station reported that, about 5 minutes after the accident, the wind was from 150° at 6 knots. The pilot landed the airplane on runway 08. Archived Notices to Airmen (NOTAMs) for the date of the accident stated that: RWY 15/33 CLSD RWY 08 CLSD TO LDG RWY 26 CLSD EXC FSL The airport manager reported that runway 15/33 was closed due to construction and they issued a NOTAM with the intention that pilots could take off on runway 8 and land on runway 26 to avoid construction equipment. He added that airport management had no issues if pilots landed on runway 8, as long as the landing facilitated a headwind and construction equipment was avoided. He reported that the NOTAM for runway 26 meant "closed except full stop landing."