Annex A to AMC1 Article 11 - section overview

In plain language

This Annex provides guidance to UAS operators on collecting and presenting evidence and data for operational authorization applications in the 'specific' category using the SORA process, outlining the general workflow, document structure, and evidence submission requirements.

Requirement as structured

This Annex provides guidance to UAS operators on collecting and presenting evidence and data for operational authorization applications in the 'specific' category using the SORA process, outlining the general workflow, document structure, and evidence submission requirements.

Original regulatory text

GUIDELINES ON COLLECTING AND PRESENTING INFORMATION ON SYSTEMS AND OPERATIONS REGARDING UAS OPERATIONS CONDUCTED IN THE ‘SPECIFIC’ CATEGORY The purpose of this Annex is to provide guidance to UAS operators for collecting and presenting evidence and data required when compiling an application to obtain operational authorisation for UAS operations in the ‘specific’ category. This document does not replace civil regulations but provides recommendations and guidance as to how UAS operators can comply with those regulations using the SORA process. This document is composed of the following five chapters: A.1: Key principles for completing the application documents for UAS operations to be conducted in the ‘specific’ category It explains the different documents and how to use them to compile an application. A.2: SORA risk assessment template It is intended to support UAS operators in compiling all the information necessary to perform a risk assessment. A.3: Structure of the operations manual It provides an operations manual model structure for UAS operators to follow in order to present their operations manual in an appropriate manner. A.4: Compliance matrix It provides a template for UAS operators on how to present the reference between the SORA-driven requirements and the operations manual. A.5: How to document and present a flight area It contains guidance for UAS operators on how to create and include a flight area into the operations manual. A.1 Key principles for completing the application documents for UAS operations to be conducted in the ‘specific’ category How does an application generally work? The operations manual serves as the basis for an operational authorisation for UAS operations to be conducted in the ‘specific’ category. When the competent authority issues the operational authorisation, it accepts the related operations manual. General workflow Before starting collecting information and describing procedures, the UAS operator should outline a preliminary operational concept (refer to Section S.4.1 of this AMC). This preliminary operational concept ensures that the UAS operator can effectively explore all available options, and select the most suitable approach for its specific needs. Key considerations for this initial plan include the following: the intended flight location(s); the maximum operational flight altitude and speed; the flight mode: either VLOS or BVLOS with or without AOs; the type of UAS to be used; environmental limitations (time of day, weather). In the next step, the UAS operator assesses the risk for the operation and develops a high-level overview of the SORA requirements. For this, the UAS operator should apply the requirements of Section A.2 and follow each step of the SORA process. When SORA phase 1 (see Figure A.1) is completed, it is considered best practice for a UAS operator to liaise with the competent authority before moving to the data collection and procedure description (refer to Section S.3.3 of this AMC) to share its preliminary operational information and initial risk assessment. The competent authority and the UAS operator evaluate the alignment of the risk assessment with the operational information and check the correct application of the SORA steps. The competent authority may provide feedback to the UAS operator on its expectations on how to achieve an operational authorisation considering the resulting SAIL. Once the risk assessment (i.e. the outcome of SORA Phase 1) has been validated and the UAS operator has secured confirmation from the competent authority, the next step involves identifying the specific requirements that arise from the risk assessment (i.e. conduct SORA phase 2 and develop the evidence in support of compliance with the applicable OSOs, mitigations and containment). Following this identification, the UAS operator should then collect the relevant evidence and information, as well as describe the procedures that will be implemented. The UAS operator shoul

Applies when

operation

EU UAS operation

subcategory

specific

regulatory category

Specific