Colorado towns are pausing drone delivery hubs, not closing the airspace
Castle Rock and Parker are using local land-use authority to stop new hub approvals temporarily while they write rules for noise, privacy, siting, and neighborhood compatibility.
By Joel Kelly

Decision brief
FAA approval governs the aircraft and operation in the national airspace. It does not erase zoning, hub siting, setbacks, lighting, loading, emergency access, community engagement, or other local requirements on the ground.
- Towns
- 2
- Parker pause
- 9 months
- Castle Rock concept
- 18 aircraft
Castle Rock and Parker
Emergency moratorium adopted July 20
Pre-application facility described in town reporting
What changed
The towns paused hub applications while they define the ground rules.
Castle Rock, Colorado, adopted Ordinance 2026-023 imposing a temporary moratorium on the establishment of drone delivery service. Parker adopted a separate nine-month emergency moratorium on commercial drone-delivery hub applications on July 20 while staff studies federal and state rules, other cities, and possible local standards.
The Castle Rock process followed a Walmart pre-application inquiry for a Wing delivery operation at 133 Sam Walton Lane. Town materials and local reporting describe a proposed 18-aircraft facility that would recharge, reload, and launch deliveries from equipment on the store property. A pre-application inquiry is not a final site plan or approval.
Who controls what
Federal flight authority and local land-use approval solve different problems.
The ordinances do not create town-controlled airspace or ground aircraft that are already operating somewhere else. The FAA controls aviation safety, aircraft and operator certification, airspace authorization, and the federal operating framework. The towns are pausing local applications for the physical hubs where aircraft, charging, packages, workers, lighting, access, and surrounding land uses meet.
That split is already visible in the FAA's own package-delivery guidance. The agency says operators must comply with state and local requirements, establish hub and delivery infrastructure, inform communities, respond to public inquiries, and site hubs under local land-use and zoning rules. It also identifies noise-sensitive setbacks and mitigation for wildlife and historic resources as possible parts of environmental review.
Local siting file
What a delivery-hub applicant should bring before the hearing
The strongest application translates aircraft operations into parcel-level facts a resident, planner, fire official, and council member can evaluate.
- 01
Draw the actual site
Show pads, charging, loading, security, setbacks, lighting, access, utilities, emergency areas, and nearby sensitive uses.
- 02
Model the operation
State aircraft count, hours, expected and maximum flights, routes, sound methods, maintenance activity, and abnormal-event handling.
- 03
Publish the safeguards
Explain privacy, cameras, data retention, wildlife buffers, complaint intake, incident reporting, and measurable mitigation triggers.
- 04
Define review points
Use pilot phases, performance reports, renewal conditions, and enforceable thresholds instead of promising that impacts will be minimal.
Deployment consequence
Community fit is becoming an operating requirement, not a press-release section.
Local officials raised questions about repetitive noise, privacy, site design, lighting, setbacks, and compatibility with nearby neighborhoods. Those concerns should be converted into measurable standards rather than treated as a referendum on drones in general: operating hours, sound measurement locations, fleet and pad limits, complaint response, screening, data practices, emergency procedures, and renewal conditions.
For delivery operators, local approval is now part of the deployment stack, not a communications task saved for the end. A technically approved aircraft and mature BVLOS system can still sit idle if the hub does not fit the parcel, zoning code, environmental record, or public process. The scalable program will need a repeatable local siting playbook alongside its FAA operating playbook.
Practical read
The practical line for residents and operators
Strong fit
- Local rules focused on the hub parcel, measurable effects, operating hours, and public accountability
- Operators that engage before selecting a final site and publish the proposed operating envelope
- Pilot programs with explicit limits, reporting, complaint response, and revision points
Account for
- Describing a hub moratorium as a ban on all drone flight
- Treating FAA certification as preapproval of a particular retail parcel
- Using vague privacy or noise promises where measurable local standards are possible
Source file
Verify the reporting
Continue on Drone Authority
Put the report to work
Continue this beat
More policy reporting

Industry · July 15, 2026
Amazon's Chicago plan tops out at 3,000 drone flights a day, and the comment window is open

Rule watch · July 26, 2026
The new counter-drone authority for local police is narrower than the headlines suggest

Rule watch · July 11, 2026