Current drone detection and data-network landscape — 2026-10-09
Bounded international evidence scan linked to IDEA-001.
Research question and decision served
What observable drone detection/data networks, hardware/data providers, and contributor-network analogues exist, and what can their published evidence establish about data collection? This supplies evidence for the user's data-gathering stage; later product ideas are reserved for the user.1
Scope
International discovery, with English-language official sources and explicit geographic limitations; no launch country assumed. Snapshot date: 2026-10-09 America/Los_Angeles (captures may be 2026-10-10 UTC). “Flightradar” provisionally means Flightradar24. Related idea: IDEA-001.
Three separate categories: direct drone detection/data networks; hardware and data providers; crowdsourced sensor/aircraft-tracking analogues. No implementation, live detector integration, deployment, economics validation, external publication, or recurring monitoring.
Deliverables and completion criteria
Preserved user steering; canonical company profiles with official identities, status, collection/output, deployment, participation/incentives, access, pricing, coverage and gaps; archived originals and readable extractions with provenance; sourced findings and comparison; compiled summary and unanswered questions. Complete after independent evidence review and resolved/disclosed findings, index rebuild and validator pass. A complete study is not exhaustive market coverage or proof of vendor performance.
Search approach and existing evidence
Begin at DroneSight and Flightradar24. Expand through official product/contributor/API pages and official technical background. Reuse the Bluebird user-context-only record; do not silently identify the partner. Search relevant providers across Remote ID, RF and radar modalities. Record rejected/deferred candidates and capture failures in findings.
Deliverables
- Compiled summary and comparison
- Direct-network findings, including DroneSight, Dronetag and the separately labelled Wingbits analogue
- Hardware and managed-data findings
- Aircraft-network analogue findings
- Technical and geographic background
- Capture manifest and independent evidence review
- Canonical profiles, including the coordinator's SkySafe/FliteGrid and BlueMark evidence
Progress
Work status: complete. Twelve organizations researched; existing Bluebird record retained without resolving its identity by guesswork. User steering, source archive, profiles, findings and compiled comparison are complete. Independent evidence review found no material attribution mismatch; all 61 captures passed integrity checks. Indexes and knowledge validation passed; final bookkeeping checks are recorded in review. Next action: no further work within this bounded assignment; await user direction on the prioritized research questions below.
Ownership: coordinator owns shared brief, summary, technical background, SkySafe/BlueMark profiles and sources, indexes and user steering. Three bounded researchers own separate direct-network, hardware/provider and aircraft-analogue profiles and sources; one independent reviewer is read-only. No source URL has concurrent writers.
Unresolved research questions: launch geography, Bluebird/Chewica identity, detector export fields and permitted uses, actual provider coverage/performance, operational/API availability and license terms, and contributor payout evidence. These are disclosed study gaps and future research directions, not blockers to this scoped landscape inventory.
-
Preserved user steering and task context. ↩