Data sources
Everything on this site that is not our own runway scoring comes from somewhere else. This page credits each source, states the licence where one applies, and describes what we do to the flight data we store. The same short flight-data credit appears wherever live traffic is shown.
ADS-B flight data
Contains information from adsb.lol, made available under the ODbL 1.0
Aircraft positions reach us from community feeds: adsb.lol, airplanes.live, adsb.fi, and adsb.one. adsb.lol publishes under the Open Database License 1.0. The live radar map and the arrivals and departures board try adsb.lol first when a server API key is set and a strict request budget allows it, then fall back to airplanes.live, adsb.fi, and adsb.one. Ingestion uses its own adsb.lol key on a five minute schedule. Our own data service also stores positions from these feeds for history and for landing and takeoff detection.
How we process ADS-B data
A separate service, aviation-data-ingestion, polls the point endpoints of those feeds every five minutes for each airport we track, using a 40 NM box around the field. It asks adsb.lol first and moves to the next feed only when that request fails or is cooling down, so a stored row almost always names a single feed.
Each poll appends one row per aircraft to adsb_positions, tagged with the feed it came from. The fields kept are ICAO 24-bit address, callsign, registration, aircraft type, latitude and longitude, altitude, on-ground flag, ground speed, track, vertical rate, squawk, airport code, feed name, capture time. The feed itself carries no route, so origin and destination are not taken from it: they come from a separate callsign lookup that the same service caches.
Rows are appended, never merged row by row. If two feeds report the same aircraft, both of their rows are kept and the feed column tells them apart, which is why a position can be traced back to the source that published it. Within one captured batch an aircraft appears once. Landings and takeoffs are then derived from the stored positions into a separate events table. Position rows are kept for 7 days and pruned after that.
Changes to the source data and how to get it
We do not republish the adsb.lol database. We combine its positions with positions from other feeds and with derived landing and takeoff events, and we keep only the fields listed above. This page is our description of those alterations, offered under section 4.6 of the ODbL. The derived data is available on request: email louis@cdb.solutions and tell us what you need.
All sources
Aircraft positions for the live radar map, the arrivals and departures board, and stored position history.
ODbL 1.0. Our first-choice feed.
Aircraft positions, used when adsb.lol does not answer.
Community feed. Terms as published by the provider.
Aircraft positions, used when the feeds above do not answer.
Community feed. Terms as published by the provider.
Aircraft positions, used when the feeds above do not answer.
Community feed. Terms as published by the provider.
METAR observations, TAF forecasts, and airport reference data that drive the runway call.
US Government work, public domain.
D-ATIS text for US airports, used to confirm which runway is in use.
Community service. Terms as published by the provider.
Runway geometry, airport names, and radio frequencies.
Public domain.
Street map tiles, and public parks and viewpoints found through the Overpass API.
ODbL 1.0, © OpenStreetMap contributors.
Satellite map tiles, the default basemap.
Tiles served by Esri. Terms as published by the provider.
A dark basemap that is in the code and is not requested by the current map switch.
Terms as published by the provider.
The optional precipitation radar overlay.
Public radar tiles. Terms as published by the provider.
Community spot candidates found by geosearch, each credited with its own file page and author.
Per-file licences, shown on the file page.
Airline schedules, which our data service stores and the board shows as SCHEDULE rows.
Commercial API. Terms as published by the provider.
Callsign to route lookups, cached by our data service and shown as origin and destination codes.
Community API. Terms as published by the provider.
Sun position, golden hour, and backlight warnings.
BSD 2-Clause.
Time zone for each airport, so clocks render local to the field.
CC0 1.0.
Map tiles
Satellite tiles are served by Esri. Street tiles and the public parks and viewpoints we find through Overpass are © OpenStreetMap contributors, under the ODbL. A CARTO dark basemap is in the code but is not requested by the current map switch. The optional precipitation overlay is RainViewer.
Corrections
If a credit here is wrong or incomplete, email louis@cdb.solutions and we will fix it.