Crash of a Boeing 737-529 in Garowe

Date & Time: Dec 2, 2020 at 0925 LT
Type of aircraft:
Operator:
Registration:
EY-560
Survivors:
Yes
Schedule:
Djibouti – Hargeisa – Garowe – Mogadishu
MSN:
26538/2298
YOM:
1992
Flight number:
IV206
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
31
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6050
Captain / Total hours on type:
5170.00
Copilot / Total flying hours:
900
Circumstances:
The airplane departed Djibouti on a regular schedule service to Mogadishu with intermediate stops in Hargeisa and Garowe. There were 31 passengers and 8 crew members on board. On short final approach to Garowe Airport Runway 06, the airplane lost height and impacted the ground just prior to the runway threshold (concrete), causing the right main gear to collapse. The airplane slid on the runway until it turned to the right and came to rest on the runway with the right engine cowling contacting the runway surface. All 39 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The factor contributing to the accident is weather condition. Windshear is considered as the major cause of the accident. The root cause of the accident is a loss of control of the aircraft caused by windshear.
Final Report:

Crash of a Cessna 551 Citation II/SP in Lufkin

Date & Time: Dec 2, 2020 at 0842 LT
Type of aircraft:
Registration:
N48DK
Survivors:
Yes
Schedule:
Austin - Lufkin
MSN:
551-0095
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
17772
Captain / Total hours on type:
2000.00
Aircraft flight hours:
9395
Circumstances:
After a 30-minute uneventful instrument flight rules (IFR) flight, the business jet landed in the rain on the 4,311ft-long runway. The pilot reported, and runway skid marks corroborated, that the airplane touched down about 1,000 ft from the approach end of the runway. The pilot reported braking action was initially normal and the anti-skid system cycled twice before it stopped working and he was unable to slow the airplane using the emergency brakes. The airplane continued off the departure end of the runway where it traveled through wet grass and a fence before coming to rest with the landing gear collapsed. A video of the airplane during the landing roll indicated there was a significant amount of water on the runway. No mechanical anomalies were found with the brake/antiskid systems during the postaccident examination of the airplane. Marks on the runway indicated functionality of the antiskid system. Stopping performance calculations estimated the distance required to stop the airplane on the runway was about 4,127 ft. The runway length remaining after the airplane touched down was about 3,311 ft. The pilot was aware of the runway length and weather conditions prior to departure and reported that he should have not accepted the trip.
Probable cause:
The pilot’s decision to land on a runway that did not provide enough length to stop the airplane given the wet surface conditions, resulting in a runway excursion.
Final Report:

Crash of an Antonov AN-124-100 in Novosibirsk

Date & Time: Nov 13, 2020 at 1210 LT
Type of aircraft:
Operator:
Registration:
RA-82042
Flight Type:
Survivors:
Yes
Schedule:
Seoul - Novosibirsk - Vienna
MSN:
9773054055093
YOM:
1991
Flight number:
VI4066
Country:
Region:
Crew on board:
14
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The four engine airplane departed Seoul-Incheon Airport on a cargo flight to Vienna, with an intermediate stop in Novosibirsk, carrying 14 crew members and a load consisting of 84 tons of automobile parts. Shortly after takeoff from runway 25 at Novosibirsk-Tolmachevo Airport, while in initial climb, a catastrophic failure occurred on the engine n°2. Several debris punctured the fuselage, damaging slats on both left and right side. As a result, radio communications were cut, the power supply failed and the thrust control on all three remaining engines dropped. The crew entered a circuit for an immediate return despite the aircraft was in an overweight condition for an emergency landing. After touchdown on runway 25 that offered an LDA of 3,597 metres, the crew started the braking procedure but the aircraft was unable to stop within the remaining distance. It overran, lost its both nose gears and slid in a snow covered field before coming to rest 300 metres further. All 14 occupants evacuated safely and the aircraft seems to be damaged beyond repair.
Probable cause:
Failure of the high pressure compressor disk on the engine n°2 during the takeoff procedure.

Crash of a Rockwell Sabreliner 65 near El Chico: 1 killed

Date & Time: Nov 9, 2020
Type of aircraft:
Operator:
Registration:
XA-VD?
Flight Type:
Survivors:
No
MSN:
465-30
YOM:
1980
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The crew was apparently trying to land on an illegal airstrip when the aircraft struck trees and crashed, coming to rest upside down. A load of narcotics was found on board as well as a dead body. The aircraft registration needs to be confirmed - XA-VD?.

Crash of a Embraer EMB-500 Phenom 100 in São Pedro

Date & Time: Oct 30, 2020 at 1750 LT
Type of aircraft:
Operator:
Registration:
PR-LMP
Survivors:
Yes
Schedule:
São Paulo – São Pedro
MSN:
500-00094
YOM:
2009
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7300
Captain / Total hours on type:
2350.00
Copilot / Total flying hours:
676
Copilot / Total hours on type:
409
Circumstances:
After touchdown on runway 29 at São Pedro Airport, the crew initiated the breaking procedure but the airplane failed to stop within the remaining distance. It overran, collided with various obstacles, went down an embankment of 10 metres and eventually came to rest 130 metres further, bursting into flames. All four occupants evacuated safely and the airplane was destroyed by a post crash fire.
Probable cause:
Studies and research showed that the low deceleration of the aircraft and the limitation of the hydraulic pressure provided by the brake system were compatible with a slippery runway scenario. Thus, one inferred that the runway was contaminated, a condition that would reduce its coefficient of friction and impair the aircraft's braking performance, making it impossible to stop within the runway limits. On account of the mirroring condition of the runway in SSDK, it is possible that the crew had some difficulty perceiving, analyzing, choosing alternatives, and acting appropriately, given a possible inadequate judgment of the aircraft's landing performance on contaminated runways.
Final Report:

Crash of an Antonov AN-32A in Iquitos

Date & Time: Oct 14, 2020 at 1321 LT
Type of aircraft:
Operator:
Registration:
OB-2120-P
Flight Type:
Survivors:
Yes
Schedule:
Lima - iquitos
MSN:
18 05
YOM:
1989
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5681
Captain / Total hours on type:
4530.00
Copilot / Total flying hours:
1366
Copilot / Total hours on type:
470
Aircraft flight hours:
9830
Aircraft flight cycles:
10893
Circumstances:
After touchdown on runway 06 at Iquitos-Coronel Francisco Secada Vignetta Airport, the aircraft went out of control and veered off runway to the left. It contacted trees and bushes, lost its right wing and came to rest 100 metres to the left of the runway, broken in two. A fire erupted but was quickly extinguished. All four crew members were slightly injured and the aircraft was destroyed.
Probable cause:
Runway Excursion due to loss of directional control of the aircraft after landing by disengaging the propeller stops for aerodynamic braking at a higher than established speed, which generated an uncontrollable leftward turning moment of the trajectory, due to asymmetric thrust of the propellers.
The following contributing factors were identified:
- Performing a landing on an Unstabilised Approach, not executing the established Go-Around procedure.
- Performing a failed landing due to asymmetric thrust of the propellers, not applying the procedure established in the Operator's QRH to shut down the failed engine.
- Probable failure of the KTA Fuel Regulator of the Automatic Engine Rotation Frequency and Power Regulation System, which blocked the reduction of the power of the N°2 engine to established operating regimes for the approach and landing.
Final Report:

Crash of a Douglas DC-4A in Yakataga

Date & Time: Oct 10, 2020 at 1544 LT
Type of aircraft:
Operator:
Registration:
N96358
Flight Type:
Survivors:
Yes
Schedule:
Kenai - Yakataga
MSN:
27284
YOM:
1944
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
17925
Captain / Total hours on type:
2163.00
Copilot / Total flying hours:
8832
Copilot / Total hours on type:
1964
Aircraft flight hours:
33718
Circumstances:
The commercial pilot reported that the flight had been delayed for “nearly 2 weeks due to rain” but that the company had contacted their customer, who was a local resident of the area, and he had reported that the landing grass airstrip was “currently dry” and that he was unaware of any NOTAMs reporting that the runway was closed. The pilot reported that, while landing the airplane on the airstrip, the braking action was “zero” along the entire length of the runway. Subsequently, while about 5 knots, the airplane overran the end of the runway, and the nose landing gear collapsed. The airplane sustained substantial damage to the forward fuselage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The pilot reported that, during a formal flight brief from a Federal Aviation administration (FAA) Flight Service Station (FSS), he and the copilot asked if there was “anything special going on down there” that they should be aware of” but that FSS personnel did not mention any NOTAMs stating that the runway was closed to heavy airplanes nor was it mentioned when they activated the flight plan. However, according to FAA FSS recordings, during the first conversation, the pilot did not ask for any NOTAMs for the airport. During the second conversation, the FSS asked the pilots if they needed any weather information or NOTAMs, and the pilots responded, “no,” and that they “were all good.” A NOTAM had been issued, which stated, in part, that the landing runway was closed to aircraft that weighed more than 5,000 lbs. The airport chart supplement remarks stated, in part, that “the runway was extremely soft when wet…Use of heavy aircraft over 4,000 lbs gross not recommended during fall, winter, & spring due to” soft field conditions and rutting.” The pilot reported that the airplane’s weight was about 62,568 lbs at the time of the accident.
Probable cause:
The pilots’ decision to land on a wet, soft runway, which resulted in the loss of braking action upon landing and a subsequent runway overrun and nose landing gear collapse.
Final Report:

Crash of a Socata TBM-850 in Corfu: 2 killed

Date & Time: Oct 2, 2020 at 1144 LT
Type of aircraft:
Operator:
Registration:
N965DM
Flight Type:
Survivors:
No
Schedule:
Manchester - Buffalo
MSN:
527
YOM:
2009
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
960
Captain / Total hours on type:
239.00
Aircraft flight hours:
1181
Circumstances:
The airplane was in cruise flight at FL280 when the instrument-rated pilot failed to contact air traffic control (ATC) following a frequency change assignment. After about 25 minutes, and when 30 miles east of the destination airport, the pilot contacted ATC on a frequency other than the one that was assigned. He requested the instrument landing system (ILS) approach at his intended destination, and the controller instructed the pilot to descend to 8,000 ft and to expect vectors for the ILS approach at the destination airport. The controller asked the pilot if everything was “okay,” to which the pilot replied, “yes sir, everything is fine.” The controller then observed the airplane initiate a descent. About 2 minutes later, the controller asked the pilot where he was headed, and the pilot provided a garbled response. The controller instructed the pilot to stop his descent at 10,000 ft, followed by an instruction to stop the descent at any altitude. The pilot did not respond, and additional attempts to contact the pilot were unsuccessful. The airplane impacted terrain in a heavily wooded area 17 miles from the destination airport. Rhe aircraft disintegrated on impact and both occupants were fatally injured.
Probable cause:
The pilot’s failure to maintain control of the airplane for undetermined reasons during the descent to the destination airport.
Final Report:

Crash of an Antonov AN-26Sh at Chuhuiv AFB: 26 killed

Date & Time: Sep 25, 2020 at 2050 LT
Type of aircraft:
Operator:
Registration:
76 yellow
Flight Type:
Survivors:
Yes
Schedule:
Chuhuiv AFB - Chuhuiv AFB
MSN:
56 08
YOM:
1977
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
20
Pax fatalities:
Other fatalities:
Total fatalities:
26
Circumstances:
The aircraft was engaged in a local training flight at Chuhuiv AFB, carrying 7 crew members and 20 cadets. On approach to runway 16, the crew apparently encountered engine problems when the aircraft lost height and crashed 2 km short of runway threshold near motorway E40, bursting into flames. Two passengers were seriously injured while 25 other occupants were killed. Few hours later, one of the survivors died from his injuries.

Crash of a BAe 125-800A near Alta Verapaz: 4 killed

Date & Time: Sep 23, 2020
Type of aircraft:
Operator:
Registration:
XB-PYZ
Flight Type:
Survivors:
No
MSN:
258018
YOM:
1984
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
Engaged in an illegal flight, the crew was attempting to land on a remote airstrip located in the region of Alta Verapaz. In unclear circumstances, the aircraft struck trees and crashed in a wooded area, bursting into flames. The aircraft was destroyed by a post crash fire and all four occupants were killed.