SIST EN 4709-003:2026

Aerospace series - Unmanned Aircraft Systems - Part 003: Geo-awareness requirements

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 6.3 on safe controllability of EN 4709-001:2026. 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.

Luft- und Raumfahrt - Unbemannte Luftfahrzeugsysteme - Teil 003: Anforderungen an das Geo-Sensibilisierungssystem

Dieses Dokument bietet Mittel zum Nachweis der Einhaltung von:
-   den in Teil 2, Nummer (13), Teil 3, Nummer (15) und Teil 4, Nummer (10) der Delegierten Verordnung (EU) 2019/945 der Kommission festgelegten Anforderungen an die Geo-Sensibilisierung; und
-   der Anforderung an die reibungslose Interaktion der optionalen Geofencing-Funktion mit dem Flugsteuerungssystem des UA, die in Teil 2, Nummer (14), Teil 3, Nummer (16) und Teil 4, Nummer (11) zur optionalen Geofencing-Funktion festgelegt ist.
Dieses Dokument legt die minimalen Leistungsanforderungen an diese Geo-Sensibilisierungsfunktion fest, ohne deren Gestaltung und Umsetzung vorzugeben, sofern möglich.
Die Einhaltung dieses Dokuments wird empfohlen, um sicherzustellen, dass die Geo-Sensibilisierungsfunktion ihre vorgesehenen Teilfunktionen unter allen üblicherweise im Routinebetrieb der Luftfahrt anzutreffenden Bedingungen ordnungsgemäß erfüllt.
Die Einhaltung der Anforderung an die „reibungslose Interaktion“ wird größtenteils durch EN 4709 001:2026, 6.3 „Sichere Steuerbarkeit“, geregelt. Dieses Dokument wird sich daher in hohem Maße auf sie beziehen.
ANMERKUNG   In diesem Dokument wird der Begriff „Funktion“ verwendet, um die Elemente dieser Spezifikation zu bezeichnen, und „Ausrüstung“, um das Gerät zu bezeichnen, das diese Funktion in beliebiger Form implementiert.

Série aérospatiale - Aéronefs télépilotés - Partie 003 : Exigences de géovigilance

Le présent document offre les moyens de démontrer la conformité :
—   aux exigences de « géovigilance » spécifiées aux points (13) de la Partie 2, aux points (15) de la Partie 3 et aux points (10) de la Partie 4 de l’Annexe du Règlement délégué (UE) 2019/945 ; et
—   à l’exigence d’interaction sans heurts de la fonction facultative de géorepérage avec le système de commande du vol de l’UA définie au point (14) de la Partie 2, au point (16) de la Partie 3 et au point (11) de la Partie 4 sur la fonction de géorepérage facultative.
Le présent document spécifie les performances minimales requises de cette fonction de « géovigilance », sans en prescrire la conception et la mise en œuvre dans la mesure du possible.
La conformité au présent document est recommandée comme étant l'un des moyens de garantir que la fonction de géovigilance remplira de manière satisfaisante les sous-fonctions prévues dans toutes les conditions normalement rencontrées dans des opérations aéronautiques de routine.
La conformité à l’exigence d’« interaction sans heurts » est, en grande partie, traitée en 6.3 relatif à la contrôlabilité en toute sécurité de l’EN 4709-001:2026. Le présent document y fait donc largement référence.
NOTE   Dans le présent document, nous utiliserons le terme « fonction » pour désigner les objets de la présente spécification et le terme « équipement » pour identifier l'entité mettant en œuvre cette fonction, sous quelque forme que ce soit.

Aeronavtika - Letalski sistemi brez posadke - 003. del: Zahteve glede geozavedanja

Ta dokument zagotavlja sredstva za dokazovanje skladnosti z:
- zahtevami glede "geo-zavedanja", določenimi v delu 2, točkah (13), delu 3, točkah (15) in delu 4, točkah (10) Delegirane uredbe Komisije (EU) 2019/945; in
- zahtevami glede gladkega delovanja opcijske funkcije geofenciranja (geofencing) z letalskim kontrolnim sistemom UA, določenimi v delu 2, točkah (14), delu 3, točkah (16) in delu 4, točkah (11) za opcijsko funkcijo geofenciranja.
Ta dokument določa minimalne zmogljivosti, ki jih zahteva funkcija "geo-zavedanja", brez predpisovanja njene zasnove in izvedbe, kolikor je to mogoče.
Skladnost s tem dokumentom je priporočena kot eno izmed sredstev za zagotavljanje, da bo funkcija geo-zavedanja zadovoljivo izvajala svoje predvidene podfunkcije v vseh pogojih, ki se običajno pojavljajo pri rutinskem letalskem delovanju.
Skladnost z zahtevo "gladkega delovanja" je v veliki meri obravnavana v točki 6.3 o varni obvladljivosti standarda EN 4709-001:2026. Zato se bo ta dokument v veliki meri skliceval nanj.
OPOMBA V tem dokumentu bomo uporabili izraz "funkcija" za označevanje predmetov te specifikacije in "oprema" za identifikacijo entitete, ki izvaja to funkcijo v kakršni koli obliki.

General Information

• Status: Published
• Public Enquiry End Date: 24-Feb-2021
• Publication Date: 08-Apr-2026
• ICS: 49.020 - Aircraft and space vehicles in general
• Technical Committee: I13 - Imaginarni 13
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 31-Mar-2026
• Due Date: 05-Jun-2026
• Completion Date: 09-Apr-2026
• Directive: Harmonized Standard2019/945 - Commission Delegated Regulation (EU) 2019/945 of 12 March 2019 on unmanned aircraft systems and on third-country operators of unmanned aircraft systems
• Mandate: M/567 - Standardisation Request to the European Committee for Standardisation as regards unmanned aircraft systems intended to be operated in the ‘open’ category of operations in support of Commission Delegated Regulation (EU) 2019/945
• Ref Project: EN 4709-003:2026 - Aerospace series - Unmanned Aircraft Systems - Part 003: Geo-awareness requirements

Overview

FprEN 4709-003 - Geo-awareness requirements is a draft CEN/ASD-STAN standard that defines minimum performance and verification methods for the geo-awareness function in Unmanned Aircraft Systems (UAS). It provides a recommended means of compliance with the EU Delegated Regulation (EU) 2019/945 (open category UAS and third‑country operators) and references the Commission Implementing Regulation (EU) 2019/947 for UAS geographical zone (UGZ) data. The standard targets UAS Classes 1–3 and describes how on‑board or ground components must detect, alert, and optionally prevent breaches of airspace restrictions (geofencing).

Key topics and requirements

• Function definition: Geo-awareness detects potential breaches of horizontal and vertical UGZ boundaries, time applicability of UGZs, and optionally notification/authorization requirements.
• Performance vs. design freedom: Specifies minimum performance without prescribing specific hardware/software implementations.
• Alerting behaviour: Requirements for advisory and caution alerts, time/threshold to alert, and operating/activation status.
• Data handling: Expectations for loading, updating and validating UAS geographical zone (UGZ) data supplied by Member States (UAS geographical zone data service).
• Reliability & maintainability: General design requirements covering availability, integrity, maintainability, and software/hardware management.
• Vertical limits & thresholds: Explicit consideration of vertical boundaries and timing margins for alerts and actions.
• Geofencing option: Optional automatic trajectory alteration (geofencing) to prevent UA penetration of restricted zones, including manoeuvre timing and activation requirements.
• Verification & testing: Clause 7 provides recommended test procedures covering alerting, limiting, loading, update, operating status, and geofencing verification.
• Normative references: Includes prEN 4709‑001:2019 (Product requirements and verification) and alignment with EU regulations.

Applications and who uses it

• Manufacturers and system integrators designing UAS hardware/software to meet EU regulatory requirements.
• Economic Operators: importers, distributors and trade associations seeking acceptable means of compliance.
• Conformity assessment bodies and certification teams validating geo-awareness and geofencing functions.
• Software developers of UAS ground control and Remote Pilot Stations (RPS) implementing UGZ data handling and alerting.
• Service providers (geographical information distributors / U‑Space providers) supplying UGZ data compatible with the standard.

Related standards and regulations

• Commission Delegated Regulation (EU) 2019/945 (UAS – open category)
• Commission Implementing Regulation (EU) 2019/947 (UGZ data requirements)
• prEN 4709‑001:2019 - Aerospace series - Unmanned Aircraft Systems - Part 1: Product requirements and verification

This standard is essential for achieving regulatory compliance for geo-awareness and geofencing in European UAS operations and supports safe integration of remotely piloted systems into regulated airspace.

Standards Content (Sample)

SLOVENSKI STANDARD
01-maj-2026
Aeronavtika - Letalski sistemi brez posadke - 003. del: Zahteve glede geozavedanja
Aerospace series - Unmanned Aircraft Systems - Part 003: Geo-awareness
requirements
Luft- und Raumfahrt - Unbemannte Luftfahrzeugsysteme - Teil 003: Anforderungen an
das Geo-Sensibilisierungssystem
Série aérospatiale - Aéronefs télépilotés - Partie 003 : Exigences de géovigilance
Ta slovenski standard je istoveten z: EN 4709-003:2026
ICS:
49.020 Letala in vesoljska vozila na Aircraft and space vehicles in
splošno general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN 4709-003
EUROPEAN STANDARD
NORME EUROPÉENNE
March 2026
EUROPÄISCHE NORM
ICS 03.220.50; 49.020
English Version
Aerospace series - Unmanned Aircraft Systems - Part 003:
Geo-awareness requirements
Série aérospatiale - Aéronefs télépilotés - Partie 003 : Luft- und Raumfahrt - Unbemannte
Exigences de géovigilance Luftfahrzeugsysteme - Teil 003: Anforderungen an das
Geo-Sensibilisierungssystem
This European Standard was approved by CEN on 26 January 2026.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2026 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 4709-003:2026 E
worldwide for CEN national Members.

Contents Page
European foreword . 4
1 Scope . 5
1.1 Applicability . 5
1.2 General description of the geo-awareness function . 5
1.3 Assumptions . 6
2 Normative references . 6
3 Terms, definitions, symbols and abbreviated terms . 6
4 General design requirements . 8
4.1 Intended function . 8
4.2 Effects of tests . 8
4.3 Reliability, availability, . 8
5 Geo-awareness function . 8
5.1 General. 8
5.2 Performance requirements . 9
5.2.1 Loading . 9
5.2.2 Warning . 9
5.2.3 Operating status . 10
5.3 Verification methods . 10
5.3.1 General test conditions . 10
5.3.2 Loading: verification of the uploading of UGZ . 11
5.3.3 Warning . 11
5.3.4 Operating status . 15
5.4 Pass criteria . 15
5.4.1 Loading . 15
5.4.2 Warning: alerting on potential breach of restriction . 15
5.4.3 Operating status . 16
6 Geofencing function: smooth interaction with the flight control system of the UA . 17
6.1 General. 17
6.2 Performance requirements . 17
6.2.1 Geofencing manoeuvre . 17
6.2.2 Provided information . 17
6.3 Verification requirements . 17
6.3.1 Geofencing manoeuvre . 17
6.3.2 Information provided . 18
6.4 Pass criteria . 19
6.4.1 Geofencing manoeuvre . 19
6.4.2 Information provided . 19
Annex A (informative) Guidelines for setting margins and thresholds . 20
Annex B (informative) Guidelines for management of notification and authorization . 24
Annex C (informative) Guidelines for update . 25
Annex D (informative) Colours and size recommendations for alerts . 26
Annex ZA (informative) Relationship between this document and the Regulation (EU)
2019/945 of 12th March 2019 on unmanned aircraft systems and on third-country
operators of unmanned aircraft systems . 29
Bibliography . 31

European foreword
This document (EN 4709-003:2026) has been prepared by Technical Committee CEN/TC 471
“Unmanned Aircraft Systems”, the secretariat of which is held by BNAE.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by September 2026, and conflicting national standards
shall be withdrawn at the latest by September 2026.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document has been prepared under a Standardization Request given to CEN by the European
Commission and the European Free Trade Association and supports essential requirements of
EU Directive(s)/Regulation(s).
For relationship with EU Directive(s)/Regulation(s), see informative Annex ZA, which is an integral part
of this document.
Any feedback and questions on this document should be directed to the users’ national standards body.
A complete listing of these bodies can be found on the CEN website.
According to the CEN-CENELEC Internal Regulations, the national standards organisations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,
Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of
North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and the
United Kingdom.
1 Scope
1.1 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 6.3 on safe
controllability of EN 4709-001:2026. 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.
1.2 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 to 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.
1.3 Assumptions
It is assumed that the update of UGZ data are 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.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
EN 4709-001:2026, Aerospace series — Unmanned Aircraft systems — Part 1: Product requirements and
verification
3 Terms, definitions, symbols and abbreviated terms
For the purposes of this document the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https://www.iso.org/obp
— IEC Electropedia: available at https://www.electropedia.org/
3.1
above ground level
AGL
height measured with respect to the underlying ground surface
3.2
above mean sea level
AMSL
elevation (on the ground) or altitude (in the air) of any object, relative to the average sea level datum
3.3
advisory alert
alert for conditions that require awareness and may require subsequent response by the UAS remote
pilot
3.4
automatic flight
flight following pre-programmed instructions, loaded in the unmanned aircraft (UA) flight control
system that the UA executes
3.5
caution alert
alert for conditions that require immediate awareness and subsequent response by the UAS remote
pilot
3.6
CEP
Circular Error Probability
3.7
coordinated universal time
UTC
timescale which forms the basis of a coordinated radio dissemination of standard frequencies and time
signals
Note 1 to entry: It corresponds exactly in rate with international atomic time but differs from it by an integral
number of seconds.
3.8
command unit
CU
equipment or system of equipment to control unmanned aircraft remotely as defined in point 32 of
Article 3 of Regulation (EU) 2018/1139 which supports the control or the monitoring of the unmanned
aircraft during any phase of flight, except for any infrastructure supporting the command and control
(C2) link service
3.9
geo-awareness
function that provides a warning alert to the remote pilot to avoid breaching an airspace restriction
3.10
geofencing
function that automatically prevents the UA to penetrate a certain airspace by connecting with the flight
command and control system and engaging an adequate manoeuvre without any remote pilot action
Note 1 to entry: Airspace limits compliance function” can also be the term used to designate the geofencing
function.
3.11
global navigation satellite system
GNSS
positioning system based on one or several satellite constellations
3.12
haptic signal
any type of signal that is transferred to the hand of the user through the handheld equipment to control
the UA remotely in the form of vibrations
3.13
UAS geographical zone
UGZ
portion of airspace [in 3D] established by the competent authority that facilitates, restricts, or excludes
UAS operations in order to address risks pertaining to safety, privacy, protection of personal data,
security, or the environment, arising from UAS operations
3.14
UGZ data service
data distribution service to which an UAS operator can connect to access the data related to UAS
geographical zones established in the intended location of UAS operation and applicable to the “geo-
awareness” function
3.15
warning alert
alert for conditions that require immediate awareness and immediate response by the UAS remote pilot
4 General design requirements
4.1 Intended function
The equipment implementing the “geo-awareness” function shall perform its intended sub-function(s),
as defined by the manufacturer.
4.2 Effects of tests
Unless otherwise stated, the design of the equipment shall be such that, during and after the application
of the specified tests, executing by all involved parties for respective tests, no condition exists which
would be detrimental to the subsequent performance of the equipment.
4.3 Reliability, availability,
No reliability or availability requirements are set on the “geo-awareness” function.
5 Geo-awareness function
5.1 General
The “geo-awareness” function shall be able to manage any UGZ as described in the common unique
digital format.
If more than one restriction or condition is set at the same position, the “geo-awareness” function shall
consider the most restrictive one.
Information messages associated to multiple zones should be displayed simultaneously or in alternate
way, in a clear manner regarding the priority of messages.

Adapted from and in accordance with EUROCAE ED-269 (“Minimum Operational Performance Standard
(MOPS) for UAS geo-fencing”).
NOTE 1 Caution alert provided to the remote pilot can be triggered according to time-related geographical
zones (if any). Depending on the current location of the UA and the time of flight, an alert is provided when the
current location is to become forbidden soon and need to be exited:
— this caution alert is provided soon enough to enable exit or allow safe landing before active restriction
of the UGZ;
— it is also recommended to have an advisory alert before this last one.
The management of notification and authorization is optional. Guidelines are provided in Annex B for
the management of notification and authorization.
NOTE 2 At the present time, no automatic notification or authorization management is in place or
standardized. UGZ data set test file is provided by EASA on its website, and member states will make available the
national UGZ within their Aeronautical Information Publication service.
5.2 Performance requirements
5.2.1 Loading
Loading process shall not alter the integrity and the validity of data.
5.2.2 Warning
5.2.2.1 Alerting on potential breach of restriction
The “geo-awareness” function shall provide the remote pilot with a warning alert when a potential
breach of UGZ is detected, either in horizontal plane or vertical axis.
Consistently with the definition of the data model of the UGZ, the vertical part of “geo-awareness” shall
use the AMSL altitude or the AGL height.
The choice between these 2 references will be specified individually for each UGZ.
NOTE 1 The remote pilot remains responsible for applying the local regulations with respect to height above
the surface (refer to EN 4709-001:2026 for maximum attainable height), in addition to the vertical limits by the
UGZ.
If the AGL height is not supported by the UA, the height above take-off point may be used as the
approximation. The information on the approximation, and the difference between the two height
references shall be explained in the manufacturer’s instructions in this case. The remote pilot remains
responsible for not breaching the vertical limits of the UGZ.
The alert shall be provided by one or several of the following means, e.g.:
— aural signal;
— visual light on the equipment to control UA remotely;
— visual message on the equipment to control UA remotely;
— depiction of the potential point of conflict with the UGZ;
— vibration to the pilot on the equipment to control UA remotely.
NOTE 2 For the display of the alert, colours and size recommendations are presented in Annex D.
NOTE 3 For aural, visual and haptic alerts, guidance can be found in international standard EN 61310-1.
EXAMPLE Examples of visual indications include:
— warning light at the equipment to control the UA remotely;
— text message on the display of the equipment to control the UA remotely;
— depiction indicating the need for action on the equipment to control the UA remotely.
The manufacturer’s instructions shall include detailed information and specification about visual, aural
and haptic alerts with their expected scheme (such as type, frequency, duration and pattern).
The “geo-awareness” function may provide the remote pilot with a geographical depiction of the
current horizontal and vertical UA position and the UGZ, to enable the pilot to understand the situation
and anticipate manoeuvres.
5.2.2.2 Time/threshold to alert
The time or threshold to alert shall be defined by the manufacturer in order to assist the remote pilot in
its task to prevent the UA from penetrating into the UGZ.
Margin on limits for the time or threshold to alert (meaning additional distance to the UGZ border) shall
be included.
Guidelines are provided in Annex A for the design of the alert and its margins.
5.2.3 Operating status
The “geo-awareness” function shall provide the remote pilot with a warning alert when the operating
status of the “geo-awareness” function is degraded or inoperative.
The information provided during the operation should focus on the impact on the operation so that, the
remote pilot is informed about possible functional consequences.
The potential cause of degradation and inoperative status should be explained in the manufacturer’s
instructions.
The management of update is optional. Guidelines are provided in Annex C for update.
5.3 Verification methods
5.3.1 General test conditions
For repeatability, it is assumed that environmental conditions are recorded during any test, and it is
further assumed that tests are conducted, unless otherwise noted, within the conditions defined in the
pass criteria (3) in Safely controllable requirement section of EN 4709-001:2026.
When tests are performed, the same test shall be performed three times in order to assess the effect of
variations of external conditions. The three tests’ results shall be compliant with the “pass criteria”.
When a test implies a reaction from the remote pilot, the test procedure shall include the
“analysis + reaction” time of the remote pilot as a minimum delay of 3s (or adapted value if justified by
the manufacturer) between the issuing of the alert to the remote pilot and the initiation of an action by
the remote pilot.
For each test case, the behaviour of the UAS shall be recorded: 3D position of the UA, vertical and
horizontal position accuracy, ground speed or air speed, vertical speed, UTC time, status of alert,
identification of involved UGZ.
Tests shall be performed either on representative test benches (example: flight simulators, …) or
directly in operating conditions provided by the manufacturer’s instructions.
5.3.2 Loading: verification of the uploading of UGZ
The objective of the test is to verify that the UAS can correctly interpret any possible kind of valid
UGZ data.
The language to specify the UGZ is standardized.
The manufacturer shall refer to the test file available on the EASA website for the adequate sets of test
cases.
A minimum UGZ test case list includes all the following UGZ test cases:
— horizontal restrictions (5.3.3.1.2);
— vertical limits (5.3.3.1.3);
— time conditions (5.3.3.1.4);
— vertical limits in climb/descent (5.3.3.1.5).
The UAS manufacturer shall develop a means to compare the UGZ data used internally with the data
provided by EASA. The comparison can be performed by analysis of data recorded within the system.
The following tests shall be performed:
1) Download the test file from the EASA website;
2) update the system by uploading the data;
3) compare the data in the system with the data provided by EASA.
For each test, the tests procedure below shall be applied:
— for each attribute of the data model, one test UGZ for each possibility of valid values for discrete list
of values, or with a value within the valid domain shall be designed;
— for optional attributes, tests as for mandatory attributes, and one additional test UGZ without the
attribute shall be designed.
The test result shall mention when applicable the unit of the value, and the referential associated to the
value, verified against the referential of the internal data with which they are combined (e.g. altitude,
distance).
5.3.3 Warning
5.3.3.1 Alerting on potential breach of restriction
5.3.3.1.1 General
The tests defined in this paragraph aims at demonstrating compliance of the “geo-awareness” function,
taking into account the performance requirements defined in 5.2.
When the geofencing option is available and can be disabled, the tests shall be performed with and
without the geofencing function enabled.
While performing the tests, observe and record all visual, aural and haptic alerts encountered during
the test phase.
Verify by review of the manufacturer’s instructions that visual, aural and or haptic signals are described
and specified.
5.3.3.1.2 Test of horizontal restrictions
The objective is to verify the adequacy and timeliness of the alert issued to the remote pilot in case of
potential breach of a UGZ restriction according to the performance of the UA in all control modes
declared by the manufacturer’s instructions. The objective is to verify that an alert is provided to the
remote pilot if the flight path of the UA is breaching a UGZ.
Fly the UA in each combination of the following conditions and cases (every flight condition has to be
tested with every test case):
Flight conditions:
— condition 1: At the maximum airspeed, in the range of wind conditions declared in the
manufacturer’s instructions, or at maximum groundspeed if it is controlled by groundspeed instead
of airspeed;
— condition 2: if automatic control mode is used, create a flight path breaching a UGZ.
Cases relatively to the UGZ:
— case 1: Flight perpendicular to the boundary;
— case 2: Flight with a small angle with the boundary (<5°).

Key
Horizontal or vertical boundary

UA top view
UA face view
Figure 1 — Tests of alerting for horizontal limits
5.3.3.1.3 Test of vertical limits
The following use cases allow testing the correct behaviour of the “geo-awareness” regarding the
vertical definition of UGZ.
Fly or position the UA in the following conditions:
SIST EN 4709-003:
...