Crash of a De Havilland DHC-2 Beaver in Soldotna: 6 killed

Date & Time: Jul 31, 2020 at 0827 LT
Type of aircraft:
Operator:
Registration:
N4982U
Flight Phase:
Survivors:
No
MSN:
904
YOM:
1956
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
19530
Captain / Total hours on type:
13480.00
Aircraft flight hours:
23595
Circumstances:
On July 31, 2020, about 0827 Alaska daylight time, a de Havilland DHC-2 (Beaver) airplane, N4982U, and a Piper PA-12 airplane, N2587M, sustained substantial damage when they were involved in an accident near Soldotna, Alaska. The pilot of the PA-12 and the pilot and the five passengers on the DHC-2 were fatally injured. The DHC-2 was operated as a Title 14 Code of Federal Regulations (CFR) Part 135 on-demand charter flight. The PA-12 was operated as a Title 14 CFR Part 91 personal flight. The float-equipped DHC-2, operated by High Adventure Charter, departed Longmere Lake, near Soldotna, about 0824 bound for a remote lake on the west side of Cook Inlet. The purpose of the flight was to transport the passengers to a remote fishing location. The PA-12, operated by a private individual, departed Soldotna Airport, Soldotna, Alaska, (PASX) about 0824 bound for Fairbanks, Alaska. Flight track data revealed that the DHC-2 was traveling northwest about 78 knots (kts) groundspeed and gradually climbing through about 1,175 ft mean sea level (msl) when it crossed the Sterling Highway. The PA-12 was traveling northeast about 1,175 ft msl and about 71 kts north of, and parallel to, the Sterling Highway. The airplanes collided about 2.5 miles northeast of the Soldotna airport at an altitude of about 1,175 ft msl. A witness located near the accident site observed the DHC-2 traveling in a westerly direction and the PA-12 traveling in a northerly direction. He stated that the PA-12 impacted the DHC-2 on the left side of the fuselage toward the back of the airplane. After the collision, he observed what he believed to be the DHC-2's left wing separate, and the airplane entered an uncontrolled, descending counterclockwise spiral before it disappeared from view. He did not observe the PA-12 following the collision.
Probable cause:
The failure of both pilots to see and avoid the other airplane.
Contributing to the accident were:
1) the PA-12 pilot’s decision to fly with a known severe vision deficiency that had resulted in denial of his most recent application for medical certification and
2) the Federal Aviation Administration’s absence of a requirement for airborne traffic advisory systems with aural alerting among operators who carry passengers for hire.
Final Report:

Crash of a De Havilland DHC-2 Beaver in Lake Coeur d'Alene: 6 killed

Date & Time: Jul 5, 2020 at 1422 LT
Type of aircraft:
Operator:
Registration:
N2106K
Flight Phase:
Survivors:
No
Schedule:
Coeur d'Alene - Coeur d'Alene
MSN:
1131
YOM:
1957
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
21173
Captain / Total hours on type:
217.00
Aircraft flight hours:
6171
Circumstances:
The float-equipped De Havilland DHC-2 was on a tour flight, and the Cessna 206 was on a personal flight. The airplanes collided in midair over a lake during day visual meteorological conditions. No radar or automatic dependent surveillance-broadcast data were available for either airplane. Witnesses reported that the airplanes were flying directly toward each other before they collided about 700 to 800 ft above the water. Other witnesses reported that the Cessna was at a lower altitude and had initiated a climb before the collision. Review of 2 seconds of video captured as part of a witness’ “live” photo showed that both airplanes appeared to be in level flight before the collision. No evidence of any preexisting mechanical malfunction was observed with either airplane. Recovered wreckage and impact signatures were consistent with the upper fuselage of the Cessna colliding with the floats and the lower fuselage of the De Havilland. The impact angle could not be determined due to the lack of available evidence, including unrecovered wreckage. The available evidence was consistent with both pilots’ failure to see and avoid the other airplane.
Probable cause:
The failure of the pilots of both airplanes to see and avoid the other airplane.
Final Report:

Crash of a Cessna 404 Titan in Lockhart River: 5 killed

Date & Time: Mar 11, 2020 at 0919 LT
Type of aircraft:
Registration:
VH-OZO
Survivors:
No
Schedule:
Cairns – Lockhart River
MSN:
404-0653
YOM:
1980
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
3220
Captain / Total hours on type:
399.00
Circumstances:
On 11 March 2020, a Cessna 404 aircraft, registered VH-OZO, was being operated by Air Connect Australia to conduct a passenger charter flight from Cairns to Lockhart River, Queensland. On board were the pilot and 4 passengers, and the flight was being conducted under the instrument flight rules (IFR). Consistent with the forecast, there were areas of cloud and rain that significantly reduced visibility at Lockhart River Airport. On descent, the pilot obtained the latest weather information from the airport’s automated weather information system (AWIS) and soon after commenced an area navigation (RNAV) global satellite system (GNSS) instrument approach to runway 30. The pilot conducted the first approach consistent with the recommended (3°) constant descent profile, and the aircraft kept descending through the minimum descent altitude (MDA) of 730 ft and passed the missed approach point (MAPt). At about 400 ft, the pilot commenced a missed approach. After conducting the missed approach, the pilot immediately commenced a second RNAV GNSS approach to runway 30. During this approach, the pilot commenced descent from 3,500 ft about 2.7 NM prior to the intermediate fix (or 12.7 NM prior to the MAPt). The descent was flown at about a normal 3° flight path, although about 1,000 ft below the recommended descent profile. While continuing on this descent profile, the aircraft descended below the MDA. It then kept descending until it collided with terrain 6.4 km (3.5 NM) short of the runway. The pilot and 4 passengers were fatally injured, and the aircraft was destroyed.
Probable cause:
The accident was the consequence of a controlled flight into terrain.
The following contributing factors were identified:
• While the pilot was operating in the vicinity of Lockhart River Airport, there were areas of cloud and rain that significantly reduced visibility and increased the risk of controlled flight into terrain.
In particular, the aircraft probably entered areas of significantly reduced visibility during the second approach.
• After an area navigation (RNAV) global satellite system (GNSS) approach to runway 30 and missed approach, the pilot immediately conducted another approach to the same runway that was on a similar gradient to the recommended descent profile but displaced about 1,000 ft below that profile. While continuing on this descent profile, the aircraft descended below a segment minimum safe altitude and the minimum descent altitude, then kept descending until the collision with terrain about 6 km before the runway threshold.
• Although the exact reasons for the aircraft being significantly below the recommended descent profile and the continued descent below the minimum descent altitude could not be determined, it was evident that the pilot did not effectively monitor the aircraft’s altitude and descent rate for an extended period.
• When passing the final approach fix (FAF), the aircraft’s lateral position was at about full-scale deflection on the course deviation indicator (CDI), and it then exceeded full-scale deflection for
an extended period. In accordance with the operator’s stabilized approach procedures, a missed approach should have been conducted if the aircraft exceeded half full-scale deflection at the FAF, however a missed approach was not conducted.
• The pilot was probably experiencing a very high workload during periods of the second approach. In addition to the normal high workload associated with a single pilot hand flying an approach in instrument meteorological conditions, the pilot’s workload was elevated due to conducting an immediate entry into the second approach, conducting the approach in a different manner to their normal method, the need to correct lateral tracking deviations throughout the approach, and higher than appropriate speeds in the final approach segment.
• The aircraft was not fitted with a terrain avoidance and warning system (TAWS). Such a system would have provided visual and aural alerts to the pilot of the approaching terrain for an extended period, reducing the risk of controlled flight into terrain.
• Although the aircraft was fitted with a GPS/navigational system suitable for an area navigation (RNAV) global satellite system (GNSS) approach and other non-precision approaches, it was not fitted with a system that provided vertical guidance information, which would have explicitly indicated that the aircraft was well below the recommended descent profile. Although the operator had specified a flight profile for a straight-in approaches and stabilized approach criteria in its operations manual, and encouraged the use of stabilized approaches, there were limitations with the design of these procedures. In addition, there were limitations with other risk controls for minimizing the risk of controlled flight into terrain (CFIT), including no procedures or guidance for the use of the terrain awareness function on the aircraft’s GNS 430W GPS/navigational units and limited monitoring of the conduct of line operations.

Other factors that increased risk:
• Although an applicable height of 1,000 ft for stabilized approach criteria in instrument meteorological conditions has been widely recommended by organizations such as the International Civil Aviation Organization for over 20 years, the Civil Aviation Safety Authority had not provided formal guidance information to Australian operators regarding the content of stabilized approach criteria. (Safety issue)
• The Australian requirements for installing a terrain avoidance and warning system (TAWS) were less than those of other comparable countries for some types of small aeroplanes conducting air transport operations, and the requirements were not consistent with International Civil Aviation Organization (ICAO) standards and recommended practices. More specifically, although there was a TAWS requirement in Australia for turbine-engine aeroplanes carrying 10 or more passengers under the instrument flight rules:
- There was no requirement for piston-engine aeroplanes to be fitted with a TAWS, even though this was an ICAO standard for such aeroplanes authorized to carry 10 or more passengers, and this standard had been adopted as a requirement in many comparable countries.
- There was no requirement for turbine-engine aeroplanes authorized to carry 6–9 passengers to be fitted with a TAWS, even though this had been an ICAO recommended practice since 2007, and this recommended practice had been adopted as a requirement in many comparable countries. (Safety Issue)

Other findings:
• The forecast weather at Lockhart River for the time of the aircraft’s arrival required the pilot to plan for 60 minutes holding or diversion to an alternate aerodrome. The aircraft had sufficient fuel for that purpose; and the aircraft had sufficient fuel to conduct the flight from Cairns to Lockhart River and return, with additional fuel for holding on both sectors if required.
• There was no evidence of any organizational or commercial pressure to conduct the flight to Lockhart River or to complete the flight once to commenced.
• Based on the available evidence, it is very unlikely that the pilot was incapacitated or impaired during the flight.
• There was no evidence of any aircraft system or mechanical anomalies that would have directly influenced the accident. However, as a consequence of extensive aircraft damage, it was not possible to be conclusive about the aircraft’s serviceability.
• The aircraft was fitted with Garmin GNS 430W GPS/navigational units that could be configured to provide visual (but not aural) terrain alerts. However, it could not be determined whether the
terrain awareness function was selected on during the accident flight.
Final Report:

Crash of a Learjet 55 Longhorn in Monmouth

Date & Time: Feb 25, 2020 at 2356 LT
Type of aircraft:
Registration:
N135LR
Survivors:
Yes
Schedule:
Richmond – Monmouth
MSN:
55-068
YOM:
1982
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18288
Captain / Total hours on type:
2909.00
Copilot / Total flying hours:
14759
Copilot / Total hours on type:
1978
Aircraft flight hours:
12792
Circumstances:
The pilot reported that he and the copilot were conducting an instrument approach to the runway in a business jet. He noted that the weather conditions included fog and mist. After touching down about 1,500 ft down the 7,300-ft-long runway, he engaged the thrust reversers and applied the brakes gradually because the runway was "slippery." As the airplane approached the end of the runway, he applied full braking, but the airplane departed the end of the runway and impacted a ditch, which resulted in the forward landing gear breaking and the airplane nosing down. The copilot corroborated the pilot's statement. The fuselage was substantially damaged. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause:
The flight crew's failure to stop the airplane on the available runway, which was wet and resulted in the airplane impacting a ditch.
Final Report:

Crash of a PZL-Mielec AN-2R in Magadan

Date & Time: Feb 20, 2020 at 1032 LT
Type of aircraft:
Operator:
Registration:
RA-40642
Flight Phase:
Survivors:
Yes
Schedule:
Magadan – Seymchan
MSN:
1G213-49
YOM:
1985
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8750
Captain / Total hours on type:
4543.00
Copilot / Total flying hours:
3865
Copilot / Total hours on type:
3865
Aircraft flight hours:
14822
Circumstances:
The single engine airplane, operated by T-Cement, was engaged in a charter flight from Magadan to Seymchan, carrying 12 pilots and 12 mining employees of the company and their 445 kilos of luggages and personal stuffs. After takeoff from the snowy runway 01, while climbing to a height of 10 metres, the aircraft entered a nose-up attitude while its speed dropped. At a height of about 30 metres, the angle of attack increased to 24° and the speed dropped to 65 km/h, causing the aircraft to stall and to crash in a snow covered field, some 240 metres past the runway end. All 14 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The aircraft stalled during initial climb because its total weight was above the MTOW and the CofG was well beyond the aft limit. The crew failed to prepare the flight according to procedure and, failed to proceed with a mass and balance calculation and the passengers and lugages were incorrectly placed in the cabin according to the CofG.
Final Report:

Crash of a Piper PA-31-310 Navajo in Bogotá: 4 killed

Date & Time: Feb 12, 2020 at 1544 LT
Type of aircraft:
Operator:
Registration:
HK-4686
Flight Phase:
Survivors:
No
Schedule:
Bogotá – Villagarzón
MSN:
31-344
YOM:
1968
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
1890
Captain / Total hours on type:
250.00
Copilot / Total flying hours:
646
Aircraft flight hours:
10251
Circumstances:
Shortly after takeoff from Bogotá-Guaymaral Airport, while in initial climb, the crew informed ATC about the failure of the right engine. He was cleared to return for an emergency and completed a circuit to land on ruwnay 11. On final, the airplane lost height and crashed in a wooded area located about 800 metres short of runway, bursting into flames. The aircraft was destroyed by a post crash fire and all four occupants were killed.
Probable cause:
The investigation determined that the accident was caused by the following probable cause(s):
- Loss of in-flight control as a result of slowing below Minimum Control Speed and drag, generated by the failure of the right engine (No. 2).
- Failure of engine No. 2, due to lack of lubrication, possibly caused by oil leakage through an 11.5 mm fracture, found in one of the sides of cylinder No. 2 at the height of the intake valves.
- Inappropriate application by the crew of the emergency procedure for landing with an inoperative engine, by not declaring the emergency, not feathering the propeller of the inoperative engine and configuring the aircraft early for landing (with landing gear and flaps) without having a safe runway, making it difficult to control the aircraft and placing it in a condition of loss of lift and control.

Contributing Factors:
- Failure of the operator to emphasize in the crew training program the techniques and procedures to be followed in the event of engine failure, among others, the declaration of emergency to ATC, the flagging of the propeller of the inoperative engine, the care in the application of power to the good engine so as not to increase yaw and not to configure the aircraft until landing has been assured.
- Lack of emergency calls by the crew, which denotes deficiencies in the Operator's Safety Management System, and which prevented the early warning of the aerodrome support services and deprived the crew of possible assistance from other aircraft or from the same operator.
Final Report:

Crash of a De Havilland DHC-3 Otter off Little Grand Rapids: 3 killed

Date & Time: Oct 26, 2019 at 0845 LT
Type of aircraft:
Operator:
Registration:
C-GBTU
Survivors:
No
Schedule:
Bissett - Little Grand Rapids
MSN:
209
YOM:
1957
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
9500
Captain / Total hours on type:
5800.00
Aircraft flight hours:
16474
Circumstances:
At approximately 0745 Central Daylight Time on 26 October 2019, the Blue Water Aviation float-equipped deHavillandDHC-3 Otteraircraft (registration C-GBTU, serial number 209) departed Bissett Water Aerodrome, Manitoba, with the pilot, 2 passengers, and approximately 800 pounds of freight on board. The destination was Little Grand Rapids, Manitoba, on the eastern shore of Family Lake. At approximately 0845, while on approach to Family Lake, the aircraft’s right wing separated from the fuselage. The aircraft then entered a nose-down attitudeand struck the water surface of the lake. The pilot and the 2 passengers were fatally injured. The aircraft was destroyed by impact forces. The emergency locator transmitter activated momentarily.
Probable cause:
Findings as to causes and contributing factors:
These are conditions, acts or safety deficiencies that were found to have caused or contributed to this occurrence.
1. A fatigue fracture originated in the bolt hole bore of the right-hand wing lift strut’s upper outboard lug plate, and eventually led to an overstress fracture of the right-hand wing lift strut’s upper outboard and inboard lug plates during the left turn prior to the final approach.
2. The failure of the outboard and inboard lug plates led to the separation of the righthand wing lift strut from the wing and, subsequently, the separation of the right wing from the aircraft.

Findings as to risk:
These are conditions, unsafe acts or safety deficiencies that were found not to be a factor in this occurrence but could have adverse consequences in future occurrences.
1. If operational flight plans data and load calculations are not available, there is a risk that, in the event of a missing aircraft or accident, aircraft information, including its number of occupants, route, cargo, and weight and balance information, will not be available for search and rescue operations or accident investigation.

Other findings:
These items could enhance safety, resolve an issue of controversy, or provide a data point for future safety studies.
1. The detailed visual inspection prescribed in the Viking Air Ltd. Supplementary Inspection and Corrosion Control Manual, and required by Airworthiness DirectiveCF2018-4, did not identify cracks that could form in the right-hand wing strut’s upper outboard lug plate.
Final Report:

Crash of a Cessna 402B in Coronel Oviedo

Date & Time: Sep 26, 2019 at 1830 LT
Type of aircraft:
Operator:
Registration:
ZP-BAE
Flight Phase:
Survivors:
Yes
Schedule:
Ciudad del Este – Asunción
MSN:
402B-0310
YOM:
1972
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
En route from Ciudad del Este to Asunción, the pilot encountered technical problems and reduced his altitude to attempt an emergency landing. The twin engine airplane belly landed in a prairie and slid for few dozen metres before coming to rest. All four occupants evacuated safely and the aircraft was damaged beyond repair.

Crash of a Cessna 560XL Citation Excel in Oroville

Date & Time: Aug 21, 2019 at 1132 LT
Operator:
Registration:
N91GY
Flight Phase:
Survivors:
Yes
Schedule:
Oroville - Portland
MSN:
560-5314
YOM:
2003
Flight number:
DPJ91
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6482
Captain / Total hours on type:
192.00
Copilot / Total flying hours:
4748
Copilot / Total hours on type:
858
Aircraft flight hours:
9876
Circumstances:
The crew was conducting an on-demand charter flight with eight passengers onboard. As the flight crew taxied the airplane to the departure runway, the copilot called air traffic control using his mobile phone to obtain the departure clearance and release. According to the pilot, while continuing to taxi, he stopped the airplane short of the runway where he performed a rudder bias check (the last item in the taxi checklist) and applied the parking brake without verbalizing the parking brake or rudder bias actions because the copilot was on the phone. After the pilot lined up on the runway and shortly before takeoff, the flight crew discussed and corrected a NO TAKEOFF annunciation for an unsafe trim setting. After the copilot confirmed takeoff power was set, he stated that the airplane was barely moving then said that something was not right, to which the pilot replied the airplane was rolling and to call the airspeeds. About 16 seconds later, the pilot indicated that the airplane was using more runway than he expected then made callouts for takeoff-decision speed and rotation speed. The pilot stated that he pulled the yoke back twice, but the airplane did not lift off. Shortly after, the pilot applied full thrust reversers and maximum braking, then the airplane exited the departure end of the runway, impacted a ditch, and came to rest 1,990 ft beyond the departure end of the runway. The airplane was destroyed by a postcrash fire, and the crew and passengers were not injured.
Probable cause:
The pilot’s failure to release the parking brake before attempting to initiate the takeoff, which produced an unexpected retarding force and airplane nose down pitching moment. Also causal was the flight crew’s delayed decision to abort the takeoff, which resulted in a runway excursion. Contributing to the accident was the lack of a NO TAKEOFF annunciation warning that the parking brake was engaged, and lack of a checklist item to ensure the parking brake was fully released immediately before takeoff.
Final Report:

Crash of a Cessna 208B Grand Caravan near Mayo: 2 killed

Date & Time: Aug 6, 2019 at 1113 LT
Type of aircraft:
Operator:
Registration:
C-FSKF
Flight Phase:
Survivors:
No
Site:
Schedule:
Rackla - Mayo
MSN:
208B-0673
YOM:
1998
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1694
Captain / Total hours on type:
212.00
Aircraft flight hours:
19060
Circumstances:
At 1101 Pacific Daylight Time on 06 August 2019, the Alkan Air Ltd. Cessna 208B Grand Caravan aircraft (registration C‐FSKF, serial number 208B0673) departed Rau Strip, Yukon, on a visual flight rules company flight itinerary to Mayo Airport, Yukon. The aircraft had 1 pilot, 1 passenger, and cargo on board. At 1113, the aircraft entered instrument meteorological conditions and struck rising terrain in a box canyon shortly after. The crash occurred approximately 25 nautical miles east‐northeast of Mayo Airport, at an elevation of 5500 feet above sea level. The Canadian Mission Control Centre did not receive a signal from the aircraft’s 406 MHz emergency locator transmitter. Eyewitnesses from a nearby exploration camp arrived at the site after approximately 1 hour. Royal Canadian Mounted Police and emergency medical services arrived on site approximately 90 minutes after the accident. The pilot and passenger received fatal injuries. The aircraft was destroyed; there was a brief post‐impact fire.
Probable cause:
Findings as to causes and contributing factors:
These are conditions, acts or safety deficiencies that were found to have caused or contributed to this occurrence.
1. The pilot’s decision making was influenced by several biases and, as a result, the flight departed and subsequently continued into poor weather conditions in mountainous terrain.
2. The high speed at low altitude and low forward visibility reduced the opportunities for the pilot to take alternative action to avoid terrain.
3. Within the box canyon, the canyon floor elevation increased abruptly within less than 1 NM and the low visibility prevented the pilot from detecting this and taking sufficient actions to prevent collision with terrain.
4. When the pilot turned into the box canyon, the terrain awareness and warning system aural alerts were ineffective in warning the pilot about the rising terrain either because he had already heard multiple similar alerts in the preceding minutes, or because he had silenced the alerts.

Findings as to risk:
These are conditions, unsafe acts, or safety deficiencies that were found not to be a factor in this occurrence but could have adverse consequences in future occurrences.
1. If administrative safety defences are not used as intended, it increases the risk that the hazards associated with the flight will not be identified and mitigated.

Other findings:
These items could enhance safety, resolve an issue of controversy, or provide a data point for future safety studies.
1. The pilot held a valid instrument rating and the aircraft was equipped to fly in instrument meteorological conditions. However, there were no scenarios in the pilot’s flying history on the Cessna 208B Grand Caravan or in his training where a transition from visual flight rules to a flight under instrument flight rules in an emergency was performed.
Final Report: