Pricing Search Start free trial
// EVENT · TROPICAL CYCLONE CLOSED · cyclone signals cleared, TPE held near baseline Data as of 15 Aug 2026, 21:48 UTC

Typhoon Dolphin — Shanghai airspace and Taipei's fast recovery, August 2026

← All airspace events

Typhoon Dolphin peaked at 115 kt (Category-4 equivalent) on 4 August and made landfall on the Zhejiang–Fujian coast on 9 August at ~74 kt (IBTrACS best-track). The Shanghai FIR (ZSHA) carried cyclone-related NOTAMs from 6 August — corroborated in our detection layer by tropical-cyclone SIGMETs and traffic anomalies — and those cyclone signals have since cleared, so the event is closed. The cleanest measured impact: observed traffic at Taipei Taoyuan (TPE) dipped to 521 movements on 8 August (−17% vs a ~627 baseline) as the storm crossed the strait, held near normal (600) on landfall day, and was back to 687 — ~10% above baseline — by 10 August.
// Flew to East China or Taiwan this week? The short version
  • Taipei (TPE) never shut down — traffic dipped ~17% before landfall and was back above its normal level by 10 August.
  • Shanghai area (PVG/SHA) and coastal Zhejiang–Fujian: the cyclone-related NOTAM set has unwound and the cyclone signals have cleared; only routine summer thunderstorm activity remains.
  • Typhoon disruptions are front-loaded: airlines cancel in waves before landfall and restore fast after — a cancelled evening flight often flies normally the next morning.

Advisory timeline — how active is this episode

Dolphin's best-track history: rapid intensification to 115 kt (Category-4 equivalent) on 4 August, then steady weakening on approach to the coast — landfall 9 August at ~74 kt near the Zhejiang–Fujian border, dissipating inland thereafter. Shanghai FIR (ZSHA) carried cyclone-related NOTAMs from 6 August (incl. ZSSS Shanghai-Hongqiao series), corroborated by tropical-cyclone SIGMETs and traffic anomalies in our detection layer. Daily peak intensity:

96
3 Aug
115
4 Aug
99
5 Aug
82
6 Aug
89
7 Aug
80
8 Aug
74
9 Aug

Fig. 1 — Typhoon Dolphin daily peak intensity (kt), IBTrACS best-track · Data as of 15 Aug 2026, 21:48 UTC · Source: IBTrACS best-track, WMO/USA agencies (public).

Airports in the exposure zone

AirportSizeExposureFIR
Taipei Taoyuan (TPE) large — · strait transit 8–9 Aug RCAA
Wenzhou Longwan (WNZ) large — · near landfall point ZSHA
Shanghai Pudong (PVG) large — · cyclone NOTAMs cleared ZSHA
Shanghai Hongqiao (SHA) large — · cyclone NOTAMs cleared ZSHA
Hangzhou Xiaoshan (HGH) large — · inland track ZSHA

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: Taipei's pre-emptive dip and fast return

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. Taipei Taoyuan's last 30 days:

Fig. 2 — Observed daily movements at TPE, 12 Jul – 11 Aug (latest complete UTC day). Data as of 15 Aug 2026, 21:48 UTC · Source: FlySafe monitoring (ADS-B receiver network).

  • 30-day pre-typhoon baseline: ~627 observed movements/day (mean, 8 Jul–7 Aug).
  • 8 Aug, as Dolphin crossed the Taiwan Strait: 521 (−17%) — a front-loaded, pre-emptive cancellation wave.
  • 9 Aug (landfall day): 600 — operations held near normal; the storm made landfall on the mainland coast, not over Taipei. Revision note: an early partial-coverage reading for this day has since been backfilled — there was no measured near-standstill at Taipei.
  • 10 Aug: 687 movements — ~10% above baseline, within 48 hours of the dip. Full recovery, firmly covered.
  • Coverage gaps: our receiver feed shows 27 (12 Aug) and 74 (14 Aug) — both flagged as partial coverage, cross-checked as normal traffic on an independent ADS-B feed, and must not be read as disruption.

The shape is the classic typhoon signature: a pre-emptive wind-down and a fast return — front-loaded and short, fundamentally different from the multi-day saw-tooth of volcanic ash. Live view: TPE airport brief.

What it means for flights

Typhoons stop airports differently than ash does. Ash is an engine problem; wind is a runway problem. Operations halt when crosswind and gust limits are exceeded and ground handling becomes unsafe — and resume as soon as the wind drops. That is why typhoon disruption is front-loaded (pre-emptive cancellation waves, position flights out of the storm's path) and recovery is fast, exactly the dip-and-return shape measured at Taipei (baseline ~627 → 521 on 8 Aug → 687 on 10 Aug).

Shanghai FIR: what the signals said. We do not have honest ADS-B receiver coverage inside mainland China, so we do not publish observed counts for PVG/SHA — instead our detection layer tracked the airspace itself: cyclone-related NOTAMs (including the Shanghai-Hongqiao ZSSS series), tropical-cyclone SIGMETs and en-route traffic anomalies kept the ZSHA event open from 6 August. Those cyclone-specific signals have since cleared — only routine summer thunderstorm (TS) SIGMETs remain, which are the region's August base rate, not Dolphin. Three independent signal classes agreeing was our bar for calling it a real operational event; their joint clearing for more than 48 hours is our bar for closing it.

The remnant phase still mattered. A landfalling typhoon's aviation impact does not end at landfall: inland rain bands drive low ceilings, holding and flow control for another one to two days along the track. The NOTAM set unwinding — not the calendar — was the signal that ZSHA operations were back to normal, and that unwind is now complete.

Why Taipei barely dropped. Taiwan's carriers run one of the world's most rehearsed typhoon playbooks: batch pre-cancellation, aircraft repositioned out of the strait, then a surge schedule to clear the backlog. In our data that shows up as a shallow, front-loaded dip (521 on 8 August) rather than a shutdown, with 10 August running above baseline (687 vs ~627) as the recovery day absorbs the cancelled demand.

What the data showed. Across the full 3–14 August window, Taipei Taoyuan's measured signature was modest and front-loaded: a ~17% pre-emptive dip to 521 movements on 8 August (vs a ~627 baseline), near-normal operations on landfall day (600 on 9 Aug), and a return to 687 movements — ~10% above baseline — by 10 August. Two later days in our receiver feed (27 on 12 Aug, 74 on 14 Aug) are coverage gaps, cross-checked as normal on an independent ADS-B feed, and are not disruption. Inside mainland China we do not publish observed counts; there the airspace signals themselves — cyclone-related NOTAMs and tropical-cyclone SIGMETs across the Shanghai FIR — have cleared, leaving only routine summer thunderstorm activity, and have stayed clear for more than 48 hours. This automated multi-signal analysis surfaces cadence inflections early and closes them out when the airspace signals clear — the operating decision on any given day stays with the airport, the airline and the relevant authorities.

Passenger questions, answered from the data

Are Shanghai flights still affected by Typhoon Dolphin?

No — the Shanghai FIR carried cyclone-related NOTAMs from 6 August, but those cyclone signals have cleared and the event closed on 15 August after more than 48 hours with no residual cyclone activity; only routine summer thunderstorm SIGMETs remain. Always check your airline's status on the day of travel.

Is Taipei airport back to normal after the typhoon?

Yes — observed traffic at TPE dipped to 521 movements on 8 August (−17% vs a ~627 baseline) and was back to 687 on 10 August, about 10% above baseline, within 48 hours. The TPE brief updates nightly.

Is it safe to fly near a typhoon?

Aircraft do not fly through typhoons — dispatchers route around them, and airports in the wind field pause operations under crosswind limits set by regulators and manufacturers. We publish the measured operational picture; routing and go/no-go decisions belong to operators and authorities.

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

“Observed traffic at Taipei Taoyuan dipped about 17% to 521 movements on the day Typhoon Dolphin crossed the Taiwan Strait and returned to 687 — roughly 10% above its ~627-movement daily baseline — within 48 hours, while the Shanghai FIR's cyclone-related NOTAMs and SIGMETs have since cleared, according to flight-monitoring service FlySafe.zone.”

Chart: observed traffic at TPE
PNG · 1600px · attribution baked in
Observed daily movements at TPE — light version preview
Chart: advisory cadence
PNG · 1600px · attribution baked in
Typhoon Dolphin daily peak intensity (kt), IBTrACS best-track — 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 — Typhoon Dolphin — Shanghai airspace and Taipei's fast recovery, August 2026", https://flysafe.zone/events/typhoon-dolphin-2026-08/, data as of 15 Aug 2026, 21:48 UTC — free to cite with a link. Observed-traffic figures are FlySafe’s own ADS-B-derived counts (floor, not total). Storm track and intensity attributed to IBTrACS best-track (public); airspace signals from published NOTAMs and SIGMETs. Method: /methodology/ · Press: /press/.

Related coverage