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.
Ormond Beach, FL
The pilot stated that the flight proceeded to the destination airport and was cleared by air traffic control to land on runway 8. The flight turned from the downwind leg onto base, then onto final approach and with 30-degrees of flaps extended, attempted to maintain 61 knots for the practice short field landing. She began to flare but felt the main landing gear wheels "skid against the pavement" and the airplane then became airborne. She maintained the aft elevator input and again felt the main landing gear wheels skid on the runway and the airplane became airborne again. After the third touchdown the airplane remained on the runway and she taxied to the ramp. According to the NTSB "Pilot/Operator Aircraft Accident/Incident Report" form, witness reported seeing a flat approach, contact with the runway, then the airplane porpoised. The recommendations section of the report indicates that a go-around should have been performed upon first indication of a faulty approach.
The failure of the student pilot to initiate a recovery from the bounced landing resulting in a hard landing.
On October 21, 2006, about 1315 eastern daylight time, a Cessna 172S, N401ER, registered to Wells Fargo Bank Northwest NA Trustee, operated by Embry-Riddle Aeronautical University, bounced during landing at the Ormond Beach Municipal Airport, Ormond Beach, Florida. Visual meteorological conditions prevailed at the time and no flight plan was filed for the 14 CFR Part 91 instructional flight from Daytona Beach International Airport, Daytona Beach, Florida, to Ormond Beach Municipal Airport. The airplane was substantially damaged and the student pilot, the sole occupant, was not injured. The flight originated about 1245, from Daytona Beach International Airport. The pilot stated that the flight proceeded to the destination airport and was cleared by air traffic control to land on runway 8. The flight turned from the downwind leg onto base, then onto final approach and with 30-degrees of flaps extended, attempted to maintain 61 knots for the practice short field landing. She began to flare but felt the main landing gear wheels "skid against the pavement" and the airplane then became airborne. She maintained the aft elevator input and again felt the main landing gear wheels skid on the runway and the airplane became airborne again. After the third touchdown the airplane remained on the runway and she taxied to the ramp. According to the NTSB "Pilot/Operator Aircraft Accident/Incident Report" form, a witness reported seeing a flat approach, contact with the runway, then the airplane porpoised. The recommendations section of the report indicates that a go-around should have been performed upon first indication of a faulty approach.