Counter-UAS Site Survey Checklist for Project Planning

Plan a counter-UAS site survey covering assets, threats, RF noise, sight lines, installation, power, networks, operations and acceptance routes.

A field-ready checklist for mapping assets, threats, RF conditions, sight lines, installation constraints, networks and acceptance routes. A counter-UAS site survey converts a product concept into an installable and testable system. It documents the protected assets, likely drone approaches, radio environment, terrain, sensor sight lines, mounting points, power, networks, maintenance access and legal constraints. Without this work, quoted coverage circles and equipment quantities are assumptions rather than an engineering design. The survey should produce evidence that another engineer can review: maps, coordinates, photographs, spectrum records, obstruction profiles, network diagrams, installation constraints and a draft acceptance route matrix. What should be prepared before visiting the site? Collect current site plans, aerial imagery, asset lists, operating hours, incident history, approved drone activity, security procedures and responsible contacts. Ask for known radio systems, restricted areas, roof-access rules, hazardous zones and future construction. Prepare a coordinate system, map layers and naming convention so observations from different teams can be combined. Bring calibrated or verified instruments appropriate to the task, plus permission for photography, spectrum observation and any controlled flight activity. Which assets and consequences must be mapped? Mark assets whose disruption would create safety, operational, financial or regulatory impact. Include approach corridors, storage, power distribution, control rooms, public areas and locations where evidence or response teams must operate. For each asset, document the required warning time and the decision that follows an alert. A runway may require earlier warning than a small fenced yard. A data center roof may prioritize reliable near-boundary identification, while a border site may prioritize long linear coverage. How should likely drone approaches be assessed? Review launch access, roads, public land, terrain masking, rooflines and prevailing operational patterns. Consider low flights along structures, direct high approaches, autonomous routes and controller locations. Do not assume threats approach from the direction with the best sensor view. Create representative routes and heights for later testing. Mark segments where line of sight is blocked, where a target may appear late…