WPR20LA194 · Cessna 182 N
Cessna 182 N · Accident: loss of control in flight during initial climb
From Memaloose Airport (25U) to Lewiston Nez Perce County Airport (KLWS)
Event
- NTSB case
- WPR20LA194
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 182 N
- Aircraft type
- Cessna 182
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N9169G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Memaloose Airport (25U), Imnaha, ORTo Lewiston Nez Perce County Airport (KLWS), Lewiston, ID
- Aircraft age
- About 49 years (built 1971)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Initial climb
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20LA194
- Event ID
- 20200624X65620
- Case number
- WPR20LA194
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2020-06-24.
- API snapshot SHA-256: b165de659a5d7e57bbeb23661b8cacaa9fa1461a251ea88a03d43aba6b4fd1fb; retrieved 2026-09-16T11:55:55.306Z.