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.
Phenix City, AL
The private pilot was on a visual flight rules cross country flight when he began encountering instrument conditions. The pilot continued into the instrument conditions for about 30 minutes before asking Atlanta Approach Control for directions to the nearest airport for landing. The controller directed the pilot to two different nearby airports but both were below minimums. The pilot informed the controller that he was low on fuel and needed to land as soon as possible. The controller directed the pilot to the Columbus Metropolitan Airport, Columbus, Georgia. The pilot told the controllers that he would attempt an Instrument approach. The pilot attempted four unsuccessful approaches with the controllers talking him through each approach. On the fifth approach, at five miles from the runway the pilot stated that both engine's quit due to fuel exhaustion. The pilot called "mayday" and during the forced landing the airplane collided with trees and the ground separating the right wing, half of the left wing, and coming to rest inverted. The pilot did not report any mechanical deficiencies with the airplane during the attempted approaches.
The pilot's inadequate decision to continue VFR flight into IMC conditions, which resulted in a loss of engine power due to fuel exhaustion.
The private pilot was on a visual flight rules cross country flight when he began encountering instrument conditions. The pilot continued into the instrument conditions for about 30 minutes before asking Atlanta Approach Control for directions to the nearest airport for landing. The controller directed the pilot to two different nearby airports but both were below minimums. The pilot informed the controller that he was low on fuel and needed to land as soon as possible. The controller directed the pilot to the Columbus Metropolitan Airport, Columbus, Georgia. The pilot told the controllers that he would attempt an instrument approach. The pilot attempted four unsuccessful approach's with the controllers talking him through each approach. On the fifth approach, at five miles from the runway the pilot stated that both engine's quit due to fuel exhaustion. The pilot called "mayday" and during the forced landing the airplane collided with trees and the ground separating the right wing, half of the left wing, and coming to rest inverted. The pilot did not report any mechanical deficiencies with the airplane during the attempted approach's.