GNSS Interference over Al Maktoum (Dubai World Central) — Aviation Impact, August 2026
- Al Maktoum (DWC) and its neighbours (DXB, SHJ, AUH) are operating normally — GNSS interference degrades navigation avionics, it does not stop flights, and DWC is at its usual ~150 movements a day.
- This is chronic and region-wide: aircraft over the Gulf have flagged GNSS degradation for months — a steady state that crews and dispatchers already plan around with conventional navigation and ATC vectoring.
- What we measure is navigation integrity, not safety: two-thirds of aircraft over the Dubai cell flag degraded GPS confidence, but go/no-go decisions belong to operators and authorities.
Advisory timeline — how active is this episode
This is not an eruption or a storm — it is a persistent GNSS-interference environment that aircraft over the Gulf have flown through for months. The chart below is our cell-level detection signal: the daily share of tracked aircraft over the Dubai grid cell (25°N 55°E) — the airspace above and around Al Maktoum International (DWC) — whose broadcasts flag low navigation integrity (NIC), the broad ADS-B indicator that a receiver has lost confidence in its GNSS position. It ran 52%–76% across 10–17 August, 62% (485 of 789 aircraft) on the latest complete day, 17 August. Two honest caveats: this is our short cell-level series (daily aggregation for this cell begins 10 August in our data, and the most recent complete day it covers is 17 August), and low-NIC is a broad flag — the stricter, jamming-grade measure is lower (see below). Daily low-NIC ratio:
Fig. 1 — Daily share of tracked aircraft reporting low navigation integrity (NIC) over the Dubai grid cell (25°N 55°E), % · Data as of 18 Aug 2026, 15:45 UTC · Source: Aircraft ADS-B navigation-integrity (NIC) fields, FlySafe-derived daily aggregate (public telemetry).
Airports in the exposure zone
| Airport | Size | Exposure | FIR |
|---|---|---|---|
| Al Maktoum International Airport (DWC) | large | — · cell 25°N 55°E · 68% low-NIC · traffic normal (~150/day) | OMAE |
| Dubai International Airport (DXB) | large | — · same Dubai cell · Emirates FIR · traffic normal | OMAE |
| Sharjah International Airport (SHJ) | large | — · Emirates FIR · traffic normal | OMAE |
| Zayed International Airport (AUH) | large | — · Emirates FIR · traffic normal | OMAE |
| Muscat International Airport (MCT) | large | — · Muscat FIR · ~8% jamming-grade | OOMM |
| Bahrain International Airport (BAH) | large | — · Bahrain FIR · ~3% jamming-grade | OBBB |
Distance alone does not determine impact — wind direction and the flight levels the ash reaches decide which airports and routes are affected on a given day. FIR = Flight Information Region.
What it means for flights
GNSS interference is a navigation problem, not a runway problem. Ash is an engine problem and wind is a runway problem; jamming and spoofing are a position problem — they corrupt the GNSS fix an aircraft computes. Airliners carry multiple independent navigation sources (inertial reference, DME/DME, VOR) and fly published procedures under ATC surveillance, so degraded GNSS is absorbed rather than grounding traffic. That is exactly why the Dubai cell can show two-thirds of aircraft flagging low navigation integrity while Al Maktoum runs a normal ~150-movement day. The operational cost is workload and margin, not cancelled flights.
Two numbers, two thresholds — read them precisely. We publish two related but different measures. Low-NIC (Navigation Integrity Category below threshold) is a broad flag that a receiver's position confidence has dropped — that is the 52%–76% cell figure. Jamming-grade degradation (low NACp, position-accuracy category) is a stricter bar closer to confirmed interference — that is the FIR-level ~10.5% figure for the Emirates FIR (OMAE) on 15 August. Both are FIR/cell-level aggregates from aircraft telemetry, labelled as such; neither is a per-passenger statement, and the gap between them is the point, not a contradiction.
It is regional and persistent, not a DWC event. The same signal sits across the Gulf, and Al Maktoum shares its airspace cell with Dubai International — this is Dubai-terminal-area airspace, not a runway-specific effect. In our 15 August FIR aggregates the Emirates FIR (OMAE) reads ~10.5% jamming-grade, the Muscat FIR (OOMM) ~8.0% and the Bahrain FIR (OBBB) ~3.3%, with the Tehran FIR (OIIX) ~5.9%; the Emirates FIR has averaged roughly 12.7% over the last 90 days, so mid-August at the FIR level is if anything calmer than its own three-month norm. We hold back on thinly-covered FIRs where only a handful of aircraft are seen per snapshot, because a high ratio on two aircraft is noise, not a measurement.
What would change this story. Three signals would move it from steady-state to escalation: a NOTAM series suspending GNSS-based approach procedures (RNP/RNAV) at a major Gulf airport, a sustained jump in the stricter jamming-grade ratio rather than the broad NIC flag, or diversions and go-arounds attributable to lost navigation. Our automated multi-signal analysis checks the NIC and NACp streams against NOTAM and traffic signals every three hours; this page and the DWC brief update from the same cycle.
What the data showed — close-out, 18 August. None of the escalation signals fired. The broad low-NIC flag over the Dubai cell stayed inside its chronic band to the end — 75% on 16 August (584 of 783 aircraft), 62% on 17 August (485 of 789), never leaving the 52%–76% range it held from 10 August. The stricter, jamming-grade measure ended the tracked window below the 90-day norm in all three FIRs on 17 August, the latest complete day: Emirates FIR (OMAE) 8.3% (1,214 of ~14,600 aircraft) against a ~12.4% 90-day average, Muscat FIR (OOMM) 7.2% against ~9.6%, and Bahrain FIR (OBBB) 1.8% against ~12.6%. Throughput never moved: Al Maktoum averaged about 140 movements a day over the closing week, which its own brief reads as a normal level, with DXB, SHJ and AUH normal alongside. No NOTAM series suspended GNSS-based approaches at a major Gulf airport, the jamming-grade ratio fell rather than jumped, and no navigation-loss diversions surfaced — so this brief documented a steady state, not an escalation, and we are closing it. The chronic Gulf-wide interference floor persists and remains tracked in the DWC brief and the live regional GPS-interference map. All figures are aggregates of aircraft-broadcast navigation-integrity (NIC) and position-accuracy (NACp) telemetry from the crowdsourced ADS-B network — a floor, not a total.
Passenger questions, answered from the data
Airliners navigate with several independent systems, not GNSS alone, and Al Maktoum was operating normally throughout the tracked window — about 140 movements a day over the closing week, a normal level for Dubai's second airport. We publish the measured picture (navigation-integrity ratios, throughput); routing and go/no-go decisions belong to operators and authorities. Check your airline's status on the day of travel.
GNSS interference means jamming (drowning out satellite signals) or spoofing (broadcasting false ones), which degrades the position a receiver computes. In practice passengers do not notice it: flight crews cross-check against inertial and ground-based navigation and follow ATC vectors, which is why interference over the Gulf has persisted for months without stopping traffic. It raises crew workload and can trigger nuisance avionics alerts, not cancellations.
Across 10–17 August 2026 the share of tracked aircraft over the Dubai cell flagging low navigation integrity (a broad indicator) held between 52% and 76% — 62% on 17 August, the latest complete day. The stricter jamming-grade measure ended that window at 8.3% over the Emirates FIR — below its ~12.4% 90-day average — with ~7% over the Muscat FIR and ~2% over the Bahrain FIR, both also below their own norms. These are FIR- and cell-level aggregates from aircraft telemetry, reported as a floor from the crowdsourced receiver network — not a per-flight figure. With no escalation beyond the chronic band, this brief was closed on 18 August; the live picture continues in the DWC airport brief and the regional GPS-interference map.
For media — the full kit
Everything on this page — charts, CSV, quotes — is published under CC BY 4.0: free to reuse with attribution to FlySafe.zone. Charts come in dark (social/web) and light (print/light layouts) versions; attribution and license are embedded in every file.
“Over the Dubai grid cell that covers Al Maktoum International, 68% of tracked aircraft — 560 of 822 on 15 August — broadcast degraded GNSS navigation integrity, part of a chronic Gulf-wide pattern that has held for months, yet Al Maktoum kept operating at its normal ~150 movements a day, according to flight-monitoring service FlySafe.zone.”
Boilerplate — about the source (for your article footer)
FlySafe.zone monitors airspace risk and observed airport activity worldwide: 334 flight-information regions scored daily, GPS-interference signals, volcanic-ash exposure and daily observed movements at 493 airports from the crowdsourced ADS-B receiver network. Methodology: flysafe.zone/methodology.
Need a different cut of the data, a comment, or numbers for another airport? Leave an email — we answer fast during active events.
