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.
Tuskegee, AL
The airplane had taken off to the north, on a runway that slopes upward, with power lines as an obstruction at the departure end of the runway. The turf runway was 1800 feet long. As the airplane started to climb, the landing gear struck the power lines, the airplane fell to the ground, caught on fire and burned. The pilot stated that he usually takes off to the south, but a 'tailwind' caused him to takeoff to the north. He further stated he started his takeoff run and the airplane '...didn't gain speed like it should have. He said he 'should have stopped [the] takeoff, [but] waited too late. Rotated with too low a airspeed, could not clear power lines, cut wire and went into trees.' In addition, the pilot told the FAA that he did not have any engine problems.
The pilot's failure to attain adequate airspeed, and his failure to abort the takeoff.
On August 2, 1998, about 1845 central daylight time, a Cessna 172F, N7884U, registered to a private individual, crashed near Tuskegee, Alabama, while on a Title 14 CFR Part 91 personal flight. Visual meteorological conditions were reported and no flight plan was filed. The airplane was destroyed. The private-rated pilot and one passenger reported minor injuries. The flight was originating from a private airstrip at the time. The airplane had taken off to the north, on a runway that slopes upward, with power lines as an obstruction at the departure end of the runway. As the airplane started to climb, the landing gear struck the power lines, the airplane fell to the ground, caught on fire and burned. The pilot stated that he usually takes off to the south, but a "tailwind" caused him to takeoff to the north. He further stated he started his takeoff run and the airplane "...didn't gain speed like it should have. [I] should have stopped [the] takeoff, waited too late. Rotated with too low a airspeed, could not clear power lines, cut wire and went into trees." In addition, the pilot told the FAA that he did not have any engine problems.