Event ERA24LA390

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.” 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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

• — Personnel issues-Task performance-Planning/preparation-Fuel planning-Pilot
• — Aircraft-Fluids/misc hardware-Fluids-Fuel-Fluid level