FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR18FA141 · Cessna 182G G

13 May 2018 · Cascade, ID, United States

Cessna 182G G · Accident: controlled flight into terrain/object (CFIT) en route

From Boise Air Terminal/Gowen Field (BOI) to McCall Municipal Airport (MYL)

Report a problem

Event

NTSB case
WPR18FA141
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
1 · 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 182G G

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
N2377R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Boise Air Terminal/Gowen Field (BOI), Boise, IDTo McCall Municipal Airport (MYL), MC CALL, ID
Aircraft age
About 54 years (built 1964)
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
En route · cruise
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
Controlled flight into terrain/object (CFIT)
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Experience/knowledge

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

NTSB narrative

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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR18FA141
Event ID
20180514X82202
Case number
WPR18FA141
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: investigation status. 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: 1e75813c534f2115a7dcd808e68c8c028915999b51628f42819e3e437cda2bbf; retrieved 2026-09-15T06:40:40.331Z.