Air India flight to Mumbai: Mid-air hijack alert triggers security protocol

Photo: Instagram/@airindia

On Monday at 8:40 pm, Air India flight AI 2957, heading to Mumbai from New Delhi’s Indira Gandhi airport, sent an emergency signal to the air traffic control (ATC) in Delhi, suggesting that the plane had been hijacked.

Once the ATC received the alert, they immediately followed the emergency protocol. This meant informing the destination airport (Mumbai), security agencies, and the Indian Air Force. A central committee was formed, including representatives from the Delhi police, the Central Industrial Security Force (CISF), which is responsible for airport security, the Airports Authority of India (AAI), the Bureau of Civil Aviation Security (BCAS), and the Air Force.

Even though the pilot soon told the ATC that it was a false alarm, the protocol remained in place. A former ATC official explained that the ATC couldn’t just trust the pilot's words because it was possible that the pilot could have been under pressure. “What if the pilot was being forced to say everything was normal, maybe even at gunpoint?” the official asked.

The flight, carrying 126 passengers, landed safely in Mumbai at 9:47 pm, where the authorities were ready for the situation. At 9:30 pm, an emergency was declared at Mumbai airport. The airport formed a special aerodrome committee, and police and other security agencies, including the National Security Guard (NSG), were placed on alert.

When the flight landed, it was taken to an isolated area at the airport. Passengers were not allowed to get off until about an hour later when the authorities were sure everything was fine.
The situation started when the plane’s transponder sent a “squawk 7500” signal to the Delhi ATC just after takeoff. This signal stayed active for about three minutes. Squawk codes are four-digit numbers that air traffic controllers use to identify aircraft. There are specific codes for emergencies, like Squawk 7500, which signals a hijacking. The other emergency codes are 7600 for radio communication failure and 7700 for any general aircraft emergency.

Ministry officials said the airline had reported the issue, and the Directorate General of Civil Aviation (DGCA), along with BCAS and CISF, started an investigation. They want to understand why the hijack signal was sent. It could have been a mistake by the pilot or the air traffic controller, but only after the investigation will the exact cause be known.

An Air India spokesperson could not be reached for comment. However, an airline official familiar with the incident stated that there was no sign of any crew involvement in the false alarm. It could have been a technical issue, and everything would be clearer once the DGCA finishes its inquiry.

The pilot told the ATC shortly after takeoff that there was no hijacking, and the flight was normal. Despite this, all the necessary emergency steps were followed by authorities to be prepared for any situation. After landing, the pilot assured the airport officials that it was just a regular flight and not a hijacking.

#trending #latest #AirIndia #MumbaiFlight #HijackAlert #EmergencyProtocol #ATC #FalseAlarm #AviationNews #MumbaiAirport #IndianAirForce #AirIndiaAI2957 #SecurityResponse #AviationSafety #FlightEmergency #AirTrafficControl #SquawkCode #HijackAlert #DGCA #CISF #AirportSecurity #AviationInvestigation #Mumbai #breakingnews #trendingnews #DXBIndiaNews #BreakingNewsIndia #IndiaUpdates #GlobalIndiaNews #TrendingInIndia #DXBTrending #IndiaHeadlines #TopStoriesIndia #MiddleEastMeetsIndia #ViralIndiaNews #SouthAsiaNews #AllIndianews #breakingsportsnews #breakingPoliticalnews #breakingFinancenews #breakingregionalnews #Entertainmentnews #Educationnews #technologynews #DXBIndia

Simple yoga poses to help reduce PCOD symptoms and balance hormones... Read More.

RPSC has released the RAS Preliminary Exam 2024 admit cards today, January 30, 2025.... Read More.