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.
Westminster, MD
The flight instructor reported that during a dual training flight with a student pilot, they returned to their base airport and practiced two landings without incident. During the third landing, the student pilot applied too much elevator back pressure in the landing flare, and the instructor stated “power.” Subsequently, the student pilot applied full power to go-around, instead of a “slight amount of power” which was what the flight instructor expected. After the application of full power, the airplane drifted beyond the right side of the runway, was near the aerodynamic stall speed, and was approaching trees ahead. The flight instructor reported that she “eventually” was able to take the flight controls, where she reduced power to idle, lowered the nose of the airplane, and landed in a down sloping grass area beyond the end of the runway. During the runway excursion, the airplane impacted trees, which resulted in substantial damage to the right wing and fuselage. Neither pilot reported any preimpact mechanical malfunctions or failures that would have precluded normal operation with the airplane.
The student pilot’s loss of control during a go-around and the delayed remedial action initiated by the flight instructor, which resulted in a runway excursion and collision with trees.
The flight instructor reported that during a dual training flight with a student pilot, they returned to their base airport and practiced two landings without incident. During the third landing, the student pilot applied too much elevator back pressure in the landing flare, and the instructor stated “power.” Subsequently, the student pilot applied full power to go-around, instead of a “slight amount of power” which was what the flight instructor expected. After the application of full power, the airplane drifted beyond the right side of the runway, was near the aerodynamic stall speed, and was approaching trees ahead. The flight instructor reported that she “eventually” was able to take the flight controls, where she reduced power to idle, lowered the nose of the airplane, and landed in a down sloping grass area beyond the end of the runway. During the runway excursion, the airplane impacted trees, which resulted in substantial damage to the right wing and fuselage. Neither pilot reported any preimpact mechanical malfunctions or failures that would have precluded normal operation with the airplane.