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.
Minneapolis, MN
The student pilot said that the airplane bounced during landing. 'To avoid continued bounces, I decided to go-around. When I added power, the plane turned, heading off the runway. I tried to regain airspeed with full power.' The student pilot said that he did not have sufficient altitude to clear some buildings on the northwest side of the airport. He flew the airplane between two buildings. 'It [the airplane] appears to have caught a wire drawn between the buildings. The plane pitched down, hitting two fences. The airplane came to rest in a group of trees.' Examination of the wreckage revealed no anomalies.
the student pilot's improper recovery from a bounced landing and failure to maintain proper runway alignment during a go-around (aborted landing). Factors relating to the accident were: the pilot's improper flare for landing, the reduced light conditions at dusk, and the obstruction (static wire) that was encountered during the go-around.
On June 16, 1997, at 1938 central daylight time (cdt), a Piper PA-38-112, N2455F, operated by a student pilot, sustained substantial damage when on a go-around from a bounced landing, the airplane struck a wire. The airplane subsequently impacted into a field. Visual meteorological conditions prevailed at the time of the accident. The personal flight was being conducted under 14 CFR Part 91. A flight plan was not on file. The student pilot reported no injuries. The local flight originated at Minneapolis, Minnesota, at 1930 cdt. In his written statement, the student pilot said that the airplane bounced during landing. "To avoid continued bounces, I decided to go-around. When I added power, the plane turned, heading off the runway. I tried to regain airspeed with full power." The student pilot said that he did not have sufficient altitude to clear some buildings on the northwest side of the airport. He flew the airplane between two buildings. "It [the airplane] appears to have caught a wire drawn between the buildings. The plane pitched down, hitting two fences. The airplane came to rest in a group of trees." The Federal Aviation Administration (FAA) inspector who examined the wreckage at the site found the airplane resting in a field on the west side of an airport perimeter road. The inspector observed several propeller strikes in the road crossing from east to west. Damage was observed to a 3/8-inch rusted static wire located 150 feet east of the accident site. Both of the airplane's wings had broken off at the wing roots. The aft fuselage and empennage were twisted to the left. The airplane's nose gear was bent aft and upward. The airplane's firewall was bent aft. The propeller fittings were sheared at the flange. Both propeller blades were pealed rearward, and showed torsional bending and chordwise scratching. Flight control continuity was confirmed. Examination of the engine, engine controls and other airplane systems revealed no anomalies.