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

September 19, 2024 · Cessna 172K · N7058G

Fredericksburg, VA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
September 19, 2024
Injury Outcomes
1 injury (1 minor injury)
Location
Fredericksburg, VA
Aircraft
Cessna 172K (1969)
Tail Number
N7058G
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
ERA24LA390

The pilot reported that the airplane had been stored in a hangar for two years awaiting an engine rebuild. Following the rebuild and an annual inspection, the pilot planned to ferry the airplane to his farm. After a preflight inspection, the pilot had trouble starting the engine due to a low battery, requiring a jump start. After successfully starting the engine, and shortly after departure, the engine lost total power about five miles from the farm, requiring a forced landing. The airplane collided with trees during the ensuing off-airport landing. A postaccident examination of the airplane’s wreckage revealed no evidence of any preimpact mechanical malfunctions or failures of the engine and that the airplane’s fuel tanks were absent of fuel. In a subsequent statement, the pilot confirmed that the accident was the result of fuel exhaustion.

NTSB Probable Cause

The pilot’s inadequate fuel planning, which resulted in fuel exhaustion and a subsequent total loss of engine power.

Full Narrative

On September 19, 2024, about 1530 eastern standard time, a Cessna 172K, N7058G, was substantially damaged when it was involved in an accident near Fredericksburg, Virginia. The private pilot received minor injuries. The flight was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that the airplane had been stored in a hangar for two years awaiting an engine rebuild. After the rebuild and an annual inspection, he planned to fly the airplane back to his farm. Following a preflight inspection, the pilot attempted to start the engine but found the battery was too low. After a jump start, he departed, circled the airport, and headed toward the farm. When the flight was about five miles from the farm, the engine lost total power, and the pilot performed a forced landing. After clearing trees along the approach to a pasture, he slipped the airplane to lose altitude and he began to flare the airplane about 1/3 of the way into the pasture. The pilot then noticed a gravel drive with utility lines and trees at the end of the pasture. He stated that since he still had sufficient airspeed, he pulled back on the control yoke, the airplane became airborne, and he was able to clear the utility line and trees. The airplane then touched down hard. The pilot stated that he ground-looped the airplane to avoid the river at the end of the pasture. The airplane contacted the trees that he had just cleared before coming to rest. During the postaccident examination of the airplane, about 5 ounces of fuel were drained from the fuel sump-gascolator and carburetor, with no contaminants or water present. Both the left- and right-wing fuel tanks were empty. Examination of the engine confirmed compression on all four cylinders and continuity of the valvetrain. The cylinders and exhaust system components were examined with a lighted borescope with no anomalies noted. The left and right magnetos operated normally when tested. The spark plugs, ignition harness, and carburetor screen were examined, with no anomalies noted. The oil filter and housing were inspected and found to be free of contaminants. No anomalies were found that would have precluded normal operation of the engine. In a subsequent written statement, the pilot stated, “my aircraft experienced fuel exhaustion while returning to my farm. I thought I had enough fuel to make it, but I didn’t and ran out of gas.”

Flight

Event TypeAccident
Event Time15:30 EDT
Nearest Airport0nm
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172K
Tail NumberN7058G
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-E2D · Reciprocating · 150
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
Wind280° @ 3 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point66 F
Altimeter29.88 inHg
Observation Time16:35
Weather SourceWFAC

Appendix: Source Data