Pricing Search Start free trial
// EVENT · GNSS INTERFERENCE CLOSED 13 OCT · INTERFERENCE PERSISTED — CELL 55.8% ON 12 OCT, SEVEN-DAY 53.9% AGAINST 37.8% IN AUGUST · LRBB 4.8% (FIR-LEVEL) · OTP OCTOBER TRAFFIC ~10% UNDER SEPTEMBER, NOT ATTRIBUTED Data as of 13 Oct 2026, 16:15 UTC · closed · per-cell series complete through 12 Oct (14 Sep a gap), traffic through 10 Oct (29 Sep a gap; 11 Oct provisional, not plotted)

GNSS Interference North of Bucharest Swings Back to 52.1% on 2 October 2026 After 30.6% a Day Earlier — Five Days of Alternating Readings Since the One-Day Collapse to 18.7%, the Seven-Day Figure Down to 43.5% From 59.4%, and the 1 October Dip Arriving on a Full Sample, Which Weakens the Coverage Caveat We Flagged

← All airspace events

Close-out, 13 October 2026: this brief is closed without a recovery to report. After the five alternating days described below, the 45°N 25°E cell settled rather than cooled — ten consecutive days at 48.1–61.7% from 3 to 12 October, 61.7% (384 of 622) on 6 October, 55.8% (355 of 636) on 12 October, the final plotted day; the rolling seven-day figure bottomed at 42.3% on 3 October and read 53.9% (2,383 of 4,425) at close-out, the calendar week of 5–11 October closed at 54.3% against the 56.0% record week and the 37.8% of August, and no day read below 25% after 28 September. Bucharest's own cell set a series high of 61.1% (460 of 753) on 6 October and closed its highest full week at 53.4%; the Bucharest FIR (LRBB) read 4.8% on 12 October, its highest since 12 September and still inside the band it has held since 8 September (FIR-level), 4.1% over seven days against 3.5% over 90. Observed traffic at Bucharest Henri Coandă stepped down about ten percent from 1 October — about 330 movements a day across 1–10 October against about 367 in September — a step that was in place before the cell's rise and did not move with it; we record it and do not attribute it. The closing block at the end of this page carries the full account. Written 3 October: Over the 45°N 25°E cell — the southern Carpathians and Prahova Valley, 90–130 km north-west of Bucharest — Friday 2 October 2026 read 52.1% of tracked aircraft (306 of 587) broadcasting a low Navigation Integrity Category, after Thursday 1 October fell to 30.6% (188 of 615), the cell's third-lowest day since 19 August (FlySafe monitoring, crowdsourced ADS-B network; a floor, not a total; 14 September is a gap in our per-cell feed). Five days, five reversals: 18.7% on 28 September, 40.5% on 29 September, 46.8% on 30 September, 30.6% on 1 October, 52.1% on 2 October — each day moving against the one before, inside a 33-point band, which is an intermittent signal rather than either a hot run or a cooling one. 52.1% is above only the two lowest of the ten days from 18 to 27 September (45.4% and 45.9%) and below the other eight, which ran up to 63.1%, and the rolling seven-day figure is 43.5% (1,816 of 4,175 aircraft) — down from 59.4% nine days earlier, and up eight tenths of a point on the day. The 1 October dip settles part of a question we left open, against our own caveat: it came on 615 tracked aircraft, inside the cell's ordinary 546–693 range, with the whole inland band sampling 9,870 aircraft against 10,000 the day before. We had written that a low flag rate on a full sample would weaken the coverage explanation for 28 September's 18.7%; that is what 1 October delivered, so the flag rate here moves independently of how many aircraft we receive. 28 September's own 461-aircraft sample was still the thinnest since 12 August, so a narrower caveat stays on that one day. The swings are band-wide, not one cell: across the inland band of central Romania (44–47°N, 22–27°E) the flagged share went 22.5% on 27 September, 11.0% on 28 September, 24.6% on 29 September, 29.9% on 30 September, 17.9% on 1 October and 29.2% on 2 October, against 27.7–39.7% across 21–26 September — with Bucharest's own cell stepping 43.1% → 31.7% → 46.1%, Sibiu's 36.6% → 23.3% → 38.4% and Cluj's 39.4% → 16.7% → 38.4% over the same three days, and the Black Sea coast cells moving with the band on both of them (33–40% on 1 October, 41–46% on 2 October). The trend before this week was up: September closed at 49.5% of aircraft flagged (8,810 of 17,793 across its 29 observed days) against 37.8% across 10–31 August, the weekly figure climbed 28.1% → 37.2% → 47.9% → 45.0% → 46.8% → 53.6% → 56.0% for the complete week of 21–27 September, the highest in the series, and the seven highest days all fall inside 18–26 September, topped by the 63.1% (422 of 669) of Thursday 24 September. What we do not claim is that five alternating days have settled anything: the week of 28 September aggregates to 38.6% on its five observed days (1,106 of 2,865), October's two days to 41.1% (494 of 1,202), and a full week is what would tell us whether this is a step down from the record week or a run of noise around the same level. Bucharest's own cell (44°N 26°E, covering Henri Coandă and Băneasa) read 46.1% (348 of 755 aircraft) on 2 October, 40.4% over seven days, and rose from 38.2% in August to 46.9% in September — the same sign, a few points behind. At FIR scale the picture is far milder and labelled as such: the Bucharest FIR (LRBB) averaged 3.1% over the last 7 days against a 3.4% 90-day average, and read 3.3% on 2 October after 2.2% on 1 October (FIR-level, high confidence) — 1 October is now a settled second break below the 3.0–5.3% band the FIR had held since 8 September, tying 15 August as its lowest day since 4 August. Observed traffic at Bucharest Henri Coandă (OTP) stayed in its normal range, reading 340 movements on Thursday 1 October — the latest plotted day, the softest Thursday in the window but above its four lowest days overall — while the cell that day was quiet, not hot; 29 September is left as a gap because our collection that day has a midday hole. 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 Bucharest or across Romania? The short version
  • This brief closed on 13 October 2026. Bucharest (OTP) kept operating throughout: observed movements averaged about 367/day across September and 330/day across 1–10 October — a step down of about ten percent that was in place from the first days of the month, before the interference cell rose, and that we do not attribute to it. 29 September is left as a gap because the day has a four-hour hole in our collection. Check your airline on the day.
  • The airspace north-west of the city — the Carpathian foothills between Ploiești and Brașov — saw the share of aircraft flagging degraded navigation climb from 38% in August to 49.5% in September, with the week of 21–27 September the highest full week in the series at 56.0% and a 63.1% peak on 24 September. Five alternating days followed (18.7% to 52.1%), and then the cell settled rather than cooled: ten consecutive days at 48–62% from 3 to 12 October, 55.8% on the final day, the week of 5–11 October at 54.3%, the seven-day figure at 53.9%. No return to the August level. Bucharest's own cell set its series high of 61.1% on 6 October and read 49.8% on 12 October, 52.0% over the week.
  • The zone has a gradient, not a wall, and on 12 October, the final plotted day, it ran the same way it had on 2 October: 13.3% of aircraft were flagged at 22°E over western Romania, 47.0% at 24°E near Sibiu, 55.8% at 25°E, 66.1% at 26°E over the Buzău side — against 49.8% over Bucharest, 42.0% on the Bulgarian Black Sea coast, and 2.0–14.1% across the Danube over inland northern Bulgaria. Over the seven days to 12 October every cell in the band read higher than it had across September; the Bulgarian cells did not.
  • 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

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 cell that tripped our threshold is the 1°×1° box centred on 45°N 25°E — the southern Carpathians and the Prahova Valley between Ploiești and Brașov, roughly 90–130 km north-west of Bucharest and under the arrival and departure tracks between the capital and Transylvania and central Europe. It is not Bucharest's own cell; that one sits one box to the south-east and is reported separately below. In its first week (10–17 August) this cell read 16.5–42.1%; over 1–30 September it ran 18.7–63.1%; its first two October days read 30.6% and 52.1%. The week of 21–27 September closed at 56.0% (2,585 of 4,619 aircraft) — still the highest full week in the series, ahead of the 47.9% of the week of 24 August; the week of 14 September read 53.6% on its six observed days. The highest single day is still Thursday 24 September — 63.1% (422 of 669 aircraft), then 62.6% (21 Sep), 62.0% (26 Sep, 430 of 693) and 61.8% (18 Sep), and the seven highest readings in the 53-day series all fall inside 18–26 September. What has happened since is not a trend but an alternation: Monday 28 September fell through the floor of the run at 18.7% (86 of 461), 52nd of 53 days and the lowest reading since 13 August; Tuesday 29 September read 40.5% (235 of 580); Wednesday 30 September 46.8% (291 of 622); Thursday 1 October fell again to 30.6% (188 of 615), the cell's third-lowest day since 19 August; and Friday 2 October came back to 52.1% (306 of 587). Five consecutive days, each one moving against the day before, inside a 33-point band. So the deepest single-day fall in the series lasted one day, as the three earlier pullbacks had — 45.4% on 27 September, 45.9% on 25 September, 52.8% on 22 September, each recovered the next day — but a second dip arrived three days later, and the series now looks intermittent rather than either hot or cooling. We say plainly where 2 October sits: 52.1% is above only the two lowest of the ten days from 18 to 27 September (45.4% and 45.9%) and below the other eight, which ran up to 63.1%. None of 63.1%, 18.7%, 30.6% or 52.1% is the level, and the weekly figure is what carries the claim: 28.1% in the week of 10 August, then 37.2%, 47.9%, 45.0%, 46.8%, 53.6% across the six observed days of the week of 14 September, and 56.0% across the full week of 21 September; the week of 28 September has five observed days at 38.6% (1,106 of 2,865) and no weekly figure yet. 14 September is not plotted: our per-cell feed holds no data for that day in any cell — a collection gap, not a reading. Honesty note: this per-cell series begins on 10 August, so it is 53 observed days deep and we make no claim about a longer baseline. The cell is busy — 439–710 tracked aircraft a day across the series, 546–693 across 1–27 September — so single-day percentages here are steadier than on a thin cell. And the sample question we flagged on 28 September has now been partly answered, against our own caveat: 1 October's 30.6% came on 615 aircraft, squarely inside the ordinary range, with the whole inland band sampling 9,870 aircraft against 10,000 the day before. A low flag rate on a full sample is exactly the test we said would weaken the coverage explanation, and it fired — the flag rate moves independently of how many aircraft we receive. 28 September's own 461-aircraft sample was still the thinnest since 12 August, so we keep a narrower caveat on that one day rather than drop it. The cell's Sundays have run 40.4%, 43.3%, 52.0%, 28.6%, 57.0%, 58.5% and 45.4%, its Mondays 29.5%, 42.1%, 45.9%, 37.6%, 32.9%, 62.6% and 18.7%, its Thursdays 16.5%, 38.9%, 48.9%, 44.7%, 53.7%, 51.5%, 63.1% and now 30.6%, and its Fridays 36.5%, 32.9%, 52.6%, 52.4%, 52.2%, 61.8%, 45.9% and now 52.1% — too wide a spread on any of those weekdays to read any single day as a calendar effect. Close-out, 13 October: the alternation stopped the day after that passage was written. From Saturday 3 October to Monday 12 October the cell posted ten consecutive days inside a 48.1–61.7% band — 54.7%, 50.6%, 59.1%, 61.7% (384 of 622) on Tuesday 6 October, the fifth-highest of the 63 observed days, 52.3%, 51.8%, 55.1%, 48.1%, 52.8% and 55.8% (355 of 636) on 12 October, the final plotted day — on samples of 593–702 aircraft. The calendar week of 28 September–4 October closed at 43.0% (1,796 of 4,172), inside the 35–45% band this page said would file 18–26 September as a hot run that peaked; the next week, 5–11 October, closed at 54.3% (2,384 of 4,391), within two points of the record week, so that filing did not hold. The rolling seven-day figure bottomed at 42.3% on 3 October and read 53.9% (2,383 of 4,425) on 12 October. October's first twelve days aggregate to 52.1% (3,923 of 7,536) against 49.5% across September and 37.8% across 10–31 August. No day read below 25% after 28 September, and no full week read above 60%. Every count is a floor — solely aircraft the crowdsourced receiver network received are included. Daily share of aircraft flagging degraded navigation in the cell:

47.6
1 Sep
49.9
2 Sep
44.7
3 Sep
52.4
4 Sep
52.6
5 Sep
28.6
6 Sep
32.9
7 Sep
42.8
8 Sep
37.6
9 Sep
53.7
10 Sep
52.2
11 Sep
50.9
12 Sep
57
13 Sep
47.6
15 Sep
42.1
16 Sep
51.5
17 Sep
61.8
18 Sep
57.9
19 Sep
58.5
20 Sep
62.6
21 Sep
52.8
22 Sep
58.9
23 Sep
63.1
24 Sep
45.9
25 Sep
62
26 Sep
45.4
27 Sep
18.7
28 Sep
40.5
29 Sep
46.8
30 Sep
30.6
1 Oct
52.1
2 Oct
54.7
3 Oct
50.6
4 Oct
59.1
5 Oct
61.7
6 Oct
52.3
7 Oct
51.8
8 Oct
55.1
9 Oct
48.1
10 Oct
52.8
11 Oct
55.8
12 Oct

Fig. 1 — daily share of tracked aircraft broadcasting a low Navigation Integrity Category (NIC) in the 45°N 25°E cell (southern Carpathians / Prahova Valley, north-west of Bucharest), % — crowdsourced ADS-B network · Data as of 13 Oct 2026, 16:15 UTC · closed · per-cell series complete through 12 Oct (14 Sep a gap), traffic through 10 Oct (29 Sep a gap; 11 Oct provisional, not plotted) · Source: FlySafe monitoring — crowdsourced ADS-B navigation-integrity data (public).

Airports in the exposure zone

AirportSizeExposure (12 Oct, at close-out)FIR
Bucharest Henri Coandă (OTP) large — · ≈49.8% of aircraft flagged on 12 Oct (own cell 44°N 26°E, 387 of 777; 52.0% over 7 days) · traffic ~10% under September, not attributed LRBB
Bucharest Băneasa (BBU) medium — · shares Bucharest's cell — ≈49.8% flagged on 12 Oct (52.0% over 7 days) LRBB
Brașov-Ghimbav (GHV) medium — · inside the trigger cell — ≈55.8% flagged on 12 Oct (355 of 636; 53.9% over 7 days) LRBB
Sibiu (SBZ) medium — · western edge — ≈47.0% flagged on 12 Oct (own cell 45°N 24°E, 358 of 761; 42.7% over 7 days) LRBB
Cluj Avram Iancu (CLJ) large — · ≈56.9% flagged on 12 Oct (own cell 46°N 23°E, 334 of 587; 43.2% over 7 days) LRBB
Constanța Mihail Kogălniceanu (CND) medium — · ≈42.4% flagged on 12 Oct (own cell 44°N 28°E, 28 of 66 — thin sample; 51.2% over 7 days) LRBB

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: Bucharest traffic stepped down about ten percent at the start of October — before the cell's rise, and not in step with it

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. Bucharest Henri Coandă's last 30 days:

Fig. 2 — Observed daily movements at OTP, 10 Aug – 10 Oct (latest complete UTC day). Data as of 13 Oct 2026, 16:15 UTC · closed · per-cell series complete through 12 Oct (14 Sep a gap), traffic through 10 Oct (29 Sep a gap; 11 Oct provisional, not plotted) · Source: FlySafe monitoring (ADS-B receiver network).

  • Across the 10 Aug–1 Oct window plotted above: ~373 observed movements/day, averaged over the 52 plotted days — the 377 reference line was set on the first 40 days and is kept stable so the series stays comparable across updates. On every plotted day, network-wide collection ran at 88% or more of the window's median day, and the lowest of those are Sundays and Saturdays, when traffic itself is lower. One day inside the run, Tuesday 29 September, is left as a gap — an empty slot, not a reading — because our collection at OTP that day has a hole in the middle of it; that is set out below. Observed counts are a floor, not a total.
  • Through the September swings in the cell (1–30 Sep, 29 September a gap): 392 / 404 / 389 / 379 / 336 / 393 / 390 / 315 / 377 / 351 / 382 / 337 / 380 / 372 / 352 / 375 / 378 / 377 / 328 / 372 / 376 / 328 / 372 / 369 / 371 / 333 / 376 / 366 / — / 383 observed movements — a September mean of about 367/day over the 29 plotted days against about 382/day over 10–31 August. A four-percent difference is inside the day-to-day noise of the series: the two lowest days in the window remain Saturday 22 August (312) and Tuesday 8 September (315), both before the cell's late-September climb, and 18 September — the first day the cell crossed 60% — read 377, exactly the reference.
  • The latest plotted day is the window's softest Thursday, and we neither hide it nor promote it to a signal. Thursday 1 October read 340 movements (177 departures, 163 arrivals), below the window's other Thursdays of 374, 370, 409, 389, 351, 378 and 369 — but above its four lowest days overall (312, 315, 328, 328) and the third-lowest Monday-to-Friday day in the whole run. One weekday at the bottom of a spread is not a trend, and the cell was quiet that day (30.6%), which is the opposite of the pairing a traffic effect from interference would produce. The day before, Wednesday 30 September, read 383 — the second-highest Wednesday in the window after 404.
  • The softening we flagged still sits a fifth of a movement a day from a week that precedes the cell's climb, so the claim stays downgraded. The last complete seven-day window, to 28 September, averages 359.3/day; 8–14 September averages 359.1/day, the softest week in the window. Two tenths of a movement a day is not a separation in either direction. What the spread does say is that the whole window is narrow: the 44 complete seven-day averages inside it run 359–414/day, and that last week is at the bottom of that range rather than outside it — the last five of those averages read 360.3, 359.4, 360.1, 360.7 and 359.3, which is a flat line. The gap on 29 September means no new seven-day average can be formed until the window ending 6 October; the six plotted days of 25 September–1 October average 361.5/day. We will call traffic a signal only if a full week falls below the window's range while the cell stays hot; it has not.
  • Coverage notes, and a correction in place: Wednesday 30 September is now plotted at 383 (204 departures, 179 arrivals), six more than the 377 we published last update — late detections, the fifth update in six in which the latest bar later gained a handful of movements. The daily rollup disagrees in the other direction: today's re-ingest left it holding 247 for 30 September, and the OTP airport brief currently shows that figure, which is the wall-clock clipping artefact landing on a settled day. The hour-by-hour profile for 30 September is full across the operating day and network-wide collection that day ran above the window's median, so the recount is what we plot. Tuesday 29 September remains the gap in the chart: rollup and recount now agree at 278 movements (149 departures, 129 arrivals), unchanged from last update, and the day's profile still has the hole — 10, 8, 2 and 0 movements in the 11:00–14:00 UTC hours against 14–28 in those hours on each of the five days before and 15–26 on the day after. Network-wide collection that day ran at 87% of the window's median, the lowest of any day in the window. A day with a hole in the middle of it is not a soft traffic day, and we leave the slot empty rather than publish it as one. Thursday 1 October is plotted at 340: rollup and recount agree, the hourly profile is full across the operating day (22, 20, 17 and 17 movements in those same four midday hours), and network-wide collection ran at 99% of the window's median. A latest bar can still gain a handful of movements on late detections. 2 October has barely started arriving — 18 movements, all departures, with the network-wide feed at about 6% of a normal day — and is not plotted.
  • A note on the baseline: OTP's airport brief compares each day with the same weekday, so its reference moves — its latest day is Thursday 1 October at 340 movements against a 378 same-weekday reference, which it reads as normal at −10%. On this page the latest plotted day is that same Thursday at 340, ten percent under the window-level ~377 reference. Three weekday floors stand as recorded: Monday 28 September's 366 is the second-softest Monday in the window after 24 August's 348, against Mondays of 391, 394, 425, 390, 372 and 376; Sundays in the window have run 372–455 (404, 385, 455, 393, 380, 372, 376), so the four September Sundays step 393 → 380 → 372 → 376 and the drift we flagged earlier has stopped; and 26 September's 333 is the third-lowest Saturday after 312 (22 August) and 328 (19 September). All of this is inside the ordinary spread of the series.
  • 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. The bars show an ordinary early-autumn profile across the whole run, through the cell's 63.1% record on 24 September, its 18.7% collapse on 28 September, its 46.8% on 30 September, its 30.6% on 1 October and its 52.1% on 2 October — and the one empty slot, 29 September, is our collection, not the airport.
  • Close-out, 13 October — the record through 10 October, and a test that fired on the numbers. Nine days were added at close-out, each the raw recount of our flight records with a full hourly profile: 360 / 294 / 335 / 345 / 309 / 342 / 332 / 348 / 295 observed movements across Friday 2 to Saturday 10 October (10 October from the recount, 163 departures and 132 arrivals, because the daily rollup had clipped that day to 98 and the OTP airport brief flags it as a gap). One correction in place: Thursday 1 October, published at 340, settled at 344 (180 departures, 164 arrivals) on late detections — the sixth such correction in seven updates. Sunday 11 October reads 344 in both the rollup and the recount but is not plotted: network-wide collection for that day stood at 81% of the window's median at close-out and was still filling; the OTP airport brief reads it as normal at −9% against a 376 Sunday reference. The plotted-day collection floor, recomputed over the whole window, is about 88% (6 September 87.8%, 10 October 88.6%); 5–9 October ran at 98–108%. What the ten October days show is a step, not a swing: they average 330 movements a day against about 367 across September and 382 across 10–31 August, and every one of them is the softest of its weekday in the window — Monday 345 (prior low 348), Tuesday 309 (315), Wednesday 342 (363), Thursday 332 and 344 (351), Friday 348 and 360 (371), Saturday 294 and 295 (312), Sunday 335 (372). The five complete seven-day windows ending 6–10 October average 338.6, 332.7, 331.0, 329.3 and 329.4 a day; the 44 windows to 28 September ran 359.1–414.3. That is the condition this page set for calling traffic a signal — a full week below the window's range while the cell stays hot — and on the numbers it was met: the week of 5–11 October closed at 54.3% in the cell. We record that and still do not attribute the step to interference, for a reason the dates make plain: the step is already present on 1–4 October (344, 360, 294, 335 — each the lowest or second-lowest of its weekday), when the cell was at its quietest of the whole run (seven-day figure 42.3–43.5%), and it did not deepen as the cell rose — about 333 a day across 1–4 October, about 329 across 5–10 October, while the cell's seven-day figure climbed from 42.3% to 53.9%. A uniform eight-to-ten-percent step across every weekday from the first days of a month, flat while the navigation layer moved, is the shape of a schedule change between the summer and autumn seasons rather than of a navigation-layer effect; our data cannot separate the two, and our NOTAM feed carries no Romanian items, so there is no regulatory signal to test against either. The two softest days, the Saturdays of 3 and 10 October, also fell on thinner network collection (91% and 89% of the median), which accounts for part of those two readings and none of the weekday ones. Observed counts remain a floor, not a total.

Live view: OTP airport brief.

What it means for flights

The news is the climb, and then five days that reverse each other. Romanian airspace has carried elevated GNSS interference since the war in Ukraine brought electronic-warfare reach across the Black Sea basin (background: the Plovdiv jamming incident of 2025 and how GPS jamming works). What our detection layer has caught is not a new zone but a steady intensification inland, over the Carpathian foothills north-west of the capital. Aggregated over comparable samples — 13,001 tracked aircraft across 10–31 August, 17,793 across 1–30 September — the flagged share in the 45°N 25°E cell moved from 37.8% to 49.5%, and the weekly figure climbed in steps: 28.1% → 37.2% → 47.9% → 45.0% → 46.8% → 53.6% → 56.0% for the complete week of 21–27 September, the highest full week in the series. From 10 September to 27 September the cell did not post a day below 42.1%; the seven highest days in the series are all inside 18–26 September, topped by 24 September's 63.1%, then 62.6% on 21 September and 62.0% on 26 September. A twelve-point rise on samples of thirteen and nearly eighteen thousand aircraft is not noise. What we never claimed was a level, and the five days since the record week are why that restraint mattered — in both directions: 28 September read 18.7% (86 of 461), 44 points off the record day and the lowest since 13 August; 29 September 40.5% (235 of 580); 30 September 46.8% (291 of 622); 1 October 30.6% (188 of 615); 2 October 52.1% (306 of 587). Every one of those five days moved against the day before. Had we called 28 September a turn, 24 hours would have falsified it, as 24 hours falsified the three earlier pullbacks — 52.8% on 22 September, 45.9% on 25 September, 45.4% on 27 September. Had we called 30 September a resumption, 1 October would have falsified that too, which is why we did not. The rolling seven-day figure has gone 59.4% → 57.1% → 57.7% → 56.0% → 51.1% → 49.5% → 47.6% → 42.7% → 43.5% across nine days: down sixteen points from its high, and flat on the last two, while the calendar week of 21–27 September still stands as the highest complete week on record here. Both statements are true at once, and the page carries both. The week of 28 September has five observed days and aggregates to 38.6% (1,106 of 2,865); October's first two days aggregate to 41.1% (494 of 1,202). Neither is a weekly figure, and we will not treat either as one.

A band across Wallachia that stops at the Danube. Interference has a footprint, and on this side of the Black Sea it runs east–west along the 44–46°N band. It went quiet inland on 28 September, came back on 29 and 30 September, went quiet again on 1 October and firmed again on 2 October; the coast moved against the band on the first two of those days and with it on the last two. Along the 45°N row on 2 October the flag rate ran 9.8% at 22°E over the Banat, 18.7% at 23°E, 38.4% at 24°E near Sibiu, 52.1% at 25°E and 60.8% at 26°E over the Buzău side (110 of 181 aircraft) — then 41.7% at 27°E on 24 aircraft and 62.5% at 28°E on 16, both directions rather than measurements. One row south, along 44°N: 5.6% at 22°E, 7.5% at 23°E, 11.6% at 24°E, 32.2% at 25°E, 46.1% over Bucharest at 26°E, 28.8% at 27°E (81 of 281) and 46.4% at 28°E over Constanța on a thin 56 aircraft. Cross the Danube to the 43°N row over northern Bulgaria and the same longitudes read 0.7%, 3.6%, 3.1%, 5.4%, 11.3%, 21.0%, rising toward the Black Sea coast at 28°E (42.7%, 126 of 295) and nowhere else. The day before, 1 October, the same 45°N row had read 7.1%, 12.9%, 23.3%, 30.6% and 37.2%: every inland cell lost between a third and a half of its flag rate and took most of it back the next day, which is the second time in five days the band has done that. Aggregated across the inland band (44–47°N, 22–27°E) the series reads 22.5% on 27 September, 11.0% on 28 September (8,496 aircraft — the second-lowest band-wide day in the series after 8.9% on 13 August), 24.6% on 29 September (9,642), 29.9% on 30 September (10,000), 17.9% on 1 October (9,870) and 29.2% on 2 October (9,670), against 27.7–39.7% across 21–26 September: the band is back inside that range, at its low end, and the sample barely moved across the last four of those days while the flag rate halved and doubled. The seven-day aggregates to 2 October: 43.5% in the trigger cell, 50.6% one cell east, 40.4% over Bucharest, 32.3% near Sibiu, 27.3% over Cluj, 5.6% at 43°N 25°E. With September complete, the August-to-September comparison keeps the same sign in each of these band cells, with the 18.7% day included: 44°N 26°E (Bucharest) 38.2% → 46.9%, 45°N 26°E 40.1% → 55.2%, 46°N 24°E 39.2% → 50.7%, 46°N 25°E 31.3% → 49.5%, 45°N 24°E 28.7% → 37.5%, 44°N 25°E 28.7% → 36.9%, 47°N 24°E 43.5% → 57.0%, and even Cluj's cell 24.7% → 32.9%. Bulgaria did not follow: 43°N 25°E moved 10.7% → 9.9%, 43°N 27°E 25.2% → 24.5%. Through September the zone intensified across central and eastern Romania without spreading south; since 28 September it has switched inland on and off from one day to the next. The cells beyond the trigger cell are doing the same thing in step: Sibiu's cell went 47.1% (26 Sep) → 28.1% → 14.0% → 34.1% → 36.6% → 23.3% → 38.4% against a 32.3% week, Cluj's 34.4% → 22.1% → 9.2% → 28.6% → 39.4% → 16.7% → 38.4% against 27.3%, and the north-western border cell at 47°N 22°E 26.2% → 17.7% → 9.6% → 30.2% → 51.6% → 16.0% → 39.7% against 27.3%. Swings of twenty points on single days, in both directions twice inside five days, are exactly why we change the map only on seven-day figures; on those figures the footprint has neither widened nor narrowed.

FIR-average hides the band — why the cell-level number matters. By the FIR-wide measure, the whole Bucharest FIR (LRBB) sits at 3.1% over the last 7 days against a 3.4% 90-day average, reading 3.3% (743 flagged of roughly 22,800 tracked aircraft) on 2 October — back inside the 3.0–5.3% band it had held since 8 September, after 1 October's 2.2% (537 flagged of roughly 24,500) became the second day below it, tying 15 August as the lowest FIR-level reading since 4 August (FIR-level, high confidence). The August-to-September movement at that scale is 3.7% → 3.5% — flat to slightly down — because the average pools the hot central band with quiet western Romania and, above all, with the high-altitude transit traffic that crosses the FIR on the Europe–Middle East trunk routes, most of which reports healthy integrity. Note what that meant on the days that mattered: 24 September set a record in the cell while the FIR reading went down, to 3.2%; 28 September saw the cell drop 27 points and the FIR reading did not move at all, 3.5% against 3.5%; 29 September, the day the cell recovered 22 points, is the day the FIR figure finally fell, to 2.8%; and only on 30 September and again on 1–2 October did the two move the same way. A measure that registers the record and the collapse in none of the right directions is measuring something else — and on the 90-day scale it is telling the truth about the FIR as a whole. Over the seven days to 2 October the degraded share in the 45°N 25°E cell is about fourteen times the FIR figure, and about sixteen times it on 2 October itself. Both numbers are true; the cell-level one alone tells a dispatcher what the Prahova Valley looks like today. The neighbouring FIRs at the same 7-day scale: Sofia (LBSR) ~3.1% against a ~4.3% 90-day average, Budapest (LHCC) ~0.3%, Belgrade (LYBA) ~0.1%, and Chișinău (LUUU) ~23.0% against ~23.0% — but LUUU's figure rests on roughly 250 tracked aircraft a day and carries low confidence in our feed, so treat it as indicative. The Kyiv FIR (UKBV) returns one or two aircraft a day and is not measurable here. One FIR-wide figure hides the band; the band alone overstates the FIR. We label which scale each number belongs to for exactly that reason.

Interference degrades navigation; it does not ground flights. 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 Bucharest's departure board shows nothing: the traffic section above reads an ordinary early-autumn profile — a September mean of about 367 observed movements a day against about 382 in the second half of August — while around four aircraft in ten over the cell north-west of the city flagged degraded GNSS across the past week, and the board looked no different on the days the cell went quiet or on the days it came back. The latest plotted day makes the point from the other side: 1 October was the window's softest Thursday and one of the cell's quietest days, which is the wrong way round for a traffic effect.

Honest arithmetic on a busy cell. The 45°N 25°E cell saw 546–693 tracked aircraft a day across 1–27 September — a large sample by the standards of this series, which is why a single day here carries more weight than on the thin Baltic and Finnish cells we have covered. Even so, a Sunday can move the figure by twenty points on the mix of traffic alone (28.6% on 6 September against 57.0% and 58.5% on the two Sundays after), so the climb is claimed on the weekly and monthly aggregates — roughly 4,600 aircraft a week — and never on a single day. The last nine days are the case for that discipline in both directions. We reported 63.1% as a series high and wrote that it was not the level; 25 September came in at 45.9%. We reported that pullback and wrote that it was not a turn; 26 September came in at 62.0%. We reported that recovery and declined to call a level; 27 September came in at 45.4%. We reported that and declined to call a turn; 28 September came in at 18.7%. We reported that and declined to call an ending; 29 September came in at 40.5%, then 30 September at 46.8%. We reported that bounce and expressly declined to call it a resumption; 1 October came in at 30.6%. We reported nothing as settled, and 2 October came in at 52.1%. Any one of those days, called a plateau, a peak or an ending, would have been falsified inside 24 hours, while the seven-day figure moved 59.4% → 43.5% across the same nine days — the only line here that has moved in one direction, and it has been flat for the last two. The sample caveat has now been tested, and it fails for the general case: we wrote that if the cell's aircraft count returned to the 546–693 range while the flag rate stayed low, the coverage caveat would fall away. On 1 October the count was 615 — ordinary — and the flag rate was 30.6%, with the inland band sampling 9,870 aircraft against 10,000 the day before and network-wide collection running at its highest of the week (1.24 million aircraft-cell observations on 1 October, 1.26 million on 2 October, against 1.22 million on 28 and 30 September and 1.20 million on 29 September). A low day can therefore arrive on a full sample, so coverage is not the explanation for low days in general. What survives is narrower: 28 September's own sample of 461 aircraft was still the thinnest since 12 August and about a quarter below the September range, and every neighbouring Romanian cell sampled 10–25% fewer aircraft that same day, so we keep the caveat on that single reading and have dropped it for the rest. All days are plotted as measured. A day with no data at all, like 14 September, is left out rather than filled in. The same discipline governs the traffic section, where two corrections stand on the record this update: Wednesday 30 September, published at 377, has settled at 383 on late detections — the fifth such correction in six updates, each made in place and stated rather than quietly redrawn — while the daily rollup has gone the other way and now shows that day at 247, a wall-clock clipping artefact that the OTP airport brief is currently displaying and that the hour-by-hour profile contradicts. Tuesday 29 September is left as a gap for a different reason: not a late day but a holed one, missing most of four midday hours, and a further two days of late detections have not filled the hole. Two of the cells in this brief — Constanța's (56 aircraft) and the 27°E cell east of Buzău (24) — are flagged as thin samples for the same reason. Every figure here is an aggregate of crowdsourced receiver telemetry: a floor, not a total.

What would change the picture. Written 3 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, where the cell settles after the 18.7% / 40.5% / 46.8% / 30.6% / 52.1% sequence: the week of 21–27 September closed at 56.0%, the highest complete week in the series, and the rolling seven-day figure has eased from 59.4% to 43.5% across nine days. A full week above 60%, which we have not seen, is still what a new level would look like; a full week in the 35–45% band would file 18–26 September as a hot run that peaked; a second day below 25% inside the same week would be the first such pair since mid-August, and 1 October's 30.6% came within six points of it. Five days decide none of those, and the five-day alternation is itself the thing to watch: if the cell keeps switching between roughly 30% and roughly 50% from one day to the next, the honest description is intermittent jamming at a lower duty cycle than late September, not an ending. Second, Bucharest's own cell (44°N 26°E, 46.1% on 2 October, 40.4% over 7 days) following the trigger cell across 60% — that would put the strongest interference directly over the capital's terminal airspace rather than on its north-western approaches; its best single day so far is the 60.8% of 10 September and its weekly figure is twenty points short. Third, the FIR-level LRBB ratio breaking decisively out of the band it held from 8 September rather than oscillating around it — it read 3.2% on the cell's record day, 3.5% on 28 September, unmoved by the cell's collapse, then 2.8% on 29 September, 3.2% on 30 September, 2.2% on 1 October — tying 15 August as its lowest since 4 August — and 3.3% on 2 October, back inside. Two sub-3% days in four is the closest thing to a FIR-scale signal this series has produced, and we will call it one only on a seven-day figure. The cells beyond the trigger cell have now answered five times in five days — down, up, up, down, up — so the footprint is neither widening nor demonstrably contracting; that is a question for the next seven-day figure rather than for one day. A fourth signal — regulatory action, meaning NOTAMs suspending satellite-based approach procedures at Romanian airports — would be the clearest operational marker, and we flag its absence honestly: our NOTAM feed currently carries no Romanian items at all, so its silence here is a gap in our coverage, not evidence that nothing has been issued. This page updates from the same monitoring cycle as the OTP brief, the Romania airspace page and the live regional GPS-interference map.

What the data showed: close-out, 13 October. This brief opened on 22 September to track a September climb in the 45°N 25°E cell and stayed open through the five alternating days that followed the record week. It closes on 13 October with both on the record and no recovery to report: the interference did not end, it settled. The cell. The alternation stopped on 3 October. From 3 to 12 October the cell posted ten consecutive days inside a 48.1–61.7% band — 54.7%, 50.6%, 59.1%, 61.7%, 52.3%, 51.8%, 55.1%, 48.1%, 52.8%, 55.8% — on samples of 593–702 aircraft; 6 October's 61.7% (384 of 622) is the fifth-highest of the 63 observed days, behind four days from 18–26 September. The rolling seven-day figure bottomed at 42.3% on 3 October, rose back to 55.1% by 9 October and closed at 53.9% (2,383 of 4,425) on 12 October. The calendar weeks settle what five days could not: 28 September–4 October closed at 43.0% (1,796 of 4,172) and 5–11 October at 54.3% (2,384 of 4,391), within two points of the 56.0% record week. October's first twelve days aggregate to 52.1% (3,923 of 7,536) — against 49.5% across September and 37.8% across 10–31 August, the level this page would have needed to see again to call a recovery. The tests this page set, answered. A full week above 60%: not seen (43.0%, 54.3%). A full week in the 35–45% band, which would have filed 18–26 September as a hot run that peaked: seen once, 43.0% for the week of 28 September, and reversed by the week after — so the hot run did not peak; it became the level. A second day below 25%: none; no day read below 30.6% after 28 September and none below 48.1% after 2 October. Bucharest's own cell (44°N 26°E) crossing 60%: on one day — 61.1% (460 of 753) on 6 October, the highest in its series, ahead of the 60.8% of 10 September — and its week of 5–11 October closed at 53.4% (2,921 of 5,471), its highest full week, with 52.0% over the seven days to 12 October and 49.8% (387 of 777) on the final day; it followed the trigger cell up without matching it. The Bucharest FIR (LRBB) breaking out of its band: it did not. After the 2.2% of 1 October it read 3.3%, 3.1%, 3.2%, 3.9%, 3.7%, 3.7%, 3.5%, 4.2%, 4.6% and 4.8% on 12 October — its highest since 12 September and inside the 2.2–5.3% span it has held since 8 September — with the seven-day average at 4.1% (about 23,000 tracked aircraft a day) against a 90-day average of 3.5%, where on 2 October the seven-day figure had sat below the 90-day (FIR-level, high confidence). Three rising days at the end of the record are three days, and the FIR average still pools the hot band with quiet western Romania and high-altitude transit. Neighbours over the same seven days: Sofia (LBSR) 3.9%, Budapest (LHCC) 0.4%, Belgrade (LYBA) 0.1%, Chișinău (LUUU) 27.3% on about 210 aircraft a day, low confidence; the Kyiv FIR is not measurable in our feed. The footprint. Aggregated across the inland band (44–47°N, 22–27°E) the daily flag rate ran 28.2–37.0% from 3 to 12 October, 33.6% (23,386 of 69,693 aircraft) over the seven days to 12 October — back inside the 27.7–39.7% of 21–26 September, with no repeat of the band-wide halving of 28 September and 1 October. Over those seven days every cell in the band read above its September figure: 44°N 26°E (Bucharest) 46.9% → 52.0%, 45°N 26°E 55.2% → 65.8%, 46°N 24°E 50.7% → 59.0%, 45°N 24°E (Sibiu) 37.5% → 42.7%, 44°N 25°E 36.9% → 39.0%, 46°N 23°E (Cluj) 32.9% → 43.2%. Across the Danube, 43°N 25°E read 11.6% against 9.9% in September and 43°N 27°E 25.7% against 24.5%. The zone deepened in place through its sixty-third observed day and did not spread south; the 45°N 26°E cell east of this one, which crossed 70% on 6 October, has its own October brief. Regulatory signal. Our NOTAM feed still carries no Romanian items at close-out, so its silence on satellite-based approach procedures remains a gap in our coverage, not a finding. Traffic. Bucharest Henri Coandă recorded 344, 360, 294, 335, 345, 309, 342, 332, 348 and 295 observed movements across 1–10 October — about 330 a day against about 367 across September and 382 across 10–31 August — and every one of those ten days is the softest of its weekday in the 62-day window. The five complete seven-day windows ending 6–10 October average 329–339 movements a day, below the 359–414 range of every window to 28 September; the week of 5–11 October closed at 54.3% in the cell. That is the test this page set for calling traffic a signal, and it was met on the numbers. We record it and withhold the attribution, because the step was already in place on 1–4 October, when the cell was at its quietest of the run (seven-day 42.3–43.5%), and it stayed flat — about 333 a day across 1–4 October, about 329 across 5–10 October — while the cell's seven-day figure climbed from 42.3% to 53.9%: a uniform step at the turn of a month that does not move with the navigation layer is the shape of a seasonal schedule change, and our data cannot separate the two. The airport's own brief reads the latest day, Sunday 11 October, as normal at −9% against its 376 same-weekday reference. The traffic section above sets out the collection checks behind each day. What this brief did not do is call a peak, a plateau or an ending on any single day, and the record shows why: 28 September's collapse, 30 September's bounce and 1 October's dip were each reversed within 24 hours, and the one line that had moved in a single direction across the whole run — the seven-day figure — turned around on 3 October and ended 11.6 points above its low. Per-cell readings for this region continue in the live regional GPS-interference map and the Airspace Indices tool, and the airport's traffic in the OTP brief. Every figure here is an aggregate of crowdsourced receiver telemetry — a floor, not a total — and procedures and go/no-go decisions belong to operators and authorities.

Passenger questions, answered from the data

Is GPS jamming affecting flights to Bucharest right now?

As of 13 October 2026 this brief is closed, and the closing numbers are not a recovery. The airspace cell over the Carpathian foothills north-west of Bucharest (45°N 25°E) read 55.8% of tracked aircraft flagging degraded navigation on Monday 12 October, the final plotted day, after ten consecutive days at 48.1–61.7% from 3 October; the seven-day figure was 53.9% and the week of 5–11 October closed at 54.3%, against 56.0% for the record week of 21–27 September and 37.8% across August. Bucharest's own cell read 49.8% on 12 October, 52.0% over the week, after a series high of 61.1% on 6 October. Observed traffic at Bucharest Henri Coandă (OTP) ran about 330 movements a day across 1–10 October against about 367 in September — a step that was in place before the cell rose and that we do not attribute to the interference. Aircraft in the affected area broadcast degraded navigation but continue operating on back-up systems. Current readings are on the live regional map and the OTP brief; check your airline's status on the day of travel.

Has the GPS interference over Romania got worse?

Over central and eastern Romania it got measurably worse through September, and has since switched on and off from one day to the next: in the 45°N 25°E cell 49.5% of tracked aircraft flagged across 1–30 September against 37.8% across 10–31 August, with the weekly figure climbing from 28.1% to 56.0% for the complete week of 21–27 September and the seven highest days in the series all falling inside 18–26 September, topped by 63.1% on 24 September. Then came five alternating days — 18.7% on 28 September, 40.5%, 46.8%, 30.6% on 1 October and 52.1% on 2 October — with every inland cell across the band moving in step on each of them. It is a swinging series rather than a fixed level (22 September 52.8%, 25 September 45.9%, 27 September 45.4% inside the same run), so the seven-day figure — now 43.5%, sixteen points off its high and flat over the last two days — is the number to read, and five days cannot say whether the run has peaked. Eight further cells across the 44–47°N band between 23°E and 26°E rose by eight to eighteen points on the August-to-September comparison — Bucharest's own cell from 38.2% to 46.9% — while the cells across the Danube over northern Bulgaria did not move. Averaged across the whole Bucharest FIR (LRBB) the change is 3.7% → 3.5% — a FIR-level number, deliberately much lower than the cell, because it pools the band with quiet western Romania and high-altitude transit traffic. At close-out on 13 October the answer had firmed: the cell settled at 48.1–61.7% across 3–12 October (week of 5–11 October 54.3%, seven-day 53.9%), every band cell read above its September figure over the seven days to 12 October, the Bulgarian cells did not, and the FIR-level LRBB figure stood at 4.1% over seven days against 3.5% over 90.

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. The 45°N 25°E cell saw 546–693 aircraft a day across 1–27 September, then 461 on 28 September — its smallest sample since 12 August — and 580, 622, 615 and 587 across 29 September to 2 October. That matters for one specific reason: 1 October's low reading of 30.6% arrived on an ordinary 615-aircraft sample, which is the test we said would show that low readings are not a coverage artefact. It fired, so the caveat now applies only to 28 September's thin day. We report the climb, and any fall, on weekly and monthly aggregates rather than on single days.

Why does Bucharest’s traffic look normal if about half the aircraft over the cell are flagging?

Because the two measure different layers. The 56.0% figure for the week of 21–27 September counts aircraft broadcasting degraded position quality in a specific airspace cell; the traffic figure counts departures and arrivals at the airport. Interference degrades a navigation source with documented back-ups — it does not close a runway — so it leaves no signature in the movement count. Bucharest averaged about 373 observed movements a day over the 52 plotted days to 1 October, about 367 a day in September against about 382 in the second half of August — a difference inside the day-to-day noise. Three honest caveats: the latest plotted day, Thursday 1 October, read 340, the softest Thursday in the window, though above its four lowest days overall and recorded on a day when the cell itself was quiet at 30.6%; the last complete seven-day window, to 28 September, at 359.3 a day, sits two tenths of a movement above 8–14 September's 359.1, the softest week in the window — and that week sits before the cell's climb; and 29 September is left as a gap here because the day has a hole in our collection across four midday hours, not because traffic fell. Both weeks are inside the window's 359–414 spread of seven-day averages, so neither separates interference from ordinary variation. At close-out the picture had changed in one respect: across 1–10 October the airport ran about 330 movements a day, about ten percent under September, with every day the softest of its weekday in the window — a step that was in place from 1 October, before the cell rose, and did not move with it; the close-out block sets out why we record it and do not attribute it.

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 Carpathian foothills north-west of Bucharest, the share of tracked aircraft broadcasting degraded navigation integrity settled at 48–62% a day across 3–12 October 2026 after five alternating days at the turn of the month, reading 55.8% on 12 October with a seven-day figure of 53.9% — against 56.0% for the record week of 21–27 September and 37.8% across August — so the monitoring brief closed on 13 October with no recovery to report. Bucharest's own airspace cell set a series high of 61.1% on 6 October, the wider Bucharest flight-information region averaged 4.1% over the final week, and Henri Coandă airport's observed traffic ran about ten percent under its September level across 1–10 October, a step that preceded the cell's rise and is not attributed to it, according to flight-monitoring service FlySafe.zone.”

Chart: observed traffic at OTP
PNG · 1600px · attribution baked in
Observed daily movements at OTP — 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 45°N 25°E cell (southern Carpathians / Prahova Valley, north-west of Bucharest), % — 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 North of Bucharest Swings Back to 52.1% on 2 October 2026 After 30.6% a Day Earlier — Five Days of Alternating Readings Since the One-Day Collapse to 18.7%, the Seven-Day Figure Down to 43.5% From 59.4%, and the 1 October Dip Arriving on a Full Sample, Which Weakens the Coverage Caveat We Flagged", https://flysafe.zone/events/gnss-otp-2026-09/, data as of 13 Oct 2026, 16:15 UTC · closed · per-cell series complete through 12 Oct (14 Sep a gap), traffic through 10 Oct (29 Sep a gap; 11 Oct provisional, not plotted) — 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 public data and are labelled as FIR-level wherever they appear. Method: /methodology/ · Press: /press/.

Related coverage