DroneRadar Knowledge

Aircraft tracking network analogues — 2026-10-09

Bounded comparison of contributor networks and limits of applying them to drone detection.

Research FindingsDraft record

Scope and evidence status

Question: what can existing aircraft tracking networks establish about community data collection, contributor participation and access to the aggregated data? International scan as of 2026-10-09 (America/Los_Angeles); launch geography is unspecified. The user’s “flightradar” is provisionally interpreted as Flightradar24. This sub-study supports IDEA-001 and covers evidence gathering only; it proposes no subsequent product.

All capabilities, network counts and prices below are official provider claims, with current page/content inspection recorded in the source captures. No field detection, latency, paid API, independent ownership or contributor payout audit was performed. Organization profiles remain draft; the completed independent evidence review and its limits are recorded in study review.

Comparison

Organization and category Collection/deployment Contributor incentive Data access and published price Important limit
Flightradar24 — principal aircraft-network analogue ADS-B/Mode S with MLAT and other aviation inputs; supplied hosted kit, self-build or existing receiver12 Contributor features; no API; downgrade after seven-day feed outage; supplied-kit feeding is exclusive23 Separate API from US$9/month, then $90 and $900, before tax4 A map subscription is not whole-database/API access; aircraft reception is not evidence of drone coverage
ADS-B Exchange — aircraft-network analogue/data supplier Community aircraft-broadcast receivers; live and daily data products7 Ad-free map, receiver statistics/data, alerts and tracking tools after feeder linking5 Non-commercial Community API displayed $10/month/10,000 requests; currency/tax basis not explicit; enterprise annual commitment, price unknown67 “Unmanned Aircraft” currently a placeholder, not a demonstrated drone product8
OpenSky Network — nonprofit research-network analogue Pi/SDR or supported dedicated receiver; raw observations and research datasets911 8,000 API credits/day at >30% current-month receiver uptime; terms say contribution without compensation910 Research access subject to eligibility; commercial/operational licensing required, price unknown10 FAQ/licence inconsistency; FLARM decoding explicitly paused from July 20261112

What the analogy establishes

Analysis: these examples substantiate the existence of distributed contributor programmes and several forms of non-cash benefit. They also show that receiver location, continuity, hardware ownership, contribution rights and rights to consume aggregated data are separate questions. A contributor reward cannot be equated with unrestricted raw-data access. No captured programme demonstrates the viability of paying DroneRadar contributors $10 monthly.235910

The technical analogy ends at the measurement system. Flightradar24’s primary inputs are cooperative aircraft broadcasts and related aviation surveillance data; its receiver manual discusses 1090 MHz line-of-sight reception. OpenSky explicitly describes missing low/out-of-range aircraft and inability to map positionless Mode S observations without MLAT. These evidence limitations mean aircraft receiver counts or range figures cannot determine the required density or coverage of a drone network.1311

No captured analogue source establishes Remote ID reception or non-cooperative drone RF detection as equivalent to ADS-B. The parent study’s technical/background sources should support the detailed modality comparison. Aircraft tracking may include broadcasting unmanned aircraft; that fact would not establish small-drone detection coverage. ADS-B Exchange’s drone-labelled tab is specifically insufficient evidence of such capability.8

Conflicts, search approach and capture gaps

Started with official contributor, technology, API, licensing and data pages; searched within the three assigned official domains. Original HTTP HTML and the receiver PDF were retained. The Flightradar24 API page required browser inspection and a supplemental visible-text capture because HTTP extraction was only an application title; that text lacks collapsed answers, icons, layout and struck-through promotional values. PDF text retains page labels but has per-word breaks; diagrams were not inspected. OpenSky initially returned HTTP 403 to the helper, then yielded original HTML through an ordinary standard-user-agent download. The failed dev-host attempt is also retained under source SRC-b423e55a3ca9; it is not evidence for a claim.

Meaningful changes/conflicts: Flightradar24’s current Contributor name supersedes older descriptions of a Business reward; OpenSky’s permissive FAQ wording conflicts with stricter commercial/operational terms; FLARM collection listings coexist with a decoder-pause notice. ADS-B Exchange’s latency descriptions vary by product; its detailed comparison table offers Live Positions intervals of 5 s, 500 ms or 250 ms. These are not benchmark measurements.21110127

Wing was not added: the assigned three organizations provide the bounded aircraft-network comparison; a drone-operator data cooperative would require separate evidence and ownership coordination. Search results outside assigned domains and unrelated forum opinions were not used as evidence. No implication is made that the landscape is exhaustive.

Remaining research questions

  1. Which desired data rights does “whole database” mean: viewing, downloads, historical queries, raw receptions or redistribution?
  2. Which actual detector outputs and radio modalities will the partner contribute, and with what permitted uses?
  3. What coverage/uptime/quality measures can distinguish useful new observations from redundant ones in the eventual launch geography?
  4. What licences and published hardware/API prices apply to a defined use, and which contributor benefits are current rather than legacy?
  5. Does ADS-B Exchange release its announced unmanned section, and does OpenSky restore FLARM decoding? These are follow-up questions, not monitoring requests.

The company profiles contain original URLs and exact capture links. Shared indexes and study completion status belong to the coordinator.

  1. Flightradar24 how it works, publication date unknown unless noted in text; capture 2026-10-10T04:55:17Z, original.html; primary data sources. Capture is partial; see source record. ↩↩

  2. Flightradar24 contributor programme, publication date unknown unless noted in text; capture 2026-10-10T04:55:04Z, original.html; contributor FAQ, API exclusion and outage grace. Capture is partial; see source record. ↩↩↩↩

  3. Flightradar24 receiver hosting documentation, publication date 2025-09-02 (version 1.3); capture 2026-10-10T04:56:40Z, original.pdf; pp. 3–4, 10; siting and exclusive supplied equipment agreement. Capture is partial; see source record. ↩↩↩

  4. Flightradar24 API subscriptions and credits, publication date unknown unless noted in text; capture 2026-10-10T04:58:17Z, original.txt; supplemental browser text of API plans and tax note. Capture is partial; see source record. ↩

  5. ADS-B Exchange member and feeder benefits, publication date unknown unless noted in text; capture 2026-10-10T04:58:25Z, original.html; Feeder benefits. Capture is partial; see source record. ↩↩

  6. ADS-B Exchange developer hub, publication date unknown unless noted in text; capture 2026-10-10T04:56:15Z, original.html; non-commercial Community API and displayed price. Capture is partial; see source record. ↩

  7. ADS-B Exchange enterprise data products, publication date unknown unless noted in text; capture 2026-10-10T04:56:17Z, original.html; comparison table and annual minimum commitment. Capture is partial; see source record. ↩↩↩

  8. ADS-B Exchange unmanned aircraft announcement tab, publication date unknown unless noted in text; capture 2026-10-10T04:56:19Z, original.html; Unmanned Aircraft announcement placeholder. Capture is partial; see source record. ↩↩

  9. OpenSky feed data, publication date unknown unless noted in text; capture 2026-10-10T04:56:28Z, original.html; API boost and hardware choices. Capture is partial; see source record. ↩↩↩

  10. OpenSky terms of use and data license, publication date unknown unless noted in text; capture 2026-10-10T04:56:48Z, original.html; commercial/operational licence and no-compensation clauses. Capture is partial; see source record. ↩↩↩↩

  11. OpenSky FAQ, publication date unknown unless noted in text; capture 2026-10-10T04:56:48Z, original.html; questions 2–7, 18. Capture is partial; see source record. ↩↩↩↩

  12. OpenSky FLARM status, publication date unknown unless noted in text; capture 2026-10-10T04:56:49Z, original.html; July 2026 decoder pause. Capture is partial; see source record. ↩↩

Sources, provenance and record details
Record type
Research Findings
Status
draft
Generated
by: codex/session at: '2026-10-10T05:00:43Z'
Recorded checks
No verification metadata recorded.

Sources

All record metadata
type: Research Findings
title: Aircraft tracking network analogues — 2026-10-09
description: Bounded comparison of contributor networks and limits of applying them
  to drone detection.
status: draft
generated:
  by: codex/session
  at: '2026-10-10T05:00:43Z'
sources:
- id: fr-how
  resource: /references/SRC-a7a1b1b37c47/source.md
  title: Flightradar24 how it works
- id: fr-contribute
  resource: /references/SRC-e0833c15274c/source.md
  title: Flightradar24 contributor programme
- id: fr-manual
  resource: /references/SRC-32155fe3f1ac/source.md
  title: Flightradar24 receiver hosting documentation
- id: fr-price
  resource: /references/SRC-cf26ba1d0964/source.md
  title: Flightradar24 API subscriptions and credits
- id: ax-member
  resource: /references/SRC-810d96f017bf/source.md
  title: ADS-B Exchange member and feeder benefits
- id: ax-dev
  resource: /references/SRC-959664b5ba82/source.md
  title: ADS-B Exchange developer hub
- id: ax-products
  resource: /references/SRC-3d70f64ea84c/source.md
  title: ADS-B Exchange enterprise data products
- id: ax-unmanned
  resource: /references/SRC-cc5d01e606b3/source.md
  title: ADS-B Exchange unmanned aircraft announcement tab
- id: os-feed
  resource: /references/SRC-f1a096ef31b5/source.md
  title: OpenSky feed data
- id: os-terms
  resource: /references/SRC-a58f4f68e30f/source.md
  title: OpenSky terms of use and data license
- id: os-faq
  resource: /references/SRC-5a3f5cd3951c/source.md
  title: OpenSky FAQ
- id: os-flarm
  resource: /references/SRC-c368e5f008a8/source.md
  title: OpenSky FLARM status