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.