The FAA published a proposed rule on May 6, 2026, that would establish a formal process for certain operators and proprietors of fixed-site facilities to request unmanned-aircraft flight restrictions. The proposal implements Section 2209 of the FAA Extension, Safety, and Security Act of 2016 and uses the term unmanned aircraft flight restriction, or UAFR.
The most important word is proposed.
The extended public-comment period closed on August 5, 2026. As of August 8, the FAA continued to describe the measure as a proposed rule, and no final rule was located in official FAA or Federal Register sources. The proposal itself does not create a new restriction over every power plant, railroad facility, refinery, water-treatment plant, chemical facility, or industrial site. Commercial pilots must continue complying with existing airspace restrictions while watching the docket for later action.
That distinction matters when a client asks a simple question such as, “We own the facility, so can you fly here?” Ownership or site permission answers only one part of the job. The pilot still has to determine whether the operation complies with federal airspace rules, active restrictions, authorizations, and operating requirements.
What the FAA proposed in May 2026
The proposal would create a process through which eligible fixed-site operators or proprietors could ask the FAA to establish a UAFR. The FAA says eligible categories would include specified critical-infrastructure sectors and other facility classes identified in the proposal. The applicant would have to show that a restriction is justified by aviation safety, protection of people or property on the ground, national security, or homeland security.
The proposed rule describes standard and special UAFRs. Both would be legal airspace designations with defined horizontal and vertical limits. The proposal generally ties the lateral boundary to the applicant’s property and caps a restriction at 400 feet above ground level, with limited treatment for taller structures. It also describes continuous and part-time activation periods and narrow categories of operations that could be allowed inside a restriction.
Those details remain proposals until the FAA completes rulemaking. Operators should not build pricing, contracts, or legal advice around a draft regulatory provision as though it were already effective.
Restrictions that already exist today
Commercial drone pilots already encounter several different forms of airspace control. They should not be treated as interchangeable.
Security-sensitive fixed-site restrictions
The FAA currently prohibits drone operations over designated national-security-sensitive facilities. The FAA’s critical-infrastructure guidance identifies examples such as designated military facilities, national landmarks, and certain facilities including nuclear power plants. These restrictions can apply from the surface to 400 feet above ground level and may apply to all UAS operations unless an authorization or exception is available.
The FAA publishes supporting restriction data through its UAS data resources. A pilot should examine the actual restriction information for the precise location rather than relying on a client, a fence line, a manufacturer geofence, or a general map screenshot.
Temporary Flight Restrictions and NOTAMs
A TFR restricts aircraft operations in a defined area for a limited period. TFRs may be issued for disasters, hazards, major events, security situations, VIP movement, and other specific circumstances. The restriction’s text establishes its location, altitude, effective period, permitted operations, and approval process.
The FAA instructs drone pilots to check NOTAMs before flight. A TFR can appear after a job was quoted or even after a previous site visit, so a prior airspace check is not enough.
Controlled-airspace authorization
LAANC or a manual FAA authorization addresses access to controlled airspace near participating airports. It does not automatically clear every other restriction. FAA guidance specifically says pilots must still check NOTAMs, TFRs, weather, and other applicable airspace restrictions.
A green LAANC approval is therefore not a complete legal review. It is one component of the preflight record.
Property permission and operating-site access
A landowner or client can control physical access to the launch site and can authorize work on its property. That permission does not transfer control of the national airspace to the owner. Conversely, a flight that is not blocked by controlled airspace may still create trespass, access, privacy, contractual, safety, or site-security issues on the ground.
Commercial operators should document both sides: airspace compliance and site authorization.
A practical preflight workflow for critical-infrastructure jobs
A strong process is more useful than a generic instruction to “check the airspace.” The following workflow creates a record that can be reviewed later by the pilot, client, insurer, or project manager.
1. Pin the actual work area
Obtain the exact address, coordinates, property boundaries, proposed launch point, inspection area, maximum altitude, and expected flight path. Do not quote solely from a company name or mailing address. Large industrial and utility properties may span multiple airspace grids or sit near airports, heliports, restricted facilities, rail corridors, or sensitive government property.
2. Define the mission before checking permissions
Document what the client wants: exterior marketing, roof imagery, progress photos, thermal data, mapping, tower inspection, stockpile measurement, emergency response, or another service. Record whether the flight involves operations over people, vehicles, moving equipment, nighttime operations, restricted access areas, or a need to fly beyond standard Part 107 limits.
A legal flight path depends on the operation, not just the street address.
3. Check controlled airspace and FAA data
Review the FAA’s current airspace information through an approved service. Determine whether controlled-airspace authorization is required and whether LAANC can process the request. Check FAA UAS data for special-security instructions and facility-specific information.
Save the date, time, location, proposed altitude, data source, authorization number, and any operating limitations. A screenshot alone can be ambiguous unless it includes enough context to identify the site and time.
4. Check current NOTAMs and TFRs
Review active NOTAMs and the FAA TFR system close to departure and again before launch. Read the actual restriction text. Do not assume the map symbol tells you who may operate, at what altitude, or under what approval.
When a TFR applies, follow the authorization process stated in the notice. Do not treat client urgency as an exception.
5. Confirm facility restrictions and site-security requirements
Ask the client whether the site has aviation, security, photography, radio-frequency, hazardous-area, escort, personal-protective-equipment, or shutdown requirements. Determine whether the contact requesting the job has authority to approve access and imagery.
This step does not replace the FAA review. It addresses the facility’s operational controls and prevents a technically legal flight from violating the client’s own safety or security program.
6. Record a go, modify, or decline decision
The pilot-in-command should document one of three outcomes:
- Go: the operation can be conducted within all current rules and site requirements.
- Modify: change the altitude, launch point, camera angle, timing, crew, aircraft, or deliverable so the job can be performed compliantly.
- Decline or postpone: the restriction, authorization, weather, site condition, or mission requirement cannot be resolved safely and legally.
A professional decision to postpone is part of the service. It should not be treated as a failure to accommodate the client.
7. Recheck before launch
Airspace status, TFRs, NOTAMs, weather, people, vehicles, construction activity, cranes, and emergency operations can change after planning. Conduct and document a final check at the site.
Contract language should reflect regulatory change
The proposed UAFR process is a reminder that airspace access can change. Commercial proposals and service agreements should avoid guaranteeing that a particular flight will occur at a fixed time regardless of restrictions.
A practical agreement can state that performance is subject to FAA rules, authorizations, temporary restrictions, weather, site safety, and the remote pilot in command’s final safety decision. It can also explain what happens when a job must be rescheduled, redesigned, or canceled because legal access is unavailable.
This is not a reason to add vague regulatory surcharges. It is a reason to define the scope of the operator’s planning work and the conditions outside the operator’s control.
What to watch next
The extended comment period closed on August 5, 2026. As of August 8, no final rule was located in official FAA or Federal Register sources. The agency may change the proposal, issue additional notices, publish a final rule, or take no immediate final action.
Before publishing or relying on this article after that date, confirm the current status of Docket FAA-2026-4558. If a final rule is issued, update the article’s eligibility descriptions, boundaries, exceptions, application process, effective date, and operator compliance steps.
Frequently Asked Questions
Does the 2026 proposal ban drones over all critical infrastructure now?
No. The May 2026 document is a proposed rule that would create an application and designation process for eligible fixed-site facilities. Existing security-sensitive restrictions, TFRs, NOTAMs, controlled-airspace rules, and other operating requirements remain independently applicable.
Can a facility owner authorize a drone to fly through restricted airspace?
Site permission alone does not override an FAA airspace restriction. The pilot must comply with the restriction’s terms and obtain any required FAA or controlling-agency approval.
Does LAANC approval clear a critical-infrastructure restriction or TFR?
No. LAANC provides controlled-airspace authorization. FAA guidance states that pilots must still check and comply with NOTAMs, TFRs, weather, and other restrictions.
How high could a proposed UAFR extend?
The NPRM generally proposes a ceiling of 400 feet above ground level, with provisions addressing structures taller than 300 feet. The final requirements may change during rulemaking, so operators should verify the final text if and when it is issued.
What should a commercial pilot save in the job file?
Save the coordinates and mission scope, airspace and restriction checks, authorization numbers and conditions, NOTAM/TFR review, client/site permission, safety assessment, final go-or-no-go decision, and any later changes.
Source Notes
Federal Aviation Administration — Restricting Drones Near Critical Infrastructure Sites, May 6, 2026
https://www.faa.gov/newsroom/restricting-drones-near-critical-infrastructure-sites
GovInfo / Federal Register — Designation—Restrict the Operation of Unmanned Aircraft in Close Proximity to a Fixed Site Facility; Proposed Rule, 91 FR 24650, Docket FAA-2026-4558
https://www.govinfo.gov/app/details/FR-2026-05-06/2026-08943
Federal Register public-inspection PDF — Extension of Comment Period to August 5, 2026
https://public-inspection.federalregister.gov/2026-13126.pdf
Federal Aviation Administration — Critical Infrastructure and Public Venues
https://www.faa.gov/uas/critical_infrastructure
Federal Aviation Administration — Temporary Flight Restrictions
https://www.faa.gov/uas/getting_started/temporary_flight_restrictions
Federal Aviation Administration — UAS Data Exchange / LAANC
https://www.faa.gov/uas/getting_started/laanc
Federal Aviation Administration — UAS Facility Maps FAQ
https://www.faa.gov/uas/commercial_operators/uas_facility_maps/faq