# NTSB GAA19CA048: Cessna 172, N3984L, Cleburne, TX, November 1, 2018 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Data collection · Final report - Date: November 1, 2018, 14:00 local (19:00 UTC) - Place: Cleburne, TX - Coordinates: 32.355834, -97.431663 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.3558&lon=-97.4317&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern final: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report June 10, 2019 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 98598 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA19CA048 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/98598/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=98598 - Page: https://openairdocs.org/ntsb/GAA19CA048 ## 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid level (probable cause); cases with it: [Cessna 172G, 8 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=2072420), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md) - [Planning/preparation: fuel planning](https://openairdocs.org/ntsb-findings/02061030): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172G, 6 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md?model=2072420), [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 management (probable cause); cases with it: [Cessna 172G, 8 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=2072420), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md) - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Cessna 172G, 1 case](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=2072420), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern final: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) (defining event); cases with it: [Cessna 172G, 6 cases](https://openairdocs.org/ntsb-events/192/sequence.md?model=2072420), [All aircraft, 804 cases](https://openairdocs.org/ntsb-events/192/sequence.md) - [Approach-VFR pattern final: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341); cases with it: [Cessna 172G, 10 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=2072420), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Landing: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Cessna 172G, 12 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=2072420), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172G, 21 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072420), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis 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. ## Factual 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. ## Aircraft - Registration: [N3984L](https://openairdocs.org/deregistered/N3984L-2019-01-16), registration cancelled 2019-01-16, S/N 17254153, built 1966 (OpenAirDocs) - Reported make and model: Cessna 172 (G) - Registry model: [Cessna 172G](https://openairdocs.org/model/cessna-172g) (registry code 2072420) (OpenAirDocs) - Registry engine: [Continental 0-300 series](https://openairdocs.org/engine/continental-0-300-series) (registry code 17022, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17254153 - Year built: 1966 - Engines: Continental O-300-C 145 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Departed: MWL, Mineral Wells, TX - Destination: CPT, Cleburne, TX - Airport: CPT, Cleburne Rgnl, runway 33, 5,697 × 100 ft, asphalt - Equipment: None ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 25; injuries: minor; private; airplane ratings: single-engine land; medical: class 1, with waivers/limitations; last flight review October 26, 2018; seat: left; restraint: lap only; flight hours: 62 total, 62 in this make and model, 22 as pilot in command, 41 in the last 90 days, 20 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 360° at 11 knots - Visibility: 10 statute miles - Temperature: 61 °F, dew point 41 °F - Altimeter: 29.95 inHg - Observed at: KCPT ## 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 20181101022329A](https://openairdocs.org/incident/20181101022329A), Nov 1, 2018: Cessna 172G, Cleburne, TX, Substantial damage. Approx 3.6 hr pilot cross country training flight that included 6 touch and go operations at various local airports. On final leg to cpt the engine began… ## Docket (3 files) The files NTSB released with the investigation on March 11, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=98598. 1.7 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 848 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470946&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Accident Pictures (item 2, .PDF, 2 photos, 792 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470947&FileExtension=.PDF&FileName=Accident%20Pictures-Master.PDF - FAA Statement (item 3, .PDF, 40 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470948&FileExtension=.PDF&FileName=FAA%20Statement-Master.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.