SORA 2.5 Explained: The Complete Guide to EU Drone Risk Assessment in 2026

MidronePro Academy | Drone Laws & Safety | Updated September 2026

SORA 2.5 is one of the most important developments in European drone regulation for professional and advanced UAS operators in 2026. The latest version of the Specific Operations Risk Assessment methodology is designed to provide a more consistent, proportionate and harmonised way of assessing higher-risk drone operations in the European Union.

For operators working in the specific category, SORA 2.5 can determine what risks must be addressed, what mitigations are required, what safety objectives apply and what evidence may need to be provided to the competent authority.

But SORA 2.5 is often misunderstood.

It is not a drone licence, it is not a replacement for the EU drone regulations, and it does not mean that every professional drone flight requires a full SORA.

Instead, SORA is a risk-assessment methodology used to support applications for operations that fall within the specific category and are not already covered by an applicable Standard Scenario (STS), Predefined Risk Assessment (PDRA), or another available regulatory pathway.

In this guide, MidronePro explains SORA 2.5 in practical terms, including the risk-assessment process, GRC, ARC, SAIL, mitigations, containment, BVLOS operations, documentation, Spain-specific considerations and what drone operators should know in 2026.

What Is SORA 2.5?

SORA stands for Specific Operations Risk Assessment.

It is a structured methodology for assessing the safety risks associated with a particular UAS operation in the specific category.

The methodology was developed by the Joint Authorities for Rulemaking on Unmanned Systems (JARUS) and adapted by EASA for application within the European regulatory framework.

EASA incorporated the latest SORA 2.5 package into the European regulatory framework through ED Decision 2025/018/R. The June 2026 revision of EASA's Easy Access Rules for Unmanned Aircraft Systems incorporates this latest SORA 2.5 material.

The fundamental idea is straightforward:

The greater the risk created by a drone operation, the greater the level of safety evidence and mitigation that should be demonstrated.

Instead of treating every operation in the same way, SORA attempts to establish a proportionate relationship between:

• The characteristics of the operation
• The environment in which it will take place
• The people and aircraft potentially exposed to the operation
• The drone and its technical capabilities
• The proposed safety mitigations
• The evidence supporting those mitigations
• The required level of operational assurance

This risk-based philosophy is one of the central principles behind the European specific category.

For the broader regulatory framework, see the MidronePro Drone Laws & Safety Guide.

Why Was SORA 2.5 Introduced?

SORA 2.5 was introduced to make the authorization process for specific-category UAS operations more practical and consistent while maintaining an appropriate level of safety.

EASA identifies several important objectives behind the update:

• Clarifying the methodology and terminology
• Reducing room for different interpretations
• Improving harmonisation between Member States
• Reducing unnecessary evidence requirements for certain lower-risk operations
• Simplifying aspects of containment
• Maintaining a high level of safety

One particularly important change highlighted by EASA is the reduction in evidence required for most Visual Line of Sight (VLOS) operations classified as SAIL II.

This does not mean that SAIL II operations become automatically authorised.

It means that the methodology can require a more proportionate level of evidence where the assessed risk does not justify the same burden associated with more demanding operations.

For operators, that distinction is extremely important.

Who Uses SORA 2.5?

SORA 2.5 is primarily relevant to operators planning UAS operations in the specific category where a risk assessment is required.

Typical examples can include operations involving:

• BVLOS flight
• Operations with increased ground risk
• Operations in more complex airspace
• Professional inspections
• Infrastructure monitoring
• Industrial operations
• Large-scale surveying
• Some agricultural operations
• Specialised logistics operations
• Other operations outside the conditions of the open category

However, not every operation in the specific category necessarily requires an operator to start from a completely blank SORA.

Some operations may be covered by an applicable Standard Scenario or Predefined Risk Assessment.

That is why the first step should always be identifying the regulatory pathway that applies to the planned operation.

SORA 2.5 vs the Open Category

One of the easiest ways to understand SORA is to compare it with the European open category.

The important principle is that SORA does not simply mean "commercial drone licence."

The European system is based primarily on the risk and characteristics of the operation rather than simply whether money is being made.

For example, a professional photographer may be able to conduct a low-risk operation in the open category if all applicable conditions are satisfied.

A highly complex commercial operation may instead require a specific-category authorization.

See our Drone Laws in Spain 2026 guide for the national context.

When Is SORA Required?

EASA explains that when an operation is not covered by a Standard Scenario or PDRA, applicants are required to conduct a risk assessment, identify appropriate mitigations and comply with the applicable safety objectives.

SORA provides the methodology used for this purpose.

This creates an important decision point for an operator:

Step 1: Determine whether the operation fits the open category

If it does, SORA is normally unnecessary.

Step 2: Check whether an applicable Standard Scenario exists

If the operation fits an STS, the relevant regulatory pathway may be substantially simpler than creating a bespoke SORA.

Step 3: Check applicable PDRAs

A Predefined Risk Assessment can provide an established pathway for certain types of operations.

Step 4: If no predefined pathway applies, assess whether SORA is appropriate

This is where a tailored risk assessment may become necessary.

The exact regulatory pathway should always be confirmed with the competent authority responsible for the operation.

How SORA 2.5 Works

SORA 2.5 follows a structured sequence that progressively evaluates the risk of the proposed operation.

The simplified logic is:

1. Describe the operation
2. Determine the initial Ground Risk Class
3. Determine the final Ground Risk Class
4. Determine the initial Air Risk Class
5. Determine the residual Air Risk Class
6. Apply tactical mitigations where required
7. Determine the SAIL level
8. Determine containment requirements
9. Determine Operational Safety Objectives
10. Compile the comprehensive safety portfolio

This sequence is important because the SORA outcome is not simply a single "risk score."

It produces a structured safety case describing how the operator intends to conduct the operation safely.

Step 1: Describe the Operation

The first stage is defining exactly what the operator intends to do.

This is sometimes referred to through the concept of the ConOps, or Concept of Operations, although SORA 2.5's structure places the operation description at the beginning of the process.

The description should establish the characteristics of the planned flight, including factors such as:

• Where the operation will occur
• How high the aircraft will fly
• How far it will travel
• Whether the operation is VLOS or BVLOS
• The type of UAS being used
• The operating environment
• The people potentially exposed
• The surrounding airspace
• The operational volume
• Normal and contingency procedures
• Relevant limitations

A weak operation description creates problems later because every subsequent risk assessment depends on understanding the operation accurately.

A good SORA therefore starts with a precise operational concept rather than jumping immediately into technical documentation.

Step 2: Determine the Initial Ground Risk Class

The initial Ground Risk Class (iGRC) evaluates the inherent ground risk associated with the operation before specific mitigations are credited.

In simple terms:

What could happen to people on the ground if the UAS loses control?

The assessment considers factors such as:

• Population exposure
• Operational area
• Aircraft characteristics
• Potential impact consequences
• Operational limitations

SORA 2.5 uses a structured approach to establish the initial ground-risk classification.

Population density is therefore an important part of many SORA assessments.

The objective is not simply to determine whether people are present.

The methodology attempts to quantify and classify the level of exposure associated with the operation.

Step 3: Determine the Final Ground Risk Class

Once the initial ground risk is established, the operator can identify appropriate ground-risk mitigations.

Examples can include measures intended to:

• Reduce the probability of people being exposed
• Reduce the size of the operational area
• Control access to the area
• Improve emergency procedures
• Limit operations to suitable locations
• Reduce the consequences of a loss of control

The quality of a mitigation matters.

SORA distinguishes between the integrity of a mitigation—how effective it is expected to be—and its assurance—how convincingly the operator can demonstrate that it is implemented and effective.

This is why simply writing "we will keep people away" is not necessarily sufficient evidence.

The operator must be able to demonstrate how the mitigation is actually implemented.

Ground Risk Mitigations in SORA 2.5

Operational planning and controlled flight areas can be important elements of a professional UAS safety case.

Image source: Wikimedia Commons. U.S. Forest Service / UAS operation imagery.

SORA does not simply ask whether a mitigation exists.

It asks whether the mitigation provides an appropriate safety benefit and whether the operator can demonstrate the required level of integrity and assurance.

This makes documentation extremely important.

An operator should therefore think about safety measures before preparing the final application rather than treating documentation as an administrative task at the end.

Step 4: Determine the Initial Air Risk Class

The Air Risk Class (ARC) concerns the risk of encountering other aircraft.

In simple terms:

How likely is the UAS to encounter a manned aircraft within the operational environment?

The assessment considers the airspace and operating environment in which the drone will fly.

SORA distinguishes between the initial ARC and the residual ARC.

The initial ARC represents the generalised air-collision risk associated with the operational volume before relevant strategic mitigations are considered.

The residual ARC represents the risk after those mitigations have been applied.

This is especially important for operations involving:

• Controlled airspace
• Busy aviation environments
• BVLOS operations
• Operations near airports
• Operations crossing different airspace environments
• Operations requiring structured conflict mitigation

Strategic and Tactical Air-Risk Mitigations

SORA separates different types of risk reduction.

Strategic Mitigation

Strategic mitigations reduce the likelihood of encountering other aircraft before the drone takes off.

Examples can involve:

• Operational restrictions
• Time restrictions
• Geographical restrictions
• Airspace coordination
• Other measures that reduce exposure to aircraft traffic

Tactical Mitigation

Tactical mitigations address the risk during the operation itself.

Depending on the operation, these can involve procedures or technical means designed to detect and respond to potential conflicts.

The exact mitigation requirements depend on the resulting risk assessment and applicable safety objectives.

Step 5: Tactical Mitigation Performance Requirement

Where tactical mitigations are required, SORA establishes the appropriate Tactical Mitigation Performance Requirement (TMPR).

The purpose is to determine the level of performance needed from the mitigation to reduce the remaining air risk to an acceptable level.

This is particularly relevant to advanced operations where simply maintaining visual observation is not enough to manage the airspace risk.

For operators developing BVLOS missions, this stage can become technically significant.

Step 6: Understanding SAIL

One of the most important SORA concepts is SAIL.

SAIL stands for Specific Assurance and Integrity Level.

SORA uses SAIL to connect the assessed risk of an operation with the level of assurance and integrity that must be demonstrated.

There are six SAIL levels:

The SAIL level should not be interpreted as a simple ranking of how "dangerous" a drone is.

It represents the level of assurance and integrity required to demonstrate that the proposed operation can meet the applicable safety objectives.

This distinction is essential when reading SORA documentation.

Why SAIL II Matters in SORA 2.5

SAIL II is particularly relevant because EASA has highlighted a reduction in evidence requirements for most low-risk VLOS operations classified as SAIL II.

This is one of the areas where SORA 2.5 can make the authorization process more proportionate.

However, operators should not assume:

"SAIL II means no safety evidence."

The correct interpretation is that the evidence burden can be reduced where the methodology and applicable conditions allow it.

The operator still needs to demonstrate compliance with the applicable safety objectives.

Step 7: Containment in SORA 2.5

Containment is another important component of SORA 2.5.

The basic idea is that the UAS should remain within the defined operational volume and that appropriate measures should exist to prevent or manage unintended excursions.

SORA 2.5 changes the structure of containment compared with earlier versions.

EASA's SORA material places containment at Step 8, after determining the SAIL level and before the Operational Safety Objectives.

EASA has also highlighted that SORA 2.5 relaxes certain requirements associated with containment within the operational volume.

This is particularly relevant for operators whose previous SORA preparation involved extensive containment documentation.

Nevertheless, containment remains an important part of the overall safety case.

Step 8: Operational Safety Objectives

The Operational Safety Objectives (OSOs) describe the safety objectives that must be addressed by the operator.

They can relate to areas including:

• Organisation
• Operational procedures
• Remote pilot competence
• Technical systems
• Maintenance
• UAS reliability
• Operational control
• Emergency procedures
• Human factors
• Safety management

The required integrity and assurance level depends on the SORA outcome.

EASA's guidance explains that Annex E provides criteria for assessing the integrity and assurance of the OSOs proposed by an applicant.

This is where the safety case becomes more than a description of the flight.

The operator must demonstrate that the organisation, people, procedures and technical systems collectively provide the required level of safety.

Step 9: The Comprehensive Safety Portfolio

The final stage is assembling the evidence into a comprehensive safety portfolio.

This is effectively the structured package demonstrating how the operator intends to meet the safety requirements identified through the SORA.

Depending on the operation, documentation can include:

• Operational description
• Risk assessment
• Ground-risk mitigations
• Air-risk mitigations
• Containment strategy
• Operational procedures
• Emergency procedures
• Remote pilot competence evidence
• Maintenance procedures
• UAS technical information
• Safety management documentation
• Evidence supporting applicable OSOs
• Other material required by the competent authority

The precise evidence package depends on the operation and resulting SORA requirements.

EASA provides templates and forms to help operators collect and present the necessary information for specific-category applications.

SORA 2.5 and BVLOS Drone Operations

BVLOS operations illustrate why operation-specific risk assessment becomes increasingly important as drone missions become more complex.

Image source: Wikimedia Commons, CC BY-SA 4.0. Photographer: Nambi2015.

Beyond Visual Line of Sight (BVLOS) is one of the areas where SORA becomes particularly important.

Once a pilot cannot continuously maintain the required visual awareness of the aircraft, the operational environment and airspace risks can become considerably more complex.

Examples of advanced BVLOS missions include:

• Long-range infrastructure inspection
• Pipeline monitoring
• Power-line inspection
• Large-area surveying
• Medical delivery
• Industrial logistics
• Remote surveillance
• Maritime operations

SORA provides a structured way to assess those risks rather than relying on a simple distance limit.

For a pilot planning a BVLOS mission, however, SORA should be regarded as part of a wider regulatory and operational framework rather than as the only requirement.

SORA 2.5 and Population Density

Population density is especially important when calculating ground risk.

The reason is intuitive:

A drone operating over a remote area presents a different potential ground exposure from an aircraft operating over a dense urban environment.

SORA 2.5 introduces a more quantitative approach to determining the initial Ground Risk Class, which makes reliable population-density information an important component of the assessment.

Operators should therefore use appropriate and defensible geographical data when preparing a SORA.

The data should correspond to the operational area and should be presented in a way that allows the competent authority to understand how the ground-risk classification was determined.

SORA 2.5 vs PDRA

A PDRA can be much easier when your operation fits its predefined conditions.

If your operation falls outside those conditions, however, a SORA-based application may be the appropriate route.

Operators should always check the current EASA and national material before deciding which pathway applies.

SORA 2.5 vs Standard Scenarios

Standard Scenarios (STS) are another important part of the European system.

An STS describes a predefined type of UAS operation for which the relevant risk assessment and mitigations have already been established.

This can significantly simplify the regulatory process when an operation fits the scenario.

The practical rule is:

Before starting a bespoke SORA, check whether an STS or PDRA already covers your operation.

Doing this can save substantial time and reduce unnecessary documentation.

How Much Documentation Does SORA 2.5 Require?

There is no universal page count or fixed documentation package that applies to every SORA.

The amount of evidence depends on the characteristics and risk of the proposed operation.

A relatively straightforward operation can therefore require considerably less evidence than a complex BVLOS operation involving populated areas and complicated airspace.

This is exactly what the risk-based philosophy is designed to achieve.

Higher-risk operations should justify a higher level of assurance.

Lower-risk operations should not automatically face the same burden.

How to Prepare a SORA 2.5 Application

1. Define the operation precisely

Do not begin with generic statements such as "commercial drone inspection."

Define the aircraft, location, altitude, operating volume, flight path, VLOS/BVLOS conditions, people exposure and operational procedures.

2. Check STS and PDRA options first

Determine whether an existing predefined pathway can cover the mission.

3. Map the operational environment

Collect reliable information about terrain, population, airspace, airports, obstacles and relevant geographical zones.

4. Calculate ground risk

Determine the initial and final Ground Risk Class and document the mitigations being credited.

5. Assess air risk

Determine the applicable Air Risk Class and identify the appropriate strategic and tactical mitigations.

6. Determine the SAIL

Use the SORA methodology to determine the required assurance and integrity level.

7. Address containment

Demonstrate how the aircraft will remain within the required operational volume.

8. Address the OSOs

Build evidence showing that the operator, personnel, procedures and UAS meet the applicable safety objectives.

9. Build the safety portfolio

Compile the complete application package in a logical and traceable structure.

10. Review the application before submission

Make sure every mitigation, assumption and safety objective is supported by evidence.

Common SORA 2.5 Mistakes

Mistake 1: Starting with the drone instead of the operation

SORA assesses an operation, not simply a drone model.

Mistake 2: Assuming a powerful drone automatically produces a lower risk

A sophisticated aircraft does not automatically eliminate operational risk.

Mistake 3: Ignoring population exposure

Ground risk depends heavily on who and what is exposed beneath the operation.

Mistake 4: Treating SORA as a checklist

A SORA should form a coherent safety argument rather than become a collection of disconnected documents.

Mistake 5: Using unsupported assumptions

Statements about population, airspace, aircraft performance or mitigation effectiveness should be supported by credible evidence.

Mistake 6: Forgetting national requirements

EASA provides the European framework, but operators still need to consider the competent authority and applicable national requirements.

Mistake 7: Assuming SORA means automatic approval

SORA supports an authorization application. It does not guarantee that the competent authority will approve the operation.

SORA 2.5 for Commercial Drone Operators

SORA 2.5 is particularly significant for the growing professional drone industry.

Commercial UAS operations are increasingly moving beyond simple aerial photography.

Modern drone missions can involve:

• Infrastructure inspection
• Energy infrastructure
• Railway inspection
• Construction monitoring
• Mining
• Agriculture
• Surveying
• Logistics
• Emergency response
• Environmental monitoring

Many of these applications can require operational conditions that go beyond the open category.

SORA provides a common framework for demonstrating how these operations can be conducted safely.

For companies building a professional UAS operation, understanding SORA can therefore become an important part of long-term regulatory planning.

SORA 2.5 in Spain

For Spanish operators, SORA exists within the wider European UAS regulatory framework and is implemented through the applicable Spanish competent-authority processes.

Spain's national aviation authority is AESA — Agencia Estatal de Seguridad Aérea.

A Spanish operator planning a specific-category operation should therefore consider:

• The EU UAS regulatory framework
• The SORA 2.5 methodology
• Applicable AESA procedures
• Spanish geographical zones
• Applicable airspace restrictions
• Remote-pilot competency requirements
• Operational procedures
• Applicable insurance and national requirements

A SORA does not replace Spanish aviation rules.

Instead, it forms part of the regulatory pathway for demonstrating that a particular operation can be conducted safely.

For the broader Spanish framework, see our complete Spain Drone Laws 2026 guide.

What SORA 2.5 Means for Drone Technology

Advanced UAS operations increasingly combine autonomous systems, communications, safety procedures and structured operational risk management.

Image source: NASA / Wikimedia Commons. Image from NASA Langley UAS testing.

SORA 2.5 is not only a regulatory development.

It also influences how professional UAS systems are designed and operated.

As drone operations become more complex, operators increasingly need aircraft and systems capable of supporting:

• Reliable navigation
• Command and control
• Detect-and-avoid capabilities where applicable
• Geofencing and operational controls
• Reliable flight termination or contingency mechanisms
• Accurate telemetry
• Operational logging
• Predictable performance
• Maintenance and configuration management

This means future professional drone selection will increasingly depend not only on camera quality or flight time, but also on whether the aircraft and supporting systems can contribute credible evidence to a safety case.

Does SORA 2.5 Make EU Drone Authorisation Easier?

In many cases, yes—but not automatically.

EASA explicitly designed SORA 2.5 to simplify aspects of the authorization process while maintaining safety.

The most significant benefits can include:

• Clearer methodology
• More consistent interpretation
• Greater harmonisation across Member States
• Reduced evidence requirements for many low-risk SAIL II VLOS operations
• More proportionate containment requirements

However, a complex BVLOS operation with significant ground and air risk can still require substantial technical and operational evidence.

SORA 2.5 makes the methodology more proportionate.

It does not make high-risk operations low-risk.

What SORA 2.5 Does Not Mean

• It does not replace EU Regulation 2019/947.
• It does not replace national aviation requirements.
• It does not automatically authorise an operation.
• It does not mean every commercial flight requires SORA.
• It does not make BVLOS operations automatically legal.
• It does not eliminate the need for operational procedures.
• It does not remove the responsibility of the operator to demonstrate safety.
• It does not guarantee approval by a competent authority.

This distinction is essential for anyone researching SORA for the first time.

SORA 2.5: Practical Checklist for Operators

SORA 2.5 vs SORA 2.0

SORA 2.5 is an evolution rather than a completely different risk philosophy.

The fundamental risk-based structure remains recognizable, but the updated version changes several elements of the process.

Operators moving from an older SORA methodology should therefore avoid simply copying an old assessment and changing the version number.

The operation should be reviewed against the applicable SORA 2.5 structure and current national application requirements.

Why SORA 2.5 Matters for the Future of European Drones

The European drone market is moving toward increasingly sophisticated operations.

Small camera drones are already capable of advanced autonomous functions.

Larger UAS platforms are being developed for:

• Inspection
• Surveying
• Logistics
• Medical delivery
• Agriculture
• Emergency response
• Security applications
• Industrial monitoring

As these operations expand, aviation authorities need a way to distinguish genuinely different levels of risk.

SORA provides that framework.

SORA 2.5 is therefore important not because it creates a new type of drone licence, but because it helps establish a more structured pathway for integrating advanced UAS operations into European airspace.

MidronePro Verdict: Is SORA 2.5 Good for Drone Operators?

Yes—provided operators understand what it is designed to do.

SORA 2.5 does not eliminate the regulatory complexity associated with advanced drone operations.

Instead, it attempts to make that complexity more proportionate.

For lower-risk operations, that can mean less unnecessary evidence.

For complex operations, it provides a structured framework for demonstrating safety.

For professional drone companies, this is a positive development.

The most important lesson is simple:

SORA is about the operation, not simply the drone.

A sophisticated aircraft does not automatically produce a safe operation. A well-designed operation, supported by appropriate mitigations, procedures, personnel and evidence, is what ultimately matters.

For operators preparing for advanced European drone operations in 2026, understanding SORA 2.5 is becoming increasingly important.

Learn More at MidronePro Academy

Continue building your knowledge with these MidronePro Academy resources:

• Drone Laws & Safety Guide 2026 — The complete foundation for responsible drone operations.
• Drone Laws in Spain 2026 — Understand the European framework and Spanish AESA requirements.
• Drone Registration Guide 2026 — Learn when drone operator registration is required.
• Drone Travel Guide 2026 — Prepare for international drone travel and changing regulations.
• Explore Drone Laws & Safety — Browse more regulatory and safety resources.

For official regulatory information, always consult the latest EASA, European Commission and national aviation-authority publications before submitting an operational application or conducting an advanced UAS operation.

Regulatory Disclaimer

This article is provided for general educational purposes and is not legal, regulatory or aviation-safety advice. Drone regulations, acceptable means of compliance, geographical restrictions and national authorization procedures can change. Always consult the latest official EASA material, European Union legislation and the competent national aviation authority before conducting an operation in the specific category.

Frequently Asked Questions

What does SORA 2.5 stand for?

SORA 2.5 stands for Specific Operations Risk Assessment version 2.5. It is a risk-assessment methodology used to evaluate UAS operations in the European specific category.

Who developed SORA 2.5?

The SORA methodology was developed by the Joint Authorities for Rulemaking on Unmanned Systems (JARUS). EASA adapted the JARUS methodology for application within the European Union regulatory framework.

Is SORA 2.5 a drone licence?

No. SORA 2.5 is a risk-assessment methodology. It supports the assessment and authorization process for certain UAS operations in the specific category.

Does every commercial drone flight require SORA 2.5?

No. Commercial status alone does not determine whether SORA is required. The applicable operating category, operational conditions and available regulatory pathways determine what process applies.

Does BVLOS require SORA 2.5?

BVLOS operations can fall within the specific category and may require a SORA-based authorization unless another applicable regulatory pathway covers the operation. Operators should verify the exact requirements with the competent authority.

What is SAIL in SORA 2.5?

SAIL means Specific Assurance and Integrity Level. It establishes the level of assurance and integrity that must be demonstrated for the safety objectives associated with an operation.

What are GRC and ARC?

GRC refers to Ground Risk Class and evaluates risk to people and property on the ground. ARC refers to Air Risk Class and addresses the risk of encountering other aircraft.

Does SORA 2.5 make drone authorization easier?

It is designed to simplify and harmonise the authorization process. EASA specifically highlights reduced evidence requirements for most low-risk VLOS operations classified as SAIL II and certain relaxed containment requirements.

Is SORA 2.5 used in Spain?

Yes. SORA 2.5 forms part of the European framework applicable to specific-category UAS operations, with Spanish operations subject to the applicable AESA procedures and national requirements.

Can a PDRA replace a SORA?

A PDRA can provide an alternative predefined pathway when the operation fits the conditions of the applicable PDRA. If the operation does not fit an available predefined pathway, a SORA-based assessment may be required.

Can a Standard Scenario replace SORA?

When an operation fits an applicable Standard Scenario, the STS provides a predefined regulatory pathway and can avoid the need for a bespoke SORA assessment.

Does completing a SORA guarantee authorization?

No. A SORA supports an application and provides a structured safety assessment, but the competent authority remains responsible for assessing the application and determining whether the operation can be authorised.

Where can I find the official SORA 2.5 documentation?

The latest European SORA 2.5 material is incorporated into EASA's Easy Access Rules for Unmanned Aircraft Systems. Operators should always use the latest official EASA material and the current procedures of the relevant national aviation authority.