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.
Williamsburg, VA
The solo student pilot reported that during a day visual meteorological condition flight, in the landing flare he saw a deer where he intended to touch down. He further reported that he banked to the right and applied power to go-around, but during the turn to the right he was unable to clear a line of trees in his flight path. The student pilot reported that the landing gear "scraped" one line of trees, and in order to avoid a thicker line of trees ahead, he forced the airplane down into a marsh area. The fuselage and both wings sustained substantial damage. The pilot did not report any mechanical malfunctions or failures with the airplane that would have precluded normal operation. During a postaccident interview with an airport representative, he reported that the airport does not a have a perimeter fence. The Federal Aviation Administration Chart Supplement airport page for the accident airport in part states: "Deer and birds on and invof [in the vicinity of] arpt."
An evasive maneuver during the landing flare to avoid deer on the runway, which resulted in a collision with trees and terrain during a go-around. Contributing to the accident was the lack of an airport perimeter fence.
The solo student pilot reported that during a day visual meteorological condition flight, in the landing flare he saw a deer where he intended to touch down. He further reported that he banked to the right and applied power to go-around, but during the turn to the right he was unable to clear a line of trees in his flight path. The student pilot reported that the landing gear "scraped" one line of trees, and in order to avoid a thicker line of trees ahead, he forced the airplane down into a marsh area. The fuselage and both wings sustained substantial damage. The pilot did not report any mechanical malfunctions or failures with the airplane that would have precluded normal operation. During a postaccident interview with an airport representative, he reported that the airport does not a have a perimeter fence. The Federal Aviation Administration Chart Supplement airport page for the accident airport in part states: "Deer and birds on and invof [in the vicinity of] arpt."