Air India Ahmedabad plane crash: What we saw at the site in Ahmedabad
On Thursday afternoon, a Boeing 787 aircraft en route from Ahmedabad to London crashed in the BMJ Medical College campus area, just 5 km from the airport. Our reporter brings you live visuals and ground updates from the spot where the tail of the aircraft still lies embedded in a building.
The area has suffered extensive damage — this includes the mess where students were gathered during lunchtime and the postgraduate hostel nearby. The crash has resulted in confirmed casualties among both passengers and local residents, including students and possibly bystanders.
Rescue and recovery efforts continue. The National Disaster Response Force (NDRF), forensic teams, and aviation authorities are on the ground. The focus now shifts to retrieving the black box — both the Cockpit Voice Recorder (CVR) and Digital Flight Data Recorder (DFDR) — to understand what caused the fatal crash.
Presentation: Jagriti Chandra
Production: Aniket Singh Chauhan
Hashtags
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
New Indian Express
a day ago
- New Indian Express
Six aircraft engine shutdown incidents reported this year: Civil Aviation Ministry
NEW DELHI: A total of six aircraft engine shutdown incidents and three incidents of May Day calls have been reported so far this year, according to the civil aviation ministry. As per data shared by Minister of State for Civil Aviation Murlidhar Mohol with the Rajya Sabha, there have been two incidents of engine shutdown, each involving IndiGo and SpiceJet, while Air India and Alliance Air had one such incident each. There have been three incidents of May Day Call, including for the Air India aircraft operating the London Gatwick-bound flight AI 171 that crashed into a building soon after take off from Ahmedabad on June 12. IndiGo and Air India Express also had one incident each of May Day Call. A pilot repeats May Day thrice to clearly communicate with the air traffic controller on the ground that the aircraft is in a life-threatening situation and needs urgent help.
Time of India
2 days ago
- Time of India
Air India apologises, 'deep cleans' after roaches found on flight
. NEW DELHI: Air India has apologised for cockroaches on last Saturday's San Francisco-Mumbai (via Kolkata) flight due to which seats of some flyers had to be changed. The aircraft, a relatively new ex-Delta Boeing 777 (VT-AEH), was "deep cleaned" during its technical halt in Kolkata and the airline will initiate "a comprehensive investigation to determine the source / cause of this incident and implement measures to prevent recurrence. " The aircraft had taken off from San Francisco at 8.28pm (local time) on Aug 2. The cockroach trouble happened as it flew to Kolkata, where it arrived after about 16 hours. "...Two passengers were unfortunately bothered by the presence of a few small cockroaches on board. Our cabin crew, therefore, relocated the two to other seats...," an Air India spokesperson said. "During the flight's scheduled fuel stop in Kolkata, our ground crew promptly conducted a deep cleaning process to address the issue. The same aircraft subsequently departed in time for Mumbai. Despite our regular fumigation efforts, insects can sometimes enter an aircraft during ground operations... We sincerely apologize for any inconvenience caused," the spokesperson added.
New Indian Express
2 days ago
- New Indian Express
Human error, inadequate infra at Goa airport caused Air India plane's aborted take-off: AAIB report
NEW DELHI: Human error and the lack of adequate infrastructure at Goa's Manohar International Airport led to the aborted take-off of an Air India flight to Hyderabad last December, the Aircraft Accident Investigation Bureau (AAIB) has said in its final report on the incident released on Monday. The incident involving Air India flight AIC 2592, carrying 151 passengers and 7 crew members, occurred on the night of December 5, 2024. The flight was stopped mid-roll just as it was accelerating for take-off. The AAIB, which investigated the event under the Aircraft Rules, 2017, has now released its 16-page final report. The Airbus A320 was rolling down the taxiway at 124 knots around 9.17 pm when the Air Traffic Control (ATC) noticed the aircraft was not on the assigned runway. Visibility at the time was 3,000 metres. The flight had mistakenly entered Taxiway 'A' instead of Taxiway 'A5', which had been assigned for take-off on Runway 28. The aircraft was immediately ordered to abort take-off, and the pilots complied. The AAIB classified the incident as a "serious incident." Specifying the probable causes for the incident, the probe report said there was a "Situational Awareness Deficit" on the part of the crew. The take-off clearance given by the ATC likely caused the crew's cognitive focus to shift entirely towards the take-off.
