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.
Wilkes-Barre, PA
The student pilot contacted air traffic control (ATC), and was instructed to enter a right downwind for runway 4, a 7,501-foot-long, 150-foot-wide, asphalt runway. Shortly thereafter, the airplane's radio's stopped working. The student pilot attempted to troubleshoot the problem, and was able to receive, but not transmit over the radio. He elected to land on runway 4, however, he overheard ATC clear another airplane to land, that was on a 5 mile final approach. The student pilot stated that he was "nervous" about the other airplane, turned a very early base leg, and approached "high and fast." The airplane contacted the runway hard, and began to bounce. It then departed the right side of the runway. Examination of the airplane, which included a radio check, did not reveal any discrepancies. A weather observation taken at the airport, about the time of the accident, included winds from 340 degrees at 8 knots.
The student pilot's improper flare and improper recover from a bounced landing. Factors in this accident were the crosswind condition and the partial failure of the airplane's transceiver, as reported by the pilot.
On August 8, 2004, about 1445 eastern daylight time, a Cessna 172P, N4599D, was substantially damaged while landing at the Wilkes-Barre-Scranton International Airport (AVP), Wilkes-Barre, Pennsylvania. The certificated student pilot was not injured. Visual meteorological conditions prevailed, and a visual flight rules flight plan was filed for the solo instructional flight conducted under 14 CFR part 91. The student pilot stated that he contacted air traffic control (ATC), and was instructed to enter a right downwind for runway 4, a 7,501-foot-long, 150-foot-wide, asphalt runway. Shortly thereafter, the airplane's radio stopped working. The student pilot attempted to troubleshoot the problem, and was able to receive, but not transmit. He elected to land on runway 4, however, he overheard ATC clear another airplane to land, that was on a 5 mile final approach. The student pilot stated that he was "nervous" about the other airplane, turned a very early base leg, and approached "high and fast." The airplane contacted the runway hard, and began to bounce. It then departed the right side of the runway. Examination of the airplane, which included a radio check, by a Federal Aviation Administration inspector, did not reveal any discrepancies. The student pilot reported 72.5 hours of total flight experience, all in the same make and model as the accident airplane, which also included 10.8 hours of solo flight experience. A weather observation taken at AVP, at 1454, included winds from 340 degrees at 8 knots.