For the complete documentation index, see llms.txt. This page is also available as Markdown.

Coverage & Hex Values

FliteGrid uses a hexagonal grid system to map airspace coverage across the country. Whether a hex is eligible for payment determines whether hosting a sensor there earns you $50 per month.

The H3 Grid System

FliteGrid divides the map into hexagonal cells using Uber's H3 geospatial indexing system, an open-source standard used widely across the geospatial industry.

The network operates at H3 resolution 8. Each hex covers roughly 0.7 square kilometers, which maps closely to the real-world reception range of a well-placed Remote ID sensor. That sizing is the reason for the network's simplest rule: one sensor per hex, one deployer per hex. A single well-positioned sensor covers its hex, so there's no reason to stack redundant hardware in the same airspace, and no ambiguity about who covers what.

Eligible Hexes

Not all airspace needs coverage equally. A hex covering a major airport matters far more to FliteGrid's customers than a hex over open farmland. So hexes come in two kinds:

Eligible hexes cover airspace where drone tracking data is commercially valuable. Hosting an online sensor in an eligible hex pays $50 per month, flat. Eligible hexes cluster around:

  • Airports — Unauthorized drone activity near airports poses direct safety risks to manned aviation.

  • Critical infrastructure — Power plants, substations, transmission lines, water treatment facilities, refineries, and data centers.

  • Correctional facilities — Prisons dealing with a surge in drone-based contraband smuggling.

  • Stadiums and event venues — Large public gatherings where unauthorized drones pose safety and security threats.

  • Military installations — Bases requiring comprehensive airspace awareness.

  • Border zones — Wide-area drone detection for border security operations.

  • Universities — Large campuses with sporting events, research facilities, and dense populations.

  • Transportation infrastructure — Ports, railyards, and major transportation corridors.

All other hexes are not currently eligible for payment. The network's goal is coverage where customers need it, and the payment model keeps sensor deployment pointed at exactly those places.

You don't need to be directly on top of a facility. Eligibility is determined hex by hex, and the coverage map at flitegrid.io shows you precisely which hexes qualify.

Eligibility Can Change

Hex eligibility reflects current customer demand and airspace priorities, and those evolve. New customers, new facilities, and new regulatory requirements can make previously ineligible hexes eligible. The reverse is possible too, though changes that affect an active deployer come with advance notice. See the Terms and Conditions for how eligibility changes are handled.

Claiming a Hex

Hexes are claimed on a first-come, first-served basis through the coverage map. Once you claim a hex and pay your deposit, it's yours: no one else can deploy there while your claim is active. For the full claim process, see Claim Your Hex.

Last updated