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.
Saluda, SC
The pilot stated that after arrival to the destination airport he overflew it and entered a left downwind leg of the airport traffic pattern for landing. He configured the airplane for landing then turned onto the base and final legs of the airport traffic pattern where he lowered full flaps maintaining a crosswind correction of right wing low and left rudder input. On short final he reduced power to idle and flared either too little or too late, after which the airplane bounced. With the airplane in a slight nose-up attitude, he believed he added power too quickly but did not recall adding right rudder input. The airplane violently and abruptly turned left, after which he was partially able to recover but not before flying away from the runway and impacting a chain link fence. The airplane then landed hard in an open area on the airport resulting substantial damage to both wings and the bottom of the fuselage. The pilot reported that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded a normal operation.
The pilot’s failure to maintain control of the airplane during an aborted landing, which resulted in a runway excursion, collision with a fence, and a hard landing .
The pilot stated that after arrival to the destination airport he overflew it and entered a left downwind leg of the airport traffic pattern for landing. He configured the airplane for landing then turned onto the base and final legs of the airport traffic pattern where he lowered full flaps maintaining a crosswind correction of right wing low and left rudder input. On short final he reduced power to idle and flared either too little or too late, after which the airplane bounced. With the airplane in a slight nose-up attitude, he believed he added power too quickly but did not recall adding right rudder input. The airplane violently and abruptly turned left, after which he was partially able to recover but not before flying away from the runway and impacting a chain link fence. The airplane then landed hard in an open area on the airport resulting substantial damage to both wings and the bottom of the fuselage. The pilot reported that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded a normal operation.