Shenzhen Bao'an (SZX) Observed Traffic −70% on 16 November 2026 — a Step in Our Count From the Afternoon of 15 November, Cause Unconfirmed
- Our count at Shenzhen Bao'an fell from about 1,137 movements a day to 337 on Monday 16 November, after a step at 06:00 UTC on Sunday 15 November.
- Our worldwide feed, Guangzhou, Hong Kong and Bao'an's weather read ordinary or close to it; Macau also fell sharply. That mix fits a local loss of receiver coverage, a real local disruption, or both — our data cannot tell which.
- We have no independent count at Bao'an, and our notice set for the Guangzhou FIR was last refreshed on 4 October. Check your airline and the airport for the status of any flight.
Advisory timeline — how active is this episode
Our feed sees a large share of Bao'an's traffic on an ordinary day: 989–1,430 observed movements a day across 18 October – 14 November, a 1,137/day median. On Saturday 14 November the five three-hour blocks from 00:00 to 15:00 UTC (08:00–23:00 Shenzhen time) read 206–236 each. On Sunday 15 November the morning ran the same way until 06:00 UTC — 229 and 196 in the first two blocks — then the 06:00–09:00 block read 52, with 6 departures in the 06:00 hour and none in the 07:00 hour. Arrivals came back in the afternoon blocks; departures stayed at roughly a third of the day before. On Monday 16 November no block read above 86, and the day totals 337. Three-hour blocks, 14–16 November:
Fig. 1 — Observed departures + arrivals at Shenzhen Bao'an (SZX) in each three-hour UTC block, 14–16 November 2026 (Shenzhen time = UTC+8); 14 November is a recount from the underlying flight records, 15–16 November are provisional · Data as of 17 Nov 2026, 03:50 UTC · SZX series settled through 13 Nov; 14 Nov plotted as a recount (stored row clipped at 1,111); 15 Nov and 16 Nov provisional; ZGZU NOTAM set last refreshed 4 Oct · Source: Observed movement records for ZGSZ from a crowdsourced ADS-B receiver network, as collected by FlySafe monitoring.
Airports in the exposure zone
| Airport | Size | Observed signal | FIR |
|---|---|---|---|
| Shenzhen Bao'an International Airport (SZX) | large | — · 16 Nov: 337 observed movements (129 dep / 208 arr), provisional, −70% vs a 1,137 median; 15 Nov: 879 (469 / 410), step at 06:00 UTC; 14 Nov: 1,369 on recount; low-altitude position reports 78 on 16 Nov vs 177–382 a day on 8–15 Nov; weather visual; no closure event in ZGZU | ZGZU |
| Macau International Airport (MFM) | medium | 59 km · Also down in our feed: 97 on 16 Nov (35 dep / 62 arr) vs 247–328 a day on 8–15 Nov; 15 Nov read 247, ordinary; the second network read 127 on 15 Nov, in its usual range (16 Nov not yet in) | VHHK |
| Hong Kong International Airport (HKG) | large | 38 km · Still reading: 911 on 15 Nov and 706 on 16 Nov (393 dep / 313 arr) vs 666–920 on 8–14 Nov; low-altitude position reports over the airport 139 on 16 Nov vs 106–178 a day on 8–15 Nov | VHHK |
| Zhuhai Jinwan Airport (ZUH) | medium | 83 km · Same FIR: 311 on 15 Nov, 194 on 16 Nov vs 226–268 a day on 10–14 Nov — softer, not a collapse | ZGZU |
| Guangzhou Baiyun International Airport (CAN) | large | 98 km · Same FIR, still reading: 1,115 on 15 Nov and 976 on 16 Nov vs 891–1,133 a day on 10–14 Nov | ZGZU |
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 step on Sunday afternoon, then a low Monday
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. Shenzhen Bao'an International's last 30 days:
Fig. 2 — Observed daily movements at SZX, 18 Oct – 16 Nov (latest complete UTC day). Data as of 17 Nov 2026, 03:50 UTC · SZX series settled through 13 Nov; 14 Nov plotted as a recount (stored row clipped at 1,111); 15 Nov and 16 Nov provisional; ZGZU NOTAM set last refreshed 4 Oct · Source: FlySafe monitoring (ADS-B receiver network).
- Baseline in our own feed: 1,137 observed movements/day (median of 18 Oct – 14 Nov), range 989–1,430. The four previous Mondays read 1,097, 1,067, 1,141, 1,140.
- Mon 16 Nov: 337 — 129 departures, 208 arrivals — 70% below the median; the detection layer fired at −70% against a 7-day average of 1,118. Provisional: the day's records arrived in a single ingest pass at 03:13 UTC on 17 November and can still rise a little.
- Sun 15 Nov: 879 (469 / 410), −23% — an ordinary morning, then the break at 06:00 UTC. Provisional.
- Sat 14 Nov: 1,369 on recount from the underlying flight records (the stored row, cut short by a routine partial refresh, holds 1,111) — an ordinary day.
- The flight numbers went quiet too, not just the runway. Callsigns that departed Bao'an on 12–13 November appear 904 and 912 times a day in our flight records on those days; on 16 November, 146 times in all, 120 of them departing Bao'an. Because they mostly vanished from the feed rather than reappearing without an origin, this test cannot separate a gap in coverage from fewer flights.
Observed counts are a floor, not a total. Live view: SZX 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. A flight is tied to Bao'an from the departure and arrival legs that nearby receivers happen to catch. When a receiver that covers the airport goes offline, flights keep operating but our reconstruction stops attaching them to the runway: the number drops, the runway does not. That is why we publish observed counts as a floor, not a total, and why a −70% reading opens an investigation rather than a headline. A real disruption — a restriction, a runway or system problem — would produce the same kind of fall, which is why we do not pick one.
The shape: an ordinary morning, then a break at a fixed hour. Operational disruptions from weather tend to build through a schedule and recover in stages. Our count did something more abrupt: on 15 November departures read 35–64 an hour from 00:00 to 06:00 UTC, then 6 in the 06:00 hour and none in the 07:00 hour, and arrivals in the 06:00–09:00 block fell to 30 against 97 the day before. Arrivals recovered in the afternoon blocks (100 and 90) while departures did not. On 16 November every hour read 2–19 departures. In the raw position sample, reports below 1,500 m around Bao'an fell from 177–382 a day on 8–15 November to 78 on 16 November. An abrupt break at a fixed time fits a source switching off, and it also fits a real stoppage that starts at a set hour — the shape alone does not decide it.
The geography test: wider than Bao'an, narrower than the region. If our whole feed had failed, the worldwide table would show it — it does not: 120,498 flight records for 16 November against 126,408 for 15 November. If the whole Pearl River Delta had gone quiet, Guangzhou would show it — Baiyun read 976 on 16 November, inside its 891–1,133 range of 10–14 November. Hong Kong read 706, near the bottom of its recent 666–920 range, and the low-altitude sample over Hong Kong airport held at 139 reports. Macau did not hold: 97 on 16 November against 247–328 on 8–15 November, and Zhuhai was softer at 194. Across a wide box over southern Guangdong, distinct aircraft in our position sample went from 2,098–2,139 a day on 8–15 November to 1,924 on 16 November. We report the Macau fall rather than wave it away: it widens the question, it does not answer it.
Weather, notices and closure signals. Bao'an's weather reports in our set were routine: all 33 reports on 15 November and all 38 on 16 November were in visual conditions, most of them CAVOK, winds up to 12 kt, and none of 723 reports in the past 30 days was in instrument conditions. Our NOTAM set for the Guangzhou FIR holds 6 notices and none closes the aerodrome, a runway or airspace — but that set was last refreshed on 4 October, while other FIRs refreshed this morning, so it says nothing about notices issued since. Our detection layer has registered no closure event in ZGZU or in the Hong Kong FIR (VHHK) since July, and no FIR-level traffic anomaly in either since 13 November. These are FIR-level observations, not statements about the airport.
Why we cannot confirm it — and what would. At most airports we check a drop like this against a second crowdsourced ADS-B network. At Bao'an that network is effectively blind: in November it holds a single departure on five days and nothing on the rest. Its one-degree grid cell covering Bao'an, Macau and Zhuhai read 1,508–1,589 distinct aircraft a day on 8–15 November, including 1,525 on 15 November, the day our step began — steady, but a cell count includes overflights and is not a movement count; its 16 November figure is not in yet. So there is no independent count, and we do not claim one. A return of Bao'an's departures to their usual 30–70 an hour in the daytime hours (UTC 00:00–14:00), or Macau's count coming back in step with it, is what would end this episode in our data. 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 cannot confirm that. Our observed count at Bao'an fell from a 1,137/day median to 337 on 16 November after a step at 06:00 UTC on 15 November, while our worldwide feed, Guangzhou and Hong Kong kept reading and the weather was visual and calm. Macau also fell sharply, and our notice set for the Guangzhou FIR was last refreshed on 4 October, so we cannot rule a local disruption in or out. The independent network we would use to settle it does not cover SZX. For a specific flight, check the airline and the SZX brief, which updates nightly.
Not in our counts so far. Guangzhou Baiyun read 976 on 16 November, inside its recent range, and Hong Kong 706, near the bottom of its recent range. Macau is the exception: 97 against 247–328 the week before. See the HKG, CAN and MFM briefs.
Not according to the airport's routine weather reports in our set: every report on 15 and 16 November was in visual conditions, mostly CAVOK, with winds up to 12 kt.
We do not make that call — we publish what our monitoring can and cannot measure. Here the measurement itself is in question, so the reading is not by itself evidence of a disruption, and not evidence against one. 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 Shenzhen Bao'an International fell to 337 movements on 16 November 2026 in FlySafe's own crowdsourced ADS-B feed — 70% below its 1,137-a-day median — after a step at 06:00 UTC on 15 November, while the worldwide feed, Guangzhou and Hong Kong kept reading and the weather was visual; Macau also fell sharply, and with no independent count at Bao'an the cause remains unconfirmed, 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.

