Rome Fiumicino (FCO) Observed Traffic −55% on 17 November 2026 — a Reading From a Short Day in Our Feed; a Second Network Counts a Typical Tuesday
- Our count at Fiumicino fell to 335 movements on Tuesday 17 November, against a 7-day average of 747 — on a day when our worldwide feed was also short, mostly before 12:00 UTC.
- A second ADS-B network we cross-check against counts 641 movements at Fiumicino that day, in line with the previous Tuesday's 638. The ash flag on the airport is an exercise for Vesuvius, not an eruption.
- 17 November is provisional in our own feed and can still rise on the next nightly refetch. Check your airline and the airport for the status of any flight.
Advisory timeline — how active is this episode
Fiumicino's day runs from about 06:00 to 24:00 UTC, and its busiest blocks sit between 06:00 and 15:00 UTC. On 14–16 November the blocks before 12:00 UTC held 362, 351 and 342 movements. On Tuesday 17 November the same blocks held 30 — those are the hours in which our worldwide feed held about a sixth of its usual records. The 12:00–15:00 UTC block, when the worldwide feed was still recovering, read 40 against 149–155. From 15:00 UTC the blocks read 111, 103 and 51 — 265 movements, against 321–393 in the same hours of 14–16 November. Three-hour blocks, 14–17 November:
Fig. 1 — Observed movements (departures + arrivals) at Rome–Fiumicino (FCO) in each three-hour UTC block, 14–17 November 2026 (Rome time = UTC+1); recounted from the underlying flight records in our primary feed; 16–17 November provisional · Data as of 18 Nov 2026, 18:52 UTC · pulse = our primary feed (LIRF) 19 Oct – 17 Nov, 15 Nov plotted as a recount from the underlying flight records; second crowdsourced ADS-B network in through 17 Nov (no 6 Nov row) as cross-check; movements by three-hour block 14–17 Nov recounted from the underlying flight records; 16–17 Nov provisional, 17 Nov from a single ingest pass at 02:32 UTC on 18 Nov; LIRR NOTAM set refreshed 18 Nov 18:33 UTC · Source: Observed movement records for LIRF from a crowdsourced ADS-B receiver network, as collected by FlySafe monitoring.
Airports in the exposure zone
| Airport | Size | Observed signal | FIR |
|---|---|---|---|
| Rome–Fiumicino Leonardo da Vinci International Airport (FCO) | large | — · 17 Nov: 335 observed movements (170 dep / 165 arr), provisional, −55% vs a 747 7-day average; movements before 12:00 UTC 30 vs 342–362, from 15:00 UTC 265 vs 321–393; second network 641 (350 / 291) vs 638 the previous Tuesday; ash flag = Vesuvius exercise advisories (18 Nov), no eruption | LIRR |
| Milan Malpensa International Airport (MXP) | large | 511 km · Same shape on 17 Nov: 126 departures vs 250–364 on 10–16 Nov; departures before 12:00 UTC 20 vs 118–174; second network 485 (245 / 240) vs 471–649 on 10–16 Nov | LIMM |
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: a low Tuesday at Fiumicino inside a short day for the whole feed
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. Rome–Fiumicino Leonardo da Vinci International's last 30 days:
Fig. 2 — Observed daily movements at FCO, 19 Oct – 17 Nov (latest complete UTC day). Data as of 18 Nov 2026, 18:52 UTC · pulse = our primary feed (LIRF) 19 Oct – 17 Nov, 15 Nov plotted as a recount from the underlying flight records; second crowdsourced ADS-B network in through 17 Nov (no 6 Nov row) as cross-check; movements by three-hour block 14–17 Nov recounted from the underlying flight records; 16–17 Nov provisional, 17 Nov from a single ingest pass at 02:32 UTC on 18 Nov; LIRR NOTAM set refreshed 18 Nov 18:33 UTC · Source: FlySafe monitoring (ADS-B receiver network).
- Baseline in our own feed: 878 observed movements/day (median of 19 Oct – 16 Nov), range 722–1,012. The two previous Tuesdays read 775 and 722; the level has eased since the winter schedule began on 25 October.
- Tue 17 Nov: 335 — 170 departures, 165 arrivals — 62% below the median; the detection layer fired at −55% against a 7-day average of 747. Provisional: the day's records arrived in a single ingest pass at 02:32 UTC on 18 November and can still rise.
- The whole feed is short on 17 November. Our worldwide table holds 81,931 flight records for the day against 121,560–146,699 for 10–16 November. Records with a take-off between 00:00 and 12:00 UTC number 8,024 against 46,217 on 16 November; from 12:00 UTC, 73,907 against 75,343.
- Other Italian airports show the same shape: Milan Malpensa logged 20 departures before 12:00 UTC against 118–174 on 10–16 November; Bergamo, Venice, Catania and Rome Ciampino read low the same way.
- Second crowdsourced ADS-B network, Fiumicino, 17 Nov: 641 movements (350 / 291) against 638 on Tue 10 Nov and 704 on Tue 3 Nov; its 7–16 November days range 624–829.
- Sun 15 Nov is plotted as 895, a recount from the underlying flight records; the stored row, cut short by a routine partial refresh, holds 208. Mon 16 Nov: 818 (402 / 416), provisional.
Observed counts are a floor, not a total. Live view: FCO airport brief.
What it means for flights
A crowdsourced count can fall without any traffic falling. Observed movements are reconstructed from ADS-B receivers run by volunteers, then aggregated on our side and loaded in nightly batches. When a batch arrives short, every airport in it reads low at once, while flights keep operating. That is why we publish observed counts as a floor, not a total, and why a −55% reading opens an investigation rather than a headline. A real local disruption — a restriction, a runway or system problem, a strike — would also lower the count, so we test for both rather than pick one.
The worldwide test: the whole feed was short on 17 November. Our worldwide table holds 81,931 flight records for 17 November against 121,560–146,699 for each of 10–16 November, and it arrived in a single pass at 02:32 UTC on 18 November. The shortfall sits in the first half of the UTC day: 8,024 records with a take-off between 00:00 and 12:00 UTC against 46,217 the day before, while from 12:00 UTC the table holds 73,907 against 75,343. Fiumicino's morning and midday banks fall inside those hours, so the airport is hit harder than a uniform loss would suggest. Across Italy the pattern repeats: Milan Malpensa logged 20 departures before 12:00 UTC against 118–174 on 10–16 November, Bergamo 7 against 45–86, Venice 6 against 35–59. A reading that moves with the entire feed is first of all a feed reading.
The Fiumicino test: closer to normal once the feed recovered, and normal in a second network. If something at Fiumicino itself had cut traffic, the evening hours would show it as deeply as the morning. From 15:00 UTC (16:00 local) our feed attached 265 movements to FCO — 120 departures and 145 arrivals — against 334, 393 and 321 in the same hours of 14, 15 and 16 November: lower, but nowhere near the 30-against-342 of the morning. The evening shortfall is not unique to Rome: Malpensa's departures after 12:00 UTC read 106 against 138–190, consistent with our European records also running soft in the afternoon. The 12:00–15:00 UTC block still reads 40 against 149–155, in hours when the feed was still below its usual volume. The second crowdsourced ADS-B network we cross-check against counts 641 movements at Fiumicino on 17 November — 350 departures and 291 arrivals — against 638 on Tuesday 10 November and 704 on Tuesday 3 November.
The ash flag: an exercise for Vesuvius, not an eruption. Fiumicino carries a volcanic-ash exposure flag in our data because the Toulouse Volcanic Ash Advisory Centre issued four advisories for Vesuvius on 18 November, and the London centre retransmitted one. Every one of them is marked STATUS: EXER — part of the VOLCEX26 exercise, with the remark "PLEASE DISREGARD" — and the last, at 15:33 UTC, closes the exercise with "NO VA EXP" (no volcanic ash expected). They were issued the day after the low reading and play no part in it. The most recent real advisory in our set for an Italian volcano is for Etna on 30 October. No ash advisory and no closure signal applies to the Rome FIR (LIRR) on 17 November.
Weather, notices and closure signals. The routine weather reports for Fiumicino on 17 November in our set show light rain showers between about 05:50 and 07:20 UTC with cloud down to 1,500–2,500 ft, then mostly visual conditions, and light rain again from 19:20 UTC with visibility of 8–9 km; wind at or below 15 kt, no gusts reported. There is a gap in the reports between 03:00 and 04:50 UTC. Since 18 October, 2 of 1,602 Fiumicino reports in our set were in instrument conditions. Our notice set for the Rome FIR (LIRR), refreshed at 18:33 UTC on 18 November, holds 25 notices, all standing obstacle notices for low-flying areas; none mentions Fiumicino, so the set can neither confirm nor rule out an aerodrome notice there. Our detection layer registered no closure signal for LIRR on 17 November; the most recent, a low-confidence (0.09) volcano-category signal, covers 28–30 October. These are FIR-level observations, not statements about the airport.
What would close this episode — and what would reopen it. Two things would close this episode in our data: our 17 November total rising on the next nightly refetch, as provisional days usually do once the missing records arrive, and the second network's 641 holding as published. If our refetched count still reads low and the second network revises down, we will say so here. This automated multi-signal analysis surfaces anomalies like this one early and publishes what can and cannot be measured; the operating picture on any given day belongs to the airport, the airlines and the relevant authorities.
Passenger questions, answered from the data
Our data does not show that. Our own observed count at Fiumicino fell to 335 movements on 17 November against a 7-day average of 747, but our whole worldwide feed was short that day — 81,931 flight records against 121,560–146,699 on 10–16 November — and Milan Malpensa and other Italian airports read low by the same pattern. A second crowdsourced ADS-B network counts 641 movements at Fiumicino that day, against 638 on the previous Tuesday. For a specific flight, check the airline and the FCO brief, which updates nightly.
Not in the advisories in our set. The ash advisories for Vesuvius issued on 18 November by the Toulouse and London Volcanic Ash Advisory Centres are all marked as an exercise (VOLCEX26, "please disregard"), and the last one closes the exercise with no ash expected. The most recent real advisory for an Italian volcano in our set is for Etna on 30 October.
Because the gap in our feed sits in the same hours as Fiumicino's busiest banks. On 17 November our worldwide table held about a sixth of its usual records before 12:00 UTC (13:00 in Rome); Fiumicino's blocks before 12:00 UTC read 30 movements against 342–362 on the three days before. From 15:00 UTC, when the feed was back near normal volume, Fiumicino read 265 against 321–393.
We do not make that call — we publish what our monitoring can and cannot measure. Here the reading coincides with a short day in our own feed, a second network reads the day in line with the previous Tuesday, and the ash flag is an exercise, so it is not by itself evidence of a disruption. Your airline and the airport are the authoritative sources for any flight.
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 Rome–Fiumicino fell to 335 movements on 17 November 2026 in FlySafe's own crowdsourced ADS-B feed — 55% below its 7-day average of 747 — on a day when the whole worldwide feed held 81,931 flight records against 121,560–146,699 on the seven days before; a second crowdsourced ADS-B network counts 641 movements at Fiumicino that day, in line with 638 on the previous Tuesday, the airport's volcanic-ash flag traces to an exercise for Vesuvius, and the low reading has no confirmed local cause, 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.

