logo
Bangkok-bound Air India flight 'held back' at Mumbai airport for over 5 hours

Bangkok-bound Air India flight 'held back' at Mumbai airport for over 5 hours

The Hindua day ago

A Bangkok-bound Air India flight from the city was held back for over five hours on June 25, after some hay was found stuck in one of the aircraft's wings, the airline has said.
This was immediately attended to, and the aircraft was subsequently cleared for operation, Air India said in a statement.
The Tata Group-run airline did not share other key details such as the number of passengers and crew on board, the type of aircraft, the scheduled time of departure and for how long the passengers remained stranded at the Mumbai airport.
However, according to flight tracking website flightradar24.com, the flight AI 2354, operated by an Airbus A320Neo plane, was scheduled to depart from Mumbai at 7:45 a.m. However, it departed after a delay of over five hours— around 1 p.m.
"AI2354 scheduled to operate from Mumbai to Bangkok on 25 June 2025 was held back as some hay was found stuck below the left wing of the operating aircraft," Air India said in a statement on Friday (June 27, 2025).
This was immediately attended to, and the aircraft was subsequently cleared for operation, the airline said, adding that the source of the hay (getting below the wing) could not be identified.
It also said as the flight crew came under the regulatory flight duty time limitations, the flight could not depart immediately.
The service provider handling the aircraft at Mumbai airport has been instructed to investigate the matter, which has been duly reported to the safety regulator, Directorate General of Civil Aviation (DGCA), Air India said in the statement.
The passengers were disembarked and served refreshments, and the flight departed as soon as a fresh set of flight crew reported, the airline added.
The incident came days after the DGCA detected multiple violations related to airlines, airports, aircraft maintenance works, and repeated defects in multiple cases during its surveillance at major airports, an exercise carried out in less than two weeks after the June 12 Air India plane crash in Ahmedabad.
Without disclosing names of the airlines, airports and other entities in relation to the defects, the regulator had on Tuesday said surveillance covered multiple critical areas such as flight operations, airworthiness, ramp safety, Air Traffic Control (ATC), Communication, Navigation and Surveillance (CNS) systems, and pre-flight medical evaluations.
The surveillance was done last week and the DGCA is stepping up efforts to strength the overall safety oversight of the aviation ecosystem.

Orange background

Try Our AI Features

Explore what Daily8 AI can do for you:

Comments

No comments yet...

Related Articles

Mumbai-Bound Ethiopian Airlines Boeing 787 Flight Makes Emergency Landing After Passengers Fall Ill: Report
Mumbai-Bound Ethiopian Airlines Boeing 787 Flight Makes Emergency Landing After Passengers Fall Ill: Report

India.com

time3 hours ago

  • India.com

Mumbai-Bound Ethiopian Airlines Boeing 787 Flight Makes Emergency Landing After Passengers Fall Ill: Report

A Mumbai-bound Ethiopian Airlines flight made an emergency landing in the city at around 1:40 am on Friday, reportedly after seven passengers onboard fell sick. According to a report by The Times of India, the Boeing 787 Dreamliner aircraft experienced a 'depressurisation' issue. Meanwhile, upon landing, the sick were attended by a medical team at the airport. Furthermore, one of the individuals who fell ill required hospitalisation. The issue reportedly started when the aircraft was over the Arabian Sea. Heathrow-Mumbai AI Flight Earlier, on June 23, ANI reported, citing an Air India Spokesperson, that on board flight AI130 from London Heathrow to Mumbai, five passengers and two crew reported feeling dizzy and nauseous during different phases of the flight. The flight had landed safely in Mumbai, where the medical teams provided immediate medical assistance. After landing, two passengers and two cabin crew, who continued to feel sick, were taken to the medical room for further examination and were later discharged. Air India Ahmedabad Crash The issues also come at a time when the nation is reeling from the aftermath of the tragic Air India flight AI171 crash in Ahmedabad shortly after takeoff on June 12. The flight had departed from Ahmedabad at 1:38 pm and had 242 passengers, including crew members, on board. Notably, it was a Boeing 787-8 aircraft. The ill-fated plane crashed into the building of BJ Medical College and resulted in deaths and injuries to individuals who were not onboard. The government and authorities sprang into action. According to a release of the Ministry of Civil Aviation, dated June 26, 2025, both the Cockpit Voice Recorders (CVR) and Flight Data Recorders (FDR) were recovered—one from the rooftop of the building at the crash site and the other from the debris. "Subsequently, the black boxes were brought from Ahmedabad to Delhi by IAF aircraft with full security on 24 June, 2025. The front black box arrived at AAIB Lab, Delhi with the DG, AAIB at 1400 hrs on 24 June, 2025. The rear black box was brought by a second AAIB team and reached AAIB Lab, Delhi at 1715 hrs on 24 June, 2025," the release added.

Survivor's guilt, scorn: How Vishwaskumar Ramesh is dealing with life and loss after Air India crash
Survivor's guilt, scorn: How Vishwaskumar Ramesh is dealing with life and loss after Air India crash

India Today

time5 hours ago

  • India Today

Survivor's guilt, scorn: How Vishwaskumar Ramesh is dealing with life and loss after Air India crash

The gift of life may turn into a curse if you are the only survivor of a plane crash that claimed 271 lives, including 241 co-passengers—one of them your brother. British national of Indian origin Vishwaskumar Ramesh, 40, who miraculously escaped when Air India Flight AI171 plunged into an Ahmedabad medical college compound shortly after take-off on June 12, appears to have battled severe survivor's has been unable to sleep. His survival came at a profound cost—the loss of brother Ajay, 45, who was seated just across the aisle on seat 11J. Ramesh was the occupant of 11A. Besides the heavy burden of survivor's guilt, his ordeal was compounded by a baseless businessman from Leicester, UK, described the crash as a blur of terror. 'Thirty seconds into take-off, there was a loud noise and the plane crashed. It was sudden. When I woke up, I found bodies all around me,' Ramesh has told DD News channel from his hospital seat, it seems, detached during the crash, landing in a narrow gap between buildings where loose soil cushioned the fall, saving him from the fireball that the aircraft turned into. 'The plane broke and my seat came off,' Ramesh told doctors, recounting how he had unbuckled himself and crawled through a shattered fuselage, his left hand burned by flames. The brothers, natives of Diu, were returning to the UK after visiting family in their ancestral village of Bucharwada. Ramesh has returned to his village, where he is refusing to interact with anyone except footage of the air tragedy had captured him stumbling barefoot through the plane's debris, shouting, 'Plane fatyo che! (The plane exploded!)', even as he tried to return to the wreckage to find Ajay, only to be restrained by first guilt, a well-documented psychological phenomenon, likely gripped Ramesh in the days that followed. Clinical studies describe it as a profound sense of remorse or unworthiness experienced by those who survive a tragedy while others, especially loved ones, do survivor's guilt can manifest as intrusive thoughts, depression or a fixation on 'why me?'. Ramesh's repeated statements—'I don't know how I survived' and 'I still can't believe I'm alive'—suggest a struggle to process it all. His proximity to Ajay during the crash likely amplified his sense of responsibility, as if he could have done something to save his public nature of his suffering, amplified by viral videos, may have further complicated his ability to grieve privately, as the world watched his every move. The heart-wrenching visuals of Ramesh, bandaged and limping, carrying Ajay's coffin during the funeral procession in Diu on June 18, underscored his grief. Ramesh broke down multiple times, shouldering his brother's bier alongside their father, Ramesh Bhalia, as the family Ramesh grappled with his loss, a disturbing rumour surfaced on social media. It suggested he had fabricated his presence on the flight. The rumour spread rapidly, fuelled by the sensational nature of the crash and the public's fascination with his survival. The origins of it are unclear, possibly stemming from misinformation or scepticism about how someone could survive such a catastrophic event June 20, actor and singer Suchitra Krishnamoorthi, in her now-deleted post, said: 'So this #vishwaskumarramesh lied about being a passenger on the plane & the only survivor? This is seriously weird. Didn't his family in the UK corroborate his story? What about his brother's funeral that he was seen giving kandha to? Deserve not only some serious punishment but some mental asylum time if this is true, uff.'Within hours, several independent social media influencers and users circulated reels and posts, joining the bandwagon of scepticism against Ramesh, and a rumour that he was arrested by police caught the backlash was also swift. Social media users condemned Krishnamoorthi for her insensitivity, pointing to overwhelming evidence of Ramesh's survival: hospital records, police confirmation, Air India's passenger manifest listing him on seat 11A, and video footage of him emerging from the wreckage. However, videos and posts continue to police commissioner G.S. Malik and Dr Dhaval Gameti, who treated Ramesh at Ahmedabad Civil Hospital, confirmed his identity and injuries, noting he was 'disoriented with multiple injuries' but out of danger. Ramesh's survival was not only verified but celebrated by authorities, with Prime Minister Narendra Modi and home minister Amit Shah visiting him in hospital. And yet, the rumour's brief traction reveals how quickly public perception can shift from empathy to scepticism, particularly in high-profile to India Today Magazine- EndsTune InTrending Reel

Quick action of railway official averts collision of two trains near Kovilpatti
Quick action of railway official averts collision of two trains near Kovilpatti

The Hindu

time7 hours ago

  • The Hindu

Quick action of railway official averts collision of two trains near Kovilpatti

A timely action in split seconds by an alert railway official by shutting down power of overhead equipment prevented a speeding express train from ramming from behind another train moving slowly ahead between Kovilpatti and Kadambur railway stations on Tuesday night. The second train that was cleared for running at 110 kmph stopped just 5 km ahead of the other train on the same track and within same signal block section, railway officials said. Initial reports suggested that bungling in following standard safety procedure in issuing of line clear ticket - mandatory for allowing train to proceed further in the event of signal failure - by Kovilpatti Station Master, had led to the incident. An enquiry by railway officials of various departments is underway into the safety breach. According to railway sources, the loco pilot of Train No 06322 Dindigul-Nagercoil special train had noticed at 6.42 p.m. on Tuesday (July 24, 2025) that the intermediate block signal at Kumarapuram between Kovilpatti and Kadambur railway stations had failed. He had tried to reach the station master of Kovilpatti through the signal post (railway) telephone. However, he could not communicate with him. Loco pilot followed safety protocol Hence, following the safety protocol during signal failures in mid-section, the loco pilot waited for more than the mandatory five minutes and then set out the train at 7.02 p.m. 'He operated the train at 8 kmph speed, which is stipulated speed at nights on a track with failed signal. At this speed, he would be able to stop the train immediately in the event of the train facing any unforeseen obstruction on the track,' a railway source said. Meanwhile, Train No. 16368 Varanasi to Kanniyakumari Express had arrived Kovilpatti at 7.06 p.m. Railway sources said that consequent to the IBS failure, the Varanasi express train was allowed to move out of Kovilpatti railway station with a line clear ticket and to proceed towards Kadambur railway station at the usual speed of 110 kmph. The manual go-ahead was given much before the other train could reach Kadambur. 'Station Masters worked on assumption' It seems the Station Masters on both ends were under the assumption that the Nagercoil-bound train was running at the normal sectional speed of 110 kmph and hence they anticipated it to reach Kadambur railway station at any moment, the source said. They had failed to assess the risk factor due to Nagercoil-bound train running at 8 kmph. It would take at least 90 minutes for the train for crossing 12 km from the IBS to reach Kadambur railway station. The line clear ticket is an authority issued by the Station Master, in consultation with the other Station Master of the section, to allow the train to proceed on track during signal failures. 'It also assures the loco pilot that the section ahead is free of any vehicle (train),' the source explained. However, in this case, despite the block section of Kovilpatti-Kadambur was not free of train movement, the second train was allowed to pass through it. Timely intervention Even as the train was fast approaching Kadambur railway station, the section controller at Madurai Divisional Office noticed two trains proceeding in close proximity on the same block section. He immediately alerted the officials in Traction Distribution and asked them to shut down power in the OHE to stop the Varanasi train and thus averted the possible collision of two express trains. The trains were separated by a distance of only five km, an official said. Another official said that the SM, Kovilpatti had asked the loco pilot to watch out whether a level crossing gate near the IBS was in closed position before proceeding further. Even as the loco pilot was about to slow down the train to stop it at the IBS, the power was shut down curtailing its movement. Meanwhile, the signal was set right around 9.20 p.m. Four express trains suffered detention in the range of over one hour to over three hours. Investigation revealed that burning of signal cables had led to the IBS failure.

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