AMC & GM to Part-UAS — Issue 1, Amendment 1

Annex II to ED Decision 2020/022/R ‘Acceptable Means of Compliance (AMC) and Guidance Material (GM) to the Annex (Part-UAS) to Regulation (EU) 2019/947 — Issue 1, Amendment 1’

Annex II to ED Decision 2019/021/R is amended as follows: The text of the amendment is arranged to show deleted text, new or amended text as shown below: (a) deleted text is marked with strikethrough; (b) new or amended text is highlighted in blue; (c) an ellipsis ‘(…)’ indicates that the remaining text is unchanged.

The UAS operator should submit an application according to the following form. The application and all the documentation referred to or attached should be stored for two years in a manner that ensures their protection from unauthorised access, damage, alteration, and theft. The declaration may be complemented by the description of the procedures to ensure that all operations are in compliance with Regulation (EU) 2016/679 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, as required by point UAS.SPEC.050 (1)(a)(iv).

yes no

yes no

Instructions for filling in the form

1.1 The UAS operator registration number in accordance with Article 14 of the UAS Regulation.

1.2 The nName of the accountable manager or the name of the UAS operator in the case of a natural person.

2.1 The nName of the manufacturer of the UAS.

2.2 The mModel of the UAS as defined by the manufacturer.

2.3 Include the EASA TC number, if available.

2.34 The sSerial number of the UA defined by the manufacturer, or the UA registration mark if the component authority requires the use of a UAS with an EASA TC.for the UA requiring registration according to Article 14 of the UAS Regulation

2.5 If a UAS with an EASA TC is required, the UAS should have a certificate of airworthiness (CofA).

2.6 If a UAS with an EASA TC is required, the UAS should have a noise certificate.

2.47 The cConfiguration of the UA.

2.58 The mMaximum take-off mass for which the UA is designed, expressed in kg.

2.69 The mMaximum cruise air speed expressed in m/s and knots in parenthesis.

2.710 State the maximum dimensions of the UA in metres (e.g. for aeroplanes: the length of the wingspan; for helicopters: the diameter of the propellers; for multirotors: the maximum distance between the tips of 2 opposite propellers). NOTE: Section 2 may include more than one UAS. In that case, it should be filled with the data of all the UAS intended to be operated. 3.1 The description of the intended operation characterising the area where it will take place (i.e. urban, sparsely populated, industrial, etc.) and the airspace. 3.3 The number of the PDRA, if applicable. 3.6 A list of the mitigation measures and the OSOs put in place, as required by the PDRA or proposed by the UAS operator if no PDRA is available. Sufficient information should be provided to the competent authority to assess the robustness of the measures. 3.8 A short description of the procedures established by the UAS operator to ensure that all operations are in compliance with Regulation (EU) 2016/679 on the protection on personal data as required by point UAS.SPEC.050(1)(a)iv. Note: The signature and stamp may be provided in electronic form.

OPERATIONAL AUTHORISATION TEMPLATE

The competent authority should produce the operational authorisation according to the following form:

NAA Operational authorisation Logo

Instructions for filling in the form 1.1 Name of the State of the UAS operator. 1.2 Identification of the issuing competent authority. 1.3 Contact detailsdata of the person responsible for issuing the authorisation. 2.1 Registration information of the UAS operator in accordance with Article 14 of the UAS Regulation. 2.2 UAS operator’s registered first name and last surname or, in the case of a legal entity, the business name. 2.3 The contact details include the telephone and fax numbers, including the country code, and the email address at which the accountable manager and the safety manager can be contacted without undue delay. 2.4 Reference number, as issued by the competent authority. 3.1 Name of the manufacturer of the UAS. 3.2 Model of the UAS as defined by the manufacturer. 3.3 Include the EASA TC number if the competent authority requires the use of a UAS with an EASA TC. 3.34 Serial number of the UA defined by the manufacturer or UA registration mark if the competent authority requires the use of a UAS with an EASA TCfor the UA requiring registration according to Article 14 of the UAS Regulation. 3.5 If a UAS with an EASA type certificate (TC) is required, the UAS should have a certificate of airworthiness (CofA) and a noise certificate, and the competent authority should require compliance with the continuing-airworthiness rules. 4.1 Locations where the UAS operation has been authorised, based on the adaptation of mitigation measures. 4.2 Characterisation of the authorised airspace (i.e. low risk — ARC -aA, medium risk — ARC -b, high risk — ARC -cC). 4.3 List the operational limitations, including at least: — the maximum height;

— limitations on the payload; — limitations on the operations (i.e. the possibility to handoverhand over to another remote pilot during the flight); — the minimum contents of the OM; — the methodology to verify the operational procedures; — the need for an emergency response plan (ERP); — the maintenance requirements; and — the record-keeping requirements. 4.4 List the mitigation measures including at least protection of a third party on the ground (including the definition of a specific authorised flight path, if applicable) . 4.5 The minimum competency required for the remote pilot and the methodology to assess it. 4.6 The minimum competency required for the staff essential for the operation (i.e. maintenance staff, the launch and recovery assistant, UA VAO, etc.) and the methodology to assess it. Note: The signature and stamp may be provided in electronic form.

AMC1 UAS.LUC.060 Privileges of an LUC holder

SCOPE OF PRIVILEGES

Within the terms of its approval, the LUC holder should be able: (a) without prior declaration to the competent authority, to authorise its own operations based on an STS; and (b) without prior approval of the competent authority, to authorise one or more of the following types of own operations: (1) one based on a PDRA that requires an authorisation; (2) one based on one or more modifications of an STS (variants), which does not involve changes in the ConOps, the category of UAS used or the competencies of the remote pilots; or (3) one that does not correspond to a PDRA, but falls within a type of activity already performed by the UAS operator. In case of UAS operations that are conducted at SAIL V and VI, the competent authority requires the LUC holder to use a UAS with an EASA TC. In case of UAS operations that are conducted at SAIL III and IV, the competent authority specifies if the LUC holder is required to use a UAS with an EASA TC.

GM1 UAS.LUC.060 Privileges of an LUC holder

For the purpose of granting privileges to LUC applicants, the competent authority may apply a gradual approach. Depending on the UAS operator’s past safety performance and safety record over a defined period of time (e.g. the previous 6 months), the competent authority may expand the scope of the UAS operator’s privileges. The gradual approach should not be understood as preventing the competent authority from granting privileges with a greater scope to a first-time LUC applicant who has an adequate structure and competent personnel, an effective safety management system and has demonstrated a good compliance disposition. For operations that are conducted at SAIL III and IV, and to facilitate harmonisation among EASA Member States, EASA recommends that the competent authority always requires LUC holders to use a UAS with an EASA TC.