FlarePath
Cases › WPR14FA044 · Part 135 fatal

CESSNA U206FMcCall Aviation Inc.

Donnelly, ID, USA · 2013-11-06·N206KL

3
fatal
0
serious
Fatal
highest injury
Destroyed
damage

What happened

NTSB summary, verbatim

Before departing on the cross-country flight over mountainous terrain, the accident pilot and two other pilots going to the same remote airstrip discussed the weather and checked webcams positioned throughout the passes. The accident pilot took off first and flew south before turning east to cross the mountains, while the other two pilots chose to fly north before crossing the mountains. Inflight radio communications from the accident pilot indicated that when he first turned east to cross the mountains, he encountered weather that required him to turn around and fly further south before turning east again. No further radio communications from the accident pilot were heard. The other two pilots reported encountering marginal weather with low clouds during their flights to the destination, which they completed without incident. Flight track data downloaded from the accident airplane's onboard GPS unit indicated that, during the final 40 seconds of the flight, the airplane made a left turn of about 90 degrees followed by a right turn of about 180 degrees while maintaining an altitude of about 8,150 ft. This flightpath suggests that the pilot was following the contour of the horseshoe-shaped ridgeline at that location. However, the ridgeline varied in elevation between about 8,000 and 8,200 ft, and the airplane impacted steep, heavily wooded terrain about 100 ft below the top of the ridgeline. A postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation. Due to the location of the accident site, weather reporting stations and weather products were limited. Satellite imagery did not show low-level clouds because of a mid-level cloud layer at 15,000 ft. A weather model run to simulate relative humidity over the accident site revealed that the lower altitudes above terrain likely had a much lower visibility with relative humidity greater than 98%. Thus, it is likely that the pilot was maneuvering the airplane in or near low clouds when he lost visual contact with the ground resulting in controlled flight into terrain.  

Photographs

11the aircraft, and what the investigators found
Wreckage and site documentation · 11 photographs from the docket

Photographs are NTSB docket attachments — works of the US government, in the public domain. Captions are the Board’s own.

Probable cause

the Board's determination
The pilot's failure to maintain clearance from terrain while maneuvering in likely low-ceiling and low-visibility conditions in mountainous terrain.

Occurrence sequence

2 stepsNTSB coding · CICTT taxonomy
  1. 1 · Maneuvering-low-alt flying
    VFR encounter with IMC
  2. 2 · Maneuvering
    Controlled flight into terr/obj (CFIT)
    defining event

Findings

4 causal · 0 contributing
  • CAUSE
    Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude — Not attained/maintained
  • CAUSE
    Personnel issues › Task performance › Use of equip/info › Aircraft control — Pilot
  • CAUSE
    Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low visibility — Effect on operation
  • CAUSE
    Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling — Effect on operation

NTSB analysis

from the final report

Before departing on the cross-country flight over mountainous terrain, the accident pilot and two other pilots going to the same remote airstrip discussed the weather and checked webcams positioned throughout the passes. The accident pilot took off first and flew south before turning east to cross the mountains, while the other two pilots chose to fly north before crossing the mountains. Inflight radio communications from the accident pilot indicated that when he first turned east to cross the mountains, he encountered weather that required him to turn around and fly further south before turning east again. No further radio communications from the accident pilot were heard. The other two pilots reported encountering marginal weather with low clouds during their flights to the destination, which they completed without incident. Flight track data downloaded from the accident airplane's onboard GPS unit indicated that, during the final 40 seconds of the flight, the airplane made a left turn of about 90 degrees followed by a right turn of about 180 degrees while maintaining an altitude of about 8,150 ft. This flightpath suggests that the pilot was following the contour of the horseshoe-shaped ridgeline at that location. However, the ridgeline varied in elevation between about 8,000 and 8,200 ft, and the airplane impacted steep, heavily wooded terrain about 100 ft below the top of the ridgeline. A postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation. Due to the location of the accident site, weather reporting stations and weather products were limited. Satellite imagery did not show low-level clouds because of a mid-level cloud layer at 15,000 ft. A weather model run to simulate relative humidity over the accident site revealed that the lower altitudes above terrain likely had a much lower visibility with relative humidity greater than 98%. Thus, it is likely that the pilot was maneuvering the airplane in or near low clouds when he lost visual contact with the ground resulting in controlled flight into terrain.