Skip to content
Sign in
Technology · Asia

Mumbai ATC's new enroute radar sent false 7500 hijack alert; Air India AI2030 with 306 diverted to Jaipur

Mumbai air traffic control's recently installed enroute radar system transmitted a false 7500 hijack alert that led Mumbai ATC to direct Air India flight AI2030, carrying 306 people, to divert and land in Jaipur. The aircraft arrived at about 11 am and was parked on a remote bay while aviation and security agencies opened probes into the new ATC systems.

AI-assisted synthesis · Based on 5 outlets' reporting · Full text read from 3 of 5 outletsHow it's made

5 outlets3 regionsLatest reporting 3 min read
Coverage: Center OnlyL 0 · C 3 · R 0 · 2 unrated
Updat3 graphic: India
Updat3 graphic · Map data: Natural Earth Natural Earth (public domain)

What happened

Key facts

  • Mumbai air traffic control's recently installed enroute radar system transmitted a 7500 hijack alert that was false (per The Times of India, indianaviationnews.net).
  • Pilots on AI2030 did not squawk the 7500 code and told Mumbai ATC that all operations on the flight were normal (per The Times of India).
  • Mumbai ATC asked the aircraft to divert and the plane landed in Jaipur at about 11 am and was parked on a remote bay (per The Times of India).
  • Police sources cited a reported bomb threat in some reports, while other local sources described the event as a hijacking rumour rather than a confirmed bomb threat (per theaviationhub.co.uk, turkiyetoday.com).
  • Senior B787 pilots told The Times of India that a chance of the hijack code being set inadvertently is 'one in a trillion' according to the pilots quoted (per The Times of India, theaviationhub.co.uk, turkiyetoday.com).

The brief

A false 7500 hijack alert generated by Mumbai air traffic control’s recently installed enroute radar system forced Air India flight AI2030, carrying 306 people on the Frankfurt–Delhi sector, to divert and land at Jaipur, sources reporting the incident say.

Pilots on board did not squawk the 7500 code and told Mumbai ATC that all operations were normal, but ATC followed the hijack-alert protocol and instructed the aircraft to divert; the Boeing 787 (VT-TSE) landed at about 11 am and was taken to a remote parking bay.

Air India acknowledged in a statement that AI2030 operating from Frankfurt to Delhi on Oct 14 was diverted to Jaipur after a perceived security concern. Aviation and security agencies have opened investigations focusing on the new radar and ATC systems installed in Mumbai, and India’s Directorate General of Civil Aviation is reported to be involved in inquiries.

Some reports cite police sources saying a bomb threat was communicated to airport authorities, while other local sources described the episode as a hijacking rumour rather than a confirmed bomb threat; those accounts differ on whether a separate threat message existed beyond the false 7500 alert.

Multiple outlets report that all 306 passengers and the crew were safely deboarded and escorted to holding areas inside Jaipur airport after the aircraft was placed in an isolation bay for security checks.

The Times of India quotes senior B787 pilots who said the chance of a hijack code being set inadvertently on the aircraft is extremely small, described there as a "one in a trillion" likelihood; other outlets referenced preliminary indications that the alert may have been activated accidentally.

Authorities are probing both the functionality of the newly installed enroute radar at Mumbai and procedural responses by ATC and airport security; the Times of India also noted administrative vacancies at the Airport Authority of India relevant to air navigation services.

At this stage, investigators are examining system logs, ATC recordings and statements from the flight crew and airport police to determine whether the alert originated from the radar equipment, a separate threat communication, or human error, and whether procedural changes are required before the passengers complete their onward journeys.

Why it matters

  • Passengers on Air India AI2030 — 306 people — faced prolonged delays and were moved into holding areas while security checks and an investigation were carried out, imposing concrete time and logistical costs on those travellers and on airline operations.
  • The Airport Authority of India’s air navigation services and the newly installed enroute radar system are directly implicated by the probes, which creates operational and oversight consequences for AAI and for airlines that rely on Mumbai ATC for enroute control.
  • If the alert stemmed from equipment or integration faults in the new radar, aircraft routing and diversion protocols may be triggered more often, increasing costs for carriers and airports through unscheduled diversions and security responses; the sources document probes into system logs and ATC procedures as the mechanism for establishing that cause.
  • Police and aviation investigators have competing accounts to examine — a reported bomb threat cited by some police sources versus a hijacking rumour and a possible accidental activation of the 7500 code in other reports — creating a clear investigative interest for the DGCA and airport security authorities to resolve which communication pathway produced the response.

What to watch next

  • Whether the Directorate General of Civil Aviation and aviation security agencies publish a formal finding about the source of the 7500 alert, as reported probes are examining system logs and ATC recordings.
  • Whether the Airport Authority of India implements procedural or technical changes to the new Mumbai enroute radar system or ATC protocols, as investigations focus on that equipment and on air navigation services oversight.
  • Whether police records confirm a separate bomb threat communication to Jaipur or Mumbai authorities, given conflicting reports that cite a bomb threat versus a hijacking rumour.
  • Whether Air India or AAI announce changes to diversion or isolation-bay procedures for flights routed through Mumbai enroute control after the probes conclude.

How it's being covered

Coverage analysisShow details
5 source articles · 5 unique outlets
Coverage mix: Center Only· 3 Center
Where the outlets are based: Asia 40% · Europe 20% · Other 40%
Coverage mix
Center Only
Left
Center
Right
0 outlets
3 outlets
0 outlets
The marker shows coverage balance: each unique outlet counts once. 2 unrated outlets are not included.
Geography
Where the outlets covering this story are based.
5 unique outletsDominant coverage: Asia
Coverage imbalance
  • Coverage is currently concentrated among Center-rated outlets (3 of 3 rated sources); comparatively few Left or Right-rated outlets have published on the event.
How we measure coverage

How outlets' accounts compare

1 factual disagreement · 4 framing differences · 2 uncorroborated claims · 3 information gaps
Sources disagree on one factual point.Compared across 3 reports whose full text Updat3 used; 2 other outlets were checked by headline only.
Factual disagreements
Sources report different numbers, dates, attribution or causes for the same thing.
  • The Times of India attributes the alert to Mumbai ATC's recently installed enroute radar system, implying a technical cause; theaviationhub.co.uk and turkiyetoday.com report police citations of a bomb threat or hijacking activation by the pilot as preliminary indications, creating disagreement over whether the trigger was equipment error, pilot action, or an external threat message.
Updat3: The evidence conflicts; Updat3 does not present either version as established.
Framing / emphasis differences
Sources agree on the facts but emphasise different angles, actors or consequences.
  • The Times of India frames the event as a false hijack alert caused by Mumbai's newly installed enroute radar system and emphasises a technical fault; turkiyetoday.com and theaviationhub.co.uk include reporting that cites a bomb threat or police references to a bomb threat.
  • Some outlets characterise the incident as a hijack-alert activation possibly by mistake, while others frame it around an external reported bomb threat that prompted an emergency landing notification.
  • All sources that provide a passenger count report 306 people on board; no conflicting passenger number appears across the supplied texts.
  • The Times of India attributes the false alert to Mumbai ATC's new enroute radar system; theaviationhub.co.uk and turkiyetoday.com attribute the diversion to a reported bomb threat or to pilot-activated hijack alert in their preliminary accounts.
Updat3: The underlying facts agree; only the emphasis differs.
One-sided or uncorroborated claims
Claims that come from one party or one source family and are not independently corroborated.
  • The Times of India quotes senior B787 pilots saying the chance of the hijack code being set inadvertently is 'one in a trillion'.
  • The Times of India records an Air India statement saying AI2030 operating from Frankfurt to Delhi on Oct 14 was diverted to Jaipur following a perceived security concern.
Updat3: Not independently corroborated yet — treat as a claim, not an established fact.
Not established by the reporting
Information the available reporting does not contain or confirm. This is a gap, not a disagreement.
  • No source provides a technical diagnostic report or vendor statement about the specific failure mode of the new enroute radar that would explain how it transmitted a false 7500 alert.
  • No source supplies detailed timelines of communications between Mumbai ATC and Jaipur airport controllers or full ATC transcript excerpts that would show the sequence of messages leading to the diversion.
  • No source mentions whether similar false alerts have occurred with this radar elsewhere or whether regulators had raised prior concerns about the installation.
Updat3: Updat3 cannot conclude anything about this from the current sources.

How we got here

The technical framework for transponder squawk codes that underpins any 7500 alert originates in International Civil Aviation Organization procedures — ICAO’s Doc 4444 and Annex 10 — which standardised discrete Mode A codes (including 7500 for unlawful interference) and their operational handling in international air traffic services (ICAO, longstanding guidance; current editions in force 2016–2020).

Domestic operational responsibility for radar installations and controller procedures rests with the Airports Authority of India and the Directorate General of Civil Aviation, which issued revised ATC equipment and incident-reporting guidelines in 2019.

Original sources

1 of 5 articles · Middle East · Show all

Every story links to the reporting it was built from. How we choose sources

Spotted a factual error, a broken link or a misleading summary? Tell us.