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 10, 2012 · Piper PA-28-151 · N43003

Iuka, MS

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
April 10, 2012
Injury Outcomes
2 injuries (2 minor injuries)
Location
Iuka, MS
Aircraft
Piper PA-28-151
Tail Number
N43003
Operator
Siherb Aviation
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
ERA12CA276

On the day before the accident, the pilot and passenger flew the airplane 575 miles from their home airport to conduct business. The pilot reported that during that flight he observed a discrepancy with the airplane's fuel quantity indicating gauges but that the gauges seemed to work correctly when he "pushed" on the edge of the instrument panel. After landing, the pilot requested that the airplane be refueled, but when he returned the next day to prepare for the return flight, the fuel tanks had not been filled. The pilot visually observed the fuel quantity in both fuel tanks and estimated that there was sufficient fuel for about 3.5 hours of flying, so he decided to take off and stop for fuel during the return flight. About 2.5 hours and 300 miles into the flight, the pilot began searching for an airport where he could land and refuel the airplane. Shortly thereafter, the airplane's engine began losing power, so the pilot switched fuel tanks and diverted to nearest airport, which was about 14 miles away. About 4 miles from the airport, the engine lost all power, and the pilot performed a forced landing in a field. The airplane struck several trees during the landing roll, shearing the wings from the fuselage. The pilot reported no preimpact mechanical malfunctions or failures of the airplane, with the exception of the accuracy of the airplane's fuel gauges. Examination of the wreckage at the accident scene revealed no evidence of any fuel, fuel spillage, fuel leakage, or odor of fuel.

NTSB Probable Cause

The pilot's improper preflight planning and inflight fuel management, which resulted in a total loss of engine power due to fuel exhaustion.

Full Narrative

On the day prior to the accident flight, the pilot and the passenger flew the accident airplane 575 miles from their home airport to conduct business. During that flight the pilot reported that there was a discrepancy with the airplane's fuel quantity indicating gauges, and that they seemed to work correctly when he "pushed" on the edge of the instrument panel. After landing, the pilot had requested that the airplane be serviced with fuel, but when he returned the following day for the return flight, the fuel tanks had not been filled. Prior to departing on the accident flight, the pilot visually observed the fuel quantity in both fuel tanks and assumed that the quantity of fuel was sufficient for about 3.5 hours of flying. About 2.5 hours and 300 miles into the flight, with the airplane's fuel gauges displaying that 10 and 7 gallons remained in the left and right fuel tanks, respectively, the plot began searching for an airport where he could land and refuel the airplane. Shortly thereafter, the airplane's engine began losing power, so the pilot switched fuel tanks and diverted to nearest airport, which was about 14 statute miles away. About 4 miles from the airport, the engine lost all power, and the pilot performed a forced landing to a field below. The airplane struck several trees during the landing roll, shearing the wings from the fuselage. The pilot reported no pre-impact mechanical malfunctions or failures of the airplane, with the exception being the accuracy of the airplane's fuel gauges. Examination of the wreckage at the accident scene revealed no evidence of any fuel, fuel spillage, fuel leakage, or odor of fuel.

Flight

Event TypeAccident
Event Time16:25 CDT
Nearest Airport0nm
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-151
Tail NumberN43003
Aircraft CategoryAir
DamageSubstantial
OperatorSiherb Aviation
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 · Reciprocating · 150
Seats4

People & Injuries

Injury Summary2 injuries (2 minor injuries)
Fatal0
Serious0
Minor2
Uninjured0
Total2
Crew 1Age 61 · Third Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind340° @ 7 kt
Visibility10 sm
CeilingBroken clouds 7500 ft
Temperature / Dew Point70 F / 45 C
Altimeter30.09 inHg
Observation Time19:15
Weather SourceWFAC

Appendix: Source Data