Crash of a Boeing 737-8HG in Kozhikode: 21 killed

Date & Time: Aug 7, 2020 at 1941 LT
Type of aircraft:
Operator:
Registration:
VT-AXH
Survivors:
Yes
Schedule:
Dubai - Kozhikode
MSN:
36323/2109
YOM:
2006
Flight number:
IX1344
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
184
Pax fatalities:
Other fatalities:
Total fatalities:
21
Captain / Total flying hours:
10848
Captain / Total hours on type:
4612.00
Copilot / Total flying hours:
1989
Copilot / Total hours on type:
1723
Aircraft flight hours:
43691
Aircraft flight cycles:
15309
Circumstances:
Air-India Express Limited B737-800 aircraft VT-AXH was operating a quick return flight on sector Kozhikode-Dubai-Kozhikode under ‘Vande Bharat Mission’ to repatriate passengers who were stranded overseas due to closure of airspace and flight operations owing to the Covid-19 pandemic. The aircraft departed from Kozhikode for Dubai at 10:19 IST (04:49 UTC) on 07 August 2020 and landed at Dubai at 08:11 UTC. The flight was uneventful. There was no change of crew and no defect was reported on the first sector. The aircraft departed from Dubai for Kozhikode at 10:00 UTC as flight AXB 1344 carrying 184 passengers and six crew members. AXB 1344 made two approaches for landing at Kozhikode. The aircraft carried out a missed approach on the first attempt while coming into land on runway 28. The second approach was on runway 10 and the aircraft landed at 14:10:25 UTC. The aircraft touched down approximately at 4,438 ft on 8,858 ft long runway, in light rain with tailwind component of 15 knots and a ground speed of 165 knots. The aircraft could not be stopped on the runway and this ended in runway overrun. The aircraft exited the runway 10 end at a ground speed of 84 knots and then overshot the RESA, breaking the ILS antennae and a fence before plummeting down the tabletop runway. The aircraft fell to a depth of approximately 110 ft below the runway elevation and impacted the perimeter road that runs just below the tabletop runway, at a ground speed of 41 knots and then came to an abrupt halt on the airport perimeter road just short of the perimeter wall. There was fuel leak from both the wing tanks; however, there was no postcrash fire. The aircraft was destroyed and its fuselage broke into three sections. Both engines were completely separated from the wings. The rescue operations were carried out by the ARFF crew on duty with help of Central Industrial Security Force (CISF) personnel stationed at the airport and several civilians who rushed to the crash site when the accident occurred. Upon receipt of the information about the aircraft crash the district administration immediately despatched fire tenders and ambulances to the crash site. Nineteen passengers were fatally injured and Seventy Five passengers suffered serious injuries in the accident while Ninety passengers suffered minor or no injuries. Both Pilots suffered fatal injuries while one cabin crew was seriously injured and three cabin crew received minor injuries. The rescue operation was completed at 16:45 UTC (22:15 IST).
Probable cause:
The probable cause of the accident was the non adherence to SOP by the PF, wherein, he continued an unstabilized approach and landed beyond the touchdown zone, half way down the runway, in spite of ‘Go Around’ call by PM which warranted a mandatory ‘Go Around’ and the failure of the PM to take over controls and execute a ‘Go Around’.

The following contributing factors were identitified:

The investigation team is of the opinion that the role of systemic failures as a contributory factor cannot be overlooked in this accident. A large number of similar accidents/incidents that have continued to take place, more so in AIXL, reinforce existing systemic failures within the aviation sector. These usually occur due to prevailing safety culture that give rise to errors, mistakes and violation of routine tasks performed by people operating within the system. Hence, the contributory factors enumerated below include both the immediate causes and the deeper or systemic causes.

(i) The actions and decisions of the PIC were steered by a misplaced motivation to land back at Kozhikode to operate next day morning flight AXB 1373. The unavailability of sufficient number of Captains at Kozhikode was the result of faulty AIXL HR policy which does not take into account operational requirement while assigning permanent base to its Captains. There was only 01 Captain against 26 First Officers on the posted strength at Kozhikode.

(ii) The PIC had vast experience of landing at Kozhikode under similar weather conditions. This experience might have led to over confidence leading to complacency and a state of reduced conscious attention that would have seriously affected his actions, decision making as well as CRM.

(iii) The PIC was taking multiple un-prescribed anti-diabetic drugs that could have probably caused subtle cognitive deficits due to mild hypoglycaemia which probably contributed to errors in complex decision making as well as susceptibility to perceptual errors.

(iv) The possibility of visual illusions causing errors in distance and depth perception (like black hole approach and up-sloping runway) cannot be ruled out due to degraded visual cues of orientation due to low visibility and suboptimal performance of the PIC’s windshield wiper in rain.

(v) Poor CRM was a major contributory factor in this crash. As a consequence of lack of assertiveness and the steep authority gradient in the cockpit, the First Officer did not take over the controls in spite of being well aware of the grave situation. The lack of effective CRM training of AIXL resulted in poor CRM and steep cockpit gradient.

(vi) AIXL policies of upper level management have led to a lack of supervision in training, operations and safety practices, resulting in deficiencies at various levels causing repeated human error accidents in AIXL

(vii) The AIXL pilot training program lacked effectiveness and did not impart the requisite skills for performance enhancement. One of the drawbacks in training was inadequate maintenance and lack of periodic system upgrades of the simulator. Frequently recurring major snags resulted in negative training. Further, pilots were often not checked for all the mandatory flying exercises during simulator check sessions by the Examiners.

(viii) The non availability of OPT made it very difficult for the pilots to quickly calculate accurate landing data in the adverse weather conditions. The quick and accurate calculations would have helped the pilots to foresee the extremely low margin for error, enabling them to opt for other safer alternative.

(ix) The scrutiny of Tech Logs and Maintenance Record showed evidence of nonstandard practice of reporting of certain snags through verbal briefing rather than in writing. There was no entry of windshield wiper snag in the Tech log of VT-AXH. Though it could not be verified, but a verbal briefing regarding this issue is highly probable.

(x) The DATCO changed the runway in use in a hurry to accommodate the departure of AIC 425 without understanding the repercussions on recovery of AXB 1344 in tail winds on a wet runway in rain. He did not caution AXB 1344 of prevailing strong tail winds and also did not convey the updated QNH settings.

(xi) Accuracy of reported surface winds for runway 10 was affected by installation of wind sensor in contravention to the laid down criteria in CAR. This was aggravated by frequent breakdown due to poor maintenance.

(xii) The Tower Met Officer (TMO) was not available in the ATC tower at the time of the accident. The airfield was under two concurrent weather warnings and it is mandatory for the TMO to be present to update and inform the fast changing weather variations to enhance air safety. During adverse weather conditions the presence of the TMO in the ATC tower was even more critical.

(xiii) The AAI has managed to fulfil ICAO and DGCA certification requirements at Kozhikode aerodrome for certain critical areas like RESA, runway lights and approach lights. Each of these, in isolation fulfils the safety criteria however, when considered in totality, this left the aircrew of AXB 1344 with little or no margin for error. Although not directly contributory to the accident causation, availability of runway centreline lights would have certainly enhanced the spatial orientation of the PIC.

(xiv) The absence of a detailed proactive policy and clear cut guidelines by the Regulator on monitoring of Long Landings at the time of the accident was another contributory factor in such runway overrun accidents. Long Landing has been major factor in various accidents and incidents involving runway excursion since 2010 and has not been addressed in CAR Section 5, Series F, Part II.

(xv) DGCA did not comprehensively revise CAR Section 5, Series F, Part II Issue I, dated 30 Sep 99 (Rev. on 26 Jul 2017) on ‘Monitoring of DFDR/QAR/PMR Data for Accident/Incident Prevention’ to address the recommendations of the COI of 2010 AIXL Managlore Crash regarding the exceedance limits, resulting in the persisting ambiguities in this matter.

(xvi) DFDR data monitoring for prevention of accidents/incidents is done by AIXL. However 100% DFDR monitoring is not being done, in spite of the provisions laid down in the relevant CAR and repeated audit observations by DGCA. DFDR data monitoring is the most effective tool to identify exceedance and provide suitable corrective training in order to prevent runway accidents like the crash of AXB 1344. However, ATR submitted by AIXL on the said findings were accepted by DGCA year after year without ascertaining its implementation or giving due importance to its adverse implications.
Final Report:

Crash of a Harbin Yunsunji Y-12-II in Dhobley

Date & Time: Aug 4, 2020
Type of aircraft:
Operator:
Registration:
KAF128
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Dhobley - Nairobi
MSN:
0097
YOM:
1997
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was returning to Nairobi-Eastleigh (Moi Air Base) after various supplies were delivered at Dhobley Airport on behalf of the Amisom, the African Union Mission in Somalia. Upon takeoff from Dhobley Airstrip, the aircraft crashed in unclear circumstances. All 10 occupants were injured while the aircraft was damaged beyond repair.

Crash of an Antonov AN-74TK-100 in Gao

Date & Time: Aug 3, 2020 at 1000 LT
Type of aircraft:
Operator:
Registration:
RA-74044
Flight Type:
Survivors:
Yes
Schedule:
Bamako - Gao
MSN:
470 97 936
YOM:
1994
Flight number:
UNO052P
Location:
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13299
Captain / Total hours on type:
2246.00
Copilot / Total flying hours:
3051
Copilot / Total hours on type:
1580
Aircraft flight hours:
13302
Aircraft flight cycles:
6496
Circumstances:
The aircraft was completing flight UNO-052P from Bamako to Gao on behalf of the United Nations Multidimensional Integrated Stabilization Mission in Mali (MINUSMA). En route, the crew encountered technical problems with the electrical system when the right generator failed. The crew attempted to start the APU several times but without success when the left generator also failed. The undercarriage were lowered manually and the landing was completed on a wet runway in rainy conditions. After touchdown, the crew started the braking procedure but was unable to deploy the thrust reversers. At a speed of 140-160 km/h, the aircraft overran, lost its undercarriage and came to rest in a waterlogged land. All 11 occupants were rescued, among them six were injured. The aircraft was destroyed.

Ground fire of a Boeing 777-F60 in Shanghai

Date & Time: Jul 22, 2020 at 1520 LT
Type of aircraft:
Operator:
Registration:
ET-ARH
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Shanghai – Addis Ababa – São Paulo – Santiago de Chile
MSN:
42031/1242
YOM:
2014
Flight number:
ET3739
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Parked at position 306 at Shanghai-Pudong Airport, the aircraft was prepared for a cargo service to Santiago de Chile with intermediate stops in Addis Ababa and São Paulo, when a fire erupted in the cargo compartment. The aircraft was partially destroyed by fire and damaged beyond repair. No one was injured.

Crash of a De Havilland DHC-8-Q402 Dash-8 in Beledweyne

Date & Time: Jul 14, 2020
Operator:
Registration:
5Y-VVU
Flight Type:
Survivors:
Yes
Schedule:
Djibouti City – Beledweyne
MSN:
4008
YOM:
2000
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Beledweyne-Haji-Sheikh Mahmud Hasan (Ugas Khalif) Airport, the aircraft went out of control and came to rest against several earth mounds, bursting into flames. All three crew members managed to escape while the aircraft was destroyed by fire. The crew was completing a cargo flight from Djibouti City on behalf of the African Union Mission to Somalia (AMISOM) and it is believed that the aircraft was carrying food supplies.

Crash of an Embraer EMB-121A Xingu in Tegará da Serra: 2 killed

Date & Time: Jun 14, 2020 at 0840 LT
Type of aircraft:
Registration:
PT-MBV
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Tangará da Serra – Goiânia
MSN:
121-053
YOM:
1982
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
607
Captain / Total hours on type:
41.00
Copilot / Total flying hours:
425
Aircraft flight hours:
4453
Circumstances:
Four minutes after takeoff from Tengará da Serra Airport Runway 20, while climbing, the twin engine airplane entered an uncontrolled descent. One minute later, it crashed with a high angle of attack in a cornfield, bursting into flames. The airplane disintegrated on impact and both occupants were killed.
Probable cause:
One should not rule out the hypothesis of a possible malfunction of the aircraft's angle-of-attack control system, considering that the records related to the provision of the calibration service (a necessary condition for the proper functioning of the referred system, and prescribed in the aircraft's maintenance manual) were not identified in the pertinent
control documents.
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 a Mitsubishi MU-2B-60 Marquise in Sioux Falls: 1 killed

Date & Time: Jun 7, 2020 at 0415 LT
Type of aircraft:
Operator:
Registration:
N44MX
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Everett – Huron - Kokomo
MSN:
1526
YOM:
1981
Flight number:
MDS44
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
22000
Captain / Total hours on type:
10900.00
Aircraft flight hours:
12104
Circumstances:
The pilot departed on a cross country flight in a turbine-powered, multiengine airplane at night and in visual meteorological conditions. Recovered GPS data revealed that as the airplane accelerated down the runway, it drifted to the right of the runway centerline. A video recording showed that shortly after takeoff, the airplane rolled right, the nose dropped, and the airplane impacted the ground. It came to rest on its left side with both wings separated and the fuselage was highly fragmented forward of the main landing gear. A post-accident examination of the airframe and engines found no mechanical malfunctions or anomalies that would have precluded normal operation. A witness that spoke to the pilot shortly before the accident flight stated that the pilot exhibited difficulty in completing some paperwork; however, no medical reasoning for this difficulty could be determined based upon the available evidence. The investigation determined that at the time of the accident the pilot had been on duty for about 19 hours and 20 minutes, which was contrary to duty and rest regulations. At his estimated arrival time into the destination, the pilot would have accumulated about 20 hours and 54 minutes of duty time. The investigation was unable to determine if the pilot took advantage of the opportunity for rest that existed during the day, and therefore could not determine if fatigue contributed to the accident. Investigators were unable to determine the reason for the loss of control on takeoff with the available information.
Probable cause:
The pilot’s failure to maintain control of the airplane during takeoff for reasons that could not be determined.
Final Report:

Crash of a Cessna 402C in Hampton

Date & Time: May 9, 2020 at 1513 LT
Type of aircraft:
Operator:
Registration:
N4661N
Survivors:
Yes
Schedule:
Peachtree City - Peachtree City
MSN:
402C-0019
YOM:
1979
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7330
Captain / Total hours on type:
11.00
Copilot / Total flying hours:
1096
Copilot / Total hours on type:
5
Aircraft flight hours:
17081
Circumstances:
According the commercial pilot and a flight instructor rated check pilot, they were conducting their first long-duration, aerial observation flight in the multiengine airplane, which was recently acquired by the operator. They departed with full fuel tanks, competed the 5-hour aerial observation portion of the flight, and began to return to the destination airport. About 15 miles from the airport, the left engine fuel warning light illuminated. Within a few seconds, the right engine stopped producing power. They attempted to restart the engine and turned the airplane toward an alternate airport that was closer. The pilots then turned on the electric fuel pump, the right engine began surging, and soon after the left engine stopped producing power. They turned both electric fuel pumps to the low setting, both engines continued to surge, and the pilots continued toward the alternate airport. When they were about 3 miles from the airport, both engines lost total power, and they elected to land on a highway. When they were a few feet above the ground, power returned briefly to the left engine, which resulted in the airplane climbing and beginning to roll. The commercial pilot pulled the yoke aft to avoid a highway sign, which resulted in an aerodynamic stall, and subsequent impact with trees and terrain. The airplane sustained substantial damage to the wings and fuselage. Although both pilots reported the fuel gauges indicated 20 gallons of fuel remaining on each side when the engines stopped producing power, the flight instructor noted that there was no fuel in the airplane at the time of the accident. In addition, according to a Federal Aviation Administration inspector who responded to the accident site, both fuel tanks were breached and there was no evidence of fuel spillage.
Probable cause:
A dual total loss of engine power as a result of fuel exhaustion.
Final Report:

Crash of a Learjet 35A in Esquel: 3 killed

Date & Time: May 5, 2020 at 2238 LT
Type of aircraft:
Operator:
Registration:
LV-BXU
Flight Type:
Survivors:
Yes
Schedule:
San Fernando – Esquel
MSN:
35-462
YOM:
1982
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1498
Copilot / Total flying hours:
2612
Aircraft flight hours:
11711
Aircraft flight cycles:
10473
Circumstances:
The airplane departed San Fernando Airport on an ambulance flight to Esquel, carrying a doctor, a nurse and two pilots. On approach to Esquel-Brigadier General Antonio Parodi Airport at night, the crew encountered poor visibility (200 metres) and the visual contact with the runway was lost intermittently. Nevertheless, the crew continued the approach and at decision height, the captain decided to continue the descent. After crossing Runway 23 threshold at a height of 78 feet, the pilot-in-command initiated a go-around procedure and turned to the left. The airplane continued in a left hand turn, causing the left wing tip fuel tank to struck the ground. Out of control, the airplane crashed on a small embankment located about 400 metres to the left of the runway centerline, coming to rest upside down and bursting into flames. Both passengers were killed and both pilots were seriously injured. Two days later, the copilot died from injuries sustained.
Probable cause:
It was determined that the accident was the consequence of a controlled flight into terrain (CFIT) and the airplane did not suffer any technical anomalies.
The following contributing factors were identified:
- The crew failed to check the approach charts according to SOP's,
- The approach was initiated and continued in conditions that were below weather minimums,
- Visibility data transmitted by Tower to the crew were inaccurate, leading to confusion on the part of the pilots and their decision-making,
- Both engines were at full power upon impact as the crew was initiating a go-around procedure.
Final Report: