Wesley Alexander • June 26, 2026 • 8 min read

Tactical Summary

The FAA's Notice of Proposed Rulemaking for Section 2209 of the FAA Extension, Safety, and Security Act of 2016 closes for public comment on July 6, 2026. The NPRM was published in the Federal Register on May 6, 2026, opening a 60-day window under docket FAA-2026-4558. If you operate near critical infrastructure for inspection, surveying, mapping, or public safety, this is the rule that will define where you can and cannot fly for the next several years, and the comment period is the only point where operators get to shape it before it hardens into 14 CFR Part 74.

This is not a temporary flight restriction or a one-off NOTAM. It is a permanent petition-based framework that lets eligible facility operators ask the FAA to draw a restricted box around their site. Nearly a decade after Congress directed the agency to build this process, the FAA finally has a 181-page proposal on the table, prompted by Executive Order 14305, Restoring American Airspace Sovereignty. You have until July 6 to tell the FAA whether it drew the box too big.

What the Rule Actually Creates

The NPRM establishes a new 14 CFR Part 74 and a mechanism called an Unmanned Aircraft Flight Restriction, or UAFR. A qualifying facility operator petitions the FAA, demonstrates a safety or security need, and if approved the FAA designates restricted airspace around that fixed site. The restriction comes in two tiers.

A Standard UAFR defines horizontal and vertical airspace limits around a qualifying fixed-site facility. A Special UAFR is the stricter tier, reserved for sensitive federal sites and certain facilities endorsed by federal security or intelligence agencies. The Special tier is modeled on the existing Special Security Instructions process under 14 CFR 99.7, carries five-year designations, and in some cases the airspace can be treated as national defense airspace. That last point matters because national defense airspace brings the possibility of criminal penalties under 49 U.S.C. 46307 for unauthorized operation, alongside civil penalties and certificate revocation.

One clarification the FAA makes explicitly, and that operators should internalize: a UAFR does not authorize geo-fencing, and it does not give the facility operator any new authority to detect, jam, or physically interfere with your aircraft. A UAFR is an airspace designation and a legal line, not a counter-UAS system. Detection and mitigation still require separate lawful authority, which most private facilities do not have. The practical effect is to help law enforcement distinguish a lawful transit from an unlawful incursion, not to hand private security teams a kill switch.

The Carve-Out That Keeps Commercial Operators Flying

Here is the provision every commercial pilot needs to read closely, because it is the difference between this rule being a manageable compliance task and a business-ending wall. Under proposed section 74.250, operators conducting work under Parts 91, 107, 108, 135, and 137 would retain access to Standard UAFR airspace, provided they meet three conditions:

  1. Broadcast Remote ID the entire time.
  2. Transit in the shortest practicable time, meaning you do not loiter inside the restricted box.
  3. Notify the facility in advance of the transit.

That carve-out is the reason infrastructure inspection, agricultural application under Part 137, survey and mapping work, and public-safety operations can continue near covered sites. But read the conditions as what they are: a compliance checklist with teeth. If your aircraft is not broadcasting Remote ID, you lose the carve-out. If you cannot document that you transited efficiently and notified the facility, you have no defense if a UAFR violation is alleged. The transit exception protects you only if you can prove you met its terms, and proving it is a documentation problem you should solve now, not after an enforcement letter arrives.

Note also that the Special UAFR tier does not carry the same automatic transit carve-out. For sensitive federal sites designated under the Special tier, the assumption should be no transit without explicit authorization.

Who Can Petition, and Why the Scope Question Is Everything

Eligibility is deliberately narrow on paper. To petition for a UAFR, a facility must be a fixed, permanent, non-mobile site that falls within the federal definition of critical infrastructure at 42 U.S.C. 5195c(e), covering the 16 sectors from National Security Memorandum 22. Those sectors are broad in aggregate: energy, chemical, oil refineries, transportation, nuclear, water and wastewater, communications, IT, manufacturing, food and agriculture, healthcare, emergency services, financial services, and large commercial venues among them.

Beyond sector membership, a petitioner must show it has at least one critical asset vulnerable to drone operations, has deployed physical security measures including restricted access and the ability to receive Remote ID messages, and can demonstrate that damage or disruption to the facility would have a regional or national-level debilitating impact. Applicants must also submit security and incident-response plans, describe the cost and rerouting impacts on airspace users, and provide information for the FAA's National Environmental Policy Act review.

That last requirement is a quiet pressure point operators should understand. Because disruption of these facilities can mean hazardous-substance releases, fires, explosions, or contamination events, the FAA folds environmental consequence analysis into the petition. It raises the evidentiary bar for applicants, which is good for transit-dependent operators, but it also signals that energy and chemical sites have the strongest case for approval. If you fly inspection routes around refineries, substations, pipelines, or water treatment, assume those operators will be first in line to petition.

The aggregate sector list is exactly why the FAA's specific request for comment matters. The agency is asking the industry directly whether restrictions could be drawn too broadly or implemented in ways that create undue friction for lawful operators. With 16 sectors eligible and a debilitating-impact standard that is open to interpretation, the risk is a patchwork of overlapping restricted boxes that turns routine inspection corridors into a permission maze. That is the comment the FAA needs to hear from working operators, and it is the comment only working operators can credibly make.

What To Do Before July 6

This is the actionable part. The comment window is the leverage point, and it closes in days.

First, if you operate commercially near any of the 16 sectors, file a comment at Regulations.gov under docket FAA-2026-4558. The most useful comments are specific and operational: name the routes or mission types that would be affected, quantify the rerouting cost or time penalty, and state plainly whether the section 74.250 transit conditions are workable for your concept of operations. Generic objections get aggregated and discounted. A concrete account of how a UAFR over a specific refinery would force a survey crew into a longer, less safe route is the kind of input that moves a final rule.

Second, audit your Remote ID compliance now, because the transit carve-out is conditioned on it. Confirm every aircraft in your fleet broadcasts standard Remote ID or carries a compliant module, and that you can demonstrate it. Our BVLOS compliance checklist and the Part 108 explainer both cover where Remote ID fits into a documented compliance posture.

Third, build a facility-notification and transit-logging procedure into your standard operating procedures before any UAFRs are designated. The carve-out requires advance notification and shortest-practicable-time transit. If you bake a notification template and a transit-time log into your SOPs now, you will be ready the day the first restriction near your operating area goes live. This is the same pre-staging discipline we wrote about for critical-infrastructure security programs: the operators who treat compliance as procedure rather than improvisation are the ones who keep flying.

The UAVHQ Read

Section 2209 has been coming for nine years, and the temptation is to treat the NPRM as just another regulatory headline. That is the wrong read. This rule creates permanent restricted airspace around an enormous category of fixed sites, and the only protection keeping commercial operators in the air near those sites is a conditional transit carve-out that you have to actively comply with and document. The comment window is the single moment where operators can argue for keeping that carve-out broad and the restrictions narrow.

File a specific comment before July 6. Get your Remote ID house in order. Write the facility-notification and transit-logging procedure into your SOPs. The operators who engage now will be the ones who shaped the airspace they have to fly in for the next five years, instead of inheriting it.

If you operate near critical infrastructure and need help drafting a substantive Section 2209 comment, mapping how proposed UAFRs would affect your routes, or building the Remote ID and transit-documentation posture the carve-out requires, that is exactly the kind of work UAVHQ does.

Sources

Section 2209 UAFR Critical Infrastructure 14 CFR Part 74 NPRM FAA-2026-4558 Remote ID Part 108 Part 107 Part 137 Commercial Drone Compliance Comment Deadline Executive Order 14305

Need Expert Drone Consulting?

UAVHQ offers professional consulting for BVLOS waivers, Part 107/108 compliance, critical-infrastructure program design, regulatory comment strategy, and airspace planning. 25+ years of aviation expertise at your service.

Explore Our Services →