Counter-UAS is becoming a multi-agency challenge
For many years, Counter-UAS was primarily approached as a military capability: Detect the drone. Identify the threat. Defeat it.
For law enforcement and public safety, the reality is different. A drone appears near an airport, railway, major event, prison or critical infrastructure site.
Who owns the problem?
The police?
The infrastructure operator?
The aviation authority?
A security organization?
Or an organization already operating drones in that airspace?
Increasingly, the answer is: several of them.
And that is where the real Counter-UAS challenge begins.
Different organizations see different parts of the incident.
A sensor detects an unknown aircraft. An aviation system knows about authorised drone operations. Police hold operational intelligence. The infrastructure operator understands the local threat and potential consequences. Another public-safety organization may have its own aircraft in the air. Individually, these are fragments of information. Together, they can create the shared operational picture needed for coordinated decision-making. The future of public-safety Counter-UAS therefore cannot simply be about connecting more sensors to a command centre. It needs to connect organizations, information and decisions.
Multi-agency means more than sharing data.
Connecting organizations is considerably more complex than connecting systems. Each participating organization has its own responsibilities, information, security requirements and legal authority. Effective multi-agency operations therefore require more than exchanging a data feed. Organizations need to determine who can see what, which mission or aircraft information can be shared, under what conditions, and for how long. Access and operational rights may need to be granted to another organization for a specific operation and withdrawn again when that operation ends.
Some information can be shared widely. Other information may only be available to specific roles, agencies or individuals. In some cases, an organization may need to share the existence or status of an operation without exposing the underlying sensitive information. This becomes even more complex when operations cross national borders. Different agencies, regulatory frameworks, security classifications, authorities and operating procedures may need to work together around the same airspace and the same incident.
True multi-agency interoperability is therefore not simply about whether systems can exchange data. It is about whether organizations can share the right information, with the right organization, under the right authority, at the right moment, and retain control over that access.
Who does what?
A multi-agency response needs to answer some fundamental questions:
Who detects?
Who identifies?
Who assesses the threat?
Who has legal authority?
Who decides?
Who responds?
How are decisions shared and recorded across agencies?
These questions become increasingly important as lower airspace grows more complex. Police, fire and rescue services, border agencies, infrastructure operators and commercial operators may all be conducting legitimate UAS or BVLOS operations while an unidentified drone enters the same environment.
So the first question isn't necessarily:
“How do we stop the drone?”
It may be:
“Does everyone involved have the same operational picture?”
The layer between detection and response.
Counter-UAS is developing from a primarily technological challenge into an operational and multi-agency governance challenge. Detection remains essential. Mitigation may sometimes be necessary. But between detection and response sits a critical operational layer:
Shared situational awareness → Threat assessment → Authority → Coordinated decision-making → Response → Evidence & audit trail
Technology alone cannot provide this. Effective Counter-UAS requires participating organizations to understand the same situation, know their respective responsibilities and authorities, and coordinate decisions and actions across organizational boundaries. In cross-border operations, that coordination must extend across national boundaries without requiring participating organizations to surrender control of their own operational information.
Where SKYOPS fits.
SKYOPS supports this by creating a shared operational picture across organizations, while allowing each participating agency to retain control over its own roles, responsibilities, permissions and operational information. This is more than data sharing. Participating organizations can determine which operational information is shared, with whom and under which permissions. Access can be granted for a specific operational purpose and withdrawn when it is no longer required. Mission and aircraft information can be selectively shared without automatically exposing the complete underlying operation. Known UAS and manned aviation activity, airspace information, sensor detections, C-UAS tracks and operational intelligence can be brought together within one operational environment. Role-based access keeps sensitive information controlled, while relevant information can be made available across organizational and, where required, national boundaries. This enables police, fire and rescue services, defence, aviation authorities and critical-infrastructure operators to coordinate around the same incident while retaining their own authority and information governance.
SKYOPS does not replace the specialist systems of participating organizations. It provides the operational layer that connects them: One airspace. Multiple agencies. One shared operational picture.