Jump to content

1996 Charkhi Dadri mid-air collision

Coordinates: 28°33′38″N 76°18′15″E / 28.56056°N 76.30417°E / 28.56056; 76.30417
From Wikipedia, the free encyclopedia
(Redirected from Gaurav Maheshwari)

Saudia Flight 763
Kazakhstan Airlines Flight 1907
Accident
Date12 November 1996 (1996-11-12)
SummaryMid-air collision
SiteCharkhi Dadri, Haryana, India
28°33′38″N 76°18′15″E / 28.56056°N 76.30417°E / 28.56056; 76.30417
Total fatalities349
Total survivors0
First aircraft

HZ-AIH, the Boeing 747 involved, in 1986
TypeBoeing 747-168B
OperatorSaudi Arabian Airlines
IATA flight No.SV763
ICAO flight No.SVA763
Call signSAUDIA 763
RegistrationHZ-AIH
Flight originIndira Gandhi International Airport, Delhi, India
DestinationDhahran International Airport, Dhahran, Saudi Arabia
Occupants312
Passengers289
Crew23
Fatalities312
Survivors0
Second aircraft

UN-76435, the Ilyushin Il-76TD involved, in 1994
TypeIlyushin Il-76TD
OperatorKazakhstan Airlines
IATA flight No.KZ1907
ICAO flight No.KZA1907
Call signKAZAKH 1907
RegistrationUN-76435
Flight originChimkent Airport, Kazakhstan
DestinationIndira Gandhi International Airport, Delhi, India
Occupants37
Passengers27
Crew10
Fatalities37
Survivors0

On 12 November 1996, Saudia Flight 763, a Boeing 747 en route from Delhi, India, to Dhahran, Saudi Arabia, and Kazakhstan Airlines Flight 1907, an Ilyushin Il-76 en route from Chimkent, Kazakhstan, to Delhi, collided over the city of Charkhi Dadri, around 100 km (62 mi; 54 nmi) west of Delhi. The crash killed all 349 people on board both planes, making it the world's deadliest mid-air collision[1][2] and the deadliest aviation accident ever in India.[3][4] The final report from the investigation found that "[T]he root and approximate cause of the collision" was the failure of the Kazakh crew to maintain the correct altitude.[5] Contributing factors included the poor English language skills in the Kazakh cockpit resulting in inadequate interpretation of directions provided by air traffic control, and three specific incidents of failures in crew resource management (CRM) by the Kazakh crew.[6] The report also suggested technical enhancements (including ACAS and SSR) that would provide assistance in preventing a future crew's mistakes being allowed to go unchecked in real time.[7]

Aircraft involved

[edit]

Saudi Arabian Airlines Flight 763

[edit]

Saudi Arabian Airlines Flight 763 was a Boeing 747-168B, registration HZ-AIH, departing from Delhi as part of a scheduled international DelhiDhahranJeddah passenger service with 312 people on board.[8] The crew on this flight consisted of Captain Khalid al-Shubaily (aged 44), First Officer Nazir Khan (aged 37), and Flight Engineer Ahmed Edrees (aged 33). Al-Shubaily was a veteran pilot with 9,837 flying hours.[9]

There is some dispute as to the nationalities of the passengers of Flight 763. According to an article published on 14 November 1996, 215 Indians, many of whom worked in Saudi Arabia as blue-collar workers, boarded the flight, along with 40 Nepalis and three Americans.[10] However, according to a different article, the passenger manifest included 17 people of other nationalities, including nine Nepalis, three Pakistanis, two Americans, one Bangladeshi, one British, and one Saudi Arabian.[4] Twelve of the crew members, including five anti-terrorism officials, were Saudi Arabian citizens.[11]

Kazakhstan Airlines Flight 1907

[edit]

Kazakhstan Airlines Flight 1907, an Ilyushin Il-76TD with registration UN-76435 was on a charter service from Chimkent Airport to Delhi. The crew consisted of Captain Alexander Robertovich Cherepanov (aged 44), First Officer Ermek Kozhahmetovich Dzhangirov (aged 37), Flight Engineer Alexander Alexanderovich Chuprov (aged 50), Navigator Zhahanbek Duisenovich Aripbaev (aged 51), and Radio Operator Egor Alekseevich Repp (aged 41).[12][9] Cherepanov was highly experienced, with 9,229 flight hours.[13]

A company from Kyrgyzstan chartered the flight, and the passenger manifest mostly included ethnic Russian Kyrgyz citizens planning to go shopping in India.[4][12][10] Thirteen Kyrgyz traders boarded the flight.[11]

Accident

[edit]

Saudia Flight 763 departed Delhi at 18:32 local time (13:02 UTC). Kazakhstan Airlines Flight 1907 was descending simultaneously, to land at Delhi.[8] Both flights were controlled by approach controller V.K. Dutta.[9] Immediately after take-off, the Saudia flight was cleared to an initial altitude of 10,000 feet (3,050 m). At 18:34, Dutta cleared the Kazakh plane to descend to 15,000 feet (4,550 m) when it was 74 nautical miles (137 km) from the beacon of the destination airport. Two minutes later, at 18:36, Dutta cleared the Saudia plane, travelling on the same airway but in the opposite direction, to climb to 14,000 feet (4,250 m). At 18:38, the SVA crew reported reaching 14,000 feet, and requested a higher level. Dutta told them to hold their altitude and standby, to which First Officer Khan replied, "Saudi 763 will maintain one four zero."[9]

At 18:39, the Kazakh flight reported having reached its assigned altitude of 15,000 feet, but it was actually higher, at 16,348 feet (5,000 m), and still descending.[14][9] At this time, Dutta advised the flight, "Identified traffic 12 O'Clock, reciprocal, Saudia Boeing 747 at ten miles, likely to cross in another five miles. Report, if in sight."[9] Radio Operator Repp requested clarification, to which Dutta replied, "Traffic...is at eight miles, level 140."[9] Repp acknowledged the update, and signed off with, "Now looking 1907."[9]

Less than a minute later, at 18:40, the crew of a United States Air Force cargo flight made a radio call saying they had seen "a big explosion" at their two o'clock position.[9] Dutta attempted to contact the Saudia and Kazakh flights, but received no response. The two aircraft had collided, with the left wing of the Kazakh flight slicing through the left wing of the Saudia 747 while the left horizontal stabilizer of the 747 sliced off the vertical stabilizer (including the horizontal stabilizer) of the Kazakh flight.[citation needed] The crippled Saudi Boeing immediately lost control and went into a rapidly descending spiral with fire trailing from the wing, and broke up in mid air before crashing into the ground at a nearly supersonic speed of 1,135 km/h (613 kn; 705 mph). With most of its left wing and vertical stabilizer gone, the Ilyushin went into a flat spin and crashed into a field at a flat attitude near the wreckage of the Saudia plane. All 312 people on board SVA763 and all 37 people on Flight 1907 were killed.[15]

The recorder of the Saudi Arabian plane revealed the pilots said the Islamic Istighfar (forgiveness prayer) and recited the Shahada before impact with the ground.[9]

The collision took place about 100 kilometres (60 mi) west of Delhi.[16] The wreckage of the Saudi Arabian aircraft landed near Dhani village, Bhiwani District, Haryana. The wreckage of the Kazakh aircraft hit the ground near Birohar village, Rohtak District, Haryana.[13]

Investigation and final report

[edit]

The crash was investigated by the Lahoti Commission, headed by then-Delhi High Court judge Ramesh Chandra Lahoti. Depositions were taken from the Air Traffic Controllers Guild and the two airlines. The flight data recorders (FDR) were decoded by Kazakhstan Airlines and Saudia under the supervision of air crash investigators in Moscow and Farnborough, England, respectively.[17] The ultimate cause was held to be the failure of Kazakhstan Airlines Flight 1907's pilot to follow ATC instructions, whether due to cloud turbulence or due to communication problems.[9][18][19]

The commission determined that the accident had been the fault of the Kazakhstani Il-76 crew, who (according to FDR evidence) had descended from the assigned altitude of 15,000 to 14,500 feet (4,550 to 4,400 m) and subsequently 14,000 feet (4,250 m) and even lower. The report ascribed the cause of this serious breach in operating procedure to the lack of English language skills on the part of the Kazakhstan aircraft pilots; they were relying entirely on Radio Operator Repp for communications with the ATC. As part of this, the report suggested that First Officer Dzhangirov (and possibly Captain Cherepanov) might have misunderstood Dutta's final radio call, and assumed that the Saudi 747's altitude (14,000 feet) was their own assigned altitude.[9] Indian air controllers also complained that the Kazakhstani pilots sometimes confused their calculations because they are accustomed to using metre altitudes and kilometre distances, while most other countries use feet and nautical miles respectively for aerial navigation.[20] Although the crew in this particular collision did not appear to have made a computational error, Kazakhstan Airlines did not have enough foot-marked altimeters for all crewmembers. Repp did not have his own flight instrumentation and had to look over the pilots' shoulders for a reading, which likely limited his own situational awareness.[21]

Kazakh officials found such a misunderstanding implausible, because their records showed Dzhangirov sufficiently fluent to teach English to other Kazakh pilots at the time. Instead, they concluded – from the Kazakhstani plane's misleading flight data records – that the aircraft had descended while their pilots were battling turbulence inside a bank of cumulus clouds.[9][18] Meteorological reports,[21] the affidavits of a Lockheed C-141B Starlifter crew that observed the crash,[17][22] and conclusive analysis by the investigators – showing that the specific flight data record the Kazakh officials focused on proved only that the record was based on faulty recording equipment on the plane[23] – disproved the Kazakh theory that turbulence was to blame.

However, whether or not particular crewmembers fully understood the radio transmissions or were distracted by atmospheric conditions, the five-person crew was sufficiently large that it likely struggled to maintain common situational awareness and coordinate crew actions.

Just a few seconds before impact, Repp had realised that the pilots were flying below the required 15,000 feet and brought it to their attention. Cherepanov gave orders for full throttle, and the plane climbed, only to hit the oncoming Saudi Arabian plane. The tail of the Kazakhstani plane clipped the left wing of the Saudi Arabian jet, severing both parts from their respective planes.

Furthermore, the investigation noted that Indira Gandhi International Airport did not have secondary surveillance radar, which provides extra information, such as the aircraft's identity and altitude, by reading transponder signals; instead the airport had a primary radar, which produces readings of distance and bearing, but not altitude. In addition, departures and arrivals both shared a single corridor within the civilian airspace around New Delhi. While most areas have separate corridors: one for departures and another one for arrivals, the airspace of Delhi in 1996 had only one civilian corridor for both departures and arrivals, because much of the airspace was taken by the Indian Air Force.[17]

Due to the crash, the air-crash investigation report recommended changes to air-traffic procedures and infrastructure in New Delhi's air-space:[9]

  • Separation of inbound and outbound aircraft through the creation of 'air corridors'
  • Installation of a secondary air-traffic control radar for aircraft altitude data
  • Mandatory collision avoidance equipment on commercial aircraft operating in Indian airspace
  • Reduction of the airspace over New Delhi that was formerly under exclusive control of the Indian Air Force

Aftermath

[edit]

The Directorate General of Civil Aviation subsequently made it mandatory for all aircraft flying in and out of India to be equipped with an airborne collision avoidance system. This set a worldwide precedent for mandatory use of traffic collision avoidance system.[24]

As of 2021, there is an ongoing effort by the Charkhi Dadri district administration to develop a memorial honoring the victims of the mid-air collision. The proposed memorial, which would consist of names and other information of the victims, would be located at a to-be built memorial-park in the district. However, the district administration is waiting to get an approval for the project from the Haryana government, and plans to include the participation of Ministry of Civil Aviation of India, Airport Authority of India, and embassies of Saudi Arabia and Kazakhstan in the development of the memorial.[25]

Documentaries

[edit]

Miditech, a company based in Gurugram, Haryana, produced a documentary about the disaster called Head On!, which aired on the National Geographic Channel.[17]

The collision was also the subject of the 2009 episode "Sight Unseen", of the Canadian-made, internationally distributed documentary series Mayday.[23]

See also

[edit]

References

[edit]

Citations

[edit]
  1. ^ Cooper, Kenneth J. (13 November 1996). "At Least 349 Are Killed in Collision". The Washington Post. Archived from the original on 26 June 2013.
  2. ^ Ashraf, Syed Firdaus. "Charkhi Dadri collision report expected this weekend". Rediff. New Delhi. Archived from the original on 10 April 2014.
  3. ^ "India air safety profile". Aviation Safety Network. Retrieved 10 April 2014.
  4. ^ a b c Burns, John F. (13 November 1996). "Two Airliners Collide in Midair, Killing All 351 Aboard in India". The New York Times. Archived from the original on 6 March 2014.
  5. ^ Lahoti 1997, p. VII
  6. ^ Lahoti 1997, p. VII
  7. ^ Lahoti 1997, pp. VIII, XIII
  8. ^ a b Kingsley-Jones, Max; Learmount, David (20 September 1996). "Collision raises doubts on ATC routeings". Flightglobal. Flight International. Archived from the original on 1 January 2015.
  9. ^ a b c d e f g h i j k l m n Lahoti 1997
  10. ^ a b Burns, John F. (14 November 1996). "Indian Officials Gather Evidence on Midair Collision". The New York Times. Archived from the original on 3 January 2015.
  11. ^ a b "Pilot error focus of India collision investigation". New Delhi: CNN. 14 November 1996. Archived from the original on 28 January 2000.
  12. ^ a b Burns, John F. (5 May 1997). "One Jet in Crash Over India Ruled Off Course". The New York Times. Archived from the original on 3 March 2018.
  13. ^ a b Civil aviation aircraft accident summary for the year 1996 (PDF) (Report). Directorate General of Civil Aviation. p. 8/18. Archived from the original (PDF) on 3 January 2015.
  14. ^ Accident description for Kazakhstan Airlines Flight 1907 at the Aviation Safety Network
  15. ^ Job, Macarthur (November–December 2006), "Mid-Air Disasters" (PDF), Flight Safety Australia, p. 42, archived from the original (PDF) on 30 October 2008, retrieved 10 September 2009
  16. ^ Bellamy, Christopher (13 November 1996). "Human error is blamed for crash". The Independent. Archived from the original on 26 February 2014.
  17. ^ a b c d Head On – AirCrash (TV documentary). Miditech. Archived from the original on 23 March 2007.
  18. ^ a b "Kazakh aircraft held responsible for Charkhi Dadri mishap". rediff.com. 1997. Archived from the original on 23 May 2020.
  19. ^ Morris, Hugh (12 July 2017). "The truth behind the 10 deadliest plane crashes of all time". The Daily Telegraph. London. Archived from the original on 23 May 2020.
  20. ^ McGirk, Tim (14 November 1996). "THE INDIAN AIR CRASH: Tapes point blame at Kazakh pilot". The Independent. Archived from the original on 1 May 2019.
  21. ^ a b "Communication gap caused Charkhi Dadri mishap". Rediff. 26 May 1997. Archived from the original on 7 October 1999. Retrieved 4 July 2006.
  22. ^ "Charkhi Dadri collision occurred in "heavy clouds": US pilot". Rediff. Archived from the original on 11 October 1999. Retrieved 4 July 2006.
  23. ^ a b "Sight Unseen". Mayday. Season 7. Episode 4. Montreal: Cineflix. 11 November 2009. Discovery Channel Canada et al.
  24. ^ "History & future of airborne collision avoidance". Eurocontrol. 9 March 2012. Archived from the original on 4 February 2018. Retrieved 6 May 2019.
  25. ^ "Haryana's Charkhi Dadri plans a memorial for 1996 mid-air collision victims". The Times of India. 4 March 2021. Archived from the original on 18 February 2024.

Further reading

[edit]
[edit]
External image
image icon Pre-Crash photos of the two airliners at Airliners.net