ATC Communication

The Deadliest Mid-Air Collision Was a Language Failure

The deadliest mid-air collision in history turned on a language failure. What the 1996 Charkhi Dadri disaster teaches pilots preparing for the ICAO test.

A
AviLingo Team
June 4, 202610 min read

The Deadliest Mid-Air Collision Was a Language Failure

Just before sunset on 12 November 1996, a Saudia Boeing 747 climbed out of Delhi on the same narrow airway that a Kazakhstan Airlines Ilyushin Il-76 was descending toward the city on — head to head, separated only by a thousand feet of altitude that one of them was supposed to hold. They did not hold it. The two aircraft met in cloud over the farming village of Charkhi Dadri, and all 349 people aboard died. It remains the deadliest mid-air collision in aviation history.

The official Court of Inquiry put the mechanical cause plainly: the Il-76 descended below its assigned altitude and flew into the 747's level. But running underneath that altitude bust was a communication failure — a cockpit that relayed English through a third man, a traffic warning that went unanswered, and a position report that did not match where the aircraft actually was. That thread is why this accident helped create the ICAO language test pilots sit today.

For anyone preparing for the ICAO Language Proficiency Test (LPT), Charkhi Dadri is not a history lesson. It is a description of exactly what the test is trying to measure — and what happens when the measurement isn't there.

What happened over Charkhi Dadri

Both aircraft were under one approach controller working a single bidirectional airway into and out of Delhi. The Saudia flight, SVA763, a Boeing 747 bound for Dhahran with 312 aboard, had levelled at 14,000 feet and was told to hold there. The Kazakhstan flight, KZA1907, an Il-76 charter inbound from Shymkent with 37 aboard, was cleared to descend to 15,000 feet — a thousand feet of vertical separation above the 747, exactly as the system is designed to provide.

The Il-76 reported reaching 15,000 feet. According to the flight-data evidence later examined by the inquiry, it had not — it was still higher and still descending, and it kept descending: through 15,000, down toward 14,500, and lower, into the altitude the 747 was holding. The controller, seeing the conflict on radar, called the converging traffic and the closing range. The crew queried him once, then went quiet. Seconds before impact the Il-76's radio operator realised they were far below their assigned level and called for a climb. The aircraft pitched up — straight into the descending path it should never have entered. The Il-76's tail struck the 747's left wing. Neither crew transmitted a distress call.

The crash was investigated by the Lahoti Commission, the Indian Court of Inquiry led by Justice R.C. Lahoti, with the flight recorders read out in Moscow and at Farnborough in England. Its finding was that the primary cause was the Il-76's failure to maintain its assigned altitude. The reasons behind that failure are where the language story lives.

Where was the language failure?

Two things about the Kazakh cockpit matter here, and both are about communication rather than airmanship.

First, the people flying the aircraft were not the people talking to the controller. The Il-76 carried a dedicated radio operator who handled radiotelephony in English, because the pilots' own English was limited. Every instruction from Delhi therefore passed through a relay: controller → radio operator → pilots. Every layer in a chain like that adds delay and a point where meaning can shift, and it separates the person who hears an instruction from the person whose hands are on the controls. When the controller issued an urgent, non-routine traffic warning in plain language — converging traffic, reciprocal, closing range — there was no guarantee it reached the flying pilots as the alarm it was.

Second, a read-back is not the same as comprehension, and comprehension is not the same as compliance. The Il-76 reported level at 15,000 feet while the aircraft was still descending through that altitude. Whether that was a procedural slip, an altimetry issue, or a gap between what was said on the radio and what the crew understood the aircraft to be doing, the result was the same: the words on the frequency did not match the aeroplane. That mismatch — between transmitted intent and actual state — is precisely the failure mode that direct, fluent, two-way communication exists to catch before it becomes a collision.

It is worth being honest about the limits of the record: the inquiry attributed the accident to the unauthorised descent, and cited possible factors including cloud turbulence as well as communication problems. Language was contributory, not the sole stated cause. But that is the lens this post is written through, because it is the one that turns a tragedy into a lesson a future controller or pilot can actually use — the same lens we apply to the Tenerife disaster and to the read-backs that should have saved Avianca 52.

What ICAO changed because of it

This is the part most retellings miss, and it is the part that matters most to a candidate studying for the LPT.

The Charkhi Dadri investigation did not just close with a finding. India carried it to the 32nd Session of the ICAO Assembly in September 1998, submitting a working paper that pressed ICAO to strengthen the language provisions in Annex 10, Volume II (Aeronautical Telecommunications) and Annex 1 (Personnel Licensing). It was not alone — ICAO's own Manual on the Implementation of ICAO Language Proficiency Requirements (Doc 9835) records that the Assembly acted "taking note of several accidents and incidents where the language proficiency of pilot and air traffic controller were causal or contributory factors," Tenerife and Avianca 52 among them.

That pressure produced Assembly Resolution A32-16, which directed ICAO to treat English language proficiency as a high-priority safety matter. The work fed into the language provisions formally adopted in March 2003 and made applicable on 5 March 2008 — the requirement that flight crews and controllers in international operations demonstrate at least Operational Level 4 on the six-skill ICAO rating scale.

In other words: the test you are preparing for exists, in part, because of what happened over Charkhi Dadri. Studying comprehension and interaction for the LPT is the safety lesson of this accident, written into a licence requirement.

What a pilot or controller preparing for the LPT should take from it

The ICAO scale rates six skills, and your overall level is your lowest score across all of them (see our breakdown of what each ICAO level actually requires). Charkhi Dadri stress-tests three of those six in particular — the ones candidates most often underprepare.

ICAO skillWhat it requiresWhat the accident shows
ComprehensionUnderstanding routine and non-routine exchanges, including unexpected eventsA plain-language traffic warning has to be understood and acted on instantly — there is no time to decode it after the fact
InteractionsResponding immediately and appropriately; checking, confirming, clarifying a misunderstandingThe crew queried once, then went silent; the loop was never closed
FluencyHandling the jump from rehearsed phraseology into spontaneous plain languageStandard read-backs are easy; the emergency lived entirely in unscripted plain English

Three lessons follow directly:

  1. The test is built around the unexpected, on purpose. Many candidates drill standard phraseology until it is flawless and assume that is the exam. It is not. ICAO deliberately assesses how you cope when communication moves off-script — a conflict, a change of plan, a warning you did not expect. That is where Charkhi Dadri was decided, and it is where Level 4 is decided.

  2. Reading back is not understanding. You can return a textbook read-back and still hold a wrong picture of what the aircraft is doing or where the traffic is. The skill ICAO scores is whether your response proves you understood — by confirming, correcting, or asking, not just by repeating.

  3. Comprehension is a skill you train, not a level you're born with. It improves by listening to fast, accented, real radio under pressure until non-routine instructions stop being a surprise. That is exactly what Avilingo's AI ATC trainer is built to rehearse — non-standard situations, urgency calls, and conflict warnings, scored the way a human rater scores them.

Why this one lands especially hard for CIS pilots

The relayed-radio model in the Il-76 was not an oddity; it reflected an era and a system in which a separate operator commonly handled foreign-language R/T while the pilots flew. The whole direction of ICAO's reform since 1998 has been to close that gap — to require that the people controlling the aircraft are themselves the ones who comprehend and communicate, in real time, in English. For pilots and controllers across Russia, Kazakhstan, Ukraine, and the wider CIS, that history is not abstract. The shift from relayed communication to direct, examined English proficiency is the through-line from this accident to your own licence endorsement. Charkhi Dadri is, in a hard sense, the reason the standard now lands on you.

Frequently Asked Questions

What was the cause of the Charkhi Dadri collision?

The Lahoti Commission found the primary cause to be the Kazakhstan Il-76's descent below its assigned altitude of 15,000 feet into the path of the Saudia 747, which was holding at 14,000 feet. Contributory factors included communication and comprehension problems in a cockpit that relayed English radiotelephony through a dedicated radio operator.

How many people died at Charkhi Dadri, and why is it significant?

All 349 people aboard both aircraft were killed — 312 on the Saudia 747 and 37 on the Kazakhstan Il-76. It is the deadliest mid-air collision in aviation history and one of the accidents that pushed ICAO to introduce formal English language proficiency requirements.

Did Charkhi Dadri really lead to the ICAO English test?

It was a significant contributing factor. India raised the accident at the 1998 ICAO Assembly, urging stronger language provisions. That Assembly produced Resolution A32-16, which led to the language requirements adopted in 2003 and made applicable on 5 March 2008 — the Operational Level 4 standard pilots and controllers must meet today.

How would direct English proficiency have changed that night?

No one can rewrite an accident, but the relevant point is structural: the LPT requires the flying crew themselves to comprehend and respond to non-routine plain-language communication in real time — including an urgent traffic warning — without a relay between the controller and the controls. Removing that relay, and proving the crew can act on what they hear, is the exact safety gap the requirement was designed to close.

The takeaway

Charkhi Dadri is usually filed under "altitude bust." Read it as a communication accident and it becomes the clearest possible argument for why the ICAO test focuses on comprehension and interaction rather than perfect grammar. The standard you are studying for was written, in part, in the cotton and mustard fields of Haryana. Train for the unexpected exchange, prove you understood rather than just repeated, and you are practising the lesson this accident left behind.

Topics covered

Charkhi Dadri
Aviation Safety
Radiotelephony
Comprehension
ICAO Language Proficiency
Share this article:

Practice What You've Learned

Apply these concepts with AviLingo's interactive exercises designed for aviation professionals.

Start Free