5.1. Remote aerodrome ATS procedural considerations

• ED Decision 2023/005/R found in: GM Remote Aerodrome Air Traffic Services (Jan 2026)

##### 5.1. Remote aerodrome ATS procedural considerations *ED Decision 2023/005/R* This section details recommendations on procedures related to remote aerodrome ATS. Some of these recommendations are of a general nature, whereas some are specifically related to operations from an RTC. — All formal interfaces with all stakeholders (as specified by Regulation (EU) 2017/373 [4], ATM/ANS.OR.B.005(f)) and contracted activities (as specified by Regulation (EU) 2017/373 [4], ATM/ANS.OR.B.015) should be re-evaluated to include items that are unique to remote aerodrome ATS, especially with regard to the communication between the remote ATS unit and the aerodrome. Such formal interfaces should be documented in local agreements. The need for coordination between the ATS unit and the respective aerodrome — and related aspects — is specifically covered in Chapter [7](#_DxCrossRefBm1764263624). — There might be cases where the ATS provider performs tasks which fall under the responsibility of the aerodrome operator. In case such tasks are to be continued to be performed by the ATS provider, following the introduction of remote aerodrome ATS, specific agreements between the ATS unit and the aerodrome operator should be in place[[18]](#_ftn18). Particular considerations regarding these tasks and contingency procedures should be included in the service level agreement / contract between ATS provider and aerodrome operator to achieve adequate redundancy measures in case of partial or single or multiple failures at the RTC. — Before initiating service provision, or before assuming responsibility for service provision, the ATCO/AFISO should be able to verify the status of the aerodrome (in terms of traffic, weather situation, etc.) and its related systems and a coordination and transfer of control of operational systems should take place when needed. — In today’s conventional tower operations, operating methods and procedures can sometimes differ between aerodromes due to local variations and practices. When providing service to several aerodromes from an RTC, there may be an opportunity to streamline and unify the operating methods and procedures for the aerodromes connected to the same RTC. — In today’s conventional tower operations there is often a lack of standardisation of systems and equipment between different aerodromes. ATCO/AFISO workstations and HMI are often different from one conventional tower to another. In order to support flexibility within an RTC regarding aerodrome and RTM allocation as well as to reduce ATCO/AFISO training needs and to contribute to the overall improvement of uniformity of ATM services — when providing service to several aerodromes from an RTC — it is recommended to unify the RTMs within the RTC in terms of HMI and equipment to the extent possible taking into account the different aerodromes to which services are provided. — When providing service to several aerodromes from an RTC, to support the flexibility of staff and RTM allocation between aerodromes, it is recommended that the RTC enables the transfer of responsibility of ATS for aerodromes between the RTMs within the RTC. If implemented, appropriate procedures for the transferring/merging/splitting of aerodromes between RTMs should be developed and documented. If the transferring/merging/splitting of aerodromes between RTMs is performed during ATS hours of operation, service provision should be uninterrupted. — When service can be provided to one aerodrome from different locations (RTC, conventional tower, stand-alone RTM), appropriate procedures for the transferring and assuming of responsibility of ATS between these locations should be developed and documented. Regulation (EU) 2017/373 [4] ATS.TR.225 ‘Responsibility for control’ applies. If the transfer of responsibility is performed during ATS hours of operation, service provision should be uninterrupted. --- [[18]](#_ftnref18) For further details, see Chapter [7](https://dxweb.easa.europa.eu/dx4/Topics/gm_rt_issue2_089.docx).