Crash of a Cessna 401A in Arnsberg

Date & Time: Aug 28, 2020 at 1602 LT
Type of aircraft:
Operator:
Registration:
N401JP
Flight Type:
Survivors:
Yes
Schedule:
Marl – Arnsberg
MSN:
401A-0046
YOM:
1969
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6300
Captain / Total hours on type:
500.00
Aircraft flight hours:
4568
Aircraft flight cycles:
5945
Circumstances:
At 1541 hrs, the airplane took off from Marl-Lohmühle Airfield with the pilot and 2 passengers on board to a VFR flight to Arnsberg-Menden Airfield which is located approximately 30 NM to the south-east. One of the passengers was seated in the right-hand seat next to the pilot and the other in the passenger seat behind the pilot. The radar recording of the air navigation service provider showed that the airplane climbed up to 2,200 ft AMSL. Ten minutes after take-off, the pilot established radio contact with Dortmund Tower with the request to cross Dortmund Airport control zone via the reporting point WHISKEY towards reporting point ECHO on his way to Arnsberg. At 1552:14 hrs, the tower controller answered: “[…] melden Sie WHISKEY und dann erwarten Sie Durchflug nach Arnsberg oder ECHO, wie Sie möchten, QNH eins null null eins (report WHISKEY and then expect cross flight to Arnsberg or ECHO, as you like, QNH one zero zero one)“. The pilot confirmed QNH and approach point. At 1555:22 hrs, the pilot reported having reached reporting point WHISKEY at 2,200 ft AMSL. The controller approved the flight through the control zone towards the south. The GPS and radar data showed that at 1556 hrs, the airplane turned tight towards 120° to a direct heading to Arnsberg. At 1559 hrs, as the airplane had left the control zone the controller issued the clearance to leave Tower frequency. At 1600 hrs, about 2.5 NM west of the destination aerodrome, the airplane turned left towards the east. About one minute later the airplane intersected the extended runway centre line of runway 23 at a distance of 0.7 NM from the threshold with an eastern heading. At the time, ground speed was approximately 150 kt. At 1601:39 hrs, the airplane turned left towards the final approach of runway 23. At 1602 hrs, about 1 NM from the threshold of runway 23 at about 1,500 ft AMSL, the airplane reached the extended runway centre line. The Flugleiter (A person required by German regulation at uncontrolled aerodromes to provide aerodrome information service to pilots.) stated that during final approach flaps and landing gear of the airplane had been extended. The approach looked normal. For a short time he had no longer observed the airplane because he had made some entries in the computer. His colleague had then addressed him and drew his attention to the speed of the airplane. The Flugleiter saw that the airplane had an upward large pitch angle, then plunged and disappeared from his sight. The airplane impacted the ground and the 3 occupants suffered severe injuries. The Flugleiter stated he had tried in vain to contact the pilot twice and then raised the alarm. His colleague and other first aiders had driven to the accident site immediately.
Probable cause:
The accident was due to:
• The pilot did not correct the approach by increasing engine power or did not abort the approach.
• The pilot did not monitor the airspeed during the final approach and steered the airplane into an uncontrolled flight attitude during the flare.
To the accident contributed that:
• The approach was not stabilized and not aborted.
• The pilot did not pay attention to the PAPI indication and did not perceive the stall warning.
• The large number of continuously changing approach parameters most likely exceeded the limits of the pilot’s capabilities and subsequently, the airplane was no longer controlled in a goal-oriented manner.
• The runway markings did not comply with the required standards.
Final Report:

Crash of a Rockwell 690B Turbo Commander in Ahuas

Date & Time: Aug 23, 2020
Operator:
Registration:
XB-DRA
Flight Type:
Survivors:
Yes
MSN:
11423
YOM:
1977
Country:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was engagted in an illegal contraband flight when it crash landed in an open field located near Ahuas. No one was found on site and the aircraft was damaged beyond repair. A load of cocaine was found on board.

Crash of a Let L-410UVP-E3 near Bukavu: 4 killed

Date & Time: Aug 13, 2020 at 1535 LT
Type of aircraft:
Operator:
Registration:
9S-GEN
Flight Type:
Survivors:
No
Site:
Schedule:
Kalima – Bukavu
MSN:
89 23 25
YOM:
1989
Location:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
While descending to Bukavu-Kavumu Airport on a flight from Kalima, the crew encountered poor visibility due to fog. Seven minutes prior to ETA, the aircraft struck trees and crashed in a wooded and mountainous area located in the Kahuzi-Miega National Park. The wreckage was found about 15 km south of the airport. All four occupants were killed.

Crash of a Cessna 340A in Orléans

Date & Time: Aug 10, 2020 at 1355 LT
Type of aircraft:
Operator:
Registration:
N413JF
Flight Type:
Survivors:
Yes
Schedule:
Perpignan – Orléans
MSN:
340A-0746
YOM:
1979
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2635
Captain / Total hours on type:
41.00
Circumstances:
Then twin engine airplane departed Perpignan-La Llabanère Airport on a private flight to Orléans, carrying one passenger and one pilot. On final approach to Orléans-Loiret Airport (ex Saint-Denis-de-l’Hôtel), the pilot encountered a loss of power on the left engine. He attempted an emergency landing when the airplane impacted trees and crash landed in a wooded area located about 3 km short of runway 23, bursting into flames. Both occupants escaped uninjured while the airplane was totally destroyed by a post crash fire.
Probable cause:
The exact cause of the loss of power on the left engine could not be determined. The pilot, concentrating on monitoring the approach parameters, did not immediately realize the left engine malfunction. He noticed that the aircraft's rate of descent was too high to follow the standard approach slope. The pilot first attempted to go around and reconfigured the aircraft to do so by retracting the landing gear and flaps. In spite of these actions, the pilot noticed that the power delivered by the aircraft's engines did not allow him to recover the plane and understood, by being aware of the action of his right foot on the rudder pedal, that the power delivered by the left engine was abnormally low. Given the low height of the plane at the time of this observation, the pilot decided to land in the country. Contributing to the high rate of descent after the occurrence of the left engine malfunction was the fact that the drags were extended at the time the engine power decreased and the fact that the left propeller probably windmilling until the landing.
Final Report:

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 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.

Crash of a Beechcraft B200 Super King Air near Brus Laguna

Date & Time: Jul 20, 2020
Operator:
Registration:
N740P
Flight Type:
Survivors:
Yes
MSN:
BB-1218
YOM:
1985
Country:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Engaged in an illegal flight, the twin engine airplane landed on a dirt road located about 35 km southwest of Brus Laguna. The nose gear collapsed and the aircraft came to rest, damaged beyond repair. No one was found on site and a load of 806 kilos of cocaine was seized.

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 a Gulfstream GII near Machiques: 1 killed

Date & Time: Jun 15, 2020
Type of aircraft:
Operator:
Registration:
N27SL
Flight Type:
Survivors:
Yes
MSN:
84
YOM:
1970
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The crew was engaged in an illegal trip and elected to land on a remote 'airstrip' located in the region of Machiques. The aircraft crash landed and came to rest, bursting into flames. One pilot was killed and the second was injured.

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: