Achieve Remote ID compliance via broadcast module or Standard Remote ID Declaration of Compliance
domain: www.faa.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Determine compliance path: Standard Remote ID built into the aircraft, an add-on broadcast module, or operating only within an FAA-Recognized Identification Area (FRIA)
For manufacturers, implement the message set per ASTM F3411 (broadcast/network Remote ID specification) with F3586 as the FAA-accepted Means of Compliance overlay
Have the implementation tested against the accepted Means of Compliance, typically by an accredited test lab
File a Declaration of Compliance (DoC) with the FAA only after the Means of Compliance has been reviewed and accepted
For broadcast-module retrofits, configure the module with a valid serial number/session ID and confirm it transmits required fields (location, altitude, velocity, control station location, emergency status)
Known gotchas
A DoC cannot be filed until the underlying Means of Compliance is FAA-accepted — vendors sometimes market 'Remote ID ready' hardware before that acceptance is finalized
Broadcast modules only satisfy compliance if paired with a drone that is otherwise registered; the module itself does not replace aircraft registration
ASTM F3411 defines two distinct forms (broadcast vs. network Remote ID) and the FAA rule in the US currently relies on broadcast — don't assume network Remote ID alone satisfies 14 CFR Part 89
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?