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.
Concord, NC
The pilot initiated the landing flare at idle or very low power, and the airplane bounced about four times. Each bounce was higher and more pronounced than the previous one. The pilot stated that he thought the bounces would stop, and he concentrated on keeping the airplane as straight as possible on the runway. After the third or fourth bounce, the nosewheel tire blew, and the propeller struck the ground. The airplane came to a stop in the center of the runway, and the pilot shut down the engine. The pilot stated that, after the accident, he flew with a flight instructor and learned what a porpoise condition is, how to recognize it, and how to recover the airplane from it.
The pilot's improper flare during touchdown and failure to properly recover from a bounced landing, which resulted in a loss of control and inflight collision with the runway. A factor was the pilot did not understand the porpoise condition during landing.
On March 8, 2003, at 2015 eastern standard time, a Cessna 172P, N52546, registered to ISO Aero Service, Inc., and operated by the private pilot, collided with the runway during a bounced landing at Concord Regional Airport in Concord, North Carolina. The personal flight was operated under the provisions of Title 14 CFR Part 91 with a visual flight rules plan filed. Visual meteorological conditions prevailed. The private pilot and the passenger were not injured, and the airplane sustained substantial damage. The local flight originated in Concord, North Carolina, about 1915. The pilot was cleared to land on runway 20 at Concord Regional Airport in Concord, North Carolina. The pilot stated the approach was normal and on glideslope at 65 knots with 20 degrees of flaps. He stated he performed the landing flare at idle or very low power, and the airplane bounced. The pilot stated that, after the second bounce, "the characteristic of the plane seemed to change with the bounces becoming higher and more pronounced than the previous ones." The pilot stated he thought the bounces would stop, and he concentrated on keeping the airplane as straight as possible on the runway. After the third or fourth bounce, the nosewheel tire blew, and the propeller struck the ground. The airplane came to a stop in the center of the runway, and the pilot shut down the engine. Examination of the airplane revealed buckling of the right side of the fuselage near the main landing gear strut, buckling of the firewall near the lower right engine mount, buckling of the floor, damage to the nose gear, and damage to both propeller blade tips. The pilot stated that, after the accident, he flew with a flight instructor and learned what a porpoise condition is, how to recognize it, and how to recover the airplane from it.