Embention Autopilots for Loitering Munitions & C-UAS: The New Standard for One-Way Drones
The aerospace industry is witnessing a shift in the loitering munitions and C-UAS with the emergence of new autopilot systems from Embention
The European UAS industry has entered a new regulatory era with the full implementation of the SORA 2.5 methodology. The Spanish State Aviation Safety Agency (AESA) recently hosted a divulgative day to outline these critical updates, which Embention attended to gain firsthand insight into the new framework. Based on the technical details presented during this session, this article summarizes the fundamental shifts in risk assessment that program managers and UAS manufacturers must now navigate to secure operational authorizations under the new EASA standards.
The shift to quantitative ground risk assessment (Annex F)
The most profound technical evolution in SORA 2.5 is the transition from a qualitative to a quantitative determination of the Intrinsic Ground Risk Class (iGRC). The previous reliance on broad estimations has been replaced by a data-driven model anchored in Annex F. Operators must now calculate the iGRC using precise mathematical formulas that account for the Critical Area of the unmanned aircraft, calculated based on maximum dimension and kinetic energy, and the specific population density (people/km²) of the flight volume.
This granularity offers a significant advantage for precision engineering. Operators using advanced systems can leverage verified technical data to demonstrate a reduced Critical Area, potentially lowering the iGRC. Notably, a proportionality principle has been introduced where UAS <250 g with a maximum cruise speed of < 25m/s (resulting in very low kinetic energy) are automatically classified as iGRC 1. However, for larger, complex UAS, the focus shifts to the rigorous proof of Integrity and Assurance required to validate these quantitative safety claims against the new standard.
Process optimization: the 10-step flow and “Description of the ConOps”
The SORA architecture has been rationalized from 11 steps down to 10 steps, creating a more logical safety case progression. Step 1 is now formally defined as the “Description of the ConOps”, but with a stricter requirement for Detailed Operational Information supported by the standardized templates in Annex A. This change forces operators to define specific technical parameters, such as the Operational Volume and Ground Risk Buffer, reducing the administrative iteration often experienced with authorities like AESA.
The sequence of assessment has also been strategically reordered to prioritize containment. Containment Requirements are now evaluated in Step 8, explicitly preceding the definition of Operational Safety Objectives (OSOs) in Step 9. This ensures that the risk of the UAS leaving the Operational Volume and infringing on the Adjacent Area is addressed before final safety objectives are set. Furthermore, the entire SORA process is now explicitly divided into two phases: Phase 1 (Risk Assessment) and Phase 2 (Safety Case), allowing operators to validate their Specific Assurance and Integrity Level (SAIL) with the regulator before investing in the full comprehensive safety portfolio.
Overhaul of mitigations and the ERP paradigm shift
SORA 2.5 introduces a stricter, more structured approach to Strategic Mitigations for Ground Risk (M1), splitting them into three distinct categories to eliminate ambiguity:
- M1A (Sheltering): Reducing risk by flying over persons inside structures or protected vehicles.
- M1B (Operational Restrictions): Reducing risk by limiting the operational volume to a controlled ground area.
- M1C (Ground Observation): Using visual observers to clear the area (replacing the previous VLOS intrinsic credit).
Perhaps the most critical compliance change is the removal of the Emergency Response Plan (ERP) as a standalone M3 mitigation credit. In SORA 2.5, the ERP is no longer a tool to lower the final GRC; instead, it has been integrated directly into the OSOs (specifically referenced in OSO #01) as a mandatory requirement. This means a validated, effective ERP is now a non-negotiable prerequisite for every operation, regardless of the SAIL. This elevates the importance of reliable Flight Termination Systems (FTS) and means of crashworthiness, which must be seamlessly integrated with the flight control system to meet the new OSO standards.
The implementation of SORA 2.5 by AESA and other EASA member states raises the bar for technical compliance, favoring professional operators and manufacturers who can provide verifiable reliability data. In this data-centric regulatory environment, the role of certified, high-integrity avionics becomes the cornerstone of a successful authorization. Embention remains committed to supporting this transition, developing the Veronte Autopilot ecosystem to provide the precise telemetry, containment capabilities, and failure management evidence required to satisfy the stringent demands of SORA 2.5 for complex UAS missions.
