Drone services need more than FAA permission to survive politically and legally over the long term. They need property permission. A drone can be airworthy and lawfully piloted and still generate trespass, nuisance, privacy, or takings problems if it repeatedly cuts through the immediate reaches above private land. This article lays out a permissioned drone-access model grounded in express consent, paid licenses, recorded avigation easements, public-right-of-way corridors, community opt-in zones, and narrow emergency exceptions. The aim is not to ground drones. It is to hand drone operators a legitimate, insurable, financeable, publicly tolerable pathway through low-altitude space - while keeping intact the individual landowner’s right to exclude and to get paid when that right is burdened.
I. The missing layer in drone policy: access, not just safety
Most drone regulation starts from aviation safety, and that makes sense. The aircraft has to be safe, the pilot or operator qualified, the route collision-free, and the whole operation compliant with FAA rules. Small UAS operations under Part 107 generally happen at or below 400 feet above ground level, which puts drones in the band where landowner interests are most credible.[1]
But safety clearance is not property authorization. A truck can be roadworthy and licensed; that does not entitle it to roll across a private driveway uninvited. A utility can be regulated from top to bottom; that does not let it string wires over private land without an easement. A drone may satisfy every FAA requirement on the books; that should not amount to a free easement through the lower sky over every home, farm, business, school, and church.[2]
The distinction matters because legitimacy is at stake. If drone policy treats private low-altitude airspace as ownerless, it is asking for backlash from homeowners, local officials, privacy advocates, and eventually judges. If it treats low-altitude access as a property problem, it opens up the possibility of a market. Landowners can say yes, operators can pay, communities can set terms, and public-safety agencies can build routes people actually trust.
II. Permission as infrastructure
Permission is not a roadblock to drone infrastructure - permission is infrastructure. A workable aerial network demands predictable rights of passage, and the legal tools for creating those rights already exist. A landowner can give express consent for a single flight. A business can issue a revocable license for inspections. A homeowner association can approve a delivery corridor subject to defined limits. A city can license access over its public rights-of-way. A drone operator can acquire a recorded avigation easement for recurring flights.[3]
Permission should be understood broadly, but it should not be watered down. Express landowner consent counts. A paid easement counts as permission plus compensation. A recorded covenant may bind successors. A license may be temporary and subject to revocation at any time. A statutory emergency exception may authorize entry when there is a genuine emergency, but it ought to be narrow and auditable. What should not count as permission is the bare fact that the aircraft is capable of flying there.
A workable access instrument should pin down at least eight things: the horizontal route, altitude band, time of day, duration of permission, payload or use case, noise and lighting limits, data-collection constraints, and compensation. It should also specify who may fly, who may view or store data, how long it is retained, and when it must be deleted. The more intrusive the use, the more formal the instrument needs to be.[4]
III. Avigation easements and micro-easements
Aviation law already supplies the essential template. When airport operations burden nearby land with low overflights, noise, clearance restrictions, or approach surfaces, governments and airport sponsors routinely acquire avigation easements. Griggs held that an airport sponsor had effectively taken such an easement. Federal law recognizes the acquisition or condemnation of airspace interests needed for airports and navigation facilities.[5]
Drone corridors should follow the same logic, only smaller. A recurring commercial drone route over a private parcel is, functionally, a low-altitude avigation easement. It may not be as heavy a burden as a jet approach path, but it is still an access right over someone else’s property. If that access has value to the operator and imposes a burden on the owner’s right to exclude, the property system should treat it as a compensable, negotiable interest.
A micro-avigation easement could be standardized without much difficulty. It might authorize flights within a narrow altitude band, over a mapped path, at specified times, below defined noise thresholds, with no hovering except for safety, no imaging except for navigation, and automatic deletion of incidental data. It might pay annual rent, per-flight fees, or community royalties. It might bundle indemnity, insurance, and a complaint process. It could lapse unless renewed. None of this is exotic. It is ordinary property law applied to a new vehicle.
IV. The scholarly case for airspace sharing
Troy Rule has argued that recognizing landowner airspace interests can actually help commercial drone development rather than hinder it. His 2023 work on drones and the sharing economy proposes that landowners could license low-altitude airspace to drone users, building a market that protects property rights while giving drone operators the certainty they need.[6] In earlier work, he argued that existing aerial trespass and takings doctrines are a poor fit for drones because “immediate reaches” is too vague to support a scalable industry.[7] His prescription is to sharpen the entitlement, not to pretend it does not exist.
Rule’s drone-zoning work is also relevant here. Drone operations are not interchangeable. A rural crop-monitoring flight, a roof inspection, a police emergency response, a delivery corridor, and a hovering news drone each carry different risks. State and local governments are often better placed than the FAA to deal with privacy, land use, takeoff and landing sites, noise externalities, and the distribution of local burdens - provided they do not collide with federal aviation safety rules.[8]
Brent Skorup arrives at a comparable conclusion from a federalism and infrastructure angle. He contends that landowners - public and private - hold low-altitude airspace interests, and that drone operators face trespass, nuisance, and takings exposure if those interests get brushed aside. He has proposed cooperative federalism and leasing of airspace above public roads as a way to build drone highways while sidestepping many private-property conflicts.[9] His work on auctioning airspace treats route exclusivity and transferability as tools for reducing congestion, financing infrastructure, and allocating scarce aerial corridors efficiently.[10]
V. A policy architecture for permissioned corridors
A state, city, or regional compact could implement - given the right technology - permissioned drone access through seven linked components.
First, define a presumptive landowner-control layer. The statute does not have to settle every altitude question for all time. It can set a practical default: drones may not engage in recurring, non-emergency, low-altitude transit through the immediate reaches of private land without permission. The precise altitude might shift depending on use, structure height, zoning district, or state policy. The point is to establish a default property rule, not to micromanage aircraft safety.
Second, create a consent registry. Landowners, HOAs, building owners, utilities, farms, and commercial campuses could opt into specified drone uses. Consent could be parcel-specific, route-specific, time-limited, and revocable unless memorialized as an easement. Operators would get machine-readable confirmation of where they are and are not cleared to fly.
Third, standardize licenses and easements. A short-form drone-access license could handle occasional roof inspection, property management, or agricultural monitoring. A recorded drone avigation easement could handle recurring delivery or public-safety routes. Standardization cuts transaction costs and makes underwriting easier.
Fourth, prioritize public-right-of-way corridors. Streets, alleys, utility corridors, railroad corridors, waterways, and public buildings are the natural starting points. Many routes can be laid out to follow public or already-burdened corridors, which reduces the need to cross private homes. This is the strongest piece of Skorup’s road-airspace proposal.[11]
Fifth, require compensation where access is recurring or commercially valuable. Compensation can flow to individual owners, neighborhood associations, community benefit funds, or municipal air-rights trusts. Payment is not just about fairness; it is a political stabilizer. People resist being used for free. Many of them will accept being paid under clear rules.
Sixth, adopt privacy and data-minimization rules. Permission to transit is not permission to surveil. Navigation cameras, thermal sensors, microphones, facial-recognition tools, ALPR payloads, and high-zoom optics each deserve separate treatment. The route license should specify what data may be collected, who can access it, how long it is retained, and when it must be deleted.[12]
Seventh, preserve narrow emergency exceptions. Fire, search and rescue, active threats, disaster response, and imminent threats to life may justify temporary nonconsensual access. But emergency exceptions should be logged, time-limited, reviewable, and tied to genuine exigency. They should not quietly expand into a general municipal drone privilege.
VI. Drone first response under a permissioned model
Drone first response is both the hardest and the most important test case. Public-safety drones can arrive before officers, assess danger, locate missing persons, inspect fires, and reduce unnecessary police contact. Those benefits are real and no one should dismiss them. But a DFR program that normalizes routine low-altitude government flights over residential areas also raises the sharpest privacy and constitutional concerns.
A permissioned DFR model should start with public assets: police and fire stations, city buildings, parks, streets, alleys, utility corridors, and other municipal property. From there, it should layer in voluntary private corridors through express consent, neighborhood opt-in agreements, and compensated easements. For recurring routes over private land, the agency should secure permission or pay for access. For genuine emergencies, the agency may rely on narrow exigent-access authority, but should log the flight, purpose, route, sensors used, retention period, and any sharing of footage.
This structure does something important for public trust. It lets a city say: we are not building a general aerial surveillance state; we are building defined, audited, permissioned response corridors. And it lets homeowners say yes without giving up everything. A person might consent to fire-response overflight but not package delivery; to transit but not hovering; to daytime flights but not nighttime ones; to navigation imaging but not investigatory recording.
VII. Counterarguments and answers
Holdouts. A single owner could block a route. The answer is corridor design and technology-driven aggregation. Routes should begin over public rights-of-way and consenting parcels. Owners can join pools, HOAs can negotiate collectively, and dynamic contracts can reduce friction. In the rare cases where a route is genuinely necessary for public use, eminent domain and just compensation remain available. What is not legitimate is dodging the holdout problem by denying that anyone owns the burdened interest.
Preemption. Singer v. City of Newton illustrates that local drone rules can be struck down when they clash with FAA objectives or effectively create a parallel local aviation code.[13] That is a real constraint. But it does not wipe out all property, trespass, privacy, zoning, and consent requirements. The FAA’s own UAS fact sheet draws a line between federal aviation-safety regulation and the many state and local police-power subjects that remain on the table.[14] The drafting lesson: regulate authorization to use property and local impacts, not aircraft design or air-traffic control.
Transaction costs. But spectrum policy shows that defining rights and enabling secondary markets can attract investment to invisible resources that are otherwise nearly impossible to share.[15] Airspace markets will need a registry, APIs, insurance, standard instruments, and dispute resolution. That is infrastructure, and it is worth building.
Equity. Wealthy neighborhoods may sell access while poorer neighborhoods absorb the cost. A permissioned system should therefore include anti-concentration rules, community benefit payments, public transparency, and opt-out rights. The goal is to prevent uncompensated burdens - not to hand anyone a license to exploit the most politically vulnerable neighborhoods.
The right to exclude is too strong for a technological age. The opposite is closer to the truth. New technology makes exclusion more important, not less. Loretto and Cedar Point did not become irrelevant because cable equipment was useful or union access was temporary.[16] Drone networks may be socially beneficial, but usefulness is exactly why the Takings Clause exists: so the public can obtain what it needs while spreading the cost rather than dumping it on a few property owners.[17]
Conclusion
Permissioned drone access is the constitutional middle path. It backs drones by giving them lawful corridors. It backs landowners by preserving consent and compensation. It helps cities by reducing backlash and litigation risk. It helps investors by converting legal uncertainty into defined, transferable assets. The future of low-altitude flight should not rest on the fiction that the lower sky is empty. It should rest on the same tools that have always made infrastructure possible: property rights, easements, licenses, public corridors, and payment.
Notes
[1] 14 C.F.R. pt. 107; 14 C.F.R. § 107.51(b).
[2] 49 U.S.C. § 40103; United States v. Causby, 328 U.S. 256, 264-67 (1946).
[3] Causby, 328 U.S. at 264; Griggs v. Allegheny County, 369 U.S. 84, 89 (1962).
[4] Kaiser Aetna v. United States, 444 U.S. 164, 176 (1979); Cedar Point Nursery v. Hassid, 594 U.S. 139, 149-50 (2021).
[5] Griggs, 369 U.S. at 88-90; 49 U.S.C. § 40110(a)(2).
[6] Troy A. Rule, Drones, Airspace, and the Sharing Economy, 84 Ohio St. L.J. 157 (2023).
[7] Troy A. Rule, Airspace in an Age of Drones, 95 B.U. L. Rev. 155 (2015).
[8] Troy A. Rule, Drone Zoning, 95 N.C. L. Rev. 133 (2016).
[9] Brent Skorup, Drone Technology, Airspace Design, and Aerial Law in States and Cities (Mercatus Center, Dec. 2020); Brent Skorup, Aerial Law in States and Cities, 55 Akron L. Rev. 157 (2022).
[10] Brent Skorup, Auctioning Airspace, Mercatus Working Paper (2018).
[11] Skorup, Drone Technology, Airspace Design, and Aerial Law in States and Cities, supra note 9.
[12] California v. Ciraolo, 476 U.S. 207 (1986); Florida v. Riley, 488 U.S. 445 (1989); United States v. Jones, 565 U.S. 400 (2012); Kyllo v. United States, 533 U.S. 27 (2001).
[13] Singer v. City of Newton, 284 F. Supp. 3d 125 (D. Mass. 2017).
[14] FAA & U.S. Department of Transportation, State and Local Regulation of Unmanned Aircraft Systems (UAS) Fact Sheet (updated July 2023).
[15] Dale Hatfield & Phil Weiser, Toward Property Rights in Spectrum: The Difficult Policy Choices Ahead, Cato Institute Policy Analysis No. 575 (Aug. 17, 2006).
[16] Loretto v. Teleprompter Manhattan CATV Corp., 458 U.S. 419 (1982); Cedar Point, 594 U.S. 139.
[17] U.S. Const. amend. V; Penn Central Transportation Co. v. City of New York, 438 U.S. 104 (1978).