Crash of a Bombardier Global Express E-11A near Sharana AFB: 2 killed

Date & Time: Jan 27, 2020 at 1309 LT
Operator:
Registration:
11-9358
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Kandahar - Kandahar
MSN:
9358
YOM:
2009
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
4736
Captain / Total hours on type:
1053.00
Copilot / Total flying hours:
1343
Copilot / Total hours on type:
27
Circumstances:
On 27 January 2020, at approximately 1309 hours local time (L), an E-11A, tail number (T/N) 11-9358, was destroyed after touching down in a field in Ghanzi Province, Afghanistan (AFG) following a catastrophic left engine failure. The mishap crew (MC) were deployed and assigned to the 430th Expeditionary Electronic Combat Squadron (EECS), Kandahar Airfield (KAF), AFG. The MC consisted of mishap pilot 1 (MP1) and mishap pilot 2 (MP2). The mission was both a Mission Qualification Training – 3 (MQT-3) sortie for MP2 and a combat sortie for the MC, flown in support of Operation FREEDOM’S SENTINEL. MP1 and MP2 were fatally injured as a result of the accident, and the Mishap Aircraft (MA) was destroyed. At 1105L, the MA departed KAF. The mission proceeded uneventfully until the left engine catastrophically failed one hour and 45 minutes into the flight (1250:52L). Specifically, a fan blade broke free causing the left engine to shutdown. The MC improperly assessed that the operable right engine had failed and initiated shutdown of the right engine leading to a dual engine out emergency. Subsequently, the MC attempted to fly the MA back to KAF, approximately 230 nautical miles (NM) away. Unfortunately, the MC were unable to get either engine airstarted to provide any usable thrust. This resulted in the MA unable to glide the distance remaining to KAF. With few options remaining, the MC maneuvered the MA towards Forward Operating Base (FOB) Sharana, but did not have the altitude and airspeed to glide the remaining distance. The MC unsuccessfully attempted landing in a field approximately 21 NM short of FOB Sharana.
Probable cause:
The Accident Investigation Board (AIB) President found by a preponderance of the evidence that the cause of the mishap was the MC’s error in analyzing which engine had catastrophically failed (left engine). This error resulted in the MC’s decision to shutdown the operable right engine creating a dual engine out emergency. The AIB President also found by a preponderance of the evidence that the MC’s failure to airstart the right engine and their decision to recover the MA to KAF substantially contributed to the mishap.
Final Report:

Crash of a McDonnell Douglas MD-83 in Bandar-e Mahshahr

Date & Time: Jan 27, 2020 at 0736 LT
Type of aircraft:
Operator:
Registration:
EP-CPZ
Survivors:
Yes
Schedule:
Tehran - Bandar-e Mahshahr
MSN:
53464
YOM:
1994
Flight number:
RV6936
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
136
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18430
Captain / Total hours on type:
7840.00
Copilot / Total flying hours:
300
Copilot / Total hours on type:
124
Circumstances:
On Jan. 27, 2020, at 03:12 UTC Caspian Airlines (CPN) Flight 6936, an MD83, EP-CPZ took off from Mehrabad International Airport and climbed to FL320 as final cruising level. At about 03:45:37 UTC, the aircraft was flying according to the flight plan route on Airway B417 at an assigned FL320. Due to another traffic departing flight, an A320, IRA356 from Abadan Airport (OIAA) to destination Mashhad International Airport (OIMM), the ACC controller issued direct routing to the flight CPN 6936 position GODMO. At 03:49:34 UTC, CPN6936 requested descent clearance, so the flight was cleared to FL100. At 03:52:30 UTC, the pilot called Mahshahr AFISO and reported position 50 nm inbound GODMO and estimated time over GODMO at 03:59 UTC. At 03:52:51 UTC, Mahshahr AFISO reported necessary information as below: "RWY active is 31; wind is now 280/08kts, CAVOK, temperature +06, DP 04 and QNH 1023, expected VOR approach RWY 31 via GODMO 1E ARRIVAL" At 03:53: 33 UTC, the pilot requested RWY 13 and Mahshahr AFISO performed VOR/DME approach RWY 13, via GODMO 1F arrival. At 03:59:39 UTC, the pilot reported, “we are approaching position GODMO in contact with destination Mahshahr.” At 04:00:41UTC, the pilot reported his position “GODMO” to Mahshahr AFISO. At 04:02:46 UTC, the pilot reported leaving of IAF and received landing clearance for RWY13. Finally, at 04:06:11 UTC, the aircraft landed on RWY 13, passed two-thirds of RWY length and ran off the end of runway13 after landing at Mahshahr Airport at 04:06 UTC, Khuzestan province. The accident flight was being operated on an Instrument Flight Rules (IFR) flight plan in a Visual Meteorological Condition (VMC). The main door of the accident aircraft was opened in emergency condition, but the slide skid did not operate automatically. The cabin floor was just too close to the ground (grass surface) due to the impact of the nose and main landing gears strut which were broken after the runway overrun. The evacuation was performed from the main door, and all 136 passengers and 8 crew members disembarked.
Probable cause:
The Aircraft Accident Investigation Board determines that the probable causes of this accident were the pilots’ failures below, resulting in a runway overrun:
- Poor decision-making for acceptance of the risk of high-speed landing;
- Un-stabilized approach against the normal flight profile;
- Poor CRM in the cockpit; and
- Poor judgment and not accomplishing go-around while performing an unstabilized approach.

Contributing Factors:
- Loading of 5 tons of extra fuel, which increased the landing distance required.
- Decision to make a landing on RWY 13 with tailwind.
- Inability of the copilot (PM) to take control of the aircraft and proper action to execute goaround.
Final Report:

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

Date & Time: Jan 12, 2020
Type of aircraft:
Registration:
AP-AMB
Flight Phase:
Survivors:
No
Schedule:
Rahim Yar Khan - Rahim Yar Khan
MSN:
1415
YOM:
1960
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The airplane departed Rahim Yar Khan-Sheikh Zayed Airport and was spraying pesticide in the area to tackle another wave of locust attacks, which began in December 2019, on the request of the district administration. In unknown circumstances, the single engine airplane went out of control and crashed in a sandy area located in Sadiqabad, killing both crew members, a pilot and a flight engineer. They were completing a mission on behalf of the Department of Agriculture of Pakistan. Initial investigations suggest the plane crashed due to a technical fault.

Crash of a Boeing 737-8KV in Sabashahr: 176 killed

Date & Time: Jan 8, 2020 at 0618 LT
Type of aircraft:
Operator:
Registration:
UR-PSR
Flight Phase:
Survivors:
No
Schedule:
Tehran - Kiev
MSN:
38124
YOM:
2016
Flight number:
PS752
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
167
Pax fatalities:
Other fatalities:
Total fatalities:
176
Captain / Total flying hours:
11590
Captain / Total hours on type:
8428.00
Copilot / Total flying hours:
7633
Copilot / Total hours on type:
3642
Circumstances:
On Wednesday, January 08, 2020, at 00:53, the inbound flight No. 751 of Ukraine International, Boeing 737-800, UR-PSR, en route to Tehran Imam Khomeini INTL. Airport from Kyiv Boryspyl INTL. Airport was cleared for landing, and after four minutes landed on the IKA runway. After disembarking 58 passengers and refueling, the flight crew went on to check into the hotel located at IKA. From 01:16 to 01:38, the aircraft was refueled with 9510 kg (11800 liters) of fuel. Once the total weight of the cargo received from passengers (310 packages weighing 6794 kg) was determined, in order to comply with the maximum takeoff weight allowed for aircraft, 82 packages in 2094 kg in weight, were separated by Airport Service Company, that is, they were not loaded. Initially, 78 packages of the passenger's luggage were not loaded first, then due to the large volume of passengers' hand luggage, the flight attendants passed some of them on to the Airport Service Company personnel to be placed in the aircraft cargo. After that, 4 packages belonging to the passengers were removed from the aft cargo door, where the hand luggage was placed. At 04:35, the flight crew embarked on the aircraft. After checking the aircraft and cabin, boarding was announced at 04:45, and passengers started to board the plane. Based on the available documents, 167 passengers proceeded to the Airport Services Co. counter at the airport terminal, all of whom went on board. Only one of the passengers who received the boarding pass online the night before the flight, due to the delay in arriving in Tehran from another city did not go to the airport in person, and therefore had been removed from the list of passengers provided by the UIA. At 05:13, the pilot made his first radio contact with the IKA's control tower ground unit and requested the initial clearance for flying, which was issued by the controller subsequently. At 05:48, all the aircraft documents required to start the flight operations were filled out, and all the doors were then closed at 05:49. The flight was initially scheduled for 05:15, and based on the flight coordinator's report form, the reason given for its delay was the aircraft being overweight and the decision not to load the passengers' lugga for reducing the aircraft weight. At 05:51 the pilot notified his position at the airport parking, declared his readiness to exit the parking and start up the aircraft. The IKA tower asked him to wait for receiving the clearance since they wanted to make the coordination required with other relevant units. At 05:52, the IKA tower made the necessary coordination with the Mehrabad approach unit, who contacted Tehran ACC asking for clearance. Accordingly, the controller in ACC made coordination on Ukrainian flight clearance with the CMOCC. The clearance was issued by the CMOCC. At 05:54, the Mehrabad approach unit, received the FL260 clearance for the flight AUI752 from ACC, and forwarded it to IKA via the telecommunication system. Flight no. 752 was detached from the A1 Jet Bridge and at about 05:55 started to leave its parking position, NO 116 on the right, by a pushback truck. Following that, at 05:55 the ground controller cleared the AUI752 flight for startup and exiting the parking, which was read back by the pilot. At 06:12, the aircraft took off from the Runway 29 Right of IKA and was delivered to the Mehrabad approach unit. The pilot contacted the approach unit, and announced the IKA 1A radar procedure as SID procedure. Next, the Mehrabad approach identified and cleared the flight to climb to FL260. The controller instructed the pilot to turn to the right after 6,000 feet, and continue straight to PAROT. After it was read back by the pilot, the controller again instructed the pilot to continue to PAROT point once passing the 6000-foot altitude, which was read back by the pilot. From 06:17 onwards, upon the disappearance of the PS752 information from the radarscope, the controller called the captain repeatedly, but received no response. According to the data extracted from the surveillance systems and FDR, the aircraft climbed to an altitude of 8,100 feet; thereafter, the label including the call sign and altitude of aircraft disappeared from the radarscope, yet no radio contact indicating unusual conditions was received from the pilot. FDR recording terminated at 06:14:56. This time corresponds to the termination of Secondary Surveillance Radar (SSR) and ADS-B information. After the mentioned time, the aircraft was still being detected by the Primary Surveillance Radar (PSR), according to which the aircraft veered right and after approximately three minutes of flying, it disappeared from the PSR at 06:18 too. The aircraft was conducting the flight under the Instrument Flight Rules (IFR) and the accident occurred around half an hour before the sunset.
Probable cause:
Cause of the Accident:
- The air defense's launching two surface-to-air missiles at the flight PS752, UR-PSR aircraft the detonation of the first missile warhead in proximity of the aircraft caused damage to the aircraft systems and the intensification of damage led the aircraft to crash into the ground and explode instantly.

Other Contributing Factors:
- The mitigating measures and defense layers in risk management proved to be ineffective due to the occurrence of an unanticipated error in threat identifications, and ultimately failed to protect the flight safety against the threats caused by the alertness of defense forces.
Final Report:

Crash of a Harbin Yunsunji Y-12-II in Haputale: 4 killed

Date & Time: Jan 3, 2020
Type of aircraft:
Operator:
Registration:
SCL-857
Flight Phase:
Survivors:
No
Schedule:
Wirawila - Colombo
MSN:
0021
YOM:
1990
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
Crashed in unknown circumstances in Haputale while completing a survey flight from Wirawila to Colombo-Ratmalana Airport. The aircraft was destroyed by a post crash fire and all four crew members were killed.

Crash of a Fokker 100 in Almaty: 12 killed

Date & Time: Dec 27, 2019 at 0721 LT
Type of aircraft:
Operator:
Registration:
UP-F1007
Flight Phase:
Survivors:
Yes
Schedule:
Almaty – Nursultan
MSN:
11496
YOM:
1996
Flight number:
Z92100
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
93
Pax fatalities:
Other fatalities:
Total fatalities:
12
Captain / Total flying hours:
20141
Captain / Total hours on type:
3956.00
Copilot / Total flying hours:
11544
Copilot / Total hours on type:
4144
Aircraft flight hours:
44632
Aircraft flight cycles:
52771
Circumstances:
The Fokker 100 departed Almaty Airport on a regular schedule service (flight Z92100) to Astana-Nursultan Nazarbayev Airport, carrying 93 passengers and a crew of five. During the takeoff roll on runway 05R with flaps at zero, after a course of 36 seconds and at a speed of 148 knots, the crew started the rotation. Immediately after liftoff, the airplane rolled to the right at an angle of 5° then to the left at an angle of 19° without an increase of the indicated airspeed. After reaching the height of 20 feet in a pitch angle of 14°, the airplane started to descend then hit the runway surface with the base of the tail. It landed on its main landing gear and rolled for about 15 seconds with the nose gear still in the air. The airplane took off again at a speed of 138 knots then the crew retracted the landing gear. In a pitch angle of 19°, the airplane lost speed (130 knots), veered to the right, belly landed and slid for about 850 metres, went through a fence and eventually crashed into a house located near the perimeter fence, some 80 metres to the right of the extended center line. 47 occupants were injured, 39 escaped unhurt and 12 others were killed, among them the captain. The aircraft was destroyed. There was not fire.
Probable cause:
The accident was the consequence of an asymmetrical loss of wing lift properties at the stage of takeoff, which resulted in the aircraft crashing down immediately after leaving the runway and rolling to the right on the snowy ground, breaching the airport perimeter fence and colliding with a two-story private building located 9-10 m from the fence. As a result of collision, 11 passengers and one crew member died and 47 passengers received different injuries because of overloading, striking, destruction and crushing of the aircraft structure. The cause of the loss of wing lift properties was most likely the effect of ground icing.
Contributing factors:
- The crew, after analyzing the actual meteorological situation at Almaty airport, may not have drawn sufficient conclusions to better inspect the entire aircraft and especially (tactile method) the leading edge of the wing;
- The Flight Safety Management System (FMS) of Beck Air JSC contains mainly only general provisions and specific actions that were not adapted for implementation, which did not allow timely identification and elimination of existing risks affecting flight safety.
- Collision of the aircraft with a two-storey private structure, which affected the severity of the consequences.
Final Report:

Crash of a Cessna 208 Caravan I in Moo 2: 2 killed

Date & Time: Sep 24, 2019 at 0930 LT
Type of aircraft:
Operator:
Registration:
1917
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Surasi - Surasi
MSN:
208-0267
YOM:
1997
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The crew (one instructor aged 58 and one pilot under supervision aged 28) departed Surasi Air Base around 0900LT on a training flight. En route, in unknown circumstances, the single engine airplane crashed near Moo 2 (Sai Yok district). The aircraft disintegrated on impact and both occupants were killed.

Crash of a Viking Air DHC-6 Twin Otter 400 near Kampung Mamontoga: 4 killed

Date & Time: Sep 18, 2019 at 1100 LT
Operator:
Registration:
PK-CDC
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Timika - Ilaga
MSN:
950
YOM:
2016
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
The twin engine airplane departed Timika Airport at 1036LT on a cargo flight to Ilaga, carrying one passenger, a crew of four and a load of 1,7 ton of rice. At 1054LT, the crew gave his ETA at Ilaga Airport when the contact was lost about six minutes later. As the airplane failed to arrive at destination, SAR operations were initiated. The wreckage was found four days later in a mountainous terrain, at an altitude of 4,115 meters, about 10 km from Kampung Mamontoga. The aircraft was totally destroyed and all four occupants were killed.

Crash of a Beechcraft 350 Super King Air in Pansol: 9 killed

Date & Time: Sep 1, 2019 at 1510 LT
Operator:
Registration:
RP-C2296
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Dipolog - Manila
MSN:
FL-196
YOM:
1998
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
9
Circumstances:
The airplane encountered a loss of control in flight while approaching Manila and crashed into a private resort located in Barangay Pansol, Calamba, Laguna, Philippines. It lost radar contact with Manila Approach after being cleared to descent from 9,000 feet for 5,000 feet tracking-in radial 170, 25 DME to Ninoy Aquino International Airport (RPLL). The aircraft wreckage was found in a private resort with coordinates of 14°10’33.62” N and 121°11’34” E and heading approximately 228° with most its fuselage totally burned. All the nine (9) occupants were fatally injured and two (2) other persons on the ground sustained serious injuries. The aircraft took off from Dipolog Principal Airport (RPMG), Dipolog City, Zamboanga del Norte bound for Manila (RPLL) on a MEDEVAC flight. Instrument Metrological Condition (lMC) prevailed at the time of the accident.
Probable cause:
The aircraft experienced a loss of control in flight (LOC-I) after encountering adverse and hazardous atmospheric turbulent weather conditions which led to an inflight breakup.
The following contributing factors were identified:
- The presence of adverse and potentially hazardous atmospheric conditions on route of the flight.
- Failure of the flight crew to maintain situational awareness.
- Break-down of CRM to apply appropriate emergency procedures to recover the aircraft from the unusual situation they encountered.
Final Report:

Crash of a PZL-Mielec AN-2R near Lake Siljan-Kuel: 2 killed

Date & Time: Aug 30, 2019 at 0730 LT
Type of aircraft:
Operator:
Registration:
RA-33061
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Us-Khatyn – Suordakh
MSN:
1G218-48
YOM:
1986
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
12500
Captain / Total hours on type:
3806.00
Aircraft flight hours:
3848
Circumstances:
The single engine airplane departed Us-Khatyn on a flight to Suordakh, carrying five passengers, two pilots and a load consisting of 600 kilos of various goods. While cruising at an altitude of about 1,450 metres, the crew encountered moderate atmospheric turbulences and was unable to maintain the altitude. The aircraft lost height and crashed on the rocky slope of amountain located 15 km southeast from the Lake Siljan-Kuel, some 250 km from the destination. Two passengers were killed while five others occupants were injured. The aircraft was destroyed.
Probable cause:
The accident was caused by the fact that the PIC did not maintain a safe flight altitude in mountainous terrain, which led to the aircraft getting into strong downdrafts while flying over the leeward side of the ridge, uncontrolled descent and collision with the top of the mountain.
The contributing factors of AP, most likely, were:
- insufficient analysis of meteorological conditions and the possibility of the formation of strong ascending and descending air currents in the mountains;
- Failure of the PIC to take safety measures when flying in the mountains and to act in case of falling into downward air currents when crossing a mountain ridge;
- the use of motor gasoline with an octane rating of less than 95, which led to a decrease in engine power;
- performing a mission on the An-2 aircraft without the procedure for restoring skills and admission to flights on this type after a significant break in flights (about 15 years).
Final Report: