Pricing Search Start free trial
// EVENT · GNSS INTERFERENCE CLOSED 13 OCT · STEADY STATE DOCUMENTED, NO RECOVERY — 57°N 25°E CELL 82.3% ACROSS 1–12 OCT, 60.9–100% ON ALL 63 OBSERVED DAYS SINCE 10 AUG · RIGA CELL 69.5% · EVRR 8.1% (FIR-LEVEL) · RIX TRAFFIC NORMAL Data as of 13 Oct 2026, 18:55 UTC · closed · per-cell, movement and FIR-level series all complete through 12 Oct (14 Sep a gap)

GNSS Interference over Eastern Latvia, Revisited — 84% of Aircraft Flagging Degraded Navigation North-East of Riga over the Latest Week, 66% over Riga's Own Cell, Fifty-Three Days Without Change, September–October 2026

← All airspace events

Close-out, 13 October 2026: this brief is closed as a documented steady state, the same way its August predecessor was — the interference did not end. Across 1–12 October the 57°N 25°E cell aggregated to 82.3% (246 of 299 tracked aircraft) against 83.4% across September and 84.0% across 10–31 August, read 73.3% (22 of 30) on 12 October, the final plotted day, and has posted 60.9–100% on every one of its 63 observed days since 10 August. Riga's own cell closed the calendar week of 28 September–4 October at 66.6% (621 of 932) — the lowest calendar week of the series, the test this page set — then returned to 69.2% for 5–11 October and aggregates to 69.5% (1,120 of 1,611) across 1–12 October, between a 56.7% on 6 October and an 84.0% on 10 October; its monthly figures step down 73.9% → 71.9% → 69.5%, which we report as measured and do not call a trend on twelve days. At its own scale the Latvia FIR (EVRR) drifted quieter — 8.1% over 6–12 October against a 10.4% 90-day average, with one 10.4% day on 10 October and a 6.7% on 12 October, the lowest daily reading in that feed since at least the start of July (FIR-level, medium confidence). Riga's observed traffic averaged about 182 movements a day across 1–12 October, above September's 177. The closing numbers are in the final section; the text that follows was written on 4 October and is kept as the record. Written 4 October: Over the 57°N 25°E cell — Vidzeme, the Cēsis–Valmiera area roughly 60–170 km north-east of Riga toward the Estonian border — 16 of 19 tracked aircraft broadcast a low Navigation Integrity Category on 2 October 2026, the latest observed day: 84.2% (FlySafe monitoring, crowdsourced ADS-B network; a floor on a thin sample, not a total). Across 26 September–2 October the cell aggregates to 84.0% (137 of 163 aircraft), which is the sounder reading. This is not a new zone and not a spike: the cell has run 60.9–100% on every one of the 53 days observed since our per-cell series opened on 10 August — 83.4% across September against 84.0% across 10–31 August; 14 September is a gap in the feed — so the latest week sits half a point above the September level. We documented this same cell in August and closed it as a steady state; seven and a half weeks on, the numbers describe the same steady state. The more consequential figure is closer to the airport: Riga's own cell (56°N 23°E, which contains the airport and the city) aggregates to 66.3% (624 of 941 aircraft) over 26 September–2 October, on a sample nearly six times the size of the trigger cell — below every calendar-week aggregate since 10 August, which ran 68.6–77.3% — having read 84.5% on 21 September, near the top of the 54.5–84.9% range it has held since 10 August, then 58.3% on 24 September, 59.9% (85 of 142) on 28 September and 57.5% (73 of 127) on 30 September, its three lowest September days, with 70.9% (95 of 134) on 1 October and 65.2% (92 of 141) on 2 October; all of it inside the band. Those three days are three of the only four readings below 60% since 10 August, they still have not been joined by a fourth, and each was a day of the whole 56°N row — on 24 September the row read low and recovered together, on 28 September the cells east of the airport at 24°E and 25°E fell with Riga's, and on 30 September every cell from 21°E to 25°E read 51–71% before rising back to 62–83% the next day — so we report a softer fortnight over Riga as measured, and will call it a trend only on a full calendar week: the week of 28 September stands at 64.3% (438 of 681) after five days, which would be the lowest calendar week of the series if it closed there. The five softest seven-day windows in the whole series now all end between 28 September and 2 October, at 65.2–67.0% against 68.6% for the next lowest — but those windows share six days out of seven with each other, so they are one soft fortnight described five times, not five findings. Its September average is 71.9% against 73.9% in August. The field around Riga has two hot flanks and a quiet corridor: cells at 26°E and beyond toward the Russian border read 95–100% over the week, northern Lithuania along 55°N 22–24°E reads 82–93%, while the Gulf of Riga and Courland cells at 57°N 22–23°E read 27–37%. At FIR scale the picture is far milder and labelled as such: the Latvia FIR (EVRR) averaged 8.4% over 27 September–3 October against a 10.6% 90-day average and read 8.4% on 2 October and 7.9% on 3 October (FIR-level, medium confidence) — because that average pools the saturated east and south with the quiet sea corridor and high-altitude transit. The FIR feed runs a day ahead of the per-cell and movement feeds, so its window ends on 3 October where theirs end on 2 October. Observed traffic at Riga (RIX) stayed in its normal range and reached the top of it, averaging about 180 movements a day over 23 Aug–2 Oct, reading 200 on Thursday 1 October and 204 on Friday 2 October — the busiest day of the window, about 13% above that reference and 6 above the next-busiest Friday in it. GNSS interference is a navigation-layer signal, not a runway closure; aircraft continue to operate on inertial and ground-based navigation, and procedures and go/no-go decisions belong to operators and authorities.
// Flying to Riga or across the eastern Baltic? The short version
  • This brief closed on 13 October 2026 as a documented steady state — the interference did not end. Riga (RIX) kept operating in its normal range throughout: about 182 observed movements a day across 1–12 October against 177 in September, with the window's three busiest days all in October (204 on 2 October, 200 on 1 October, 199 on Friday 9 October); Tallinn (TLL) and Vilnius (VNO) likewise; check your airline on the day.
  • The interference is around the city as much as beyond it: across 1–12 October, 82% of aircraft flagged in the Vidzeme cell 60–170 km north-east of Riga and 70% over Riga's own cell — the airport cell has sat between 55% and 85% on every observed day since 10 August; the calendar week of 28 September–4 October closed at 66.6%, the lowest of the series, the week after returned to 69.2%, and a fourth sub-60% day arrived on 6 October (56.7%) four days before the cell's third-highest reading (84.0% on 10 October); month by month the airport cell reads 74% → 72% → 70% from August to the first twelve days of October — softer over Riga, measured, and not called a trend on twelve days.
  • It is a steady state, not a new event — the automated trigger called it new because the cell's sample reached 30 aircraft for the first time in a month and because the comparison day a week earlier (14 September) is a gap in our feed; the 63-day series shows no inflection — 84.0% in August, 83.4% in September, 82.3% across 1–12 October.
  • GPS interference is a navigation-integrity issue, not a closure event — inertial systems and ground-based aids (ILS, VOR/DME) back satellite navigation up; the practical cost is precision and workload, occasionally a diversion in poor weather.

Advisory timeline — how active is this episode

Close-out, 13 October: the series below runs through 12 October, the final plotted day, and the closing figures are in the last section of this page; the paragraph that follows is kept as written on 4 October. Written 4 October: Our detection layer reads the navigation-integrity field every ADS-B aircraft broadcasts — the Navigation Integrity Category, a self-reported measure of how far the aircraft trusts its own position. When satellite navigation is jammed or spoofed, receivers lower that figure, and the share of aircraft broadcasting a low NIC rises. The 1°×1° cell at 57°N 25°E covers Vidzeme — Cēsis, Valmiera, Smiltene — roughly 60 to 170 km north-east of Riga on the way to the Estonian border. On 2 October, the latest observed day, it read 84.2% (16 of 19 aircraft), after 81.5% (22 of 27) on 1 October and 88.9% (24 of 27) on 30 September; across 26 September–2 October the cell aggregates to 84.0% (137 of 163), which is the figure to hold on to — the single days here sit on 14 to 34 aircraft and swing accordingly. Honesty note on how this brief came about: this is the same cell we documented in August and closed on 19 August as a steady state. Our automated trigger re-raised it as a new interference zone for two mechanical reasons, neither of which is a change in the interference. First, the trigger needs at least 30 tracked aircraft in the cell on the latest day, and 21 September was the first day since 22 August on which this thin cell logged that many — the sample grew, not the share. Second, the check for “quiet a week earlier” looks at 14 September, and that day is empty in the per-cell feed — a collection gap, not a quiet day — the same technicality that produced our Warsaw brief. The series says the opposite of “new”: since it opened on 10 August the cell has posted 60.9–100% on all 53 observed days. Across September the flagged share is 83.4% (542 of 650 aircraft) against 84.0% (482 of 574) across 10–31 August; calendar-week aggregates run 77.4%, 83.6%, 91.0%, 84.1%, 86.1%, 79.5% (six observed days in the week of 14 September) and 81.6% over 21–27 September, the week of 28 September stands at 84.3% (102 of 121) on its first five days, and the latest seven days, 26 September–2 October, aggregate to 84.0%. Eleven days after the trigger the cell is where it was seven weeks ago. This is a steady state inside a known field, and we publish it as such. The cell is thin — between 14 and 34 tracked aircraft a day in September — so single days swing by ten points or more on sampling alone: the 100% readings of 8 September (20 of 20) and 24 September (18 of 18), and the series low of 60.9% on 19 September (14 of 23), are all sampling extremes, not levels. Every count is a floor — solely aircraft the crowdsourced receiver network received are included. Daily share of aircraft flagging degraded navigation in the cell:

82.6
1 Sep
89.3
2 Sep
83.3
3 Sep
81
4 Sep
84.6
5 Sep
84.2
6 Sep
80
7 Sep
100
8 Sep
85.2
9 Sep
91.7
10 Sep
81
11 Sep
77.8
12 Sep
90.9
13 Sep
76.5
15 Sep
78.9
16 Sep
78.3
17 Sep
95.7
18 Sep
60.9
19 Sep
86.4
20 Sep
73.5
21 Sep
71.4
22 Sep
85.7
23 Sep
100
24 Sep
78.9
25 Sep
75
26 Sep
90.9
27 Sep
88.9
28 Sep
76.2
29 Sep
88.9
30 Sep
81.5
1 Oct
84.2
2 Oct
81
3 Oct
77.3
4 Oct
87
5 Oct
87.5
6 Oct
90
7 Oct
70
8 Oct
84.6
9 Oct
88.6
10 Oct
80
11 Oct
73.3
12 Oct

Fig. 1 — daily share of tracked aircraft broadcasting a low Navigation Integrity Category (NIC) in the 57°N 25°E cell (Vidzeme — Cēsis–Valmiera area, north-east of Riga toward the Estonian border), % — crowdsourced ADS-B network · Data as of 13 Oct 2026, 18:55 UTC · closed · per-cell, movement and FIR-level series all complete through 12 Oct (14 Sep a gap) · Source: FlySafe monitoring — crowdsourced ADS-B navigation-integrity data (public).

Airports in the exposure zone

AirportSizeExposure (12 Oct, at close-out)FIR
Riga International (RIX) large — · ≈68.8% flagged (own cell 56°N 23°E, 99 of 144) · 7-day 68.0% · 1–12 Oct 69.5% · 60–170 km south-west of the 73.3% cell · traffic normal, 182 observed movements on 12 Oct EVRR
Lennart Meri Tallinn (TLL) medium — · ≈72.6% flagged (own cell 59°N 24°E, 159 of 219) · 7-day 76.4% · 124 observed movements on 12 Oct, inside its 85–139 window band EETT
Vilnius International (VNO) medium — · ≈48.8% flagged (own cell 54°N 25°E, 41 of 84) · 7-day 57.8% · 141 observed movements on 12 Oct, after 138 the day before EYVL
Kaunas International (KUN) small — · ≈85.5% flagged (own cell 54°N 24°E, 94 of 110) · 7-day 89.5% · 28 observed movements on 12 Oct, after 28 the day before EYVL

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 our monitoring showed: Riga traffic held its normal range to the end — about 182 observed movements a day across 1–12 October against 177 in September — while the cells around it stayed where they were

FlySafe tracks observed departures and arrivals at 493 airports from crowdsourced ADS-B receiver data. Observed counts are a floor, not a total — receiver coverage varies — but an airport measured against its own baseline is a reliable shape. Riga International's last 30 days:

Fig. 2 — Observed daily movements at RIX, 23 Aug – 12 Oct (latest complete UTC day). Data as of 13 Oct 2026, 18:55 UTC · closed · per-cell, movement and FIR-level series all complete through 12 Oct (14 Sep a gap) · Source: FlySafe monitoring (ADS-B receiver network).

  • Across the 23 Aug–12 Oct window plotted above: ~179 observed movements/day, averaged over the 50 days with data (179.4; the ~180 reference line is the figure this page has carried since 4 October, kept fixed so the bars stay comparable), inside a 154–204 band. Observed counts are a floor, not a total.
  • 1–12 October, with the Vidzeme cell at 70.0–90.0% flagged on every day and Riga's own cell at 56.7–84.0%: 200 / 204 / 170 / 188 / 185 / 169 / 166 / 178 / 199 / 161 / 183 / 182 observed movements — an October mean of about 182/day against about 177/day across September and about 182/day over 10–31 August. The window's three busiest days all fell in October: 204 on Friday 2 October, 200 on Thursday 1 October and 199 on Friday 9 October (the window's seven Fridays ran 179–204). The 1–2 October pair we reported as the top of the range rather than a new level stayed exactly that: the ten days after them averaged 178. Weekday by weekday the profile is ordinary — Mondays 182–194, Tuesdays 154–175, Wednesdays 165–178, Thursdays 178–200, Saturdays 160–175, Sundays 170–188 — and the last plotted day, Monday 12 October, read 182 (95 departures, 87 arrivals), the lowest of the window's seven Mondays by two. As all window, the pairings run against any interference reading of the traffic: Saturday 10 October, at 161 the quietest October day (tied with 29 August and 1 September, above the window's 154 and 160), fell on the day Riga's own cell posted its highest October flag rate, 84.0%; Tuesday 6 October read 169, mid-range for the window's Tuesdays, on the day the airport cell posted its lowest, 56.7%.
  • Coverage notes: 14 September is a collection gap in both our per-cell and our movement feeds — no receiver data for that day, in any cell, so it is left blank rather than filled in. Each of 3–12 October arrived complete on the feed's daily run the following morning, and all 41 earlier bars were re-checked against the feed at close-out and are unchanged — this feed has not revised a settled day at any point in the series. The per-cell, movement and FIR-level feeds all end on 12 October this time; there is no one-day lead between them to reconcile.
  • A note on the baseline: RIX's airport brief runs on a different receiver feed and compares each day with the same weekday, so its reference moves — its latest run (13 October, 18:25 UTC) classifies Sunday 11 October as normal, −4% against a same-weekday reference of 185, with a 7-day average of 181, and reads 177 for that day, where the feed behind the bars above holds 183. It flags 10 October as a collection gap at 32 movements, where this feed holds a complete 161; and its trailing days have firmed up the way we said they would — its 1 October entry, which read 158 at our last update against the 200 here, now stands at 193, and its 2 October entry at 193 against the 204 here. The ~180 on this page is the window-level reference, weekday-independent. Our August brief used a ~201 reference over 18 Jul–16 Aug from an earlier feed; in the current feed the monthly means are 182 for 10–31 August, 177 for September and 182 for 1–12 October, so the September dip was a seasonal step that October has already made back — and the two references are not directly comparable.
  • The point: GNSS interference does not surface in the movement count. It surfaces in the navigation-integrity layer — aircraft broadcasting degraded position quality — not in whether flights depart. Across the twelve October days plotted here Riga flew about 182 observed movements a day, its busiest stretch of the window, while more than four in five aircraft over the cell to the north-east and seven in ten over the airport's own cell flagged degraded GNSS.

Live view: RIX airport brief.

What it means for flights

Why this brief exists — and why it is not the story the trigger told. Our detection layer raises a GNSS candidate when a cell near a large airport crosses 60% of aircraft flagged on the latest day, on a sample of at least 30 tracked aircraft, and the same cell was quiet a week earlier. The 57°N 25°E cell crossed the first bar on 21 September at 73.5%. It cleared the sample bar because 21 September happened to be its busiest day since 22 August — 34 aircraft where the September norm is around 22; the two days after it logged 14 apiece, then 18, 19, 20, 22, 27, 21, 27, 27 and 19 on 24 September–2 October. And it passed the “quiet a week ago” test on a technicality: the comparison day, 14 September, holds no data for any cell in the feed. Read against the actual series, that third condition fails outright — the cell has never posted a day below 60.9% since observation began on 10 August, and its September average is higher than the day that tripped the trigger. We already know this cell: it was the subject of our August brief, which closed on 19 August after eight days in a 69–85% band with no escalation. We are publishing again, because six further weeks of data are worth having on record and because the measured picture has a detail the August brief could sketch but not settle: the airport's own cell is now as heavily flagged as the trigger cell, on a far larger sample. But we label it as what it is. There is no escalation here to report, and a reader who arrives expecting news of a sudden jamming surge over Riga should leave with the opposite understanding.

Two hot flanks and a quiet corridor — the shape of the field around Riga. Written 4 October. Interference has a footprint, and around Riga it has a recognisable shape. Along the 57°N row on 2 October the flag rate ran 34.0% at 21°E over the Baltic off Courland, 22.4% at 22°E and 36.9% at 23°E over the Gulf of Riga and its northern shore, 45.0% at 24°E, 84.2% at 25°E over Vidzeme (16 of 19), then 100% at 26°E (18 of 18) toward Alūksne and the Russian border; the 26 September–2 October aggregates say the same with less noise — 36.6%, 27.4%, 36.7%, 48.6%, 84.0%, 100.0%. One row south, the 56°N row that holds the airport read 61.0% at 21°E, 57.4% at 22°E, 65.2% over Riga at 23°E (92 of 141), 69.4% at 24°E, 73.7% at 25°E and 93.3% at 26°E (15 aircraft) on 2 October — a few points below its own weekly figures across most of the row — and those weekly figures are 58–66% across western and central Latvia, 77.5% at 25°E and 94.9% at the eastern edge. South again, the 55°N row over northern Lithuania is saturated — 87.5%, 95.1%, 96.6% (119 aircraft over the Šiauliai area) and 87.0% across 21–24°E on 2 October, 82.0–93.2% over those cells for the week — and to the north the 58°N row over southern Estonia repeats the east–west slope, 41–55% at 21–23°E rising to 74.5% at 24°E, 89.6% at 25°E and 91.5% at 26°E. So the quiet corridor is the sea and the northern shore of the Gulf of Riga at 57°N; the hot flanks are the east toward Russia and the south toward Kaliningrad; and the airport sits on the hotter side of the line. In the August-to-September comparison almost nothing moved: the Vidzeme cell 84.0% to 83.4%, Riga's cell 73.9% to 71.9%, the cell east of the airport at 24°E 62.5% to 64.7%, the 57°N 24°E cell 53.3% to 54.5%, the Gulf cells at 57°N 22–23°E 40.2% to 35.1% and 40.0% to 37.5%. The one clear change is at the eastern edge, where 56°N 26°E rose from 81.8% to 92.8% — on 404 September aircraft, a firming of the saturated flank, not a spread toward the city.

FIR-average hides the flanks — why the cell-level number matters. Written 4 October. By the FIR-wide measure, the whole Latvia FIR (EVRR) sits at 8.4% over 27 September–3 October against a 10.6% 90-day average, reading 9.6% on 30 September, 7.5% on 1 October, 8.4% on 2 October and 7.9% on 3 October on roughly 1,780–1,850 tracked aircraft a day (FIR-level, medium confidence). This feed runs a day ahead of the per-cell one, which is why its week ends on 3 October. It has held a 7.3–9.7% band over the 14 days to 3 October — narrower than the 7.2–11.3% we quoted last update, because 18 September's 11.3% has rolled out of the window rather than because anything moved — and its monthly averages, 11.6% in July, 10.6% in August and 10.0% across September, describe a FIR that is, if anything, drifting very slightly quieter. The reason the FIR figure is an order of magnitude below the cells is that it pools the saturated eastern and southern flanks with the quiet sea corridor and, above all, with high-altitude transit traffic crossing the FIR on the Scandinavia–Central Europe and Baltic trunk routes, most of which reports healthy integrity. Zoom to Riga's own cell and the degraded share is nearly eight times the FIR figure. Both numbers are true; the cell-level one alone tells a dispatcher what the approaches to Riga look like today. The neighbouring FIRs on the same 27 September–3 October window: Tallinn (EETT) ~11.4% against a ~10.7% 90-day average (medium confidence), Vilnius (EYVL) ~20.8% against ~21.0% (medium), St Petersburg (ULLL) ~14.2% against ~12.0% (high), Helsinki (EFIN) ~9.0% against ~8.7% (high), and Kaliningrad (UMKK) ~27.3% against ~29.0% — on about 78 tracked aircraft a day and low confidence, so indicative rather than firm. One FIR-wide figure hides the flanks; a single cell alone overstates the FIR. We label which scale each number belongs to for exactly that reason.

Interference degrades navigation; it does not ground flights. Written 4 October. The figure counts aircraft broadcasting downgraded navigation integrity in their ADS-B position-quality fields — the consistent fingerprint of GNSS interference. It does not mean those aircraft are lost or off course. Airliners cross-check satellite positioning against inertial reference systems and ground-based aids — ILS, VOR/DME — and fall back to them when GNSS degrades, with published contingency procedures for GNSS loss. The real cost is precision and workload: satellite-based (RNP/RNAV) approaches can become unavailable, approach minima rise, and in poor visibility that can mean holding or a diversion to an alternate. That is exactly why Riga's departure board shows nothing: the traffic section above reads an ordinary early-autumn profile — a September mean of about 177 observed movements a day, and the window's two busiest days last, 200 on Thursday 1 October and 204 on Friday 2 October — while two in three aircraft over the airport's own cell flagged degraded GNSS across 26 September–2 October. For Riga's arrivals the relevant figure is that 66.3% weekly aggregate over the airport's own cell, not the thin trigger cell to the north-east; for traffic routing east toward the Russian border it is the 95–100% at 26°E and beyond. Weather matters for the practical outcome: Riga's 30-day record shows instrument conditions on about 14% of observations, so on most days a satellite-based approach becoming unavailable costs little; on the minority of low-visibility days it is when a diversion to Kaunas, Vilnius or Tallinn becomes plausible — and each of those sits under a flagged cell of its own (85%, 64% and 72% on 2 October).

Honest arithmetic on a thin cell, a large cell and a six-week series. Written 4 October. The Vidzeme cell sees between 14 and 38 tracked aircraft a day in our feed — thin enough that a single day can move by ten or fifteen points on the mix of traffic alone, which is why the 100% readings of 8 September (20 of 20) and 24 September (18 of 18), and the 60.9% of 19 September (14 of 23), are reported as sampling extremes and not as levels, and why we describe the state on weekly aggregates of 127–214 aircraft and monthly aggregates of 574 and 650. A cell that can reach 100% on eighteen aircraft can also fall twenty points the next day on the same physics — and did, to 78.9% on nineteen aircraft on 25 September, then 75.0% on twenty aircraft on 26 September before reading 90.9% on twenty-two on 27 September, 88.9% on twenty-seven on 28 September, 76.2% on twenty-one on 29 September, 88.9% on twenty-seven on 30 September, 81.5% on twenty-seven on 1 October and 84.2% on nineteen on 2 October; the 84.0% for 26 September–2 October is the number we stand behind. Riga's own cell is a different instrument: 117–147 aircraft a day, roughly 790–965 a week, so its weekly figures — 68.6%, 75.9%, 77.3%, 73.6%, 72.7%, 76.4% (six observed days) and 70.0% over the calendar weeks to 27 September, 66.3% over the latest seven days to 2 October and 65.2% over 24–30 September, still the softest seven-day window since observation began — carry real weight, and its 84.5% on 21 September is reported as a single day near the top of the range (the series high is 84.9%, on 22 August), not as a step — and the 58.3% of 24 September, 59.9% of 28 September and 57.5% (73 of 127) of 30 September are reported the same way, the three lowest September days and close to the 54.5% series low of 10 August; the entire 56°N row read low on each of those days, and each time the cell came back within a day or three — to 76.4% (97 of 127) by 27 September, 67.9% (93 of 137) on 29 September, 70.9% (95 of 134) on 1 October and 65.2% (92 of 141) on 2 October. We will not pretend the clustering is nothing: three of the four sub-60% days since 10 August fell inside one week, and they pull the latest seven-day figures below every calendar week before them — the five softest seven-day windows of the series now all end between 28 September and 2 October, at 65.2–67.0% against 68.6% for the next lowest, though consecutive seven-day windows share six of their seven days, so that is one soft fortnight counted five times rather than five independent facts. Two days of October have since read 70.9% and 65.2%, neither of them a fourth sub-60% day. We report all of that as measured and will call it a trend only if the calendar week of 28 September closes there — it stands at 64.3% (438 of 681) after five days, which would be the lowest calendar week of the series. A day with no data at all, like 14 September, is left out rather than filled in — and, as explained above, that same blank is part of what tripped the trigger. The series begins on 10 August, so it is 53 observed days deep and we make no claim about how long these cells have looked like this beyond that; the wider southern and eastern Baltic belt has carried elevated interference for well over a year (background: Baltic GPS-jamming escalation, how GPS jamming works and our GNSS explainer), and its other ends are covered in separate active briefs — south-eastern Finland, Gdańsk and east of Warsaw. The same discipline governs the traffic section, where 14 September is blank for the same reason, where 19 and 21 September are shown at their backfilled values rather than the partial readings first received, and where 3 October is withheld because the movement feed has not published it yet. Every figure here is an aggregate of crowdsourced receiver telemetry: a floor, not a total.

What would change the picture. Written 4 October; each of these tests is answered in the close-out block below. Three measured things are watched continuously by our automated multi-signal analysis. First, the quiet corridor: the 57°N 22–23°E cells over the Gulf of Riga (22.4% and 36.9% on 2 October, 27.4% and 36.7% across 26 September–2 October against 29.4% and 35.5% the week before — flat, with the 22°E cell marginally quieter) are the tell-tales — a step in those cells toward the 60–70% the 56°N row shows would mean the field had closed over the northern approaches and the sea routes to Stockholm and Helsinki rather than stopping at the shore. Second, the FIR-level EVRR ratio breaking decisively above the 7.3–9.7% band it has held over the 14 days to 3 October rather than oscillating inside it. Third, a shift from jamming (signal loss) toward spoofing (a coherent false position), or interference reaching approach paths at RIX in low-visibility conditions. A fourth signal — regulatory action, meaning NOTAMs suspending satellite-based approach procedures at Latvian airports — would be the clearest operational marker, and we flag its absence honestly: our NOTAM feed currently carries no items for the Latvia, Tallinn or Vilnius FIRs at all, so its silence here is a gap in our coverage, not evidence that nothing has been issued. No traffic-based airspace closure has registered for those three FIRs in our detection layer since the start of August. The picture can also change downward, and we would say so as plainly: the airport cell's 65.2% over 24–30 September is still its softest seven-day figure since observation began, 26 September–2 October follows at 66.3%, and three of its four sub-60% days since 10 August fell between 24 and 30 September — but each of those was a low day for the whole 56°N row, each reversed within days, and the two October days so far read 70.9% and 65.2%, inside the band. If the calendar week of 28 September, at 64.3% on its first five days, closes at that level, it would be the lowest calendar week of the series and a measured easing over Riga rather than sampling noise; that week closes on 4 October and we will say which way it went in the next update. This page updates from the same monitoring cycle as the RIX brief and the live regional GPS-interference map; if the Vidzeme or Riga cells drop below the bands they have held, or the Gulf corridor climbs into them, the page will say so.

What the data showed — close-out, 13 October. This brief opened on 23 September to put on record that an automated re-raise of the 57°N 25°E cell was a steady state, not a new zone, and to carry the series forward. It closes on 13 October with no recovery to report: the interference did not end, it held — and we close it the way its August predecessor was closed, as a documented steady state. The trigger cell. From 3 to 12 October the Vidzeme cell read 81.0%, 77.3%, 87.0%, 87.5%, 90.0%, 70.0%, 84.6%, 88.6%, 80.0% and 73.3% (22 of 30) on samples of 16 to 35 aircraft — 10 October's 31 of 35 being the second-largest sample of the series after 22 August. The calendar week of 28 September–4 October closed at 82.9% (136 of 164) and the week of 5–11 October at 84.4% (152 of 180); 1–12 October aggregates to 82.3% (246 of 299) against 83.4% across September and 84.0% across 10–31 August. Sixty-three observed days, every one of them between 60.9% and 100%; the two softest October days, 70.0% (14 of 20) on 8 October and 73.3% on 12 October, are the third- and sixth-lowest of the series, both inside the band and both on the thin sample this cell always carries. There is no inflection in it, in either direction. Riga's own cell, and the test this page set. The calendar week of 28 September–4 October closed at 66.6% (621 of 932) — the lowest calendar week of the series, below the 68.6% of 10–16 August — so by this page's own test it was a measured easing over Riga rather than sampling noise; the weekend pulled it up from the 64.3% it stood at after five days, and the week of 5–11 October came back to 69.2% (651 of 941), inside the range of every calendar week before it. The fourth sub-60% day did arrive: 56.7% (72 of 127) on 6 October, the second-lowest day of the series after 10 August's 54.5%, with the cell east of the airport at 24°E down to 43.5% the same day and the row back at 66–77% the next. Four days later the cell read 84.0% (105 of 125) on 10 October, its third-highest day — on the same day the Latvia FIR posted its one high reading and the Gulf of Riga cells their highest October readings — and 65.7% the day after. Across 1–12 October the airport cell aggregates to 69.5% (1,120 of 1,611), 68.0% over the final seven days; its monthly figures step down 73.9% (10–31 August), 71.9% (September), 69.5% (twelve days of October) — about two points a month. We report that as measured and do not call it a trend on twelve days; the softest rolling week of the series is still 24–30 September at 65.2%. The shape of the field. Over 6–12 October the 57°N row read 33.2%, 26.4%, 32.2% and 51.6% from 21°E to 24°E over the Baltic, the Gulf of Riga and its northern shore, then 82.4% at 25°E and 97.5% at 26°E; the 56°N row through the airport 63.7%, 67.2%, 68.0%, 59.7%, 77.2%, 87.7%; northern Lithuania on 55°N 85–97% across 21–24°E; southern Estonia on 58°N 53–55% at 21–23°E rising to 79.6%, 93.7% and 97.4%. Two hot flanks, a quiet corridor, the airport on the hotter side of the line — unchanged from 2 October, and from August. What did move, slightly and broadly, is the level west of 25°E: across 1–12 October every cell on the 56°N and 57°N rows from 21°E to 24°E reads below its September figure, by between one and nine points (Riga's cell 69.5% against 71.9%; the Gulf cells 26.0% and 33.3% against 35.1% and 37.5%), while the eastern edge did not move — 57°N 26°E 98.0% against 98.2%, 56°N 26°E 90.3% against 92.8% on 207 aircraft. Twelve days, a few points, reported and not called. The tests this page set, answered. The quiet corridor at 57°N 22–23°E stepping toward the 60–70% of the row south of it: it did not — 25.5% and 27.5% at 22°E for the calendar weeks of 28 September and 5 October, 35.8% and 33.3% at 23°E; its one high day, 44.1% and 41.2% on 10 October, reversed to 23.5% and 32.1% the next. The Latvia FIR (EVRR) breaking decisively above its 7.3–9.7% band: one day — 10.4% on 10 October, the highest since 18 September — followed by 7.3% and then 6.7% on 12 October, the lowest daily reading in this feed since at least the start of July; the seven days to 12 October average 8.1% against a 10.4% 90-day average, the first twelve days of October 8.1% after 11.6% in July, 10.6% in August and 10.0% in September, and the lowest seven-day windows since 1 September are the ones ending 9 October (8.10%) and 8 and 12 October (8.13%) — FIR-level, medium confidence, about 1,740 tracked aircraft a day. At FIR scale, then, Latvia drifted quieter, not louder. The neighbours on the same 6–12 October window: Tallinn (EETT) 11.2% against a 10.7% 90-day average, Vilnius (EYVL) 20.6% against 20.9%, St Petersburg (ULLL) 11.9% against 12.2% (high confidence), Helsinki (EFIN) 8.9% against 8.5% (high), Kaliningrad (UMKK) 27.3% against 29.0% on about 83 aircraft a day at low confidence on six of the seven days; the one-day spike of 8 October — Tallinn 15.4%, Helsinki 16.4% — did not reach Latvia, which read 7.3% that day. A shift from jamming toward spoofing, or interference on the approach paths in low visibility: the navigation-integrity measure on this page cannot separate the two, and nothing in our data identifies either — not fired, and not excluded by us. Regulatory action: our NOTAM feed still carries no items at all for the Latvia, Tallinn or Vilnius FIRs, so its silence remains a gap in our coverage and not evidence; no traffic-based airspace closure registered for those FIRs or for Kaliningrad in our detection layer between 1 August and close-out. Traffic. Riga (RIX) flew 170, 188, 185, 169, 166, 178, 199, 161, 183 and 182 observed movements on 3–12 October — about 182 a day across 1–12 October, its busiest stretch of the window, against 177 across September and 182 across 10–31 August; the window's three busiest days all fell in October (204, 200, 199), and its weekday profile is ordinary to the end. Tallinn (TLL) read 72.6% flagged over its own cell on 12 October with 124 observed movements, inside its 85–139 window band; Vilnius (VNO) 48.8% with 141; Kaunas (KUN) 85.5% with 28. No attribution of any traffic figure to the interference is made, and none is warranted by the pairings — the quietest October day at Riga fell on the airport cell's highest flag day. Why close now. The purpose of this brief was to show that the trigger had re-raised a steady state, and three weeks of further data say exactly that, as eight days did in August. A brief labelled active that has nothing to add is not an honest page, so this one ends. The Baltic interference field persists — it has for well over a year — and these cells remain tracked on the RIX brief and the live regional GPS-interference map; should the Vidzeme or Riga cells leave the bands they have held, or the Gulf corridor climb into them, that will be a new brief and not a reopening of this one. All cell-level figures are FlySafe aggregates of ADS-B Navigation Integrity Category reports from crowdsourced receiver networks — a floor, not a total; FIR-level ratios come from the same class of public data and are labelled as FIR-level wherever they appear; airport movement counts are observed ADS-B departures and arrivals, also a floor.

Passenger questions, answered from the data

Is GPS jamming affecting flights to Riga right now?

As of 13 October 2026 this brief is closed, and the closing numbers are not a recovery. The airspace cell 60–170 km north-east of Riga (57°N 25°E, Vidzeme) aggregated to 82.3% of aircraft flagging degraded navigation across 1–12 October and read 73.3% on Monday 12 October, the final plotted day, on a sample of 30 aircraft — levels it has held, within a 60.9–100% band, on every one of the 63 days observed since 10 August. Riga's own cell aggregated to 69.5% over the same twelve days, between 56.7% on 6 October and 84.0% on 10 October, all inside its 54.5–84.9% range. Observed traffic at Riga (RIX) stayed in its normal range to the end, averaging about 182 movements a day across 1–12 October against 177 in September. Aircraft in the affected area broadcast degraded navigation but continue operating on back-up systems. The Baltic interference field persists: see the live RIX brief and the regional GPS-interference map, and check your airline's status on the day of travel.

Is this a new jamming zone near Riga?

No. It is the same cell we documented in August and closed on 19 August as a steady state. Our automated trigger flagged it as new for two mechanical reasons: 21 September was the first day since 22 August on which the thin cell logged the 30 tracked aircraft the trigger requires, and the comparison day one week earlier, 14 September, is a collection gap in the per-cell feed — so the check for “quiet a week ago” passed on an empty day. The series itself shows the 57°N 25°E cell at 60.9–100% on all 63 days observed from 10 August to 12 October, when this brief closed — 84.0% across 10–31 August, 83.4% across September and 82.3% across 1–12 October, with calendar-week aggregates between 77.4% and 91.0%. Riga's own cell moved from 73.9% in August to 71.9% in September and 69.5% across 1–12 October. The one clear month-on-month change is at the eastern edge, where the 56°N 26°E cell rose from 81.8% to 92.8% — a firming of an already saturated flank, not a spread toward the city.

Is it dangerous to fly when there’s GPS interference?

Aircraft carry independent navigation systems — inertial reference and ground-based aids such as ILS and VOR/DME — that crews and air-traffic control use when satellite positioning degrades, and regulators publish procedures for interference-prone airspace. We publish the measured picture: where interference is concentrated, how persistent it is and how it is moving. Operational and go/no-go decisions belong to operators and authorities.

What does ‘low NIC’ mean and how do you measure it?

NIC is the Navigation Integrity Category — a value each ADS-B aircraft broadcasts describing how much it trusts its own position. When GNSS is jammed or spoofed, that value falls. We aggregate NIC reports collected by crowdsourced ADS-B receiver networks into a per-cell daily share of aircraft reporting low integrity, on 1°×1° cells. Because it counts nothing but the aircraft the network received, the share is a floor — real exposure may be higher, not lower. On the Vidzeme cell that is between 14 and 38 aircraft a day, so we describe the state on weekly and monthly aggregates rather than on single days — which is why the 84.2% of 2 October is quoted alongside the 84.0% for 26 September–2 October, not on its own; Riga's own cell, at 117–147 aircraft a day, supports firmer daily reading.

Why does Riga’s traffic look normal if seven in ten aircraft over the airport are flagging?

Because the two measure different layers. The 69.5% figure for 1–12 October counts aircraft broadcasting degraded position quality in the airspace cell that contains the airport; the traffic figure counts departures and arrivals at Riga. Interference degrades a navigation source with documented back-ups — it does not close a runway — so it leaves no signature in the movement count. Riga averaged about 179 observed movements a day over the 50 days with data between 23 August and 12 October — about 177 a day in September and about 182 across 1–12 October, against about 182 across 10–31 August — and its three busiest days all fell in October: 204 on Friday 2 October, 200 on Thursday 1 October and 199 on Friday 9 October. 14 September is excluded as a collection gap in our feed. What interference can cost, on the minority of days with low visibility, is a satellite-based approach becoming unavailable, higher minima and occasionally a diversion — none of which showed up in the count over this window.

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 eastern Latvia, 60–170 km north-east of Riga, 82.3% of tracked aircraft broadcast degraded navigation integrity across 1–12 October 2026 — a level the cell has held within a 60.9–100% band on every one of 63 observed days since 10 August — while the share over Riga's own airspace cell was 69.5%, down from 71.9% in September and 73.9% in August, the wider Latvia flight-information region averaged 8.1% over the seven days to 12 October against a 10.4% 90-day average, and Riga's observed traffic stayed in its normal range at about 182 movements a day, according to flight-monitoring service FlySafe.zone, which closed its brief on 13 October as a documented steady state.”

Chart: observed traffic at RIX
PNG · 1600px · attribution baked in
Observed daily movements at RIX — light version preview
Chart: advisory cadence
PNG · 1600px · attribution baked in
daily share of tracked aircraft broadcasting a low Navigation Integrity Category (NIC) in the 57°N 25°E cell (Vidzeme — Cēsis–Valmiera area, north-east of Riga toward the Estonian border), % — crowdsourced ADS-B network — 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 Eastern Latvia, Revisited — 84% of Aircraft Flagging Degraded Navigation North-East of Riga over the Latest Week, 66% over Riga's Own Cell, Fifty-Three Days Without Change, September–October 2026", https://flysafe.zone/events/gnss-rix-2026-09/, data as of 13 Oct 2026, 18:55 UTC · closed · per-cell, movement and FIR-level series all complete through 12 Oct (14 Sep a gap) — free to cite with a link. Observed-traffic figures are FlySafe’s own ADS-B-derived counts (floor, not total). Navigation-integrity figures are FlySafe aggregates of ADS-B Navigation Integrity Category (NIC) reports from crowdsourced receiver networks — a floor, not a total. FIR-level interference ratios come from the same class of public data and are labelled as FIR-level wherever they appear. Airport movement counts are observed ADS-B departures and arrivals, also a floor. Method: /methodology/ · Press: /press/.

Related coverage