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.
Raleigh, NC
According to the pilot, after returning from a cross-country flight they were conducting a night landing on runway 32. After landing on the runway, the airplane bounced and the pilot added full power, and started a right climbing turn. After seeing another airplane on short final approach to runway 23L, the pilot elected to continue the right climbing turn. At this point the pilot noticed that the airspeed had dropped to 40 knots. The airplane collided with trees.. The post-accident examination of the airplane revealed the nose of the airplane was crushed and displaced aft towards the firewall. The right wing assembly displayed leading edge crush damage, and separated at the wing root. The left wing assembly was buckled and displaced aft. The vertical and horizontal stabilizers were buckled and twisted. The empennage was buckled, and no flight control anomalies with the airplane were reported by the pilot prior to the accident.
The pilot's failure to maintain adequate obstacle clearance during initial climb, which resulted in an in-flight collision with trees
On May 26, 2005, at 2205 eastern daylight time, a Cessna 172, N496AC, registered to and operator by Flightgest Incorporated, collided with trees during climb out at Raleigh Durham International Airport, Raleigh, North Carolina. The personal flight was operated under the provisions of Title 14 CFR Part 91 with no flight plan filed. Visual meteorological conditions prevailed at the time of the accident. The private pilot and passenger were uninjured, and the airplane sustained substantial damage. The flight fight departed Raleigh Durham International Airport, Raleigh, North Carolina on May 26, 2005 at 1900. According to the pilot, after returning from a cross-country flight they were conducting a night landing on runway 32. After landing on the runway the airplane bounced continuously down the runway. The pilot added full power, climbed out and made a 90-degree climbing right turn to avoid runway 23L. Another 90-degree right turn was initiated when the pilot observed an airplane on short final for runway 23L. As the airplane climbed out the airspeed dropped to 40 Knots. The pilot lowered the nose in an attempt to regain airspeed. After lowering the nose the pilot observed trees ahead of the airplane and attempted to climb above the trees but was unable to do so. The pilot stated "the airplane collided with trees." Post accident examination of the airplane revealed the nose of the airplane was crushed and displaced aft towards the firewall. The right wing assembly displayed leading edge crush damage, and separated at the wing root. The left wing assembly was buckled and displaced aft. The vertical and horizontal stabilizers were buckled and twisted. The empennage was buckled. No flight control anomalies were reported by the pilot prior to the accident.