Air India jet skids during landing in Mumbai, damaging aircraft and runway
All passengers and crew members have since disembarked, Air India said, without saying whether anyone was injured. Air India flight AI2744 had flown from Kochi in southern Kerala state to Mumbai.
The Mumbai airport said in a statement there were 'minor damages reported to the airport's primary runway' due to what it described as a 'runway excursion', and a secondary runway had been activated to ensure operational continuity.
The aircraft has been grounded for checks, Air India added.
A Times of India report, citing sources, said three tyres had burst on the aircraft after the landing. TV footage from NDTV and India Today showed the outer casing of the engine damaged, with some apparent cracks.
Air India has come under intense scrutiny after a Boeing 787 Dreamliner crashed in the Indian city of Ahmedabad last month, killing 260 people.
The European Union Aviation Safety Agency said earlier this month it plans to investigate its budget airline, Air India Express, after Reuters reported the carrier did not follow a directive to change engine parts of an Airbus A320 in a timely manner and falsified records to show compliance.
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Saudi Gazette
3 days ago
- Saudi Gazette
Voices in the cockpit fuelling controversy over Air India crash
DELHI — When the preliminary report into the crash of Air India Flight 171, which killed 260 people in June, was released, many hoped it would bring some measure of closure. Instead, the 15-page report added fuel to a firestorm of speculation. For, despite the measured tone of the report, one detail continues to haunt investigators, aviation analysts and the public alike. Seconds after take-off, both fuel-control switches on the 12-year-old Boeing 787 abruptly moved to "cut-off", cutting fuel to the engines and causing total power loss - a step normally done only after landing. The cockpit voice recording captures one pilot asking the other why he "did the cut-off", to which the person replies that he didn't. The recording doesn't clarify who said what. At the time of take-off, the co-pilot was flying the aircraft while the captain was monitoring. The switches were returned to their normal inflight position, triggering automatic engine relight. At the time of the crash, one engine was regaining thrust while the other had relit but had not yet recovered power. The plane was airborne for less than a minute before crashing into a neighbourhood in the western Indian city of Ahmedabad. Several speculative theories have emerged since the preliminary report - a full report is expected in a year or so. The Wall Street Journal and Reuters news agency have reported that "new details in the probe of last month's Air India crash are shifting the focus to the senior pilot in the cockpit". Italian newspaper Corriere della Sera claimed that its sources had told them the first officer repeatedly asked the captain why he "shut off the engines". Sumeet Sabharwal, 56, was the captain on the flight, while Clive Kunder, 32, was the co-pilot who was flying the plane. Together, the two pilots had more than 19,000 hours of flight experience - nearly half of it on the Boeing 787. Both had passed all pre-flight health checks before the crash. Understandably, the wave of speculative leaks has rattled investigators and angered Indian pilots. Last week, India's Aircraft Accident Investigation Bureau (AAIB), the lead investigator, stated in a release that "certain sections of the international media are repeatedly attempting to draw conclusions through selective and unverified reporting". It described these "actions [as] irresponsible, especially while the investigation remains ongoing". Jennifer Homendy, chairwoman of the US's National Transportation Safety Board (NTSB), which is assisting the investigation, said on X that the media reports were "premature and speculative" and that 'investigations of this magnitude take time". Back in India, the Indian Commercial Pilots' Association condemned the rush to blame the crew as "reckless" and "deeply insensitive", urging restraint until the final report is out. Sam Thomas, head of the Airline Pilots' Association of India (ALPA India), told the BBC that "speculation has triumphed over transparency", emphasising the need to review the aircraft's maintenance history and documentation alongside the cockpit voice recorder data. At the heart of the controversy is the brief cockpit recording in the report - the full transcript, expected in the final report, should shed clearer light on what truly happened. A Canada-based air accident investigator, who preferred to remain unnamed, said that the excerpt of the conversation in the report presents several possibilities. For example, "if pilot 'B' was the one who operated the switches - and did so unwittingly or unconsciously - it's understandable that they would later deny having done it," the investigator said. "But if pilot 'A' operated the switches deliberately and with intent, he may have posed the question knowing full well that the cockpit voice recorder would be scrutinised, and with the aim of deflecting attention and avoiding identification as the one responsible. "Even if the AAIB is eventually able to determine who said what, that doesn't decisively answer the question 'Who turned the fuel off?'". "We may even never know the answer to that question." Investigators told the BBC that while there appeared to be strong evidence the fuel switches were manually turned off, it's still important to keep "an open mind". A glitch in the plane's Full Authority Digital Engine Control (FADEC) system, which monitors engine health and performance, could, in theory, trigger an automatic shutdown if it receives false signals from sensors, some pilots suggest. However, if the pilot's exclamation — 'why did you cut-off [the fuel]?' — came after the switches moved to cut-off (as noted in the preliminary report), it would undermine that theory. The final report will likely include time-stamped dialogue and a detailed analysis of engine data to clarify this. Speculation has been fuelled less by who said what, and more by what wasn't said. The preliminary report withheld the full cockpit voice recorder (CVR) transcript, revealing only a single, telling line from the final moments. This selective disclosure has raised questions: was the investigation team confident about the speakers' identities but chose to withhold the rest out of sensitivity? Or are they still uncertain whose voices they were hearing and needed more time to fully investigate the matter before publishing any conclusions? Peter Goelz, former NTSB managing director, says the AAIB should release a voice recorder transcript with pilot voices identified. "If any malfunctions began during take-off, they would be recorded in the Flight Data Recorder (FDR) and would likely have triggered alerts in the flight management system - alerts the crew would almost certainly have noticed and, more importantly, discussed." Investigators are urging restraint in drawing conclusions. "We have to be cautious because it's easy to assume that if the switches were turned off, it must mean intentional action - pilot error, suicide, or something else. And that's a dangerous path to go down with the limited information we have," Shawn Pruchnicki, a former airline accident investigator and aviation expert at Ohio State University, told the BBC. At the same time, alternative theories continue to circulate. Indian newspapers including the Indian Express flagged a possible electrical fire in the tail as a key focus. But the preliminary report makes clear: the engines shut down because both fuel switches were moved to cut-off - a fact backed by recorder data. If a tail fire occurred, it likely happened post-impact, triggered by spilled fuel or damaged batteries, an independent investigator said. Last week, AAIB chief GVG Yugandhar stressed that the preliminary report aims to "provide information about 'WHAT' happened". "It's too early for definite conclusions," he said, emphasising the investigation is ongoing and the final report will identify "root causes and recommendations". He also pledged to share updates on "technical or public interest matters" as they arise. Summing up, Pruchnicki said the probe "boils down to two possibilities — either deliberate action or confusion, or an automation-related issue". "The report doesn't rush to blame human error or intent; there's no proof it was done intentionally," he added. In other words, no smoking gun - just an uneasy wait for answers that may never even fully emerge. — BBC
Al Arabiya
4 days ago
- Al Arabiya
Death toll rises to 27 in Bangladesh air force jet crash: Official
At least 27 people were killed after a Bangladesh Air Force training jet crashed into a college and school campus in Dhaka, officials said on Tuesday, with 88 people, including children, being treated in hospital. The F-7 BGI aircraft crashed shortly after taking off at 1:06 p.m. (0706 GMT) on Monday from the Kurmitola airbase in the capital during a routine training mission. The military said the plane suffered a mechanical failure. Sayedur Rahman, special assistant to the chief adviser on health, told reporters that 27 people had died and 88 others were hospitalized with burn injuries. The government declared a day of mourning, with flags at half-mast and special prayers held at places of worship. The pilot was among those killed, and the military said a committee has been formed to investigate the crash. The F-7 BGI is the final and most advanced variant in China's Chengdu J-7/F-7 aircraft family. Bangladesh signed a contract for 16 of the aircraft in 2011, with deliveries completed by 2013. The crash comes just weeks after an Air India plane collided with a medical college hostel in Ahmedabad, India, killing 241 of the 242 people on board and 19 on the ground in what was the world's worst aviation disaster in a decade.
Al Arabiya
4 days ago
- Al Arabiya
US authorities probing airliner's close call with B-52 bomber
US aviation regulators said Monday they are investigating a recent close call in which a passenger plane took emergency action to avoid a mid-air collision with a US military bomber. A Delta flight operated by SkyWest took off Friday from Minneapolis and was approaching the city of Minot, North Dakota, when the pilot rapidly rerouted after seeing another aircraft approaching from the right. 'I don't know how fast they were going, but they were a lot faster than us. I felt it was the safest thing to do to turn behind it,' the pilot told passengers, according to recorded audio. 'Sorry about the aggressive maneuver,' he added. 'This is not normal at all.' The Federal Aviation Administration said in a statement that US officials are 'investigating the event involving SkyWest Airlines Flight 3788 at Minot International Airport on Friday, July 18.' SkyWest said it has also launched a probe. The flight had been cleared for approach by the control tower 'but performed a go-around when another aircraft became visible in their flight path,' the airline said in a statement reported by US media. The nearby US Air Force base confirmed in a statement that a B-52 bomber had performed an approved flyover Friday night at the North Dakota State Fair and said the crew was communicating with air traffic controllers at Minot's commercial airport. 'The B-52 crew contacted Minot International Airport tower and the tower provided instructions to continue two miles westbound after the flyover. The tower did not advise of the inbound commercial aircraft,' the Air Force said. It offered no further details about the near miss. Minot, about 50 miles from the Canadian border, is home to both a commercial airport and a US Air Force base. In a passenger video posted to Instagram and verified by Storyful, the SkyWest pilot told passengers he was not informed of the B-52's presence. He said the Minot tower, which does not use radar—a common situation at smaller US airfields—gave him conflicting instructions that could have put the aircraft in danger. 'He said 'Turn right.' I said there's an airplane over there. And he says 'Turn left,'' the pilot said. 'I don't know why they didn't give us a heads-up because the Air Force base does have radar and nobody said, 'Hey, there's also a B-52 in the pattern.'' The passenger who filmed the video, Monica Green, said she was 'sick to my stomach' about the near collision. Green, quoted by NBC News, said she felt the jet veer sharply. 'I just remember the plane going, like, sideways… and just looking straight out the window and just seeing grass,' she said, describing a moment with no visible skyline. The incident comes less than six months after a US Army helicopter collided with an American Airlines jet near Washington's Reagan National Airport, killing all 67 people aboard both aircraft. That disaster prompted federal authorities and Congress to review protocols governing coordination between military and civilian aircraft in shared airspace.
