Resources

Drones are rapidly becoming a critical tool in the world of security. From protecting sensitive infrastructure to supporting border surveillance, the use of unmanned aerial systems (UAS) has evolved from manual, pilot-on-site missions to highly automated, remotely supervised Drone-in-a-Box (DiaB) deployments.

As public safety agencies and private security companies increasingly adopt drone technology, the benefits - faster response times, improved situational awareness, and operational efficiency - are becoming clear. However, these advancements also bring new regulatory challenges, particularly for beyond visual line-of-sight (BVLOS) operations.

From Manual Patrols to Autonomous Overwatch

Security applications were among the first use cases for professional drone operations. Initially, these missions were flown manually with pilots on-site, providing aerial views during perimeter patrols, event monitoring, or incident response.

Today, we see a strong shift towards automated DiaB systems that can be permanently installed at strategic locations such as ports, energy facilities, or along national borders. These systems can:

• Launch autonomously in response to sensor alerts or scheduling

• Stream real-time video and data to a remote control center

• Return to the docking station for charging and data upload

• Be integrated with ground-based sensors, alarms, or detection systems

This makes drones a persistent, scalable security asset - capable of providing overwatch, incident response, mapping, and inspection, all in one platform.

Public vs. Private Security Applications

Public Security Use Cases

For public authorities, drones are being deployed in a variety of missions:

• Customs and Border Protection: Monitoring remote areas, detecting smuggling activities, or tracking irregular border crossings

• Coast Guards: Conducting coastal surveillance, vessel identification, or search-and-rescue coordination

• Police and State Security Forces: Responding to threats near sensitive facilities, conducting aerial overwatch, or supporting tactical operations

These state operators often benefit from more regulatory flexibility. In many EU Member States, public authorities are exempt from some of the more stringent requirements for BVLOS operations, enabling them to fly in Class G airspace without full detect-and-avoid systems or even full SORA compliance, provided safety is otherwise ensured.

Civil and Industrial Security Applications

On the commercial side, security companies are deploying drones for:

• Port surveillance

• Perimeter patrols of energy infrastructure (including nuclear sites)

• Monitoring of railways and depots

• Industrial site security in petrochemical zones, refineries, or logistics hubs

In these environments, drones are increasingly used for both security (live monitoring, threat detection) and inspection/mapping (infrastructure checks, thermal imaging, digital twin creation). However, for commercial operators, the regulatory requirements are more strict - especially for BVLOS operations.

To legally fly beyond visual line-of-sight in most European countries, commercial operators must:

• Operate within atypical airspace (e.g., close to structures or inside segregated areas)

• Obtain a SORA-based operational authorisation

• Implement compensating mitigations such as parachute systems, strategic deconfliction, or detect-and-avoid (DAA) capabilities

Without a harmonised DAA standard, BVLOS remains a significant hurdle for private security operators.

Airspace Awareness and Airspace Integration

To safely integrate security drones into shared airspace, operators increasingly combine DiaB platforms with drone detection systems or cooperative airspace tools. These help operators:

• Detect manned aircraft using ADS-B data

• Identify other drones in the vicinity using drone detection systems

• Establish clear airspace corridors using UTM/U-space and geofencing solutions

AirHub is actively integrating with platforms such as SafeSky and ground-based drone detection systems to enable full airspace situational awareness, helping operators avoid mid-air conflicts and meet key mitigation requirements under SORA.

Supporting Safe and Compliant Security Drone Operations

At AirHub, we support both public agencies and commercial operators with:

Consultancy Services

• End-to-end support in obtaining SORA authorisations, including:

  • Concept of Operations (ConOps)

  • SORA risk assessment

  • Operations Manual (OM) and Emergency Response Plans

• Strategic advice on airspace classification, mitigation selection, and U-space readiness

Software Solutions

• The AirHub Drone Operations Center (DOC) enables you to:

  • Monitor multiple DiaB systems remotely

  • Set up automated flight schedules or response triggers

  • View live video and telemetry streams

  • Integrate with C-UAS systems and airspace data sources

  • Maintain full audit trails for compliance and reporting

Our platform is ISO27001-certified, offers Secure Data Mode (blocking all outgoing data except to selected servers), and supports Single Sign-On (SSO) for enterprise-level access control - ensuring both data security and operational accountability.

Final Thoughts

Whether securing a national border or protecting a high-value industrial site, drones are proving to be a transformative asset in the security sector. But the shift from manual to autonomous operations - and from visual to BVLOS flights - requires a deep understanding of both the technology and the evolving regulatory framework.

At AirHub, we help organisations bridge this gap. With a strong combination of consulting expertise and scalable software solutions, we enable public and private stakeholders to unlock the full potential of drone security operations—safely, legally, and effectively.

Drone as First Responder (DFR) programs are transforming the way emergency services respond to incidents. What began as an experimental practice with pilots stationed on rooftops in the United States has now evolved into sophisticated, remotely operated networks using drone-in-a-box (DiaB) systems. This shift has not only improved response times but also reshaped how we approach the integration of unmanned systems into regulated airspace.

The Origin of DFR

The first DFR programs took shape in the U.S., where police departments began deploying drones from station rooftops or nearby locations to rapidly respond to 911 calls. These drones provided situational awareness before officers arrived on-scene, supporting safer and more efficient decision-making. These early deployments were still operated by pilots within visual line-of-sight (VLOS), typically stationed near the take-off location.

Scaling with Drone-in-a-Box Systems

As the technology matured, these programs expanded in scale and complexity. Drone-in-a-Box systems now enable fully remote operation, where a drone is housed in an automated docking station, ready to be dispatched within seconds. This opens up the ability to operate DFR programs 24/7 across multiple locations, even with limited personnel.

These systems are increasingly integrated with Computer-Aided Dispatch (CAD) systems, allowing drones to be automatically dispatched to incident locations as soon as an emergency call is registered. The result is a dramatic reduction in response time and enhanced situational awareness for first responders.

Regulatory Landscape: BVLOS and Atypical Airspace

The rise of DiaB systems introduces new regulatory challenges. Since the pilot is no longer physically co-located with the drone, these operations inherently fall under Beyond Visual Line-of-Sight (BVLOS) rules. BVLOS operations require significant additional mitigations due to the increased operational risk.

Europe: Atypical Airspace and Operational Mitigations

In Europe, regulators often allow DFR operations under SORA-based frameworks, particularly in Atypical Airspace. This means the operation is conducted in areas that are naturally shielded from other airspace users, such as:

• Close proximity to buildings or infrastructure

• Restricted or segregated airspace

• Controlled airspace with ATC coordination ensuring separation from manned aviation

Until a standard for Detect and Avoid (DAA) is fully defined, BVLOS operations are generally restricted to these kinds of environments. Additional mitigations include:

• Using dynamic population density data

• Integrating parachutes and FTS that comply with MoC 2512 and MoC 2511

• Rigorous remote pilot training and emergency procedures

• Technical validation of the operational volume (e.g. C2-link integrity, electromagnetic interference, etc.)

United States: Altitude-Based DAA Requirements

In the U.S., a similar pattern is emerging:

• BVLOS operations below 200 feet AGL often do not require DAA systems

• BVLOS operations up to 400 feet AGL typically require DAA capabilities

To meet these requirements, operators employ technologies such as:

• ADS-B receivers to detect manned air traffic

• Drone detection systems to identify nearby unmanned traffic

• Integration of DFR systems with UTM services and airspace awareness tools

Full Airspace Awareness: Combining Drone Enablement and C-UAS

To support BVLOS safety and compliance, many DFR programs are now combining Drone-in-a-Box technology with counter-UAS (C-UAS) systems. This allows for:

• Detection of non-cooperative drones

• Enhanced awareness of local air traffic

• Real-time deconfliction for safe mission execution

At AirHub, we are actively integrating our platform with systems such as SafeSky and various drone detection technologies to provide a full airspace picture for DFR operations.

Public vs. Commercial Operators: A Regulatory Divide

It's important to note that state operators (e.g. police departments) in the EU often benefit from more flexible regulatory conditions. In some member states, public safety agencies can conduct BVLOS operations in Class G airspace without DAA, provided they operate under state exemption rules.

On the other hand, commercial security companies are still required to operate in Atypical or segregated airspace and adhere strictly to SORA and EASA regulations. Until a harmonised DAA standard is introduced, this distinction is likely to remain.

How AirHub Supports DFR Operations

Whether you are a public agency or a commercial security provider, AirHub offers full-spectrum support for DFR programs:

Consultancy:

• SORA application and documentation (ConOps, OM, ERP, etc.)

• Strategy support and regulatory coordination

• Stakeholder engagement and training programs

Software:

• AirHub Drone Operations Center (DOC) for mission planning, real-time operations, and compliance

• Integration with drone detection and airspace awareness tools

• Risk assessment and checklist functionality

• Secure Data Mode, encrypted 4G service and SSO for privacy and access control

Final Thoughts

Drone as First Responder is no longer a future concept - it is a rapidly scaling reality. With the right technologies and regulatory strategies in place, DFR can drastically enhance public safety, security, and situational awareness. At AirHub, we are proud to support this evolution by delivering both the tools and expertise needed to make it work.

Interested in starting or scaling a DFR program? Contact our team to explore what is possible.

As drone operations evolve in complexity and scale, ensuring operational safety is no longer optional, it is a regulatory, operational, and moral imperative. One of the cornerstones of a mature drone operation, particularly within the specific category under the European Union’s SORA (Specific Operations Risk Assessment) framework, is the Emergency Response Plan (ERP). It ensures that operators are not only prepared to prevent incidents, but also fully equipped to respond effectively when emergencies occur.

In this article, we break down what an ERP is, how it fits into the SORA methodology, what has changed from version 2.0 to 2.5, and how both our consultancy and software can help you develop, manage, and maintain a compliant and effective ERP.

What Is an Emergency Response Plan (ERP)?

An Emergency Response Plan outlines the structured procedures to follow after an emergency occurs during a drone operation. It includes actions for:

• Communicating with local authorities and aviation stakeholders

• Containing hazards and limiting the spread of damage

• Recovering the aircraft or its remains

• Initiating post-incident analysis and reporting

• Coordinating with emergency services

It’s essential to distinguish this from contingency, abnormal, or emergency procedures in the Operations Manual. Those are designed to keep the operation safe during an incident, like loss of GPS or radio link. An ERP, by contrast, outlines the course of action after control is lost, a crash occurs, or a third-party is affected.

The Role of ERP in SORA 2.0

Under SORA 2.0, the ERP is listed as mitigation M3 during Step 3 (Final GRC Determination). When an ERP is properly designed, tested, and validated with high robustness, it can reduce the Ground Risk Class (GRC) by one level. This reduction can be crucial in making certain operations feasible, especially when operating close to or over people, property, or critical infrastructure.

However, the use of ERP as a risk reduction measure was optional, only implemented if the operator wished to reduce their GRC and was able to justify its effectiveness. This flexibility created varying levels of maturity in how ERPs were developed and implemented.

ERP in SORA 2.5: A Mandatory Operational Safety Objective

SORA 2.5, released in 2024 by JARUS, changes the game. ERP is no longer an optional mitigation but a required component of the Operational Safety Objectives (OSO #08). This reflects a growing recognition that emergency preparedness must be baked into every drone operation, regardless of its complexity or context.

This shift means that:

• All operators must now have an ERP, regardless of whether they seek to reduce their GRC.

• ERPs must meet predefined robustness levels aligned with their overall SAIL (Specific Assurance and Integrity Level).

• Authorities will assess ERP documentation and implementation more rigorously during the approval process.

This evolution strengthens the safety culture across the industry, ensuring that emergency management becomes a non-negotiable element of every UAS operator’s safety management system.

How Our Consultancy Team Can Help

Developing an ERP is not a checkbox exercise, it requires careful planning, operational insight, and alignment with the overall ConOps, SORA, and Operations Manual. Our consultancy team has helped dozens of organizations across Europe and beyond to:

• Draft complete and compliant Emergency Response Plans

• Define emergency roles and responsibilities within organizations

• Integrate ERP content into the ConOps and Operations Manual (OM Part B)

• Design ERP exercises and drills to validate effectiveness

• Prepare ERP documentation for CAA review

Beyond ERPs, we also support operators with:

• Authoring and validating full SORA packages (ConOps, GRC, ARC, OSOs)

• Developing Operations Manuals (OM Part A/B)

• Establishing and auditing Safety Management Systems (SMS)

• Supporting recurrent training and risk review procedures

Whether you’re seeking your first operational authorization or scaling a complex Drone-in-a-Box network, our team has the regulatory and operational experience to ensure you are fully prepared.

How the AirHub Platform Supports ERP Implementation

Our software platform is designed to ensure not just compliance at the time of authorization, but also operational safety on a day-to-day basis. You can upload and link your ERP directly to operational plans within the AirHub Drone Operations Center (DOC). This ensures that your ERP is always tied to the relevant mission and available to all stakeholders.

Within the platform, you can build custom checklists to trigger pre- and post-incident procedures. These checklists can include tasks like notifying ATC, contacting emergency services, or completing post-event reporting.

The AirHub DOC includes mapping tools that help visualize the operational environment, including:

• Location of emergency services (hospitals, fire brigades)

• ATC zones and frequencies

• Critical infrastructure and high-risk zones

This spatial awareness helps pilots and operational managers make informed decisions before and after incidents.

Final Thoughts

The importance of an Emergency Response Plan cannot be overstated. With the regulatory shift in SORA 2.5, ERPs are now a mandatory component of every medium- to high-risk operation. But even beyond compliance, a well-crafted ERP demonstrates professionalism, preparedness, and a deep commitment to safety.

At AirHub, we help drone operators - from government agencies to security companies and critical infrastructure providers - embed ERP into their safety culture through both expert consultancy and purpose-built software.

If you want to review or upgrade your current ERP, are preparing a new SORA package or create an optimal workflow within our software platform our team is here to help. Reach out to us to ensure your next operation is safe, compliant, and resilient.