ERA24LA390

NTSB accident investigation · Cessna 172K · Fredericksburg, VA · September 19, 2024

Accident · Minor injuriesClass 3 · LimitedFinal report
Date
September 19, 2024, 15:30 local (19:30 UTC)
Place
Fredericksburg, VA
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N7058GCessna 172K
Defining event
Enroute-cruise: Fuel exhaustion
Weather
Visual (VMC) · Day
Status
Completed
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20240919015189A
Case key
195163

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

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

Findings · 2

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Planning/preparation: fuel planningPersonnel issues › Task performance · PilotCessna 172K: 4 casesAll aircraft: 719 casesProbable cause
Fluids: fuelAircraft › Fluids/misc hardware · Fluid levelCessna 172K: 5 casesAll aircraft: 1,695 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

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.

Factual 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.”

Aircraft

Registration
N7058G
Reported as
Cessna 172K
Category
Airplane
Serial number
17258758
Built
1969
Airframe hours
5,261
Engine
Lycoming O-320-E2D, 150 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Utility; Standard, Normal
Last inspection
Annual · September 18, 2024 · 1 hours before
Departed
CJR · Culpeper, VA
Destination
Same as departure
Equipment
Auto-pilot

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
79
Injuries
Minor
Certificate
Commercial
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 2, With waivers/limitations
Seat
Left
Restraint
Lap only
Flight hours
4,001 total · 1,963 in this make and model · 32 in the last 90 days · 8 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
280° at 3 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
79 °F, dew point 66 °F
Altimeter
29.88 inHg
Observed at
KXSA, 11 nm away
METAR
METAR KXSA 192035Z AUTO 28003KT 10SM CLR 26/19 A2988 RMK AO2 T02610194=

Docket · 5

The files NTSB released with the investigation on April 2, 2025, on NTSB’s docket system: statements, records, photos and specialists’ reports. 4.4 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.