Air India Flight Diverted to Jaipur After False Hijack Alert
JAIPUR, INDIA — October 15, 2026: An Air India flight travelling from Frankfurt to New Delhi was diverted to Jaipur on Wednesday after a hijack alert triggered aviation security procedures, prompting authorities to inspect the aircraft and screen passengers before allowing the journey to continue.
Flight AI2030, operated by a Boeing 787-9 aircraft, landed safely at Jaipur International Airport on October 14. The aircraft was moved to an isolation bay for security checks after air traffic control received a signal associated with possible hijacking or unlawful interference.
Reports differ on the precise origin of the alert. Initial accounts indicated that the aircraft had transmitted transponder code 7500, the internationally recognised code associated with a hijacking. Subsequent reporting raised the possibility of an air traffic control system malfunction.
No actual hijacking was confirmed, and the incident remains subject to investigation.
Air India Aircraft Diverted as a Precaution
According to reports from Indian media outlets, the aircraft landed in Jaipur at approximately 9:35 a.m. local time on Wednesday. Security personnel subsequently examined the aircraft and its luggage as part of precautionary procedures.
The flight was carrying approximately 300 people, including passengers and crew. Later reports put the total number on board at 306.
Air India said the diversion followed a perceived security concern. The airline confirmed that the relevant security agencies had checked and cleared the aircraft and crew.
Passengers were taken to the terminal during the inspection process and subsequently allowed to reboard after security screening.
What Is Squawk Code 7500?
Squawk code 7500 is an internationally recognised aircraft transponder code used to indicate unlawful interference, including a hijacking situation.
When air traffic control receives this signal, it can trigger an immediate security response because authorities must consider the possibility that an aircraft or its crew may be under threat.
In the Air India incident, the alert prompted the diversion to Jaipur as a precaution while the circumstances were examined.
However, the transmission of a hijack-associated code does not, by itself, establish that a hijacking has taken place.
Technical Error or Incorrect Alert Under Investigation
The circumstances surrounding the alert have generated differing accounts.
Initial reports suggested that the pilot may have activated the hijack code. Other reports indicated that the pilots had told air traffic control that conditions aboard the aircraft were normal.
Subsequent reporting raised the possibility that a technical problem involving the air traffic control system may have generated the alert. India’s Directorate General of Civil Aviation was reported to be examining the incident.
The precise cause should not be treated as established until the investigation determines how the alert originated.
Flight Resumes Journey to Delhi
After security agencies completed their checks, the aircraft was cleared to continue its journey to the Indian capital.
Reports published on October 15 said the flight departed Jaipur later on Wednesday and landed in Delhi at approximately 3:11 p.m. local time.
The diversion caused a substantial delay for passengers, but the aircraft, passengers and crew were reported safe.
The incident highlights the importance of aviation security protocols, which require airlines and air traffic control authorities to respond cautiously to potential hijacking signals, even when the initial warning later proves unfounded.
