- Date
- July 23, 2021, 20:45 local (Jul 24, 2021, 03:45 UTC)
- Place
- Mt. Hood, OR
- Injuries
- 1 minor, 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N8884Cessna 180K
- Defining event
- Enroute: Loss of engine power (total)
- Weather
- Visual (VMC) · Night
- Status
- Completed
- Report
- Approved by Office Director
- Investigation class
- Class 3
- NTSB office
- Western Pacific Region
- Parties
- Federal Aviation Administration
- FAA report
- 20210723017279A
- Case key
- 103569
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The total loss of engine power while in cruise flight for reasons that could not be determined based on available evidence. Contributing to the accident was the presentation of an abandoned airport as available for use in the Federal Aviation Administration airports database.
Findings · 2
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
The pilot had made two flights on the day of the accident. The first flight was 1.2 hours in duration and the pilot did not report any anomalies on that flight. According to the engine data monitor (EDM), about 30 minutes into the second flight, the engine experienced a total loss of power. The pilot used his personal electronic device to access an aviation navigation application that included Federal Aviation Administration-approved charts; he used this information as a guide to divert to the nearest airport only to discover upon arrival that the airport had been abandoned and a barn had been erected on the approach end of runway 34. The pilot believed that he had sufficient altitude to change the landing direction, but the airplane collided with a tree and terrain while on the base leg, about 100 ft north of the airport. The airplane sustained substantial damage to the right wing and aileron. The pilot reported that he started the day with 42 gallons of fuel on board. The EDM reported 18.3 gallons left in the tanks at the time of the accident. Fuel was found in both tanks when the airplane was recovered. Fuel was also found in the carburetor bowl. The finger screens of both wings were unobstructed. It is likely that fuel exhaustion was not causal to this accident. Examination of the airframe revealed multiple bends in the fuel line from the gascolator to the carburetor; however, the fuel lines were secured with clamps and exhibited no signs of kinks, collapse or leaks. The airplane had been flown at least 41 hours with the fuel lines in the present configuration without any loss of power issues, making it unlikely that the bends in the lines resulted in fuel starvation. Further examination of the airframe and engine revealed no mechanical malfunctions or failures that would have precluded normal operation. Environmental conditions reported near the accident site about the time of the accident were conducive to light carburetor icing during cruise and descent power; however, carburetor icing was likely not causal, as the pilot reported the engine lost total power without coughing or sputtering. Following the accident, the engine was test run and operated normally for 10 minutes, from idle to maximum speed, using a supplemental fuel supply and the airplane’s throttle, mixture, and propeller controls.
Factual narrative
On July 23, 2021, about 2045 Pacific daylight time, a Cessna 180K airplane, N8884 was substantially damaged when it was involved in an accident near Mt. Hood, Oregon. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. About 45 minutes after takeoff the engine lost all power with no indications of coughing or sputtering, but the propeller continued to spin. The engine did not regain power, despite the actions of the pilot which included, cycling the propeller, adjusting the mixture to full rich, advancing the throttle to full power, and ensuring that the carb heat was off. The pilot then turned north and used his personal electronic device (PED) to access an aviation navigation application that included Federal Aviation Administration-approved charts, which he used as a guide to fly direct to Ken Jernstedt Airfield (4S2). He soon realized that he would not make it to 4S2 but observed on the PED that Hanel Field (0OR9) was directly ahead. He proceeded north with the intent to land on runway 34. Upon arrival the pilot saw that the airport was abandoned, and a barn had been erected on the approach end of runway 36, along with multiple vehicles parked on the runway. He decided that he had the altitude to change landing directions and land on runway 16. While maneuvering to runway 16 he added 20° of flaps and turned to a left base leg. He detected a tailwind, felt his rate of descent rate increase, and heard the stall warning horn activate. The airplane struck a tree and collided with terrain about 100 ft north of the runway. The airplane came to rest in a field covered by shrubs and trees. The right wing, from the tip to about midspan, and the right aileron separated. The pilot reported that his PED had an aviation navigation application that included Federal Aviation Administration approved charts. The pilot reported that he started the day with 42 gallons of fuel. During the recovery of the airplane on the following day, about 10-15 gallons of fuel were removed from the right wing, and an estimated 5 to 10 gallons had leaked out of the left wing, which still had some fuel remaining in the tank. Examination of the airframe revealed that the fuel hose exited the gascolator, made a 90° bend followed by a 180° bend, then attached to a fuel flow transducer. A second fuel hose exited the fuel flow transducer, made a 90° bend then attached to the carburetor. The hoses were secured with clamps to the engine mounts and exhibited no signs of kinks, collapse, or leaks. The airplane was equipped with an engine data monitoring (EDM) system on August 5, 2020. The fuel flow transducer and the two connecting hoses were part of that installation. According to the pilot, the airplane had accumulated about 41 hours on the airplane, over about 42 flights since the installation of the EDM. Further examination of the airframe and engine revealed no mechanical malfunctions or failuresthat would have precluded normal operations. The engine was test-run for 10 minutes at maximum speed using a supplemental fuel tank and the airplane’s throttle, mixture, and propeller controls. The engine operated normally from idle to maximum speed during the entire run time. According to the data recovered from the EDM, the internal clock was set to coordinated universal time (UTC). The EDM contained data on the last 63 flights and had identified them as Flt# 11 through Flt #73. The last two flights, number 72 and 73, occurred on July 23; however, both were recorded as having occurred on July 24 due to the internal clock being set to UTC. The recorded time was converted to local time for this report. Flight number 72 began at 1816:28 and continued until 1926:20. The pilot did not report any anomalies on this flight. All recorded data were consistent with an uneventful flight. The fuel used quantity began at 21.5 gallons and ended at 33.9 gallons for a total of 12.4 gallons used. Flight number 73, the last flight recorded and the accident flight, began at 1935:35 until 2039:06. Data captured included exhaust gas temperature, cylinder head temperature, manifold pressure, engine RPM, oil pressure, and fuel used. At 1935:36, all data rose in a manner consistent with the engine starting and producing power until about 2033:42, when all recorded data began to decrease sharply and continued to decrease until the end of the recorded data. At 2033:48, the fuel flow fluctuated from 0.6 to 0.0 for the remainder of the recorded data, consistent with a total loss of power. Fuel used began at 33.9 and ended at 45.2, for a total of 11.3 gallons used.
Aircraft
- Registration
- N8884
- Reported as
- Cessna 180K
- Category
- Airplane
- Serial number
- 18053039
- Built
- 1979
- Airframe hours
- 2,021.1
- Engine
- Continental TSIO-520 SER, 300 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Operator
- Dragon Wagon LLC
- Registered owner
- Dragon Wagon LLC
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · June 21, 2021 · 0 hours before
- Departed
- HRI · Hermiston, OR
- Destination
- S48 · Sandy, OR
- Airport
- 0OR9 · Hanel Fld, runway 16/34, 1,900 × 25 ft, asphalt
- Equipment
- Electronic multifunction display, Stall warning system, ADS-B, Data recorder, Electronic flight bag or handheld device
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 58
- Injuries
- None
- Certificate
- Private
- Airplane ratings
- Single-engine sea, Single-engine land
- Medical
- Class 2, With waivers/limitations
- Last flight review
- April 28, 2020
- Seat
- Left
- Restraint
- 4-point
- Flight hours
- 1,263 total · 311 in this make and model · 1,106 as pilot in command · 52 in the last 90 days · 24 in the last 30 days · 4 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Night
- Wind
- 280° at 8 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 81 °F, dew point 48 °F
- Altimeter
- 30.06 inHg
- Turbulence
- Unknown
- Observed at
- KDLS, 16 nm away
- METAR
- METAR KDLS 240453Z AUTO 28008KT 10SM CLR 27/09 A3006 RMK AO2 SLP177 T02670094
Docket · 11
The files NTSB released with the investigation on February 28, 2023, on NTSB’s docket system: statements, records, photos and specialists’ reports. 11.2 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.