Cape Town (CPT) Observed Traffic −60% on 17 November 2026 — a Reading From a Short Day in Our Feed; a Second Network Counts an Ordinary Tuesday
- Our count at Cape Town fell to 93 movements on Tuesday 17 November, against a 7-day average of 230 — 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 239 movements at Cape Town that day, close to its usual 252. The weather was visual all day.
- 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
Cape Town's day is front-loaded: most of its departures leave between 03:00 and 12:00 UTC — 05:00 to 14:00 local time. On 14–16 November the four blocks from 00:00 to 12:00 UTC held 136, 135 and 121 movements. On Tuesday 17 November the same blocks held 24 — 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 10 against 43–54. From 15:00 UTC the blocks read 32, 23 and 4 — 59 movements, inside the 39–77 of 14–16 November. Three-hour blocks, 14–17 November:
Fig. 1 — Observed movements (departures + arrivals) at Cape Town (CPT) in each three-hour UTC block, 14–17 November 2026 (Cape Town time = UTC+2); recounted from the underlying flight records in our primary feed; 16–17 November provisional · Data as of 18 Nov 2026, 15:48 UTC · pulse = our primary feed (FACT) 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:30 UTC on 18 Nov; FACA NOTAM set refreshed 18 Nov 15:32 UTC · Source: Observed movement records for FACT from a crowdsourced ADS-B receiver network, as collected by FlySafe monitoring.
Airports in the exposure zone
| Airport | Size | Observed signal | FIR |
|---|---|---|---|
| Cape Town International Airport (CPT) | large | — · 17 Nov: 93 observed movements (48 dep / 45 arr), provisional, −60% vs a 230 7-day average; movements before 12:00 UTC 24 vs 121–136, from 15:00 UTC 59 vs 39–77; second network 239 (118 / 121) vs a 252 median; weather visual; no notice closes CPT | FACA |
| O.R. Tambo International Airport (JNB) | large | 1273 km · Cape Town's busiest route, same shape: 195 on 17 Nov (121 dep / 74 arr) vs 437 on 16 Nov; departures before 12:00 UTC 77 vs 145–195; second network 438 (219 / 219) vs 498 on 16 Nov | FAJA |
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 Cape Town 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. Cape Town International's last 30 days:
Fig. 2 — Observed daily movements at CPT, 19 Oct – 17 Nov (latest complete UTC day). Data as of 18 Nov 2026, 15:48 UTC · pulse = our primary feed (FACT) 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:30 UTC on 18 Nov; FACA NOTAM set refreshed 18 Nov 15:32 UTC · Source: FlySafe monitoring (ADS-B receiver network).
- Baseline in our own feed: 265 observed movements/day (median of 19 Oct – 16 Nov), range 190–304. The two previous Tuesdays read 280 and 255.
- Tue 17 Nov: 93 — 48 departures, 45 arrivals — 65% below the median; the detection layer fired at −60% against a 7-day average of 230. Provisional: the day's records arrived in a single ingest pass at 02:30 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.
- Johannesburg O.R. Tambo shows the same shape: 77 departures before 12:00 UTC against 145–195 on 14–16 November.
- Second crowdsourced ADS-B network, Cape Town, 17 Nov: 239 movements (118 / 121) against a 252/day median for 7–16 November (range 183–271); the previous Tuesday read 255.
- Sun 15 Nov is plotted as 266, a recount from the underlying flight records; the stored row, cut short by a routine partial refresh, holds 63. Mon 16 Nov: 228 (107 / 121), provisional. Sat 7 Nov (190) reads low in both networks (183 in the second) and is not explained here.
Observed counts are a floor, not a total. Live view: CPT 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 −60% reading opens an investigation rather than a headline. A real local disruption — a restriction, a runway or system problem — 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:30 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. Cape Town's main departure bank falls inside those hours — 05:00 to 14:00 local time — so the airport is hit harder than its daily total suggests. Johannesburg O.R. Tambo logged 77 departures before 12:00 UTC against 145–195 on 14–16 November. A reading that moves with the entire feed is first of all a feed reading.
The Cape Town test: ordinary once the feed recovered, and ordinary in a second network. If something at Cape Town itself had cut traffic, the evening hours would show it too. From 15:00 UTC (17:00 local) our feed attached 59 movements to CPT — 19 departures and 40 arrivals — against 39, 77 and 64 in the same hours of 14, 15 and 16 November. The 12:00–15:00 UTC block still reads low (10 against 43–54), in hours when our worldwide feed was also still below its usual volume. The second crowdsourced ADS-B network we cross-check against counts 239 movements at Cape Town on 17 November — 118 departures and 121 arrivals — against a 252/day median for 7–16 November and 255 on the previous Tuesday.
Weather, notices and closure signals. Every routine weather report for Cape Town on 17 November in our set reads CAVOK — no significant cloud, visibility 10 km or more — with a south-easterly wind of 17–20 kt in the first hours of the UTC day, easing to 5–7 kt by mid-morning and a south-westerly 14–16 kt in the afternoon, one gust of 21 kt reported at 19:00 UTC. Over the past 30 days 3% of Cape Town's reports in our set were in instrument conditions. Our notice set for the Cape Town FIR (FACA), refreshed at 15:32 UTC on 18 November, holds 11 notices — light displays, weather-balloon operations, parachute drop zones, a radio relay station out of service, publication amendments — and none closes the aerodrome or a runway; it holds currently valid notices, so one issued and withdrawn earlier would not appear. Our detection layer registered low-confidence (0.18), unattributed FIR-level closure signals for FACA on 15 and 18 November, both tied to a parachute drop-zone notice near Tulbagh, and none for 17 November. 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 239 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 Cape Town fell to 93 movements on 17 November against a 7-day average of 230, but our whole worldwide feed was short that day — 81,931 flight records against 121,560–146,699 on 10–16 November — and Johannesburg O.R. Tambo reads low by the same pattern. A second crowdsourced ADS-B network counts 239 movements at Cape Town that day, close to its 252/day median. For a specific flight, check the airline and the CPT brief, which updates nightly.
Because the gap in our feed sits in the same hours as Cape Town's busiest bank. Most Cape Town departures leave between 05:00 and 14:00 local time (03:00–12:00 UTC); on 17 November our worldwide table held about a sixth of its usual records before 12:00 UTC. From 15:00 UTC, when the feed was back at normal volume, Cape Town's count was in its usual range.
Not according to the airport's routine weather reports in our set: on 17 November every report read CAVOK — no significant cloud and visibility of 10 km or more. The wind was south-easterly at 17–20 kt in the first hours of the UTC day and south-westerly at 14–16 kt in the afternoon, with one gust of 21 kt at 19:00 UTC.
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, and a second network reads the day in its usual range, 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 Cape Town International fell to 93 movements on 17 November 2026 in FlySafe's own crowdsourced ADS-B feed — 60% below its 7-day average of 230 — 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 239 movements at Cape Town that day, close to its 252-a-day median, 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.

