The recent false hijack alert involving Air India’s long-haul flight from Frankfurt to Delhi has prompted an investigation by aviation and security authorities. On October 14, the Boeing 787-9, carrying approximately 300 passengers, entered Indian airspace via an extended route due to the closure of Pakistani airspace for Indian flights.

The aircraft was reportedly squawking transponder code 7500, which indicates a hijacking or unlawful interference, leading to its diversion to Jaipur. Upon receiving the alert, Mumbai air traffic control (ATC) contacted the pilots, who asserted that all operations were normal. Despite this assurance, established protocols necessitated the diversion of the aircraft to Jaipur, where it was parked in a remote area for safety.

Comprehensive checks were conducted on all passengers, their luggage, and the aircraft itself, all of which were found to be secure. After the thorough inspections, the aircraft was cleared to resume its journey to Delhi with the same crew. This incident has raised questions about how the transponder code was activated, with discussions ongoing regarding potential software issues on the ATC side.

Technical Aspects of the Incident

Senior pilots operating the Boeing 787 have indicated that the likelihood of the 7500 code being activated inadvertently is extremely low, with estimates suggesting a “one in a trillion” chance. Each digit of the transponder code must be entered manually, making accidental activation highly improbable.

Experts have noted that there is no single button that could be pressed by mistake to trigger such a code. Officials from the Mumbai ATC have stated that the new system in place makes it “unlikely” that a software error caused the incident. When a pilot activates the 7500 code, the aircraft’s representation on radar changes to red, accompanied by an alarm.

Other codes, such as 7600 for emergencies and 7700 for communication failures, serve different purposes and are not interchangeable. In light of these technical details, the investigation will focus on understanding the circumstances that led to the activation of the hijack code and whether any external factors contributed to the situation.

Response and Passenger Safety

Following the aircraft’s landing in Jaipur, a multi-agency security operation was initiated. Teams from the Central Industrial Security Force (CISF), local police, and the Bomb Detection and Disposal Squad (BDDS) conducted thorough inspections of the aircraft, passenger baggage, and cargo holds.

The National Security Guard (NSG) was also placed on standby in New Delhi as a precautionary measure. Airport authorities confirmed that all passengers were safely taken to the terminal building after undergoing security checks. Reports indicated that there was no panic among passengers, who were informed about the situation and reassured of their safety.

The airport management stated that normal flight operations continued during the security response. Once the security checks were concluded, the Aerodrome Committee evaluated the situation and determined that the threat alert had been resolved. Subsequently, the aircraft and crew were cleared for departure, allowing the flight to continue its journey to Delhi.

In a statement, Air India expressed regret for the inconvenience caused to passengers due to the unexpected disruption. The airline emphasised its commitment to passenger safety and security, stating that it worked closely with authorities to minimise inconvenience during the incident.

Long or Short, get news the way you like. No ads. No redirections. Download Newspin and Stay Alert, The CSR Journal Mobile app, for fast, crisp, clean updates!

App Store – https://apps.apple.com/in/app/newspin/id6746449540

Google Play Store – https://play.google.com/store/apps/details?id=com.inventifweb.newspin&pcampaignid=web_share