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.
Swainsboro, GA
The pilot reported that the airplane was approaching the destination airport on the base leg of the traffic pattern in night visual meteorological conditions. At that time, the runway lights were set on high intensity, which diluted the threshold lights. Additionally, the pilot stated that the red localizer antenna hazard lights distracted him (they were located about 750 feet before the runway threshold). He further stated that he was too low and struck trees during final approach. The airplane impacted trees with both wings about 2,400 feet before the runway threshold. The impact with trees resulted in damage to the left wing spar, lower fuselage, and the stabilator. The pilot stated that there were no preimpact mechanical malfunctions with the airplane. Following the accident, the airport manager checked all runway lighting and found them to be operational.
The pilot’s failure to maintain the proper glidepath during final approach in night visual meteorological conditions, which resulted in a collision with trees.
The pilot reported that the airplane was approaching the destination airport on a base leg of the traffic pattern in night visual conditions. At that time, the runway lights were set on high intensity, which diluted the threshold lights. Additionally, the red localizer antenna hazard lights were distracting. The pilot further stated that he was too low and struck trees during final approach; however, the airplane landed on the runway without further incident. The pilot added that there were no preimpact mechanical malfunctions with the airplane. A Federal Aviation Administration inspector stated that the airplane impacted trees with both wings about 2,400 feet prior to the runway threshold. The impact with trees resulted in damage to the left wing spar, lower fuselage, and the stabilator. The runway was 6,021 feet long and was equipped with a localizer approach, but was not equipped with an instrument landing system approach. The runway was also not equipped with a visual approach slope indicator. The red localizer antenna hazard lights were located about 750 feet prior to the runway threshold. Following the accident, the airport manager checked all runway lighting and found them to be operational.