Crash of a Cessna 402C in Provincetown

Date & Time: Sep 9, 2021 at 1600 LT
Type of aircraft:
Operator:
Registration:
N88833
Survivors:
Yes
Schedule:
Boston – Provincetown
MSN:
402C-0265
YOM:
1979
Flight number:
9K2072
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
17617
Captain / Total hours on type:
10000.00
Aircraft flight hours:
36722
Circumstances:
The pilot was transporting six passengers on a scheduled revenue flight in instrument meteorological conditions. The pilot familiarized himself with the weather conditions before departure and surmised that he would be executing the instrument landing system (ILS) instrument approach for the landing runway at the destination airport. The operator prohibited approaches to runways less than 4,000 ft long if the tailwind component was 5 knots or more. The landing runway was 498 ft shorter than the operator-specified length. The pilot said he obtained the automated weather observing system (AWOS) data at least twice during the flight since he was required to obtain it before starting the instrument approach and then once again before he crossed the approach’s final-approach-fix (FAF). Though the pilot could not recall when he checked the AWOS, he said the conditions were within the airplane and company performance limits and he continued with the approach. A review of the wind data at the time he accepted the approach revealed the tailwind component was within limitations. As the airplane approached the FAF, wind speed increased, and the tailwind component ranged between 1 and 7 knots. Since the exact time the pilot checked the AWOS is unknown, it is possible that he obtained an observation when the tailwind component was within operator limits; however, between the time that the airplane crossed over the FAF and the time it landed, the tailwind component increased above 5 knots. The pilot said the approach was normal until he encountered a strong downdraft when the airplane was about 50 to 100 ft above the ground. He said that the approach became unstabilized and that he immediately executed a go-around; the airplane touched down briefly before becoming airborne again. The pilot said he was unable to establish a positive rate of climb and the airplane impacted trees off the end of the runway. The accident was captured on three airport surveillance cameras. A study of the video data revealed the airplane made a normal landing and touched down about 500 ft from the beginning of the runway. It was raining heavily at the time. The airplane rolled down the runway for about 21 seconds, and then took off again. The airplane entered a shallow climb, collided with trees, and caught on fire. All seven occupants were seriously injured and the airplane was destroyed.
Probable cause:
The pilot’s delayed decision to perform an aborted landing late in the landing roll with insufficient runway remaining. Contributing to the accident was the pilot’s failure to execute a go-around once the approach became unstabilized, per the operator’s procedures.
Final Report:

Crash of an Ilyushin II-112V in Kubinka: 3 killed

Date & Time: Aug 17, 2021 at 1118 LT
Type of aircraft:
Operator:
Registration:
RF-41400
Flight Type:
Survivors:
No
Schedule:
Kubinka - Kubinka
MSN:
01-01
YOM:
2008
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
On August 13, the aircraft (first prototype of this new model) departed the aviation plant at Voronezh Airport on a flight to Moscow-Zhukovsky, preparing for a demonstration flight at the 7th Military Technical Forum. On August 17, the crew departed Zhukovsky for a test flight to Kubinka Airport where the aircraft landed at 1109LT. Four minutes after takeoff at 1114LT, while flying at low altitude in a flat attitude, the right engine caught fire. 35 seconds later, while the crew elected to reach the airport, the aircraft rolled to the right, got inverted and crashed in a wooded area located 2,5 km short of runway 22. The aircraft was totally destroyed and all three crew members were killed. This first exemple was dedicated to the Russian Aerospace Forces (Vozdushno-kosmicheskiye sily) and was also registered 01 yellow.
Crew:
Nikolay Dmitrievich Kuimov, test pilot,
Dmitry Komarov, test pilot,
Nikolai Khludeyev, flight engineer.

Crash of a Cessna 425 Conquest I in Helena

Date & Time: Aug 11, 2021 at 0900 LT
Type of aircraft:
Operator:
Registration:
N783MB
Flight Type:
Survivors:
Yes
Schedule:
Faribault - Missoula
MSN:
425-0103
YOM:
1982
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6000
Captain / Total hours on type:
800.00
Aircraft flight hours:
9576
Circumstances:
The pilot stated that on the morning of the accident he filled both wing fuel tanks to full. After takeoff, he climbed to his planned cruise altitude of 24,000 ft mean sea level (msl). While en route to his destination, the pilot reported that the left engine experienced a flame-out. The pilot opted to divert from the originally planned destination and descended. When the airplane was about 7,900 ft msl, the pilot reported that the right engine experienced a loss of power and that he was not going to be able to make it to the airport. Shortly thereafter, the airplane collided with trees and the airplane came to rest with the right wing and empennage severed from the fuselage.
Probable cause:
A flameout of both engines due to fuel starvation for reasons that could not be determined due to the airplane’s damage. There was fuel in the wing tanks at the time of the impact. Postaccident examination of the wreckage did not reveal any anomalies. A partial amount of fuel was found in both of the filter bowls, but it is unknown if fuel was able to reach the engines. A complete examination of the fuel system could not be completed due to the damage incurred to the airplane at impact. Both engines flaming out within a short time of one another is likely indicative of a fuel supply or delivery issue; however, the nature of the problem could not be identified during postaccident examination.
Final Report:

Crash of a Piper PA-46-350P Malibu Mirage in Courchevel: 1 killed

Date & Time: Aug 6, 2021 at 1144 LT
Operator:
Registration:
F-HYGA
Flight Type:
Survivors:
Yes
Schedule:
Cannes - Courchevel
MSN:
46-36483
YOM:
2010
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
345
Captain / Total hours on type:
80.00
Circumstances:
The single engine airplane departed Cannes-Mandelieu Airport on a private flight to Courchevel with two passengers and one pilot on board. The goal of the flight was to maintain the validity of the pilot to access to the Courchevel Altiport. Following a right hand base leg, the pilot configured the airplane to land on runway 22. On final, the altimeter showed an altitude close to the runway threshold, and the aircraft was levelled off to the runway threshold. A few seconds before landing, the stall warning sounded, the engine power was increased and then reduced completely. The undercarriage impacted an embankment above the runway threshold and were torn off. The airplane lifted a bit then fell back onto the runway. It slid for about 100 metres before coming to rest. A fire erupted on the right side of the fuselage. The pilot and the front passenger exited the aircraft through the rear door and managed to extract the rear passenger, who was unconscious and died a few minutes later.
Probable cause:
The accident was the consequence of a premature descent during the approach. The pilot started the descent on the base leg, whereas mountain landing practices call for a descent on final approach after interception of the descent plan, combined with an erroneous assessment of the aircraft's position in relation to the final descent plan. Investigations revealed that the aircraft was flying at an altitude of 6,600 feet during the last turn, about 400 feet below the altitude indicated on the approach chart.
The following factors may have contributed to the accident:
- The period of training received by the pilot was probably insufficient;
- A lack of landing experience at Courchevel;
- A misunderstandings between the pilot and the passenger seated on the right about his role during the flight, himself being an airline pilot and instructor.
Final Report:

Crash of a Canadair CL-605 Challenger in Truckee: 6 killed

Date & Time: Jul 26, 2021 at 1318 LT
Type of aircraft:
Registration:
N605TR
Flight Type:
Survivors:
No
Schedule:
Coeur d'Alene - Truckee
MSN:
5715
YOM:
2008
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
5680
Captain / Total hours on type:
235.00
Copilot / Total flying hours:
14308
Copilot / Total hours on type:
4410
Aircraft flight hours:
5220
Circumstances:
The captain and first officer (FO) departed on a non-revenue flight operating under instrument flight rules with four passengers bound for Truckee, California. Most of the flight was uneventful. During the descent, air traffic control (ATC) told the flight crew to expect the area navigation (RNAV [GPS]) approach for runway 20. The captain (pilot flying [PF]) stated and the FO (pilot monitoring [PM]) calculated and confirmed that runway 20 was too short for the landing distance required by the airplane at its expected landing weight. Instead of making a request to ATC for the straight-in approach to runway 11 (the longer runway), the captain told the FO they could take the runway 20 approach and circle to land on runway 11, and the FO relayed this information to ATC. ATC approved, and the flight crew accepted the circle-to-land approach. Although the descent checklist required that the flight crew brief the new circle-to-land approach, and the flight crew’s acceptance of the new approach invalidated the previous straight-in approach brief, they failed to brief the new approach. ATC instructed the flight crew to hold, but the captain was slow in complying with this instruction, so the FO started the turn to enter the holding pattern and then informed ATC once they were established in the hold. About 20 seconds later, ATC cleared them for the approach. Before the FO confirmed the clearance, he asked the captain if he was ready for the approach, and the captain stated that he was. The FO subsequently commented that they had too much airspeed at the beginning of the approach and then suggested a 360° turn to the captain, but the captain never acknowledged the excessive airspeed and refused the 360° turn. After the FO visually identified the airport, he told the captain to make a 90° right turn to put the airplane on an approximate heading of 290°, which was parallel to runway 11 and consistent with the manufacturer’s operating manual procedures for the downwind leg of the circling approach. However, the FO instructed the captain to roll out of the turn prematurely, and the captain stopped the turn on a heading of about 233° magnetic, which placed the airplane at an angle 57° left of the downwind course parallel with runway 11. As a result of the early roll-out, the flight crew established a course that required an unnecessarily tight turning radius. When they started the turn to final, the airplane was still about 1.3 nautical miles (nm) from the maximum circling radius that was established for the airplane’s approach category. The FO also deployed flaps 45° after confirming with the captain (the manufacturer’s operating manual procedures for the downwind leg called for a flaps setting of 30°, but the manufacturer stated that a flight crew is not prohibited from a flaps 45° configuration if the approach remains within the limitations of the airplane’s flight manual). The airplane’s airspeed was 44 kts above the landing reference speed (Vref) of 118 kts that the flight crew had calculated earlier in the flight; the FO told the captain, “I’m gonna get your speed under control for you.” The FO likely reduced the throttles after he made this statement, as the engine fan speeds (N1) began to decrease from about 88% to about 28%, and the airplane began to slow from 162 kts. After the FO repeatedly attempted to point out the airport to the captain, the captain identified the runway; the captain's difficulty in finding the runway might have been the result of reduced visibility in the area due to smoke. The FO continuously reassured and instructed the captain throughout the circle-to-land portion of the approach. On the base leg to the runway and about 25 seconds before impact with the ground, the FO started to repeatedly ask for control of the airplane, but neither flight crewmember verbalized a positive transfer of control as required by the operator’s general operating manual (GOM); we could not determine who had control of the airplane following these requests. As the airplane crossed the runway extended centerline while maneuvering toward the runway, the FO noted that the airplane was too high. One of the pilots (recorded flight data did not indicate which) fully deployed the flight spoilers, likely to increase the airplane's sink rate. (The flight spoilers are deployed using a single control lever accessible to both pilots.) The airspeed at the time was 135 kts, 17 kts above the Vref based on the erroneous basic operating weight (BOW) programmed into the airplane’s flight management system (FMS). About 7 seconds later, the left bank became steeper, and the stall protection system (SPS) stick shaker and stick pusher engaged. The captain asked the FO, “What are you doing,” and the FO again asked the captain multiple times to “let [him] have the airplane.” The stick shaker and stick pusher then briefly disengaged before engaging again. The airplane then entered a rapid left roll, consistent with a left-wing stall, and impacted terrain. A postcrash fire consumed most of the wreckage. All six occupants, four passengers and two pilots, were killed.
Probable cause:
The first officer’s (FO’s) improper decision to attempt to salvage an unstabilized approach by executing a steep left turn to realign the airplane with the runway centerline, and the captain’s failure to intervene after recognizing the FO’s erroneous action, while both ignored stall protection system warnings, which resulted in a left-wing stall and an impact with terrain.
Contributing to the accident was
- The FO's improper deployment of the flight spoilers, which decreased the airplane's stall margin;
- The captain’s improper setup of the circling approach;
- The flight crew’s self-induced pressure to perform and
- Poor crew resource management which degraded their decision-making.
Final Report:

Crash of a Cessna 208 Caravan I off Norderney: 1 killed

Date & Time: Jul 26, 2021 at 1309 LT
Type of aircraft:
Operator:
Registration:
D-FLEC
Survivors:
No
Schedule:
Borkum - Norderney
MSN:
208-0388
YOM:
2005
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The single engine airplane departed Borkum Airport in the early afternoon on a local skydiving mission. At an altitude of 14,000 feet, the skydivers jumped out the cabin then the pilot reduced his altitude and returned to Norderney Airport. On approach, control was lost and the airplane crashed in the sea of Wadden, about 4 km southeast of the airfield. The aircraft was destroyed and the pilot was killed.

Crash of a De Havilland DHC-8-106 in Bur Ache

Date & Time: Jul 21, 2021
Operator:
Registration:
5Y-GRS
Survivors:
Yes
Schedule:
Nairobi – El Wak
MSN:
355
YOM:
1993
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
37
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The airplane departed Nairobi-Wilson Airport on a charter flight to El Wak, carrying 37 passengers and 4 crew members. While descending to El Wak Airport, the pilot continued to the east and elected to land on an airfield located 18 km east of El Wak, near Bur Ache, in Somalia. After landing, the airplane veered to the left and impacted a pile of earth and rocks, causing the left main gear to collapse. All 41 occupants evaacuated safely and the aircraft was damaged beyond repair.

Crash of a Beechcraft C90A King Air in Durango: 3 killed

Date & Time: Jul 18, 2021 at 0935 LT
Type of aircraft:
Operator:
Registration:
N333WW
Survivors:
Yes
Schedule:
San Luis Potosí – Durango
MSN:
LJ-1741
YOM:
2005
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
Upon landing at Durango-Guadalupe Victoria Airport following an uneventful flight from San Luis Potosí, the twin engine aircraft went out of control and crashed in a grassy area, coming to rest upside down and bursting into flames. A pilot and two passengers were killed while four other occupants were injured.

Crash of an Antonov AN-26B-100 in Palana: 28 killed

Date & Time: Jul 6, 2021 at 1505 LT
Type of aircraft:
Operator:
Registration:
RA-26085
Survivors:
No
Schedule:
Petropavlovsk-Kamchatsky – Palana
MSN:
123 10
YOM:
1982
Flight number:
PTK251
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
22
Pax fatalities:
Other fatalities:
Total fatalities:
28
Captain / Total flying hours:
3300
Copilot / Total flying hours:
1253
Copilot / Total hours on type:
1091
Circumstances:
The aircraft departed Petropavlovsk-Kamchatsky Airport at 1257LT on a schedule service (flight PTK251) to Palana, carrying 22 passengers and a crew of six, among them Olga Mokhiriova, chief of the municipality of Palana. At 1439LT, the crew contacted Palana ATC and was cleared to start the descent at 1450LT. While completing an NDB approach to runway 29, the crew encountered marginal weather conditions with fog and ceiling at 300 metres. Too low, the aircraft impacted terrain about 4 km northwest of the airport. The wreckage was found in the evening on the top of a rocky wall. The aircraft disintegrated on impact and debris fall down on the sea bank. All 28 occupants were killed.

Crash of a Lockheed C-130H Hercules in Jolo: 52 killed

Date & Time: Jul 4, 2021 at 1130 LT
Type of aircraft:
Operator:
Registration:
5125
Flight Type:
Survivors:
Yes
Schedule:
Cagayan de Oro - Jolo
MSN:
5125
YOM:
1988
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
88
Pax fatalities:
Other fatalities:
Total fatalities:
52
Circumstances:
The four engine aircraft departed Cagayan de Oro Airport to transfer troops to Jolo. On board were 88 passengers and a crew of 8, including three pilots. After landing on runway 09 at Jolo Airport, the aircraft was unable to stop within the remaining distance. It overran, collided with several house and came to rest in a wooded area, bursting into flames. At least 49 occupants were killed as well as three people on the ground. All others were injured.