Do you produce the whole authorisation package or parts of it?

Either. Most operators ask for the full safety portfolio with the operations manual; manufacturers ask for the design verification report data and the compliance matrix.

SORA 2.5, as adopted in AMC1 to Article 11 of the June 2026 rules. Earlier assessments on 2.0 can be migrated.

Is the design verification report an approval?

No. The DVR is EASA's verification of the design against the special condition; the operational authorisation is issued by the national authority to the operator.

What about a military UAS?

A military UAS is certified against STANAG 4671 / AEP-4671 and its national military airworthiness regulation, not through a SORA under Regulation (EU) 2019/947. That work is on the military airworthiness page; a dual-use platform can reuse much of the same evidence in both directions.

The operator, for the declaration and the application; the manufacturer, for the design data. Lavionic produces and checks; the signature stays with your organisation.

Compliance artefact

SORA safety portfolio and design verification report

The operational authorisation package for a UAS operator and the design evidence for a UAS manufacturer, produced by our experts with Wingman360 Teammate from your ConOps and design data.

Which rule asks for it

An operation in the specific category needs an operational authorisation from the competent authority, granted under Article 12 of Regulation (EU) 2019/947 on an application made under UAS.SPEC.030. The authorisation rests on the operational risk assessment that Article 11 governs, and the accepted means of compliance for that assessment is SORA 2.5. The operator files the risk assessment, the operations manual and the compliance evidence; at SAIL IV the design is verified by EASA through a design verification report, and at SAIL V and VI the design needs a type certificate.

1. An operational risk assessment shall: (a) describe the characteristics of the UAS operation; (b) propose adequate operational safety objectives; (c) identify the risks of the operation on the ground and in the air considering all of the below: i. the extent to which third parties or property on the ground could be endangered by the activity; ii. the complexity, performance and operational characteristics of the unmanned aircraft involved; iii. the purpose of the flight, the type of UAS, the probability of collision with other aircraft and class of airspace used; iv. the type, scale, and complexity of the UAS operation or activity, including, where relevant, the size and type of the traffic handled by the responsible organisation or person; v. the extent to which the persons affected by the risks involved in the UAS operation are able to assess and exercise control over those risks. (d) identify a range of possible risk mitigating measures; (e) determine the necessary level of robustness of the selected mitigating measures in such a way that the operation can be conducted safely.

Easy Access Rules for Unmanned Aircraft Systems (Regulations (EU) 2019/947 and 2019/945), June 2026 revision

What we deliver

SORA 2.5 comprehensive safety portfolio: the ten steps, ground and air risk, the SAIL, the OSOs with the robustness argued, in the Annex A structure.
ConOps and UAS operations manual in the Annex A parts, and the compliance matrix Annex A.4 asks for.
Design verification report application data for SAIL IV, and the type certificate route at SAIL V and VI, against SC Light-UAS and the published means of compliance.
Sources register and citation trail.

How it is produced and checked

Our experts produce the portfolio with Wingman360 Teammate on Lavionic's servers from your ConOps, design description and the regulation text. A second expert checks every OSO argument and every citation. The operator declares and the authority approves; we deliver the package and the trail.

Standards and references

Regulation (EU) 2019/947 Articles 11 and 12, UAS.SPEC.030, AMC1 Article 11 (SORA 2.5), June 2026 Easy Access Rules
JARUS SORA v2.5 main body and Annexes A to E, May 2024
SC Light-UAS Medium Risk and High Risk, DVR Guidelines Issue 3, EASA

Questions

Do you produce the whole authorisation package or parts of it?: Either. Most operators ask for the full safety portfolio with the operations manual; manufacturers ask for the design verification report data and the compliance matrix.
Which SORA version?: SORA 2.5, as adopted in AMC1 to Article 11 of the June 2026 rules. Earlier assessments on 2.0 can be migrated.
Is the design verification report an approval?: No. The DVR is EASA's verification of the design against the special condition; the operational authorisation is issued by the national authority to the operator.
What about a military UAS?: A military UAS is certified against STANAG 4671 / AEP-4671 and its national military airworthiness regulation, not through a SORA under Regulation (EU) 2019/947. That work is on the military airworthiness page; a dual-use platform can reuse much of the same evidence in both directions.
Who signs?: The operator, for the declaration and the application; the manufacturer, for the design data. Lavionic produces and checks; the signature stays with your organisation.

Sources

Easy Access Rules for Unmanned Aircraft Systems (Regulations (EU) 2019/947 and 2019/945), June 2026
JARUS SORA v2.5, 13 May 2024
EASA DVR Guidelines Issue 3, 26 September 2023