Ahmedabad plane crash live updates: Former Gujarat CM likely on board; Ahmedabad airport closed

By HT News Desk
Published on: June 12, 2025 11:18 AM IST

Ahmedabad plane crash live: As per initial reports, the flight was taking off from Ahmedabad to Gatwick at the time of the crash. Fatalities due to the crash are unknown.​

Ahmedabad: Smoke billows after a plane crashed near Ahmedabad airport,
Ahmedabad plane crash live updates: An Air India plane carrying 242 passengers crashed after takeoff in Gujarat's Ahmedabad airport. Visuals of the plane crash circulated on social media show plumes of dark smoke in the sky. As per an Air India statement, initial reports, the flight was taking off from Ahmedabad to Gatwick at the time of the crash. Fatalities due to the crash are unknown.



Follow all the updates here:
June 12, 2025 11:18 AM IST

Ahmedabad plane crash LIVE: Pilots made MAYDAY call moments before crash​

Air India Crash live: As per a statement from aviation officials, the ATC stated that the Air India plane aircraft departed from Ahmadabad at 1339 IST from runway 23.

“It gave a MAYDAY Call to ATC, but thereafter, no response was given by the aircraft to the calls made by ATC,” said officials.

The plane crashed outside the airport five minutes after takeoff.
June 12, 2025 11:15 AM IST

Air India plane crash LIVE: Civil Aviation minister 'deeply shocked' after plane crash​

Ahmedabad plane crash: Union Civil Aviation minister Ram Mohan Naidu Kinjarapu stated he was "deeply shocked" after the news of the Air India plane crash in Ahmedabad.

"Shocked and devastated to learn about the flight crash in Ahmedabad. We are on highest alert. I am personally monitoring the situation and have directed all aviation and emergency response agencies to take swift and coordinated action," he said on X.

"Rescue teams have been mobilised, and all efforts are being made to ensure medical aid and relief support are being rushed to the site. My thoughts and prayers are with all those on board and their families," he added.

June 12, 2025 11:13 AM IST

Ahmedabad plane crash live news: Former Gujarat CM likely on board, say reports​

Air India plane crash update: Former Gujarat CM Vijay Rupani is suspected to be onboard the Air India plane that crashed near Ahmedabad airport on Thursday, reports TV9. An official confirmation is awaited.

June 12, 2025 11:08 AM IST

Air India plane crash: Video show thick smoke near Ahmedabad Airport​

Moments after an Air India plane carrying 242 passengers crashed, videos showing thick smoke in the air circulated on social media. Residents living near the Ahmedabad airport area captured the visuals of the plane crash.

As per initial statements, the flight en-route to Gatwick crashed five minutes after it took off.

June 12, 2025 11:02 AM IST

Ahmedabad plane crash live news: Passenger plan was en-route to London's Gatwick at time of crash​

Air India plane crash: As per an official statement from Air India, the plane was en-route from Ahmedabad to London's Gatwick at the time of the crash.

The plane took off at 1:38 PM and crashed near the airport five minutes after takeoff.
June 12, 2025 10:56 AM IST

Ahmedabad plane crash live: Ahmedabad Airport closed​

Ahmedabad Airport has been shut down after an Air India passenger plane crashed on Thursday.

June 12, 2025 10:49 AM IST

Ahmedabad plane crash live: Number of fatalities yet to be confirmed​

As per a report by ANI, at least 242 passengers were on board the plane. An official statement is awaited
June 12, 2025 10:47 AM IST

Ahmedabad plane crash live updates: Air India plane crashes in Gujarat​

An Air India passenger plane crashed shortly after taking off at Ahmedabad Airport. As per reports, at least 242 passengers were on board.

https://www.hindustantimes.com/india-news/ahmedabad-plane-crash-live-updates-air-india-flight-crashes-ahmedabad-airport-death-toll-news-101749717953751.html

 

[Flaming Dumpster]

Pilot Flying is always the one controlling the thrust levers,

Literally watch the video I embedded which shows pilot monitoring with her right hand on the thrust levers as she's the captain so it's her call to reject the takeoff.

 

[KiwiFuzz2]

Literally watch the video I embedded which shows pilot monitoring with her right hand on the thrust levers as she's the captain so it's her call to reject the takeoff.

At the same time it was two Asian women pilots, so I'm sure they dented a few other planes on the way out.

 

[Peaches the Wonder Cat]

At the same time it was two Asian women pilots, so I'm sure they dented a few other planes on the way out.

I'm shocked they could see over the cockpit.

 

[Clockwork]

As to how important that sequence is. Doing anything wrong with the throttles from throttle up until a well established climb and gear up ends in catastrophe. I believe there was one crash that was caused by the Captains chair breaking and the seat angle went to flat back, along with the Captain. Pulling the throttles to idle as he fell back.

I was curious about this, so I looked it up. There's a description of the incident here.

It happened back in 2018, and was also an Air India plane. After the chair broke and the Captain inadvertently pulled back on the throttles, they tried to recover but just ran out of runway and only got into the air after a tail strike, and knocked out the ILS localizer and part of the perimeter wall at the end of the runway.

 

[Blewberry Nausea]

back on the throttles, they tried to recover but just ran out of runway and only got into the air after a tail strike, and knocked out the ILS localizer and part of the perimeter wall at the end of the runway.

Also neither pilot noticed the decreased thrust or corrected the problem which caused the strike.

 

[God's drunkest driver]

Complete speculation. What if one of them triggered the switches, then said out loud for the CVR, "why'd you do that?" Then immediately switched them back so that he could try to look like a hero?
After watching Captain Steeeve's last video, he really praised whichever pilot noticed and switched the switches back immediately, emphasizing the quick thinking.
Imagine if you're a pilot who isn't very bright, and you want to save the day from a catastrophic problem because you live in a haze of being raised as a main character, and are entirely over exposed to Bollywood. You want to be a hero. You can't fake a real catastrophic problem well, you're just smart enough to know you can't, but you can make something up about the other pilot causing a catastrophic situation, perfect for you to save the day.
Obviously, this backfired.

It wasn't quick though. If you operate on the assumption that one guy turned them off, the other noticed, said something, then turned them back on, 13 seconds total from last switch off to last switch on is painfully slow. Switch off, one second, switch off, wait 9 seconds while asking why it was done at some point, switch on, wait 4 more seconds, switch on. I'm not a youtube talking head so I don't have to give superfluous praise like captain steve did to avoid getting dogpiled by 100,000,000 indians or cancelled, so I'll say this was demonstrably not quick thinking, the reaction was far too slow and since we don't have CVR audio we don't know if it was too slow because of multiple options:

• it took too long to figure out what was going on (slow thinking)
• it took too long to undo (one pilot struggling to undo what the other did and being fought?)
• it was the action of one person being deliberately slow (he turned them off, waited until he knew the engines were spooled down too much to restart quickly then turned them back on)

It is a bit fishy. If your car dies when you’re merging onto the highway, do you have the presence of mind to look down at the ignition key just in case it’s suddenly off for some reason?

A 787 is a million times more complicated and there’s a dozen more things it “could be” and he just notices those switches are off?

X

The movement of touching the fuel cutoffs is within your peripheral vision unless you're looking away. Depending on the situation, you might hear it too.

 

[Oxyjen]

The movement of touching the fuel cutoffs is within your peripheral vision unless you're looking away. Depending on the situation, you might hear it too.

I’m trying to make sense of the delay before switching them back on.
And the timing of the “why did you cut off” isn’t precisely timestamped as far as I could see. If it was immediate, then I agree it’s likely he noticed the other guy did it.

 

[Overwritten Tapes]

If your car dies when you’re merging onto the highway, do you have the presence of mind to look down at the ignition key just in case it’s suddenly off for some reason?

Unless you have a hybrid or a v12 Mercedes, you can feel the engine being off. Also RPM gauge.

 

[RodgerDodger]

The Flight Safety Detectives have a long talk on the preliminary report this morning. I know a bit long and dry for some. But these are the guys that wrote the book on air crash investigations.

Edit; About 2/3rds in (sorry no timestamp) John Goglia brings up something interesting. Everyone has fallen for the "They turned the engines back on they almost made it!" narrative. He's kind of the subject matter expert on this sort of thing. And he says not only was it not happening. But that the Pajeet Pilots Pajeeted it up. With the incredible size of the 787 Engines they just don't start that easily. They need the APU to be running to start. When the pilot flipped the #1 engine back to run the APU began to spool up. And fuel began flowing into the engine again. But the APU can only put out enough power to start 1 engine at a time. The entire sequence takes 1-2 minutes. And then the pilot flipped #2 to on. Which would have completely fubared up the automated restart logic. The rising temperatures in the #1 Engine indicated fuel was starting to burn again. But they needed a lot more air moving through those massive fans to get them spinning fast enough to light off. The restart in flight needs a few thousand feet of altitude and for you to somewhat dive the plane to get more airspeed.

Basically as soon as something cut those switches they were dead. There was no possible recovery.

 

[DavidS877]

It wasn't quick though. If you operate on the assumption that one guy turned them off, the other noticed, said something, then turned them back on, 13 seconds total from last switch off to last switch on is painfully slow. Switch off, one second, switch off, wait 9 seconds while asking why it was done at some point, switch on, wait 4 more seconds, switch on.

As a general rule nothing happens quickly in something of that size. This will certainly be something they'll test in a simulator. It's not like all thrust goes away immediately, the engines spool down and a plane with that much inertia doesn't come to a sudden stop when then engines quit. So, put them in a sim and see how long to recognize and fix the problem, and then do it again with competent pilots instead of Indians. The other thing is you have to think "maybe there was a good reason" before turning them back on, are we on fire? something else?

 

[Deer Warts]

I picked up somewhere that the captain was heard complaining about his seat. It was speculated that maybe he grabbed on to the fuel switches to pull himself into position. Interesting that seat issues have caused accidents on this very airline in the recent past. Maybe he thought they were firmly locked in place and grabbing them wouldn't hurt anything. Probably not, but anything can happen in a cockpit.

The CVR , full and unedited, is going to be the key to whole thing. If those ten seconds are silent, maybe it's just because they were both shitting their pants and trying to figure out what the hell to do as the ground got closer. If there's noise ... verbal altercation or obvious sounds of a struggle ... that suggests something quite different.

Report is maddeningly vague. Either it's deliberately so to avoid pointing directly at the pilots, or the investigators are well aware that they need more than 30 days to definitively say, "Yeah, one of those guys did it." This whole thing is fascinating, although the obvious, easily disprovable lies in the Indian media are heartbreaking.

Biggest one is that the RAT deployed, presumably in reaction to an engine failure due to mechanical/technical/electrical malfunction, before the switch "transitioned" to OFF. The timestamped FDR readout makes it absolutely clear that this is false. OFF/engine cutoff/RAT/10 seconds/ON is what happened. Not engine cutoff/RAT/OFF/ON. What kills me is the more this is repeated, no matter how clearly the facts show otherwise, the more widely it will be accepted as truth.

The red herrings about the SAIB and "the chip" are further muddying the waters. While I still feel I have to be open to the possibility of a pilot not causing the crash, the intense pushback against that narrative makes it seem more likely to me, not less.

 

[anklyscr]

As a general rule nothing happens quickly in something of that size. This will certainly be something they'll test in a simulator. It's not like all thrust goes away immediately, the engines spool down and a plane with that much inertia doesn't come to a sudden stop when then engines quit. So, put them in a sim and see how long to recognize and fix the problem, and then do it again with competent pilots instead of Indians. The other thing is you have to think "maybe there was a good reason" before turning them back on, are we on fire? something else?

It will though. The instant you remove the fuel from that engine the lp section will start to slow down. Remember it’s sucking up 30 to 40 thousand horsepower worth of energy from the exhaust stream and takeoff is one of the most energy intensive aspects of flight.
The instant that some retard pulled those fuel handles the effective thrust went to zero.

 

[Oxyjen]

Unless you have a hybrid or a v12 Mercedes, you can feel the engine being off. Also RPM gauge.

That’s my point. The engine isn’t making noise, the vehicle is no longer accelerating. All you know is something has gone wrong. Has the throttle cable snapped? The points wire fallen off? The fuel pump quit?

You’re just not going to realize that the “key” is off unless you saw the other guy do it,(and then, why the delay turning it back on) or you wanted to blame him for doing it when you actually did it yourself.

Anyway, doesn’t matter, I’m just pointing out there’s room for ambiguity based on the info we have so far.. For the time being it seems most likely that the captain (who was pilot monitoring) did it, and the pilot flying noticed but for some reason did not act immediately to correct it.

 

[KiwiFuzz2]

So the "bang" noise was just the RAT deploying?

Seems like the report would have said "bang" and then dead silence?

 

[reptile baht spaniard rid]

I was curious about this, so I looked it up. There's a description of the incident here.

It happened back in 2018, and was also an Air India plane. After the chair broke and the Captain inadvertently pulled back on the throttles, they tried to recover but just ran out of runway and only got into the air after a tail strike, and knocked out the ILS localizer and part of the perimeter wall at the end of the runway.

holy fucking shit you niggers need to read this, it's WAY more terrifying than the current story, which may be as simple as "fucking pilot wanted to die" - these fuckers hit the goddamn ILS on takeoff and continued to fly the fucking plane to their destination! It took Air India quite awhile to finally tell them to divert.

Don't fly pajeet air wow

(As an aside the seat is the thing you check four times when flying a small plane, as if that fucker gives, and you don't let go of everything immediately, you're turbofucked, because the natural reaction is to try to pull yourself forward on the yoke like you do on the steering wheel in a car. If I owned my own plane the #1 safety feature I would do is make that damn seat not fucking move at all.)

 

[God's drunkest driver]

As a general rule nothing happens quickly in something of that size. This will certainly be something they'll test in a simulator. It's not like all thrust goes away immediately, the engines spool down and a plane with that much inertia doesn't come to a sudden stop when then engines quit. So, put them in a sim and see how long to recognize and fix the problem, and then do it again with competent pilots instead of Indians. The other thing is you have to think "maybe there was a good reason" before turning them back on, are we on fire? something else?

Overly complex read of the situation imo, see the 3 possibilities I think there are for this slow action in my post. Based on the evidence currently presented to us there wasn't some comprehensive troubleshooting effort or checklist read going on that happened in 9 seconds, either the other pilot immediately knew what happened because he saw/heard the switches being moved and remarked on it before undoing it, or it was a misdirection and the same pilot that turned them off turned them back on after a delay maybe thinking he could fool investigators. My assertion that this was a slow reaction is predicated on the person taking action immediately knowing what happened, which is what the CVR excerpt seems to indicate.

Also, I assume any pilot upon noticing the engine rollback would be able to instantly recognize from the EICAS that it was caused by the fuel cutoff switch since the EICAS message L/R ENG SHUTDOWN indicates fuel control or fire switch activation and is a memory item that even the most jeet type rated individual should know.

 

[DavidS877]

If I owned my own plane the #1 safety feature I would do is make that damn seat not fucking move at all.

That doesn't really work. You may have back seat passengers that need to get in or out. Heck you may need to get in or out and then move the seat forward so you can reach the pedals. Both of these are more common on a high-wing than a low-wing, so I guess you could get an inferior low-wing plane. Much of this has been reduced by Cessna where the problem was common coming out with guidance on maintenance as well as backup latches on newer models. You can also get things that you can screw in once you're seated to back up the standard locks. Hope you don't need to get out in a hurry.

 

[08903248752]

Don't fly pajeet air

If you've made the terrible mistake of flying to India, then your plane crashing on landing and killing you is the most merciful outcome.

 

[BelUwUga]

It wasn't quick though. If you operate on the assumption that one guy turned them off, the other noticed, said something, then turned them back on, 13 seconds total from last switch off to last switch on is painfully slow. Switch off, one second, switch off, wait 9 seconds while asking why it was done at some point, switch on, wait 4 more seconds, switch on.

You're missing the ingrained incompetence of jeets, their inability to acknowledge their mistakes, and the cryptic head bobbing. Example conversation:
1- Why did you cut fuel?
2-
1- Benchod bloody! Is there some issue where we needed to shutoff fuel?!
2-
1- So it's safe to turn it back on? You're breaking the plane Samir!
2-
1- Okay one is back on... I should turn on the second right?
2-

 

[God's drunkest driver]

That head bobbing thing fills me with a primal disgust for some reason.