The SORA 2.5 Drone represents the modern risk assessment methodology for complex UAS operations in the Special Category.
Drones are now used in far more applications than just aerial photography, as was the case in the past. Network inspections, photogrammetry, thermography, surveillance, agricultural applications, and BVLOS flights are just a few examples. However, as a drone’s operational capabilities increase, so do the requirements for conducting a flight safely.
When a transaction cannot be carried out in accordance with the restrictions of the Open Category or is not covered by an available Standard Scenario (STS) or other appropriate predefined procedure, operational approval under the Specific Category may be required.In these cases, one of the key assessment tools is SORA—Specific Operations Risk Assessment.SORA is a structured risk assessment methodology that helps both the UAS operator and the competent authority determine whether, and under what conditions, a specific operation can bebe carried out with an acceptable level of safety.
What exactly is SORA?
A common mistake is to think of SORA as just another “operator’s license.”
IT IS NOT.
SORA primarily concerns the company—or the drone owner—that wishes to become a UAS operator. Simply put, the logic is: What do I want to do → Where do I want to do it → With which drone → What risks are involved → How will I mitigate them → How do I demonstrate that the operation can be carried out safely.
When might SORA be needed?
A SORA may involve operations such as BVLOS (Beyond Visual Line of Sight) flights, aerial spraying, complex industrial inspections, long-distance operations, operations in high-risk environments on the ground or in the air, and, more generally, activities that cannot be carried out under the Open Category or an appropriate STS/PDRA.
However, before anyone begins the process of a full SORA, they must first consider whether the specific project can be carried out under a simpler regulatory framework. The methodology itself is designed precisely to ensure that SORA is not applied unnecessarily.
SORA 2.5: The Step-by-Step Process
The process begins with a detailed description of the operation. It is not enough to simply state, “I want to conduct a BVLOS flight.” You must describe in detail the operational environment, the area, altitude, distances, the UAS, personnel, procedures, communication systems, potential emergency situations, and the operation’s limitations.This operational description forms the basis upon which the entire assessment is built.
- Description of the business – ConOpsThe Concept of Operations (ConOps) It clearly describes exactly what is going to happen. It includes, among other things, the UAS to be used, the operational environment, the personnel, the mission execution plan, the airspace, the Command & Control systems, and the normal, contingency, and emergency procedures. Proper ConOps are fundamental. If the operation changes substantially, the risk assessment may also change.
- Risk Assessment on the Ground.
Next, the risk that the drone may pose to people on the ground is assessed. The process determines the Ground Risk Class (GRC) by taking into account factors such as the characteristics of the UAS, the operational environment, population density, and the areas that could be affected in the event of a loss of control. In SORA 2.5, the documentation includes specific details regarding flight geography, contingency volume, ground risk buffer, and related dimensions. Where required, appropriate risk mitigation measures are implemented.
- Risk Assessment in the Air.
The next major section concerns the risk of collision with other aircraft. It examines the category and characteristics of the airspace, expected air traffic, the operator’s location, which drone is being flown, and the available means of avoiding or mitigating the risk. This process determines the corresponding Air Risk Class (ARC), and, where necessary, strategic or tactical measures are implemented to address the air risk.
- Definition of SAIL
The overall assessment determines the required SAIL—Specific Assurance and Integrity Level. The SAIL essentially determines how rigorous the security evidence required for that particular operation must be. The logic is simple: the greater the risk, the stronger the documentation must be to demonstrate that this risk is under control. Operational approvals can range from SAIL I to SAIL VI.
- Operational Safety Objectives – OSOs
Depending on the outcome of the assessment, the Operational Safety Objectives (OSOs) that must be met are identified. At this point, we no longer examine just the drone. We examine the entire operational system: the reliability of the UAS, the training and competence of personnel, personnel licensing, operational procedures, maintenance, communication systems, emergency procedures, and, more generally, the measures required to ensure that the operation is conducted at the expected level of safety.
- The Operations Manual.
Another important part of the process is the Operations Manual (OM). The Operations Manual should not be a general document that simply sits in the company’s file. It must describe how the UAS operator actually operates: responsibilities, personnel, flight procedures, mission preparation, contingency procedures, emergency procedures, training, maintenance, reporting, and the procedures associated with the approved operation. The submission requirements and level of documentation also depend on the operation’s category/SAIL. Each company is required to provide the Operations Manual to its staff so they can read it and ensure everyone is informed about the procedures.
SORA, ConOps, and the Operations Manual must “speak the same language”
This is perhaps the most important part of the entire process.
We cannot describe one mode of operation in the ConOps, evaluate a different one in the SORA, and specify yet another in the Operations Manual. These documents constitute a unified documentation system.
The procedures, the technical characteristics of the UAS, the restrictions, the responsibilities of personnel, and the risk mitigation measures must be consistent with one another.
What is submitted to the Civil Aviation Authority?
The application package for an operational authorization in the Specific Category may include, as applicable, the application, a description of the operation, the SORA and related appendices, the Operations Manual, UAS specifications, maps and geographic data, emergency procedures, contact numbers, and the necessary evidence of compliance. EASA now also has specific guidelines on how to collect and present the information accompanying an application for an operating authorization. The competent authority reviews the documentation and may request clarifications, amendments, or additional information before granting the operational approval, and the implementation period may exceed 8 months.
SORA 2.5
The new June 2026 version incorporates SORA 2.5 and is now the most recent version of the methodology that has been incorporated into the European regulatory framework through the AMCs/GMs, and states that the new version aims to simplify the process while maintaining a high level of safety and strengthening the harmonized implementation of the regulation across Europe. This is particularly important for businesses that want to use drones professionally for more demanding missions. SORA is not just a “piece of paper.” SORA is not created simply to be submitted to the Authority. It outlines how an actual drone operation will be conducted safely. And once approved, the UAS operator is responsible for ensuring that every flight is conducted in accordance with the mitigation measures, safety objectives, and restrictions included in the approved assessment and operational authorization.
The role of Patras Drone Academy.
The transition from simply training an operator to establishing a fully-fledged professional UAS business requires knowledge of both flight operations and the European regulatory framework. Patras Drone Academy supports professionals and companies through the Special Category process, from the initial assessment of the business to the development of the ConOps, the SORA, and the Operations Manual, as well as the preparation of the application package required for submission to the competent Civil Aviation Authority. The goal is not merely to create documents; the goal is a drone operation that can function in practice—safely, with proper documentation, and in accordance with the current European regulatory framework.
