A single new polygon of restricted airspace over Manhattan is a small thing on its own and a useful lesson for the whole drone industry. On April 30, 2026, the FAA published a Notice of Proposed Rulemaking (Docket FAA-2025-2635, Airspace Docket No. 25-AWA-5, RIN 2120-AA66) proposing to establish Prohibited Area P-75 in the vicinity of the President's New York, NY residence. The United States Secret Service requested the restriction, and the FAA frames it as necessary to let the USSS fully secure the non-governmental property and protect its protectees in the interest of national security. The proposal amends 14 CFR Part 73, the regulation that houses special-use airspace, and comments were due June 15, 2026.
A prohibited area is the most restrictive class of special-use airspace: aircraft operations within it are barred, and 'aircraft' under modern FAA usage includes unmanned aircraft. So while the headline driver here is securing a high-value protectee against threats from the air, the practical effect lands on everyone who flies in that slice of one of the densest, most commercially active airspaces in the country - and in 2026 that increasingly means drone operators, not just helicopters and business jets.
Small polygon, real operational friction
New York City airspace is already a layered, restricted environment, and drone operators flying legitimate commercial missions there - building inspections, media, public safety support, infrastructure surveys - already navigate a dense map of controlled airspace and existing restrictions. P-75 would add one more hard exclusion, and crucially it is a security-driven one, which tends to be non-negotiable in a way that ordinary controlled airspace is not. You can sometimes get authorization to operate in controlled airspace; you do not casually get cleared into a prohibited area established to protect a presidential residence. For an operator planning a flight near that zone, P-75 is a flat no-go that has to be designed around.
The lesson generalizes beyond this one site. Security-driven airspace carve-outs are proliferating, and each is established for its own narrow protective purpose with little regard for the cumulative effect on commercial drone operations. The same period's docket shows the pattern: the FAA is simultaneously building a process for fixed-site facilities to request their own drone restrictions under Section 2209. Add prohibited areas for protectees, temporary flight restrictions for events, and facility-requested flight restrictions, and the urban airspace a commercial drone operator must reconcile becomes a moving patchwork of exclusions, each individually reasonable and collectively a planning burden.
Who this is a business problem for - and who it's a business for
For drone-services companies operating in major cities, the patchwork is a direct operating cost. Every new restricted polygon is one more thing flight planning has to ingest, one more reason a mission gets scrubbed or rerouted, and one more compliance edge that, if missed, becomes an enforcement problem. Security restrictions raise the stakes because flying into a prohibited area protecting a protectee is not a paperwork foot-fault; it is the kind of incident that draws law-enforcement and reputational consequences. The operators that scale in dense cities will be the ones with disciplined airspace-deconfliction processes, not the ones improvising.
That same friction is the business case for the other side of the market. The quiet beneficiary of every new exclusion zone is the airspace-data, UAS Traffic Management and flight-authorization software layer. A prohibited area is only a problem if your planning system does not know about it; the value of a service that keeps every temporary flight restriction, prohibited area and facility restriction current and machine-readable goes up with every polygon the FAA adds. As security carve-outs multiply, the ability to consume them automatically stops being a nice feature and becomes table stakes for operating commercially in a city.
There is a counter-drone dimension here too, because a prohibited area is only as good as the ability to detect and respond to the aircraft that ignore it. A rule that bars drones from the airspace over a protected residence implicitly raises demand for the detection, identification and mitigation systems that let the Secret Service and partner agencies know when something is flying where it should not be. That is a distinct and fast-growing slice of the autonomy-adjacent market - the counter-UAS vendors whose radar, radio-frequency sensing and identification tooling turns a regulatory line on a chart into an enforceable boundary. Every prohibited area established for protective reasons is, in effect, a procurement signal for that capability, even when the rule itself says nothing about how the restriction will be enforced.
The Remote ID regime sharpens this further. With most drones now required to broadcast identification, a security-driven exclusion zone becomes far more enforceable than it would have been a few years ago - the protective agencies can, in principle, see who is flying and where. That is good for legitimate operators, who are increasingly distinguishable from bad actors, and it raises the stakes for the careless ones, who are now both more visible and operating against a denser map of hard restrictions. The structural trend is toward an urban sky that is simultaneously more open to compliant, well-instrumented commercial drones and more tightly fenced against everyone else.
P-75 itself is narrow, security-specific, and still just a proposal - comments were due June 15, 2026, and the FAA will weigh them before finalizing. No one in the drone industry is going to litigate hard against protecting a presidential residence. But the document is a clean instance of a structural trend worth tracking: as both security agencies and infrastructure owners gain channels to fence off airspace, the open sky over American cities is being subdivided, polygon by polygon. For commercial autonomy, the competitive edge increasingly lies in who can keep up with the map.