# NTSB ERA24LA390: Cessna 172K, N7058G, Fredericksburg, VA, September 19, 2024 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Class 3 · Limited · Final report - Date: September 19, 2024, 15:30 local (19:30 UTC) - Place: Fredericksburg, VA - Coordinates: 38, -77 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.0000&lon=-77.0000&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute-cruise: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 195163 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA24LA390 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/195163/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=195163 - Page: https://openairdocs.org/ntsb/ERA24LA390 ## Probable cause The pilot’s inadequate fuel planning, which resulted in fuel exhaustion and a subsequent total loss of engine power. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Planning/preparation: fuel planning](https://openairdocs.org/ntsb-findings/02061030): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172K, 4 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md?model=2072430), [All aircraft, 719 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md) - [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid level (probable cause); cases with it: [Cessna 172K, 5 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=2072430), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-cruise: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) (defining event); cases with it: [Cessna 172K, 4 cases](https://openairdocs.org/ntsb-events/192/sequence.md?model=2072430), [All aircraft, 804 cases](https://openairdocs.org/ntsb-events/192/sequence.md) - [Emergency descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172K, 33 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072430), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## 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](https://openairdocs.org/aircraft/N7058G), registered now, S/N 17258758, built 1969 (OpenAirDocs) - Reported make and model: CESSNA 172K - Registry model: [Cessna 172K](https://openairdocs.org/model/cessna-172k) (registry code 2072430) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17258758 - Year built: 1969 - Airframe hours: 5261 - Engines: 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 ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 79; injuries: minor; 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= ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20240919015189A](https://openairdocs.org/incident/20240919015189A), Sep 19, 2024: Cessna 172K, Fredericksburg, VA, Substantial damage. Narrative of flight and accident of [privacy data omitted] – September 19, 2024 • At approximately 2:00 pm the pilot arrived at Culpeper Regional Airport to… ## Docket (5 files) The files NTSB released with the investigation on April 2, 2025, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=195163. 4.4 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 10 pages, 3.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18215474&FileExtension=pdf&FileName=6120%20LA390_Redacted-Rel.pdf - Memorandum for record - pilot email statement (item 2, PDF, 1 page, 71 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18501256&FileExtension=pdf&FileName=ERA24LA390%20-%20MOR%20Pilot%20Email-Rel.pdf - Memorandum for record - FAA inspector's wreckage examination summary (item 3, PDF, 2 pages, 72 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18195319&FileExtension=pdf&FileName=MOR%20FAA%20notes%20LA390-Rel.pdf - Maintenance records (item 4, PDF, 1 page, 168 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18215765&FileExtension=pdf&FileName=MX%20logbook%20excerpts%20n7058g_Redacted-Rel.pdf - Investigation photographs (item 5, PDF, 4 pages, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18195576&FileExtension=pdf&FileName=Investigative%20Photos%20LA390-Rel.pdf From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.