The comment window has closed on what may become the most consequential piece of domestic counter-drone policy since Remote ID: a Federal Aviation Administration proposed rule that, for the first time, gives operators of critical infrastructure a formal, standardized channel to ask the government to restrict drone flights over their own facilities.

The Notice of Proposed Rulemaking, published in the Federal Register on May 6, 2026 as Federal Register document 2026-08943 (91 FR 24650), implements Section 2209 of the FAA Extension, Safety, and Security Act of 2016 as amended, and is explicitly tied to Executive Order 14305, "Restoring American Airspace Sovereignty." Comments were due, per the Federal Register notice itself, "on or before July 6, 2026," though trade coverage at the time of publication cited a July 5 close — a discrepancy that appears to trace to weekend/holiday date handling rather than any substantive change to the docket. Either way, the public input phase is now finished, and the FAA's attention shifts to reviewing what is likely to be a substantial comment record before finalizing the rule.

What the Rule Actually Does

The NPRM does not hand critical-infrastructure operators a kill switch, and it does not create any new counter-UAS interdiction authority. What it creates is a paperwork pathway — a formal petition process by which the owner or proprietor of a permanent, fixed-site critical-infrastructure facility can ask the FAA to designate a zone around that site as an Unmanned Aircraft Flight Restriction, or UAFR.

There are two tiers:

  • Standard UAFR — prohibits most drone operations within the designated area unless the operator meets FAA-defined safety and security requirements. This is the baseline restriction and, per the rule's framing, the more readily available option.
  • Special UAFR — a stricter designation that requires advance, joint approval from the FAA and a sponsoring federal agency. Special UAFRs can be authorized for up to five years, making them a durable, long-term airspace restriction rather than the ad hoc, short-fuse Temporary Flight Restrictions (TFRs) that have historically been the government's default tool for protecting a site from above.

Crucially, enforcement of either tier would not rely on new physical or electronic countermeasures. Instead, the rule leans on existing FAA and law-enforcement authority, with Remote ID broadcast data serving as the mechanism to identify — and subsequently prosecute or cite — operators who violate a designated UAFR. In effect, the rule assumes that most drones flying in U.S. airspace are already broadcasting identifying information under the Remote ID mandate, and that a UAFR violation becomes an enforcement and attribution problem rather than a detection problem.

Sixteen Sectors, One Application Process

The proposed rule covers 16 categories of critical infrastructure: chemical facilities, commercial facilities, communications, critical manufacturing, dams, the defense industrial base, emergency services, energy, financial services, food and agriculture, government facilities, healthcare and public health, information technology, nuclear reactors/materials/waste, transportation systems, and water and wastewater systems.

According to analysis from law firm Beveridge & Diamond, which reviewed the NPRM, the rule applies specifically to operators or proprietors of permanent, non-mobile facilities as statutorily defined — meaning a fixed power substation or water treatment plant would qualify, but a mobile or temporary asset would not automatically be covered under this pathway. The firm's analysis also lays out the evaluation criteria the FAA says it will apply to petitions: aviation safety, protection of property, and national or homeland security considerations. Those three criteria appear designed to give the agency latitude to reject petitions that are more about nuisance or privacy concerns than genuine security or safety risk — though the proposed rule leaves considerable discretion in how those criteria get applied in practice.

The Political Framing

Transportation Secretary Sean P. Duffy characterized the rule as a direct response to mounting concern over drone activity near sensitive sites, saying the regulation "does just that" with respect to protecting critical facilities — language that ties the NPRM to a broader political narrative around foreign-linked drone incursions and the administration's push, via Executive Order 14305, to reassert what it calls American airspace sovereignty. That framing situates the rule alongside a string of unexplained drone sightings over military installations and infrastructure sites in recent years that fueled congressional pressure for the FAA and Department of Defense to close gaps in low-altitude airspace authority.

Notably, the rule's authors chose not to pair the new petition process with any expansion of counter-UAS authority for private operators. That is a meaningful restraint: infrastructure operators lobbying for years have often asked not just for restricted airspace on paper, but for the legal ability to detect, track, and in some cases disable unauthorized drones over their own property. This rule gives them the former without the latter, keeping detection and enforcement squarely in the hands of the FAA and law enforcement.

What Happens Next

With the comment period closed, the FAA will now review submitted comments — a process that, for rules of this scope, typically takes months rather than weeks before a final rule is published. Given the rule's grounding in a statute already ten years old (Section 2209 dates to 2016) and an executive order issued this year, there is political momentum behind moving the rulemaking forward relatively quickly, but no published timeline for a final rule has been confirmed in the sources reviewed for this article.

In the meantime, critical-infrastructure operators — and the drone operators, hobbyists, and commercial UAS companies that fly near them — are left in a holding pattern. No UAFRs, Standard or Special, are yet in effect under this specific framework; the rule remains proposed, not final. But the shape of the eventual regime is now clear: a two-tier system of long-duration, facility-requested no-fly zones, enforced not through jamming or kinetic countermeasures but through Remote ID-enabled identification and conventional enforcement action.

Why It Matters

This rule is the clearest signal yet that Washington's preferred model for protecting critical infrastructure from drone incursions is not a centralized, government-run detect-and-defeat network, but a formalized, facility-by-facility permission system. Rather than waiting on the FAA or Department of Defense to issue an emergency TFR every time a power plant or water facility reports drone activity, infrastructure owners will be able to petition for a standing restriction lasting up to five years under the Special UAFR tier.

For the drone industry, the practical stakes are significant. Sixteen sectors of infrastructure is an expansive footprint — and if even a fraction of eligible facility operators pursue Special UAFRs, commercial and recreational operators could see a meaningful patchwork of new no-fly zones stacking on top of existing TFRs, airport-proximity restrictions, and national-security no-fly areas already tracked through the FAA's LAANC and B4UFLY systems. Because enforcement rests on Remote ID rather than new detection infrastructure, the rule also puts renewed weight on Remote ID compliance: an operator who isn't broadcasting correctly, or whose broadcast module malfunctions, becomes both a nuisance and, potentially, a target for enforcement in a UAFR zone without any new detection hardware at all.

Just as important is what the rule does not do. By declining to grant new counter-UAS interdiction powers to private operators, the FAA is keeping a bright line around who is legally allowed to detect, track, and disable unauthorized aircraft — a line that infrastructure lobbies have pushed to erase for years. Whether that restraint survives contact with a final rule, and whether Congress moves separately to expand counter-UAS authority for the private sector, will shape how aggressively facility operators can actually defend their airspace once UAFRs start appearing on aeronautical charts.

Sources