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.
St. Louis, MO
The pilot reported that while landing on a wet runway and as he applied brakes during the landing roll, the airplane began to hydroplane, and the nose landing gear collapsed. The airplane veered left and exited the side of the runway coming to a stop in the grass. The airplane sustained substantial damage to the engine mount. The pilot reported there were no preimpact mechanical failures or malfunctions with the airframe and engine that would have precluded normal operation. A review of the airplane’s maintenance records revealed that Piper Aircraft Service Bulletin (SB) 1103F (a recurring inspection of the engine mount for cracks every 100 hours) was complied with only once in the airplane’s service history, which was about 437 hours before the accident occurred. Based on the available information, it was undetermined if any preexisting defects in the engine mount contributed to nose landing gear collapse. The pilot reported the accident could have been prevented by “not applying brakes” and allowing a “continued roll out.”
Environmental issues-Physical environment-Runway/land/takeoff/taxi surface-Wet surface-Ability to respond/compensate
The pilot reported that while landing on a wet runway and as he applied brakes during the landing roll, the airplane began to hydroplane, and the nose landing gear collapsed. The airplane veered left and exited the side of the runway coming to a stop in the grass. The airplane sustained substantial damage to the engine mount. The pilot reported there were no preimpact mechanical failures or malfunctions with the airframe and engine that would have precluded normal operation. A review of the airplane’s maintenance records revealed that Piper Aircraft Service Bulletin (SB) 1103F (a recurring inspection of the engine mount for cracks every 100 hours) was complied with only once in the airplane’s service history, which was about 437 hours before the accident occurred. Based on the available information, it was undetermined if any preexisting defects in the engine mount contributed to nose landing gear collapse. The pilot reported the accident could have been prevented by “not applying brakes” and allowing a “continued roll out.”