Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

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.

FAQs

NTSB Report

February 18, 2012 · Piper PA-32R-300 · N47863

Swainsboro, GA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 18, 2012
Injury Outcomes
No injuries (7 uninjured)
Location
Swainsboro, GA
Aircraft
Piper PA-32R-300
Tail Number
N47863
Operator
Ronnie Osburn
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA12CA190

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.

NTSB Probable Cause

The pilot’s failure to maintain the proper glidepath during final approach in night visual meteorological conditions, which resulted in a collision with trees.

Full Narrative

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.

Flight

Event TypeAccident
Event Time19:30 EST
Nearest AirportEmanuel County Airport (1nm)
Runway31
Runway Length6021 ft
Runway Width100 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-32R-300
Tail NumberN47863
Aircraft CategoryAir
DamageSubstantial
OperatorRonnie Osburn
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-540 · Reciprocating · 300
Seats6

People & Injuries

Injury SummaryNo injuries (7 uninjured)
Fatal0
Serious0
Minor0
Uninjured7
Total7
Crew 1Age 64 · Second Class · None

Conditions

ConditionsVMC
LightNight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point54 / 52
Altimeter30.06 inHg
Observation Time00:35
Weather SourceWFAC

Appendix: Source Data