Pricing Search Start free trial
// EVENT · GNSS INTERFERENCE CLOSED · CELL FLAG BACK IN PRE-SPIKE BAND Data as of 18 Aug 2026, 09:45 UTC

GNSS Interference over Abu Dhabi — Aviation Impact, August 2026

← All airspace events

Over the Abu Dhabi grid cell (24°N 55°E), 71% of tracked aircraft — 526 of 738 — broadcast low navigation integrity (NIC) on 15 August, the broad ADS-B flag for degraded GNSS position confidence, up from a 47%–56% band across 10–14 August. The stricter, jamming-grade measure over the Emirates FIR (OMAE) sits at about 10.5% of aircraft (1,485 of ~14,200 on 15 August) — near, and slightly below, its ~12.7% 90-day average, so the regional interference floor is chronic; what moved on 15 August is the broad cell flag, not the stricter FIR-level measure. Zayed International (AUH) is operating normally — about 344 movements a day, which its own brief scores as a normal day: GNSS interference degrades onboard navigation, it does not close the runway. All aircraft figures are a floor from the crowdsourced ADS-B network, not a total. Close-out (18 August): the cell flag fell back to 63% on 16 August and 54% on 17 August — inside the pre-spike band — and this brief is now closed.
// Flying to Abu Dhabi or the Gulf this week? The short version
  • Abu Dhabi (AUH) and its neighbours (DXB, SHJ, DWC) are operating normally — GNSS interference degrades navigation avionics, it does not stop flights, and AUH is at its usual ~344 movements a day.
  • The 15 August spike is in the broad low-NIC flag over the Abu Dhabi cell (71%); the stricter jamming-grade measure for the whole Emirates FIR was ~10.5%, actually a touch below its own 90-day norm — chronic regional interference, with a busier-than-usual day on this cell.
  • What we measure is navigation integrity, not safety: seven in ten aircraft in the Abu Dhabi cell flagged 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 spike in 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 Abu Dhabi grid cell (24°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 47%–56% across 10–14 August, then jumped to 71% (526 of 738 aircraft) on 15 August. 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 spike has since decayed: 63% on 16 August and 54% on 17 August, back inside the pre-spike band — this brief is now closed. Daily low-NIC ratio:

49
10 Aug
50
11 Aug
49
12 Aug
47
13 Aug
56
14 Aug
71
15 Aug
63
16 Aug
54
17 Aug

Fig. 1 — Daily share of tracked aircraft reporting low navigation integrity (NIC) over the Abu Dhabi grid cell (24°N 55°E), % · Data as of 18 Aug 2026, 09:45 UTC · Source: Aircraft ADS-B navigation-integrity (NIC) fields, FlySafe-derived daily aggregate (public telemetry).

Airports in the exposure zone

AirportSizeExposureFIR
Zayed International Airport (AUH) large — · cell 24°N 55°E · 71% low-NIC · traffic normal OMAE
Dubai International Airport (DXB) large — · Emirates FIR · ~10% jamming-grade · traffic normal OMAE
Sharjah International Airport (SHJ) large — · Emirates FIR · traffic normal OMAE
Al Maktoum International Airport (DWC) 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.

We are deliberately not plotting a traffic градусник here, because for GNSS interference it would be the wrong instrument: jamming and spoofing degrade what aircraft avionics compute, not how many aircraft move. Abu Dhabi has good ADS-B coverage and the counts are clear — Zayed International (AUH) ran at about 385 movements a day over the last 7 days, at or above its own baseline. Its Emirates-FIR neighbours DXB, SHJ and DWC are all reading normal too. The meaningful signal is navigation integrity, shown in the cadence chart above; the throughput number is here only to make the point that a 71% low-NIC ratio and a normal traffic day coexist. Live view: AUH airport brief.

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 Abu Dhabi cell can show 71% of aircraft flagging low navigation integrity while AUH runs a normal ~344-movement day. The operational cost is workload and margin, not cancelled flights.

Two numbers, two thresholds — and it matters which one spiked. 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 cell figure that jumped from a 47%–56% band to 71% on 15 August. 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 the same day. The honest reading: the stricter FIR measure sat near, and slightly below, its ~12.7% 90-day average, so the regional interference floor did not surge — the broad low-NIC flag over this one cell did. Both are FIR/cell-level aggregates from aircraft telemetry, labelled as such; neither is a per-passenger statement.

It is regional and persistent, not an Abu Dhabi event. The same signal sits across the Gulf. 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 a broad-flag spike 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 AUH brief update from the same cycle.

What the data showed — close-out, 18 August. The spike decayed as fast as it arrived. The broad low-NIC flag over the Abu Dhabi cell (24°N 55°E) peaked at 71% on 15 August (526 of 738 aircraft), eased to 63% on 16 August (405 of 641) and settled at 54% on 17 August (370 of 690) — back inside the 47%–56% band the cell held before the spike, for the second consecutive day. The stricter, jamming-grade measure over the Emirates FIR (OMAE) read 12.6% on 16 August and 8.3% on 17 August (1,214 of ~14,600 aircraft) — the latter below the FIR's ~12.4% 90-day average. Throughput never moved: Zayed International averaged about 385 movements a day over the closing week, at or above its baseline. With the cell flag back in its pre-spike band and the FIR-level measure below its own norm, we are closing this brief. The chronic Gulf-wide interference floor persists and remains tracked in the AUH 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

Is it safe to fly to Abu Dhabi with the GPS interference?

Airliners navigate with several independent systems, not GNSS alone, and Abu Dhabi's airports were operating normally as of 16 August 2026 — AUH at about 344 movements a day, which its own brief scores as a normal day. 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.

What is GNSS interference and does it affect my flight?

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.

How bad is the GNSS interference over Abu Dhabi right now?

On 15 August 2026, about 71% of tracked aircraft over the Abu Dhabi cell flagged low navigation integrity (a broad indicator), up from a 47%–56% band earlier in the week. The stricter jamming-grade measure was near 10.5% over the Emirates FIR — close to its ~12.7% 90-day average — with ~8% over the Muscat FIR and ~3% 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. By 17 August the cell flag had returned to 54%, inside its pre-spike band, and this brief was closed on 18 August.

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.

// Copy-paste quote

“Over the Abu Dhabi grid cell, 71% of tracked aircraft — 526 of 738 on 15 August — broadcast degraded GNSS navigation integrity, up from around half earlier in the week and part of a chronic Gulf-wide pattern; yet Zayed International kept operating at its normal ~344 movements a day, according to flight-monitoring service FlySafe.zone.”

Chart: advisory cadence
PNG · 1600px · attribution baked in
Daily share of tracked aircraft reporting low navigation integrity (NIC) over the Abu Dhabi grid cell (24°N 55°E), % — light version preview
↓ Data behind the charts — CSV CC BY 4.0 · dates + daily values, ready for your own chart
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.

No newsletters — we only reply to this request. Press page
// Cite this
"FlySafe.zone — GNSS Interference over Abu Dhabi — Aviation Impact, August 2026", https://flysafe.zone/events/gnss-auh-2026-08/, data as of 18 Aug 2026, 09:45 UTC — free to cite with a link. GNSS-degradation figures are derived from aircraft-broadcast navigation-integrity (NIC) and position-accuracy (NACp) fields; FIR-level jamming-grade ratios are the same telemetry aggregated per FIR. All figures are a floor from the crowdsourced ADS-B receiver network, not a total; no regulator or vendor names are attached. Method: /methodology/ · Press: /press/.

Related coverage