Cessna 185 accident near Prineville, Oregon, October 28, 2011
On October 28, 2011 at about 8:50 pm local time, a Cessna 185, registered N520YH, was substantially damaged in an accident during enroute (descent) near Prineville, Oregon (Bend Municipal Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A total loss of engine power due to fuel starvation, which resulted from the pilot inadvertently leaving the fuel selector set to the left tank. Contributing to the accident was the pilot’s deviation from his normal habit pattern and his failure to refer to the in-flight engine failure checklist after the engine power loss.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 28, 2011 · about 8:50 pm local time · cases in 2011
- Place
- Prineville, Oregon · Bend Municipal Airport · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 3 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 185 · all 185s on the register
- Registration
- N520YH · registry record · serial 18503619
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
During the descent to the destination airport, when the airplane was about 10 miles out and descending through about 6,500 feet, the engine experienced a total loss of power. In response to the power loss, the pilot manipulated the throttle, mixture, and propeller controls, but the engine did not regain power. When the pilot recognized that the airplane would not be able to reach the destination airport, he conducted a forced landing on an unpaved road. During the landing roll at a groundspeed of about 10 mph, the airplane struck some vegetation, and it then nosed over onto its back. The pilot reported that, at the time of the engine power loss, the electronic fuel flow instrument indicated that 16 gallons of usable fuel was remaining, which he believed was sufficient fuel for about 1 more hour of flight and to reach the destination airport. During recovery, the fuel tanks were observed to contain about 16 gallons of total fuel, and the fuel selector handle was found set to the left tank. However, it was determined that some fuel had migrated from the fuller right tank to the nearly empty left tank via the tank vent line while the airplane was inverted. The pilot stated that his typical habit was to operate the airplane with the fuel selector set to the "both" position, but that, at some point during the flight, he had moved the fuel selector to the left tank to correct a fuel imbalance with the intention of resetting it to the "both" position once the imbalance had been corrected. The pilot reported that he realized that he had forgotten to reset the fuel selector to the "both" position and that this caused the power loss. The pilot reported that he did not manipulate the fuel selector handle after the power loss because he did not believe that he had a fuel problem and that he did not refer to any emergency checklists. The Pilot's Operating Handbook contained an engine failure during flight checklist, which included the step to place the fuel selector valve in the "both" position, which the pilot did not do.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (total) during enroute (descent) defining event
- Off-field or emergency landing during enroute (descent)
The NTSB's findings
- cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Incorrect use/operation other cases naming the fuel system
- cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
- factor Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot
- factor Personnel issues › Task performance › Use of equip/info › Use of policy/procedure › Pilot
- cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid level other cases naming the fuel system
Pilot
- Certificate: airline transport pilot, flight instructor, commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 3,820 hours in all; 838 in this make and model; 30 in the last 90 days; 10 in the last 30 days; 3,396 as pilot in command; 228 on instruments
- Last flight review: October 14, 2011
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 8,131 hours
- Last inspection: annual inspection, November 2, 2010
- Maximum gross weight: 3,350 lb
- Seats: 4
- Landing gear: fixed
- Engine: Teledyne Continental IO-550 (piston); 0 hours total
The flight
- Departed from: Riggins ID at 6:30 pm
- Destination: BDN Bend OR
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 210° at 9 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 63°F (17°C), dew point 10°F (-12°C)
- Altimeter: 30.05 inHg
- Observation at 8:50 pm from BDN, 10 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
11 documents, released by the NTSB on April 24, 2014. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 10 pages | View Download |
| 2 | Sheriff Report Excerpts | PDF, 3 pages | View Download |
| 3 | Record of Conversation - Pilot | PDF, 2 pages | View Download |
| 4 | Record of Conversation - FAA Inspector | PDF, 2 pages | View Download |
| 5 | Recorder 17 - Specialist's Factual Report of Investigation | PDF, 6 pages | View Download |
| 6 | Recorder 17 - Attachment 1 Data to Support Specialist's Factual Investigation | data file | Download |
| 7 | Metars | PDF, 1 page | View Download |
| 8 | Photo 1. Road and Airplane (Crook County Sheriffs Office Photo) | PDF, 1 page | View Download |
| 9 | Photo 2. Front View (Ccso Photo) | PDF, 1 page | View Download |
| 10 | Photo 3. Aft View (Ccso Photo) | PDF, 1 page | View Download |
| 11 | Photo 4. Lower Instrument Panel (Crook County Sheriff Photo) | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N520YH on the register today · the tail number may have moved to another aircraft since
- Cessna 185 Skywagon 228 registered today · the model family and its accident history
- Cessna 72,677 aircraft on the register
- Engine: Teledyne Continental IO-550 3,077 aircraft carry this series today · as the NTSB recorded it
- Bend Municipal · nearest airport
- Accidents and incidents in Oregon 1,864 since 1982 · 279 in the last ten years
- Oregon 7,002 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR12LA023.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
