Crash of a De Havilland DHC-2 Beaver off Seldovia: 1 killed

Date & Time: Jul 19, 2019 at 1010 LT
Type of aircraft:
Operator:
Registration:
N68083
Flight Phase:
Survivors:
Yes
Schedule:
Seldovia – Anchorage
MSN:
1254
YOM:
1958
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2689
Captain / Total hours on type:
150.00
Aircraft flight hours:
29448
Circumstances:
The pilot stated that, during takeoff in the float-equipped airplane, he saw the left float begin to move into his peripheral vision from the left cockpit window and the airplane began to yaw to the left. The left wing subsequently impacted the water and the airplane nosed over, separating the right wing from the fuselage. The passengers consistently reported choppy water conditions at the time of the accident; one passenger reported that white caps were visible on the ocean waves in the distance. The passengers said that, during the takeoff, the airplane impacted a swell or wave and nosed over abruptly, and the cabin rapidly filled with water. Examination of the float assembly revealed fractures in the left front flying wire attachment fitting and the right rear flying wire attachment strap and hole elongation in the left rear flying wire attachment fitting. Additionally, the bolts attaching the two left flying wire attachment fittings to the left float were bent, and the two flying wires that had been attached to the fractured attachment fitting and attachment strap were buckled. While some areas of corrosion were observed on the fractured left forward fitting, the total area of corrosion was a small percentage of the total cross-section, and the remainder of the fracture and associated deformation of the lug was consistent with ductile overstress fracture. Similar areas of corrosion were also observed on each of the intact flying wire attachment fittings. Post-accident testing completed by the float manufacturer revealed that buckling of flying wires similar to that observed on the accident airplane was only reproduced at strap and fitting failure loads above 9,000 pounds force; the design specification load was 3,453 pounds of force. This indicates that the small amount of corrosion present on the fractured flying wire attachment fitting did not reduce its loadcarrying capability below the design specification load of 3,453 pounds of force, and that both the flying wire attachment fitting and flying wire attachment strap fractured due to overload. Therefore, it is likely that the accident airplane floats were subject to forces that exceeded their design limitations, resulting in overload of the flying wires attached to the left float. It is also likely that, given the lack of damage on either float, the force was due to impact with an ocean wave or swell and not by striking an object.
Probable cause:
The airplane's floats impact with an ocean wave or swell, which exceeded the design load specifications of the flying wire assemblies and resulted in a partial separation of the float assemblies.
Final Report:

Crash of a Cessna 208B Grand Caravan in Bethel

Date & Time: Jul 8, 2019 at 1505 LT
Type of aircraft:
Operator:
Registration:
N9448B
Survivors:
Yes
Schedule:
Newtok – Bethel
MSN:
208B-0121
YOM:
1988
Flight number:
GV262
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2258
Captain / Total hours on type:
787.00
Aircraft flight hours:
21206
Circumstances:
The commercial pilot was conducting a visual flight rules scheduled passenger flight with five passengers. During the return leg to the company’s base airport, the pilot requested, and was given clearance to, a short gravel runway of 1,858 ft that terminated at parallel cross-runways and had inbound airplanes. The wind was reported as variable at 3 knots, and the outside air temperature was 88°F which was 25° warmer than usual. The pilot stated that he conducted a steeper than normal approach and performed a normal 30° flap landing flare; however, the airplane floated halfway down the runway. He initiated a go-around by advancing the throttle to takeoff power and retracting the flaps to 20° as the main landing gear briefly touched down. Automatic dependent surveillance-broadcast (ADS-B) data indicated that the airplane arrived 0.1 mile from the runway threshold at 149 ft above ground level (agl) and 110 knots of ground speed, which was 32 knots faster than the short field landing approach speed listed in the pilot operating handbook. A witness in the air traffic control tower (the ground controller) stated that the airplane “bled off a lot of airspeed,” during the landing attempt and climbed out in a very flat profile. The tower local controller stated that after liftoff, the airplane’s right wing dropped and the airplane appeared to be turning right into conflicting landing traffic, so he twice instructed the airplane to “left turn out immediately.” The pilot stated that he attempted to comply with the tower controller’s instruction, but when he applied left aileron, the airplane appeared to stall, rolled rapidly right, and descended in a right-wing-low attitude. It subsequently impacted the surface between runways. A postimpact fire ensued, and the pilot helped the passengers egress. The airplane was destroyed by postimpact fire. Given the evidence, it is likely that the pilot decided to land on the short runway to expedite the arrival and did not perform an appropriate short field landing approach, which resulted in excessive airspeed and altitude over the runway threshold, a long landing flare, rapid deceleration, and a self-initiated go-around from a slow airspeed. Had the pilot initiated the go-around as he approached the runway with indications of an unstable visual approach, the airspeed would have been well above stall speed, which would have allowed for the desired positive climb out on runway heading. The pilot likely attempted to comply with the tower local controller’s urgent commands to turn while the airplane was near the limit of performance (the temperature was about 25 degrees warmer than average, which would have resulted in a higher density altitude than the pilot was accustomed to and degraded aircraft and engine performance). The pilot’s maneuvering resulted in the exceedance of the critical angle-of-attack of the high wing (right wing) during the left turn, and an aerodynamic stall.
Probable cause:
The pilot’s failure to maintain adequate airspeed while maneuvering during an attempted go around, which resulted in an exceedance of the airplane's critical angle of attack and an aerodynamic stall at low altitude. Contributing to the accident, was the pilot’s decision to perform an approach to a short runway at an excessive airspeed and his late decision to perform a go-around, which resulted in a slow climb at a reduced safe margin above stall airspeed.
Final Report:

Crash of a De Havilland DHC-2 Beaver off Metlakatla: 2 killed

Date & Time: May 20, 2019 at 1556 LT
Type of aircraft:
Operator:
Registration:
N67667
Survivors:
No
Schedule:
Ketchikan – Metlakatla
MSN:
1309
YOM:
1959
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1623
Captain / Total hours on type:
20.00
Aircraft flight hours:
29575
Circumstances:
The commercial pilot was conducting his first scheduled commuter flight from the company’s seaplane base to a nearby island seaplane base with one passenger and cargo onboard. According to company pilots, the destination harbor was prone to challenging downdrafts and changing wind conditions due to surrounding terrain. Multiple witnesses at the destination stated that the airplane made a westerly approach, and the wind was from the southeast with light chop on the water. Two witnesses reported the wings rocking left and right before touchdown. One witness stated that a wind gust pushed the tail up before the airplane landed. A different witness reported that the airplane was drifting right during the touchdown, and another witness saw the right (downwind) float submerge under water after touchdown, and the airplane nosed over as it pivoted around the right wingtip, which impacted the water. Flight track and performance data from the cockpit display units revealed that, as the airplane descended on the final approach, the wind changed from a right headwind of 6 knots to a left quartering tailwind of 8 knots before touchdown. The crosswind and tailwind components were within the airplane’s operational limitations. Examination of the airframe, engine, and associated systems revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation or egress. During the final approach and descent, the pilot had various wind information available to him; the sea surface wind waves and signatures, the nearest airport observation winds, the cockpit display calculated wind, and the visual relative ground speed. Had the pilot recognized that the winds had shifted to a quartering tailwind and the airplane’s ground speed was faster than normal, he could have aborted the landing and performed another approach into the wind. Although crosswind landings were practiced during flight training, tailwind landings were not because new pilots were not expected to perform them. Although the crosswind component was well within the airplane’s limits, it is possible that combined with the higher ground speed, the inexperienced pilot was unable to counteract the lateral drift during touchdown in a rapidly shifting wind. The pilot was hired the previous month with 5 hours of seaplane experience, and he completed company-required training and competency checks less than 2 weeks before the accident. According to the chief pilot (CP), company policy was to assign newly hired pilots to tour flights while they gained experience before assigning them to commuter flights later in the season. The previous year, the CP distributed a list of each pilot’s clearances for specific types of flights and destinations; however, an updated list had not been generated for the season at the time of the accident, and the flight coordinators, who were delegated operational control for assigning pilots to flights, and station manager were unaware of the pilot’s assignment limitations. Before the flight, the flight coordinator on duty completed a company flight risk assessment that included numerical values based on flight experience levels. The total risk value for the flight was in the caution area, which required management notification before releasing the flight, due to the pilot’s lack of experience in the accident airplane make and model and with the company, and his unfamiliarity with the geographical area; however, the flight coordinator did not notify management before release because the CP had approved a tour flight with the same risk value earlier in the day. Had the CP been notified, he may not have approved of the pilot's assignment to the accident flight. The pilot's minimal operational experience in seaplane operations likely affected his situational awareness in rapidly changing wind conditions and his ability to compensate adequately for a quartering tailwind at a higher-than-normal ground speed, which resulted in a loss of control during the water landing and a subsequent nose-over.
Probable cause:
The pilot’s inadequate compensation for a quartering tailwind during a water landing, which resulted in a loss of control and subsequent nose-over. Contributing to the accident was the company’s inadequate operational control of the flight release process, which resulted in assignment of an inexperienced pilot to a commuter seaplane flight.
Final Report:

Crash of a De Havilland DHC-3T Otter in the George Inlet: 1 killed

Date & Time: May 13, 2019 at 1221 LT
Type of aircraft:
Operator:
Registration:
N959PA
Flight Phase:
Survivors:
Yes
Schedule:
Ketchikan - Ketchikan
MSN:
159
YOM:
1956
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
25000
Aircraft flight hours:
30296
Circumstances:
On May 13, 2019, about 1221 Alaska daylight time, a float-equipped de Havilland DHC-2 (Beaver) airplane, N952DB, and a float-equipped de Havilland DHC-3 (Otter) airplane, N959PA, collided in midair about 8 miles northeast of Ketchikan, Alaska. The DHC-2 pilot and four passengers sustained fatal injuries. The DHC-3 pilot sustained minor injuries, nine passengers sustained serious injuries, and one passenger sustained fatal injuries. The DHC-2 was destroyed, and the DHC-3 sustained substantial damage. The DHC-2 was registered to and operated by Mountain Air Service LLC, Ketchikan, Alaska, under the provisions of Title 14 Code of Federal Regulations (CFR) Part 135 as an on-demand sightseeing flight. The DHC-3 was registered to Pantechnicon Aviation LTD, Minden, Nevada, and operated by Venture Travel, LLC, dba Taquan Air, Ketchikan, Alaska, under the provisions of Part 135 as an on-demand sightseeing flight. Visual meteorological conditions prevailed in the area at the time of the accident. According to information provided by the operators, both airplanes had been conducting sightseeing flights to the Misty Fjords National Monument area. They were both converging on a scenic waterfall in the Mahoney Lakes area on Revillagigedo Island before returning to the Ketchikan Harbor Seaplane Base (5KE), Ketchikan, Alaska, when the accident occurred. According to recorded avionics data recovered from the DHC-3, it departed from an inlet (Rudyerd Bay) in the Misty Fjords National Monument area about 1203 and followed the inlet westward toward Point Eva and Manzanita Island. At 1209, at an altitude between 1,900 and 2,200 ft, the DHC-3 crossed the Behm Canal then turned to the southwest about 1212 in the vicinity of Lake Grace. Automatic dependent surveillance-broadcast (ADS-B) tracking data for both airplanes, which were provided by the Federal Aviation Administration (FAA), began at 1213:08 for the DHC-3, and at 1213:55 for the DHC-2. At 1217:15, the DHC-3 was about level at 4,000 ft mean sea level (msl) over Carroll Inlet on a track of 225°. The DHC-2 was 4.2 nautical miles (nm) south of the DHC-3, climbing through 2,800 ft, on a track of 255°. The DHC-3 pilot stated that, about this time, he checked his traffic display and “there were two groups of blue triangles, but not on my line. They were to the left of where I was going.” He stated that he did not observe the DHC-2 on his traffic display before the collision. The ADS-B data indicated that, about 1219, the DHC-3 started a descent from 4,000 ft, and the DHC-2 was climbing from 3,175 ft. During the next 1 minute 21 seconds, the DHC-3 continued to descend on a track between 224° and 237°, and the DHC-2 leveled out at 3,350 ft on a track of about 255°. Between 1220:21 and 1221:14, the DHC-3 made a shallow left turn to a track of 210°, then a shallow right turn back to a track of 226°. The airplanes collided at 1221:14 at an altitude of 3,350 ft, 7.4 nm northeast of 5KE. The ADS-B data for both airplanes end about the time of the collision. The DHC-2 was fractured into multiple pieces and impacted the water and terrain northeast of Mahoney Lake. Recorded avionics data for the DHC-3 indicate that at 1221:14, the DHC-3 experienced a brief upset in vertical load factor and soon after entered a right bank, reaching an attitude about 50° right wing down at 1221:19 and 27° nose down at 1221:22. The DHC-3 began descending and completed a 180° turn before impacting George Inlet at 1222:15 along a northeast track.
Probable cause:
The NTSB determines that the probable cause of this accident was the inherent limitations of the see-and-avoid concept, which prevented the two pilots from seeing the other airplane before the collision, and the absence of visual and aural alerts from both airplanes’ traffic display systems, while operating in a geographic area with a high concentration of air tour activity.
Contributing to the accident were
1) the Federal Aviation Administration’s provision of new transceivers that lacked alerting capability to Capstone Program operators without adequately mitigating the increased risk associated with the consequent loss of the previously available alerting capability and
2) the absence of a requirement for airborne traffic advisory systems with aural alerting among operators who carry passengers for hire.
Final Report:

Crash of De Havilland DHC-2 Beaver in the Goerge Inlet: 5 killed

Date & Time: May 13, 2019 at 1221 LT
Type of aircraft:
Operator:
Registration:
N952DB
Flight Phase:
Survivors:
No
Schedule:
Ketchikan - Ketchikan
MSN:
237
YOM:
1952
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
11000
Aircraft flight hours:
16452
Circumstances:
On May 13, 2019, about 1221 Alaska daylight time, a float-equipped de Havilland DHC-2 (Beaver) airplane, N952DB, and a float-equipped de Havilland DHC-3 (Otter) airplane, N959PA, collided in midair about 8 miles northeast of Ketchikan, Alaska. The DHC-2 pilot and four passengers sustained fatal injuries. The DHC-3 pilot sustained minor injuries, nine passengers sustained serious injuries, and one passenger sustained fatal injuries. The DHC-2 was destroyed, and the DHC-3 sustained substantial damage. The DHC-2 was registered to and operated by Mountain Air Service LLC, Ketchikan, Alaska, under the provisions of Title 14 Code of Federal Regulations (CFR) Part 135 as an on-demand sightseeing flight. The DHC-3 was registered to Pantechnicon Aviation LTD, Minden, Nevada, and operated by Venture Travel, LLC, dba Taquan Air, Ketchikan, Alaska, under the provisions of Part 135 as an on-demand sightseeing flight. Visual meteorological conditions prevailed in the area at the time of the accident. According to information provided by the operators, both airplanes had been conducting sightseeing flights to the Misty Fjords National Monument area. They were both converging on a scenic waterfall in the Mahoney Lakes area on Revillagigedo Island before returning to the Ketchikan Harbor Seaplane Base (5KE), Ketchikan, Alaska, when the accident occurred. According to recorded avionics data recovered from the DHC-3, it departed from an inlet (Rudyerd Bay) in the Misty Fjords National Monument area about 1203 and followed the inlet westward toward Point Eva and Manzanita Island. At 1209, at an altitude between 1,900 and 2,200 ft, the DHC-3 crossed the Behm Canal then turned to the southwest about 1212 in the vicinity of Lake Grace. Automatic dependent surveillance-broadcast (ADS-B) tracking data for both airplanes, which were provided by the Federal Aviation Administration (FAA), began at 1213:08 for the DHC-3, and at 1213:55 for the DHC-2. At 1217:15, the DHC-3 was about level at 4,000 ft mean sea level (msl) over Carroll Inlet on a track of 225°. The DHC-2 was 4.2 nautical miles (nm) south of the DHC-3, climbing through 2,800 ft, on a track of 255°. The DHC-3 pilot stated that, about this time, he checked his traffic display and “there were two groups of blue triangles, but not on my line. They were to the left of where I was going.” He stated that he did not observe the DHC-2 on his traffic display before the collision. The ADS-B data indicated that, about 1219, the DHC-3 started a descent from 4,000 ft, and the DHC-2 was climbing from 3,175 ft. During the next 1 minute 21 seconds, the DHC-3 continued to descend on a track between 224° and 237°, and the DHC-2 leveled out at 3,350 ft on a track of about 255°. Between 1220:21 and 1221:14, the DHC-3 made a shallow left turn to a track of 210°, then a shallow right turn back to a track of 226°. The airplanes collided at 1221:14 at an altitude of 3,350 ft, 7.4 nm northeast of 5KE. The ADS-B data for both airplanes end about the time of the collision. The DHC-2 was fractured into multiple pieces and impacted the water and terrain northeast of Mahoney Lake. Recorded avionics data for the DHC-3 indicate that at 1221:14, the DHC-3 experienced a brief upset in vertical load factor and soon after entered a right bank, reaching an attitude about 50° right wing down at 1221:19 and 27° nose down at 1221:22. The DHC-3 began descending and completed a 180° turn before impacting George Inlet at 1222:15 along a northeast track.
Probable cause:
The NTSB determines that the probable cause of this accident was the inherent limitations of the see-and-avoid concept, which prevented the two pilots from seeing the other airplane before the collision, and the absence of visual and aural alerts from both airplanes’ traffic display systems, while operating in a geographic area with a high concentration of air tour activity.
Contributing to the accident were
1) the Federal Aviation Administration’s provision of new transceivers that lacked alerting capability to Capstone Program operators without adequately mitigating the increased risk associated with the consequent loss of the previously available alerting capability and
2) the absence of a requirement for airborne traffic advisory systems with aural alerting among operators who carry passengers for hire.
Final Report:

Crash of a Beechcraft B200 Super King Air off Kake: 3 killed

Date & Time: Jan 29, 2019 at 1811 LT
Operator:
Registration:
N13LY
Flight Type:
Survivors:
No
Schedule:
Anchorage - Kake
MSN:
BB-1718
YOM:
2000
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
17774
Captain / Total hours on type:
1644.00
Aircraft flight hours:
5226
Circumstances:
The pilot of the medical transport flight had been cleared by the air traffic controller for the instrument approach and told by ATC to change to the advisory frequency, which the pilot acknowledged. After crossing the initial approach fix on the RNAV approach, the airplane began a gradual descent and continued northeast towards the intermediate fix. Before reaching the intermediate fix, the airplane entered a right turn and began a rapid descent, losing about 2,575 ft of altitude in 14 seconds; radar returns were then lost. A witness at the destination airport, who was scheduled to meet the accident airplane, observed the pilot-controlled runway lights illuminate. When the airplane failed to arrive, she contacted the company to inquire about the overdue airplane. The following day, debris was found floating on the surface of the ocean. About 48 days later, after an extensive underwater search, the heavily fragmented wreckage was located on the ocean floor at a depth of about 500 ft. A postaccident examination of the engines revealed contact signatures consistent with the engines developing power at the time of impact and no evidence of mechanical malfunctions or failures that would have precluded normal operation. A postaccident examination of the airframe revealed about a 10° asymmetric flap condition; however, significant impact damage was present to the flap actuator flex drive cables and flap actuators, indicating the flap actuator measurements were likely not a reliable source of preimpact flap settings. In addition, it is unlikely that a 10° asymmetric flap condition would result in a loss of control. The airplane was equipped with a total of 5 seats and 5 restraints. Of the three restraints recovered, none were buckled. The unbuckled restraints could suggest an emergency that required crewmembers to be up and moving about the cabin; however, the reason for the unbuckled restraints could not be confirmed. While the known circumstances of the accident are consistent with a loss of control event, the factual information available was limited because the wreckage in its entirety was not recovered, the CVR recording did not contain the accident flight, no non-volatile memory was recovered from the accident airplane, and no autopsy or toxicology of the pilot could be performed; therefore, the reason for the loss of control could not be determined. Due to the limited factual information that was available, without a working CVR there is little we know about this accident.
Probable cause:
A loss of control for reasons that could not be determined based on the available information.
Final Report:

Crash of a De Havilland DHC-2 Beaver in Igiugig

Date & Time: Sep 20, 2018 at 1530 LT
Type of aircraft:
Operator:
Registration:
N121AK
Flight Phase:
Survivors:
Yes
MSN:
121
YOM:
1951
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12496
Captain / Total hours on type:
5000.00
Circumstances:
The pilot of the float-equipped airplane reported that, during the initial climb after a water takeoff, about 200 feet, he turned right, and the engine lost power. He immediately switched fuel tanks and attempted to restart the engine to no avail. The airplane descended and struck trees, and the right wing impacted terrain. The airplane sustained substantial damage to the right wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The pilot reported to the Federal Aviation Administration inspector that, during the initial climb and after the engine lost power, he noticed that the center tank, which was selected for takeoff, was empty. He added that passengers stated that the engine did regain power after switching tanks, but the airplane had already struck trees. The pilot reported as a recommendation to more closely follow checklists.
Probable cause:
The pilot's selection of an empty fuel tank for takeoff, which resulted in fuel starvation and the subsequent total loss of engine power.
Final Report:

Crash of a De Havilland DHC-2 Beaver I on Mt Kahiltna: 5 killed

Date & Time: Aug 4, 2018 at 1753 LT
Type of aircraft:
Operator:
Registration:
N323KT
Flight Phase:
Survivors:
No
Site:
Schedule:
Talkeetna - Talkeetna
MSN:
1022
YOM:
1957
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
2550
Captain / Total hours on type:
346.00
Aircraft flight hours:
15495
Circumstances:
The commercial pilot was conducting a 1-hour commercial air tour flight over Denali National Park and Preserve with four passengers on board. About 48 minutes after departure, the Alaska Rescue Coordination Center received an alert from the airplane's emergency locator transmitter. About 7 minutes later, company personnel received a call from the pilot, who reported that the airplane had run "into the side of a mountain." Although a search was initiated almost immediately, due to poor weather conditions in the area, the wreckage was not located until almost 36 hours later in a crevasse on a glacier about 10,920 ft mean sea level. Due to the unique challenges posed by the steepness of terrain, the crevasse, avalanche hazard, and the condition of the airplane, neither the occupants nor the wreckage were recovered from the accident site. A weather model sounding for the area of the accident site estimated broken cloud bases at 700 ft above ground level (agl) with overcast clouds at 1,000 ft agl and cloud tops to 21,000 ft agl and higher clouds above. The freezing level was at 9,866 ft and supported light-to-moderate rime type icing in clouds and precipitation. The on-scene assessment indicated that the right wing impacted snow while the airplane was flying in a wings-level attitude; the right wing had separated from the remainder of the wreckage. Based upon available weather data and forecast models and the impact evidence, it is likely that the pilot entered an area of reduced visibility and was unable to see the terrain before the airplane's right wing impacted the snow. The company's organizational structure was such that one group of management personnel oversaw operations in both Anchorage and Talkeetna. Interviews with company management revealed that they were not always aware of the exact routing a pilot would take for a tour; the route was pilot's discretion based upon the weather at the time of the flight to provide the best tour experience. Regarding risk mitigation, the company did not utilize a formal risk assessment process, but rather relied on conversations between pilots and flight followers. This could lead to an oversight of actual risk associated with a particular flight route and weather conditions. About 8 months after the accident, an assessment flight conducted by the National Park Service determined that during the winter, the hazardous hanging glacier at the accident site calved, releasing an estimated 4,000 to 6,000 tons of ice and debris. There was no evidence of the airplane wreckage near the crash site, in the steep fall line, or on the glacier surface over 3,600 ft below. Although the known circumstances of the accident are consistent with a controlled flight into terrain event, the factual information available was limited because the wreckage was not recovered and no autopsy or toxicology of the pilot could be performed; therefore, whether other circumstances may have contributed to the accident could not be determined.
Probable cause:
Impact with terrain for reasons that could not be determined because the airplane was not recovered due to the inaccessible nature of the accident site.
Final Report:

Crash of a De Havilland DHC-2 Beaver in Willow Lake: 1 killed

Date & Time: Jul 18, 2018 at 1900 LT
Type of aircraft:
Operator:
Registration:
N9878R
Flight Phase:
Survivors:
Yes
Schedule:
Willow Lake - FBI Lake
MSN:
1135
YOM:
1958
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2685
Captain / Total hours on type:
345.00
Aircraft flight hours:
22605
Circumstances:
The pilot was conducting an on-demand air taxi flight in a float-equipped airplane from a seaplane base on a public lake to a remote lakeside home, with a passenger and her young son. The passenger brought cargo to transport as well, including an unexpected 800 lbs of mortar bags. Witnesses who labored to push the airplane out after loading reported that the airplane appeared very aft heavy and the pilot said he would offload "cement blocks" if he could not take off. A review of witness videos revealed that the pilot attempted one takeoff using only 3/4 of the available waterway, then step taxied around the lake and performed a step-taxi takeoff, again not using the full length of the lake. The airplane eventually lifted off, and barely climbed over trees on the south end of the lake, before descending and impacting terrain. A home surveillance video that captured the airplane seconds before the crash revealed that 3 seconds before ground impact, the estimated altitude of the airplane was 115 ft above ground level (agl) and the groundspeed was about 64 miles per hour (mph), which was low and much slower than normal climb speed (80 mph). As the airplane banked to the left to turn on course, it rolled through 90° likely experiencing an aerodynamic stall. Analysis of the engine rpm sound revealed that the engine was operating near maximum continuous power up until impact, and a postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. A calculation performed by investigators postaccident revealed the airplane's estimated gross weight at the time of the accident was 75 lbs over the approved maximum gross takeoff weight, and the airplane's estimated center of gravity was 1.76 inches aft of the rear limit. The pilot had been recently hired by the operator and he flew his first commercial flight in the same make and model, float-equipped airplane the week before the accident. He had accumulated 12.9 flight hours, and 13 sea landings/takeoffs in the accident model airplane since being hired as a part-time pilot. Although the airplane was able to takeoff, the aircraft's out-of-limit weight-and-balance condition increased its stall speed and degraded its climb performance, stability, and slow-flight characteristics. When the pilot turned the airplane left, the critical angle of attack was exceeded resulting in an aerodynamic stall at low altitude. If the pilot had performed a proper weight and balance calculation, he may have recognized the airplane was overweight and out of balance and should not have attempted the flight without making a load adjustment.
Probable cause:
The pilot's exceedance of the airplane's critical angle of attack during departure climb, which resulted in an aerodynamic stall. Contributing to the accident was the pilot's improper decision to load the airplane beyond its allowable gross weight and center of gravity limits, coupled with his lack of operational experience in the airplane make, model, and configuration.
Final Report:

Crash of a Curtiss C-46F-1-CU Commando in Manley Hot Springs

Date & Time: Jul 16, 2018 at 0925 LT
Type of aircraft:
Operator:
Registration:
N1822M
Flight Type:
Survivors:
Yes
Schedule:
Fairbanks – Kenai
MSN:
22521
YOM:
1945
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6500
Captain / Total hours on type:
3500.00
Copilot / Total flying hours:
300
Copilot / Total hours on type:
135
Aircraft flight hours:
37049
Circumstances:
The pilot reported that, following a precautionary shutdown of the No. 2 engine, he diverted to an alternate airport that was closer than the original destination. During the landing in tailwind conditions, the airplane touched down "a little fast." The pilot added that, as the brakes faded from continuous use, the airplane was unable to stop, and it overran the end of the runway, which resulted in substantial damage to the fuselage. The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause:
The pilot's failure to attain the proper touchdown speed and his decision to land with a tailwind without ensuring that there was adequate runway length for the touchdown.
Final Report: