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.
Morganton, NC
The commercial pilot was on a Part 135 cargo flight. Since the destination airport had no weather reporting facility, company policy and FAR 135 required a VFR descent and landing from the MVA. The pilot requested and received clearance for a localizer approach to the airport, although a nearby airport was reporting 400' broken/3 miles with fog. The pilot reported to ATC that he had missed his first approach, and requested a second approach to the same airport. After executing the missed approach, the aircraft impacted mountainous terrain while aligned with the extended centerline of the localizer. CAP personnel reported that the accident site was obscured in clouds at the time of the accident. The investigation revealed that the aircraft descended about 1,500 feet below a minimum altitude on the first approach attempt. Mode C altitude data was lost during the missed approach. Four years earlier, this pilot descended below glidepath on an ILS approach and crashed into trees with weather below approach minimums.
THE FAILURE OF THE PILOT TO FOLLOW FAR AND COMPANY PROCEDURES, AND HIS FAILURE TO MAINTAIN PROPER ALTITUDE DURING THE APPROACH. FACTORS WERE THE MOUNTAINOUS TERRAIN CONDITIONS, AND THE FOGGY, LOW CEILING WEATHER CONDITIONS EXISTING AT THE TIME OF THE ACCIDENT.
THE COMMERCIAL PILOT WAS ON A PART 135 CARGO FLIGHT. SINCE THE DESTINATION AIRPORT HAD NO WEATHER REPORTING FACILITY, COMPANY POLICY AND FAR 135 REQUIRED A VFR DESCENT AND LANDING FROM THE MVA. THE PILOT REQUESTED AND RECEIVED CLEARANCE FOR A LOCALIZER APPROACH TO THE AIRPORT, ALTHOUGH A NEARBY AIRPORT WAS REPORTING 400' BROKEN/3 MILES WITH FOG. THE PILOT REPORTED TO ATC THAT HE HAD MISSED HIS FIRST APPROACH, AND REQUESTED A SECOND APPROACH TO THE SAME AIRPORT. AFTER EXECUTING THE MISSED APPROACH, THE AIRCRAFT IMPACTED MOUNTAINOUS TERRIAN WHILE ALIGNED WITH THE EXTENDED CENTERLINE OF THE LOCALIZER. CAP PERSONNEL REPORTED THAT THE ACCIDENT SITE WAS OBSCURED IN CLOUDS AT THE TIME OF THE ACCIDENT. THE INVESTIGATION REVEALED THAT THE AIRCRAFT DESCENDED ABOUT 1,500 FEET BELOW A MINIMUM ALTITUDE ON THE FIRST APPROACH ATTEMPT. MODE C ALTITUDE DATA WAS LOST DURING THE MISSED APPROACH. FOUR YEARS EARLIER, THIS PILOT DESCENDED BELOW GLIDEPATH ON AN ILS APPROACH AND CRASHED INTO TREES WITH WEATHER BELOW APPROACH MINIMUMS.