# NTSB WPR17LA147: Cessna 180, N4683B, Baker City, OR, July 9, 2017 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: July 9, 2017, 06:30 local (13:30 UTC) - Place: Baker City, OR - Coordinates: 44.835556, -117.798332 - Nearby events: https://openairdocs.org/map.md?lat=44.8356&lon=-117.7983&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute-descent: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report December 19, 2018 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 95529 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR17LA147 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/95529/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=95529 - Page: https://openairdocs.org/ntsb/WPR17LA147 ## Probable cause The loss of engine power due to fuel exhaustion, which resulted from the pilot's inadequate preflight fuel planning. ## 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 180, 12 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=2072602), [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 180, 6 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md?model=2072602), [All aircraft, 719 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-descent: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) (defining event); cases with it: [Cessna 180, 7 cases](https://openairdocs.org/ntsb-events/192/sequence.md?model=2072602), [All aircraft, 804 cases](https://openairdocs.org/ntsb-events/192/sequence.md) - [Enroute-descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Cessna 180, 6 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=2072602), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 180, 54 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072602), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The commercial pilot reported that he departed on a cross-country flight with 26.5 gallons of fuel and that he planned to make an intermediate stop to refuel before proceeding to the destination airport. The intermediate fuel stop airport was 97 nautical miles (nm) from the departure airport. About 45 minutes into the flight, when the airplane was about 3,000 ft above ground level and 5 nm east of the intermediate fuel stop airport, the engine lost power. The pilot assumed that the airplane was out of fuel and subsequently realized that the airplane would not be able to reach the intended airport. As a result, the pilot made a forced landing to a hayfield, during which the airplane sustained substantial damage. The pilot was using the fuel totalizer to keep track of the amount of fuel during the flight. The pilot reported that the fuel totalizer indicated 14 gallons at the time of the engine failure. The pilot also reported that, at that time, the fuel selector indicated "BOTH" and the fuel gauges indicated that the left tank was 3/8 full and the right tank was empty. Aircraft recovery personnel reported that, when they drained fuel from each tank, the left tank was almost empty, and the right tank had less than 1.7 gallons remaining. According to the Cessna 180 Owner's Manual, the unusable amount of fuel was 1 gallon. Additionally, no fuel streaking stains were observed on the top of either wing, which would have been consistent with fuel that was vented overboard. The pilot reported no mechanical anomalies with the airplane or engine that would have precluded normal operation. Thus, the loss of engine power resulted from fuel exhaustion. Because of his experience in the airplane make and model, the pilot should have known the airplane's fuel burn and should have planned to divert sooner rather than rely on the fuel totalizer and the fuel gauges. ## Factual narrative On July 9, 2017, about 0630 Pacific daylight time, a Cessna 180 airplane, N4683B, was substantially damaged during a forced landing following a loss of engine power near Baker City Municipal Airport (BKE), Baker City, Oregon. The commercial pilot and passenger were not injured. The airplane was registered to and operated by the pilot as a Title 14 Code of Federal Regulations Part 91 personal cross country flight. Visual meteorological conditions prevailed at the time of the accident and no flight plan was filed. The flight originated from Johnson Creek Airstrip (3U2), Yellow Pine, Idaho, about 0630 mountain daylight time and was destined for Red Bluff Municipal Airport (RBL), Red Bluff, California; BKE was a planned en route refueling stop.In a report submitted to the National Transportation Safety Board (NTSB) investigator-in-charge (IIC), the pilot reported that two days prior to the accident he and his passenger flew from Grants Pass, Oregon, to 3U2. The pilot stated that en route to 3U2 he stopped in McCall, Idaho, where he observed that the fuel totalizer read 30 gallons. He then added 26 gallons of fuel, which to his calculation indicated that he had 56 gallons of fuel on board, and set the totalizer to 50 gallons to allow for the unusable fuel; he subsequently made the 26-minute flight to 3U2. The pilot reported that the following morning, he flew to various airstrips in the backcountry, logging 1.6 [hours] tach time; the pilot stated that the fuel totalizer read 26.5 gallons when he landed at 3U2. The next morning the pilot stated that he and his passenger departed 3U2 for the 97 nautical mile (nm) flight to BKE. About 45 minutes into the flight, at an altitude of 3,000 ft above ground level and 5 nm east of BKE, and while setting up for a left downwind for runway 17, the engine lost power. The pilot stated that he then set up for a straight-in approach to runway 26, checked that the fuel selector was on BOTH, and surmised that the airplane was out of fuel. Initially thinking that he could easily make the runway, the pilot did not consider an alternate landing spot. Subsequently, when it became apparent that he was not going to make the runway, the pilot was forced to land in a hay field with irrigation ditches in his path. After having touched down the airplane dropped into a ditch and was substantially damaged; the airplane came to rest upright about 200 yards east of runway 26. The pilot mentioned that at the time of the accident the fuel totalizer indicated 14 gallons; however, it appeared the airplane was out of fuel. The pilot also commented in his statement that there had been talk of the Monarch Fuel Caps, which were installed on the accident airplane, that if they were not installed correctly with the chain and ball, that fuel will vent overboard. The pilot concluded by saying, "Ultimately, I am responsible for how much fuel is in the tanks, but I can't help thinking that there were contributing factors." In a report submittedto the NTSB IIC, a Federal Aviation Administration operations inspector assigned to the Boise Flight Standards District Office, Boise Idaho, responded to the accident site. The inspector reported that the pilot admitted to him that he had run out of fuel after he asked the pilot if he could see the data card from the Garmin 530. The inspector further reported that when he asked the pilot what the fuel gauges were reading just before the engine failure, the pilot replied that the right [gauge] was in the red and that the left gauge read 3/8. The inspector also reported that during his onsite inspection of the airplane, he did not observe any fuel streaking stains on the top of either fuel tank. Additionally, the inspector reported that when recovery personnel drained fuel from both tanks, well under a gallon was drained from the left fuel tank, and under 5 gallons from the right fuel tank. The pilot reported no mechanical anomalies with the airplane or engine that would have precluded normal operation. ## Aircraft - Registration: [N4683B](https://openairdocs.org/deregistered/N4683B-2018-05-03), registration cancelled 2018-05-03, S/N 31581, built 1955 (OpenAirDocs) - Reported make and model: CESSNA 180 (UNDESIGNAT) - Registry model: [Cessna 180](https://openairdocs.org/model/cessna-180) (registry code 2072602) (OpenAirDocs) - Registry engine: [Continental O-470 series](https://openairdocs.org/engine/continental-o-470-series) (registry code 17026, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 31581 - Year built: 1955 - Airframe hours: 3609 - Engines: CONT MOTOR O-470K SERIES 230 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 5, 2017, 9 hours before - Departed: 3U2, Yellow Pine, ID - Destination: BKE, Baker City, OR - Airport: BKE, Baker City Municipal, runway 26, 3,670 × 140 ft, asphalt - Equipment: None ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 63; injuries: none; commercial; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review March 2, 2016; seat: left; restraint: 4-point; flight hours: 5,692 total, 151 in this make and model, 5,600 as pilot in command, 100 in the last 90 days, 86 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 210° at 3 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 64 °F, dew point 50 °F - Altimeter: 30.05 inHg - Observed at: BKE, 1 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 20170709007529A](https://openairdocs.org/incident/20170709007529A), Jul 9, 2017: Cessna 180, Baker City, OR, Substantial damage. The airman stated he had filled each fuel tank at mccall Idaho and flew to johnson creek, Idaho. The next morning, flew throughout the Idaho backcountry… ## Docket (3 files) The files NTSB released with the investigation on October 10, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=95529. 4.5 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40467293&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Record of FAA Inspector's Report (item 2, .PDF, 101 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40467294&FileExtension=.PDF&FileName=Record%20of%20FAA%20Inspector%27s%20Report-Master.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 3, .PDF, 181 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40467295&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-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.