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

January 2, 2006 · Piper PA-23-160 · N4370P

Phenix City, AL

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
January 2, 2006
Injury Outcomes
2 injuries (1 serious injury, 1 minor injury), 1 uninjured
Location
Phenix City, AL
Aircraft
Piper PA-23-160
Tail Number
N4370P
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
ATL06CA031

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.

NTSB Probable Cause

The pilot's inadequate decision to continue VFR flight into IMC conditions, which resulted in a loss of engine power due to fuel exhaustion.

Full Narrative

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.

Flight

Event TypeAccident
Event Time18:36 CST
Nearest Airport5nm
Runway5
Runway Length6998 ft
Runway Width150 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-23-160
Tail NumberN4370P
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines2
Engine TypeReciprocating
Engine DetailsLycoming · O-320 · Reciprocating · 160 | Lycoming · O-320 · Reciprocating · 160
Seats5

People & Injuries

Injury Summary2 injuries (1 serious injury, 1 minor injury), 1 uninjured
Fatal0
Serious1
Minor1
Uninjured1
Total3
Crew 1Age 48 · Third Class · Serious

Conditions

ConditionsIMC
LightDusk
Wind70° @ 6 kt
Visibility1.5 sm
CeilingOvercast 400 ft
Temperature / Dew Point61 F / 57
Altimeter29.97 inHg
Observation Time20:58
Weather SourceWFAC

Appendix: Source Data