The Section 2209 Deep Dive: Sector-by-Sector Impact, Winners and Losers, and the Air-Rights Question

In Part 1 of this guide, I walked through where the Section 2209 rulemaking stands, what the proposed rule would do, and the near-term action steps every affected operator and facility owner should take. The comment window closed August 5. If you haven't read Part 1, start there. This part picks up where Part 1 left off. I want to get specific about what would change for each of the three sectors most directly affected, who would come out ahead and who would have a real problem, why the state law patchwork isn't going away if the federal rule finalizes, and where this rule could go over the next twelve to twenty-four months. This is a founder's read, not a legal analysis.

How Section 2209 would change the commercial drone industry

Three sectors would feel the proposed rule most directly, and one of them would receive a specific notification accommodation.

Infrastructure inspection

This sector would feel Section 2209 more than any other because the covered facilities are exactly the assets these operators inspect. Pipeline inspection over energy transmission corridors, electric utility inspection over transmission lines and substations, rail corridor inspection, and chemical facility inspection all involve routine drone work over what could become UAFR-designated airspace. If your work involves flying drones over the assets that would qualify for UAFR designation, your operational planning changes. Facility owners you already work with may hold UAFRs, in which case you would operate under the FAA access and notification requirements, together with any contractual coordination for work at the facility. Facility owners you don't work with may hold UAFRs you would have to transit through, in which case you would operate under the section 74.250 requirements. Either way, the paperwork burden goes up, and the relationship with facility owners matters more than it did before.

Package delivery

Delivery operators running hub-and-spoke networks in metropolitan areas need to think about this carefully. Urban delivery routes pass over a lot of what could become covered facilities: chemical facilities, water treatment plants, electrical substations, sometimes state prisons and amusement parks. The transit provision as proposed would let Part 108 delivery operators fly through Standard UAFRs if they meet the Remote ID, shortest-practicable-time, and notification requirements. If that transit provision survives the final rule substantially as drafted, delivery operations could remain economically viable in most markets. If the FAA modifies it in response to comments or during finalization, delivery route economics could change substantially in cities with dense critical infrastructure.

Public safety and Drone as First Responder

Law enforcement and fire agencies operating DFR programs frequently respond to incidents at or near critical infrastructure facilities. The proposed rule includes a specific notification accommodation for qualifying operations conducted by or for government or law enforcement: verbal notice may be given as soon as reasonably possible, with written notice within seven calendar days. That's the specific carve-out I mentioned above, and it's a meaningful one because it recognizes that public safety agencies can't always send detailed advance notifications during an active call. How well individual agencies absorb the notification workflow will depend on their existing dispatch and coordination infrastructure. Agencies still standing up programs may find the coordination burden a barrier to launch.

Who would win and who would have a problem

What follows is analysis, not a settled outcome. If the proposed rule finalizes without major changes to the transit provision, here's who I think would come out ahead and who I think would have a real problem.

The clearest potential winners are critical infrastructure owners with legal and security resources to build strong applications. Operators or proprietors of facilities that meet the applicable sector threshold and demonstrate the required need may apply. That includes energy, oil and gas, chemical, amusement park, state prison, and railroad facilities that fit the statutory categories. The application process would require demonstrating necessity for aviation safety, protection of people and property on the ground, national security, or homeland security. That's a high bar but not an impossible one for facility owners with staff who can build the case. The long wait produced a rule that, for these owners, is worth having if they can navigate the application process well.

Commercial drone operators with Part 108 authority, if Part 108 finalizes substantially as proposed, would benefit under Section 2209 as well. But the advantage isn't preferential UAFR access. Under proposed section 74.250, Parts 91, 107, 108, 135, and 137 are all in the permitted transit categories, subject to their applicable credentials and common access conditions. What Part 108 could offer is scalable BVLOS authority that would make routine long-distance operations viable at all, which multiplies the value of being able to transit UAFRs on the same terms as Part 107 operators. That combined outcome depends on both rules landing in their current shapes, and neither is guaranteed.

The operators who could have a real problem, in my view, are small and midsize commercial shops whose route dependencies pass through what could become covered facilities. If you're a two-person real estate photography business in a city with a state prison, a chemical facility, and two electrical substations along your typical route, and each of those receives a Standard UAFR, your daily operations would require the transit provision to work. That means Remote ID compliance, notification workflows including all the section 74.255 required information, and disciplined operational logs that would let you show shortest-practicable-time transit if ever asked. Documentation of that kind isn't expressly required by the proposed rule, but treating it as recommended compliance practice would put you in a much better position than the alternative. If any of those UAFRs turn out to be Special UAFRs, the transit provision wouldn't apply and the approval path would be much heavier.

Recreational operators would have the sharpest problem. The proposed rule doesn't include recreational operators in the transit categories and would require separate authorization from the FAA Administrator for them to operate in a UAFR. If a facility near your home receives a UAFR designation, recreational flying there would become significantly harder. I expect the AMA to keep pushing on this during the rulemaking process, but operators should plan for the current proposed language as the baseline.

The state law overlay

This is the part of Section 2209 that most operators haven't thought through, and it's the one I think matters most for how the rule would actually play out.

More than a dozen states wrote their own critical infrastructure drone laws during the federal delay. The specifics vary substantially. Arizona makes it a felony to intentionally photograph or loiter over or near a critical facility in furtherance of a criminal offense. Arkansas prohibits knowingly using a drone to conduct surveillance of, gather information about, or record critical infrastructure without prior written consent. Louisiana has surveillance-focused restrictions plus separate correctional-facility overflight provisions. Connecticut restricts drone operation below 250 feet over a defined critical-infrastructure facility or within 100 horizontal feet, subject to statutory exceptions. Each of these state regimes remains on the books and may apply according to their terms, subject to statutory exceptions (many of which include carve-outs for FAA-compliant operators) and federal preemption analysis.

The proposed Section 2209 rule doesn't explicitly preempt these state laws. Federal aviation preemption applies in the fields of aviation safety and efficient airspace use, but outside those fields, states can regulate if their laws don't conflict with FAA rules. Whether a specific state law would conflict with a specific federal UAFR is a case-by-case question. Not all state laws will survive that analysis, and not all federal UAFRs will preempt state law even where they overlap.

Here's the founder's perspective on this. The federal rule was supposed to create clarity. What it would actually create, at least in the near term, is more layers to navigate. Facility owners in states with existing critical infrastructure drone laws could end up holding both a federal UAFR and enforceable state protections at the same time. A Part 108 delivery operator running routes across five states could face five different state statutes governing the same physical airspace as the federal UAFR. The operators who figure out how to integrate multi-state compliance planning with federal UAFR compliance are going to have a real competitive advantage over the ones who treat Section 2209 as the only rule that matters.

Where I think this goes

Two things I'm watching that would shape how this rule plays out over the next twelve to twenty-four months.

First, the transit provision is the single biggest variable in the final rule. If the FAA preserves proposed section 74.250 substantially as drafted, the commercial drone industry would have a workable path to continue operating in and around UAFR airspace. If the FAA modifies it in response to comments or during finalization, commercial route economics could change substantially. What I'm watching is how the FAA responds to the transit comments and whether the final rule keeps the Parts 91, 107, 108, 135, and 137 list intact or narrows it.

Second, and this is the founder observation I care about most, Section 2209 could accelerate the air rights conversation. If a facility owner would hold a UAFR designation, they wouldn't hold approval authority over the airspace. The FAA has been explicit that a UAFR wouldn't give site managers authority to approve, disapprove, restrict, or prohibit compliant operations. What the facility owner would hold is a legal designation, a Federal Register entry, and the ability to ask law enforcement to focus resources on unauthorized flights. That's meaningful, but it isn't property. As a founder in the drone economy, I think this distinction is going to become one of the important conversations of the next few years: how do we build commercial arrangements around airspace above ground facilities in a legal environment where the facility owner would have some standing to influence what happens above them, but not exclusive control? Section 2209 puts that question in front of the industry more concretely than any prior rule.

Get ready.