An Unexpected Diversion
On Wednesday, October 14, passengers aboard Air India flight AI-2030 were anticipating a standard landing in New Delhi. Instead, the Boeing 787-9 aircraft, carrying 293 passengers and 13 crew members, was diverted to Jaipur International Airport. The
reason was a serious ground alert. Air traffic controllers at Mumbai's enroute control centre, and subsequently Ahmedabad ATC, had received an indication that the flight was under hijack. Following strict security protocols, authorities on the ground immediately set emergency measures in motion, directing the plane to the nearest available airport for inspection. The aircraft landed safely in Jaipur around 9:35 AM and was moved to a secure isolation bay.
Two Conflicting Realities
While emergency procedures were unfolding on the ground, the situation inside the cockpit of AI-2030 was starkly different. When Mumbai ATC contacted the pilots to query the hijack alert, the crew reported that all operations were normal and that they had not activated any emergency code. The pilots said they did not squawk the code 7500, the internationally recognized transponder signal for unlawful interference or hijacking. This created a confusing scenario: a critical alert was active on ground systems, but the flight crew, with direct control and oversight of the aircraft, saw no signs of trouble. Despite the crew's report, established safety protocols must be followed in such cases, leaving no room for error. The diversion to Jaipur was therefore mandatory.
The Investigation Begins
Once on the ground in Jaipur, security agencies including the Bureau of Civil Aviation Security (BCAS) and local police conducted an exhaustive search of the aircraft and questioned the crew. Passengers were deplaned for security screening as a precaution. The search found nothing suspicious, and the alert was officially deemed false. The Directorate General of Civil Aviation (DGCA) immediately launched an investigation into the incident's cause. Initial focus has turned towards a potential technical glitch. Investigators are examining whether the alert originated from a malfunction in a newly installed radar system at the Mumbai ATC, a software issue, or some other processing error. The probe will analyze aircraft transponder records and ATC logs to reconstruct the event's timeline and pinpoint the source of the false alarm.
Why Ground Alerts Take Precedence
This incident highlights a core principle of aviation safety: erring on the side of caution. Even with the crew reporting normal conditions, an electronic alert signifying a potential hijacking cannot be ignored. The protocol is designed to address a worst-case scenario where a crew might be communicating under duress and unable to state the true nature of their situation. The discrepancy between the ground alert and the cockpit's status is precisely why a full security response is triggered. Civil Aviation Minister K. Rammohan Naidu commented on the incident, stating that the government would await the DGCA's final report before considering any changes to security procedures, emphasizing the need to first establish exactly what happened.
