FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR18LA227 · Cessna 182 Q

18 Aug 2018 · Salmon, ID, United States

Cessna 182 Q · Accident: low altitude operation/event during initial climb

From 121D · Salmon, ID to McCall Municipal Airport (MYL)

Report a problem

Event

NTSB case
WPR18LA227
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 Q

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
N84CP
Operator
Unknown
Onboard fatalities
Unknown
Route
From 121D · Salmon, IDTo McCall Municipal Airport (MYL), McCall, ID
Aircraft age
About 39 years (built 1979)
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
Low altitude operation/event
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot-rated passenger reported that the accident pilot fueled the airplane then conducted a short formation flight of two airplanes with the accident airplane in the lead to a backcountry airstrip. The trail pilot reported that, during the briefing for the return flight, he and the accident pilot decided to take off to the north parallel to the west side of a river, and shortly after, to turn left 180° toward the south back toward the departure airport. According to the pilot-rated passenger, during takeoff and initial climb, the engine was producing power, and the airplane climbed as expected. The trail pilot, who watched the takeoff, confirmed that the takeoff and initial climb seemed normal. Shortly thereafter, the trail pilot saw the accident pilot make a 90° left turn toward the west and head up a canyon, which he said confused him because “you cannot out climb the rising terrain to the west, and it is a tight little canyon to turn in.” He indicated in a postaccident statement that he then asked the accident pilot, “where are you going? And, the pilot replied, “we’re going down.” The trail pilot indicated that he then asked the accident pilot if he was going “downstream,” and the accident pilot responded, “’crashing’ or something similar.” He received no further communication from the accident pilot. The pilot-rated passenger stated that he was unaware of any issues with the airplane before the accident pilot’s exchange with the trail pilot. He added that, after the accident, the accident pilot told him that he thought that the loss of lift was due to the airplane encountering a downdraft. He then looked at the cockpit panel and saw that the manifold pressure gauge was reading 20 inches of manifold pressure. He opined that the engine was not producing power and that the airplane was descending. According to the pilot-rated passenger, the accident pilot then said he was going “to put the[air]plane in some trees.” The passenger stated that the accident pilot turned slightly to the left, he managed the airspeed, and then the airplane settled into a stand of trees “slow and level” as the stall warning horn was “chirping.” The airplane became lodged in the trees about 10 to 12 ft above the ground. When the passenger noticed fire emanating from the engine cowling, he and the accident pilot egressed the airplane. Shortly thereafter, the airplane exploded and was subsequently consumed by fire.

Examination of the area that bordered the departure route revealed that it was very confined with a turn radius of about 800 ft and that rising terrain higher than 6,500 ft mean sea level existed on the east and west sides of the north/south-oriented river.

The airframe and engine were destroyed by the postimpact fire; however, examination of the available evidence did not reveal any mechanical failures or malfunctions that would have precluded normal operation. Based on the accident pilot’s conversation with the pilot-rated passenger, the airplane likely lost altitude due to an inadvertent encounter with downdraft conditions, and due to the loss of altitude, the confined area of the canyon did not allow the pilot to attempt the 180° course reversal. The pilot continued heading upstream in the middle of the canyon to make a precautionary landing to unsuitable mountainous terrain at the slowest airspeed possible while maintaining airplane control as it collided with trees.

Probable cause

The pilot’s inadvertent encounter with downdraft conditions, which resulted in a loss of altitude, and the pilot’s subsequent decision to conduct a precautionary landing into a stand of trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR18LA227
Event ID
20180819X22925
Case number
WPR18LA227
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
  • 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: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 0903608d75408750b145ea0fb560c1e17939ee76a2e90b22f83cc6a861d309c9; retrieved 2026-09-16T08:06:50.696Z.
  • Corrected after a review of the NTSB narrative, which states these values explicitly: damage. Narrative states the airplane exploded and was consumed by fire and that the airframe and engine were destroyed by the postimpact fire.