# NTSB CEN11CA322: Cessna 172K, N46400, Farmersville, TX, May 5, 2011 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: May 5, 2011, 16:00 local (21:00 UTC) - Place: Farmersville, TX - Coordinates: 33.217777, -96.334999 - Nearby events: https://openairdocs.org/map.md?lat=33.2178&lon=-96.3350&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report August 3, 2011 - Report: Approved by Office Director - NTSB office: Central Region - Parties: FAA FSDO - NTSB case key (mKey): 79046 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN11CA322 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/79046/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=79046 - Page: https://openairdocs.org/ntsb/CEN11CA322 ## Probable cause A loss of engine power due to fuel starvation as a result of the pilot's improper fuel management. ## 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 management (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) - [Personnel issues](https://openairdocs.org/ntsb-findings/02060000): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172K, 1 case](https://openairdocs.org/ntsb-findings/02060000/cases.md?model=2072430), [All aircraft, 137 cases](https://openairdocs.org/ntsb-findings/02060000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute: Fuel starvation](https://openairdocs.org/ntsb-events/191); cases with it: [Cessna 172K, 1 case](https://openairdocs.org/ntsb-events/191/sequence.md?model=2072430), [All aircraft, 733 cases](https://openairdocs.org/ntsb-events/191/sequence.md) - [Enroute: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) (defining event); cases with it: [Cessna 172K, 11 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=2072430), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/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) - [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Cessna 172K, 11 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=2072430), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) ## Analysis Approximately 2 hours after departure on an aerial pipeline patrol flight, the pilot turned on the fuel transfer pump, which transfers fuel from the auxiliary baggage fuel tank to the airplane’s right wing fuel tank. The pilot reported that this was his routine and that it would take about two hours to transfer the fuel from the auxiliary tank to the wing fuel tank. The pilot added that, almost 4 hours after departure, the engine sputtered; he rocked the wings and noticed that the fuel transfer pump appeared to be off. He then started the fuel transfer again. The fuel transfer light came on; however, the airplane was too low to wait for the fuel to move to the wing fuel tank and then to the engine. So the pilot elected to perform a forced landing to a field. The airplane collided with several tree branches before impacting the ground and flipping over. During the forced landing the airplane sustained substantial damage to its right wing, aft fuselage, and top of the vertical stabilizer. The pilot also stated that sometime after he started the initial transfer of fuel the transfer pump apparently turned off and he did not notice. ## Factual narrative Approximately 2-hours after departure on an aerial pipeline patrol flight, the pilot turned on the fuel transfer pump, which transfers fuel from the auxiliary baggage fuel tank to the airplane’s right wing fuel tank. The pilot reported that this was his standard routine, and that it would take about two hours to transfer the fuel from the auxiliary tank to the wing fuel tank. The pilot added that almost 4-hours after departure, the engine “sputtered”; he rocked the wings and noticed that the fuel transfer pump appeared off. He then started the fuel transfer again. The fuel transfer light came on; however, the airplane was too low to wait for the fuel to move to the wing fuel tank and then to the engine. So the pilot elected to perform a forced landing to a field. The airplane collided with several tree branches before impacting the ground and flipping over on to its back. During the forced landing the airplane sustained substantial damage to its right wing, aft fuselage, and top of the vertical stabilizer. The pilot also stated that some time after starting the initial transfer of fuel, the transfer pump apparently turned off, and he didn’t notice it. In the section, Recommendation (How could this accident have been prevented?) on the NTSB pilot/operator aircraft accident/incident report form, the pilot stated that moving the auxiliary fuel gauge and indicator light to the instrument panel; or a fuel flow meter on the instrument panel, would aid the pilot in noticing if the fuel transfer pump was on or fuel was actually transferring from the auxiliary fuel tank. ## Aircraft - Registration: [N46400](https://openairdocs.org/deregistered/N46400-2017-03-10), registration cancelled 2017-03-10, S/N 17257241, built 1968 (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: 17257241 - Airframe hours: 15000 - Engines: LYCOMING 0-360 SERIES 180 horsepower reciprocating - Damage: Substantial damage - Flight: Aerial observation, Part 91 - Operator: Texas Aerial Inspections LLC - Registered owner: Texas Aerial Inspections LLC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, September 1, 2010 - Departed: KCPT, Cleburne, TX - Destination: 52F, Roanoke, TX ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 49; injuries: none; airline transport; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review September 26, 2010; seat: left; flight hours: 8,341 total, 2,000 in this make and model, 7,869 as pilot in command, 220 in the last 90 days, 65 in the last 30 days, 7 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 170° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 75 °F, dew point 50 °F - Altimeter: 30.11 inHg - Observed at: KTKI, 15 nm away ## 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 20110505007969A](https://openairdocs.org/incident/20110505007969A), May 5, 2011: Cessna 172K, Farmerville, TX, Substantial damage. On 5 may 20011 at or about 1600L a Cessna CE-172-K serial number 172-257241 registered as n 46400 to Texas areal inspections, LLC , landed in to a field after… ## Docket (4 files) The files NTSB released with the investigation on June 3, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=79046. 3.5 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 547 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348316&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Weather Reports and Records (item 2, .PDF, 26 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348317&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records-Master.PDF - Photo1: Accident airplane (FAA photo) (item 3, .PDF, 1.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348318&FileExtension=.PDF&FileName=Photo1%3A%20Accident%20airplane%20(FAA%20photo)-Master.PDF - Photo 2: Auxiliary fuel gauge and switch (FAA photo) (item 4, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348320&FileExtension=.PDF&FileName=Photo%202%3A%20Auxiliary%20fuel%20gauge%20and%20switch%20(FAA%20photo)-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.