AeroDefense Blog

FAA Drone Restrictions for Critical Infrastructure: Navigating the May 2026 UAFR Proposal

Written by Lexi Rinaudo AeroDefense Chief Marketing Officer | May 20, 2026 1:07:22 PM

Summary: Federal Aviation Administration (FAA) drone restrictions for critical infrastructure could include strict federal mandates under a newly proposed May 2026 airspace framework. This update introduces the "Unmanned Aircraft Flight Restriction" (UAFR), providing eligible fixed sites with a legally enforceable pathway to restrict unauthorized low-altitude flights directly over their property lines. To qualify, facility operators must prove they meet the FAA's requirements and deploy Remote ID receiving capabilities to bridge the gap between regulatory policy and real-time enforcement.

 

If your critical infrastructure facility already benefits from state-level drone restrictions, you know how crucial low-altitude security is. To date, states have been the trailblazers in protecting critical infrastructure, passing local laws to deter unauthorized flights over sensitive areas.

 

The FAA’s proposed rule builds on this exact foundation. By introducing the UAFR, the federal government is establishing a uniform, nationwide standard. This means facilities no longer have to rely solely on local ordinances; they can now secure a federally recognized, 400-foot no-fly zone that integrates seamlessly with existing state and local security frameworks.

 

 

UAFR: What is it?

The FAA’s landmark Notice of Proposed Rulemaking (NPRM) introduces a brand-new airspace designation: the Unmanned Aircraft Flight Restriction (UAFR). Rather than relying on passive or informal guidelines, owners and operators now have a formal mechanism to restrict unauthorized drone flights directly over their boundaries.

 

A UAFR establishes strict, invisible horizontal and vertical boundaries to restrict drone flights directly over a facility. It is important to note that a UAFR is a legal designation, not a physical barrier or an electronic shield. It acts as a "virtual no-trespassing sign" in official airspace maps, giving law enforcement the federal teeth to penalize violators.

 

The proposal breaks these restrictions into two distinct tiers:

 

Standard UAFRs: Available to eligible commercial and public critical infrastructure. They prohibit unauthorized flights but allow rapid transit by vetted, trusted commercial operators (such as Part 107 or Part 135 pilots) who broadcast Remote ID and notify the facility manager in advance.

 

Special UAFRs: Stricter, highly secure designations reserved for sensitive federal sites or assets facing credible threats, requiring an endorsement from a federal defense, energy, or intelligence agency (such as the DOD or DOE). When a Special UAFR is issued for critical national or homeland security purposes, the FAA may designate the area as "national defense airspace" (under 49 U.S.C. § 40103(b)(3)), meaning willful violations can carry severe federal criminal penalties and prison time.

 

The Boundaries: For both types, the physical boundaries are tightly controlled. The horizontal restriction is confined strictly within the facility’s legal property lines, and the vertical ceiling is generally capped at 400 feet above ground level (AGL).

 

 

How Long Would the UAFR Last and Can it Renew?

Full-time UAFRs remain active 24/7, year-round. In contrast, part-time UAFRs operate 24 hours a day but are strictly limited to a maximum of 290 consecutive days per year.

 

Approved UAFRs are granted for a five-year renewable term before requiring review.

 

 

Who Qualifies?

  • Permanent Sites Only: The FAA interprets "fixed-site facilities" strictly as permanent, non-mobile locations. Temporary setups or mobile operations do not qualify.

  • Who Can Petition: Only the property owners, facility operators, or proprietors (either individually or collectively) have the legal standing to apply for a UAFR.

 

Eligible Sectors:

Chemical

• Commercial

• Communications

• Critical manufacturing

• Dams

• Defense industrial base

• Emergency services

• Energy

• Financial services

• Food and agriculture

• Government services and facilities

• Healthcare and public health

• Information technology

• Nuclear reactors, materials, and waste

• Transportation systems

• Water and wastewater



FAA Drone Restrictions for Critical Infrastructure: The Four Security Requirements

The most critical takeaway for facility operators is that the FAA does not grant airspace protection unconditionally. Under proposed § 74.56, a site must prove it already maintains a robust ground-based security posture. A UAFR is meant to complement existing security, not replace it.

 

To apply, a facility must demonstrate it has four core measures in place:

 

  1. Restricted Access: Physical boundaries or access controls on the ground.
  2. Designated Security Personnel: Active staff responsible for daily security operations.
  3. Security Monitoring: Perimeter surveillance via cameras, guard patrols, or equivalent systems.
  4. Remote ID Receiving Capability: The most operationally significant requirement. Facilities must have the baseline infrastructure - either deployed directly or managed via a third-party contract - to receive broadcast Remote ID messages from nearby drones in compliance with 14 CFR part 89.

The Operational Takeaway: Remote ID sensing is no longer a futuristic upgrade; the FAA has officially codified it as a minimum prerequisite for federal airspace protection.

 

Note: While these four protective security layers are the most critical for operational security teams, the FAA requires several other administrative, property boundary, and environmental disclosures to complete an application. For a deep dive into those requirements, see Subpart B of Part 74 (Minimum Requirements for a UAFR) within the NPRM.  

 

How to Apply for A UAFR

The application process is thorough and requires clear justification. Here is what the FAA’s proposed framework looks like from start to finish:

 

1. Building Your Case: To apply via the FAA portal, you must prove a legitimate safety or security need. Your application will need to detail:

 

  • Existing drone activity over your facility.
  • Your asset vulnerabilities and the potential consequences of a drone exploit (intentional or accidental).
  • How a UAFR integrates into your current security plans, including what "self-help" steps (like ground-level security) you’ve already taken.

2. The FAA Evaluation & Public Review: The FAA won't just look at security; they will also assess the UAFR’s impact on the environment and the surrounding community. If it passes initial review, the FAA will publish the proposal in the Federal Register for a 30-day public comment period.

 

3. Final Determination: After evaluating public feedback, the FAA will make its final decision:

 

  • If Approved: The UAFR is officially published and goes live on the FAA website.
  • If Denied: Don't panic. The FAA will give you one immediate opportunity to correct any deficiencies and resubmit - and you can always reapply again down the road.

 

 

Does the UAFR Allow Drone Mitigation?

While the UAFR framework marks a massive leap forward for legal clarity, it is vital to understand what the rule does not do.

 

A UAFR does not grant private facilities the legal authority to intercept, jam, or physically down a drone. Unless a federal agency holds explicit, independent statutory authority to utilize counter-UAS mitigation technology, federal criminal laws regarding airspace interference still apply.

 

 

Future-Proofing Your Airspace Security

With the regulatory framework solidifying, infrastructure operators should take immediate steps to align with the upcoming standards:

 

  • Audit Sector Thresholds: Verify if your facility meets the quantitative metrics required for eligibility.
  • Assess the Remote ID Gap: Evaluate your current airspace visibility. Because the FAA permits contracted services to fulfill the Remote ID mandate, partnering with an airspace awareness provider is the fastest route to compliance.
  • Participate in the Rulemaking: Submit operational feedback, sector-specific challenges, or boundary suggestions to regulations.gov (Docket FAA–2026–4558) before the comment window closes on July 6, 2026.

The FAA’s May 2026 UAFR proposal marks a pivotal shift toward a unified, federal standard for low-altitude security. By establishing enforceable 400-foot no-fly zones, the framework provides critical infrastructure operators with the legal teeth needed to deter unauthorized drone flights.

 

However, federal protection is a two-way street. The FAA expects facilities to earn this designation by hardening ground defenses and implementing active Remote ID tracking.

 

With the public comment window closing on July 6, 2026, the time to act is now.

 

Infrastructure leaders must evaluate their eligibility, bridge their airspace monitoring gaps, and prepare for a new era of proactive perimeter defense.



People Also Ask (PAA)

What are the new FAA drone restrictions for critical infrastructure?
The FAA's May 2026 proposed rule (published under Document Citation 91 FR 24650) introduces Unmanned Aircraft Flight Restrictions (UAFRs). These establish legally enforceable low-altitude restricted airspace zones up to 400 feet over fixed-site facilities across 16 critical infrastructure sectors.

 

How does a facility apply for an FAA drone restriction?
Eligible facility operators or proprietors must submit an application through an upcoming web-based UAFR Module. Applicants must provide precise property boundaries, a data-backed demonstration of need, and proof that four ground-based protective security measures are already active.

 

When do these new FAA drone restrictions for critical infrastructure go into effect?
The rule is currently in its public request-for-comment phase and is not yet a finalized law. Stakeholders, facility managers, and drone pilots have until July 6, 2026, to review the proposal and submit formal feedback directly to the federal government via the Federal Register Rulemaking Docket (Doc. 2026-08943).