UAS/dron requirements
List of manufacturers and models of UAS
- Definition of manufacturer: Any natural or legal person who manufactures a product or who has a product designed or manufactured and marketed under his name or trademark. The manufacturer is an ‘economic operator’ and is subject to obligations as defined in Delegated Regulation (EU) 2019/945.
- Definition of Private Construction UAS (Own Manufacture): It is a UAS assembled or manufactured for the manufacturer’s own use, excluding UAS mounted from assemblies of components placed on the market in the form of a single ready-to-assemble kit. Since it is not intended to be placed on the market, the builder of a private building UAS is not regarded as a ‘manufacturer’ within the meaning of the preceding paragraph.
- Manufacturer’s declaration (download model Manufacturer Statement UAS)
- UAS Technical Specifications Sheet (download UAS Specifications Sheet v2)
The new UAS regulatory framework, in particular Delegated Regulation (EU) 2019/945 defines these two new figures:
IMPORTANT NOTE: It is recalled that the coupling of devices to a commercial aircraft does not imply a manufacturer’s declaration.
Manufacturers wishing to have their products listed in the UAS digital catalogue of the State Aviation Safety Agency, or to update the information in that catalogue, must complete the following documents:
This statement is voluntary. However, for reasons of the quality of the information provided, this declaration must be submitted if its models are to appear on the list of manufacturers published by EASA.
Failure to complete this form in a complete and adequate manner would imply the non-insertion of your aircraft in the AESA UAS database.
And send them to AESA to drones.aesa@seguridadaerea.es.
The information of aircraft models shall be included in the Agency’s database, allowing operators with such aircraft to register them at the electronic site and to automatically submit declarations of operations according to standard scenarios or requests for authorisation in the specific category.
On the other hand, the UAS operator can show its wish that the manufacturer of its aircraft be incorporated into the databases of the UAS division in order to be able to register it. To do this, you must communicate the aircraft data using the UAS Technical Specification Sheet, sending us an email containing the information of the aircraft you wish to register at drones.aesa@seguridadaerea.es.
The equipment manufacturer must provide the technical data of the aircraft (MTOM, wingspan, speed, etc.) with the user manual of the aircraft.
It is recalled that the ‘open’ category operation does not require the registration of aircraft.
List of manufacturers and models of UAS
You can consult the list of manufacturers and models at the following link:
List of UAS manufacturers and models (periodic update)
Information on aircraft registration
- If you have submitted an operational declaration including this aircraft(s), you must make a new operational declaration including the correct aircraft. If the specified period has elapsed, the operator does not remedy the defect found, the corresponding Determination of Non-compliance with the submitted declaration will be sent.
The UAS operator shall be obliged to arrange and keep at the disposal of AESA the manufacturer’s instructions or a similar document developed by the UAS operator, where appropriate, in accordance with the documentation provided by the manufacturer, containing at least as indicated in point 22 of Appendix B UAS.STS.ES-01 or UAS.STS.ES-02.
You can consult the requirements and limitations of the national standard scenarios at the following link:
EASA management resolution approving national standard scenarios (STS-ES) for UAS operations in the ‘specific’ category under an operational declaration in accordance with Implementing Regulation (EU) 2019/947. - If you have applied for an authorisation including this aircraft(s), you must submit an amendment to the application. If the period indicated has expired, this error will not be remedied, you will receive a decision of inadmissibility of your request for authorisation.
In accordance with Article 11 of Implementing Regulation (EU) 2019/947, the operator is to collect and provide the relevant technical, operational and system information necessary to assess the risk associated with the planned UAS and SORA operation (UAS-specific risk assessment methodology described in the Regulation). Therefore, the operator must develop/update the documentation, in accordance with the requirements set out in the regulations and their implementing rules. In the case of aircraft characterisation, this is a document to be developed by the operator on the basis of the information provided by the manufacturer, in accordance with Article 11 AMC Annex A, point A.2.2. This information should be sufficient to address the required robustness levels of SORA mitigations and OSOs.
The operator shall draw up and provide, together with the application for authorisation, the documentation associated with the operation, including the aircraft characterisation document, which must follow the same criteria as those discussed above.
Once an aircraft is registered, in the registration application as an operator, under the “Aircraft” tab of the UAS list, there are two states: the so-called “Model State” and “Aircraft State”. The model state refers to whether a UAS model is in production or discontinued by the manufacturer, or whether the aircraft is subject to review by EASA once the aircraft has been registered. Within the aircraft state there are the following states: accepted, accepted auto, revised, auto-reviewed, assimilated, rejected, pending or inactive, in which the operator can review how your aircraft is located (more information about these states is available at the Electronic Headquarters if you access the interrogation icon, which will provide you with information about their meaning).
Therefore, when an operator registers an aircraft, it will be reviewed in the event that the operator has not chosen an aircraft included in the database.
Where aircraft are reviewed by AESA, if they are not correctly identified, you will receive an email informing you that you have either taken assimilated to an aircraft included in the system or rejected. In both cases, you will have 10 days to confirm or correct the identification of your aircraft, as it may be included in an operational declaration or authorisation application. In either case, you must correct the error to be specified in the mail sent:
