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.
East Killingly, CT
After conducting maneuvers during a flight review, the flight instructor reduced the engine power to idle in order to simulate an engine failure. The pilot/owner subsequently picked a field to perform the simulated forced landing to, and completed the emergency checklist. About 100 feet above the ground, the pilot asked the flight instructor if he could "have the power back." The flight instructor agreed, and the pilot subsequently increased engine power. During the climb, the airplane struck trees, then impacted the ground. The pilot reported no mechanical problems associated with the airplane, and reported that the engine was operating normally.
The flight instructor's delayed decision to discontinue the simulated forced landing, which resulted in a collision with trees.
After conducting maneuvers during a flight review, the flight instructor reduced the engine power to idle in order to simulate an engine failure. The pilot/owner subsequently picked a field to perform the simulated forced landing to, and completed the emergency checklist. About 100 feet above the ground, the pilot asked the flight instructor if he could "have the power back." The flight instructor agreed, and the pilot subsequently increased engine power. During the climb, the airplane struck trees, then impacted the ground. The pilot reported no mechanical problems associated with the airplane, and reported that the engine was operating normally.