The Initial Alert: A 'Hijack' Signal
On Wednesday morning, Air India flight AI 2030, a Boeing 787-9 carrying 306 people, was nearing its destination in Delhi after an overnight journey from Frankfurt. As it entered Indian airspace, Air Traffic Control (ATC) in Mumbai and Ahmedabad received
a 'Squawk 7500' transmission from the aircraft. This specific four-digit transponder code is an internationally recognized signal for unlawful interference or a hijacking attempt. The signal immediately triggered a high-level security response, as authorities on the ground are required to assume the worst-case scenario until proven otherwise. Following established protocol, a decision was made to divert the flight from its original destination.
Diversion and Security Protocol in Jaipur
Instead of proceeding to the busy Delhi airport, the flight was rerouted to Jaipur International Airport, landing safely at approximately 9:35 AM. Upon landing, the aircraft was immediately escorted to a remote isolation bay, a designated area for handling security-related emergencies away from the main terminal and other aircraft. A multi-agency security operation was launched, involving local police and anti-terrorism squads. All passengers and 13 crew members were deplaned and taken to the terminal for security checks, while the aircraft and all luggage were subjected to a thorough inspection by a Bomb Detection and Disposal Squad.
Pilots Report Normal Operations
Here's where the story takes a turn. While the security response on the ground was in full swing, the pilots of AI 2030 were in communication with ATC. They consistently reported that all flight operations were normal and that there was no emergency on board. The flight crew denied having intentionally transmitted the '7500' hijack code. This created a puzzling situation for authorities: the plane was sending a distress signal, but the crew insisted everything was fine. Despite the pilots' assurances, the strict security protocol had to be completed to ensure the safety of everyone on board.
The Investigation: Human Error or Technical Glitch?
With the passengers and aircraft declared safe, the focus has shifted to what caused the false alarm. An investigation by the Directorate General of Civil Aviation (DGCA) is now underway. There are two primary theories being explored. One possibility is a technical glitch, either with the aircraft's transponder system or the new ATC radar systems on the ground. Another is pilot error, where the code may have been entered accidentally. However, senior pilots have noted that setting the code requires manually dialling each of the four digits, making an accidental input highly unlikely. The pilots themselves have reportedly disputed the idea of an error, pointing instead to a potential technical issue. The investigation will aim to provide a definitive answer.
The Aftermath: An 'All Clear' and Onward Journey
After several hours on the ground in Jaipur, the exhaustive security checks concluded that there was no threat. The Aerodrome Committee gave the all-clear, and the passengers, having undergone a second round of security screening, reboarded the aircraft. The flight was then cleared for takeoff and completed its journey to Delhi later in the afternoon. In a statement, Air India confirmed the diversion was due to a 'perceived security concern' and apologized to passengers for the significant inconvenience and disruption, reiterating that safety remains its highest priority.
