Drone detection and data networks — current landscape

Answer to the research question

There are already several distinct ways to collect and aggregate drone observations. DroneSight is a close community-hosted Remote ID comparison; SkySafe/FliteGrid publishes a conditional paid-host program but currently gives no promised sensor shipment date; DedroneCity markets managed detection-data access. Dronetag and BlueMark expose receiver integration paths. These offers are evidence of a landscape, not proof of comprehensive detection, successful host payouts or sustainable DroneRadar economics.¹²³⁴⁵

“Flightradar” is provisionally interpreted as Flightradar24, as requested. Its useful analogy is a distributed collection network with contributor benefits and separately controlled commercial data access. Aircraft tracking does not establish that the same receiver, coverage geometry or data completeness applies to drones.⁹¹³

Snapshot: 2026-10-09 America/Los_Angeles. International discovery with English-language official sources; no launch geography assumed. This bounded study covers 12 researched organizations plus the existing unresolved Bluebird partner record. The user's direction is to gather data now and supply later-stage ideas separately; no product design or implementation is proposed here.¹⁴

Comparison

All operating, coverage and performance claims below are vendor statements unless explicitly identified as direct inspection of a public document. “Not established” means absent from this bounded evidence set, not necessarily unavailable commercially. See each linked canonical profile for geography, source dates, prices, uncertainties and exact captures.

Direct drone networks and detection-data services

Organization	Collection and product output	Deployment and contribution	Access, price and current evidence
DroneSight	ASTM F3411 Remote ID → mapped drone activity	Selected beta hosts; free loaned indoor receiver, host power/Wi-Fi	Host beta access/premium features; no cash reward or public API established; live traffic not captured1
SkySafe / FliteGrid	Enterprise passive RF service; distinct FliteGrid Remote ID → LTE uplink	Vendor-owned host sensor; advertised $50 USDC/eligible month at 95% uptime; $100 refundable deposit plus shipping	FliteGrid reservations, shipment date pending; continental US host scope; enterprise feed price/API rights not established2
Dedrone by Axon	RF and multi-sensor systems; DedroneCity alerts, locations and history	Customer sensor deployments or managed city network; no public paid-host program established	Vendor claims 50+ cities; no numeric data price or public bulk license captured3

Relevant hardware and data-interface providers

Organization	Collection and outputs	Deployment / participation	Price/access and limiting evidence
Dronetag	Remote ID raw feeds and cloud history; claimed receiver network	Purchased Scout receivers; no host-payment program found	Scout from €3,099/$3,499; licensed cloud/local modes, authenticated APIs; Sensor+ pricing conflicts with future-development wording4
BlueMark / DroneScout	Remote ID → local JSON/MQTT; Bridge phone relay/MAVLink	Customer fixed/mobile/embedded receivers	ds230 €950; ds240 €1,650; Bridge ds110 retail €149, excluding VAT; local interface is not shared-network data access5
DroneShield	Passive RF alerts plus fused C2 records	Customer site/mobile systems; multi-site aggregation	RESTful API advertised, price/schema/resale rights not established; no crowd-host program evidenced6
DJI AeroScope	Legacy proprietary DJI identification/telemetry receiver	Institutional deployments	Official service suspension 2026-04-15 for both variants; surviving order page conflicts; no supported current supply inferred7
Robin Radar IRIS	Active radar → physical target detection/classification and 3D tracks	Enterprise radar plus processing station	C2 interfaces documented; price not established; radar track ≠ broadcast serial/operator identity8

Crowdsourced aircraft-data analogues

Organization	Collection / output	Contributor model	Access and comparison limit
Flightradar24	Aircraft tracking from several sources, including ADS-B and MLAT	Own receiver or selected hosted kit; Contributor subscription benefit	Contributor plan excludes API; separate API from US$9/month before tax; does not establish broad drone detection9
ADS-B Exchange	Aircraft ADS-B/Mode S/MLAT data	Feeder benefits; community participation	Community API displayed $10/month (currency/tax unspecified) for noncommercial use; this is a buyer fee, not contributor pay; unmanned offer not demonstrated10
OpenSky Network	Research-oriented aircraft observations and historical access	Volunteer feed, contributor API allocation benefit	Commercial/operational use requires written license; no compensation promised in terms11
Wingbits	ADS-B observations → live/history API	Purchased approved stations, geographic placement and variable token/partner rewards	Public OpenAPI schema captured; numeric plan prices not captured; no fixed cash return evidenced12

What the Flightradar24 analogy does and does not support

It supports studying distributed receiver placement, contributor onboarding, uptime-linked benefits and aggregation into a common view. The observed commercial/API boundaries also show why “access to the whole database” needs a precise definition: account visibility, own-station observations, history, API quotas and redistribution are separate entitlements.⁹¹⁰¹¹

It does not support assuming all drones broadcast a compatible signal, treating aircraft reception ranges as drone ranges, assuming RF alerts always include coordinates, or reading vendor node counts as measured airspace coverage. Remote ID packets, broader RF-link detection and active-radar tracks represent different observations. FAA background itself describes RID exceptions and different location fields for standard RID versus add-on modules.¹³³⁸

Analysis: the relevant comparison is the mechanism of contribution and data access. A common map does not make the underlying measurements equivalent. No source in this study validates IDEA-001's proposed $10 monthly payment; the FliteGrid offer also has different ownership, connectivity, geographic and uptime conditions.¹⁴²

Important uncertainties and contradictions

• Availability: DroneSight is advertised private beta; FliteGrid has pending shipment dates. A live website or account form does not demonstrate fulfilled deployment.¹²
• Lifecycle: DJI's current order copy conflicts with its dated suspension notice.⁷
• Documentation: Dronetag Sensor+ status, Dedrone site/model counts, Robin power specifications, and FliteGrid payment-administration guidance disagree across vendor documents. The profiles preserve these conflicts.⁴³⁸²
• Verification: No independent comparative field trials, audited active receiver/coverage counts, completed community payout histories or negotiated redistribution licenses were obtained. Vendor claims remain vendor claims.
• Capture: Some dynamic maps/pricing and authenticated dashboards are absent. Wingbits numeric pricing was not captured. Flightradar24 numeric API prices were recovered through a supplemental browser-text capture, with layout and collapsed-content limitations. Source records retain failed attempts and successful follow-ups; the archive manifest distinguishes them. Original HTML is not a full rendered website.
• Scope: This is an international discovery scan, not an exhaustive worldwide vendor census. Official evidence is strongest for US/European services and globally marketed suppliers. It does not establish launch-country legal/data-use permissions. Bluebird/Chewica remains user-provided partner context.

Unanswered questions and next research directions

1. Geography and observed population: Which country and which drone classes/signals should future evidence gathering prioritize?
2. Partner evidence: What exact entity/product is Bluebird/Chewica, and what fields, timestamps, confidence measures and export rights does it provide?
3. Actual availability: Can DroneSight and FliteGrid substantiate delivered receivers, active coverage and data/payout access? Can Dronetag resolve its mode/pricing conflict?
4. Data rights and quality: For the most relevant networks, what sample records, schemas, retention, duplication rules, API limits and redistribution licenses are actually available?
5. Independent observations: What receiver tests and customer deployments establish missed detections, false positives, geolocation uncertainty and site-dependent coverage?

These are research directions, not accepted product decisions or permission to contact vendors. Detailed evidence: direct-network findings, hardware findings, aircraft analogues, technical background, and capture manifest.

Review and completion

The bounded study is complete. An independent reviewer checked all 12 profiles, four findings documents, this synthesis and the archive manifest, reporting no material claim-to-evidence mismatch. All 61 saved captures passed checksum/byte-count checks. Index rebuild and knowledge validation passed. Review scope and limitations are recorded separately; this verifies attribution and archive integrity, not vendor performance. No product, incentive or deployment decision was made.

type: Research Summary
title: Drone detection and data networks — current landscape
description: Compiled comparison and evidence limits for the 2026-10-09 international
  scan.
status: draft
generated:
  by: codex/session
  at: '2026-10-10T05:02:57Z'
sources:
- id: dronesight
  resource: /research/companies/dronesight.md
  title: DroneSight
- id: skysafe
  resource: /research/companies/skysafe.md
  title: SkySafe — FliteGrid and enterprise drone-data network
- id: dedrone
  resource: /research/companies/dedrone.md
  title: Dedrone by Axon
- id: dronetag
  resource: /research/companies/dronetag.md
  title: Dronetag
- id: bluemark
  resource: /research/companies/bluemark.md
  title: BlueMark Innovations BV — DroneScout
- id: droneshield
  resource: /research/companies/droneshield.md
  title: DroneShield
- id: dji
  resource: /research/companies/dji.md
  title: DJI — AeroScope
- id: robin-radar
  resource: /research/companies/robin-radar.md
  title: Robin Radar Systems — IRIS
- id: flightradar24
  resource: /research/companies/flightradar24.md
  title: Flightradar24
- id: adsb-exchange
  resource: /research/companies/adsb-exchange.md
  title: ADS-B Exchange
- id: opensky-network
  resource: /research/companies/opensky-network.md
  title: OpenSky Network
- id: wingbits
  resource: /research/companies/wingbits.md
  title: Wingbits
- id: background
  resource: /research/studies/RES-001-current-landscape/technical-background.md
  title: Official technical background
- id: steering
  resource: /docs/project-information/ideas/IDEA-001-community-detector-network/input-2026-10-09-data-focus.md
  title: User steering
x_work_status: complete