Frankfurt-Delhi Air India flight diverted to Jaipur after hijacking alert, probe on

Air India flight AI 2030 was flying from Frankfurt to Delhi when the pilot issued a hijacking alert. The aircraft, a Boeing 787-9, was diverted to Jaipur International Airport. It made an emergency landing safely on Wednesday morning. The incident mattered because the alert suggested possible hijacking or unlawful interference during flight.

The aircraft was showing transponder code 7500, an internationally recognised hijacking code. Air Traffic Control received the pilot-in-command’s alert and redirected the flight to Jaipur. After landing, the Boeing was moved to a designated isolation bay. Security teams then checked the aircraft, passengers, and baggage.

All passengers and crew members were safely evacuated to a holding area in the terminal. Police also reported that the emergency landing followed a bomb threat. The aircraft was later cleared by authorities, and passengers were expected to board again. The DGCA continued investigating, while Air India had not issued an official statement.

Transponder code 7500 is an internationally recognised aviation code indicating a possible hijacking or unlawful interference. It matters because it gives Air Traffic Control a rapid, standardised warning without requiring a long radio explanation. The signal can prompt controllers and authorities to treat the aircraft as a serious security emergency.

In this incident, Air India flight AI 2030 was squawking 7500 while travelling from Frankfurt to Delhi. The pilot-in-command also issued a hijacking alert. ATC received that alert and arranged for the aircraft to divert to Jaipur International Airport, where it could be isolated and checked safely.

The code identified the type of danger suspected, but it did not establish exactly what had happened onboard. Police sources separately reported a bomb threat, while the DGCA investigated the circumstances. The aircraft was cleared after checks, but the alert led to emergency procedures before passengers could continue toward Delhi.

The flight did not continue to Delhi because its pilot issued a hijacking alert while the aircraft was in the air. The aircraft was also squawking transponder code 7500, which signals possible hijacking or unlawful interference. Such an alert requires authorities to reduce uncertainty and protect everyone onboard before normal travel resumes.

ATC received the alert and diverted AI 2030 to Jaipur International Airport. After landing, the Boeing 787-9 was moved to a designated isolation bay. That location allowed security personnel to examine the aircraft away from ordinary airport operations. Police sources said the emergency landing followed a reported bomb threat, adding another reason for careful screening.

Passengers and crew were deplaned in phases under security supervision. Their baggage was screened, and teams from the ATS, airport security agencies, and local police took part. The aircraft was later cleared by authorities, and passengers were expected to board again. The DGCA continued its investigation into the alert and the reported threat.

The article identifies six main organisations or operational groups connected with the response: Air Traffic Control, the DGCA, the Anti-Terrorism Squad, airport security agencies, local police, and the National Security Guard. Airport authorities and security personnel are also mentioned, but they overlap with the broader airport response. Their involvement shows that an in-flight security alert can activate several layers of government action.

ATC received the pilot’s alert and arranged the diversion. Airport security agencies, the ATS, and local police helped secure the isolation bay and screen passengers and baggage. Security personnel supervised the phased deplaning of both pilots and passengers. The NSG was placed on standby in New Delhi, according to preliminary information.

The DGCA acted as the aviation regulator and began investigating the incident. Airport authorities informed police about the reported bomb threat. The article does not state that every named group entered the aircraft or performed the same task. Instead, the groups supported different parts of the response, from immediate control to later investigation.

After AI 2030 landed in Jaipur, all passengers and crew members were safely evacuated. They were taken to a designated holding area inside the airport terminal. This separated people from the aircraft while security teams examined the plane and managed the emergency in a controlled way.

Both pilots and the passengers were deplaned in phases under security supervision. Passengers and their baggage were screened as part of the checks. The aircraft itself was escorted to a designated isolation bay, where security personnel examined it. Ground teams from the ATS, airport security agencies, and local police supported the operation.

The article reports no injuries or arrests. Authorities later cleared the aircraft. DGCA sources said passengers were expected to board soon, suggesting that the flight might resume after the checks. The exact outcome of the reported bomb threat and the reason for the initial hijacking alert remained under investigation when the report was published.

A hijacking alert concerns possible unlawful control or interference with an aircraft. A bomb threat concerns a possible explosive device. They are different threats, but both create uncertainty about safety onboard. Until authorities determine what is happening, they must protect passengers, crew, airport workers, and other aircraft.

In this case, the pilot’s alert and transponder code 7500 prompted ATC to divert AI 2030 to Jaipur. Police sources separately said the emergency landing followed a reported bomb threat. After landing, the aircraft was moved to an isolation bay. Passengers and crew were removed in phases, while security personnel checked the aircraft and screened baggage.

These overlapping procedures do not prove that the two alerts had the same cause. The article says the DGCA was investigating and that further details were awaited. The common response was precautionary: isolate the aircraft, control movement, examine possible risks, and keep people under supervision until authorities cleared the plane.

Emergency coordination begins when a pilot detects or reports a serious problem. The pilot-in-command of AI 2030 issued a hijacking alert, and the aircraft transmitted code 7500. That gave ATC a standard warning and allowed controllers to respond while the aircraft was still airborne. The goal was to move the flight safely to an airport prepared for the emergency.

ATC diverted the aircraft to Jaipur. After landing, airport security personnel moved it to an isolation bay. The ATS, airport security agencies, and local police supported the checks. Passengers and baggage were screened, and both pilots and passengers were deplaned in phases. The NSG was placed on standby in New Delhi.

The DGCA then investigated the incident and examined the circumstances behind the alert. Police sources also reported a bomb threat, while further details remained awaited. The article shows a sequence rather than one single action: pilots report, controllers redirect, airport teams secure, and regulators investigate. Each part helps manage immediate risk and establish what happened.