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.
Saint Petersburg, FL
The student pilot stated that after takeoff during his second supervised solo flight, he remained in the traffic pattern and landed uneventfully. During the landing roll he elected to perform a touch-and-go landing and applied power for takeoff. Immediately after adding power, the airplane turned left. He applied right rudder to correct the left turn but then decided to perform a full stop landing. He applied the brakes in an effort to keep the airplane on the runway, and reduced power before the airplane departed the runway, and went into water while traveling about 30 knots. The student pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The student's certified flight instructor stated that after veering to the left, the airplane exited the runway, crossed a perpendicular runway, and then impacted a ditch at which time he heard power applied. He then observed the airplane travel into the water and ran to the airplane to assist his student. Postaccident inspection of the flight controls revealed no evidence of preimpact failure or malfunction. The airplane sustained substantial damage to the firewall and fuselage.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
The student pilot stated that after takeoff during his second supervised solo flight, he remained in the traffic pattern and landed uneventfully, but during the landing roll elected to perform a touch-and-go landing and applied power. Immediately after adding power, the airplane turned left and he used rudder to correct the left turn but then decided to perform a full stop landing. He applied the brakes in an effort to keep the airplane on the runway, and reduced power, then added a little power inadvertently because he was nervous, then reduced power. The airplane departed the runway, and went into water while traveling about 30 knots. The student pilot further stated there was no preimpact mechanical failure or malfunction. The students’ certified flight instructor stated that after veering to the left, the airplane exited the runway onto grass, crossed runway 25, and then went into a ditch at which time he heard power applied. He then watched the airplane travel into the water and ran to the airplane to assist his student. Postaccident inspection of the flight controls by a Federal Aviation Administration airworthiness inspector revealed no evidence of preimpact failure or malfunction.