# NTSB CEN11LA001: Cessna 172D, N2593, Durango, CO, October 3, 2010 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: October 3, 2010, 11:00 local (17:00 UTC) - Place: Durango, CO - Coordinates: 37.235553, -107.86972 - Nearby events: https://openairdocs.org/map.md?lat=37.2356&lon=-107.8697&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Fuel starvation](https://openairdocs.org/ntsb-events/191) - Highest injury: Minor injuries - Injuries: 2 minor - Status: Completed, report January 25, 2012 - Report: Approved by Office Director - NTSB office: Central Region - Parties: FAA Flight Standards District Office - NTSB case key (mKey): 77478 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN11LA001 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/77478/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=77478 - Page: https://openairdocs.org/ntsb/CEN11LA001 ## Probable cause A total loss of engine power due to the pilot inadvertently moving the fuel selector to the OFF position. Contributing to the accident was the pilot's unfamiliarity with this model accident airplane. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Experience/qualifications: total experience w/ equipment](https://openairdocs.org/ntsb-findings/02031025): Personnel issues › Experience/knowledge · Pilot (probable cause); cases with it: [Cessna 172D, 1 case](https://openairdocs.org/ntsb-findings/02031025/cases.md?model=2072410), [All aircraft, 269 cases](https://openairdocs.org/ntsb-findings/02031025/cases.md) - [Fuel system: fuel selector/shutoff valve](https://openairdocs.org/ntsb-findings/01022823): Aircraft › Aircraft systems · Incorrect use/operation (probable cause); cases with it: [Cessna 172D, 1 case](https://openairdocs.org/ntsb-findings/01022823/cases.md?model=2072410), [All aircraft, 176 cases](https://openairdocs.org/ntsb-findings/01022823/cases.md) - [Fuel system: fuel selector/shutoff valve](https://openairdocs.org/ntsb-findings/01022823): Aircraft › Aircraft systems · Unintentional use/operation (probable cause); cases with it: [Cessna 172D, 1 case](https://openairdocs.org/ntsb-findings/01022823/cases.md?model=2072410), [All aircraft, 176 cases](https://openairdocs.org/ntsb-findings/01022823/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Fuel starvation](https://openairdocs.org/ntsb-events/191) (defining event); cases with it: [Cessna 172D, 2 cases](https://openairdocs.org/ntsb-events/191/sequence.md?model=2072410), [All aircraft, 733 cases](https://openairdocs.org/ntsb-events/191/sequence.md) - [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Cessna 172D, 9 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=2072410), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) ## Analysis The first takeoff attempt was aborted when the passenger's door popped open. The pilot taxied back to the end of the runway, closed the door, and began the takeoff. During the second takeoff attempt, as the airplane reached about 200 feet, the engine sputtered and lost power. The pilot enriched the mixture and applied carburetor heat, and the engine sputtered and lost power a second time. The pilot said that, during the forced landing, he shut the fuel off and turned off the master switch before the airplane impacted a dry river bottom. A postaccident examination of the airplane revealed that the fuel selector was found in the BOTH position at the accident site, even though the pilot reported he shut the fuel off prior to impact. The engine was test run to full power, and no anomalies were noted. It is likely that the pilot inadvertently turned off the fuel before the last takeoff, particularly since he was unfamiliar with this model of airplane. ## Factual narrative On October 3, 2010, approximately 1100 mountain daylight time, a Cessna 172D, N2593, was substantially damaged when it impacted terrain following a loss of engine power during takeoff from Animas Airpark (00C), Durango, Colorado. Visual meteorological conditions (VMC) prevailed at the time of the accident. The personal flight was being conducted under the provisions of 14 Code of Federal Regulations (CFR) Part 91 without a flight plan. The pilot and passenger on board the airplane sustained minor injuries. The cross-country flight was originating at the time of the accident, and was en route to Page (PGA), Arizona. In a telephone interview, the pilot stated that whereas he had considerable experience in Cessna 172s, this was an older "D" model and a rental airplane. He had never flown He and his wife had flown from PGA to 00C two days before without incident and they were returning home. The pilot said he took off from runway 19 and when the airplane had climbed about 200 feet and was at midfield, the engine lost power. The pilot pushed the nose over to maintain airspeed and made a forced landing in a river bottom. According to the pilot's accident report, the fuel tanks were full and a preflight inspection was accomplished with no anomalies noted. Prior to takeoff, the mixture was leaned for maximum takeoff power, the fuel selector was positioned on both tanks, the flaps were set to 10 degrees, and the magnetos were checked. The first takeoff attempt was aborted when the passenger's door popped open. The pilot taxied back to the end of the runway, closed the door, and began the takeoff. The airplane was rotated about halfway down runway 19 (5,010 feet long). After climbing about 200 feet, the engine "sputtered a little, followed by silence!" The pilot said there was no remaining runway on which to land and he was committed to "going off the cliff at the south end of the mesa (the airport is situated on top of a mesa). The pilot enriched the mixture and applied carburetor heat. The engine "sputtered again like it wanted to run, then went silent." The pilot said he shut the fuel off, leaned the mixture, and turned off the master switch. The pilot cleared a power line by dropping 20 degrees of flaps and using up elevator. The airplane hit a brush pile in a flat attitude and bounced 40 feet. A Federal Aviation Administration (FAA) inspector from the Salt Lake City Flight Standards District Office (FSDO) went to the accident site. He interviewed the pilot and the fixed base operator (FBO). The inspector said he found the fuel selector in the BOTH position. The pilot has said he turned the fuel selector to the OFF position. In a telephone interview, the pilot stated that although he had considerable experience in Cessna 172s, this was an older "D" model and a rental airplane. He had never flown the Cessna 172D before. The fuel selector on recent model 172s’ has the left tank in the 9 o’clock position, the right tank in the 3 o’clock position, bothtanks in the 12 o’clock position, and the off position in the 6 o’clock position. Earlier model 172s had an L-shaped selector handle with a long hand and a short hand. On December 30, 2010, the engine was functionally tested at the facilities of Air Transport in Phoenix, Arizona. No anomalies were noted and full power was achieved. Asked how this accident could have been prevented, it pilot responded in the accident report: "Stick to flying my own airplane." ## Aircraft - Registration: [N2593](https://openairdocs.org/deregistered/N2593-2014-09-30), registration cancelled 2014-09-30, S/N 172-49893 (OpenAirDocs) - Reported make and model: CESSNA 172D - Registry model: [Cessna 172D](https://openairdocs.org/model/cessna-172d) (registry code 2072410) (OpenAirDocs) - Category: Airplane - Serial number: 172-49893 - Airframe hours: 3820 - Engines: Continental O-300-D 145 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Meca Supply - Registered owner: Meca Supply - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 14, 2010, 21 hours before - Departed: 00C, Durango, CO - Destination: PGA, Page, AZ - Airport: 00C, Animas Airpark, runway 19, 5,010 × 50 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 37; injuries: minor; private; airplane ratings: single-engine land, single-engine sea; medical: class 3, without waivers/limitations; last flight review August 26, 2010; seat: left; flight hours: 515 total, 150 in this make and model, 495 as pilot in command, 16 in the last 90 days, 7 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: variable at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 64 °F, dew point 43 °F - Altimeter: 30.34 inHg - Observed at: DRO, 5 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 20101003048549A](https://openairdocs.org/incident/20101003048549A), Oct 3, 2010: Cessna 172D, Durango, CO, Destroyed. Pilot tookoff and as soon as he ceared the airport enviromnt at 200 feet the enging quit, he glided to the spot of impact into a brush patch and bounced to… ## Docket (7 files) The files NTSB released with the investigation on January 20, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=77478. 1.7 MB in all. - NTSB Form 6120.1-2, Pilot-Operator Aircraft Accident Report (item 1, .PDF, 561 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40341787&FileExtension=.PDF&FileName=NTSB%20Form%206120.1-2,%20Pilot-Operator%20Aircraft%20Accident%20Report-Redacted.PDF - Record of Telephone Conversation (item 2, .PDF, 34 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40358608&FileExtension=.PDF&FileName=Record%20of%20Telephone%20Conversation-Master.PDF - Weather Reports and Records (item 3, .PDF, 40 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40338991&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records-Master.PDF - Photo 1 - N2593 at accident site in creek bed. (item 4, .PDF, 62 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40357272&FileExtension=.PDF&FileName=Photo%201%20-%20N2593%20at%20accident%20site%20in%20creek%20bed.-Master.PDF - Photo 2 - Left side of airplane. (item 5, .PDF, 54 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40357273&FileExtension=.PDF&FileName=Photo%202%20-%20Left%20side%20of%20airplane.-Master.PDF - Photo 3 - Front of airplane. (item 6, .PDF, 65 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40357274&FileExtension=.PDF&FileName=Photo%203%20-%20Front%20of%20airplane.-Master.PDF - Photo 4 - Engine test run. Full power being developed. (item 7, .PDF, 884 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40357275&FileExtension=.PDF&FileName=Photo%204%20-%20Engine%20test%20run.%20Full%20power%20being%20developed.-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.