logo
Air India plane crash: Recalling the Charkhi Dadri collision, one of the worst aviation disasters in history

Air India plane crash: Recalling the Charkhi Dadri collision, one of the worst aviation disasters in history

Indian Express5 days ago

A London-bound Air India Boeing 787 Dreamliner crashed into a residential neighbourhood in Ahmedabad last week, killing at least 249 people.
The aviation disaster — one of the worst in decades — came 29 years after the Charkhi Dadri mid-air collision of Saudia Flight 763 which was going from Delhi to Saudi Arabia's Dhahran, and Kazakh Flight 1907 which was travelling from Kazakhstan's Chimkent (now Shymkent) to Delhi. The accident led to the death of all 349 people on board both planes.
Here is a look at what led to the Charkhi Dadri accident, which is considered the deadliest mid-air collision in aviation history of the world.
The incident
On November 12, 1996, around 6.40 pm, the Saudia Flight 763 took off from Delhi to Dhahran, carrying many Indian workers to their jobs in the Middle East and with Captain Khalid al-Shubaily in the cockpit.
Around the same time, Kazakh Flight 1907, which had Captain Alexander Cherepanov in the cockpit, was about to land in Delhi.
Suddenly, as the narrator in the popular air crash documentary show, Mayday (Air Crash Investigations), puts it, 'the early evening sky ignites into a fireball… flaming wreckage falls from the sky'.
Tim Place, the pilot of a United States Air Force cargo plane, in the vicinity, first witnessed the incident. 'This cloud just lit up… felt like you could feel the heat,' he said. All three planes were in contact with air traffic controller V K Dutta.
The massive jets plunged into the mustard fields below, in two wreckage fields seven kilometres apart, in Charkhi Dadri, around 120 km away from Delhi.
The cause of the crash
Kazakh Flight 1907 was flying at 23,000 ft, about 74 nautical miles from Delhi airport when its crew first contacted Dutta. He cleared the flight to descend and maintain 15,000 ft, according to a recent report by The Indian Express. Saudi Flight 763 was first cleared to fly at 10,000 ft and then at 14,000 ft. Dutta instructed the crew to maintain 14,000 ft and stand by for permission to climb higher.
This was done to ensure a mandatory 1,000-ft separation between the jets when they crossed paths. Working with only a primary radar, the only one available around that time, Dutta depended on the pilots of the Kazakh 1907 and Saudi 763 to know their altitudes. Both crews acknowledged Dutta's instructions to maintain 15,000 ft and 14,000 ft, respectively. 'Saudi seven six three (will) maintain one four zero (14,000 ft),' the Saudi crew acknowledged. This was their last transmission to the ATC.
Following the crash, the government set up a Court of Inquiry. The investigation did not find any fault with Dutta and said he had given correct instructions to both flight crew. It held that the mid-air collision happened because the Kazakh pilots did not maintain their assigned altitude of 15,000 ft and descended to 14,000 ft, according to The Indian Express report.
Another possible reason for the Kazakh jet deviating from its assigned altitude, investigators felt, could be the pilot's poor proficiency in English, who may have misunderstood the altitude assigned to the Saudi jet as his own.
The accident led to several corrective steps, including equipping major airports with SSRs (Secondary Surveillance Radar) and separate air corridors for arriving and departing aircraft besides the installation of a Traffic Alert and Collision Avoidance System (TCAS) in the aircraft. India has not witnessed any mid-air collision ever since.

Orange background

Try Our AI Features

Explore what Daily8 AI can do for you:

Comments

No comments yet...

Related Articles

Teary eyes bid farewell to Air India crew member Deepak Pathak who died in Ahmedabad crash
Teary eyes bid farewell to Air India crew member Deepak Pathak who died in Ahmedabad crash

Hindustan Times

timean hour ago

  • Hindustan Times

Teary eyes bid farewell to Air India crew member Deepak Pathak who died in Ahmedabad crash

Emotional scenes unfolded at the funeral of Air India crew member Deepak Pathak whose mortal remains were consigned to flames at a Badlapur crematorium in the presence of thousands of mourners on Saturday. The London-bound Air India flight AI-171 carrying 242 passengers and crew members crashed in Ahmedabad last Thursday.(PTI) Pathak (34), who had been serving the national carrier for the past 11 years, was among the crew members aboard the ill-fated London-bound flight which crashed in Ahmedabad on June 12. His body was handed over to his family members after a nine-day-long identification process, confirmed through DNA testing. Tears flowed freely as the coffin arrived at his residence in Rawal Complex on Ambernath-Badlapur Road. Many struggled to hold back emotions, with heartfelt scenes unfolding among the grieving crowd. Pathak's large portrait accompanied the coffin, standing as a silent tribute as mourners offered floral respects. The funeral procession witnessed an overwhelming turnout. Family, friends, neighbours, and people from all walks of life walked behind the flower-bedecked truck carrying Pathak's coffin to the Manjarli crematorium. Pathak's family members had recalled that he had shared his photos on social media just before the flight took off from the Ahmedabad international airport. "He called our mother that morning and just said 'good morning'. That was the last time we heard his voice," his sister had said. "We couldn't speak often because of our schedules, but my mother and I would always talk about him". Pathak was the third of five siblings and had married four years ago. He is survived by his elderly parents, wife, and two married sisters. In the last few days, the last rites of Captain Sumeet Sabharwal, pilot in command of the Air India plane, cabin supervisor Shradha Dhavan, senior crew member Aparna Mahadik, and crew member Maithili Patil- all from Maharashtra- were conducted in their respective hometowns. The mortal remains of Capt Sabharwal, Dhavan, and Mahadik were cremated at crematoriums in suburban Chakala, Mulund, and Goregaon in Mumbai, respectively. Maithili Patil's last rites were performed in Raigad district. The London-bound Air India flight AI-171 carrying 242 passengers and crew members crashed in Ahmedabad last Thursday, killing all but one on board, and 29 on the ground as the aircraft smashed into a medical complex.

IndiGo Flight Declared 'Mayday' Due To Low Fuel, Landed Safely: Sources
IndiGo Flight Declared 'Mayday' Due To Low Fuel, Landed Safely: Sources

NDTV

timean hour ago

  • NDTV

IndiGo Flight Declared 'Mayday' Due To Low Fuel, Landed Safely: Sources

Budget carrier IndiGo's Guwahati-Chennai flight, with 168 passengers, made an emergency landing in Bengaluru after pilots declared 'mayday' due to "insufficient fuel", said sources. The incident comes just a week after Air India Dreamliner flight to London crashed shortly after take-off in Ahmedabad. The incident took place on Thursday and both pilots have been derostered. The Air India Boeing 787-8 Dreamliner issued a mayday call shortly before it crashed around lunchtime on June 12, bursting into a fireball as it hit residential buildings. The IndiGo plane, which was critically low on fuel, made a safe landing in Bengaluru. "After getting the distress call, the ATC (Air Traffic Control) alerted the on-ground staff members who swung into action. Medical and fire services personnel were in place. The aircraft landed safely at 8:20 pm," the Times of India reported, quoting sources at the Kempegowda International Airport. On Friday, a Madurai-bound Indigo flight suffered a technical snag mid-air and sought permission to fly back to Chennai and land, sources said. The plane, carrying about 68 passengers, landed safely and all the passengers were deplaned with due safety measures in place, sources added.

Flying Beast freezes as he simulates Air India Flight 171 crash: ‘All you can do is watch the ground come at you'
Flying Beast freezes as he simulates Air India Flight 171 crash: ‘All you can do is watch the ground come at you'

Indian Express

timean hour ago

  • Indian Express

Flying Beast freezes as he simulates Air India Flight 171 crash: ‘All you can do is watch the ground come at you'

YouTuber Gaurav Taneja, aka Flying Beast, suggested that overloading might be one of the reasons behind the recent Air India Flight 171 crash in Ahmedabad, which claimed the lives of 270 people. In a new video posted on his YouTube channel, which has nearly 10 million subscribers, he simulated the crash under different settings, and debunked several theories around it. At first, he had suggested that a dual engine failure could be the only reason behind a Boeing 787 Dreamliner crashing in the manner that Flight 171 did. In the new video, he seemed to point in the direction of pilot error, combined with several other issues. Carrying out further analysis of the dual engine failure theory, he conducted a simulation. 'I was fixated on this reason until today evening. In the sim, everything was falling into place. After takeoff, we killed both engines at 100 feet,' he said, adding that he made the aircraft 'a little heavy'. He said, 'Usually, this aircraft is 62 tonnes, but considering that it was a long flight to London, I've made it 70 tonnes.' After conducting the first simulation, he said, 'It was scary. I froze. There was nothing that you could do. What could you do? All you can do is pray and watch the ground come at you.' Also read – Gaurav Taneja, aka Flying Beast, reveals 'every flight has snags' but airlines have 'habit' of ignoring safety issues Citing the video of the crash, he said that the aircraft's nose seemed to tilt up in the moments ahead of the crash, which suggests that the pilot made a last-ditch effort to pull up. 'It's very scary. You have 10 seconds, basically. You can do nothing. You pull the nose up to avoid a heavy impact, and perhaps save a few lives on the ground. It fell like a rock on the ground,' he said. He conducted another simulation with an even heavier aircraft, and discovered that, like Flight 171, it didn't take off at the normal stage. 'I was terrified, I could see the runway about to end. 'Because of the late liftoff, the pilots' were too distracted to pull the landing gear up,' he speculated. In the same video, Taneja suggested that the pilots aboard the aircraft might've been startled when the first engine failed during takeoff, and were left with no choice but to proceed because the engine failure happened after the point of no return on the runway. Once the aircraft was airborne, they mistakenly killed the second engine, and forgot to pull the landing gear up. Previously, Taneja had defended the pilots against any criticism, saying that they are the easiest people to blame in such events, because they aren't around to defend themselves. He has also said that both engines of a Boeing 787 failing is practically unheard of. He said, 'They were distracted. They were supposed to pull up the landing gear at around 100 feet. Now, listen carefully. They climbed for 100-150 feet with a damaged engine, and forgot to pull the landing gear up. In the Boeing 787, pilots are required to follow 'memory items' in the event of an engine failure. When they hit 400 feet, the pilot 'flying' pulled the thrust idle switch for the faulty engine, and the pilot 'monitoring' pulled the fuel control switch off for the wrong engine… One engine was damaged on the ground, the other engine they killed themselves.' In the wake of several flight cancellations following the Flight 171 disaster on June 12, Taneja praised pilots for putting their foot down and refusing to fly potentially unsafe machines. On Saturday, the Directorate General of Civil Aviation (DGCA) ordered immediate action against three senior Air India officials following 'serious and repeated violations,' the Hindustan Times reported.

DOWNLOAD THE APP

Get Started Now: Download the App

Ready to dive into a world of global content with local flavor? Download Daily8 app today from your preferred app store and start exploring.
app-storeplay-store