The U.S. aircraft register, updated daily
Accidents · NTSB WPR20LA194 · Final report

Cessna 182 accident near Imnaha, Oregon, June 24, 2020

On June 24, 2020 at about 2:41 am local time, a 1971 Cessna 182, registered N9169G, was substantially damaged in an accident during initial climb near Imnaha, Oregon (Memaloose Usfs airport). It was a personal flight under general aviation rules (Part 91). 2 people were seriously injured; 2 others were unhurt. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s excessively high pitch attitude and failure to maintain adequate airspeed during takeoff, which resulted in an exceedance of the airplane’s critical angle of attack and impact with terrain. Contributing to the accident was the pilot’s fatigue and his incomplete actions to abort the takeoff.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 24, 2020 · about 2:41 am local time · cases in 2020
Place
Imnaha, Oregon · Memaloose Usfs · cases near this airport · map
Type
Accident
Injuries
2 people were seriously injured; 2 others were unhurt.
Weather
visual conditions (good weather)
Aircraft
Cessna 182 N, built 1971 · all 182s on the register
Registration
N9169G · registry record · serial 182
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot and three passengers were making an intermediate stopover at a mountain airstrip to camp with his family. They overflew the destination airport, and the pilot did not observe any concerns, but after they landed at the airport, the airplane became lodged in soft dirt. After several hours, they freed the airplane and decided to return to the airport they had departed from that morning. The pilot stated he felt the airplane begin to lift off the ground early during takeoff, so he maintained a nose low attitude to build up airspeed before starting a climb. When the airplane reached midfield, the pilot suddenly felt the airplane slow down and assumed the landing gear had contacted the runway. He wanted to abort the takeoff, but instead decided to fly the airplane as it had suddenly started to climb. Nearing the end of the runway he shoved the yoke forward after he heard the stall warning horn, but the airplane rolled to the right and impacted the ground. The pilot reported no preimpact mechanical malfunctions or failures with the airplane or engine that could have precluded normal operation. Contrary to the pilot’s recollection of events, flight data showed the airplane pitch increased excessively during the takeoff and the initial climb, and engine power decreased to about idle power as the airplane rotated, continued to climb, and airspeed decreased below stall speed. The stall warning horn likely engaged about the time the airplane’s critical angle of attack was exceeded, resulting in an aerodynamic stall and subsequent impact with terrain. Performance computations for the accident flight were consistent with the pilot’s, which suggested the airplane had sufficient takeoff distance to depart the runway, despite a high-density altitude. Weight and balance computations showed that the airplane was not over gross weight or outside of center of gravity limitations but that it was in a state of forward center of gravity at the time of the accident. The forward center of gravity would have resulted in a nose-heavy condition that required additional back pressure to maintain control during takeoff. The investigation did not find any evidence to suggest the airplane “slowed” during takeoff as the pilot suggested, but a wet patch on the runway or natural obstacles such as small rocks could have been present and adversely affected the takeoff roll. The accident pilot was likely fatigued after working for several hours to free the airplane from being lodged in soft dirt. This factor, coupled with stress and the pilot’s reported self-induced pressure to depart the airport, may have impaired the pilot’s judgment and decision making, causing him to overlook some of the risks associated with this departure. The fatigue likely also affected his ability to properly respond during the takeoff attempt.

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

  1. Loss of control in flight during initial climb defining event
  2. Aerodynamic stall/spin during initial climb
  3. Collision with terrain or object (not controlled flight into terrain) during initial climb

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
  • Personnel issues › Psychological › Personality/attitude › Motivation/respond to pressure › Pilot
  • Environmental issues › Physical environment › Terrain › Rough terrain › Effect on operation
  • Environmental issues › Task environment › Pressures/demands › Personal pressure › Awareness of condition
  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Not attained/maintained
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Pitch control › Not attained/maintained

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 771.9 hours in all; 163.6 in this make and model; 43.4 in the last 90 days; 32.5 in the last 30 days; 716.7 as pilot in command; 0 on instruments
  • Last flight review: December 16, 2019
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 5,268.7 hours
  • Last inspection: annual inspection, April 20, 2020; 36.7 hours since
  • Maximum gross weight: 2,950 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental O-470 UTS (piston); 5,268 hours total

The flight

  • Departed from: 25U Imnaha OR at 2:41 am
  • Destination: KLWS Lewiston ID
  • Flight plan: none
  • Runway 17/3, 3,300 ft by 120 ft

Weather at the time

  • Light: dusk
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 79°F (26°C), dew point 45°F (7°C)
  • Altimeter: 30.05 inHg
  • Observation at 2:51 am from KMYL, 41 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers12

Photographs from the investigation 3 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

14 documents, released by the NTSB on July 13, 2022. 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.

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

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR20LA194.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.