9,000 New Drone Restrictions? What Every Drone Operator Needs to Know Right Now

If you fly drones near power lines, pipelines, chemical plants, stadiums, prisons, or amusement parks, this could affect you. If you operate any of those facilities, this could affect you even more.

The FAA just proposed a new rule that would let owners of qualifying critical infrastructure petition the FAA to restrict drone flights over their sites. Congress first told the FAA to create this process in 2016. Nearly ten years of delay followed. Eleven months after President Trump signed an executive order telling the FAA to move, the proposal finally landed. It's out for public comment right now, and comments close August 5.

This is Part 1 of a two-part guide. I want to walk you through what actually happened, what the rule would do in plain English, and what you should be doing right now to be ready. Part 2 will get into how this could change different corners of the industry, who benefits, who has a problem, and where I think this is all heading.

The one-paragraph version

Here's the whole thing in one paragraph so you have the shape of it before I dig in. The FAA published a proposed rule on May 6, 2026, that would create a new application process. Operators of qualifying critical infrastructure facilities could apply to have the airspace over their site designated as restricted. If the FAA agrees (usually after a public comment window of at least 30 days on the proposed restriction), certain qualified drone operations could still transit the restricted airspace under a specific process: broadcast Remote ID, cross in the shortest practicable time, and provide notice through the FAA-prescribed process. Recreational operators wouldn't get the transit option. Operations by or for government agencies or law enforcement would get a specific notice accommodation. The restricted airspace would be narrow: it can't go past the facility's property line, and it's generally capped at 400 feet up. The FAA modeled a scenario with roughly 9,159 applications over five years. That's a scenario, not a forecast. The comment window is open until August 5. Nobody knows exactly when the final rule lands, but there's a September 2027 statutory deadline in play. That's the whole shape. Now let me walk you through what matters.

How we got here (and why it matters that we waited)

Congress first told the FAA to create this process in 2016. Ten years ago. The original deadline was January 2017. The FAA missed it. Congress extended the deadline in 2018 and added railroad facilities to the scope. The FAA missed that one too. Congress extended it again in 2024, added state prisons to the scope, and set a new deadline. The FAA missed the 2024 deadline for publishing the proposal as well. The final rule deadline is still ahead, in September 2027. Between the original 2017 deadline and the 2026 proposal, more than a dozen states got tired of waiting and wrote their own laws. Arizona, Arkansas, Louisiana, Texas, Connecticut, and others. Every one of them handled critical infrastructure drone protection a little differently. That's the mess we're walking into.

A June 2025 executive order from President Trump called Restoring American Airspace Sovereignty directed the FAA to act promptly, adding pressure to an already overdue rulemaking. Eleven months later, the proposed rule landed in the Federal Register on May 6, 2026. Whatever you think about the policy choices, that executive order added the pressure that finally moved this along.

As someone who watches this space closely, what strikes me isn't the political difficulty. Airspace policy is always politically hard. What strikes me is that the delay created its own problem. The proposed federal rule wouldn't clean up the state law patchwork. It just adds another layer on top of it. If you fly across multiple states, that matters. I'll get into what that looks like in Part 2.

What the rule would actually do

The rule creates an application process. It doesn't automatically restrict anything. If you operate or have a qualifying legal interest in an eligible fixed-site facility, you could apply. You'd have to make a case that the restriction is needed for safety, security, or protecting people on the ground. The FAA reviews the application, and if it's conditionally approved, the proposed restriction would ordinarily be published for at least 30 days of public comment before the FAA makes a final decision. For the normal application process, no restriction would take effect until an eligible facility operator applies, the public has an opportunity to comment, and the FAA approves it.

There are two flavors of restriction. The standard version is what most facility operators would use. It restricts drones from flying in the designated airspace unless they meet a specific transit process I'll get to in a second. The other flavor, called a special restriction, is reserved for federal security and intelligence agencies, military departments, and qualifying nonfederal facilities that are sponsored by one of those agencies. A special restriction is much more restrictive: outside operators would generally need approval from both the designated using agency and the FAA before flying through. Either type could remain in effect for up to five years and then would have to be renewed.

Now, the restrictions themselves are narrower than a lot of the industry chatter has suggested. The restricted airspace can't extend beyond the facility's property line. And it's generally capped at 400 feet above the ground, with a small exception for tall structures. So this isn't a broad buffer around the facility. It's a defined column of airspace, closely tied to the facility itself.

Here's the part that matters most for anyone actually flying. For a standard restriction (not a special one), there's a transit process. If you're operating under one of the permitted categories (which cover a wide range of certificated operations including small-drone commercial work, delivery, agricultural spraying, air taxi, and qualifying government operations), you can fly through the restricted airspace if you do three things. You broadcast Remote ID, which is already required for many covered operations. You cross in the shortest practicable time. And you provide notice to the site manager through the FAA-prescribed process, with a specific set of information including contact details, your certificate or permit number, your Remote ID serial numbers, aircraft registration, the restricted-airspace site you're transiting, your area of operation, when you'll be flying, how many drones, and what you're doing. The FAA is proposing to build a web-based notification module for this and is considering automated or whitelist alternatives. So while the requirement is clear, the exact mechanics may evolve. Under the current proposal, operators would need this information ready, although the final process could allow one-time or automated submission.

Recreational flyers don't get the transit option. If a facility near your home gets restricted, you'd need separate authorization from the FAA to fly there. In practice, that's going to be much harder than just choosing a different route or flight area. If you fly recreationally near a stadium, an amusement park, or a prison that might get a restriction, plan accordingly.

Public safety and government operations get a specific accommodation. Operations conducted by or for a government agency or law enforcement, when conducted within the agency's or law-enforcement body's legal authority, can provide verbal notice as soon as reasonably possible, with written notice following within seven calendar days. This is a meaningful notification accommodation because it recognizes that these operators can't always send detailed advance notifications during an active call.

One thing worth clearing up because it comes up a lot: this rule doesn't give facility owners the right to shoot down or jam drones. The proposal does not grant or expand counter-drone authority. It does require that applicants have basic passive Remote ID sensing, so the facility can receive Remote ID broadcasts from compliant drones. But it does not authorize active mitigation of any kind. Any active mitigation would still require independent authority under existing law, which most facility owners do not have and could not obtain through this rule.

How big could this get?

The scale numbers are where things get interesting. National Security Memorandum 22 identifies sixteen critical infrastructure sectors. Federal sector agencies inside those sectors identified approximately 125,000 facilities as potentially high priority, though the criteria aren't fully worked out for every sector. In the FAA's economic-modeling analysis, the agency modeled a scenario with roughly 9,159 applications over the first five years. That's a modeling scenario, not an FAA forecast or prediction.

If the modeled scenario plays out anywhere close to that number, this becomes one of the biggest changes to where drones can fly in a decade. That's worth paying attention to.

What you should be doing right now

Whether you operate a facility that could apply, fly commercially near facilities that might get restricted, or run a public safety drone program, here's the near-term action list.

• Submit a comment before August 5. The FAA is actively looking for practical input from real operators. What the FAA has said is that the most useful comments identify a specific piece of the proposal, explain what you'd change and why, and back it up with actual data or examples from your work. If you have skin in this game, your comment matters. The docket number for finding the rule and filing your comment is FAA-2026-4558.
• If you operate or have a qualifying legal interest in a facility that might be eligible, start gathering the information the proposal is likely to require. Incident logs, security assessments, and any documentation of drone incursions you've had. The application process itself is still evolving (the FAA is considering staggered application windows), but many of those underlying records are likely to remain useful even if the final application requirements change. Get them organized now.
• Read the proposed rule. I know that sounds intimidating. The full proposal is available on FederalRegister.gov and Regulations.gov. You don't need to read every word. Focus on the transit process and the notification requirements. Those are the two sections that will most affect how you fly.
• Get your Remote ID compliance sorted. Remote ID broadcasting would be required for the transit process, so if your drones aren't broadcasting correctly, or if your registration doesn't match your aircraft, fix that now. Verify the broadcast on every aircraft you fly. Document what you find.
• Start mapping which of your routes might pass through restricted airspace and start collecting the data fields you'd need to provide (contact info, certificate numbers, Remote ID serial numbers, aircraft registration). Don't build a fixed manual notification system yet because the FAA is proposing a web-based module and is considering automated or whitelist alternatives. What you can do now is get the underlying data organized so you're ready to plug it into whatever notification process a final rule may require.

Coming in Part 2

Part 2 goes deep on the three sectors that would feel this rule the hardest: infrastructure inspection, package delivery, and public safety drone programs. I'll lay out who I think comes out ahead and who has a real problem. I'll walk through the mess of state laws that this rule doesn't clean up, and what that means if you operate across multiple states. And I'll close with where I think this whole thing is heading, including a question about air rights that this rule has quietly put in front of the industry.

Get ready.