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.
Reidsville, NC
The pilot circled the airport twice, and then he entered the traffic pattern for a landing. He realized that he was landing long so he aborted the landing and initiated a go around. During the go around, the aircraft's tail section struck the top of a tree, 300 yards from the edge of the runway. According to an FAA inspector, the pilot was attempting to land at an unfamiliar grass strip.
The pilot's delay in the initiation of a go-around, and his failure to maintain obstacle (tree) clearance.
On September 25, 1998, about 1725 eastern daylight time, a Cessna 152, N152DD, registered to a private owner, crashed near Reidsville, North Carolina, while on a Title 14 CFR Part 91 personal flight. Visual meteorological conditions were reported and no flight plan was filed. The airplane was substantially damaged. The private-rated pilot reported no injuries. The flight had originated from Burlington, North Carolina, about 1615. The pilot stated he flew to Warfield, circled two times and then entered the pattern for a landing. The pilot then stated he, "...made a long approach to the landing field but as soon as I realized that the paved surface was not long enough and buildings and an aircraft were at the end of the runway and having not touched down yet, I attempted to abort the landing and make a go around." After clearing the aircraft, buildings, and power lines, the pilot stated "...the aircraft tail section struck the top of a tree which threw me into the tree and suddenly the flight was terminated." The FAA inspector reported that the pilot was "attempting to land at an unfamiliar grass strip." He made two passes over the field and on the third approach he "overshot" the runway. Just before touchdown the pilot realized he was "too far down the runway for a safe landing." The pilot attempted a go around, applied power to the engine, and climbed over trees at the edge of the runway. According to the FAA inspector, "...the pilot stalled the aircraft due to high angle of attack and full flaps. Aircraft came in contact with tree 300 yards from edge of runway."