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.
Bunn, NC
During the attempted landing, the airplane "floated some" and touched down on the 2,500-foot turf runway near the midpoint with insufficient distance remaining to stop. The pilot then increased engine power and aborted the landing but felt that the engine was not producing full power. The pilot maneuvered the airplane in an attempt to avoid trees beyond the departure end of the runway, but the airplane struck the trees in a level attitude, resulting in substantial damage to the fuselage, empennage, and both wings. A witness reported observing the airplane intermittently during the attempted landing and said that, when he first saw the airplane, it had traveled a significant distance down the runway. He then heard the airplane's engine power increase, watched as it climbed in a shallow right turn, and realized that the airplane would not be able to clear the 25-foot tall trees beyond the end of the runway. Both the witness and a weather reporting station 7 nautical miles from the accident site reported that an approximate 6-knot tailwind prevailed about the time of the accident. Examination of the airframe and engine found no evidence of any preimpact mechanical malfunctions or failures.
The pilot did not attain a proper touchdown point while attempting to land with a tailwind and delayed his decision to abort the landing.
The pilot intended to practice takeoffs and landings at several local airports, and entered the traffic pattern to land on runway 04, the 2,500-foot long, turf runway. During the attempted landing, the airplane "floated some" and touched down near the runway midpoint with insufficient distance remaining to stop. The pilot then increased engine power and aborted the landing, but felt that the engine was not producing full power. The pilot maneuvered the airplane in an attempt to avoid trees beyond the departure end of the runway, but subsequently struck the trees in a level attitude, resulting in substantial damage to the fuselage, empennage, and both wings. A witness reported intermittently observing the airplane during the attempted landing, and when he first saw the airplane, it had traveled a significant distance down the runway. He then heard the airplane's engine power increase, watched as it climbed in a shallow right hand turn, and realized that the airplane would not be able to clear the 25-foot tall trees beyond the end of the runway. The witness and a weather reporting station located 7 nautical miles from the accident site reported that an approximate 6-knot tailwind prevailed about the time of the accident. Federal Aviation Administration inspectors examined the airframe and engine following the accident, and found no evidence of any pre-impact mechanical malfunctions or failures.