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

November 1, 2018 · Cessna 172 G · N3984L

Cleburne, TX

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
November 1, 2018
Injury Outcomes
1 injury (1 minor injury)
Location
Cleburne, TX
Aircraft
Cessna 172 G (1966)
Tail Number
N3984L
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
GAA19CA048

The pilot reported that, during the final approach to the destination airport, the engine lost power. Due to homes that were in line with the approach end of the runway, he decided to perform an emergency landing in a field, during which the airplane slid and then came to rest in trees. The airplane sustained substantial damage to the left wing. The pilot reported that he had not considered the engine's fuel burn for touch-and-go landings or headwinds during his preflight planning. During postaccident examination, a Federal Aviation Administration inspector reported that the fuel gauges read zero and that no fuel was found in the right fuel tank and only 10 ounces of fuel were found in the left fuel tank. Fuel was added to the airplane, and the engine started and operated normally. He added that he talked to the pilot, and he stated that he had flown 3.6 hours and performed at least six touch-and-go landings. The pilot also stated that the airplane usually has a 3.5-hour maximum range at 1,000 ft above ground level at 8 to 9 gallons per hour and that he likely did not properly monitor the engine's fuel consumption, which led to fuel exhaustion. Given the evidence, it is likely the pilot did not ensure that there was sufficient fuel onboard the airplane for the flight and that he did not monitor it properly during the flight, which resulted in fuel exhaustion and the subsequent total loss of engine power.

NTSB Probable Cause

The pilot's improper preflight fuel planning and in-flight fuel management, which resulted in fuel exhaustion and the subsequent total loss of engine power.

Full Narrative

The newly certificated pilot reported that during a cross country flight, he hadn't considered the engine's fuel burn for touch and goes or headwinds, and during the final approach to the destination airport, the engine lost power. Due to homes that were in line with the approach end of the runway, instead of continuing to the runway, he decided to perform an emergency landing in a field. During the off-airport landing, the airplane "slid" and came to rest in trees. The airplane sustained substantial damage to the left wing. During the post-accident examination, a Federal Aviation Administration inspector reported that, the fuel gauges read zero, and that there was no fuel in the right fuel tank and only 10 ounces were recovered from the left fuel tank. Additional fuel was added to the airplane and the engine started and operated normally. He added that, after speaking to the pilot, the pilot "basically admitted" that he did not properly monitor the engine's fuel consumption.

Flight

Event TypeAccident
Event Time14:00 CDT
Nearest AirportCleburne Rgnl (0nm NE)
Runway33
Runway Length5697 ft
Runway Width100 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172 G
Tail NumberN3984L
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsContinental · O-300-C · Reciprocating · 145
Seats4

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 25 · First Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind360° @ 11 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point61 F / 41 C
Altimeter29.95 inHg
Observation Time19:15
Weather SourceWFAC

Appendix: Source Data