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

April 26, 2026 · Piper PA-30 NO Series · N8432Y

Enterprise, AL

Overview

Report Status
Probable Cause
Event Type
Accident
Date
April 26, 2026
Injury Outcomes
No injuries (2 uninjured)
Location
Enterprise, AL
Aircraft
Piper PA-30 NO Series (1967)
Tail Number
N8432Y
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA26LA190

The pilot stated that the purpose of the flight in the multiengine airplane was to build proficiency and to take an acquaintance, who was not a pilot, on a familiarization flight. The pilot described that before departing the airplane had 22 gallons of fuel in the main fuel tanks, and 15 gallons of fuel in the auxiliary fuel tanks, and that the entire flight was conducted utilizing the main fuel tanks. The pilot flew over a practice area for 20 minutes and then returned to the departure airport where he performed two uneventful touch-and-go landings. The pilot added that he miscalculated the fuel consumption rate and thought about 15 minutes of fuel remained for the third landing, which would have been full-stop. He further stated that while turning from the downwind to the base leg of the airport traffic pattern for the third landing, both engines lost total power. The pilot turned toward the runway and attempted to restart one of the engines; however, the attempt was unsuccessful and the airplane impacted trees about ½-mile short of the runway. The airplane sustained substantial damage to the fuselage, empennage, and both wings. The pilot added that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.

NTSB Probable Cause

The pilot’s inadequate preflight and inflight fuel planning, which resulted in a total loss of engine power due to fuel starvation and subsequent forced landing into trees.

Full Narrative

The pilot stated that the purpose of the flight in the multiengine airplane was to build proficiency and to take an acquaintance, who was not a pilot, on a familiarization flight. The pilot described that before departing the airplane had 22 gallons of fuel in the main fuel tanks, and 15 gallons of fuel in the auxiliary fuel tanks, and that the entire flight was conducted utilizing the main fuel tanks. The pilot flew over a practice area for 20 minutes and then returned to the departure airport where he performed two uneventful touch-and-go landings. The pilot added that he miscalculated the fuel consumption rate and thought about 15 minutes of fuel remained for the third landing, which would have been full-stop. He further stated that while turning from the downwind to the base leg of the airport traffic pattern for the third landing, both engines lost total power. The pilot turned toward the runway and attempted to restart one of the engines; however, the attempt was unsuccessful and the airplane impacted trees about ½-mile short of the runway. The airplane sustained substantial damage to the fuselage, empennage, and both wings. The pilot added that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.

Flight

Event TypeAccident
Event Time11:59 CDT
Nearest AirportEnterprise Muni (1nm SW)
Runway05/2
Runway Length5080 ft
Runway Width100 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-30 NO Series
Tail NumberN8432Y
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines2
Engine TypeReciprocating
Engine DetailsLycoming · IO-320-B1A · Reciprocating · 160 | Lycoming · IO-320-B1A · Reciprocating · 160
Seats6

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 2Age 49 · Second Class · None

Conditions

ConditionsVMC
LightDaylight
Wind320° @ 7 kt
Visibility10 sm
CeilingBroken clouds 29000 ft
Temperature / Dew Point63 F
Altimeter29.91 inHg
Observation Time12:00
Weather SourceWFAC

Appendix: Source Data