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.
Winder, GA
The pilot reported that, during a night flight, while lowering the flaps for landing, the cockpit lights turned off. He attempted to turn the lights back on to no avail. He added that the precision approach path indicator (PAPI) lights were off and that he could not get the runway lights to turn on either. As he was landing past "the first arrow in front [chevron in the displaced threshold]," he heard a "thump." He taxied the airplane to the ramp without further incident. The passenger, an airframe and powerplant mechanic, reported that, during approach after the cockpit lights went out, he used his flashlight to light up the cockpit. He was unable to correct the panel lights but observed that the runway lights were "bright." He added that, during the landing, he felt the "bottom drop out" and that the airplane landed hard and bounced. Postaccident examination revealed that the right horizontal stabilator sustained substantial damage. The pilot added that he and the passenger went to the beginning of the approach runway and found pieces of broken runway lights. Archived NOTAMs for the date of the accident stated that: RWY 31 PAPI UNUSABLE
The pilot’s failure to maintain an adequate approach path at night after an electrical failure, which resulted in the airplane striking runway lights.
The pilot reported that, during a night flight, while lowering the flaps for landing, the cockpit lights turned off. He attempted to turn the lights back on, to no avail. He added that the precision approach path indicator (PAPI) lights were off, and he could not get the runway lights to turn on either. As he was landing past "the first arrow in front [chevron in the displaced threshold]", he heard a "thump". He taxied to the ramp without further incident. The passenger, an airframe and powerplant mechanic, reported that, during approach after the cockpit lights went out, he used his flashlight to light up the cockpit. He was unable to correct the panel lights but observed that the runway lights were "bright". He added that, during the landing, he felt the "bottom drop out" and the airplane landed hard and bounced. Postaccident examination revealed that the right horizontal stabilator sustained substantial damage. The pilot added that he and the passenger went to the beginning of the approach runway and found pieces of broken runway lights. Archived Notices to Airmen (NOTAMs) for the date of the accident stated that: RWY 31 PAPI UNUSABLE