Name:
ASD-STAN PREN 4709-003 CORR 1 PDF
Published Date:
08/10/2023
Status:
[ Active ]
Publisher:
Aerospace and Defence Industries Association of Europe - Standardization
Applicability
This document provides means to demonstrate compliance with:
— the “geo-awareness” requirements specified in Part 2 points (13), Part 3 points (15) and Part 4 points (10) of the Commission Delegated Regulation (EU) 2019/945; and to
— the requirement on the smooth interaction of the optional geofencing function with the flight control system of the UA set by Part 2 points (14), Part 3 points (16) and Part 4 points (11) on the optional geofencing function.
This document specifies the minimum performance required from this “geo-awareness” function, without prescribing its design and implementation as far as possible.
Compliance with this document is recommended as one means of assuring that the geo-awareness function will perform its intended sub-functions satisfactorily under all conditions normally encountered in routine aeronautical operation.
Compliance to the “smooth interaction” requirement is, for a large part, addressed by subclause 6.3 on safe controllability if EN 4709-001:2023. This document will therefore refer to it to a large extend.
NOTE In this document, we will use “function” to designate the objects of this specification, and “equipment” to identify the entity implementing this function in whatever form.
General description of the geo-awareness function
“Geo-awareness” means a function that, based on the information provided by Member States describing the operational conditions set on the UAS geographical zones (UGZ) they have defined according to Article 15 of Commission Implementing Regulation (EU) 2019/947, detects a potential breach of airspace limitations and alerts the remote pilot so that they can take immediate and effective action to prevent that breach.
The ‘‘geo-awareness’’ function addressed in this document manages only the conditions required to comply with the requirements set by Regulation (EU) 2019/945:
— horizontal and vertical boundaries of UGZ;
— time applicability of the UGZ;
In addition, this document provides Guidelines for Management of notification and authorization required by UGZ and data update
Other conditions that member States may set when defining UGZ as per article 15.1 of Commission Implementing Regulation (EU) 2019-947 not required by Regulation (EU) 2019/945 are not addressed in this version of the document.
Optionally a UAS bearing a class identification label may be equipped with a function of automatic alteration of the trajectory that prevents the UA from penetrating a certain airspace by engaging an adequate manoeuvre without any pilot action. This additional function called “geofencing” does not release the UAS from the obligation to comply with the “geo-awareness” requirement. In addition, it is subject to a requirement of smooth interaction with the flight control system.
The “geo-awareness” function can be realized as a set of hardware and/or software components inside the UAS, in the command unit and/or on board the UA itself, which are fed by data related the applicable UGZ for the intended zone of operation, provided by a ground service called in our document “UGZ data service”.
The document is structured as follows:
— clauses 1 to 3 of this document provide information required to understand the need for the function characteristics and tests defined in the remaining sections. It describes typical function applications and operational objectives and is the basis for the performance criteria stated in clause 4 to clause 5. Definitions essential to proper understanding of this document are provided in clause 3;
— clause 4 contains general design requirements for the “geo-awareness” function;
— clause 5 contains the detailed requirements for the “geo-awareness” function, defining performance under standard operating conditions and recommended test procedures for demonstrating compliance;
— clause 6 contains the requirements for the automatic geofencing function, defining performance under standard operating conditions and recommended test procedures for demonstrating compliance.
Operational performance standards for functions or components that refer to equipment capabilities that exceed the regulatory requirements are identified as optional features.
Assumptions
It is assumed that the update of UGZ data is not required during the flight.
It is assumed that the quality of the UGZ data provided and received by the UAS are verified for validity against the common unique digital format required by Article 15.3 of Regulation (EU) 2019/947.
| Edition : | P1 |
| File Size : | 1 file , 1.3 MB |
| Number of Pages : | 33 |
| Published : | 08/10/2023 |