Compare and highlight differences

Compare / EASA/ Incorporated Amendments/ Compare & Highlight Differences

AMC1 UAS.SPEC.030(2) Application for an operational authorisation -- EASA Form 208

Available versions for ERULES-1963177438-15578

ED Decision 2022/002/R found in: Unmanned Aircraft Systems (2019/947 and 2019/945) Part-UAS (Jul 2024)
ED Decision 2025/018/R found in: Unmanned Aircraft Systems (Jun 2026)

From

Show details Hide details

AMC1 UAS.SPEC.030(2) Application for an operational authorisation

ED Decision 2022/002/R

APPLICATION FORM FOR AN OPERATIONAL AUTHORISATION

The UAS operator should submit an application for an operational authorisation according to the following form. The application and all the documentation referred to or attached to the application should be stored for at least 2 years after the expiry of the related operational authorisation or submission of application in case of refusal. The UAS operator should ensure the protection of the stored data 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](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679&qid=1610371712444) 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)](#_DxCrossRefBm1106656785) of the UAS Regulation.

<table border="1" cellpadding="0" cellspacing="0" width="706"><tr><td valign="top" width="91"><p align="center"><div class="image-container"><img alt="EASA EAR image" src="/static/files/file_5I6t1EH0lEH/image018.png"/></div></p></td><td colspan="6" valign="top" width="615"><p align="center"><b>Application for an operational authorisation for the ‘specific’ category</b></p></td></tr><tr><td colspan="7" valign="top" width="706"></td></tr><tr><td colspan="7" valign="top" width="706"><p><b>Data protection</b>: Personal data included in this application is processed by the competent authority pursuant to <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679&amp;amp;qid=1610371712444">Regulation (EU) 2016/679</a> of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A31995L0046&amp;amp;qid=1610371877615">Directive 95/46/EC</a> (General Data Protection Regulation). Personal data will be processed for the purpose of the performance, management and follow-up of the application by the competent authority in accordance with <a href="#_DxCrossRefBm1106656760">Article 12</a> of <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32019R0947&amp;qid=1625433223089">Regulation (EU) 2019/947</a> of 24 May 2019 on the rules and procedures for the operation of unmanned aircraft.</p><p>If the applicant requires further information concerning the processing of their personal data or exercising their rights (e.g. to access or rectify any inaccurate or incomplete data), they should refer to the point of contact of their competent authority.</p><p>The applicant has the right to file a complaint regarding the processing of their personal data at any time to the national data protection supervisory authority.</p></td></tr><tr><td colspan="7" valign="top" width="706"></td></tr><tr><td colspan="3" valign="top" width="324"><p> New application</p></td><td colspan="4" valign="top" width="382"><p> Amendment to operational authorisation NNN-OAT-xxxxx/yyy</p></td></tr><tr><td colspan="7" valign="top" width="706"><p align="center"><b>1. UAS operator data</b></p></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>1.1 UAS operator registration number</b></p></td><td colspan="4" valign="top" width="382"></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>1.2 UAS operator name</b></p></td><td colspan="4" valign="top" width="382"></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>1.3 Name of the accountable manager</b></p></td><td colspan="4" valign="top" width="382"></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>1.3 Operational point of contact</b></p><p>Name</p><p>Telephone</p><p>Email</p></td><td colspan="4" valign="top" width="382"></td></tr><tr><td colspan="7" valign="top" width="706"><p align="center"><b>2</b><b>Details of the UAS operation</b></p></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>2.1 Expected date of start of the operation</b></p></td><td valign="top" width="114"><p>DD/MM/YYYY</p></td><td colspan="2" valign="top" width="144"><p><b>2.2 Expected end date</b></p></td><td valign="top" width="124"><p>DD/MM/YYYY</p></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>2.3 Intended location(s) for the operation</b></p></td><td colspan="4" valign="top" width="382"></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>2.4 Risk assessment reference and revision</b></p></td><td colspan="4" valign="top" width="382"><p> SORA version __ PDRA # __-__ other _________</p></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>2.5 Level of assurance and integrity</b></p></td><td colspan="4" valign="top" width="382"></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>2.6. Type of operation</b></p></td><td colspan="4" valign="top" width="382"><p> VLOS BVLOS </p></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>2.7 Transport of dangerous goods</b></p></td><td colspan="4" valign="top" width="382"><p> Yes No </p></td></tr><tr><td colspan="2" rowspan="2" valign="top" width="133"><p><b>2.8 Ground risk characterisation</b></p></td><td valign="top" width="191"><p><b>2.8.1 Operational area</b></p></td><td colspan="4" rowspan="2" valign="top" width="382"></td></tr><tr><td valign="top" width="191"><p><b>2.8.2 Adjacent area</b></p></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>2.9 Upper limit of the operational volume</b></p></td><td colspan="4" valign="top" width="382"></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>2.10 Airspace volume of the intended operation</b></p></td><td colspan="4" valign="top" width="382"><p>A B C D E F G </p><p>U-space Other, specify</p></td></tr><tr><td colspan="2" rowspan="2" valign="top" width="133"><p><b>2.11 Residual air risk level</b></p></td><td valign="top" width="191"><p><b>2.12.1 Operational volume</b></p></td><td colspan="4" valign="top" width="382"><p>ARC-a ARC-b ARC-c ARC-d</p></td></tr><tr><td valign="top" width="191"><p><b>2.11.2. Adjacent volume</b></p></td><td colspan="4" valign="top" width="382"><p>ARC-a ARC-b ARC-c ARC-d</p></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>2.12 Operations manual reference</b></p></td><td colspan="4" valign="top" width="382"></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>2.13 Compliance evidence file reference</b></p></td><td colspan="4" valign="top" width="382"></td></tr><tr><td colspan="7" valign="top" width="706"><p align="center"><b>3. UAS data</b></p></td></tr><tr><td colspan="2" valign="top" width="133"><p><b>3.1 Manufacturer</b></p></td><td valign="top" width="191"></td><td colspan="2" valign="top" width="144"><p><b>3.2 Model</b></p></td><td colspan="2" valign="top" width="238"></td></tr><tr><td colspan="2" valign="top" width="133"><p><b>3.3 Type of UAS</b></p></td><td valign="top" width="191"><p>Aeroplane Helicopter</p><p>Multirotor Hybrid/VTOL</p><p>Lighter than air / other</p></td><td colspan="2" valign="top" width="144"><p><b>3.4 Max characteristic dimensions</b></p></td><td colspan="2" valign="top" width="238"><p>_____ m</p></td></tr><tr><td colspan="2" valign="top" width="133"><p><b>3.5 Take-off mass</b></p></td><td valign="top" width="191"><p>_____ kg</p></td><td colspan="2" valign="top" width="144"><p><b>3.6 Maximum speed</b></p></td><td colspan="2" valign="top" width="238"><p>_____ m/s (_____ kt)</p></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>3.7 Serial number or, if applicable, UA registration mark</b></p></td><td colspan="4" valign="top" width="382"></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>3.8 Type certificate (TC) or design verification report, if applicable</b></p></td><td colspan="4" valign="top" width="382"></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>3.9 Number of the certificate of airworthiness (CofA), if applicable</b></p></td><td colspan="4" valign="top" width="382"></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>3.10 Number of the noise certificate, if applicable</b></p></td><td colspan="4" valign="top" width="382"></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>3.11 Mitigation of effects of ground impact</b></p></td><td colspan="4" valign="top" width="382"><p> No Yes, low Yes, medium Yes, high</p></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>3.12 Technical requirements for containment</b></p></td><td colspan="4" valign="top" width="382"><p> Basic Enhanced</p></td></tr><tr><td colspan="7" valign="top" width="706"><p align="center"><b>4. Remarks</b></p></td></tr><tr><td colspan="7" valign="top" width="706"></td></tr><tr><td colspan="7" valign="top" width="706"><p align="center"><b>5. Declaration of compliance</b></p></td></tr><tr><td colspan="7" valign="top" width="706"><p><i>I, the undersigned, hereby declare that the UAS operation will comply with:</i></p><p>— <i>any applicable Union and national regulations related to privacy, data protection, liability, insurance, security, and environmental protection;</i></p><p>— <i>the applicable requirements of </i><a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32019R0947&amp;qid=1625433223089"><i>Regulation (EU) 2019/947</i></a><i>; and</i></p><p>— <i>the limitations and conditions defined in the operational authorisation provided by the competent authority.</i></p><p><i>Moreover, I declare that the related insurance coverage, if appliable, will be in place at the start date of the UAS operation.</i></p></td></tr><tr><td colspan="3" valign="top" width="324"><p><b>Date</b></p><p>DD/MM/YYYY</p></td><td colspan="4" valign="top" width="382"><p><b>Signature and stamp</b></p></td></tr><tr height="0"></tr></table>

Instructions for filling in the application form

If the application relates to an amendment to an existing operational authorisation, indicate the number of the operational authorisation and fill out in red the fields that are amended compared to the last operational authorisation.

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

1.2 UAS operator’s name as declared during the registration process.

1.3 Name of the accountable manager or, in the case of a natural person, the name of the UAS operator.

1.4 Contact details of the person responsible for the operation, in charge to answer possible operational questions raised by the competent authority.

2.1 Date on which the UAS operator expects to start the operation.

2.2 Date on which the UAS operator expects to end the operation. The UAS operator may ask for an unlimited duration; in this case, indicate ‘Unlimited’.

2.3 Location(s) where the UAS operator intends to conduct the UAS operation. The identification of the location(s) should contain the full operational volume and ground risk buffer (the red line in Figure 1). Depending on the initial ground and air risk and on the application of mitigation measures, the location(s) may be ‘generic’ or ‘precise’ (refer to [GM2 UAS.SPEC.030(2)](#_DxCrossRefBm1106656820)).

![EASA EAR image](/static/files/file_5I6t1EH0lEH/image036.png)

Figure 1 — Operational area and ground risk buffer

2.4 Select one of the three options. If the SORA is used, indicate the version. In case a PDRA is used, indicate the number and its revision. In case a risk assessment methodology is used other than the SORA, provide its reference. In this last case, the UAS operator should demonstrate that the methodology complies with [Article 11](#_DxCrossRefBm1106656763) of the UAS Regulation.

2.5 If the risk methodology used is the SORA, indicate the final SAIL of the operation, otherwise the equivalent information provided by the risk assessment methodology used.

2.6 Select one of the two options.

2.7 Select one of the two options.

2.8 Characterise the ground risk (i.e. density of overflown population density, expressed in persons per km2, if available, or ‘controlled ground area’, ‘sparsely populated area’, ‘populated area’, ‘gatherings of people’) for both the operational and the adjacent area.

2.9 Insert the maximum flight altitude, expressed in metres and feet in parentheses, of the operational volume (adding the air risk buffer, if applicable) using the AGL reference when the upper limit is below 150 m (492 ft), or use the MSL reference when the upper limit is above 150 m (492 ft).

2.10 Select one or more of the nine options. Select ‘Other’ in case none of the previous applies (i.e. military areas).

2.11 Select one of the four options.

2.12 Indicate the OM’s identification and revision number. This document should be attached to the application.

2.13 Indicate the compliance evidence file identification and revision number. This document should be attached to the application.

3.1 Name of the manufacturer of the UAS.

3.2 Model of the UAS as defined by the manufacturer.

3.3 Select one of the five options.

3.4 Indicate 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 two opposite propellers) as used in the risk assessment to identify the ground risk.

3.5 Indicate the maximum value, expressed in kg, of the UA take-off mass (TOM), at which the UAS operation may be operated. All flights should then be operated not exceeding that TOM. The TOM may be different from (however, not higher than) the MTOM defined by the UAS manufacturer.

3.6 Maximum cruise airspeed, expressed in m/s and kt in parentheses, as defined in the manufacturer’s instructions.

3.7 Unique serial number (SN) of the UA defined by the manufacturer according to standard ANSI/CTA‑2063‑A‑2019, *Small Unmanned Aerial Systems Serial Numbers*, 2019, or UA registration mark if the UA is registered. In case of privately built UAS or UAS not bearing a unique SN, insert the unique SN of the remote identification system.

3.8 Include the EASA TC number, or the UAS design verification report number issued by EASA, if applicable.

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

3.10 If a UAS with an EASA TC is required by the competent authority, the UAS should have a noise certificate.

3.11 Select one of the four options.

3.12 Select one of the two options.

4 Free-text field for the addition of any relevant remark.

Note 1: Section 3 may include more than one UAS. In that case, it should be filled in with the data of all the UASs intended to be operated. If needed, fields may be duplicated.

Note 2: The signature and stamp may be provided in electronic form.

##### AMC1 UAS.SPEC.030(2) Application for an operational authorisation — EASA Form 208

*ED Decision 2025/018/R*

**APPLICATION
FORM FOR AN OPERATIONAL AUTHORISATION**

The UAS operator should submit an application for an operational
authorisation according to the following form. The application and
all the documentation referred to or attached to the application
should be stored for at least 2 years after the expiry of the
related operational authorisation or submission of application in
case of refusal. The UAS operator should ensure the protection of the
stored data 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](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679&qid=1610371712444) 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)](#_DxCrossRefBm1295819108)
of the UAS Regulation.

<table cellpadding="7" cellspacing="0">
<colgroup>
<col/>
</colgroup>
<colgroup>
<col/>
</colgroup>
<colgroup>
<col/>
</colgroup>
<colgroup>
<col/>
</colgroup>
<colgroup>
<col/>
</colgroup>
<colgroup>
<col/>
</colgroup>
<colgroup>
<col/>
<col/>
</colgroup>
<colgroup>
<col/>
</colgroup>
<colgroup>
<col/>
<col/>
</colgroup>
<colgroup>
<col/>
</colgroup>
<colgroup>
<col/>
</colgroup>
<colgroup>
<col/>
</colgroup>
<colgroup>
<col/>
</colgroup>
<colgroup>
<col/>
<col/>
</colgroup>
<colgroup>
<col/>
</colgroup>
<tbody>
<tr valign="top">
<td><p align="center">
<img align="bottom" border="0" name="Image10" src="source-marked.part-0002_html_2b6a293e.png"/>
</p>
</td>
<td colspan="17"><p align="center">
<b>Application
				for an operational authorisation for the ‘specific’ category</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#808080" colspan="18" valign="top"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td colspan="18" valign="top"><p>
<b>Data
				protection</b>: Personal data included in this application is
				processed by the competent authority pursuant to <u><a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679&amp;amp;qid=1610371712444">Regulation
				(EU) 2016/679</a></u> of the European Parliament and
				of the Council of 27 April 2016 on the protection of natural
				persons with regard to the processing of personal data and on the
				free movement of such data, and repealing <u><a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A31995L0046&amp;amp;qid=1610371877615">Directive
				95/46/EC</a></u> (General Data Protection Regulation).
				Personal data will be processed for the purpose of the
				performance, management and follow-up of the application by the
				competent authority in accordance with <u><a href="#_DxCrossRefBm1295819048">Article 12</a></u>
				of <u><a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32019R0947&amp;qid=1625433223089">Regulation
				(EU) 2019/947</a></u> of 24 May 2019 on the rules and
				procedures for the operation of unmanned aircraft.</p>
<p>
If
				the applicant requires further information concerning the
				processing of their personal data or exercising their rights
				(e.g. to access or rectify any inaccurate or incomplete data),
				they should refer to the point of contact of their competent
				authority.</p>
<p>
The
				applicant has the right to file a complaint regarding the
				processing of their personal data at any time to the national
				data protection supervisory authority.</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#808080" colspan="18" valign="top"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td colspan="3"><p>
<input type="checkbox"/>
				New application</p>
</td>
<td colspan="15"><p>
<input type="checkbox"/>
				Amendment to operational authorisation NNN-OAT-xxxxx/yyy</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#808080" colspan="18" valign="top"><p align="center">
<b>1.
				UAS operator data</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>1.1
				UAS operator registration number</b></p>
</td>
<td colspan="15"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>1.2
				UAS operator name</b></p>
</td>
<td colspan="15"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>1.3
				Name of the accountable manager</b></p>
</td>
<td colspan="15"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>1.3
				Operational point of contact</b></p>
<p>
Name</p>
<p>
Telephone</p>
<p>
Email</p>
</td>
<td colspan="15"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#808080" colspan="18" valign="top"><p align="center">
<b>2</b>.
				<b>Details of the UAS operation</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>2.1
				Expected date of start of the operation</b></p>
</td>
<td colspan="3"><p>
DD/MM/YYYY</p>
</td>
<td colspan="7"><p>
<b>2.2
				Expected end date</b></p>
</td>
<td colspan="5"><p>
DD/MM/YYYY</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>2.</b><b>3</b> <b>Risk assessment reference and revision</b></p>
</td>
<td colspan="15"><p>
<input type="checkbox"/>
				SORA edition date __   <input type="checkbox"/> PDRA # __-__
				edition date</p>
<p>
<input type="checkbox"/>
				other _________</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>2.</b><b>4</b><b>.
				Type of operation</b></p>
</td>
<td colspan="15"><p>
<input type="checkbox"/>
				VLOS            <input type="checkbox"/> BVLOS          
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>2.</b><b>5</b> <b>Transport of dangerous goods</b></p>
</td>
<td colspan="15"><p>
<input type="checkbox"/>
				Yes               <input type="checkbox"/> No          
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>2</b>.<b>6</b>
<b>Dropping
				material</b></p>
</td>
<td colspan="15"><p>
<input type="checkbox"/>
				Yes               <input type="checkbox"/> No          
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>2.7
				What is the minimum RP:UA ratio allowed between the remote pilot
				(RP) and the UA that may be operated simultaneously?</b></p>
</td>
<td colspan="15"><p>
RP:UA
				___:____</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>2.8
				Operations manual reference</b></p>
</td>
<td colspan="15"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>2.9
				Compliance matrix file reference</b></p>
</td>
<td colspan="15"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#808080" colspan="18" valign="top"><p align="center">
<b>3.
				UAS data</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="2"><p align="left">
<b>3.1
				Design organsation name</b></p>
</td>
<td bgcolor="#ffffff"><p>
<br/>
</p>
</td>
<td bgcolor="#d9d9d9" colspan="8"><p>
<b>3.2
				Model</b> <b>name</b></p>
</td>
<td colspan="7"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="2"><p>
<b>3.3
				Type of UAS</b></p>
</td>
<td bgcolor="#ffffff"><p>
<b><input type="checkbox"/></b> <b>Fixed wing</b></p>
<p>
<b><input type="checkbox"/></b> <b>Rotorcraft-helicopter</b></p>
<p>
<b><input type="checkbox"/></b> <b>Rotorcraft-gyroplane</b></p>
<p>
<b><input type="checkbox"/></b> <b>VTOL-capable aircraft (VCA) (including multirotors)</b></p>
<p>
<b><input type="checkbox"/></b><b>Lighter
				than air / other</b></p>
</td>
<td bgcolor="#d9d9d9" colspan="8"><p>
<b>3.4
				Maximum UA characteristic dimensions</b></p>
</td>
<td colspan="7"><p>
_____
				m</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="2"><p>
<b>3.5
				Take-off mass</b></p>
</td>
<td bgcolor="#ffffff"><p>
_____
				kg</p>
</td>
<td bgcolor="#d9d9d9" colspan="8"><p>
<b>3.6
				Maximum speed</b></p>
</td>
<td colspan="7"><p>
_____
				m/s (_____ kt)</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>3.7
				Type of C2 link</b></p>
</td>
<td colspan="15"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>3.8
				Size of the adjacent ground area</b></p>
</td>
<td colspan="15"><p>
<b>____
				km</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>3.9
				Is the UAS tethered during the operation?</b></p>
</td>
<td colspan="15"><p>
<b><input type="checkbox"/></b> <b>Yes      <input type="checkbox"/> No</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>3.10
				Type of propulsion system</b></p>
</td>
<td colspan="15"><p>
<b><input type="checkbox"/></b> <b>Electric       <input type="checkbox"/> Combustion</b></p>
<p>
<b><input type="checkbox"/></b> <b>Hybrid, specify type: ______________________</b></p>
<p><b><input type="checkbox"/></b> <b>Other, please specify: _____________________</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>3.11
				Serial number or, if applicable, UA registration mark</b></p>
</td>
<td colspan="15"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>3.12
				Type certificate (TC) or design verification report, if
				applicable</b></p>
</td>
<td colspan="15"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>3.13
				Number of the certificate of airworthiness (CofA), if applicable</b></p>
</td>
<td colspan="15"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>3.14
				Number of the noise certificate, if applicable</b></p>
</td>
<td colspan="15"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>3.15
				E-conspicuity system</b></p>
</td>
<td colspan="15"><p>
<input type="checkbox"/>
				Direct remote ID   <input type="checkbox"/> Network remote ID    
</p>
<p>
<input type="checkbox"/>
				SRD-860 In             <input type="checkbox"/> SRD-860 Out  
</p>
<p><input type="checkbox"/>
				ADS-B In      <input type="checkbox"/> ADS-B Out     <input type="checkbox"/>
				Other________</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="3"><p>
<b>3.16
				Green flashing light</b></p>
</td>
<td colspan="15"><p>
<input type="checkbox"/>
				Yes           <input type="checkbox"/> No</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#d9d9d9" colspan="18" valign="top"><p>
<input type="checkbox"/>
<b>I, the UAS operator, declare that:</b></p>
<p>
				— the
				UAS operation complies with any applicable Union and national
				regulations related to privacy, data protection, liability,
				insurance, security, and environmental protection;</p>
<p>
				— I
				have developed procedures to ensure that the intended UAS
				operation complies with the security requirements applicable to
				the area(s) of operation; 
</p>
<p>
				— I
				have developed measures to protect against unlawful interference
				and unauthorised access; 
</p>
<p>
				— I
				have developed procedures to ensure that all flights comply 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;</p>
<p>
				— I
				have developed procedures for the remote pilot(s) to plan UAS
				operations in a manner that minimises nuisance, including noise-
				and other emissions-related nuisance, to people and animals;</p>
<p>
				— I
				have records of: 
</p>
<p>
				— all
				relevant qualifications and training courses completed by the
				remote pilot(s) and other personnel in charge of duties essential
				to the UAS operation and by maintenance staff, for at least 3
				years after those persons have ceased employment with the
				organisation or have changed their position within the
				organisation; 
</p>
<p>
				— the
				maintenance activities carried out on the UAS for a minimum of 3
				years;</p>
<p>
				— the
				information on UAS operations, including any unusual technical or
				operational occurrences and other data as required by the
				declaration or by the operational authorisation for a minimum of
				3 years;</p>
<p>
				— an
				up-to-date list of designated remote pilots-in-command for each
				flight, and if applicable, for each phase of flight; 
</p>
<p>
				— an
				up-to-date list of maintenance staff employed to carry out
				maintenance activities;</p>
<p>— the
				insurance coverage, if applicable, will be in place at the
				expected date of start of the UAS operation</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#808080" colspan="18" valign="top"><p align="center">
<b>Section
				4 – Specific operations risk assessment (SORA)</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#d9d9d9" colspan="18" valign="top"><p align="center">
<b>Step
				#1 — Documentation of the proposed operation</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#dbe5f1" colspan="4"><p>
<b>Step
				#1.1 Description of proposed locations</b></p>
</td>
<td bgcolor="#d9d9d9" colspan="14"><p>
				— If
				location-specific:</p>
<p>
Give
				reference to the file:</p>
<p>
___________________________________
				
</p>
<p>
<br/>
<br/>
</p>
<p>
				— If
				location-independent: (generic authorisation)</p>
<p>
Give
				reference to the file as example of a location:</p>
<p>___________________________________</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td colspan="18" valign="top"><p>
<b>Step
				#1.2 Short description of the proposed operation</b></p>
<p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#dbe5f1" colspan="4"><p>
<b>Step
				#1.3 Dimensions of the operational volume and the adjacent volume</b></p>
<p>
(Rounded
				up to first decimal place)</p>
</td>
<td bgcolor="#d9d9d9" colspan="7"><p>
Maximum
				height of the flight geography</p>
<p>
Maximum
				height of the contingency volume</p>
<p>
Width
				of the contingency volume</p>
<p>
Width
				of the ground risk buffer</p>
<p>Width
				of the adjacent volume</p>
</td>
<td bgcolor="#d9d9d9" colspan="4"><p>
HFGmax<br/>
<br/>
<br/>
</p>
<p>
HCVmax<br/>
<br/>
<br/>
</p>
<p>
SCVmax<br/>
<br/>
<br/>
</p>
<p>
SGRBmax</p>
<p><br/>
SAV</p>
</td>
<td bgcolor="#d9d9d9" colspan="3"><p>
________
				m<br/>
<br/>
<br/>
</p>
<p>
________
				m<br/>
<br/>
<br/>
</p>
<p>
________
				m<br/>
<br/>
<br/>
</p>
<p>
________
				m <br/>
<br/>
<br/>
</p>
<p>________
				m</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#d9d9d9" colspan="18" valign="top"><p align="center">
<b>Step
				#2 — UAS intrinsic ground risk class (iGRC)</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#dbe5f1" colspan="4"><p>
<b>Step
				#2.1 Type of operational areas or maximum population density on
				the ground</b> (including flight geography, contingency volume
				and ground risk buffer)</p>
</td>
<td bgcolor="#d9d9d9" colspan="14"><p>
<input type="checkbox"/>
				controlled ground area                         people/km2</p>
<p>
<input type="checkbox"/>
				sparsely populated area                        <input type="checkbox"/>
				up to 5 
</p>
<p>
<input type="checkbox"/>
				up to 50</p>
<p>
<input type="checkbox"/>
				up to 500</p>
<p>
<input type="checkbox"/>
				populated area                                <input type="checkbox"/>
				up to 5 000</p>
<p>
<input type="checkbox"/>
				up to 50 000</p>
<p>
<input type="checkbox"/>
				more than 50 000   
</p>
<p>
<input type="checkbox"/>
				assemblies of people                                 <input type="checkbox"/>
				no limit</p>
<p><br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#dbe5f1" colspan="4"><p>
<b>Step
				#2.2 Specify the intrinsic ground risk class (iGRC)</b></p>
</td>
<td bgcolor="#d9d9d9" colspan="14"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td colspan="18" valign="top"><p>
<b>Step
				#2.3 Remarks/Reasoning for Step #2 (optional)</b></p>
<p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#d9d9d9" colspan="18" valign="top"><p align="center">
<b>Step
				#3 — Final ground risk class (GRC) determination (optional)</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#dbe5f1" colspan="4" rowspan="8"><p>
<b>Step
				#3.1 Specify the ground risk mitigations applied and the level of
				robustness </b>
</p>
<p>(if
				applicable)</p>
</td>
<td bgcolor="#d9d9d9" colspan="14"><p>
<b>M1</b>(A)
				Strategic mitigation — sheltering</p>
</td>
</tr>
<tr>
<td bgcolor="#d9d9d9" colspan="3"><p>
				☐None</p>
</td>
<td bgcolor="#d9d9d9" colspan="3"><p>
				☐Low</p>
</td>
<td bgcolor="#d9d9d9" colspan="6"><p>
				☐Medium</p>
</td>
<td bgcolor="#d9d9d9" colspan="2"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="14"><p>
<b>M1</b>(B)
				Strategic mitigation — operational restrictions</p>
</td>
</tr>
<tr>
<td bgcolor="#d9d9d9" colspan="3"><p>
				☐None</p>
</td>
<td bgcolor="#d9d9d9" colspan="3"><p>
<br/>
</p>
</td>
<td bgcolor="#d9d9d9" colspan="6"><p>
				☐Medium</p>
</td>
<td bgcolor="#d9d9d9" colspan="2"><p>
				☐High</p>
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="14"><p>
<b>M1</b>(C)
				Tactical mitigation — ground observation</p>
</td>
</tr>
<tr>
<td bgcolor="#d9d9d9" colspan="3"><p>
				☐None</p>
</td>
<td bgcolor="#d9d9d9" colspan="3"><p>
				☐Low</p>
</td>
<td bgcolor="#d9d9d9" colspan="6" valign="top"><p>
<br/>
</p>
</td>
<td bgcolor="#d9d9d9" colspan="2" valign="top"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#d9d9d9" colspan="14"><p>
<b>M2</b>
				Effects of UA impact dynamics are reduced  
</p>
</td>
</tr>
<tr>
<td bgcolor="#d9d9d9" colspan="3"><p>
				☐None</p>
</td>
<td bgcolor="#d9d9d9" colspan="3"><p>
<br/>
</p>
</td>
<td bgcolor="#d9d9d9" colspan="6"><p>
				☐Medium</p>
</td>
<td bgcolor="#d9d9d9" colspan="2"><p>
				☐High</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#dbe5f1" colspan="4"><p>
<b>Step
				#3.2 Specify the final ground risk class (GRC)</b></p>
</td>
<td bgcolor="#d9d9d9" colspan="14"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td colspan="18" valign="top"><p>
<b>Step
				#3.2 Remarks/Reasoning for Step #3 (optional)</b></p>
<p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#d9d9d9" colspan="18" valign="top"><p align="center">
<b>Step
				#4 — Initial air risk class (ARC)</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#dbe5f1" colspan="4" rowspan="3" valign="top"><p>
<b>Step
				#4.1 Classification of the airspace where the operation is
				intended to be conducted (multiple answers possible)</b></p>
</td>
<td><p>
				☐A</p>
</td>
<td colspan="3"><p>
				☐B</p>
</td>
<td><p>
				☐C</p>
</td>
<td colspan="3"><p>
				☐D</p>
</td>
<td colspan="2"><p>
				☐E</p>
</td>
<td colspan="3"><p>
				☐F</p>
</td>
<td><p>
				☐G</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td colspan="6"><p>
				☐Restricted
				area</p>
</td>
<td colspan="8"><p>
				☐Danger
				area</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td colspan="14"><p>
				☐TMZ
				       ☐RMZ        ☐ATZ        ☐CTR         ☐CTA       
				☐FIZ</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#dbe5f1" colspan="4"><p>
<b>Step
				4.2 Specify the initial air risk class (ARC) of the operational
				volume</b></p>
</td>
<td colspan="14"><p>
				☐ARC-a
				    ☐ARC-b    ☐ARC-c    ☐ARC-d</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td colspan="18" valign="top"><p>
<b>Step
				#4.3 Remarks/Reasoning for choosing the ARC in Step #4</b></p>
<p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#d9d9d9" colspan="18" valign="top"><p align="center">
<b>Step
				#5 — Strategic air risk mitigations and final air risk class
				(ARC)</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#dbe5f1" colspan="4"><p>
<b>Step
				#5.1 Specify the strategic mitigations of the air risk class, if
				applied</b></p>
</td>
<td colspan="6"><p>
				☐No</p>
</td>
<td colspan="8"><p>
				☐ VLOS
				
</p>
<p>
				☐BVLOS
				with AOs</p>
<p>
				☐ Operational
				restrictions</p>
<p>☐
				Common
				rules and structures</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#dbe5f1" colspan="4"><p>
<b>Step
				#5.2 Residual air risk class </b>
</p>
<p>(after
				strategic mitigation)</p>
</td>
<td colspan="14"><p>
				☐ARC-a
				   ☐ARC-b    ☐ARC-c    ☐ARC-d</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td colspan="18" valign="top"><p>
<b>Step
				#5.3 Remarks/Reasoning for Step #5 (not needed if no mitigation
				applied)</b></p>
<p><br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#d9d9d9" colspan="18" valign="top"><p align="center">
<b>Step
				#6 — Tactical mitigation performance requirements (TMPRs) and
				robustness level</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#dbe5f1" colspan="4"><p>
<b>Step
				#6 Tactical mitigation performance requirements (TMPRs)</b></p>
</td>
<td colspan="14"><p>
				☐ No
				requirement (VLOS / BVLOS with AOs)</p>
<p>
				☐BVLOS
				
</p>
<p>
				☐No
				requirement (ARC-a)</p>
<p>
				☐Low
				(ARC-b)</p>
<p>
				☐Medium
				(ARC-c)</p>
<p>
				☐High
				(ARC-d)</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td colspan="18" valign="top"><p>
<b>Step
				#6.1 Remarks/Reasoning for Step #6 (optional)</b></p>
<p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#d9d9d9" colspan="18" valign="top"><p align="center">
<b>Step
				#7 — SAIL determination</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#dbe5f1" colspan="4"><p>
<b>Step
				#7.1 Specific assurance and integrity level (SAIL)</b></p>
</td>
<td colspan="14"><p>
				☐SAIL
				I  ☐SAIL II   ☐SAIL III   ☐SAIL IV   ☐SAIL V  
				☐SAIL VI</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#d9d9d9" colspan="18" valign="top"><p align="center">
<b>Step
				#8 — Determination of containment requirements</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#dbe5f1" colspan="4"><p>
<b>Step
				#8.1 Containment  </b>
</p>
</td>
<td colspan="14"><p>
				☐Low
				   ☐Medium    ☐High    ☐Tethered</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#dbe5f1" colspan="4"><p>
<b>Step
				#8.2 Assembly of people within 1 km of the operational volume?</b></p>
</td>
<td colspan="14"><p>
				☐No
				   ☐Yes</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td colspan="18" valign="top"><p>
<b>Step
				#8.2 Remarks/Reasoning for Step #8 (optional)</b></p>
<p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#d9d9d9" colspan="18" valign="top"><p align="center">
<b>Step
				#9 — Identification of operational safety objectives (OSOs)</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td bgcolor="#dbe5f1" colspan="4"><p>
<b>Step
				#9.1 Operational safety objectives</b></p>
</td>
<td bgcolor="#d9d9d9" colspan="14"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td bgcolor="#808080" colspan="18" valign="top"><p align="center">
<b>5.
				Remarks</b></p>
</td>
</tr>
</tbody>
<tbody>
<tr>
<td colspan="18" valign="top"><p>
<br/>
</p>
</td>
</tr>
</tbody>
<tbody>
<tr valign="top">
<td colspan="3"><p align="left">
<b>Date</b></p>
<p>
DD/MM/YYYY</p>
</td>
<td colspan="15"><p>
<b>Signature
				and stamp</b></p>
</td>
</tr>
</tbody>
</table>

**EASA
Form 208**

Instructions for filling in the
application form

If the application relates to an amendment to an existing operational
authorisation, indicate the number of the operational authorisation
and fill out in red the fields that are amended compared to the last
operational authorisation.

Section 1

1.1 UAS operator registration number in
accordance with [Article
14](#_DxCrossRefBm1295819232) of the UAS Regulation.

1.2 UAS operator’s name as declared
during the registration process.

1.3 Contact details of the person
responsible for the operation, in charge to answer possible
operational questions raised by the competent authority.

Section 2

2.2 Date on which the UAS operator expects
to end the operation. The UAS operator may ask for an unlimited
duration; in this case, indicate ‘Unlimited’.

2.3 Select one of the three options. If the SORA is used, indicate
the edition date as defined in [AMC1
Article 11](#_DxCrossRefBm1295819063). In case a PDRA is used, indicate the
number and its edition date as defined in the applicable AMC to
Article 11. In case a risk assessment methodology is used other than
the SORA, provide its reference. In this last case, the UAS operator
should demonstrate that the methodology complies with [Article 11](#_DxCrossRefBm1295819063)
of the UAS Regulation. In case a PDRA is used,
then section 4 of this form is not required to be completed.

2.7 If the UAS flight manual provided by the UAS
designer indicates that it is designed with a level of automation
that reduces the remote pilot’s workload allowing one remote pilot
(RP) to control multiple UA simultaneously, then specify the number
of UA that one remote pilot is permitted to control (e.g. in case one
RP is able to control simultaneously five UA, indicate RP:UA 1:5).
This number should not exceed the limit defined in the UAS flight
manual. Additionally, the UAS operator may decide to have a pool of
remote pilots controlling multiple UA simultaneously. In this case,
clear procedures should be developed to define who is the
pilot-in-command, responsible during each phase of the flight (e.g.
in case three RPs are permitted to control simultaneously ten UA,
indicate RP:UA 3:10).

2.8 Indicate the OM’s identification and revision number.

2.9 Indicate the compliance matrix file identification and revision
number (e.g. the compliance matrix defined in Chapter A.4 of [Annex
A to AMC1 Article 11](#_DxCrossRefBm1295819070) (SORA). This document should be
attached to the application.

Section 3

This section may be replicated for all authorised
UAS models to be used under this operational authorisation.

3.2 Model of the UAS as defined by the design organisation in the UAS
flight manual.

3.3 Fixed-wing UA includes configurations such as aeroplanes, kites,
gliders, etc.).

Rotorcraft-helicopter UA includes all
vertical-lift configurations having up to 2 rotors.

Rotorcraft-gyroplane UA is a special configuration
with unpowered rotor.

VTOL-capable aircraft (VCA) UA includes
vertical-lift configurations with 3 or more rotors and fixed-wing UA
capable of vertically taking off and landing.

Lighter-than-air configurations include configurations such as
airships, hot-air balloons, etc.

3.4 Indicate the maximum dimensions of the UA in metres (refer to
definition I.141 ‘UA characteristic dimension’ in [Annex
I of AMC1 Article 11](#_DxCrossRefBm1295819074) (SORA)).

3.5 Indicate the maximum value of the UA take-off mass (TOM),
expressed in kg, at which the UA may be operated. All flights should
be conducted without exceeding the specified TOM. The TOM may be
different from (however, not exceeding) the MTOM defined by the UAS
design organisation in the UAS flight manual.

3.6 Maximum operational airspeed, expressed in m/s and kt in
parentheses, that the remote pilot will not exceed during the
operation. This should always be lower than the maximum defined in
the UAS flight manual.

3.7 Indicate the type of C2 link to be used during the operation
(e.g. radio link, LTE/5G, satellite, etc.).

3.8 indicate the size in km to be considered for the adjacent ground
area starting from the limits of the ground risk buffer, using the
instructions defined in Section S.4.8.4 of [AMC1
Article 11](#_DxCrossRefBm1295819063) (SORA).

3.11 This field is mandatory if the UA is
registered according to Article 14(7) of Implementing Regulation (EU)
2019/947. If the UA is not registered, the NAA may indicate the
unique serial number (SN) of the UA defined by the design
organisation according to standard ANSI/CTA‑2063‑A‑2019,
*Small Unmanned Aerial Systems Serial
Numbers*, 2019. In case of privately
built UAS or UAS not equipped with a unique SN, insert the unique SN
of the remote identification system. For UAS operations classified in
SAIL V or higher, the serial numbers of all UAS should be provided
and any change to them would require the competent authority’s
prior approval. For UAS operations classified up to SAIL IV, a change
to the serial number does not require a prior approval from the
competent authority.

3.12 Include the EASA TC number, or the UAS design verification
report (DVR) number issued by EASA, if applicable.

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

3.14 If a UAS with an EASA TC is required by the competent authority,
the UAS should have a noise certificate.

3.15 Multiple options are possible. Direct remote ID developed
according to EN 4709-002.

In order to compile Section 4, please refer to
[AMC1
Article 11](#_DxCrossRefBm1295819063) (SORA).

Section 4

**Step
#1.1:**

The identification of the location(s) should
contain the full operational volume and ground risk buffer (the red
line in Figure 1; refer to [Annex
A to AMC1 Article 11](#_DxCrossRefBm1295819070) for
guidance and examples on the calculation of the operational volume
and ground risk buffer). Depending on the initial ground and air risk
classification determined using the SORA process and on the
application of mitigations, the location(s) may be ‘generic’ or
‘precise’ (refer to [GM2
UAS.SPEC.030(2)](#_DxCrossRefBm1295819076)).

![](/static/files/file_RLF4ozmpQHW/image151.png)

***Figure
1 — Operational area and ground risk buffer***

— Please, refer to [GM2
UAS.SPEC.030(2)](#_DxCrossRefBm1295819076) for guidance
on the conditions to apply for ‘generic’ versus ‘precise’
locations.

— If location-specific: please, provide a list
with the geo-coordinates for each location including the operational
volume (flight geography and contingency volume), the ground risk
buffer and the air risk buffer (if available) as a separate file
using either ‘.txt’, ‘.kmz’ or ‘.kml’.

— If location-independent: please, provide a
reference to the documented process for the determination of volumes
and buffers and the assessment of the local conditions and their
compliance limitations. An example of a geographical file (e.g.
‘.kmz’ or ‘.kml’) may be provided to show a typical
operational volume, ground risk buffer and the air risk buffer (if
available).

**Step
#1.2**: Insert, for
example, transport, inspection, filming, testing, etc.

**Step
#1.3**: Please, provide a
list with this information if location-specific with multiple
locations.

**Step
#4.1**: For information on
the airspace classification, refer to Article 2 and to points
SERA.6001 and SERA.6005 of Regulation (EU) No 923/2012.

**Step
#9.1**: List the OSOs and
the level of robustness you intend to comply with. The level of
robustness should as a minimum reflect the one defined in Table 14 of
Section S.4.9.3 of [AMC1
Article 11](#_DxCrossRefBm1295819063) considering the
SAIL listed in point ‘Step #7.1’ of this form.

SECTION 5 Free-text
field for the addition of any relevant remark.

Note: The signature and stamp may be provided in electronic form.

Compare / EASA/ Incorporated Amendments/ Compare & Highlight Differences

AMC1 UAS.SPEC.030(2) Application for an operational authorisation -- EASA Form 208

View