Specific Operations Risk Assessment (SORA)
New SORA Version 2.5
Please refer to the ‘Transition from SORA 2.0 to SORA 2.5’ section below for further information. The processing time of SORA 2.5 applications might be longer than usual due to induced changes in the review process.
Prerequisite knowledge
Knowledge of aviation processes, such as procedures for verifying safety-related systems, is an advantage. Should such knowledge and experience not be available in-house, and depending on the complexity of the safety case to be developed, applicants may consider engaging specialised companies to support the application process and provide guidance throughout.
Transition from SORA 2.0 to SORA 2.5
New SORA Ground Risk Map
The new SORA Ground Risk map (Population Density) aligned with SORA 2.5 is available on https://map.geo.admin.ch. Two layers are available to select: “SORA Ground Risk 100” (100m × 100m resolution) and “SORA Ground Risk 200” (200m × 200m resolution).
EASA Executive Decision on SORA 2.5 has entered into force on 30.09.2025. Until 01.04.2026 (6-months transition period), the FOCA will continue accepting applications based on SORA 2.0. Authorisations issued by the FOCA based on SORA 2.0 remain valid until 30.09.2027, or until their specified expiry date.
FOCA and UAS operators will work together throughout the transition period to update the FOCA Guidance Material accordingly. In the meantime, applicants can refer to the links below for the relevant EASA Acceptable Means of Compliance and Guidance Material for SORA 2.0 and SORA 2.5:
- SORA 2.0: Easy Access Rules for UAS (Revision from July 2024)
- SORA 2.5: AMC & GM to IR (EU) 2019/947 — Issue 1, Amendment 3
Steps to an authorization
Step 1– Ensure that the SORA process suits your needs
Before starting the SORA process, the applicant should verify that the proposed operation is feasible. Things to verify before beginning the SORA process are whether:
- the operation falls under the Open category;
- the operation is covered by a standard scenario (STS) or by a predefined risk assessment (PDRA);
- the operation falls under the ‘certified’ category;
- the operation is subject to a specific NO-GO from FOCA.
If none of the above cases applies, the SORA process can be applied.
The EASA Drone Rule Navigator can be used to help you identify the type of request that suits your needs.
Be aware that the SORA authorization process usually follows an iterative approach and may involve several rounds of exchanges. It requires close coordination with FOCA and adapts to the complexity of the project. Depending on the adjustments to be made to the safety portfolio following FOCA’s assessment, the overall evaluation may take additional time before it can be finalized.
Step 2– Familiarize yourself with the Regulations and reference documents
Before submitting a request, it is essential to review the applicable regulatory framework. FOCA provides dedicated guidance material, which must be consulted (see below). We also strongly recommend reviewing the other documents available under the “Links” and “Documents” sections at the bottom of this page.
Step 3– Initial submission: “Part 1” form
The process begins with the submission of the “Part 1” form (in PDF format; see below). FOCA will then examine the admissibility of the request. In certain cases, a 30-minute meeting may be organized between the applicant and a FOCA UAS expert to clarify specific aspects of the file.
Two “Part 1” forms are available below: one for SORA version 2.0 and one for version 2.5. Please ensure that you use the correct form.
Step 4– Continuation of the request: “Part 2” form and Compliance Spreadsheet
Once the admissibility has been confirmed, the applicant is invited to submit the “Part 2” form, together with the required annexes (as specified in the form), a Master Data List, and a mandatory compliance spreadsheet. The form and the compliance spreadsheet are provided by FOCA to each applicant individually.
Step 5– Assessment, exchanges, and issuance of the authorization
FOCA conducts a comprehensive review of the application. In most cases, multiple exchanges between FOCA and the applicant are required before the file can be accepted. Once all conditions are met, FOCA issues an operational authorization, which is valid for a period of two years maximum.
Modification or extension of an authorization
If an operational or technical modification is introduced to an already authorized activity, or if an extension of an authorization approaching its expiry date is requested, the dedicated form provided by FOCA must be used (see below).