SORA v2.5 for Heavy Lift Logistics Drones: a Manufacturer's Guide

By Anne-Lise Scaillierez, The Drone Office.

Introduction

Drone delivery of small packages — particularly in healthcare for blood samples or urgent medical supplies — has been explored for several years. Those operations face their own challenges: high ground risk from urban environments and BVLOS flight, albeit typically within controlled airspace over cities. Their saving grace is small size, usually below 25 kg.

A new segment is now growing in significance: logistics by heavy lift drones, which raises very different regulatory challenges. Uncrewed platforms are increasingly attractive for logistics applications in dual-use environments — last-mile resupply to forward positions, medical materiel delivery, evacuation of casualties in search and rescue operations, or resupply in semi-permissive environments. Their vertical take-off and landing (VTOL) heavy lift drone capability, mechanical simplicity, and relatively low unit cost make them compelling where fixed-wing logistics crewed aircraft or drones are operationally impractical.

Manufacturers building platforms for this mission set face a specific set of regulatory challenges. The moment a dual-use or commercially-derived UAV enters civil airspace — for trials, type validation, export demonstration, or operator training — it falls squarely within the scope of the UK CAA and EASA's Specific Operations Risk Assessment (SORA) framework, now at version 2.5.

This article walks through the key SORA considerations specific to heavy lift drone regulation. the large logistics multi-rotor mission profile and explores what manufacturers need to think about at the design and documentation stage in terms of SORA drone certification or review — not just at the point of authorisation.

Why Large Logistics Drones face High SORA Ground Risk Class

Large logistics drones have several characteristics that make them a challenging SORA case from the outset.

Large size and speed place them in the higher ground risk categories within SORA.

Under SORA, the intrinsic Ground Risk Class (iGRC) is a score from 1 to 10, based on two factors:

• The size and operational speed of the drone — represented across the five columns of the iGRC table. Larger, faster drones pose a higher impact risk.

• The maximum population density within the ground risk footprint — represented across the seven rows. Higher population density means more people at risk.

Not all logistics multi-rotor drones are designed identically, but it is fair to say that their maximum characteristic dimension — measured from blade tip to blade tip — can exceed 3 m. This places them in the third column of the iGRC table, even if their operational speed is below 35 m/s, resulting in an elevated iGRC.

Where a platform's characteristics sit on the lower end of its official column, running the SORA risk model using its specific characteristics may demonstrate that the iGRC is one step lower than the column would initially suggest.

Large size and speed also place them in the medium robustness containment category.

What happens if the drone experiences a fly-away — a loss of control event that takes it beyond the ground risk buffer into the adjacent area? Containment requirements address exactly that risk. They are a set of technical functionalities and procedures designed to mitigate the risk of a fly-away.

Containment robustness — low, medium, or high — is determined by three factors:

• the drone's characteristic dimension and maximum design speed (using the same five-column structure as the iGRC table)

• the population density of the adjacent area

• the SAIL level.

The adjacent area may be larger than you expect.

Under SORA 2.5, the lateral outer limit of the adjacent area is calculated as the distance the drone would travel in three minutes at its maximum speed. Where that calculated distance is less than 5 km, a minimum of 5 km applies; where it falls between 5 km and 35 km, the calculated distance is used; and where it exceeds 35 km, 35 km is the upper limit. For a logistics drone with a maximum speed of 20 m/s (72 km/h), this produces an adjacent area extending roughly 3.6 km from the operational volume boundary — which defaults to the 5 km minimum. A faster platform at 30 m/s produces a 5.4 km adjacent area, which is used as calculated. The point is that even when testing and evaluating your platform at a seemingly remote site, the adjacent area extends well beyond what feels intuitively like your operating footprint. Containment at medium robustness may be triggered even in locations that appear rural, if population density in that outer ring meets the relevant threshold in the containment table.

Europe is a densely populated continent, and manufacturers should not assume that a trial site that appears remote will automatically fall below the relevant density threshold in its adjacent area.

BVLOS is the intended end-state, even if trials begin under VLOS.

You may conduct initial testing under visual line of sight (VLOS), but customers will want to test and train in real-life operational conditions, which means BVLOS SORA authorisation. Platforms must be designed to be BVLOS-ready, and manufacturers should anticipate demonstrating BVLOS safety cases as part of the authorisation pathway even when early trials take place within VLOS.

Autonomous or highly automated operation affects OSO compliance.

Tactical logistics platforms often operate with minimal remote pilot intervention, relying on pre-programmed routes, automated collision avoidance, and autonomous abort procedures. This affects how Operational Safety Objectives (OSOs) related to human oversight are assessed — particularly those covering human error management, flight envelope protection, and safe recovery from control anomalies.

Multiple System Operations (MSO) introduce additional regulatory complexity.

Looking further ahead, it is reasonable to expect that logistics drones will be operated as a fleet, in the same way a logistics company manages a fleet of vehicles. This breaks the conventional one-remote-pilot-to-one-UAS relationship and triggers a developing set of regulatory requirements affecting ground station design, command and control (C2) link architecture, and onboard automation, each with associated robustness expectations.

Variable and often controlled airspace.

Logistics corridors may cross controlled airspace, transport routes, or urban peripheries. Unlike ISR platforms that can be routed around population centres, logistics drones must reach a specific destination.

BVLOS operations are currently conducted within segregated airspace, but platforms must be designed to be BVLOS-ready to the maximum extent, and manufacturers should plan for testing their equipment while safely operating within a segregated environment.

Keep the SAIL as Low as Possible

Each of the characteristics above pushes a large logistics platform and its operations toward a higher SAIL — the Specific Assurance and Integrity Level that determines the required robustness of safety evidence across the SORA framework.

A higher SAIL has direct cost and commercial implications:

·       it increases the engineering and documentation burden on the manufacturer

·       it imposes compliance obligations on the operator.

Customers operating at SAIL III, for example, must themselves demonstrate SAIL III-level organisational competency. Helping your customer achieve a lower SAIL — through design features that support mitigations — is a genuine competitive differentiator.

Design Implications for Manufacturers

The most important insight from SORA for large logistics multi-rotor manufacturers is that the framework rewards design decisions made early. Platforms built with SORA compliance in mind are dramatically easier to assess than those for which documentation is assembled retrospectively.

Redundant C2 links 

A platform with dual-band or satellite-supplemented command links can demonstrate a more robust response to link degradation, directly supporting the OSOs related to C2 link performance and safe recovery from technical issues.

Flight termination reliability

An independently powered flight termination system — separate from the main flight controller — provides the strongest evidence for containment criterion 4. This is worth designing into the platform architecture from the outset.

Geofencing at software and/or hardware level 

Software-only geofencing is generally treated as medium robustness in SORA assessments. Hardware-enforced geofencing, using an independent processor that verifies position against stored boundary data and can command flight termination independently of the main flight computer, supports a higher robustness claim and strengthens the containment argument.

Documented failure mode analysis.

A structured Failure Mode and Effects Analysis (FMEA), completed during development, forms the evidentiary backbone of multiple OSO compliance arguments. Manufacturers who produce this as part of their standard engineering process — rather than as a retrospective exercise for certification purposes — will save significant time and cost at the authorisation stage.

User manual and Human-Machine Interface documentation 

Even at SAIL II, the documentation requirements for end-user benefit are often poorly addressed by commercial-off-the-shelf UAS products, particularly elements covering the HMI design and how it is intended to minimise the risk of human error. Addressing this explicitly, and documenting it clearly, reduces friction in the OSO compliance review.

Conclusion: Start Earlier Than You Think

SORA is not a process that can be bolted on at the end of a development programme. For large logistics platforms, the evidential requirements across the OSOs and containment requirements CORs represent a substantial engineering and documentation effort — one that is far better planned for than discovered at the point of authorisation application.

If you are developing a multi-rotor logistics platform and want to understand where your current design sits against SORA requirements — or want to plan a compliance roadmap from initial ConOps through to operational authorisation — get in touch.

Regulatory frameworks are subject to ongoing revision. Always verify current requirements with the relevant competent authority.

Certo Aerospace Heavy Lift Rotorcraft