'Were told can't land in Delhi due to security reasons': Frankfurt-Delhi Air India passengers recall hijacking scare

Air India flight AI2030 was flying from Frankfurt to Delhi when air traffic control received a hijacking alert from the aircraft. The flight was diverted to Jaipur as a precaution, creating confusion among passengers who were told only that they would land for security reasons. It later continued safely to Delhi.

The aircraft transmitted transponder code 7500, the internationally recognised code for hijacking or unlawful interference. After landing in Jaipur around 9.30 am, passengers remained onboard for at least two hours. They later disembarked, showed passports when asked, and waited while check-in baggage was scanned.

The aircraft, crew, and passengers were cleared after the security checks. The flight reached Delhi’s Terminal 3 around 3.15 pm. The Directorate General of Civil Aviation is investigating what triggered the alert, including whether the problem came from the aircraft or the air traffic control system.

Code 7500 is the internationally recognised aviation transponder code for hijacking or unlawful interference. It is a serious emergency signal because it tells air traffic control that an aircraft may be under coercion or facing an unauthorised takeover. The code allows controllers and relevant authorities to respond quickly.

In this incident, AI2030 transmitted 7500 while flying from Frankfurt to Delhi. Air traffic control received the alert and directed the aircraft to Jaipur instead of allowing it to land immediately in Delhi. Passengers were later told the aircraft needed a security check, without being given the full details.

The signal does not automatically prove that a hijacking has occurred. Officials suspected this alert may have been caused by a technical glitch, but the cause had not been established. India’s Directorate General of Civil Aviation will investigate whether the issue involved the aircraft or the air traffic control system.

AI2030 was carrying 293 passengers and 13 crew members, making the diversion a large-scale security operation. The aircraft was a Boeing 787-9 flying from Frankfurt to Delhi. Although everyone eventually reached Delhi safely, the unexpected stop substantially extended the journey.

Passengers were informed around 9 am that the flight would divert to Jaipur. It landed there around 9.30 am and remained on the ground while security procedures took place. Passengers waited onboard for at least two hours, then spent another two hours waiting after disembarking while their baggage was scanned. They later reboarded.

The aircraft finally reached Terminal 3 at Delhi’s Indira Gandhi International Airport around 3.15 pm. Based on the reported diversion announcement and arrival times, passengers experienced roughly six hours of disruption after the alert. The article does not provide the flight’s scheduled Delhi arrival time, so the exact delay cannot be calculated.

After AI2030 landed in Jaipur, passengers faced several layers of security checks. They remained inside the aircraft for at least two hours while officials prepared the response. The captain later announced that passengers would have to disembark for further checks.

Once outside, passengers saw many security personnel. Some, including Gurjeet Singh Khalsa, were asked to show their passports. Security personnel then instructed everyone to wait while check-in baggage underwent scanning. Another waiting period of about two hours followed before passengers could return to the aircraft.

Air India said all passengers disembarked, underwent security checks, and later reboarded. The relevant security agencies also checked and cleared the aircraft and crew. After those procedures were completed, the pilot was allowed to fly the aircraft to Delhi. The incident shows how a perceived threat can affect passengers, luggage, crew, and the aircraft itself.

A hijacking alert can immediately change an aircraft’s flight plan and activate a major security response. The priority is to protect passengers and crew while determining whether the alert reflects a real threat or a false signal. That is why AI2030 was diverted rather than continuing directly to Delhi.

In Jaipur, passengers remained onboard, then disembarked for security checks. Some showed passports, and all check-in baggage was scanned. Security agencies checked the aircraft and crew before clearing them. The aircraft then reboarded its passengers and continued to Delhi under the pilot’s control.

These actions can cause lengthy delays, anxiety, and disruption for hundreds of travellers. They also lead to official investigations. In this case, the DGCA will examine what triggered code 7500 and whether the source was the aircraft or the ATC system. A suspected technical glitch does not remove the need for a full response.

Air traffic control acts first by receiving and responding to the aircraft’s emergency transponder signal. In this case, ATC received code 7500 and diverted AI2030 to Jaipur. Officials later allowed the pilot to fly the aircraft back to Delhi after the security response was completed.

Air India operated the flight and informed passengers that a security concern had caused the diversion. Its crew managed announcements, disembarkation, and reboarding. Relevant security agencies carried out checks on the passengers, baggage, aircraft, and crew. They cleared the aircraft and crew before the flight resumed.

The Directorate General of Civil Aviation serves as the regulator and investigator. It will determine what triggered the squawk and whether the fault lay with the aircraft or the ATC system. The incident therefore involves immediate operational action by ATC and the airline, physical security work by agencies, and later technical oversight by the regulator.

Aircraft transponders communicate with air traffic control by sending identifying information and selected emergency codes. During normal flights, this helps controllers distinguish aircraft, follow their positions, and manage safe routes. The system also gives controllers a way to recognise certain urgent situations.

The clearest example here is AI2030’s transmission of code 7500. That code indicated hijacking or unlawful interference, so ATC received an immediate warning and diverted the aircraft to Jaipur. The signal helped authorities identify a possible security emergency before the aircraft reached Delhi. The passengers were then checked and the baggage was scanned.

A transponder signal is an important warning, but it still requires verification. Officials suspected that AI2030’s alert may have resulted from a technical glitch. The DGCA will investigate whether the aircraft or ATC system caused the problem. The response shows that these systems support both routine flight management and emergency protection, while human checks confirm what happened.