Valencia (VLC) Traffic 'Drop' — 19 Observed Movements on a ~292-Movement Day, and a Feed That Stopped Hearing the Airport at 05:00 UTC, August 2026
- Nothing in the layers we track indicated a disruption at Valencia. The −93% on 26 August was a measurement failure: our feed stopped logging the airport at 05:00 UTC and recorded nothing for the next eighteen hours, while a second independent receiver network counted a normal 141 movements there the same day — and a normal 127, 129, 121, 130 and 130 on the five days after.
- The mechanism is visible in our own raw data: low-altitude reception within ~38 km of the airport fell from ~157 reports a day to 12 (26 Aug) and stayed at 2, 5, 7, 7 and 7 through 31 August — inside 10 km it hit zero outright on 27, 28, 29 and 31 August — while traffic across the same sky at higher altitudes kept being heard and neighbouring Alicante and Barcelona kept full close-in coverage throughout.
- Reception came back around midday on 1 September and the count confirmed it. Valencia logged 165 of its 172 movements that day from 12:00 UTC onward — against 169, 167 and 166 in the same window on the three preceding Tuesdays — and 2, 3, 4 and 5 September then settled at 287, 292, 291 and 277 movements spread hour by hour across each day — a four-day mean of 287, within 2% of the ~292 baseline. 6 and 7 September are still finalising feed-wide, so those counts are not read here. This page is now closed: observed counts are a floor, not a total, and for a specific flight, check your airline or the airport as always.
Advisory timeline — how active is this episode
This chart does not show flights — it shows how well we could hear them. Every day from 12 to 25 August our receiver network logged between 118 and 196 position reports below 3,000 m within about 38 km of Valencia Airport (mean ~157) — the low-and-close band where departures and final approaches live. On 26 August that fell to 12, and stayed down at 2, 5, 7, 7 and 7 across 27–31 August — a 92–99% loss sustained for six days — before 1 September recorded 92, then 149, 165, 164, 156 and 184 across 2–6 September, every one of those five days back inside — and the last a little above — the pre-outage band. Tighter in, the pattern is starker: within 10 km of the airport below 1,000 m — the runway and short-final band — reception ran 39–63 reports a day from 12 to 25 August, then 6 on the 26th (all of them before 06:00 UTC), zero on the 27th, 28th and 29th, one on the 30th, zero on the 31st — and then 39 on 1 September, 48 on the 2nd, 50 on the 3rd, 53 on the 4th, 43 on the 5th and 72 on the 6th, back inside its own pre-outage band, each of the last five spread across the whole day from 04:00–05:00 to past 20:00 UTC. Over the very same patch of sky, the count of distinct aircraft heard at all altitudes held up far better throughout: 270, 234, 231, 241, 235 and 245 across 26–31 August, then 286, 313, 327, 319, 345 and 312 on 1–6 September, against a 273–354 band over the preceding fortnight (mean ~329) — modestly below that band during the outage, not a collapse. High traffic still largely audible, low traffic effectively gone, and then both back to normal within a day and a half of the recovery and staying there for six days now — that is a reception pattern, not a traffic pattern:
Fig. 1 — Position reports below 3,000 m within ~38 km of Valencia Airport, 12 Aug – 6 Sep 2026 · Data as of 7 Sep 2026, 18:55 UTC · Source: FlySafe monitoring (crowdsourced ADS-B receiver network, raw position layer).
Airports in the exposure zone
| Airport | Size | Observed signal | FIR |
|---|---|---|---|
| Valencia Airport (VLC) | large | — · 26 Aug: 19 observed movements, all before 06:00 UTC — coverage out six days; reception and count both returned from ~12:00 UTC on 1 Sep (172 movements, 165 of them after midday), and 2–5 Sep settled at a normal 287, 292, 291 and 277 | LECB |
| Alicante-Elche Miguel Hernández (ALC) | large | — · 134 km south, same FIR — close-in coverage unaffected on every day 26 Aug–6 Sep | LECB |
| Ibiza (IBZ) | large | — · 368 movements on 26 Aug, then 398, 414, 417, 439, 395, 367, 365, 358, 381 and 393 through 5 Sep — within its normal range | LECB |
| Palma de Mallorca (PMI) | large | — · 642 movements on 26 Aug, then 878, 617, 887, 1,032, 780, 732, 835, 875, 942 and 951 through 5 Sep — no regional signal | LECB |
| Josep Tarradellas Barcelona-El Prat (BCN) | large | — · 998 movements on 26 Aug, then 1,140, 1,150, 1,086, 1,103, 1,142, 1,104, 1,152, 1,149, 1,163 and 1,079 through 5 Sep; full low-altitude coverage held throughout | LECB |
| Adolfo Suárez Madrid–Barajas (MAD) | large | — · 1,099 movements on 26 Aug, then 1,301, 1,299, 1,215, 1,295, 1,263, 1,226, 1,263, 1,257, 1,314 and 1,195 through 5 Sep — feed healthy nationally on all eleven settled days | LECM |
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 shows: an airport that stopped being audible, not an airport that stopped flying
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. Valencia Airport's last 30 days:
Fig. 2 — Observed daily movements at VLC, 28 Jul – 5 Sept (latest complete UTC day). Data as of 7 Sep 2026, 18:55 UTC · Source: FlySafe monitoring (ADS-B receiver network).
- Four-week baseline (28 Jul–24 Aug): ~292 observed movements/day, in a tight 266–315 band with no missing days. The four prior Wednesdays averaged ~291 (297, 291, 291, 285).
- Wednesday 26 Aug came in at 19 observed movements — −93% vs the four-week baseline. Detection fired at −92% against a rolling seven-day average of ~250; that window was computed while 25 August was still finalising. On settled records the 25th reads 296 — a fully normal day — so the seven days before the anomaly average ~289 and the drop is a clean cliff off a normal Tuesday, not the tail of a declining week.
- The timestamps are the tell. All 19 movements were logged between 01:00 and 05:00 UTC — 1, 0, 5, 10, 3 across those hours — and then nothing at all for the remaining eighteen hours of the day, straight through Valencia's busiest morning and evening banks. Airports do not shut down at 06:00 and stay shut with no closure signal; feeds do.
- Both sides of the ledger went at once on the 26th — 16 departures and 3 arrivals — the airport dropping out of the feed altogether partway through the day rather than the partial loss of close-in reach we measured at Palermo.
- Six consecutive settled days now show the loss, and none of it anywhere else. 27 Aug finalised at 6 movements (0 departures, 6 arrivals scattered between 07:00 and 18:00 UTC) against a complete national feed: Madrid 1,301, Barcelona 1,140, Palma 878, Ibiza 398, Alicante 233. 28 Aug reads 12 (1 departure, 11 arrivals from 08:00 to 19:00 UTC) with the rest of Spain normal — Madrid 1,299, Barcelona 1,150, Palma 617, Ibiza 414, Alicante 363. 29 Aug reads 16 (zero departures, 16 arrivals from 00:00 to 18:00 UTC) — Madrid 1,215, Barcelona 1,086, Palma 887, Ibiza 417, Alicante 246. 30 Aug settled at 6 (zero departures, 6 arrivals between 10:00 and 23:00 UTC) against Madrid 1,295, Barcelona 1,103, Palma 1,032, Ibiza 439 and Alicante 266. And 31 August, which we last published as an unfinished day we would not read, has since settled: 15 movements at Valencia — again zero departures, 15 arrivals thinly spread from 04:00 to 23:00 UTC — on a fully normal Monday network-wide (150,209 flight records against 151,906, 152,982 and 155,923 on the three Mondays before it), with Madrid at 1,263, Barcelona 1,142, Palma 780, Ibiza 395 and Alicante 248. Departures — the half only close-in receivers hear — ran at zero on every settled outage day bar one, a single departure on the 28th.
- 1 September: the count came back, and its shortfall is accounted for hour by hour. On settled records Valencia logged 172 movements — 79 departures and 93 arrivals, against zero-or-one departures on every day of the outage — which is still −41% against the ~292 baseline. But the day's shape explains the gap without appeal to traffic: nothing at all from 00:00 to 05:00, seven movements across 06:00–08:00, nothing again from 09:00 to 11:00, and then 165 of the day's 172 movements in a continuous stream from 12:00 to 23:59 UTC — the exact hour close-in reception returned in the position layer. In that covered 12:00–24:00 window Valencia ran 165 movements against 169, 167 and 166 in the same window on the three preceding Tuesdays (band 140–176 across 11–25 Aug). Where we could hear the airport, the airport was normal.
- 2 September closes it: a whole normal day, start to finish. On settled records Valencia ran 287 movements — 145 departures and 142 arrivals — −2% against the ~292 four-week baseline, and in line with the 291 and 285 of the two Wednesdays before the outage. Unlike 1 September there is no uncovered block left: movements run in every hour from 03:00 to 23:00 UTC with only the two deep-night hours empty, peaking as Valencia normally does across the morning bank (17, 20, 22 at 06:00–08:00) and the evening one (22, 20, 17 at 17:00–19:00). The position layer for the same day matches — 149 low-altitude reports and 48 inside 10 km, Fig. 1.
- 3, 4 and 5 September have all settled normal, and they close the event. On settled flight records Valencia logged 292 movements on 3 September (146 departures, 146 arrivals) — firmed up from the 289 we published two days ago — then 291 on the 4th (147/144) and 277 on the 5th (136/141): 0%, −0.3% and −5% against the ~292 baseline, each on a complete national feed (152,389, 159,751 and 137,413 flight records network-wide) with Madrid at 1,257, 1,314 and 1,195, Barcelona 1,149, 1,163 and 1,079, Palma 875, 942 and 951, Ibiza 358, 381 and 393, Alicante 280, 323 and 316. All three run hour by hour across the full day with Valencia's usual banks — the 4th peaking at 19, 21, 23 across 06:00–08:00 and 15, 13, 15 across 16:00–18:00; the 5th at 14, 22, 22 and 16, 24, 15 — and the position layer agrees on every one of them: 165, 164 and 156 low-altitude reports and 50, 53 and 43 inside 10 km, Fig. 1. Four consecutive fully covered, fully normal days (2–5 September, mean 287 movements) is what closes a coverage anomaly.
- Gap days, flagged: 6 and 7 September are whole-feed days still finalising — 14,983 flight records network-wide on the 6th against the 151,632, 152,809 and 152,389 of the days before it (Madrid 78, Barcelona 52, Palma 18, Ibiza 13, Alicante 8), and 7 September barely begun — so Valencia's stored counts of 11 and 0 on those days carry no information in either direction and both are held out of the pulse chart above, which ends on the last complete day. The position layer for 6 September is complete, and it is normal: 184 low-altitude reports, 72 inside 10 km and 312 distinct aircraft over the wider ring, Fig. 1.
- The correction we printed on 28 August has fully healed. Both stored days a partial refresh had overwritten — 28 August (once Valencia 2 / Madrid 47 / Barcelona 79) and 29 August (once Valencia 11 on a network-wide stored volume of 32,414) — now read 12 and 16 at Valencia on normal network volumes of 259,865 and 237,510, exactly the figures we published from the underlying flight records and stood behind. The standing lesson stands too, and it applied again on this final cycle: our newest days are provisional in both directions — 2 September firmed from the 281 we first published to 287, 3 September went from an unreadable 6 to 289 and has since firmed once more to 292, and 4 September, which the last version of this page declined to read at 9 movements on an unfinished feed, has settled at a fully normal 291 — which is why 6 and 7 September are not read here. The stored-layer artefact recurred and then healed as expected: the rollup that showed Valencia at 118 for 2 September now reads 287, matching the flight records we published. One instance of it is live at the time of writing — the stored rollup shows Valencia at 51 for 4 September, and every Spanish airport correspondingly low that day, because a refresh window clipped it mid-day. We publish from the underlying flight records, which read 291 across a normal 24-hour shape on a complete national feed, and expect the stored layer to heal on its next full pass as it has every previous time.
Observed counts are a floor, not a total — they measure what our receivers heard, and they are only meaningful while coverage holds. Live view: VLC airport brief.
What it means for flights
What fired, and why we publish it anyway. Our detection layer flagged VLC when 26 August came in at 19 observed movements against a rolling seven-day average of ~250 — a −92% traffic anomaly at one of Spain's busiest airports, in the last week of the peak summer season. On settled records that comparison is starker still: 25 August, which was mid-collection when the alert fired and read 207 at the time, has since finalised at a fully normal 296, putting the seven days before the anomaly at ~289 and the drop at −93% off a clean baseline. A number that large at a name-recognisable airport is precisely the raw material of a phantom headline, so automated multi-signal analysis does what it always does before anything is claimed: check the anomaly against every other layer we track — the hour-by-hour shape of the count, the arrivals/departures split, the raw position feed, neighbouring airports, a second independent receiver network, closure signals and GNSS interference. Not one of those layers corroborated an operational event at Valencia; several of them positively contradicted it, and the recovery on 1 September closed the case in the same direction. We publish that evidence, as we did for the Palermo coverage anomaly, the Monterrey coverage collapse and the Memphis Sunday false alarm — publishing observed counts honestly means publishing their failure modes too.
A day that ends at 05:00 UTC. The decisive fact is not the size of the drop but its clock. Valencia's 19 observed movements on 26 August are stacked entirely in the 01:00–05:00 UTC window (1, 0, 5, 10, 3 per hour), and the feed then records zero movements for the following eighteen hours — across the whole morning departure bank, the whole day, and the evening arrivals. A real operational shutdown of that shape would be one of the largest aviation events in Europe this summer, announced by the airport and the Spanish authorities and visible in every airspace layer we track; nothing of the kind exists in our data or in any signal reaching our detection layer. A feed that loses an airport partway through a day produces exactly this shape, and it is the same shape whichever side of the ledger you look at: 16 departures and 3 arrivals, both sides stopping at the same moment. The five settled days that followed did not repeat that clean cliff but did not recover either — 27 August logged 6 arrivals and zero departures, thinly scattered from 07:00 to 18:00 UTC; 28 August, 11 arrivals and 1 departure from 08:00 to 19:00; 29 August, 16 arrivals and again zero departures, from 00:00 to 18:00; 30 August, 6 arrivals and zero departures between 10:00 and 23:00; and 31 August, now settled too, 15 arrivals and zero departures spread from 04:00 to 23:00. Departures, which only close-in receivers hear at all, are the part that stayed away for the whole outage — and the part that came back first when reception did: 79 of them on 1 September, and a fully ordinary 145, 146, 147 and 136 across the 2nd to the 5th.
Our own raw data shows the coverage going — and coming back. Beneath the movement counts sits a rawer layer: individual position reports. Within roughly 38 km of Valencia Airport, reports below 3,000 m — the low, close band where departures and final approaches are heard — ran between 118 and 196 per day from 12 to 25 August (mean ~157). On 26 August that layer recorded 12, then 2, 5, 7, 7 and 7 across 27–31 August. Tighten the ring to 10 km and the floor to 1,000 m — the runway and short-final band — and the outage is absolute rather than merely deep: 39 to 63 reports a day through 12–25 August, then 6 on the 26th (all before 06:00 UTC), zero on the 27th, zero on the 28th, zero on the 29th, one on the 30th and zero on the 31st. Over the identical patch of sky, distinct aircraft heard at all altitudes held up far better — 270, 234, 231, 241, 235 and 245 across those six days, against a 273–354 band through the preceding fortnight (mean ~329), landing modestly below that band rather than collapsing. Aircraft cruising over the Valencia region at flight levels were still largely audible; aircraft near the ground were not. As interpretation rather than measurement: high-altitude traffic is heard by distant receivers across a wide horizon, while a departure on the runway or an aircraft on short final can only be heard by antennas close in. Lose the close-in receivers and the airport disappears from the count while the sky above it does not. On 1 September that reversed. Nothing was heard low and close until 09:00 UTC, then a trickle, then from 12:00 a steady stream: 92 low-altitude reports on the day and 39 inside 10 km — the latter back at the bottom of its own pre-outage 39–63 band, every one of them logged from 12:00 onward — from 29 distinct aircraft, the lowest of them at 8 m above the ground. Distinct aircraft over the wider ring recovered to 286. 2 to 6 September then ran as ordinary days throughout: 149, 165, 164, 156 and 184 low-altitude reports, and 48, 50, 53, 43 and 72 inside 10 km, spread hour by hour from 04:00–05:00 to past 20:00 UTC, with 313, 327, 319, 345 and 312 distinct aircraft over the wider ring — every one of those figures inside its pre-outage band, the last day's close-in count somewhat above it. Six days and six hours after the airport went quiet in our data, the receivers started hearing it again, a day later they were hearing it normally, and they have gone on doing so for five days since.
A second network saw a normal Valencia. We cross-check against a second crowdsourced ADS-B aggregate built on a different set of volunteer receivers. It recorded 141 movements at VLC on 26 August (70 departures, 71 arrivals), then 127 on the 27th, 129 on the 28th, 121 on the 29th, 130 on the 30th, 130 on the 31st, then 118, 113, 121, 120, 128 and 133 across 1–6 September — against its own 21-day mean of ~131 and a normal band of 97–155 (11–31 August). In other words: on the day our feed heard 19 aircraft, another network heard a fully ordinary Valencia, and it went on hearing one for the next six days while ours did not — through the day ours recovered and every day since, on which the two instruments finally agree. Two instruments cannot both be right about one airport, and an airport has only one reality — so the disagreement was itself the finding, and it pointed at our measurement, which is where the recovery then confirmed the fault lay. We label the check honestly in the other direction too: crowdsourced networks share volunteer hosts and neither is a complete census, so this corroborates that Valencia was operating in a normal range, not that any exact number is the truth.
Nothing regional, nothing hazardous. The footprint followed receiver geography, not airline geography. Every other Spanish airport we track ran normally in our own feed on every settled day of the outage — 26 August: Madrid 1,099 movements, Barcelona 998, Palma 642, Málaga 560, Ibiza 368, Alicante 219; the 27th: 1,301 / 1,140 / 878 / 628 / 398 / 233; the 28th: 1,299 / 1,150 / 617 / 647 / 414 / 363; the 29th: 1,215 / 1,086 / 887 / 631 / 417 / 246; the 30th: 1,295 / 1,103 / 1,032 / 664 / 439 / 266; the 31st: 1,263 / 1,142 / 780 / 630 / 395 / 248; 1 September: 1,226 / 1,104 / 732 / 608 / 367 / 260; 2 September: 1,263 / 1,152 / 835 / 618 / 365 / 261; 3 September: 1,257 / 1,149 / 875 / 638 / 358 / 280; 4 September: 1,314 / 1,163 / 942 / 642 / 381 / 323; and 5 September: 1,195 / 1,079 / 951 / 624 / 393 / 316. The low-altitude position layer around Alicante (194, 176, 233, 243, 235, 194 reports on the 26th to the 31st, then 205, 221, 239, 269, 261 and 222 on 1–6 September) and Barcelona (714, 715, 709, 684, 673, 739, then 626, 755, 734, 721, 663 and 664) was untouched on every one of those days, including the ones for which movement records were absent or unfinished. There is no ash in the picture: no volcanic-ash advisory bears on this airspace and the airport carries no ash exposure. GNSS interference in the grid cell containing Valencia sat at ~1.3% of aircraft on 26 August (8 of 631), ~1.1% on the 27th, ~0.2% on the 28th, ~1.4% on the 29th, ~0.3% on the 30th, ~1.0% on the 31st, ~0.3% on 1 September (2 of 603), ~0.5% on the 2nd, ~0.9% on the 3rd, ~0.6% on the 4th (4 of 634) and ~1.3% on the 6th, all indistinguishable from the 0.7–1.7% of the days before, with the airport's own 7-day interference ratio at zero. One day sits marginally outside that band and we flag it rather than round it away: 5 September read ~2.1% (14 of 659), a modest single-day uptick in the same cell, with no corresponding change in movements (277) or reception (156 low-altitude reports) that day. That cell kept hearing 579–659 aircraft a day throughout — another sky that never went quiet. And no closure event registered anywhere in the Barcelona FIR (LECL) at any point in August or since — that is a FIR-level statement about airspace signals, not a claim about operations at Valencia Airport, which belong to the airport, the airlines and the Spanish authorities.
What we can now say, and what would still change this page. We never declared Valencia 'operating normally' while the instrument that would prove it was the one that had failed. What the recovery adds is the missing half of the argument: the failing layer started working again, and the moment it did, the airport reappeared at normal volume. Valencia's 1 September ran 165 movements in the 12:00–24:00 UTC window — the hours in which close-in reception was back — against 169, 167 and 166 in that same window on the three preceding Tuesdays; the day's overall −41% is the three uncovered morning blocks, hour for hour, and departures returned at 79 after six days at zero or one. 2, 3, 4 and 5 September remove even that residual: 287, 292, 291 and 277 movements across normal 24-hour shapes — a four-day mean of 287, within 2% of the baseline — with 145, 146, 147 and 136 of them departures. Eight caveats we carried in earlier versions have since settled, and we correct rather than leave them standing: 25 August, first labelled a feed-wide partial-collection day at 207 movements, finalised at a normal 296; 27, 28, 29 and 30 August, each first labelled a collection gap, finalised with the rest of Spain normal and Valencia alone at 6, 12, 16 and 6; and 31 August, which we last declined to read at all, has now settled on a fully normal Monday network-wide — Valencia alone at 15, and not one departure among them; 3 September, which an earlier version declined to read as a fresh feed-wide day at 6 movements, has settled on a complete national feed at 292; and 4 September, which the last version declined to read at 9 movements on an unfinished feed, has settled at a fully normal 291. The stored-layer correction that ran the other way has fully healed as well: 28 and 29 August, once overwritten down to Valencia 2 / Madrid 47 / Barcelona 79 and Valencia 11 on a 32,414-movement network volume, now read 12 and 16 on normal volumes, exactly as we published from the underlying flight records. The 2 September instance has healed too — the rollup that read 118 now reads 287 — and one fresh instance is live as we close: the stored rollup shows Valencia at 51 for 4 September, with every Spanish airport correspondingly low, while the underlying flight records read 291. The blind spots that remain are narrower but real: we hold no weather-station series for LEVC, so the METAR-continuity check that corroborated the Palermo verdict was never available here; and 6 and 7 September are whole-feed days still finalising (14,983 flight records network-wide on the 6th against ~152,000 on each of the three days before it), so we read those days from position reports only and their Valencia counts of 11 and 0 mean nothing. Two things would still reopen this page: movement records arriving with Valencia's counts below its ~292 baseline on fully covered days (a residual would become the story), or an official closure or disruption signal for VLC appearing in any layer (this becomes a disruption event and the framing changes). Absent either, this closes as what the evidence says it was — a six-day receiver-coverage loss, ended. This page carries the standing lesson: before believing a drop, check what time of day it happened.
What the data showed — closing entry. This page is closed as of 7 September 2026, 18:55 UTC. The signal that opened it has been absent for more than five days, and the number that closes it is the recovery: 2–5 September ran 287, 292, 291 and 277 observed movements at Valencia — a four-day mean of 287, or −2% against the ~292 four-week baseline, on complete national feeds and normal 24-hour shapes. Against the outage window that is the whole argument in one line: 19, 6, 12, 16, 6 and 15 movements across 26–31 August, and 0, 0, 1, 0, 0 and 0 departures on those days, against 145, 146, 147 and 136 departures on the four settled days after reception returned. The instrument recovered on 1 September at 12:00 UTC and the airport reappeared in the same hour; it has stayed recovered since, with the low-altitude position layer at 149, 165, 164, 156 and 184 reports a day through 6 September against a ~157 pre-outage mean, and the second crowdsourced network — which never lost Valencia — reading 118 to 133 across the same days, inside its own band throughout. What the whole episode measured was our own coverage, not Valencia's traffic: the −93% of 26 August was a receiver-coverage failure, it lasted six days, and no closure signal registered in the Barcelona FIR (LECL) at any point in August or since. Two days are excluded by our own gap rule rather than read: 6 and 7 September are still finalising feed-wide, so their movement counts are not used here, and the pulse chart ends on the last complete day (5 September). Observed movement counts come from a crowdsourced ADS-B receiver network and are a floor, not a total; the cross-check network is a second crowdsourced aggregate; closure and GNSS-interference signals come from our own detection layer at FIR and grid-cell level. We publish measured signals, not safety verdicts — operating decisions belong to the airlines, the airport and the Spanish aviation authorities. Automated multi-signal analysis continues to watch Valencia the way it watches every airport we track; if a new signal fires, it will be a new page. Live view: VLC airport brief.
Passenger questions, answered from the data
No signal in the layers we track indicated a disruption at any point. No closure registered anywhere in the Barcelona FIR (LECL) in August or since, GNSS interference around Valencia sat at its normal ~1%, and every neighbouring Spanish airport ran normally on 26 August and on every settled day since. The −93% figure came from our own observed count, which stopped recording the airport at 05:00 UTC and logged nothing for the next eighteen hours — while a second independent receiver network counted 141 movements at Valencia the same day, a normal figure for it. When our reception returned around midday on 1 September, the airport reappeared at normal volume in the same hour, and 2–5 September ran fully ordinary 287, 292, 291 and 277 movements across the whole day. For the status of a specific flight, check your airline or the airport's own channels.
The observed count did — 19 movements on 26 August 2026 against a ~292 four-week average. But observed counts are a floor, not a total, and the shape of this one showed it was not real traffic: all 19 movements were logged before 06:00 UTC, after which the feed recorded nothing for eighteen hours; low-altitude reception around the airport fell from ~157 reports a day to 12, and stayed down at 2, 5, 7, 7 and 7 through 31 August, with the band inside 10 km at zero on four of those days, while aircraft over the same airspace at cruise altitude were still heard; and a second crowdsourced network recorded 141, 127, 129, 121, 130 and 130 movements across those same six days. Every cross-check pointed to lost close-in receiver coverage rather than to flights stopping — and the recovery settled it: coverage returned around 12:00 UTC on 1 September, Valencia logged 165 of that day's 172 movements in the covered 12:00–24:00 window against 169, 167 and 166 in the same window on the three previous Tuesdays, and 2–5 September settled at 287, 292, 291 and 277 movements — a four-day mean within 2% of the baseline — spread across the whole day.
By the shape, not the size. A real disruption unwinds over hours and leaves traces in other layers: closure signals, diversions to alternates, knock-on effects at connected airports, an airport and an authority saying so. A coverage failure starts at one moment and takes both arrivals and departures with it, is confined to one airport's immediate airspace while overflights keep being heard, disagrees with independent receiver networks, and ends as abruptly as it began — with traffic reappearing at full volume the hour reception returns. Valencia's 26 August has every marker of the second pattern and none of the first, and its 1 September recovery matched the pattern to the hour — which is why we published it as an anomaly in our measurement rather than as an event at the airport.
We publish measured signals, not safety verdicts — operating and go/no-go decisions belong to airlines, airports and the Spanish aviation authorities, who work from complete operational data rather than crowdsourced tracking. Nothing in the layers we track indicated a hazard at Valencia; what degraded there, on the evidence, was public visibility of the airport's traffic, and that visibility returned on 1 September and has been running normally on every settled day since. For any specific flight, check your airline on the day of travel.
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.
“Observed traffic at Valencia Airport fell 93% below its four-week average on 26 August, but all 19 recorded movements were logged before 06:00 UTC and the feed then went silent for eighteen hours, while low-altitude reception around the airport collapsed from about 157 position reports a day to 12 and stayed down through 31 August — hitting zero inside 10 km on four of those days — even as higher-altitude traffic across the same airspace kept being heard and a second independent receiver network counted a normal 141 movements there that day and normal figures on the six days after; close-in reception returned around midday on 1 September and the airport reappeared in the count in the same hour, logging 165 of that day's 172 movements between 12:00 and 24:00 UTC against 169, 167 and 166 in that window on the three preceding Tuesdays, and 2 to 5 September then settled at fully normal 287, 292, 291 and 277 movements spread across the whole day — a four-day mean within 2% of the airport's four-week baseline — confirming a receiver-coverage failure rather than a disruption, according to flight-monitoring service FlySafe.zone.”
Boilerplate — about the source (for your article footer)
FlySafe.zone monitors airspace risk and observed airport activity worldwide: 334 flight-information regions scored daily, GPS-interference signals, volcanic-ash exposure and daily observed movements at 493 airports from the crowdsourced ADS-B receiver network. Methodology: flysafe.zone/methodology.
Need a different cut of the data, a comment, or numbers for another airport? Leave an email — we answer fast during active events.

