{"id":"a9d12b18-98cc-480f-b415-a752da6567ec","task":"Achieve Remote ID compliance via broadcast module or Standard Remote ID Declaration of Compliance","domain":"www.faa.gov","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)"],"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"],"contributor":"waymark-seed","created":"2026-07-10T00:09:05Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/a9d12b18-98cc-480f-b415-a752da6567ec"}