This is a good article. Click here for more information.

Air India Express Flight 1344

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Air India Express Flight 1344
File:Boeing 737-8HJ, Air India Express AN1157698.jpg
VT-AXH, the aircraft involved in the accident, in 2006.
Accident summary
Date 7 August 2020 (2020-08-07)
Summary Runway overrun in poor weather conditions due to pilot error
Site Beyond runway 10 at Calicut International Airport, Malappuram district, Kerala, India
Lua error in package.lua at line 80: module 'strict' not found.
Passengers 184
Crew 6
Injuries (non-fatal) 167[1]
Fatalities 21[2]
Survivors 169
Aircraft type Boeing 737-8HG(SFP)
Operator Air India Express
Registration VT-AXH
Flight origin Dubai International Airport, United Arab Emirates
Destination Calicut International Airport, Kerala, India
Syntax error
<maplink zoom="15" latitude="<strong class="error"><span class="scribunto-error" id="mw-scribunto-error-2">Lua error in package.lua at line 80: module 'strict' not found.</span></strong>" longitude="<strong class="error"><span class="scribunto-error" id="mw-scribunto-error-3">Lua error in package.lua at line 80: module 'strict' not found.</span></strong>" text="[Full screen]">

[


{"type": "FeatureCollection",

 "features": [


{ "type": "Feature",

  "geometry": {"type": "Point", "coordinates": [Lua error in package.lua at line 80: module 'strict' not found.,Lua error in package.lua at line 80: module 'strict' not found.] },
  "properties": {
   "title": "Calicut International Airport", 
   "description": "",
   "marker-symbol": "-number", "marker-size": "medium", "marker-color": "#B80000" }
}

, { "type": "Feature",

  "geometry": {"type": "Point", "coordinates": [Lua error in package.lua at line 80: module 'strict' not found.,Lua error in package.lua at line 80: module 'strict' not found.] },
  "properties": {
   "title": "Crash site", 
   "description": "",
   "marker-symbol": "-number", "marker-size": "medium", "marker-color": "#B80000" }
}





























] }

]</maplink>

Air India Express Flight 1344 was a scheduled international flight on 7 August 2020 from Dubai, United Arab Emirates, to Kozhikode, India, landing at Calicut International Airport. The flight was part of the Vande Bharat Mission to repatriate Indian nationals stranded due to the COVID-19 pandemic. The flight crew aborted two landing attempts because of heavy rain and tailwind. On the third landing attempt, the aircraft touched down on runway 10, but skidded off the end of the tabletop runway and slid down a 9–10.5 m (30–35 ft) slope, killing 19 passengers and both pilots. The four cabin crew members and 165 passengers survived, of whom all but two were injured.[3] This was the second fatal accident involving Air India Express, after the 2010 Mangalore crash.

Background

Airport

Calicut International Airport in Karipur, Malappuram, is considered one of the most dangerous airports in India, according to India's Directorate General of Civil Aviation (DGCA).[4] It has a tabletop runway, a runway that is located on the top of a plateau or hill with one or both ends adjacent to a steep precipice which drops into a gorge. The DGCA designated Calicut Airport as a "critical airfield", which means that only the captain (and not the first officer) can perform takeoffs and landings there.[5] The Airports Authority of India says that the airport is licensed for use in all weather conditions under instrument flight rules, but that the pilots operating flights to and from Calicut Airport (both day and night) should have sufficient flying hours at night to handle the dangerous conditions.[6]

Captain Mohan Ranganathan, a member of a safety advisory committee of the Ministry of Civil Aviation, said in 2011 that Calicut Airport is "unsafe". He recommended that Calicut Airport not be used for landing during wet weather. He observed that the airport had a tabletop runway with a steep down-slope from one-third of the runway 10 and inadequate "buffer zones", referring to the runway end safety areas (RESA) at both ends of the runway. Instead of the recommended 240 m (790 ft) safety area, it had only 90 m (300 ft). The width of runway 10 is only half of the minimum width that existing regulations require, with very little buffer zone on either side, whereas the recommended width is 150 m (490 ft). Calicut Airport also lacked an engineered materials arrestor system (EMAS), which could have prevented the accident. He also reported that there were heavy rubber deposits on the runway.[7] Calicut Airport's management ignored several warnings about the dangerous conditions at Calicut Airport, especially during wet conditions.[8][9][10] Many international airlines stopped landing wide-body aircraft at Calicut because of the dangerous conditions.[11][12] Ranganathan said "The warnings were ignored... in my opinion, it is not an accident but a murder. Their own audits have had flagged safety issues".[10]

Conditions at Calicut Airport were investigated in 2019, following a tailstrike during the landing of Air India Express aircraft. The investigation revealed several safety hazards, including multiple cracks in the runways, pools of stagnant water, and excessive rubber deposits. In July 2019, the DGCA issued a show-cause notice to the director of Calicut Airport because of these hazards.[13][14][15]

Aircraft and crew

The accident involved a Boeing 737-800 with a short-field performance package, registered as VT-AXH, manufacturer's serial number 36323 and line number 2108.[16] The aircraft, that first flew on 15 November 2006, was operated by Air India Express and had a tail livery with India Gate on the left and Gateway of India on the right.[17] The crew consisted of Captain Deepak Sathe (59), first officer Akhilesh Kumar (32); and four flight attendants.[18][19][20] Sathe had landed successfully at Calicut airport at least 27 times, including more than ten times in 2020.[11] He had 10,000 hours of flying experience on the Boeing 737, including 6,662 as commander.[21]

Crash

The aircraft departed stand E6 and took off from runway 30R at Dubai International Airport on 7 August 2020, at 14:14 GST (7 August 2020, 10:14 UTC) and was scheduled to arrive at Calicut International Airport at 19:40 IST (7 August 2020, 14:10 UTC), covering a distance of 2,673 kilometres (1,661 mi).[22] It was a repatriation flight for people who had been stranded abroad due to the COVID-19 pandemic, under the Vande Bharat Mission.[23]

The aircraft reached the airport on schedule. The approach was for runway 28, but two landings were aborted due to tailwind and the aircraft circled, waiting for clearance before making a landing on runway 10.[lower-alpha 1][26][27] At around 19:37 IST (14:07 UTC), they were given clearance to land on runway 10.[12] Due to the monsoon and floods in Kerala at the time, inclement weather conditions reduced visibility at the time of landing to 2,000 m (6,600 ft). Runway 28 was operational and in the first landing attempt, the pilot could not see the runway thus requested for runway 10. On the second attempt on 2,860 m (9,380 ft) runway 10, the aircraft touched down near taxiway ''C'', which is approximately 1,000 m (3,300 ft) beyond the runway threshold.[28][29] The aircraft failed to stop before the end of the tabletop runway and plunged 9–10.5 m (30–35 ft) into a gorge, splitting the fuselage into two sections upon impact.[26][30] The accident site was around 3 km (9,800 ft) from the airport terminal.[31] No post-crash fire was reported.[32] It was suggested that the crew shut off the engines on landing, which may have saved lives by preventing a fire.[33] According to a CISF officer, the aircraft did not slide into the gorge. It took off from the cliff and then collapsed.[31]

The accident was the second fatal accident of Air India Express and was similar to Air India Express Flight 812 which also overran the runway 10 years earlier at Mangalore International Airport, killing 158 people on board.[34][35][36]

Victims

A total of 184 passengers, four cabin crew and two cockpit crew were on board, all Indian.[37][38][39] Seventeen people died on-spot from the crash, including both pilots.[32] Later the death toll rose to twenty-one people on 24 August.[40][41][2] and more than 100 people were injured.[42][43][44] The chief minister of Maharashtra, Uddhav Thackeray, announced a state funeral for late Wing commander Captain Deepak Vasant Sathe in Mumbai.[45]

List of fatalities[46][2]
Type of victims Total on board Survivors Fatalities
Passengers 184 165 19
Pilots 2 0 2
Cabin crew 4 4 0
Total 190 169 21

Compensation

The Government of India and Kerala each announced an interim compensation of ₹10 lakh (US$15,000) for the families of the deceased above the age of 12 years, ₹5 lakh (US$7,400) for below the age of 12 years, ₹2 lakh (US$3,000) for seriously injured, and ₹50,000 (US$740) for those who sustained minor injuries.[47] It was also announced that the medical expenses of the injured would be borne by the state government.[48][49]

Air India Express completed the disbursement of interim compensation to all passengers and next of kin of the deceased passengers soon after the accident.[50] Interim compensation of ₹10 lakh (US$15,000) was paid to the next of kin of 15 deceased passengers who were above the age of 12, ₹5 lakh (US$7,400) to the next of kin of 4 deceased passengers who were below the age of 12, ₹2 lakh (US$3,000) each to 92 passengers and 2 crew members who were critically injured, and ₹50,000 (US$740) each to 73 passengers who suffered minor injuries.[50]

Aftermath

Rescue and response

Following the incident, local people from the surrounding Karipur village rushed to the crash site to rescue trapped victims from the aircraft,[51] followed by 40 Central Industrial Security Force (CISF) personnel who were guarding the perimeter of the airport, a quick reaction team and the Chief Airport Security Officer. Family members of the CISF personnel living nearby also joined.[52] Police and firefighters were also deployed for the initial rescue operations.[53] All passengers were evacuated in about three hours and taken to various hospitals in Kozhikode and Malappuram districts.[42][44][39] Emergency response team, GO Team[lower-alpha 2] and special assistance team of Air India (officially known as 'Angels of Air India')[46] from Kochi, Mumbai and Delhi were sent to the accident site.[55][56] Three CISF officers were awarded Director General commendation disc for their rescue efforts after the mishap.[57][58] The accident is predicted to cost the insurers and their reinsurers ₹375 crore (US$56 million), which includes aircraft or hull and liability for third party and passengers. It is around 90 per cent of the insured value and Air India will recover this amount since the aircraft has been totally damaged. The insurer is an Indian insurance consortium led by New India Assurance. Claim settlement survey has already started.[59][60][61] The airline had engaged a US-based firm, Kenyon International, to recover the baggage along with Angels of Air India.[62]

COVID-19 infection

Two passengers on the flight who survived tested positive for COVID-19, after arriving at a hospital after the accident. To check the spread among other passengers and rescue personnel, CISF and Kerala Health Department asked their personnel and other passengers who were on the flight to undertake testing and quarantine.[63][48][64] One week later, 24 officers involved in the rescue operation tested positive. Kondotty municipality, the place where the airport is located, was subsequently declared as a containment zone.[65][66]

Pilots associations' response

The International Federation of Air Line Pilots' Associations (IFALPA) tightly monitored the actions after the accident and responded "Our thoughts are with the families of the pilots, crew members, and passengers who lost their lives aboard the aircraft. We send support and wishes to all the survivors, many of them injured and in hospital in critical condition." They got in touch with the Indian association, Air Line Pilots’ Association-India (ALPA-India) and the Aircraft Accident Investigation Bureau (AAIB) for technical expertise and assistance in investigation.[67][11]

Following the accident, many pilot associations in the country soared up against the director of the DGCA, Arun Kumar, and wanted him to be replaced with someone more technically sound in aviation, after he referred to the late pilots as "fellows” and also said, "...and the landing it seems was not appropriate...", "The landing was not smooth". The pilot associations pointed that these comments from the director were amateurish and made them "the laughing stock of the aviation world".[68]

Public interest litigation

According to Yeshwant Shenoy, a lawyer fighting for safer airports in India, the DGCA should have put restrictions on conditions when airlines could land or take off. He blamed the DGCA for being incompetent and negligent after the 2010 crash in Mangalore, and called it a state-run syndicate.[69] He filed a Public Interest Litigation (PIL) in the Kerala High Court after the crash, to shut down operations of Calicut airport as it is not compliant with air regulations. Shenoy demanded for an open inquiry by a Court of Inquiry instead of a closed one by AAIB. He also demanded that the investigation should be conducted by the Central Bureau of Investigation as local police weren't experienced in these.[70]

Investigation

The Directorate General of Civil Aviation (DGCA) and Flight Safety Departments investigated the accident.[44][71][72] The cockpit voice recorder and flight data recorder were recovered the next day and sent to Delhi for analysis.[73] Boeing was to send its investigation team to examine the debris of the aircraft for defects and assist the probe.[74][57]

Initial findings suggested that at the time of landing, the tailwind was around 9 knots (17 km/h). The aircraft was at 176 knots (326 km/h) at an altitude of approximately 450 feet (140 m) above the surface of runway 10, which is not considered ideal for short finals during poor weather conditions.[75] The throttle was found to be in a fully forward position (takeoff or go-around position) and the spoilers were retracted from the position of the speed brake lever, which indicates that the pilots might have tried for a go-around.[76][77] The tailwind, rubber deposits and wet runway affecting the braking performance of the aircraft are thought to be contributory factors to the accident.[7] Civil Aviation Minister, Hardeep Puri, in a press conference at Kozhikode on 8 August, said that there had been sufficient fuel onboard for the aircraft to have flown to a diversion airport.[75] The possibility of pilot error as a cause of the accident was suggested by DGCA's Arun Kumar.[78][12][79][80]

Several concerns were raised on the inquiry on this incident, by Captain Mohan Ranganathan, Yeshwant Shenoy and others, that it might get covered up and the truth would never surface.[7][10][69] Royal Aeronautical Society fellow and aviation safety expert Amit Singh alleged that evidence in the crash site was being tampered, as few unidentified people were spotted near the wreckage, thus asked for an open investigation.[81] He also pointed out that investigations were flawed and instead of punishing real culprits, actions were taken against the pilots.[82]

Aircraft Accident Investigation Bureau (AAIB)

The AAIB team in Kozhikode probed the incident with the assistance of Airports Authority of India officials, air traffic control, ground staff, CISF, the fire team and the rescue team. It found evidence of waterlogging of the runway at the time of landing. It also checked whether ATC was aware of waterlogging and whether the pilots adhered to rules. The preliminary investigation report was expected to be ready in a week after the accident,[57] however this did not happen.[83] The United States National Transportation Safety Board (NTSB) also sent a member to assist the AAIB.[84]

A five-member committee was set up by AAIB on 13 August, to investigate the incident, with the final report to be submitted on 13 January 2021. The committee headed by Captain S.S. Chahar, former designated examiner on Boeing 737 Next Generation, was to also provide recommendations to avoid such accidents in future.[85][86][87] The civil aviation ministry cited delays due to the COVID-19 pandemic and granted a two-month extension to the AAIB to submit its draft final probe report on the crash.[88][89]

The report was released on September 11, 2021, where it said that the probable cause of the accident was "the non-adherence to standard operating procedures by the pilot flying". The pilot in command did not do a Go Around despite the call for it by the co-pilot, who also failed to take over the controls.[90][91][1]

Ban on wide-body aircraft

Shortly after the crash, operations of wide-body aircraft at Kozhikode were put on hold. As a result, Etihad and Saudia removed their services to Calicut.[92]

In popular culture

Vande Bharat Flight IX 1344: Hope to Survival is a 2021 Discovery+ original documentary based on the crash. The 45-minute documentary creates graphical simulations of the accident.[93][94]

See also

Explanatory notes

<templatestyles src="Reflist/styles.css" />

Cite error: Invalid <references> tag; parameter "group" is allowed only.

Use <references />, or <references group="..." />

References

<templatestyles src="Reflist/styles.css" />

Cite error: Invalid <references> tag; parameter "group" is allowed only.

Use <references />, or <references group="..." />

External links

  1. ↑ 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 2.2 Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ 7.0 7.1 7.2 Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ 10.0 10.1 10.2 Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ 11.0 11.1 11.2 Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ 12.0 12.1 12.2 Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ 26.0 26.1 Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ 31.0 31.1 Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ 32.0 32.1 Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ 39.0 39.1 Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ 42.0 42.1 Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ 44.0 44.1 44.2 Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ 46.0 46.1 Lua error in package.lua at line 80: module 'strict' not found.
  47. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  48. ↑ 48.0 48.1 Lua error in package.lua at line 80: module 'strict' not found.
  49. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  50. ↑ 50.0 50.1 Lua error in package.lua at line 80: module 'strict' not found.
  51. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  52. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  53. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  54. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  55. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  56. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  57. ↑ 57.0 57.1 57.2 Lua error in package.lua at line 80: module 'strict' not found.
  58. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  59. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  60. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  61. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  62. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  63. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  64. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  65. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  66. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  67. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  68. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  69. ↑ 69.0 69.1 Lua error in package.lua at line 80: module 'strict' not found.
  70. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  71. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  72. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  73. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  74. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  75. ↑ 75.0 75.1 Lua error in package.lua at line 80: module 'strict' not found.
  76. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  77. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  78. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  79. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  80. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  81. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  82. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  83. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  84. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  85. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  86. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  87. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  88. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  89. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  90. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  91. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  92. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  93. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  94. ↑ Lua error in package.lua at line 80: module 'strict' not found.


Cite error: <ref> tags exist for a group named "lower-alpha", but no corresponding <references group="lower-alpha"/> tag was found, or a closing </ref> is missing

Retrieved from "https://infogalactic.com/w/index.php?title=Air_India_Express_Flight_1344&oldid=726749260"