Drone regulation coverage in 2026 has been dominated by Part 108, the beyond-visual-line-of-sight proposal that is not yet final. That focus has obscured a rule that is fully in force.
Remote ID is enforced
Remote ID is fully enforced across major markets in 2026. This is not a proposal, not pending, and not subject to a comment period.
Aircraft operating without compliant Remote ID broadcast are operating unlawfully in jurisdictions that require it. There is no ambiguity to interpret.
The contrast with Part 108 is instructive. As of late July 2026, Part 108 remained a notice of proposed rulemaking, and no operator can claim Part 108 authority. Some coverage has described it as taking effect in July, which the rulemaking record does not support.
One rule is enforceable today and gets little attention. The other is not enforceable and gets most of it.
What Remote ID requires in practice
Remote ID broadcasts identification and location information from the aircraft during flight, allowing it to be identified by authorities and other airspace users.
Compliance comes in two forms: aircraft with the capability built in, or a broadcast module attached to an aircraft that lacks it. Older airframes are not automatically excluded — they need a module.
Why this matters more than the proposal
For a commercial operator, enforcement risk sits with rules in force. A client asking about regulatory compliance is asking about Remote ID, airspace authorisation and pilot certification — not about a proposed BVLOS framework.
The practical checklist for operating legally today has not changed because of the Part 108 discussion:
Remote ID compliance on every aircraft flown. Including older equipment and including aircraft used for training.
Airspace authorisation where required. Unaffected by the BVLOS proposal.
Waivers for anything beyond standard operations. The current regime requires a waiver for each BVLOS operation — slow and case-by-case, but it is the process that exists.
Where the two connect
The broader regulatory direction is toward performance-based approvals rather than case-by-case waivers, and Remote ID is a precondition for that shift. An airspace where every aircraft broadcasts identity is the foundation on which routine BVLOS operation becomes administratively possible.
Notably, the unresolved areas in the Part 108 comment record are electronic conspicuity and right-of-way — both directly downstream of identification and position broadcasting.
So Remote ID is not merely a rule that happens to be in force. It is the groundwork for the one everybody is discussing, which is a reason to treat compliance as infrastructure rather than paperwork.
