Why did air traffic control fail to prevent the 1996 Charkhi Dadri collision?
This analysis examines the specific technical and human factors identified in the investigation of the 1996 Charkhi Dadri mid-air collision, focusing on radar limitations and crew communication issues.
Cite this page
“Why did air traffic control fail to prevent the 1996 Charkhi Dadri collision?” thisDay, thisday.info/history/1996-charkhi-dadri-mid-air-collision-1996/. Accessed 12 Nov. 2026.
Why did air traffic control fail to prevent the 1996 Charkhi Dadri collision? (n.d.). thisDay. Retrieved November 12, 2026, from https://thisday.info/history/1996-charkhi-dadri-mid-air-collision-1996/
“Why did air traffic control fail to prevent the 1996 Charkhi Dadri collision?” thisDay. Accessed November 12, 2026. https://thisday.info/history/1996-charkhi-dadri-mid-air-collision-1996/.
Expected vs. Actual Control Capabilities
The investigation highlighted a critical gap between the capabilities expected for safe air traffic management and the actual equipment available at the time of the accident.
| The plan needed | What happened | Why it mattered |
|---|---|---|
| Controllers have real-time altitude data for all aircraft. | Primary radar provided only distance and bearing, lacking altitude readings. | Controllers could not detect the Il-76's altitude deviation until it was too late. |
| Crews accurately interpret and execute ATC instructions. | Il-76 crew had poor English skills, leading to inadequate interpretation of directions. | Miscommunication contributed to the failure to maintain the correct altitude. |
| Crew resource management ensures safety checks are performed. | Three specific incidents of CRM failure occurred in the Kazakh crew. | Internal crew errors went unchecked, allowing the deviation to persist. |
The Infrastructure Gap
The investigation pinpointed a severe technical shortfall at the Indian airport involved in the incident. The facility operated without secondary surveillance radar, a system designed to deliver precise altitude data for aircraft. Consequently, air traffic controllers depended exclusively on primary radar. This equipment generated readings for distance and bearing but failed to provide altitude information. This limitation meant that controllers could track the horizontal position of the aircraft but could not verify their vertical separation in real time. The absence of this data created a blind spot in the air traffic control system.
The report explicitly noted this lack of secondary surveillance radar as a contributing factor to the collision. Without altitude readings, the control tower could not detect when the Kazakhstan Airlines flight deviated from its assigned flight level. The primary radar's inability to provide vertical data meant that the system was fundamentally incapable of alerting controllers to the developing conflict. This technical constraint placed the burden of maintaining safe separation entirely on the pilots, a responsibility that was complicated by other human factors identified in the investigation.
Language and Crew Dynamics
Human factors played a decisive role in the sequence of events leading to the crash. The final report highlighted the poor English language skills of the crew aboard the Ilyushin Il-76. This linguistic barrier resulted in an inadequate interpretation of the directions provided by air traffic control. The crew's inability to fully comprehend or accurately execute the instructions contributed to their failure to maintain the correct altitude. This communication gap was not a minor detail but a central element in the causal chain of the accident.
In addition to language issues, the investigators documented three specific incidents of failures in crew resource management by the Kazakh crew. These CRM failures indicate that the internal processes for checking and verifying flight parameters were not functioning effectively. The combination of external communication difficulties and internal procedural lapses created a situation where the altitude deviation was not corrected. The crew's inability to manage these resources effectively allowed the error to persist until the collision occurred.
The Decisive Moment
The collision itself occurred over the city of Charkhi Dadri in the state of Haryana, approximately 100 kilometers west of Delhi. The two aircraft, a Saudia Boeing 747-168B and a Kazakhstan Airlines Ilyushin Il-76TD, met in the sky near the village of Tikan. The failure of the Flight 1907 crew to maintain the correct altitude was the direct cause of the impact.
The impact was catastrophic, killing all 349 people on board both aircraft. There were no survivors from either plane. The sheer scale of the loss of life established the incident as the world's deadliest mid-air collision. It also became the deadliest aviation accident without survivors and the deadliest aviation accident in the Indian subcontinent. The physical destruction of both aircraft was total, with the wreckage scattered over the area near Tikan village.
Investigative Findings and Recommendations
The final report from the investigation did not stop at identifying the causes but also proposed technical enhancements to prevent future accidents. The investigators suggested the implementation of Automatic Collision Avoidance Systems (ACAS) and Secondary Surveillance Radar (SSR). These technologies were recommended to provide assistance in preventing future crew mistakes from going unchecked in real time. The report emphasized the need for systems that could actively alert pilots and controllers to potential conflicts, compensating for human error and communication barriers.
The recommendations focused on creating a more robust safety net that did not rely solely on pilot vigilance and language proficiency. By introducing ACAS and SSR, the system would gain the ability to detect and alert on altitude conflicts automatically. This approach addressed the specific vulnerabilities identified in the 1996 incident, namely the lack of altitude data and the difficulty in communicating and verifying instructions. The report's suggestions aimed to ensure that similar failures in crew resource management and communication would not result in a fatal outcome in the future.
Timeline: Saudia Flight 763 and Kazakhstan Airlines Flight 1907 collide over Charkhi Dadri
- 1996-11-12 Saudia Flight 763 and Kazakhstan Airlines Flight 1907 collide over Charkhi Dadri.
- 1996-11-13 The New York Times publishes an article on the passenger manifest of Flight 763.
- 1996-11-14 The New York Times publishes a follow-up article with updated passenger manifest details.
- 2021-03-04 Charkhi Dadri district administration announces plans for a memorial-cum-park.
- 1996-11-12 Investigation identifies lack of secondary surveillance radar as a contributing factor.
Related on thisDay
Cite this page
“Why did air traffic control fail to prevent the 1996 Charkhi Dadri collision?” thisDay, thisday.info/history/1996-charkhi-dadri-mid-air-collision-1996/. Accessed 12 Nov. 2026.
Why did air traffic control fail to prevent the 1996 Charkhi Dadri collision? (n.d.). thisDay. Retrieved November 12, 2026, from https://thisday.info/history/1996-charkhi-dadri-mid-air-collision-1996/
“Why did air traffic control fail to prevent the 1996 Charkhi Dadri collision?” thisDay. Accessed November 12, 2026. https://thisday.info/history/1996-charkhi-dadri-mid-air-collision-1996/.