Zoned by the Parcel, Flown by the Radius

A Richardson, Texas, homeowner stood at a council microphone in February and reported 122 Amazon delivery drones over her house in a single ten-hour period, roughly one every five minutes (Zeff, "Richardson Residents"). By April, the council that had approved the facility on a four-to-three vote met in executive session to ask whether it could withdraw its approval. The answer was no. The zoning was valid, and the legal exposure of undoing it was too great. The city manager advised residents to complain to the FAA and to their members of Congress (Zeff, "Richardson City Council").

That sequence is about to go national. Amazon plans to offer drone delivery in nearly 500 cities and towns by year-end, a sixfold expansion, with an internal target of one million deliveries (Palmer). Each site serves a 7.5-mile radius (Amazon).

The usual critique is that municipal codes lack a definition for a drone hub. True, and a few cities are fixing it. That framing understates the problem.

Zoning is a parcel-based instrument. Drone delivery is a radius-based entitlement. A public hearing notice reaches owners within a few hundred feet of the site. A 7.5-mile service radius covers roughly 176 square miles, several thousand times the size of the noticed area. The population that receives legal notice and the population that experiences the impact barely overlap.

The land use process assumes notice precedes impact. Here, impact precedes awareness. The opposition constituency is not assembled before the vote by certified mail. It is assembled after the vote, by operations, at a moment when the entitlement is already legally unassailable.

A council member who voted yes and cannot vote no again retains one instrument: public criticism of the applicant. Approval turns your supporters into your most motivated critics, because expressing frustration is the only authority they have left. In Richardson, Amazon raised the minimum altitude for outbound flights to an average of 225 feet and rerouted traffic over commercial land (Zeff, "Richardson City Council"). These were real concessions, made after the vote, that bought compliance rather than support.

Note what the city could still enforce. The zoning change capped delivery hours from 7 a.m. to 8 p.m. (Zeff, "Richardson Residents"). That single condition, written into the approval, outperformed every letter the city sent afterward.

Local winners: industrial and flex landlords whose sites are deeply separated from housing, a feature increasingly priced. Cities that define use before the first application, because leverage exists only before rights vest. Second wave jurisdictions that write conditions from another city's complaint log.

Local losers: the first city in a region to say yes, whose council absorbs the learning curve in public. Residents under the corridor, who bear the impact but have no permit to appeal. The next applicant in that jurisdiction, because when a lightly reviewed approval produces a loud surprise, the legislative response is never narrow. Notice radii widen, use tables tighten, and a housing project two years later pays for a drone hub's noise complaints.

There is also a fiscal consequence that nobody models. In Richardson, a homeowners association president told the council that neighbors were considering protesting their home appraisals (Zeff, "Richardson City Council"). A city that books a delivery hub as an economic development win may find that part of the cost returns as a soft spot in its tax base.

Underwrite the radius, not the parcel. Before site control, map the corridor: which neighborhoods, which associations with covenant authority, which council districts, which schools and parks. Size political diligence to the service area, not the notice area.

Volunteer conditions while you still have something to trade. Hours, altitude floors, routing commitments, a published complaint line with a response standard. Offered at the hearing, these win votes and credit. Extracted later, they win nothing.

Build the record you will need at the federal level. Every new site still clears FAA review and public comment. A city with a thick complaint file and no relationship with you will use it.

If you build anything else in these markets, watch the ordinances being drafted right now. Reactive codes are written broadly.

Cities will not win jurisdiction over the sky. They will use every tool they still hold, with the intensity of officials surprised in front of their own constituents. Legal validity does not solve that. Sequencing does.

Land Use Strategies has spent three decades building public and political support to get projects approved and keep them running afterward. If you are siting aerial logistics infrastructure or building in a city that just learned it cannot regulate its own airspace, we should talk.

Works Cited

Amazon. "Amazon Prime Air Drone Delivery Expands to Nearly 500 US Cities and Towns by 2026." About Amazon, 19 Aug. 2026, www.aboutamazon.com/news/transportation/amazon-prime-air-drone-delivery-expansion.

Palmer, Annie. "Amazon to Expand Drone Service to Nearly 500 Cities after Targeting 1 Million Deliveries This Year." CNBC, 19 Aug. 2026, www.cnbc.com/2026/08/19/amazon-plans-drone-expansion-as-top-exec-projects-1-million-deliveries.html.

Zeff, Isabella. "Richardson City Council Will Not Pursue Amazon Rezoning after Drone Complaints." Community Impact, 14 Apr. 2026, communityimpact.com/richardson/government/richardson-city-council-will-not-pursue-amazon-rezoning-after-drone-complaints/.

Zeff, Isabella. "Richardson Residents Voice Concern about Amazon Delivery Drone Noise, Frequency." Community Impact, 13 Feb. 2026, communityimpact.com/richardson/government/richardson-residents-voice-concern-about-amazon-delivery-drone-noise-frequency/.