GNSS Interference over Dubai — Aviation Impact, August 2026
- Dubai (DXB) and its neighbours (SHJ, AUH) are operating normally — GNSS interference degrades navigation avionics, it does not stop flights, and DXB is at its usual ~912 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 in 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) 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 all eight days, 10–17 August — 62% (485 of 789 aircraft) on the final day. Two honest caveats: this is our short cell-level series (daily aggregation for this cell begins 10 August in our data), and low-NIC is a broad flag — the stricter, jamming-grade measure is lower (see below). The band never broke, and no escalation signal fired — this brief is now closed as a documented steady state (see the close-out 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:50 UTC · Source: Aircraft ADS-B navigation-integrity (NIC) fields, FlySafe-derived daily aggregate (public telemetry).
Airports in the exposure zone
| Airport | Size | Exposure | FIR |
|---|---|---|---|
| Dubai International Airport (DXB) | large | — · cell 25°N 55°E · 65% low-NIC · traffic normal | OMAE |
| Sharjah International Airport (SHJ) | large | — · Emirates FIR · traffic normal | OMAE |
| Zayed International Airport (AUH) | large | — · Emirates FIR · traffic normal | OMAE |
| Al Maktoum International Airport (DWC) | large | — · Emirates FIR | OMAE |
| Muscat International Airport (MCT) | large | — · Muscat FIR · ~18% jamming-grade | OOMM |
| Bahrain International Airport (BAH) | large | — · Bahrain FIR · ~7% 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 DXB runs a normal ~912-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 ~8% figure for the Emirates FIR (OMAE). 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 Dubai event. The same signal sits across the Gulf. In our recent FIR aggregates the Muscat FIR (OOMM) reads the strongest of the well-covered airspaces (~18% jamming-grade), the Emirates FIR (OMAE) ~8% and the Bahrain FIR (OBBB) ~7%; the Emirates FIR has averaged roughly 13% over the last 90 days, so mid-August 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 DXB brief update from the same cycle.
What the data showed — close-out, 18 August. This brief documented a steady state, and a steady state is how it ends. Across the full 10–17 August window the broad low-NIC flag over the Dubai cell (25°N 55°E) never left the 52%–76% band it opened in — 68% on 15 August (560 of 822 aircraft), 75% on 16 August (584 of 783), 62% on 17 August (485 of 789). The stricter, jamming-grade measure over the Emirates FIR (OMAE) closed at 8.3% on 17 August (1,214 of ~14,600 aircraft), below the FIR's ~12.4% 90-day average, with the Muscat FIR (OOMM) at ~7.2% and the Bahrain FIR (OBBB) at ~1.8% — each below its own 90-day norm. Throughput never moved: Dubai International averaged about 939 movements a day over the closing week (a 15 August receiver-coverage gap day is excluded from that average), in line with its baseline. None of the escalation signals set out above fired — no NOTAM series suspending GNSS approaches, no sustained jump in the jamming-grade ratio, no navigation-attributed diversions. With eight days of data showing chronic interference without escalation, we are closing this brief as a documented steady state. The Gulf-wide interference floor persists and remains tracked in the DXB 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 Dubai's airports were operating normally as of 15 August 2026 — DXB at about 912 movements a day, in line with its baseline. 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.
As of 15 August 2026, about 65% of tracked aircraft over the Dubai cell flagged low navigation integrity (a broad indicator), while the stricter jamming-grade measure was near 8% over the Emirates FIR, ~18% over the Muscat FIR and ~7% over the Bahrain FIR. These are FIR- and cell-level aggregates from aircraft telemetry, reported as a floor from the crowdsourced receiver network — not a per-flight figure. Through 17 August the cell flag stayed inside its 52%–76% band (62% on 17 August) and the Emirates-FIR jamming-grade measure ended at 8.3%, below its ~12.4% 90-day average; this brief was closed on 18 August with the chronic floor still tracked in the live tools.
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, two-thirds of tracked aircraft — 522 of 797 on 14 August — broadcast degraded GNSS navigation integrity, part of a chronic Gulf-wide pattern that has held for months, yet Dubai International kept operating at its normal ~912 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.
