Crash of a Beechcraft 350i Super King Air on Mt Artos: 7 killed

Date & Time: Jul 15, 2020 at 2245 LT
Operator:
Registration:
EM-809
Flight Phase:
Survivors:
No
Site:
Schedule:
Van - Van
MSN:
FL-896
YOM:
2015
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The twin engine aircraft departed Van-Ferit Melen Airport at 1834LT on a survey/reconnaissance mission over the province of Hakkari and Van, carrying five passengers and two pilots. At 2232LT, the crew informed ATC about his position vertical to Başkale on approach to Van-Ferit Melen Airport. Thirteen minutes later, the aircraft struck the slope of Mt Artos located 30 km southwest of runway 03 threshold. The aircraft was destroyed upon impact and all seven occupants were killed.

Crash of a PZL-Mielec AN-2R in Kistenovo: 2 killed

Date & Time: Jul 13, 2020 at 0337 LT
Type of aircraft:
Operator:
Registration:
RA-40851
Flight Phase:
Survivors:
No
Schedule:
Bol’shoye Boldino - Bol’shoye Boldino
MSN:
1G174-47
YOM:
1977
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
5036
Copilot / Total flying hours:
2000
Copilot / Total hours on type:
1400
Circumstances:
The crew was completing a spraying mission near the village of Kistenovo, about six km north of Bol'shoye Boldino Airfield. While flying at a low height against sunrise, the crew failed to see and avoid power cables. The single engine airplane collided with cables and a concrete post before crashing in a cornfield, bursting into flames. The copilot was killed and the captain was seriously injured. He died two days later from his injuries. The aircraft was destroyed by a post crash fire.
Probable cause:
The cause of the accident with the An-2 RA-40851 aircraft was the collision of the aircraft with a reinforced concrete support and power transmission lines in a controlled flight while performing the aerial application at an extremely low altitude.
The contributing factors most likely were:
- Field processing when the sun is less than 15° above the horizon and the sun's heading angle is less than 30°,
- Insufficient prudence of the PIC when performing a VFR flight for aerial application,
- Failure of the pilot to take into account the presence of artificial obstacles in the flight area,
- Lack of marking of power lines.
Final Report:

Crash of a Lockheed C-130H3 Hercules at Al Taji AFB

Date & Time: Jun 8, 2020 at 2205 LT
Type of aircraft:
Operator:
Registration:
94-6706
Flight Type:
Survivors:
Yes
Schedule:
Ali Al Salem AFB - Al Taji AAF
MSN:
5398
YOM:
1995
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total hours on type:
1700.00
Copilot / Total hours on type:
506
Circumstances:
On 8 June 2020, at approximately 2205 hours local time (L), the mishap aircraft (MA), a C-130H (tail number (T/N) 94-6706), was involved in a mishap during a routine mobility airlift mission from Ali Al Salem Air Base, Kuwait, into Al Taji (Camp Taji), Iraq, when it failed to come to a stop during landing, overran the runway, and impacted a concrete barrier. All 26 mishap crew (MC) members and passengers survived the mishap, with relatively minor injuries to two of the individuals. The MA was damaged beyond repair, and was valued at $35,900,000. The MA was from the 165th Airlift Wing (165 AW), Georgia Air National Guard (ANG), was manned with Wyoming ANG crew members deployed from the 153d Airlift Wing (153 AW), in Cheyenne, Wyoming, and assigned to the 386th Air Expeditionary Wing (386 AEW) at Ali Al Salem Air Base, Kuwait. The mishap occurred at the end of the first planned leg of the MC’s mission on 8 June 2020. The MC departed Ali Al Salem Air Base, Kuwait, at approximately 2053L, with an uneventful start, taxi, takeoff, and cruise to Camp Taji. During descent into Camp Taji, the MC prepared the MA for a nighttime landing, using night vision devices. During this time, the MC turned the MA earlier than their planned turn point, did not descend to lower altitudes in accordance with their planned descent, and allowed the airspeed to exceed recommended maximum speeds for the configuration the plane was in. During the landing, the MA continued to be above the planned glideslope and maintained excessive airspeed, with a nose-down attitude until touchdown. The MA proceeded to “porpoise” or oscillate down the runway from the point of touchdown until the MA was slowed sufficiently by use of reverse thrust from the engines to allow the MA to settle onto the wheels, which in turn allowed for the brakes to engage. The MA, despite slowing somewhat, had less than 1,000 feet of runway remaining by that point, and thus overran the runway and did not come to a complete stop until it impacted a 12-foot-high concrete barrier, approximately 600 feet past the runway.
Probable cause:
The Accident Investigation Board (AIB) President found by a preponderance of the evidence that the causes of the mishap were the MA’s excess airspeed above recommended landing velocity, which caused the MA to maintain lift (flight) and did not provide sufficient weight on wheels (WOW) to allow braking action to occur. Additionally, the AIB President found, by a preponderance of the evidence, the MC’s failure to adequately assess risk, failure to follow proper procedures, and their poor communication were all substantially contributing factors to the mishap.
Final Report:

Crash of an Airbus A320-214 in Karachi: 98 killed

Date & Time: May 22, 2020 at 1439 LT
Type of aircraft:
Operator:
Registration:
AP-BLD
Survivors:
Yes
Site:
Schedule:
Lahore - Karachi
MSN:
2274
YOM:
2004
Flight number:
PK8303
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
91
Pax fatalities:
Other fatalities:
Total fatalities:
98
Aircraft flight hours:
47124
Aircraft flight cycles:
25866
Circumstances:
On 22 May 2020 at 13:05 hrs PST, the Pakistan International Airlines aircraft Airbus A320-214, registration number AP-BLD, took off from Lahore (Allama Iqbal International Airport – AIIAP) Pakistan to perform a regular commercial passenger flight (PK8303) to Karachi (Jinnah International Airport – JIAP) Pakistan, with 8 crew members (01 Captain, 01 First Officer, and 06 flight attendants) and 91 passengers on board. At 14:35 hrs the aircraft performed an ILS approach for runway 25L and touched down without landing gears, resting on the engines. Both engines scrubbed the runway at high speed. Flight crew initiated a go-around and informed “Karachi Approach” that they intend to make a second approach. About four minutes later, during downwind leg, at an altitude of around 2000 ft, flight crew declared an emergency and stated that both engines had failed. The aircraft started losing altitude. It crashed in a populated area, short of runway 25L by about 1340 meters. An immediate subsequent post impact fire initiated. Out of 99 souls on-board, 97 were fatally injured and 02 passengers survived. On ground 04 persons were injured however 01 out of these reportedly expired later at a hospital.

Below, the preliminary report published by the Pakistan AAIB.
Final Report:

Crash of a Quest Kodiak 100 off Sentani: 1 killed

Date & Time: May 12, 2020 at 0628 LT
Type of aircraft:
Operator:
Registration:
PK-MEC
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Jayapura - Mamit
MSN:
100-0026
YOM:
2009
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1357
Captain / Total hours on type:
185.00
Aircraft flight hours:
4707
Aircraft flight cycles:
9379
Circumstances:
On 12 May 2020, a Quest Kodiak 100 aircraft, registration PK-MEC, was being operated by Mission Aviation Fellowship (MAF) as a cargo flight from Sentani Airport (WAJJ), Jayapura, Papua with intended destination of Mamit Airstrip (WAVS) Tolikara, Papua. The pilot was the only person on board for this flight and the aircraft carried 694 kgs of cargo goods. At 0622 LT (2122 UTC), the pilot of PK-MEC aircraft requested clearance to the Sentani Tower controller to start aircraft engine and flying to Mamit at radial 241° with intended cruising altitude 10,000 feet. The Sentani Tower controller approved the request. At 0627 LT, on daylight condition, the aircraft took off from runway 12 of Sentani Airport, thereafter, the Sentani Tower controller advised to the pilot of PK-MEC to contact Jayapura Radar controller. At 0628LT, the pilot of PK-MEC declared “MAYDAY” on Jayapura Radar radio frequency. The Jayapura Radar controller tried to contact pilot of PK-MEC four times but no answer. At 0630 LT, the Jayapura Radar Controller requested the pilot of PK-RCE that was just took off from Sentani to visually observe the position of PK-MEC aircraft. Few minutes later, the pilot of PK-RCE reported to Jayapura Radar controller that some debris were seen on Sentani Lake and some boats were moving toward the debris location. The pilot of PK-RCE assumed that PK-MEC aircraft had crashed to the lake. The pilot fatally injured. The wreckages have been recovered including the Global Positioning System (GPS) data card.

Crash of an IAI 1124A Westwind II in Manila: 8 killed

Date & Time: Mar 29, 2020 at 2000 LT
Type of aircraft:
Operator:
Registration:
RP-C5880
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Manila - Tokyo
MSN:
353
YOM:
1981
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
An IAI Westwind II 1124A type of aircraft with registry number RP-C5880, was destroyed following a runway excursion while taking-off at RWY 06, Ninoy Aquino International Airport (NAIA), Manila Philippines. All eight (8) occupants (six (6) Filipino, one (1) Canadian and one (1) American citizen are fatally injured. The aircraft is being operated by Lionair Inc. and was bound for Haneda, Japan on a medical evacuation flight. While the aircraft was on take-off roll before reaching taxiway R2, sparks were noted at the runway, it continued until the aircraft came to complete stop and engulfed by fire. Chunks of rubber and metal debris were present on the runway. Scrape marks coming from the right hand (RH) wheel hub were also visible. Tire marks followed by scrape marks on the runway coming from the LH tire and wheel hub were also seen after taxiway H1 intersection. Large portion of the remaining LH tire was recovered from the grassy portion near taxiway H1. After exiting from the asphalted portion of runway safety area, the aircraft initially run over two (2) runway edge lights then impacted into a concrete electric junction box and came to a complete stop at the runway secondary fence. The aircraft settled almost 172 meters away from the end of RWY 06, in an upright position at 14°30'53.50"N; 121°1'48.48"E and heading of 170 degrees. The flight was on Instrument Flight Rules (IFR) condition. A Notice to Airmen (NOTAM) of NAIA RWY 06/24 closure for aircraft operation was declared at 2000H and opened for operation at 0420H, March 30, 2020.
Probable cause:
The accident was the caused by the combination of the decision of the PF to abort the take-off after VR that resulted to runway excursion and incorrect pilot techniques or procedures in the high-speed rejected take-off.
The following contributing factors were identified:
- Operational pressures related to the delay of schedule due to late filing of the flight plan compelling the crew to rush and meet the schedule demand.
- The crew's complacency by skipping required briefing item in the before take-off checklist, in this case, the considerations in the event of a malfunction before/after V1.
Final Report:

Crash of a PZL-Mielec AN-2P in Ust-Kamenogorsk

Date & Time: Feb 26, 2020 at 1226 LT
Type of aircraft:
Operator:
Registration:
UP-A0001
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Ust-Kamenogorsk - Aksuat
MSN:
1G140-49
YOM:
1972
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine airplane departed Ust-Kamenogorsk Airport on an ambulance flight to Aksuat. After takeoff, while in initial climb, the crew encountered engine problems. They elected to make an emergency in a snow covered field. The airplane came to rest upside down, bursting into flames. All five occupants escaped with minor injuries while the aircraft was destroyed.

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 Boeing 737-524 in Usinsk

Date & Time: Feb 9, 2020 at 1227 LT
Type of aircraft:
Operator:
Registration:
VQ-BPS
Survivors:
Yes
Schedule:
Moscow - Usinsk
MSN:
28909/2960
YOM:
1997
Flight number:
UT595
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
94
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
17852
Captain / Total hours on type:
7672.00
Copilot / Total flying hours:
6595
Copilot / Total hours on type:
4989
Aircraft flight hours:
57410
Aircraft flight cycles:
29162
Circumstances:
Following an uneventful flight from Moscow-Vnukovo Airport, the crew initiated the descent to Usinsk Airport Runway 13. On short final, the aircraft hit a snow bank (1,1 metre high) located 32 metres short of runway threshold, still on the concrete zone. Upon impact, both main gears were torn off and the airplane belly landed and slid for few hundred metres before coming to rest. All 100 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The accident with the Boeing 737-500 VQ-BPS aircraft occurred during the landing as a result of a collision of the aircraft with a snow parapet 1.1 m high at a distance of 32 m to the runway threshold (within the paved section of the runway), which resulted in damage to the main landing gear and their subsequent "folding" in the process of moving along the runway.
The accident was caused by a combination of the following factors:
- the presence of contradictions in the Federal Aviation Rules for flights in the airspace of the Russian Federation, the airline's radio control system and the aircraft operational documentation regarding the need and procedure for introducing temperature corrections to the readings of barometric altimeters at low ambient temperatures;
- Failure by the operator of the Usinsk aerodrome to comply with the FAP-262 requirements for the maintenance of the aerodrome, which resulted in the presence of snow parapets on the paved section of the landing strip;
- the operator of the Usinsk aerodrome did not eliminate the shortcomings in the winter maintenance of the aerodrome, noted based on the results of the inspection by the Rosaviatsia commission on January 22, 2020;
- lack of risk assessment in the airline associated with the execution of approaches in the baro-VNAV mode in the presence of factors that impede such approaches (low ambient temperatures, snow-covered underlying surface, drifting snow (snowstorm), significant changes in the relief in front of the runway end, lack of PAPI-type lights), as well as appropriate recommendations to the crews on the specifics of such approaches, including after the transition to visual flight, and crew training;
- insufficient assessment by the crew during the preparation of the existing threats (hazard factors) and making an insufficiently substantiated decision to perform an RNAV (GNSS) approach (under the control of the autopilot in LNAV/VNAV mode) without introducing a correction for low outside air temperature in altitude overflying waypoints, which led to a flight below the established glide path;
- performing a flight along the "extended glide path" after turning off the autopilot and switching to manual piloting without attempting to enter the set glide path;
- the PIC may have had a visual illusion of a "high glide path" due to a snow-covered underlying surface, a snowstorm and the presence of a ravine directly in front of the runway end in the absence of PAPI type lights, which led to an incorrect assessment of the aircraft's flight altitude after switching to manual piloting, lack of reaction to timely and correct warnings of the co-pilot and exit to the runway end at a height significantly less than the established one.
Final Report:

Crash of a Being 737-86J in Istanbul: 3 killed

Date & Time: Feb 5, 2020 at 1820 LT
Type of aircraft:
Operator:
Registration:
TC-IZK
Survivors:
Yes
Schedule:
Izmir - Istanbul
MSN:
37742
YOM:
2009
Flight number:
PC2193
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
177
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
Following an uneventful flight from Izmir-Adnan Menderes Airport, the crew initiated the approach to Istanbul-Sabiha Gökçen Airport runway 06. Weather conditions were poor with thunderstorm activity, rain, CB's and a wind from 290 gusting to 37 knots. After touchdown on a wet runway, the airplane was unable to stop within the remaining distance. It overran, turned slightly to the left then went down an embankment (25 meters high) and came to rest, broken in three. Three passengers were killed while all 180 other occupants were evacuated to local hospitals. It is understood that the airplane apparently landed 1,500 meters past the runway threshold (runway 06 is 3,000 meters long) with a non negligible tailwind component that must be confirmed.