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.
Park Rapids, MN
The pilot reported that he completed a full preflight inspection of the airplane with no issues noted, including inspecting all the flight control surfaces. During the run-up, the pilot checked all the flight controls and he noted they “all checked perfect.” The pilot was operating at a remote airport that was surrounded by pine trees, about 90 ft tall, on all sides. The takeoff roll from the snow-covered runway was “normal” and about 150 ft agl, the airplane “started turning/pulling left” in a descending turn. The pilot attempted to correct the turn and descent to no avail. The pilot decided to continue to use engine power until the airplane impacted trees. The airplane impacted several trees and came to rest nose down. The pilot was able to egress from the airplane without further incident. The airplane sustained substantial damage to the fuselage, both wings, and the engine mount. The pilot reported there were no preimpact mechanical malfunctions or failures with the airframe or the engine that would have precluded normal operation. A postaccident examination of the airframe established flight control continuity.
The pilot’s failure to maintain directional control and terrain clearance during initial climb, that resulted in an impact with trees and terrain.
The pilot reported that he completed a full preflight inspection of the airplane with no issues noted, including inspecting all the flight control surfaces. During the run-up, the pilot checked all the flight controls and he noted they “all checked perfect.” The pilot was operating at a remote airport that was surrounded by pine trees, about 90 ft tall, on all sides. The takeoff roll from the snow-covered runway was “normal” and about 150 ft agl, the airplane “started turning/pulling left” in a descending turn. The pilot attempted to correct the turn and descent to no avail. The pilot decided to continue to use engine power until the airplane impacted trees. The airplane impacted several trees and came to rest nose down. The pilot was able to egress from the airplane without further incident. The airplane sustained substantial damage to the fuselage, both wings, and the engine mount. The pilot reported there were no preimpact mechanical malfunctions or failures with the airframe or the engine that would have precluded normal operation. A postaccident examination of the airframe established flight control continuity.