Jump to content

1996 Charkhi Dadri mid-air collision

From Alfawiki
Saudia
IndustryAirline
Headquarters
Jeddah
,
Saudi Arabia
ProductsAir transport services

1996 Mid-Air Collision in India

On 12 November 1996, a catastrophic mid-air collision occurred involving Saudia Flight 763, a Boeing 747 traveling from Delhi, India, to Jeddah, with an intermediate stop at Dhahran, Saudi Arabia, and Kazakhstan Airlines Flight 1907, an Ilyushin Il-76 flying from Chimkent, Kazakhstan, to Delhi. The two aircraft collided above the vicinity of Charkhi Dadri, located approximately 100 km (62 mi; 54 nmi) west of Delhi. Tragically, all 349 individuals aboard both flights perished, marking this incident as the deadliest mid-air collision globally, the most severe aviation disaster with no survivors, and the worst air crash ever recorded in India.

The investigation concluded that the collision resulted primarily from the Kazakh crew's failure to maintain their assigned altitude. Additional contributing factors included the crew’s limited proficiency in English, which impaired effective comprehension of air traffic control instructions, along with three distinct instances of inadequate crew resource management (CRM) by the Kazakh flight team. Furthermore, investigators highlighted that the Indian airport was equipped only with a primary radar, capable of providing distance and bearing data but lacking altitude information due to the absence of a secondary surveillance radar. The final report recommended technical upgrades such as implementing an ACAS and installing a SSR to help prevent similar accidents by enabling real-time detection and correction of crew errors.

Saudia Flight 763

Saudia Flight 763 was operated by a Boeing 747-168B bearing the registration HZ-AIH. It departed from Delhi as part of its scheduled international route connecting Delhi, Dhahran, and Jeddah, carrying 312 passengers and crew.[1] The flight crew comprised Captain Khalid al-Shubaily, aged 45, First Officer Nazir Khan, aged 37, and Flight Engineer Ahmed Edrees, aged 33. Captain al-Shubaily was an experienced pilot with nearly 9,837 hours of flight time.[2]

There are conflicting reports regarding the passengers’ nationalities on Flight 763. One source dated 14 November 1996 states that among those on board were 215 Indian nationals, many employed in Saudi Arabia in blue-collar roles, alongside 40 Nepalis and three Americans.[3] Conversely, another report lists the manifest including 17 individuals from various other countries: nine Nepalis, three Pakistanis, two Americans, one Bangladeshi, one British, and one Saudi.[4] The crew included twelve members, five of whom were anti-terrorism personnel holding Saudi citizenship.[5]

Kazakhstan Airlines Flight 1907

Kazakhstan Airlines Flight 1907 was an Ilyushin Il-76TD aircraft registered as UN-76435 operating a chartered flight from Chimkent Airport to Delhi. The cockpit team consisted of Captain Alexander Robertovich Cherepanov (44 years old), First Officer Ermek Kozhahmetovich Dzhangirov (37), Flight Engineer Alexander Alexanderovich Chuprov (50), Navigator Zhahanbek Duisenovich Aripbaev (51), and Radio Operator Egor Alekseevich Repp (41).[6][2] Captain Cherepanov had accumulated approximately 9,229 hours of flight experience.[7]

The flight was chartered by a company based in Kyrgyzstan, although the flight itself belonged to Kazakhstan. Most passengers were ethnic Russians residing in Kyrgyzstan who intended to shop in India.[4][6][3] Among the passengers were thirteen Kyrgyz traders.[5]

Accident

Saudia Flight 763 took off from Delhi at 18:32 local time (13:02 UTC), while Kazakhstan Airlines Flight 1907 was simultaneously descending to land at the same airport.[1] Both flights were under the supervision of approach controller V.K. Dutta.[2] Shortly after departure, Saudia Flight 763 received clearance to climb to an initial altitude of 10,000 feet (3,050 m). At 18:34, Dutta authorized the Kazakh aircraft to descend to 15,000 feet (4,550 m) when it was approximately 74 nautical miles (137 km) from the destination airport’s beacon. Two minutes later at 18:36, Dutta instructed Saudia Flight 763—traveling along the same airway but in the opposite direction—to ascend to 14,000 feet (4,250 m). At 18:38, the crew of SVA763 confirmed reaching 14,000 feet and requested further climb clearance. Dutta advised them to maintain altitude and stand by; First Officer Khan responded with "Saudi 763 will maintain one four zero."[2]

At 18:39, Kazakhstan Airlines Flight 1907 reported reaching its assigned altitude of 15,000 feet; however, it was actually flying higher at 16,348 feet (5,000 m) and continuing its descent.[8][2] Controller Dutta informed the Kazakh flight: "Identified traffic at twelve o'clock reciprocal, Saudia Boeing 747 ten miles away, likely crossing in five miles. Report if visual."[2] Radio Operator Repp sought clarification and was told: "Traffic is at eight miles, level one four zero."[2] Repp acknowledged this update and ended with "Now looking 1907."[2]

Less than a minute later at approximately 18:40, a United States Air Force cargo aircraft crew radioed that they observed "a big explosion" near their two o'clock position.[2] Attempts by controller Dutta to reach both Saudia and Kazakhstan Airlines flights went unanswered. The two aircraft had collided midair; the Kazakh plane’s left wing severed part of Saudia’s left wing while the Boeing’s left horizontal stabilizer cut through the Kazakh plane’s vertical stabilizer including its horizontal stabilizer.Template:Fix/category[citation needed] The damaged Saudia Boeing lost control immediately and entered a rapidly descending spiral trailing fire from its wing before breaking apart mid-flight and crashing at nearly supersonic velocity of 1,135 km/h (613 kn; 705 mph). The Ilyushin Il-76 lost most of its left wing and vertical stabilizer causing it to enter a flat spin before impacting a field near the Saudia wreckage with a flat attitude. Tragically, all individuals aboard both flights perished—312 on SVA763 and all 37 onboard Flight 1907.[9]

The cockpit voice recorder from the Saudi aircraft captured pilots reciting Islamic prayers including the Istighfar for forgiveness and the Shahada immediately prior to impact.[2]

The collision occurred roughly 100 kilometres (60 mi) west of Delhi.[10] Debris from Saudia Flight 763 was found near Dhani village in Bhiwani District, Haryana, while wreckage from Kazakhstan Airlines Flight 1907 landed near Birohar village in Rohtak District, Haryana.[7]

Investigation and final report

The Lahoti Commission, led by then-Delhi High Court judge Ramesh Chandra Lahoti, conducted the inquiry into the accident. Testimonies were gathered from representatives of the Air Traffic Controllers Guild and the involved airlines. The flight data recorders (FDR) were analyzed by Kazakhstan Airlines and Saudia, supervised by crash investigators based in Moscow and Farnborough, England, respectively. The investigation ultimately attributed the accident to the Kazakhstan Airlines Flight 1907 pilot's failure to adhere to air traffic control (ATC) instructions, potentially caused by cloud turbulence or communication difficulties.

The commission concluded that the Kazakhstani Il-76 crew was responsible for the incident, as FDR data indicated they descended below their assigned altitude of 15,000 to 14,500 feet (4,550 to 4,400 m), then further down to 14,000 feet (4,250 m) and even lower. This significant operational lapse was linked to inadequate English proficiency among the Kazakh pilots, who depended solely on Radio Operator Repp for communication with ATC. The report suggested that First Officer Dzhangirov—and possibly Captain Cherepanov—may have misinterpreted Dutta's last radio transmission, mistakenly believing that the Saudi 747’s altitude of 14,000 feet corresponded to their own clearance. Indian air traffic controllers also noted that Kazakh pilots sometimes experienced confusion due to their routine use of metric units (metres for altitude and kilometres for distance), whereas most other countries employ feet and nautical miles for navigation. Although no computational errors were evident in this collision, Kazakhstan Airlines lacked sufficient altimeters marked in feet for all crew members. Repp did not possess personal flight instruments and had to rely on readings from the pilots' displays, likely restricting his situational awareness.

Kazakh authorities disputed the possibility of miscommunication, citing records that indicated Dzhangirov’s English was proficient enough to instruct other Kazakh pilots at that time. Instead, they argued—based on misleading flight data records from their aircraft—that the plane descended while its crew struggled with turbulence inside a bank of cumulus clouds. However, meteorological evidence, eyewitness accounts from a Lockheed C-141B Starlifter crew who witnessed the collision, and thorough investigator analysis demonstrated that the flight data record in question was unreliable due to faulty onboard equipment, thereby invalidating the turbulence explanation.

Regardless of whether specific crew members fully comprehended radio exchanges or were distracted by weather conditions, the five-person crew size may have contributed to challenges in maintaining shared situational awareness and coordinating actions effectively.

Seconds before impact, Repp recognized that the aircraft was flying below its assigned altitude of 15,000 feet (4,600 m) and alerted the pilots. Captain Cherepanov ordered full throttle as the plane began climbing but unfortunately collided with the approaching Saudi Arabian aircraft. The Kazakh plane’s tail struck the left wing of the Saudi jet, severing both components from their respective aircraft.

The investigation also highlighted deficiencies at Indira Gandhi International Airport, which lacked secondary surveillance radar capable of providing detailed information such as aircraft identity and altitude via transponder signals. Instead, only primary radar was available, offering distance and bearing data but no altitude readings. Additionally, inbound and outbound flights shared a single corridor within New Delhi’s civilian airspace; unlike most regions where separate corridors exist for arrivals and departures, Delhi’s airspace in 1996 had just one corridor because much of it was reserved for Indian Air Force operations. Neither aircraft was equipped with a traffic collision avoidance system, which could have warned both crews of impending danger.

Following this tragedy, the air crash investigation report recommended several improvements to New Delhi’s air traffic management and infrastructure:

  • Establishment of distinct 'air corridors' to separate arriving and departing flights
  • Implementation of secondary radar systems capable of providing altitude information
  • Mandatory installation of collision avoidance technology on commercial aircraft operating within Indian airspace
  • Reduction of Indian Air Force-exclusive control over New Delhi’s airspace to allow better civilian traffic management

Aftermath

Following the incident, the Directorate General of Civil Aviation mandated that every aircraft operating to and from India must be outfitted with an airborne collision avoidance system. This directive established a global benchmark for the compulsory implementation of traffic collision avoidance system technology.

As of As of 2021, the administration in Charkhi Dadri district is actively pursuing the creationTemplate:Update inline of a commemorative monument dedicated to those who lost their lives in the mid-air collision. The envisioned memorial would feature the names and pertinent details of the victims and is planned to be situated within a yet-to-be-constructed memorial park in the district. However, progress hinges on receiving authorization from the Haryana government. The initiative also aims to involve collaboration with the Ministry of Civil Aviation of India, Airport Authority of India, alongside representatives from the Saudi Arabian and Kazakhstani embassies.

Documentaries

The Haryana-based company Miditech, located in Gurugram, produced a documentary titled Head On! which was broadcast on the National Geographic Channel.

Additionally, this tragic event was featured in the 2009 installment "Sight Unseen" from the internationally aired Canadian documentary series Mayday.

Additional resources

  • Lahoti, Ramesh Chandra. Report of Court of Inquiry on Mid-Air Collision Between Saudi Arabian Boeing 747 and Kazakhstan IL-76 on 12th November, 1996 Near Delhi – India (Charkhi-Dadri, Haryana). Directorate General of Civil Aviation, Ministry of Civil Aviation, 15 July 1997. Full report. Archived version available.
  • أنس عبد الحميد القوز. مواقف طيار (كتاب) (A Pilot's Encounters). Obeikan, 2000. A publication by a Saudi aviator detailing this event.
  • Bhavya Dore. "Collision." Fifty Two, 9 October 2020.
  • "Pilot error focus of India collision investigation." CNN, 14 November 1996. Archived article.

External links

Template:External media

Lua error in mw.title.lua at line 359: bad argument #2 to 'title.new' (unrecognized namespace name 'Portal'). Template:Aviation accidents and incidents in India Template:Aviation incidents and accidents in 1996

  1. ↑ 1.0 1.1 Cite error: Invalid <ref> tag; no text was provided for refs named FGlobalATC
  2. ↑ 2.00 2.01 2.02 2.03 2.04 2.05 2.06 2.07 2.08 2.09 Cite error: Invalid <ref> tag; no text was provided for refs named collision report
  3. ↑ 3.0 3.1 Cite error: Invalid <ref> tag; no text was provided for refs named Indian Officials Gather Evidence on Midair Collision
  4. ↑ 4.0 4.1 Cite error: Invalid <ref> tag; no text was provided for refs named Two Airliners Collide in Midair, Killing All 351 Aboard in India
  5. ↑ 5.0 5.1 Cite error: Invalid <ref> tag; no text was provided for refs named Pilot error focus of India collision investigation
  6. ↑ 6.0 6.1 Cite error: Invalid <ref> tag; no text was provided for refs named One Jet in Crash Over India Ruled Off Course
  7. ↑ 7.0 7.1 Cite error: Invalid <ref> tag; no text was provided for refs named Y1996Summary
  8. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named ASN-KZK
  9. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named 4survivors
  10. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named HumanErr