1996 Charkhi Dadri mid-air collision
Saudia Boeing 747-168B and Kazakhstan Airlines Ilyushin Il-76TD · Mid-air collision due to pilot error on the Il-76
Event
- NTSB case
- DCA97WA007
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Unknown · led by another country; figures from NTSB notifications
- Event fatalities
- 349 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- 349
- Survivors
- 0
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 0 serious · 0 minor (NTSB)
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Not recorded
Aircraft 1 · Boeing 747-168B
- Flight
- SV763
- Aircraft type
- Boeing 747
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- HZ-AIH
- Operator
- Saudia
- Onboard fatalities
- 312
- Occupants
- 312
- Survivors
- 0
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- None · no survivors
- Route
- From Indira Gandhi International Airport (DEL)To King Abdulaziz International Airport (JED)
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 129: Foreign
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Not recorded
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Not recorded
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Not recorded
Aircraft 2 · Ilyushin Il-76TD
- Flight
- KZ1907
- Aircraft type
- Ilyushin IL-76
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- UN-76435
- Operator
- Kazakhstan Airlines
- Onboard fatalities
- 37
- Occupants
- 37
- Survivors
- 0
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- None · no survivors
- Route
- From Şymkent International Airport, Shymkent, KazakhstanTo Indira Gandhi International Airport (DEL)
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 129: Foreign
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Not recorded
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Not recorded
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Not recorded
Cause areas
- Personnel issues › Task performance
- Personnel issues › Experience/knowledge
- Personnel issues › Miscellaneous
From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.
Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.
From the Wikipedia article
On 12 November 1996, Saudia Flight 763, a Boeing 747-100 en route from Delhi, India, to Jeddah, with a stopover in Dhahran, Saudi Arabia, and Kazakhstan Airlines Flight 1907, an Ilyushin Il-76 en route from Shymkent, Kazakhstan, to Delhi, collided over the city of Charkhi Dadri, around 100 km west of Delhi. The crash killed all 349 people on board both planes, making it the world's deadliest mid-air collision, the deadliest aviation accident without survivors, and the deadliest aviation accident ever in India.
The final report from the investigation revealed that the Kazakh crew's failure to maintain the correct altitude led to the collision. 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. The investigators noted the Indian airport lacked a secondary surveillance radar; the airport only had a primary radar, which produced readings of distance and bearing, but not altitude. The report also suggested technical enhancements (including ACAS and SSR) that would provide assistance in preventing a future crew's mistakes from being allowed to go unchecked in real time.
Accident
Saudia Flight 763 departed Delhi at 18:32 local time (13:02 UTC). Kazakhstan Airlines Flight 1907 was descending simultaneously to land at Delhi. Both flights were controlled by approach controller V.K. Dutta. Immediately after take-off, the Saudia flight was cleared to an initial altitude of 10000 ft. At 18:34, Dutta cleared the Kazakh plane to descend to 15000 ft when it was 74 nmi 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 14000 ft. At 18:38, the Saudia 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."
At 18:39, the Kazakh flight reported having reached its assigned altitude of 15,000 feet, but it was actually higher, at 16,348 ft, and still descending. 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." Radio Operator Repp requested clarification, to which Dutta replied, "Traffic... is at eight miles, level 140." Repp acknowledged the update, and signed off with, "Now looking 1907."
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. 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 No. 1 and No.2 engines 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. The crippled Saudi Boeing immediately lost control and went into a rapidly descending spiral with fire trailing from the wing and the rear fuselage broke into several pieces while the remaining engines also ripped away before the remains of the Saudia flight crashed into the ground at a nearly supersonic speed of 1135 km/h. 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 Saudia Flight 763 and all 37 people on Kazakhstan Airlines Flight 1907 were killed.
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.
The collision took place about 60 mi west of Delhi. 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.
Investigation and cause
Investigation and final report
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. 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.
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 15000 to 14500 ft and subsequently 14000 ft 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. Indian air controllers also complained that the Kazakhstani pilots sometimes confused their calculations because they are accustomed to using Soviet-era metre altitudes and kilometre distances, while most other countries use feet and nautical miles, respectively, for aerial navigation. 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.
Kazakh officials claimed – 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. Meteorological reports, the affidavits of a Lockheed C-141B Starlifter crew that observed the crash, 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 – 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 ft 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 team noted that the 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. Moreover, neither plane was equipped with a traffic collision avoidance system, which would have alerted crew on both flights.
Due to the crash, the air crash investigation report recommended changes to air traffic procedures and infrastructure in New Delhi's airspace:
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
Text from the Wikipedia article “1996 Charkhi Dadri mid-air collision” (revision 1372209642, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
Sources
Wikipedia article: 1996 Charkhi Dadri mid-air collision
- Revision
- 1372209642 · 2026-08-30 · retrieved 2026-09-18
- Wikidata
- Q118373
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA97WA007
- Event ID
- 20020124X00116
- Case number
- DCA97WA007
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Where each value comes from
- Record
- Wikipedia article "1996 Charkhi Dadri mid-air collision" (page 1105754, revision 1372209642); merged with NTSB case DCA97WA007 (events / aircraft)
- Date
- Wikipedia infobox: date
- Place and country
- Wikipedia infobox: site
- Map position
- Wikipedia: Wikipedia article coordinates
- Aircraft, operator and route
- Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record DCA97WA007
- Operation
- airline flight number in the infobox
- Fatalities
- Wikipedia: Wikipedia infobox: total_fatalities
- Ground fatalities
- Wikipedia: not stated in the Wikipedia infobox
- Summary
- Wikipedia infobox: summary
Source notes (2)
- One occurrence in two sources, merged: the Wikipedia article "1996 Charkhi Dadri mid-air collision" and NTSB case DCA97WA007, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
- No bulk values were replaced by the NTSB case API.