466 of 1163 airports with a live pulse · vs each airport's own weekday normal · Monday 09 Nov
Today's movers — vs their own normal
Deviation is measured against each airport's own typical volume for that weekday over 30 days — never airport vs airport. Only airports with a meaningful baseline are listed.
What Airport Pulse is
One number per airport per day: departures + arrivals detected by the crowdsourced ADS-B receiver network. Every aircraft flying with a transponder is visible to volunteer ground receivers; the network estimates the departure and arrival airport of each flight, and we count what was seen at each field on the latest complete UTC day.
Read it as a heartbeat, not a turnstile. The absolute count is a floor — "at least this many" — because receiver coverage varies by region. What carries the signal is the shape: the weekly rhythm, the trend, and deviations from the airport's own normal. That is why every pulse is compared against the same airport's typical volume for that weekday, never against another airport.
Honesty rules built into the data: days where the global collection network itself failed are flagged as gaps — drawn as dashed holes on charts, excluded from every average and baseline, never rendered as "traffic collapsed". Airports where coverage is too thin for a reliable figure show an honest "insufficient coverage" note instead of a guessed number.
What it is not: not official airport statistics, not a schedule, not passenger numbers — and not a safety verdict. Airport Pulse is an observation layer. Risk judgment — folding regulatory, conflict, ash, GNSS and weather signals into one score — is what the FlySafe Console does, per route.
Most-observed airports — Monday 09 Nov
Top 50 by observed movements. "vs typical" compares to the same airport's own weekday baseline.
Every airport with a live pulse has its own brief with the 30-day curve, weather and airspace context — browse all 1163 airports →
Cite & reuse
Airport Pulse figures and charts are free to cite and republish with a visible link to the airport's brief or this page. Suggested attribution: "Source: FlySafe.zone Airport Pulse — observed ADS-B activity" + link. Movement observations are derived from OpenSky Network crowdsourced ADS-B data; keep that credit intact when republishing.
Press assets (hi-res charts, CSV series) and pulse alerts are being prepared — if you are a journalist or researcher and want early access, reach out via the contact page.
Planning a route through any of these airports? Score it in the free Console — the same engine folds ash, GNSS, regulatory and conflict signals into one 0–100 route index.
Generated 16 Nov, 12:26 UTC · observations, not operational guidance — flight planning requires official briefings.