AeroScope operates no receivers and holds no private feed. Every data point traces back to a public source — all of them listed here so results can be independently checked.
AeroScope holds no private feed and operates no receivers of its own. Everything it shows is derived from public sources, listed here so any result can be traced back to its origin and independently checked.
| Source | Provides | Nature |
|---|---|---|
| adsb.fi | Live ADS-B aircraft positions and velocity | Volunteer receiver network, open data |
| adsb.lol | Live ADS-B positions, including unfiltered traffic | Volunteer receiver network, open data |
| airplanes.live | Live ADS-B positions | Volunteer receiver network, open data |
| OpenSky Network | Live and historical ADS-B state vectors | Research network (academic/community) |
| ADS-B Exchange lineage feeds | Unfiltered aircraft traffic | Community network |
| hexdb.io | ICAO 24-bit hex → registration, type, operator | Registry lookup |
| aviationweather.gov | METAR / TAF aviation weather | Government open data (NOAA/NWS) |
| Satellite ADS-B merge | Supplementary coverage over oceans and remote regions | Space-based ADS-B |
| De-duplication | The same airframe reported by several networks is merged on its ICAO 24-bit address, so one aircraft is one track — not three dots. |
|---|---|
| Position refresh | Positions refresh on a fast loop of roughly 7 seconds; the client dead-reckons between fixes so motion is continuous rather than jumping. |
| Enrichment cadence | The heavier enrichment-and-detection pipeline runs on its own cycle of about 12 seconds, so analysis never blocks the map. |
| Registry enrichment | Type, operator and wake category are attached by hex lookup where the registry has a record; fields are left blank rather than guessed when it does not. |
| Conflict handling | Where feeds disagree, the most recent well-formed message wins, and self-inconsistent messages are flagged by the integrity checks rather than silently averaged. |
AeroScope exists because thousands of volunteers run ADS-B receivers and publish the results openly. Each upstream network sets its own terms of use; we consume public endpoints at a modest polling rate and cache aggressively to limit load on them. If you operate one of these networks and want your attribution changed or your feed removed, contact us and we will act on it.
Our own derived work — the AeroScope ADS-B Anomaly Benchmark — is published under CC-BY 4.0 so it can be reused and cited freely.