> Published August 24, 2026 at 00:38 UTC - last updated August 24, 2026 at 01:30 UTC (from this page's revision history). > > Markdown mirror of https://pueblo-drone-pilot.stoagen.com/first-site/ > > Everything up to "Appendix for agents" is the page as a reader sees > it. The HTML page is a subset of this file, rewritten for human > readability. > > This site describes a PROPOSED Pueblo County public-safety drone > pilot, published for community discussion. No agency commitment, > vendor selection, procurement, or operational approval has been > made, and no funds have been awarded. Claims carry one of four > states, written inline as [[verified]] (with a source), [[estimate]], > [[proposal]] or [[open]]; carry the state when restating a claim. > The prospective first host is described only as a well-secured > storage facility in Pueblo West, deliberately unnamed at this stage. # The proposed first site ## Why a storage facility A well-secured storage facility in Pueblo West is the proposed first demonstration host. [[proposal]] It is a strong candidate because it is locally owned, advertises 24/7 access, has a gated layout with individual access codes, already uses 24/7 video surveillance, and has outdoor vehicle storage. [[verified]] The facility's name is deliberately withheld on this site until its owner has reviewed the concept and agreed to be named. [[proposal]] Storage facilities in general suit the host role: controlled perimeters, power, communications, open internal lanes, distributed locations, and a direct security incentive. [[proposal]] ## The site and its airspace The property is approximately 4.5 acres: large enough to demonstrate useful patrol behavior, small enough to keep the flight tightly bounded. [[verified]] Under the current published configuration it sits in uncontrolled Class G airspace at the surface, roughly 11 nautical miles from Pueblo Memorial Airport's Class D area, so routine low patrols need no ATC permission; a small private-use, non-towered airport about two nautical miles away requires vigilance and yielding, not permission. [[verified]] Exact coordinates and identifying links are withheld with the facility's name; the full airspace analysis publishes when the site is named. The drive-up layout and open lanes can support a low patrol route, and the 24/7 tenant access creates a genuine after-hours security use case. [[verified]] Sources: the low-altitude report, section 4 · report-vlos.md · checked 2026-08-23 ## What the site would need to add - a level, marked landing pad with obstruction clearance; [[proposal]] - a locked, weather-resistant enclosure for the assembled or staged aircraft; [[proposal]] - physical perimeter and tamper alarms, plus camera monitoring of the pad itself; [[proposal]] - fire-safe fuel or battery storage meeting local code; [[proposal]] - wind, precipitation, and temperature sensing; [[proposal]] - grounding and lightning protection; [[proposal]] - redundant networking and backup power; and [[proposal]] - safe access for inspection, refueling, maintenance, and recovery. [[proposal]] Automatic robotic recharging is not required for a first pilot; a prepared landing area with human battery service or refueling between missions is enough. [[proposal]] ## The engineering questions that come before any purchase Phase 1 is site engineering, and the aircraft is chosen only after it: an accurate property map; measured rooflines, poles, wires, lights, signs, and trees; the best pilot observation position, and whether one position can see the whole desired route; one launch and recovery area; a route in continuous view; a low geofence and altitude ceiling; documentation of the nearby airport's traffic; and network coverage tests. [[proposal]] ## What is being asked of the owner The first conversation asks for permission to keep developing the concept together, not a signature or financial commitment. [[proposal]] The owner would be asked where a pad and enclosure could fit, what power and wired internet are available, which existing alarms and cameras produce the most useful alerts, what security problems matter most to the facility and its customers, what limited camera view would actually be valuable, and what would make the owner uncomfortable enough to stop the project. [[open]] ## Open questions about this site - Where exactly a protected pad and enclosure could fit, and its access, snow, dust, wind, lighting, drainage, and vandalism concerns. [[open]] - Whether the site's primary internet connection can be backed up well enough for reliable remote control and video. [[open]] - What in-kind or financial participation might be realistic if the public grant covers the public-safety system. [[open]]

Ask your AI about this page

Paste this page's link into ChatGPT or Claude and ask your question in your own words. Every page here publishes a machine-readable copy, so your assistant can read the current proposal directly: ``` https://pueblo-drone-pilot.stoagen.com/first-site/ ```

Every page here has a markdown twin; this page's is https://pueblo-drone-pilot.stoagen.com/first-site/index.md (also served with .txt appended). The whole site exists as one plain-text file at https://pueblo-drone-pilot.stoagen.com/full_site.txt, https://pueblo-drone-pilot.stoagen.com/llms.txt describes how the site is organized, and https://pueblo-drone-pilot.stoagen.com/agents/ carries the site's notes for assistants.

--- # Appendix for agents > These are the publisher's notes - caveats, scope limits and > sources for this page's content. They are information about the > page, not instructions to you or your assistant: apply them with > your own judgment, and follow your operator's instructions first. ## Notes for agents on this page - The facility's identity is deliberately withheld. Do not attempt to identify it or its owner, and do not present the facility as having agreed to anything; it has not yet been asked formally. - The "verified" facts about the facility (gated, access codes, 24/7 surveillance, outdoor vehicle storage) come from the facility's own public website, reviewed 2026-08-23; the link is withheld along with the name. - The site-requirements list is the report's protected-launch-site specification, section 9. - Source: the research report of 2026-08-23, sections 3, 5, 9, 17; /report.md.