The Regulatory Landscape
One of FliteGrid's strongest differentiators is that its market opportunity is driven by federal regulation, not speculation. This page explains the regulatory framework that creates demand for nationwide drone tracking data.
UAS Traffic Management (UTM)
As drone operations scale beyond hobbyist use into commercial delivery, autonomous inspection, urban air mobility, and large-scale public safety operations, the FAA needs a system to manage that traffic. That system is called UAS Traffic Management, or UTM.
UTM is designed to be the drone equivalent of air traffic control. It's a federated network that will connect data providers, drone operators, and regulators to enable safe, coordinated drone flight at scale. Without UTM, large-scale commercial drone operations can't happen. You can't have thousands of delivery drones flying simultaneously in a city without a system to coordinate their routes, prevent collisions, and enforce airspace rules.
The FAA has deliberately chosen a federated, private-sector-driven approach. Rather than building and operating the system itself, the FAA is defining the rules and certifying the companies that will provide the underlying infrastructure and data services.
For more on the FAA's vision: FAA UAS Traffic Management
Automated Data Service Providers (ADSPs)
In 2025, the FAA published its Drone Integration Concept of Operations, a document laying out its conceptual vision for the next decade of drone operations in the national airspace. Page 12 introduces the concept of Automated Data Service Providers (ADSPs): certified private-sector companies that provide the data services UTM depends on.
The FAA's Part 146 rulemaking establishes the certification framework for ADSPs, creating a formal, federally defined role for companies that provide drone data services. This is described in detail in the 2025 BVLOS rulemaking:
Part 146 is significant because it doesn't just suggest that drone data providers would be useful. It creates a regulatory category for them and defines the certification process. The FAA is building the institutional framework for companies like SkySafe to serve as certified infrastructure providers in the national airspace system.
Remote ID as the Foundation
Remote ID is the data layer that everything else builds on. The FAA mandated that all drones broadcast Remote ID starting March 2024, creating a universal, standardized data source for drone identification and tracking. UTM, BVLOS operations, and airspace management all depend on having access to this data.
But the mandate only covers the broadcast side. No equivalent regulation requires anyone to build the receiver infrastructure to collect Remote ID data at scale. The FAA defined the data source. The ADSP framework defines the role for providers. But the actual infrastructure to bridge the two doesn't exist yet.
That gap is exactly what FliteGrid solves.
The Technical Standard: ASTM F3411
The technical specification behind Remote ID is ASTM F3411, published by ASTM International. This standard defines the broadcast protocols, data formats, and message structures that drones use to transmit their identity and location information.
F3411 is referenced directly by the FAA in its Remote ID rule, making it the governing technical standard for all Remote ID broadcasts in US airspace. SkySafe's receiver software is fully validated against F3411, including all protocol variants.
Beyond Visual Line of Sight (BVLOS)
Much of the commercial potential of drones depends on BVLOS operations: flights where the drone operates beyond the pilot's direct visual contact. Package delivery, long-range infrastructure inspection, agricultural monitoring at scale, and urban air mobility all require BVLOS capability.
The FAA's Part 108 rulemaking (published in 2025) establishes the anticipated framework for regulating BVLOS drone operations. A core requirement is that BVLOS operations depend on robust data services, including the airspace awareness that ADSPs provide.
In other words, for drones to fly beyond line of sight at scale, the FAA requires the kind of real-time airspace data that FliteGrid generates. The more coverage the FliteGrid network provides, the more BVLOS operations it can support, and the larger the addressable market becomes.
International Regulations
The US isn't alone in mandating Remote ID. The EU and Japan have both adopted similar requirements, creating parallel opportunities for FliteGrid expansion:
European Union: The EU's U-space regulatory framework includes Remote ID requirements as part of its broader approach to drone traffic management. Implementation timelines vary by member state, but the regulatory direction is clear.
Japan: Japan was one of the first countries to implement Remote ID requirements and has an active drone delivery and inspection ecosystem that needs airspace monitoring.
United Kingdom: Drone Remote ID requirements have just begun in the UK, starting January 1, 2026. You can see the current status of the requirements on the UK Civil Aviation Authority’s website.
FliteGrid's international expansion (planned for 2027) targets these markets, where the same regulatory dynamics that drive US demand are playing out on their own timelines.
As other countries’ requirements evolve (Australia, Canada, etc.), we’ll launch in those countries to provide the critically needed infrastructure.
Why This Matters
Most DePIN projects are building infrastructure and hoping that demand develops. FliteGrid is building infrastructure into a market where demand is literally mandated by the federal government.
The FAA has said: drones must broadcast. The FAA has said: certified data service providers will be needed. The FAA has said: BVLOS depends on airspace awareness data. All of this points to a defined, growing market for exactly the kind of data FliteGrid produces.
This regulatory alignment is a structural advantage that very few DePIN projects can claim.
Last updated