Cessna 182G accident near Cascade, Idaho, May 13, 2018
On May 13, 2018 at about 6:30 pm local time, a 1964 Cessna 182G, registered N2377R, was destroyed in an accident during enroute (cruise) near Cascade, Idaho. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The non-instrument-rated pilot's improper decision to initiate a visual flight rules flight into an area with low ceilings due to mountain obscuration, which resulted in controlled flight into terrain.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 13, 2018 · about 6:30 pm local time
- Place
- Cascade, Idaho · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 182G G, built 1964 · all 182Gs on the register
- Registration
- N2377R · no longer on the register · serial 18255477
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The private pilot had planned to fly his airplane to his newly purchased hangar at the destination airport. On the morning of the accident, the pilot monitored weather conditions along his proposed route of flight through internet applications and highway traffic cameras. The pilot told a friend that the ceilings at the destination airport were about 700 ft and rising and that the traffic cameras showed marginal weather conditions. The pilot also told his friend that he would wait to depart until early to mid-afternoon as long as the weather conditions improved. The investigation could not determine, with the available evidence, whether the pilot was aware of the published AIRMETs for mountain obscuration and icing along his route of flight during the time surrounding the accident. When the pilot departed, the weather at the destination airport was consistent with visual meteorological conditions. However, another pilot flying a similar route as the accident pilot (but in the opposite direction) experienced low ceilings near the accident site shortly before the accident, so that pilot reversed course and landed safely. Radar data associated with the accident airplane and the debris path signatures indicated that the accident pilot likely encountered similar weather conditions and started to reverse course when the airplane impacted tree tops and then the ground. The orientation and length of the wreckage path were consistent with controlled flight into terrain. Postaccident examination of the airframe and engine revealed no evidence of any preimpact mechanical malfunctions or failures. The pilot did not hold an instrument rating. He may have been aware of the AIRMETs for mountain obscuration and icing along his route of flight as he had been monitoring highway traffic cameras for any improvement in the weather conditions. Nevertheless, his poor decision to attempt the flight was likely influenced by his long-anticipated desire to finish moving into his new hangar at his destination airport. The pilot's route of flight was along a highway about 4,800 ft mean sea level located in a valley bordered by 5,500 foot tall mountains to his left and 6,500 foot tall mountains on his right and an overcast cloud layer at 1,100 ft above ground level. Radar data showed an airplane in a turn from a northern heading to a southern heading was likely from the accident airplane as it terminated near the accident site. This evidence and the impact signatures suggests the pilot probably encountered ground fog or an area of low visibility, but impacted a tree and terrain while attempting to turn around. After the accident airplane departed, the pilot was handed off to a developmental (trainee) departure controller who provided radar services for the airplane in class C airspace, even though the airplane did not have a functioning transponder, which was inconsistent with the air traffic control (ATC) facility's standard operating procedures. Further, the developmental departure controller did not inform the controller relieving him, during the position relief briefing, of the accident airplane, which was also inconsistent with standard operating procedures. As a result, the oncoming departure controller was unable to track the accident airplane's position (because there were no alphanumeric data associated with the radar target) or terminate radar services when the airplane left the class C airspace (because he was unaware of the flight). Additionally, although the developmental departure controller did not generate a flight progress strip or use a memory aid to track the accident airplane, the facility's standard operating procedures did not require the use of flight progress strips for departing visual flight rules airplanes. However, the use of a flight progress strip might have aided the departure controller's situational awareness of the airplane. Because the accident was not survivable, the delay in identifying that the airplane had crashed did not impact the survivability of the accident. Although some of the ATC services provided for the accident flight after takeoff were not performed in accordance with the facility's standard operating procedures, those ATC services did not likely contribute to the circumstances of the accident. Had the lack of a functioning transponder impacted operations, the ATC facility would have advised the pilot that he could not proceed or to wait until an opportunity of reduced traffic.
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
- VFR encounter with IMC during enroute (cruise)
- Controlled flight into terrain or object (CFIT) during enroute (cruise) defining event
The NTSB's findings
- cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- cause Personnel issues › Experience/knowledge › Experience/qualifications › Total instrument experience › Pilot
- cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Obscuration › Decision related to condition
- cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Obscuration › Effect on operation
- cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling › Decision related to condition
- cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling › Effect on operation
- Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Contributed to outcome
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 328.6 hours in all; 231 in this make and model
- Last flight review: September 3, 2017
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 4,878 hours
- Last inspection: annual inspection, November 11, 2017; 16 hours since
- Maximum gross weight: 2,348 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental Motors O-470 (piston); 6,335 hours total
The flight
- Departed from: BOI Boise ID at 6:08 pm
- Destination: MYL Mc Call ID
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 320° at 4 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 7,000 ft
- Temperature: 57°F (14°C), dew point 45°F (7°C)
- Altimeter: 30.02 inHg
- Observation at 5:53 pm, 40 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
18 documents, released by the NTSB on April 17, 2020. 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.
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
