Annex A to AMC1 to Article 11 - section overview

In plain language

This section provides guidelines and a template for UAS operators to collect and present system and operational information (ConOps) required to conduct a Specific Operations Risk Assessment (SORA) under Article 11.

Requirement as structured

This section provides guidelines and a template for UAS operators to collect and present system and operational information (ConOps) required to conduct a Specific Operations Risk Assessment (SORA) under Article 11.

Original regulatory text

CONOPS: GUIDELINES ON COLLECTING AND PRESENTING SYSTEM AND OPERATIONAL INFORMATION FOR SPECIFIC UAS OPERATIONS A.0 General guidelines This document must be original work completed and understood by the applicant (operator). Applicants must take responsibility for their own safety cases, whether the material originates from this template or otherwise. A.0.1 Document control Applicants should include an amendment record at the beginning of the document to record changes and show how that the document is controlled. Amendment/ Revision/ Issue Number Date Amended by Signed a, b, c or 1, 2, 3 etc. DDMMYYYY Name of the person carrying out the amendment/ revision/ issue number Signature of person carrying out the amendment/ revision/ issue number This section is critical to ensure appropriate document control. Any significant changes to the ConOps may require further assessment and approval by the competent authority prior to further operations being conducted. A.0.2 References (a) List all references (documents, URL, manuals, appendices) mentioned in the ConOps: # Title Description Amendment/ Revision/ Issue Number [1] [2] A.1 Guidance for the collection and presentation of operationally relevant information The template below provides section headings detailing the subject areas that should be addressed when producing the ConOps, for the purposes of demonstrating that a UAS operation can be conducted safely. The template layouts as presented are not prescriptive, but the subject areas detailed should be included in the ConOps documentation as required for the particular operation(s), in order to provide the minimum required information and evidence to perform the SORA. A.1.1 Reserved A.1.2 Organisation overview (a) This section describes how the organisation is defined, to support safe operations. It should include: (1) the structure of the organisation and its management, and (2) the responsibilities and duties of the UAS operator. A.1.2.1 Safety (a) The ‘specific’ category covers operations where the operational risks are higher and therefore the management of safety is particularly important. The applicant should describe how safety is integrated in the organisation, and the safety management system that is in place, if applicable. (b) Any additional safety-related information should be provided. A.1.2.2 Design and production (a) If the organisation is responsible for the design and/or production of the UAS, this section should describe the design and/or the production organisation. (b) It should provide information on the manufacturer of the UAS to be used if the UAS is not manufactured or produced by the operator, i.e. by a third-party manufacturer. (c) If required, information on the production organisation of the thirdparty organisation should be provided as evidence. A.1.2.3 Training of staff involved in operations This section should describe the training organisation or entity that qualifies all the staff involved in operations with respect to the ConOps. A.1.2.4 Maintenance This section should describe: (a) the general maintenance philosophy of the UAS; (b) the maintenance procedures for the UAS; and (c) the maintenance organisation, if required. A.1.2.5 Crew This section should describe: (a) the responsibilities and duties of personnel, including all the positions and people involved, for functions such as: (1) the remote pilot (including the composition of the flight team according to the nature of the operation, its complexity, the type of UAS, etc.); and (2) support personnel (e.g. visual observers (VOs), launch crew, and recovery crew); (b) the procedure for multi-crew coordination if more than one person is directly involved in the flight operations; (c) the operation of different types of UAS, including details of any limitations to the types of UAS that a remote pilot may operate, if appropriate; and (d) details of the operator’s policy on crew health requirements, including any procedures, guidance or referen

Applies when

operation

specific

regulatory category

Specific