Air India Pilot Inadvertently Squawks 7500, Diverts Frankfurt-Delhi Flight

Air India diverted its Frankfurt-to-Delhi Boeing 787-9 to Jaipur on Wednesday, October 14, 2026, after air-traffic controllers detected the transponder code 7500. The alert prompted a security response. All 306 passengers landed safely at about 9:35 a.m., and the flight continued to Delhi, arriving at 3:23 p.m.

The transponder squawked 7500 while the aircraft was crossing the Mumbai Flight Information Region. Authorities treated the signal as a possible unlawful-interference alert, then sent the plane to Jaipur for inspection. The cause remains under investigation.

Jaipur airport director Charan Singh said preliminary indications pointed to a possible pilot mistake. He also said an investigation would establish what happened. Reports said the pilot told controllers that flight operations were normal and later denied intentionally setting the code. A technical or system-related problem has also been raised as a possibility.

The airline described the diversion as a precaution after a perceived security concern. It said the relevant security agencies cleared the aircraft and crew, and that passengers had reboarded. Its statement said: “The aircraft landed safely in Jaipur.”

The flight spent about five hours in Jaipur. Security teams checked the aircraft and baggage, screened passengers and crew, and then allowed the service to resume to Delhi.

Code 7500 triggers a response even before investigators know why it appeared

Code 7500 signals unlawful interference, including a suspected hijacking. The transponder alert can notify air-traffic control and security agencies without a crew member making an overt radio declaration. That is why the aircraft faced a security response even though controllers reportedly heard that operations were normal.

A senior air-traffic-control official described what controllers see when the code appears: “the colour of this aircraft's dot on the radar screen turns red and an alarm goes off.” The official also distinguished two other emergency codes. Code 7600 signals a radio-communication failure; 7700 indicates a general emergency.

Aviation sources quoted in connection with the incident said pilots normally enter the digits manually. Senior Boeing 787 pilots described accidental selection as “a one in a trillion” chance and said “each digit has to be physically entered.” That characterization was not a finding about this flight. Investigators have not established whether the alert came from pilot input, a system issue or another cause.

The Directorate General of Civil Aviation is investigating how the code was transmitted. No hijacking, bomb or other threat was confirmed after the Jaipur checks. The alert itself, however, required authorities to follow security procedures while they established whether a threat existed.

Controllers diverted the aircraft while it crossed the Mumbai flight region

The signal was reported at approximately 9:00 a.m. Ahmedabad Air Traffic Control was identified in some accounts as the controller that received it while the aircraft was in the Mumbai Flight Information Region. Other accounts differed over whether Mumbai or Ahmedabad received the code.

Authorities in New Delhi reportedly decided at approximately 9:10 a.m. to divert the flight to Jaipur as a precaution. The plane landed there at about 9:35 a.m. with 306 passengers aboard. Jaipur airport officials said the passengers and crew were safe.

The differing accounts of which control unit received the transmission have not changed the reported sequence: controllers detected the 7500 alert, authorities ordered a diversion, and security teams inspected the aircraft after it landed. The pilot's reported assurance that operations were normal did not end the response.

Shiv Dayal, assistant commissioner of police for Malviya Nagar, said airport authorities informed police about the emergency landing following the alert. Singh said preliminary indications suggested the pilot may have activated the code by mistake, but framed that as an early indication rather than a final explanation.

Security teams inspected the plane, luggage and passengers at Jaipur

Airport authorities moved the aircraft to an isolation bay for inspection. The checks involved Jaipur police, Central Industrial Security Force personnel, airport security agencies and bomb-detection and disposal teams. Passengers and crew disembarked under security supervision.

Teams examined the plane and baggage, while passengers underwent security screening. The aircraft, crew and passengers were cleared after the checks. No bomb or hijacking threat was confirmed, and the passengers reboarded.

The delay lasted roughly five hours before the aircraft and crew were cleared to continue. The flight then resumed its journey to Delhi with the same crew and landed at 3:23 p.m. The incident disrupted the itinerary despite the safe landing and eventual clearance.

The airline offered refunds or rescheduling if a passenger cancelled

The airline said passengers could choose complimentary rescheduling or a full refund if they cancelled their journey. It also said its teams worked with authorities to limit inconvenience and apologized for the disruption. The flight continued after passengers reboarded.

The airline said the aircraft and crew had passed the security checks, while the DGCA and other aviation and security authorities continued investigating the alert. The inquiry is focused on how the code was generated, including whether pilot error or a technical issue played a role.

The flight's diversion ended with its arrival in Delhi, but the investigation remained open on October 14. Singh's preliminary assessment pointed toward accidental activation; the final cause had not been established.