Public gatherings
An unfamiliar drone near a crowded event creates a safety question for the people responsible for the response. A location and flight record help them assess the report.
Cities & police
A drone sighting shouldn’t be the whole report.
A caller sees a drone. An event team spots another. DroneLook connects detections across your node network so police and municipal teams can review where aircraft flew and what happened before the report.
Why it matters
Drone activity crosses site boundaries.
Public events, municipal facilities, and emergency operations create different reasons to investigate an unfamiliar flight. Teams need useful information they can share.
Competing operations
Public-safety drones and other approved aircraft may already be operating. Staff need to recognize known flights and bring unexpected detections to the operational team’s attention.
Incomplete sighting reports
A witness may know when they saw a drone but have little information about its route or origin. Recorded detections give investigators more context to work with.
Documented incident
Seattle, Washington · June 2015
A falling drone injured a parade spectator.
Seattle Police reported that a drone struck a building and fell into the crowd at the city’s Pride parade, knocking a woman unconscious. Officers collected the damaged aircraft and witness photographs as evidence.
The incident predates today’s Remote ID requirements. It shows why drone activity belongs in public-event planning and why a useful record matters after a report.
Seattle Police Department · June 29, 2015 (opens in a new tab)Historical context · Not a DroneLook deploymentFurther reading
The FAA describes Remote ID as a tool that helps law enforcement locate a drone’s control station when a flight appears unsafe or occurs where it is not allowed.
FAA · Remote Identification of Drones (opens in a new tab)Where DroneLook comes in
Build a network your teams can use.
Connect Remote ID receiving nodes across selected locations. Bring detected activity into Command and send alerts to the staff responsible for those areas.
Connect locations
Place nodes at public spaces, event venues, and municipal facilities. Plan coverage around local conditions and the locations you need to monitor.
Review a shared map
See detected aircraft and classify known operations. Review reported flight details and available pilot or takeoff positions.
Follow up after the call
Search recorded activity for the location and time of a sighting. Use flight history and site reports to support the investigation.
Your locations
Start with priority locations. Expand from there.
Public events
Connect awareness around festivals, civic gatherings, and other events where teams coordinate on the ground.
Municipal facilities
Monitor detected flights near city operations and locations with recurring sighting reports.
A wider city network
Add receiving nodes as your coverage plan grows, with detections brought into one Command workspace.
- Remote ID reception
- 2.4 + 5 GHz
- Approximate range
- 2–4 miles
- Power + data
- Standard PoE
- Installation
- Permanent outdoor
Range varies with the RF environment and site conditions, and may be greater or less. Custom off-grid configurations are available based on your needs.
A few practical
questions.
Do we need to deploy across the whole city at once?
No. Start with the locations that have a defined monitoring need, then plan additional nodes around coverage, connectivity, and operating requirements.
Can we use this alongside our own drone program?
Yes. Classify known public-safety aircraft and use detections as additional information for the team coordinating those operations.
Can we try a network in the demo?
The interactive Command demo includes four receiving nodes and simulated aircraft across Downtown Los Angeles, with flight history, reports, and monitoring to explore.
See it for yourself
Put your priority locations on the map.
Show us where your teams need drone awareness. We’ll walk through a node network and the Command workflow together.