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.
Miami, FL
The solo student pilot reported that after a normal taxi and run-up, he aligned the airplane on the runway centerline and started the takeoff roll. He further reported that he attempted to rotate the airplane at 50 knots and then again at 65 knots, but the airplane "couldn't takeoff." The student pilot subsequently reduced the power to idle and applied the brakes to abort the takeoff. During the aborted takeoff, the airplane veered off the runway to the left and encountered high grass and a water retention lake about 635 feet from the runway centerline. The student pilot reported that the airplane "wouldn't respond" to his control inputs during the aborted takeoff. The left wing sustained substantial damage. The operator reported in the National Transportation Safety Board Pilot/ Operator Aircraft Accident Report that the student pilot "rotated too early and got fixated on the airspeed indicator. Then the left brake was touched causing the airplane to veer to the left." The Federal Aviation Administration Aviation Safety Inspector reported that he completed a postaccident examination of the airplane and found that the brakes were functional and confirmed flight control continuity.
The student pilot's failure to maintain directional control during the aborted takeoff, which resulted in a runway excursion.
The solo student pilot reported that after a normal taxi and run-up, he aligned the airplane on the runway centerline and started the takeoff roll. He further reported that he attempted to rotate the airplane at 50 knots and then again at 65 knots, but the airplane "couldn't takeoff." The student pilot subsequently reduced the power to idle and applied the brakes to abort the takeoff. During the aborted takeoff, the airplane veered off the runway to the left and encountered high grass and a water retention lake about 635 feet from the runway centerline. The student pilot reported that the airplane "wouldn't respond" to his control inputs during the aborted takeoff. The left wing sustained substantial damage. The operator reported in the National Transportation Safety Board Pilot/ Operator Aircraft Accident Report that the student pilot "rotated too early and got fixated on the airspeed indicator. Then the left brake was touched causing the airplane to veer to the left." The Federal Aviation Administration Aviation Safety Inspector reported that he completed a postaccident examination of the airplane and found that the brakes were functional and confirmed flight control continuity.