Crash of an Antonov AN-2 in Fakhrabad: 1 killed

Date & Time: Aug 4, 2019 at 1040 LT
Type of aircraft:
Operator:
Registration:
RT-15-305
Survivors:
Yes
Schedule:
Fakhrabad - Fakhrabad
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The crew was completing a local skydiving mission in the region of Fakhrabad, about 30 km southwest of Dushanbe. After eight skydivers departed the cabin, the crew was returning to Fakhrabad Airfield when, on final approach, the airplane crashed in unknown circumstances. The copilot was seriously injured and the captain was killed.

Crash of a Beechcraft 350i Super King Air in Islamabad: 19 killed

Date & Time: Jul 30, 2019 at 1400 LT
Operator:
Registration:
766
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Chaklala - Chaklala
MSN:
FL-766
YOM:
2011
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
19
Circumstances:
The twin engine airplane departed Chaklala-Nur Khan AFB with five crew members on board for a local training flight. In flight, it went out of control and crashed onto several houses located in the suburb of Mora Kalu, about 10 km south of Chaklala-Nur Khan AFB, Islamabad, bursting into flames. The aircraft and several houses were destroyed. All five crew members as well as 14 people on the ground were killed.

Crash of an ATR42-500 in Gilgit

Date & Time: Jul 20, 2019 at 0815 LT
Type of aircraft:
Operator:
Registration:
AP-BHP
Survivors:
Yes
Schedule:
Islamabad – Gilgit
MSN:
665
YOM:
2007
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
48
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Islamabad, the crew was cleared to land on runway 25 at Gilgit Airport. After touchdown, the crew initiated the braking procedure but the aircraft was unable to stop within the remaining distance. It overran, lost its right main gear and came to rest 12 metres further in a grassy area. All 53 occupants evacuated safely and the aircraft was damaged beyond repair.

Crash of an Antonov AN-2 in Novoshchendrinskaya

Date & Time: Jul 16, 2019
Type of aircraft:
Operator:
Registration:
RA-3098K
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The pilot, sole on board, was engaged in an aerial photography mission. In flight, he encountered engine problems and was forced to attempt an emergency landing. The aircraft crashed onto a barn located in Novoshchedrinskaya, about 15 km north of Gudermes. The pilot and three people in the barn were injured.

Crash of a Boeing 737-85R in Mumbai

Date & Time: Jul 1, 2019 at 2351 LT
Type of aircraft:
Operator:
Registration:
VT-SYK
Survivors:
Yes
Schedule:
Jaipur - Mumbai
MSN:
30410/1228
YOM:
2002
Flight number:
SG6237
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
160
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5355
Captain / Total hours on type:
5113.00
Copilot / Total flying hours:
4826
Copilot / Total hours on type:
4625
Circumstances:
On 01.07.2019, B737-800 aircraft was involved in an accident (runway excursion) at Mumbai airport while landing in moderate to heavy rain. The aircraft was under the command of an ATPL holder (PF) with a CPL holder as First Officer (PM). There were 160 passengers and 7 crew members on board. There was no injury to any of the passengers or crew members. The aircraft suffered substantial damage. The subject flight was fifth of the day for the aircraft and second for the flight crew. The flight crew had earlier operated Mumbai-Jaipur sector and the incident flight was from Jaipur to Mumbai. There were no technical issues reported by the flight crew either during Mumbai Jaipur sector or on the return leg (Jaipur- Mumbai) till descent into Mumbai. The pilots had carried out briefing amongst themselves for the approach including the weather and Go Around actions, if required. The aircraft commenced descent into Mumbai in the late evening hours. As per the reported weather at the time of approach visibility was 2100 metres in rain making it dark. Reported winds were 090/12 Knots. Runway was wet and the trend provided was ³temporary reduction in visibility to 1500 metres with thunder/ showers of rain´. During descend at approximately 7000' Pressure Altitude, the crew observed an indication for IAS disagree, indicating a discrepancy of airspeed between the instrument sources for the flight crew. Although this indication was momentary, the 'Non-Normal Checklist' was carried out. The indication discrepancy did not recur for the remainder of the flight. The aircraft was radar vectored for an ILS approach for Runway 27 at Mumbai. The approach was stabilized by 3800' Pressure Altitude with landing gear down, flaps 30 and auto brake selected at 3. The autopilot was engaged throughout the descent phase and during approach, the second autopilot was also coupled for the ILS approach. At 100', the autopilot and the auto-throttle were disengaged by the PF. The flare manoeuvre consumed approximately 5807' of the runway length prior to the aircraft touchdown with 3881' of runway remaining. After touchdown, the speed brakes deployed automatically and maximum reverse thrust and wheel brakes were applied. The aircraft exited the paved surface at 65 Knots and came to rest at a distance of 615' beyond the end of the runway. Once the aircraft came to rest, the flight crew advised cabin crew to be at their stations. The pilots were unable to contact ATC through VHF communication. The PF contacted his airline personnel using mobile phone and informed that the aircraft had overrun the runway and requested for step ladders. The ATC activated fire services and the runway was closed for operation. The Cabin crew carried out check on the passengers in the cabin. The fire services reached the aircraft location and verbal communication was established with the flight crew once the cockpit window was opened. Two Fire Services personnel boarded the aircraft from the L1 door using a fire ladder. An assessment of the aircraft structure and occupants was made and the fire services personnel informed the cabin crew that deplaning was to be carried out using fire ladders. There were no injuries during evacuation or otherwise.
Probable cause:
The runway excursion occurred because of combination of:
- Disconnection of auto pilot at an altitude 118' RA with the nose up trim bias without adequate compensation.
- Disconnection of auto throttle at 118' RA at a higher thrust setting for that phase of flight.
- Late touchdown of the aircraft on the runway.
- Reduced visual cues due to heavy rain impacting depth perception and ascertaining of actual touchdown position.
- Tailwind conditions at the time of landing resulting In increasing the distance covered during the extended flare (float).
- Approach with lower flaps (30) than recommended (40).
Final Report:

Crash of an Antonov AN-24RV in Nizhneangarsk: 2 killed

Date & Time: Jun 27, 2019 at 1024 LT
Type of aircraft:
Operator:
Registration:
RA-47366
Survivors:
Yes
Schedule:
Ulan-Ude - Nizhneangarsk
MSN:
7 73 108 04
YOM:
1977
Flight number:
AGU200
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
43
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
15167
Captain / Total hours on type:
10667.00
Copilot / Total flying hours:
6012
Copilot / Total hours on type:
1325
Aircraft flight hours:
38014
Aircraft flight cycles:
18584
Circumstances:
On a flight from Ulan-Ude to Nizhneangarsk, while descending to an altitude of 3,050 metres about 30 km from the destination airport, the crew contacted ATC and reported the failure of the left engine. The approach was continued to runway 22. After touchdown, the crew started the braking procedure when the airplane deviated to the right then veered off runway. It rolled in a grassy area, cwent through the perimeter fence and eventually impacted the building of a sewage treatment plant located 380 metres to the right of the runway centerline. The captain and the flight engineer were killed and the copilot was seriously injured. 10 other occupants were injured. The aircraft was destroyed by a post crash fire.

Crash of a PZL-Mielec AN-2R near Rodina: 2 killed

Date & Time: Jun 20, 2019 at 1000 LT
Type of aircraft:
Operator:
Registration:
UP-A0116
Flight Phase:
Survivors:
Yes
Schedule:
Rodina - Rodina
MSN:
1G232-38
YOM:
1989
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The crew was engaged in a spraying mission on behalf of Rodina Agrofirm and completed five rotations in the morning. After refueling with chemicals, the airplane took off from an airfield located about 10 km from the village of Rodina. Shortly after takeoff, it collided with the wooden pillar of an electric power line, lost height and crashed in flames 100 metres further. The captain was killed while two other occupants were seriously injured. The following day, the copilot died from his injuries.

Crash of a PZL-Mielec AN-2R near Dabady

Date & Time: Jun 9, 2019 at 1624 LT
Type of aircraft:
Operator:
Registration:
RA-81519
Flight Phase:
Survivors:
Yes
Site:
Schedule:
Kyren - Kyren
MSN:
1G208-19
YOM:
1984
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6921
Captain / Total hours on type:
6912.00
Copilot / Total flying hours:
3561
Aircraft flight hours:
3720
Circumstances:
The crew departed Kyren Airport on a crop spraying mission to treat forests. About 40 minutes into the flight, while flying at a speed of 140 km/h, the crew encountered downdrafts and the airplane lost height. Due to mountainous terrain, the crew made a turn to the right but the airplane continued to descend. The captain attempted an emergency landing when, at a speed of 85 km/h, the aircraft struck trees and crashed in a wooded area located 16 km southeast of Dabady. Both pilots were injured and evacuated to Irkutsk a day later. The aircraft was damaged beyond repair.
Probable cause:
Most likely, the reason for the accident with the An-2 RA-81519 aircraft was the execution by the flight crew along the route in the mountainous terrain to the area of ​​the AHR at an altitude not ensuring its safety, which did not allow crossing the mountain pass, led to the need to perform an emergency landing and damage to the aircraft.
The contributing factors were most likely:
- Non-consideration by the crew of a significant increase of the outside air temperature during the day,
- The crew did not set the altimeter properly,
- Lack of instrument control over the flight altitude,
- Downdraft air currents on the leeward side of the mountain slope;
- Operating fatigue, leading to a weakening of attention and a decrease in level of situational awareness.
Final Report:

Crash of an Antonov AN-32 near Lipo: 13 killed

Date & Time: Jun 3, 2019 at 1300 LT
Type of aircraft:
Operator:
Registration:
K2752
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Jorhat - Mechuka
MSN:
10 09
YOM:
1987
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
13
Circumstances:
The airplane departed Jorhat Airport at 1227LT on a flight to Mechuka, Arunachal Pradesh. About half an hour later, while in cruising altitude, radio and radar contact were lost. SAR operations were quickly initiated and the wreckage was spotted eight days later, on June 11, by the crew of a Mil Mi-17 helicopter. The wreckage was found at an altitude of 12,000 feet in a wooded and steep area, about 16 km north of Lipo and 32 km east of Mechuka Airport. The aircraft was totally destroyed and all 13 occupants were killed.

Crash of a De Havilland Dash-8-Q402 in Yangon

Date & Time: May 8, 2019 at 1852 LT
Operator:
Registration:
S2-AGQ
Survivors:
Yes
Schedule:
Dhaka - Yangon
MSN:
4367
YOM:
2011
Flight number:
BG060
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
28
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9646
Captain / Total hours on type:
1474.00
Copilot / Total flying hours:
580
Copilot / Total hours on type:
405
Aircraft flight hours:
8115
Circumstances:
The route of the aircraft on that day was DAC-RGN-DAC. At (18:03) the Bombardier DHC-8-402 aircraft, registered (S2-AGQ) contacted Yangon control tower and at (18:16) had ILS established and reported to the Yangon control tower. Due to adverse weather, Yangon control tower asked them to execute a go-around and the aerodrome operations was closed for the aviation safety for 2 hours. When the weather condition got better, the aerodrome operations was opened. And then the DHC-8-402 aircraft, registered S2-AGQ made RNP approach because only localizer was available at that moment. While the Bombardier DHC-8-402 aircraft was and making approach to runway 21, it was a bit higher than on slope 3 degree and landed on runway 21, remaining on the ground for upwards of 7 seconds, but the aircraft ran parallel to the runway, and then it flew up in the air up to 44 ft above the ground and sank again and collided with runway 03 and slid forward out of the runway and came to a complete stop on the over-run of the runway 03. There was no fire. All gears were collapsed and fuselage was broken into three sections. All 33 occupants were evacuated, among them 20 were injured. The aircraft was destroyed.
Probable cause:
While the aircraft was unstabilized on approach, the pilot did not execute a go-around.
Final Report: