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

March 21, 2003 · Cessna 172P · N89811

Potts Camp, MS

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
March 21, 2003
Injury Outcomes
No injuries (3 uninjured)
Location
Potts Camp, MS
Aircraft
Cessna 172P
Tail Number
N89811
Injuries
None
Aircraft Damage
Substantial
NTSB Number
MIA03LA078

The pilot stated that while en route to his fuel stop, about 5 minutes prior to the accident, while scanning the airplane instruments, he was surprised to see that the fuel gauges were indicating below the 5-gallon mark for each tank. After monitoring the gauges, and seeing them stabilize, he said he again started to feel confident in his calculations. About 14 miles south of Holly Springs, Mississippi, in the vicinity of Potts Camp, Mississippi, he said the engine ceased operating. He said he established the best glide speed, while looking for and selecting a field where he could execute a forced landing. As the airplane was descending he attempted to restart the engine, but was unsuccessful. After maneuvering to avoid wires, he landed the airplane in the field, and during the landing rollout the airplane's nose wheel became entangled in a wire fence, and the airplane was damaged. An FAA inspector responded to the accident scene, and noted that no fuel was present in the airplane. After recovery from the field, an FAA licensed airframe and power plant mechanic, under the supervision of the FAA inspector, conducted an examination of the airplane, and no anomalies were found. When fuel was provided, and the damaged propeller replaced, the airplane's engine was tested and it operated normally.

NTSB Probable Cause

The pilot's inadequate planning which resulted in fuel exhaustion, a forced landing to a field, and damage to the airplane during the landing rollout.

Full Narrative

On March 21, 2003, about 1709 central standard time, a Cessna 172P, N89811, registered to and operated by the Pensacola Navy Flying Club, Inc., as a Title 14 CFR Part 91 personal flight, incurred a loss of engine power, while in cruise flight in the vicinity of Potts Camp, Mississippi. Visual meteorological conditions prevailed, and a visual flight rules flight plan was filed. The private-rated pilot and two passengers received no injuries, and the airplane incurred substantial damage. The flight originated in Pensacola, Florida, the same day, about 1435. The pilot stated that he planned the flight from Pensacola, Florida, to Olive Branch, Mississippi, examining the weather, and was prepared to make one of three fuel stops, depending on the actual winds aloft. He said that after having planned the flight at home, he then stopped by the Pensacola Navy Flying Club, about 1200, to ensure the airplane would be available for the flight. At that time, he said he checked the fuel level, and determined that the airplane was full of fuel. He said he then went home filed a VFR flight plan, checked the weather again, and returned to the airplane at 1400, along with his wife and son. He said he then performed a thorough preflight inspection, observed the fuel level again, and once again determined that he did not need to call the fixed-base operator, Pensacola Aviation Inc., for fuel. He said the remaining preparations, as well as the taxi, takeoff, and initial cruise phases were normal. About 5 minutes prior to the accident, while scanning the airplane instruments, the pilot said he was surprised to find that the fuel gauges were indicating below the 5-gallon mark for each tank. After monitoring the gauges, and seeing them stabilize, he again said he started to feel confident in his calculations. He calculated his position, and prepared for a landing at Holly Springs, Mississippi, and about 14 miles south of Holly Springs, in the vicinity of Potts Camp, Mississippi, he said the engine ceased operating. He said he established best glide speed, while looking for and selecting a field where he could execute a forced landing. He further stated that as the airplane was descending he attempted to restart the engine, but was unsuccessful. During the approach to the field he had selected, he noticed utility wires, and maneuvered to avoid them, and was able to land, but during the landing rollout the airplane's nose wheel became entangled in a wire fence, and the airplane slid, coming to rest in a small ditch, incurring damage. An FAA inspector responded to the accident and noted that no fuel was present in the airplane. After recovery from the field, an FAA licensed airframe and powerplant mechanic, under the supervision of the inspector, conducted an examination of the airframe and engine, and no anomalies were found. When fuel was provided, and the damaged propeller replaced, the engine operated normally.

Flight

Event TypeAccident
Event Time17:09 CST
Nearest Airport0nm
Flight Plan FiledVFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172P
Tail NumberN89811
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsTextron Lycoming · O-360-A4M · Reciprocating · 180
Seats4

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3
Crew 1Age 25 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind330° @ 5 kt
Visibility9 sm
CeilingNone
Temperature / Dew Point54 / 45 C
Altimeter29.94 inHg
Observation Time23:00
Weather SourceWFAC

Appendix: Source Data