Commission Implementing Regulation (EU) 2017/373 of 1 March 2017 laying down common requirements for providers of air traffic management/air navigation services and other air traffic management network functions and their oversight, repealing Regulation (EC) No 482/2008, Implementing Regulations (EU) No 1034/2011, (EU) No 1035/2011 and (EU) 2016/1377 and amending Regulation (EU) No 677/2011 (Text with EEA relevance. )
Annex IVANNEX IV
In force · version of Oct 4, 2026
SPECIFIC REQUIREMENTS FOR PROVIDERS OF AIR TRAFFIC SERVICES
(Part-ATS)
SUBPART A — ADDITIONAL ORGANISATION REQUIREMENTS FOR PROVIDERS OF AIR TRAFFIC SERVICES (ATS.OR)
SECTION 1 — GENERAL REQUIREMENTS
ATS.OR.100 Ownership
(a) An air traffic services provider shall notify the competent authorities of: (1) its legal status, its ownership structure and any arrangements having a significant impact on control over its assets; (2) any links with organisations not involved in the provision of air navigation services, including commercial activities in which they are engaged either directly or through related undertakings, which account for more than 1 % of their expected revenue; furthermore, it shall notify any change of any single shareholding which represents 10 % or more of their total shareholding.
(b) An air traffic services provider shall take all necessary measures to prevent any situation of conflict of interests that could compromise the impartial and objective provision of its services.
ATS.OR.105 Open and transparent provision of service
In addition to point ATM/ANS.OR.A.075 of Annex III, the air traffic service provider shall neither engage in conduct that would have as its object or effect the prevention, restriction or distortion of competition, nor shall they engage in conduct that amounts to an abuse of a dominant position, in accordance with applicable Union and national law.
ATS.OR.110 Coordination between aerodrome operators and air traffic services providers
An air traffic services provider shall establish arrangements with the operator of the aerodrome at which it provides air traffic services to ensure adequate coordination of activities and services provided as well as exchange of relevant data and information.
ATS.OR.115 Coordination between military units and air traffic services providers
Without prejudice to Article 6 of Regulation (EC) No 2150/2005, an air traffic services provider shall ensure that its air traffic services units, either routinely or on request, in accordance with locally agreed procedures, provide appropriate military units with pertinent flight plan and other data concerning flights of civil aircraft in order to facilitate their identification.
ATS.OR.120 Coordination between meteorological services providers and air traffic services providers
(a) To ensure that aircraft receive the most up-to-date meteorological information for aircraft operations, an air traffic services provider shall make arrangements with the associated meteorological services provider for air traffic services personnel: (1) in addition to using indicating instruments, to report, if observed by air traffic services personnel or communicated by aircraft, such other meteorological elements as may be agreed upon; (2) to report as soon as possible meteorological phenomena of operational significance, if observed by air traffic services personnel or communicated by aircraft, which have not been included in the aerodrome meteorological report; (3) to report as soon as possible pertinent information concerning pre-eruption volcanic activity, volcanic eruptions and information concerning volcanic ash cloud. In addition, area control centres and flight information centres shall report the information to the associated meteorological watch office and volcanic ash advisory centres (VAACs).
(b) An air traffic services provider shall ensure that close coordination is maintained between area control centres, flight information centres and associated meteorological watch offices such that information on volcanic ash included in NOTAM and SIGMET messages is consistent.
ATS.OR.125 Coordination between aeronautical information services and air traffic services providers
(a) An air traffic services provider shall provide to the relevant aeronautical information services provider the aeronautical information to be published as necessary to permit the utilisation of such air traffic services.
(b) To ensure that the aeronautical information services providers obtain information to enable them to provide up-to-date preflight information and to meet the need for in-flight information, an air traffic services provider and aeronautical information services provider shall make arrangements to report to the responsible aeronautical information services provider, with a minimum of delay: (1) information on aerodrome conditions; (2) the operational status of associated facilities, services and navigation aids within their area of responsibility; (3) the occurrence of volcanic activity observed by air traffic services personnel or reported by aircraft; (4) any other information considered to be of operational significance.
(c) Before introducing changes to systems for air navigation under its responsibility, an air traffic services provider shall: (1) ensure close coordination with the aeronautical information services provider(s) concerned; (2) take due account of the time needed by the aeronautical information services provider for the preparation, production and issuance of relevant material for promulgation; (3) provide the information in a timely manner to the aeronautical information services provider concerned.
(d) An air traffic services provider shall observe the predetermined, internationally agreed aeronautical information regulation and control (AIRAC) effective dates in addition to 14 days postage time when submitting to aeronautical information services providers the raw information or data, or both, subject to the AIRAC cycle.
ATS.OR.127 Coordination by air traffic services providers in U-space airspace
Air traffic services providers shall:
(a) provide on a non-discriminatory basis the relevant traffic information regarding manned aircraft that is necessary as part of the common information services referred to in Commission Implementing Regulation (EU) 2021/664 ( 9 ) for a U-Space airspace established in the controlled airspace where the air traffic service provider is designated to provide its services;
(b) establish the coordination procedures and communication facilities between appropriate air traffic service units, U-space service providers and, where applicable, single common information service providers permitting provision of this data.
ATS.OR.130 Time in air traffic services
(a) An air traffic services provider shall ensure that air traffic services units are equipped with clocks indicating the time in hours, minutes and seconds, clearly visible from each operating position in the unit concerned.
(b) An air traffic services provider shall ensure that air traffic services unit clocks and other time-recording devices are checked as necessary to ensure correct time to within plus or minus 30 seconds of UTC. Wherever data link communications are utilised by an air traffic services unit, clocks and other time-recording devices shall be checked as necessary to ensure correct time to within 1 second of UTC.
(c) The correct time shall be obtained from a standard time station or, if not possible, from another unit which has obtained the correct time from such station.
ATS.OR.135 Contingency arrangements
An air traffic services provider shall develop contingency plans as required in point ATM/ANS.OR.A.070 of Annex III in close coordination with the air traffic services providers responsible for the provision of services in adjacent portions of airspace and, as appropriate, with airspace users concerned.
ATS.OR.140 Failure and irregularity of systems and equipment
An air traffic services provider shall establish appropriate arrangements for air traffic services units to immediately report any failure or irregularity of communication, navigation and surveillance systems or any other safety-significant systems or equipment which could adversely affect the safety or efficiency of flight operations or the provision of air traffic services, or both.
ATS.OR.145 Operation of air traffic control service
An air traffic services provider shall ensure that information on aircraft movements, together with a record of ATC clearances issued to such aircraft, are so displayed as to permit ready analysis in order to maintain an efficient flow of air traffic with adequate separation between aircraft.
ATS.OR.150 Transfer of responsibility for control and transfer of communications
Air traffic services provider shall establish applicable coordination procedures for transfer of responsibility for control of flights, including transfer of communications and transfer of control points, in letters of agreement and operation manuals, as appropriate.
SECTION 2 — SAFETY OF SERVICES
ATS.OR.200 Safety management system
An air traffic services provider shall have in place a safety management system (SMS), which may be an integral part of the management system required in point ATM/ANS.OR.B.005, that includes the following components:
(1) Safety policy and objectives (i) Management commitment and responsibility regarding safety which shall be included in the safety policy. (ii) Safety accountabilities regarding the implementation and maintenance of the SMS and the authority to make decisions regarding safety. (iii) Appointment of a safety manager who is responsible for the implementation and maintenance of an effective SMS; (iv) Coordination of an emergency response planning with other service providers and aviation undertakings that interface with the ATS provider during the provision of its services. (v) SMS documentation that describes all the elements of the SMS, the associated SMS processes and the SMS outputs.
(2) Safety risk management (i) A process to identify hazards associated to its services which shall be based on a combination of reactive, proactive and predictive methods of safety data collection. (ii) A process that ensures analysis, assessment and control of the safety risks associated with identified hazards. (iii) A process to ensure that its contribution to the risk of aircraft accidents is minimised as far as is reasonably practicable.
(3) Safety assurance (i) Safety performance monitoring and measurement means to verify the safety performance of the organisation and validate the effectiveness of the safety risk controls. (ii) A process to identify changes which may affect the level of safety risk associated with its service and to identify and manage the safety risks that may arise from those changes. (iii) A process to monitor and assess the effectiveness of the SMS to enable the continuous improvement of the overall performance of the SMS.
(4) Safety promotion (i) Training programme that ensures that the personnel are trained and competent to perform their SMS duties. (ii) Safety communication that ensures that the personnel are aware of the SMS implementation.
ATS.OR.205 Safety assessment and assurance of changes to the functional system
(a) For any change notified in accordance with point ATM/ANS.OR.A.045(a)(1), the air traffic services provider shall: (1) ensure that a safety assessment is carried out covering the scope of the change, which is: (i) the equipment, procedural and human elements being changed; (ii) interfaces and interactions between the elements being changed and the remainder of the functional system; (iii) interfaces and interactions between the elements being changed and the context in which it is intended to operate; (iv) the life cycle of the change from definition to operations including transition into service; (v) planned degraded modes of operation of the functional system; and (2) provide assurance, with sufficient confidence, via a complete, documented and valid argument that the safety criteria identified via the application of point ATS.OR.210 are valid, will be satisfied and will remain satisfied.
(b) An air traffic services provider shall ensure that the safety assessment referred to in point (a) comprises: (1) the identification of hazards; (2) the determination and justification of the safety criteria applicable to the change in accordance with point ATS.OR.210; (3) the risk analysis of the effects related to the change; (4) the risk evaluation and, if required, risk mitigation for the change such that it can meet the applicable safety criteria; (5) the verification that: (i) the assessment corresponds to the scope of the change as defined in point (a)(1); (ii) the change meets the safety criteria; (6) the specification of the monitoring criteria necessary to demonstrate that the service delivered by the changed functional system will continue to meet the safety criteria.
ATS.OR.210 Safety criteria
(a) An air traffic services provider shall determine the safety acceptability of a change to a functional system, based on the analysis of the risks posed by the introduction of the change, differentiated on basis of types of operations and stakeholder classes, as appropriate.
(b) The safety acceptability of a change shall be assessed by using specific and verifiable safety criteria, where each criterion is expressed in terms of an explicit, quantitative level of safety risk or another measure that relates to safety risk.
(c) An air traffic services provider shall ensure that the safety criteria: (1) are justified for the specific change, taking into account the type of change; (2) when fulfilled, predict that the functional system after the change will be as safe as it was before the change or the air traffic services provider shall provide an argument justifying that: (i) any temporary reduction in safety will be offset by future improvement in safety; or (ii) any permanent reduction in safety has other beneficial consequences; (3) when taken collectively, ensure that the change does not create an unacceptable risk to the safety of the service; (4) support the improvement of safety whenever reasonably practicable.
ATS.OR.215 Licensing and medical certification requirements for air traffic controllers
An air traffic services provider shall ensure that air traffic controllers are properly licensed and hold a valid medical certificate, in accordance with Regulation (EU) 2015/340.
SECTION 3 — SPECIFIC HUMAN FACTORS REQUIREMENTS FOR AIR TRAFFIC CONTROL SERVICE PROVIDERS
ATS.OR.300 Scope
This section establishes the requirements to be met by the air traffic control service provider with regard to human performance in order to:
(a) prevent and mitigate the risk that air traffic control service is provided by air traffic controllers with problematic use of psychoactive substances;
(b) prevent and mitigate the negative effects of stress on air traffic controllers to ensure the safety of air traffic;
(c) prevent and mitigate the negative effects of fatigue on air traffic controllers to ensure the safety of air traffic.
ATS.OR.305 Responsibilities of air traffic control service providers with regard to the problematic use of psychoactive substances by air traffic controllers
(a) An air traffic control service provider shall develop and implement a policy, with related procedures, in order to ensure that the problematic use of psychoactive substances does not affect the provision of air traffic control service.
(b) Without prejudice to provisions laid down in Directive 95/46/EC of the European Parliament and of the Council ( 10 ) and to the applicable national legislation on testing of individuals, the air traffic control service provider shall develop and implement an objective, transparent and non-discriminatory procedure for the detection of cases of problematic use of psychoactive substances by air traffic controllers. This procedure shall take into account provisions laid down in point ATCO.A.015 of Regulation (EU) 2015/340.
(c) The procedure in point (b) shall be approved by the competent authority.
ATS.OR.310 Stress
In accordance with point ATS.OR.200, an air traffic control service provider shall:
(a) develop and maintain a policy for the management of air traffic controllers' stress, including the implementation of a critical incident stress management programme;
(b) provide air traffic controllers with education and information programmes on the prevention of stress, including critical incident stress, complementing human factors training provided in accordance with Sections 3 and 4 of Subpart D of Annex I to Regulation (EU) 2015/340.
ATS.OR.315 Fatigue
In accordance with point ATS.OR.200, an air traffic control service provider shall:
(a) develop and maintain a policy for the management of air traffic controllers' fatigue;
(b) provide air traffic controllers with information programmes on the prevention of fatigue, complementing human factors training provided in accordance with Sections 3 and 4 of Subpart D of Annex I to Regulation (EU) 2015/340.
ATS.OR.320 Air traffic controllers' rostering system(s)
(a) An air traffic control service provider shall develop, implement and monitor a rostering system in order to manage the risks of occupational fatigue of air traffic controllers through a safe alternation of duty and rest periods. Within the rostering system, the air traffic control service provider shall specify the following elements: (1) maximum consecutive working days with duty; (2) maximum hours per duty period; (3) maximum time providing air traffic control service without breaks; (4) the ratio of duty periods to breaks when providing air traffic control service; (5) minimum rest periods; (6) maximum consecutive duty periods encroaching the night time, if applicable, depending upon the operating hours of the air traffic control unit concerned; (7) minimum rest period after a duty period encroaching the night time; (8) minimum number of rest periods within a roster cycle.
(b) An air traffic control services provider shall consult those air traffic controllers who will be subject to the rostering system, or, as applicable, their representatives, during its development and its application, to identify and mitigate risks concerning fatigue which could be due to the rostering system itself.
SECTION 4
REQUIREMENTS FOR COMMUNICATIONS
ATS.OR.400 Aeronautical mobile service (air–ground communications) – general
(a) An air traffic services provider shall use voice or data link, or both, in air–ground communications for air traffic services purposes.
(b) When air-ground voice communications are based on 8,33 kHz channel spacing, an air traffic services provider shall ensure that: (1) all items of equipment for air–ground voice communications include the 8,33 kHz channel spacing capability and are able to tune to 25 kHz spaced channels; (2) all voice frequency assignments have the 8,33 kHz channel spacing capability; (3) the procedures applicable to aircraft equipped with radios having the 8,33 kHz channel spacing capability and to aircraft which are not equipped with such equipment, subject to transfer between air traffic services units, are specified in the letters of agreement between those ATS units; (4) aircraft not equipped with radios having the 8,33 kHz channel spacing capability can be accommodated, provided they can be safely handled within the capacity limits of the air traffic management system on UHF or on 25 kHz frequency assignments; and (5) it communicates, on an annual basis, to the Member State that has designated it their plans for the handling of State aircraft which are not equipped with radios having the 8,33 kHz channel spacing capability, taking into account the capacity limits associated with the procedures published by the Member States in their national aeronautical information publications (AIPs).
(c) When direct pilot–controller two-way voice or data link communications are used for the provision of air traffic control service, recording facilities shall be provided by the air traffic services provider on all such air–ground communication channels.
(d) When direct air–ground two-way voice or data link communications are used for the provision of flight information service, including aerodrome flight information service (AFIS), recording facilities on all such air–ground communication channels shall be provided by the air traffic services provider, unless otherwise prescribed by the competent authority.
ATS.OR.405 Use and availability of the VHF emergency frequency
(a) As laid down in Article 3d, the VHF emergency frequency (121,500 MHz) shall be used for genuine emergency purposes, including any of the following: (1) to provide a clear channel between aircraft in distress or emergency and a ground station when the normal channels are being utilised for other aircraft; (2) to provide a VHF communication channel between aircraft and aerodromes, not normally used by international air services, in case of an emergency condition arising; (3) to provide a common VHF communication channel between aircraft, either civil or military, and between such aircraft and surface services, involved in common search and rescue operations, prior to changing when necessary to the appropriate frequency; (4) to provide air-ground communication with aircraft when airborne equipment failure prevents the use of the regular channels; (5) to provide a channel for the operation of emergency locator transmitters (ELTs), and for communication between survival craft and aircraft engaged in search and rescue operations; (6) to provide a common VHF channel for communication between civil aircraft and intercepting aircraft or intercept control units and between civil or intercepting aircraft and air traffic services units in the event of interception of the civil aircraft.
(b) An air traffic services provider shall provide the frequency 121.500 MHz at: (1) all area control centres and flight information centres; (2) aerodrome control towers and approach control units serving international aerodromes and international alternate aerodromes; (3) any additional location designated by the competent authority, where the provision of that frequency is considered necessary to ensure immediate reception of distress calls or to serve the purposes specified in point (a).
ATS.OR.410 Aeronautical mobile service (air-ground communications) – flight information service
(a) An air traffic services provider shall ensure, to the practicable extent and as approved by the competent authority, that air-ground communication facilities enable two-way communications to take place between a flight information centre and appropriately equipped aircraft flying anywhere within the flight information region.
(b) An air traffic services provider shall ensure that air-ground communication facilities enable direct, rapid, continuous and static-free two-way communications to take place between an AFIS unit and appropriately equipped aircraft operating within the airspace referred to in point ATS.TR.110(a)(3).
ATS.OR.415 Aeronautical mobile service (air–ground communications) – area control service
An air traffic services provider shall ensure that:
(a) air–ground communication facilities enable two-way voice communications to take place between a unit providing area control service and appropriately equipped aircraft flying anywhere within the control area or areas; and
(b) air–ground communications facilities enable two-way data communications to take place between a unit providing area control service and appropriately equipped aircraft flying within the airspace referred to in point AUR.COM.2001 of Commission Implementing Regulation (EU) 2023/1770 ( 11 ), to operate the data link services referred to point (1) (a) of point AUR.COM.2005 of that Implementing Regulation.
ATS.OR.420 Aeronautical mobile service (air-ground communications) – approach control service
(a) An air traffic services provider shall ensure that air-ground communication facilities enable direct, rapid, continuous and static-free two-way communications to take place between the unit providing approach control service and appropriately equipped aircraft under its control.
(b) Where the unit providing approach control service functions as a separate unit, air-ground communications shall be conducted over communication channels provided for its exclusive use.
ATS.OR.425 Aeronautical mobile service (air-ground communications) – aerodrome control service
(a) An air traffic services provider shall ensure that air-ground communication facilities enable direct, rapid, continuous and static-free two-way communications to take place between an aerodrome control tower and appropriately equipped aircraft operating at any distance within 45 km (25 NM) of the aerodrome concerned.
(b) Where conditions warrant, an air traffic services provider shall provide separate communication channels for the control of traffic operating on the manoeuvring area.
ATS.OR.430 Aeronautical fixed service (ground–ground communications) – general
(a) An air traffic services provider shall ensure that direct-speech or data link communications, or both, are used in ground–ground communications for air traffic services purposes.
(b) When communication for ATC coordination purposes is supported by automation, an air traffic services provider shall ensure that: (1) the appropriate means are implemented to automatically receive, store, process, extract and display, and transmit the relevant flight information; (2) the failures or anomalies of such automated coordination are presented clearly to the air traffic controller or controllers responsible for coordinating flights at a transferring unit; (3) the warnings related to system information exchange are presented to the relevant working positions; (4) the information about the relevant system information exchange processes is provided to the air traffic controllers; (5) air traffic controllers are provided with the means to modify the flight information exchanged.
ATS.OR.435 Aeronautical fixed service (ground-ground communications) – communication within a flight information region
(a) Communications between air traffic services units (1) An air traffic services provider shall ensure that a flight information centre has facilities for communications with the following units providing a service within its area of responsibility: (i) the area control centre; (ii) approach control units; (iii) aerodrome control towers; (iv) AFIS units. (2) An air traffic services provider shall ensure that an area control centre, in addition to being connected with the flight information centre as prescribed in point (1), has facilities for communications with the following units providing a service within its area of responsibility: (i) approach control units; (ii) aerodrome control towers; (iii) AFIS units; (iv) air traffic services reporting offices, when separately established. (3) An air traffic services provider shall ensure that an approach control unit, in addition to being connected with the flight information centre and the area control centre as prescribed in points (1) and (2), has facilities for communications with: (i) the associated aerodrome control tower or towers; (ii) with relevant AFIS unit or units; (iii) the associated air traffic services reporting office or offices, when separately established. (4) An air traffic services provider shall ensure that an aerodrome control tower or an AFIS unit, in addition to being connected with the flight information centre, the area control centre and the approach control unit as prescribed in points (1), (2) and (3), has facilities for communications with the associated air traffic services reporting office, when separately established.
(b) Communications between air traffic services units and other units (1) An air traffic services provider shall ensure that a flight information centre and an area control centre have facilities for communications with the following units providing a service within their respective area of responsibility: (i) appropriate military units; (ii) the meteorological services provider or providers serving the centre; (iii) the aeronautical telecommunication station serving the centre; (iv) appropriate aircraft operators’ offices; (v) the rescue coordination centre or, in the absence of such centre, any other appropriate emergency service; (vi) the international NOTAM office serving the centre. (2) An air traffic services provider shall ensure that an approach control unit, an aerodrome control tower and an AFIS unit have facilities for communications with the following units providing a service within their respective area of responsibility: (i) appropriate military units; (ii) rescue and emergency services (including ambulance, firefighting etc.); (iii) the meteorological services provider serving the unit concerned; (iv) the aeronautical telecommunication station serving the unit concerned; (v) the unit providing apron management service, when separately established. (3) The communication facilities required under points (b)(1)(i) and (b)(2)(i) shall include provisions for rapid and reliable communications between the air traffic services unit concerned and the military unit or units responsible for control of interception operations within the area of responsibility of the air traffic services unit, in order to fulfil obligations set out in Section 11 of the Annex to Implementing Regulation (EU) No 923/2012.
(c) Description of communication facilities (1) The communication facilities required under point (a), point (b)(1)(i) and points (b)(2)(i), (b)(2)(ii) and (b)(2)(iii) shall include provisions for: (i) communications by direct speech alone, or in combination with data link communications, whereby for the purpose of transfer of control using radar or ADS-B, the communications are established instantaneously, and for other purposes, the communications are normally established within 15 seconds; (ii) printed communications, when a written record is required; the message transit time for such communications is no longer than 5 minutes. (2) In all cases not covered by point (c)(1), the communication facilities shall include provisions for: (i) communications by direct speech alone, or in combination with data link communications, whereby the communications are normally established within 15 seconds; (ii) printed communications, when a written record is required; the message transit time for such communications are no longer than 5 minutes. (3) In all cases where automatic transfer of data to or from air traffic services computers, or both ways, is required, suitable facilities for automatic recording shall be provided. (4) The communication facilities required under points (b)(2)(i);(ii);(iii) shall include provisions for communications by direct speech arranged for conference communications whereby the communications are normally established within 15 seconds. (5) All facilities for direct-speech or data link communications between air traffic services units and between air traffic services units and other units described under points (b)(1) and (b)(2) shall be provided with automatic recording.
ATS.OR.440 Aeronautical fixed service (ground-ground communications) – communication between flight information regions
(a) An air traffic services provider shall ensure that flight information centres and area control centres have facilities for communications with all adjacent flight information centres and area control centres. Those communication facilities shall in all cases include provisions for messages in a form suitable for retention as a permanent record, and delivery in accordance with transit times specified by ICAO regional air navigation agreements.
(b) An air traffic services provider shall ensure that facilities for communications between area control centres serving contiguous control areas, in addition, include provisions for direct-speech and, where applicable, data link communications, with automatic recording, whereby for the purpose of transfer of control using ATS surveillance data, the communications are established instantaneously, and for other purposes, the communications are normally established within 15 seconds.
(c) When so required by agreement between the States concerned in order to eliminate or reduce the need for interceptions in the event of deviations from assigned track, an air traffic services provider shall ensure that facilities for communications between adjacent flight information centres or area control centres other than those mentioned in point (b): (1) include provisions for direct speech alone, or in combination with data link communications; (2) permit communications to be established normally within 15 seconds; (3) are provided with automatic recording.
(d) An air traffic services provider concerned shall ensure that adjacent air traffic services units are connected in all cases where special circumstances exist.
(e) Wherever local conditions are such that it is necessary to clear aircraft into a controlled airspace prior to departure, the air traffic services provider or providers concerned shall ensure that the air traffic services units delivering the clearance to the aircraft are connected with the air traffic control unit serving the adjacent controlled airspace.
(f) The communication facilities supporting connections to be established in accordance with points (d) and (e) shall include provisions for communications by direct speech alone, or in combination with data link communications, with automatic recording, whereby for the purpose of transfer of control using ATS surveillance, the communications are established instantaneously, and for other purposes, the communications are normally established within 15 seconds.
(g) An air traffic services provider shall provide suitable facilities for automatic recording in all cases where automatic exchange of data between air traffic services computers is required.
ATS.OR.445 Communications for the control or management of vehicles other than aircraft on manoeuvring areas at aerodromes
(a) Except where communication by a system of visual signals is deemed to be adequate, an air traffic services provider shall ensure two-way radiotelephony communication facilities for either of the following services: (1) aerodrome control service for the control of vehicles on the manoeuvring area; (2) AFIS for the management of vehicles on the manoeuvring area where such service is provided in accordance with point ATS.TR.305(f).
(b) The need for separate communication channels for the control or for the management of the vehicles on the manoeuvring area shall be determined subject to a safety assessment.
(c) Automatic recording facilities on all channels referred to in point (b) shall be provided.
ATS.OR.446 Surveillance data
(a) Air traffic services providers shall not use data from Mode S interrogators that operate under the responsibility of a third country if the allocation of the interrogator code has not been coordinated.
(b) Air traffic services providers shall ensure that the necessary capabilities are implemented to allow air traffic controllers to establish individual aircraft identification using the downlinked aircraft identification feature, as detailed in Appendix 1.
(c) Air traffic service providers shall ensure seamless operations within the airspace under their responsibility and at the boundary with adjacent airspaces by applying appropriate minimum requirements for the separation of aircraft.
ATS.OR.450 Automatic recording of surveillance data
An air traffic services provider shall ensure that surveillance data from primary and secondary radar equipment or other systems (e.g. ADS-B, ADS-C), used as an aid to air traffic services, are automatically recorded for use in accident and incident investigations, search and rescue, air traffic services and surveillance systems evaluation and training.
ATS.OR.455 Retention of recorded information and data
(a) An air traffic services provider shall retain for a period of at least 30 days the following: (1) recordings of communications channels, as specified in points ATS.OR.400(b) and (c); (2) recordings of data and communications, as specified in points ATS.OR.435(c)(3) and (5); (3) automatic recordings, as specified in point ATS.OR.440; (4) recordings of communications, as specified in point ATS.OR.445; (5) recordings of data, as specified in point ATS.OR.450; (6) paper flight progress strips, electronic flight progress and coordination data.
(b) When the recordings and logs listed in point (a) are pertinent to accident and incident investigations, they shall be retained for longer periods until it is evident that they will no longer be required.
ATS.OR.460 Background communication and aural environment recording
(a) Unless otherwise prescribed by the competent authority, air traffic services units shall be equipped with devices that record background communication and the aural environment at air traffic controller’s, or the flight information service officer’s, or the AFIS officer’s work stations, as applicable, capable of retaining the information recorded during at least the last 24 hours of operation.
(b) Such recordings shall only be used for the investigation of accidents and incidents which are subject to mandatory reporting.
SECTION 5
REQUIREMENTS FOR INFORMATION
ATS.OR.500 Meteorological information – General
(a) An air traffic services provider shall ensure that up-to-date information on existing and forecast meteorological conditions is made available to the relevant air traffic services units as necessary for the performance of their respective functions.
(b) An air traffic services provider shall ensure that available detailed information on the location, vertical extent, direction and rate of movement of meteorological phenomena in the vicinity of the aerodrome, and particularly in the climb-out and approach areas, which could be hazardous to aircraft operations, is supplied to the relevant air traffic services units.
(c) The information in points (a) and (b) shall be supplied in such a form as to require a minimum of interpretation on the part of air traffic services personnel and with a frequency which satisfies the requirements of the air traffic services units concerned.
ATS.OR.505 Meteorological information for flight information centres and area control centres
(a) An air traffic services provider shall ensure that flight information centres and area control centres are supplied with the meteorological information stipulated in point MET.OR.245(f) of Annex V, particular emphasis being given on the occurrence or expected occurrence of deterioration in a weather element as soon as this can be determined. Those reports and forecasts shall cover the flight information region or control area and such other areas, if so prescribed by the competent authority.
(b) An air traffic services provider shall ensure that flight information centres and area control centres are provided, at suitable intervals, with current pressure data for setting altimeters, for locations specified by the flight information centre or area control centre concerned.
ATS.OR.510 Meteorological information for units providing approach control service
(a) An air traffic services provider shall ensure that units providing approach control service are supplied with meteorological information for the airspace and the aerodromes with which they are concerned, as stipulated in point MET.OR.242(b) of Annex V.
(b) An air traffic services provider shall ensure that, where multiple anemometers are used, the displays to which they are related are clearly marked to identify the runway and section of the runway monitored by each anemometer.
(c) An air traffic services provider shall ensure that units providing approach control service are provided with current pressure data for setting altimeters, for locations specified by the unit providing approach control service.
(d) An air traffic services provider shall ensure that units providing approach control service for final approach, landing and take-off are equipped with surface wind display or displays. The display or displays shall be related to the same location or locations of observation and be fed from the same sensor or sensors as the corresponding display or displays in the aerodrome control tower or AFIS unit, or both, and in the aeronautical meteorological station, where such a station exists.
(e) An air traffic services provider shall ensure that units providing approach control service for final approach, landing and take-off at aerodromes where runway visual range values are assessed by instrumental means, are equipped with display or displays permitting read-out of the current runway visual range values. The display or displays shall be related to the same location or locations of observation and be fed from the same sensor or sensors as the corresponding display or displays in the aerodrome control tower or AFIS unit, or both, and in the aeronautical meteorological station, where such a station exists.
(f) An air traffic services provider shall ensure that units providing approach control service for final approach, landing and take-off at aerodromes where the height of cloud base is assessed by instrumental means, are equipped with display or displays permitting read-out of the current values of the height of cloud base. The displays shall be related to the same location or locations of observations and be fed from the same sensor or sensors as the corresponding display or displays in the aerodrome control tower or AFIS unit, or both, and in the aeronautical meteorological station, where such a station exists.
(g) An air traffic services provider shall ensure that units providing approach control service for final approach, landing and take-off are supplied with available information on wind shear which could adversely affect aircraft on the approach or take-off paths or during circling approach.
ATS.OR.515 Meteorological information for aerodrome control towers and AFIS units
(a) An air traffic services provider shall ensure that aerodrome control towers and, unless otherwise prescribed by the competent authority, AFIS units are supplied with meteorological information for the aerodrome with which they are concerned as stipulated in point MET.OR.242(a) of Annex V.
(b) An air traffic services provider shall ensure that aerodrome control towers and AFIS units are provided with current pressure data for setting altimeters for the aerodrome concerned.
(c) An air traffic services provider shall ensure that aerodrome control towers and AFIS units are equipped with surface wind display or displays. The display or displays shall be related to the same location or locations of observation and be fed from the same sensor or sensors as the corresponding display or displays in the aeronautical meteorological station, where such a station exists. Where multiple sensors are used, the displays to which they are related shall be clearly marked to identify the runway and section of the runway monitored by each sensor.
(d) An air traffic services provider shall ensure that aerodrome control towers and AFIS units at aerodromes where runway visual range values are measured by instrumental means, are equipped with display or displays permitting read-out of the current runway visual range values. The display or displays shall be related to the same location or locations of observation and be fed from the same sensor or sensors as the corresponding display or displays in the aeronautical meteorological station, where such a station exists.
(e) An air traffic services provider shall ensure that aerodrome control towers and AFIS units at aerodromes where the height of cloud base is assessed by instrumental means, are equipped with display or displays permitting read-out of the current values of the height of cloud base. The displays shall be related to the same location or locations of observations and be fed from the same sensor or sensors as the corresponding display or displays in the aerodrome control tower and AFIS units and in the aeronautical meteorological station, where such a station exists.
(f) An air traffic services provider shall ensure that aerodrome control tower and AFIS units are supplied with available information on wind shear which could adversely affect aircraft on the approach or take-off paths or during circling approach, and aircraft on the runway during the landing roll or take-off run.
(g) An air traffic services provider shall ensure that aerodrome control towers and AFIS units and/or other appropriate units are supplied with aerodrome warnings, in accordance with point MET.OR.215(b) of Annex V.
ATS.OR.520 Information on aerodrome conditions and the operational status of associated facilities
An air traffic services provider shall ensure that aerodrome control towers, AFIS units and units providing approach control service are kept currently informed of the operationally significant conditions of the movement area, including the existence of temporary hazards, and the operational status of any associated facilities at the aerodrome or aerodromes with which they are concerned, as reported by the aerodrome operator.
ATS.OR.525 Information on the operational status of navigation services
(a) An air traffic services provider shall ensure that air traffic services units are kept currently and timely informed of the operational status of radio navigation services and visual aids essential for take-off, departure, approach and landing procedures within their area of responsibility, and of those radio navigation services and visual aids essential for surface movement.
(b) An air traffic services provider shall establish appropriate arrangements in accordance with point ATM/ANS.OR.B.005(f) of Annex III to ensure that information in point (a) of this point with regard to the GNSS services is provided.
ATS.OR.530 Forwarding of braking action information
If an air traffic services provider receives by a voice communication a special air-report concerning braking action which does not correspond to what was reported, it shall inform without delay the appropriate aerodrome operator.
SUBPART B — TECHNICAL REQUIREMENTS FOR PROVIDERS OF AIR TRAFFIC SERVICES (ATS.TR)
SECTION 1 — GENERAL REQUIREMENTS
ATS.TR.100 Objectives of the air traffic services (ATS)
The objectives of the air traffic services shall be to:
(a) prevent collisions between aircraft;
(b) prevent collisions between aircraft on the manoeuvring area and obstructions on that area;
(c) expedite and maintain an orderly flow of air traffic;
(d) provide advice and information useful for the safe and efficient conduct of flights;
(e) notify appropriate organisations regarding aircraft in need of search and rescue aid, and assist such organisations as required.
ATS.TR.105 Divisions of the air traffic services
The air traffic services shall comprise the services identified as follows:
(a) the air traffic control service, to accomplish the objectives as in points (a), (b) and (c) of point ATS.TR.100, this service being divided in three parts as follows: (1) area control service: the provision of air traffic control service for controlled flights, except for those parts of such flights described in points (2) and (3) of this point, in order to accomplish the objectives established in points (a) and (c) of point ATS.TR.100; (2) approach control service: the provision of air traffic control service for those parts of controlled flights associated with arrival or departure, in order to accomplish the objectives established in points (a) and (c) of point ATS.TR.100; and (3) aerodrome control service: the provision of air traffic control service for aerodrome traffic, except for those parts of flights described in point (2) of this point, in order to accomplish the objectives established in points (a), (b) and (c) of point ATS.TR.100.
(b) the flight information service or air traffic advisory service, or both, to accomplish the objective established in point (d) of point ATS.TR.100;
(c) the alerting service, to accomplish the objective established in point (e) of point ATS.TR.100.
ATS.TR.110 Establishment of the units providing air traffic services
(a) The air traffic services shall be provided by units established as follows: (1) flight information centres shall be established to provide flight information service and alerting service within flight information regions unless the responsibility of providing such services within a flight information region is assigned to an air traffic control unit having adequate facilities for the discharge of such responsibility; (2) air traffic control units shall be established to provide air traffic control service, flight information service and alerting service within control areas, control zones and at controlled aerodromes; (3) AFIS units shall be established to provide flight information service and alerting service at AFIS aerodromes and within the airspace associated with such aerodromes.
(b) Air traffic services reporting office or offices or other arrangements shall be established for the purpose of receiving reports concerning air traffic services and flight plans submitted before departure.
ATS.TR.115 Identification of air traffic services units
(a) Air traffic services units shall be unambiguously named as follows: (1) an area control centre or flight information centre shall normally be identified by the name of a nearby town or city or geographic feature or area; (2) an aerodrome control tower or approach control unit shall normally be identified by the name of the aerodrome at which it is providing services or by the name of a nearby town or city or geographic feature or area; (3) an AFIS unit shall normally be identified by the name of the aerodrome at which it is providing services or by the name of a nearby town or city or geographic feature or area.
(b) The name of the air traffic services units and services shall be complemented by one of the following suffixes, as appropriate: (1) area control centre – CONTROL; (2) approach control – APPROACH; (3) approach control radar arrivals – ARRIVAL; (4) approach control radar departures – DEPARTURE; (5) air traffic control unit (in general) when providing ATS surveillance services – RADAR; (6) aerodrome control – TOWER; (7) surface movement control – GROUND; (8) clearance delivery – DELIVERY; (9) flight information centre – INFORMATION; (10) AFIS unit – INFORMATION.
ATS.TR.120 Language for communication between air traffic services units
Except when communications between air traffic services units are conducted in a mutually agreed language, the English language shall be used for such communications.
ATS.TR.125 Expression of vertical position of aircraft
(a) For flights in areas where a transition altitude is established, the vertical position of the aircraft shall, except as provided for in point (b), be expressed in terms of altitudes at or below the transition altitude and in terms of flight levels at or above the transition level. While passing through the transition layer, the vertical position shall be expressed in terms of flight levels when climbing and in terms of altitudes when descending.
(b) When an aircraft which has been given clearance to land, or when at AFIS aerodromes an aircraft which has been informed that the runway is available for landing, is completing its approach using atmospheric pressure at aerodrome elevation (QFE), the vertical position of the aircraft shall be expressed in terms of height above aerodrome elevation during that portion of its flight for which QFE may be used, except that it shall be expressed in terms of height above runway threshold elevation: (1) for instrument runways if the threshold is 2 m (7 ft) or more below the aerodrome elevation; (2) for precision approach runways.
ATS.TR.130 Determination of the transition level
(a) The appropriate air traffic services unit shall establish the transition level to be used in areas where a transition altitude is established, for the appropriate period of time on the basis of QNH (altimeter subscale setting to obtain elevation when on the ground) reports and forecast mean sea level pressure, if required.
(b) The transition level shall be located above the transition altitude such that at least a nominal 300 m (1 000 ft) vertical separation minimum is ensured between aircraft flying concurrently at the transition altitude and at the transition level.
ATS.TR.135 Minimum cruising level for IFR flights
(a) Air traffic control units shall not assign cruising levels below the minimum flight altitudes established by the Member States, except when specifically authorised by the competent authority.
(b) Air traffic control units shall: (1) determine the lowest usable flight level or levels for the whole or parts of the control area for which they are responsible; (2) assign flight levels at or above such level or levels; (3) pass the lowest usable flight level or levels on to pilots on request.
ATS.TR.140 Provision of altimeter setting information
(a) The appropriate air traffic services units shall at all times have available for transmission to aircraft in flight, on request, the information required to determine the lowest flight level which will ensure adequate terrain clearance on routes or on segment of routes for which this information is required.
(b) Flight information centres and area control centres shall have available for transmission to aircraft, on request, an appropriate number of QNH reports or forecast pressures for the flight information regions and control areas for which they are responsible, and for those adjacent.
(c) The flight crew shall be provided with the transition level in due time prior to reaching it during descent.
(d) Except when it is known that the aircraft has already received the information in a directed transmission, an QNH altimeter setting shall be included in: (1) the descent clearance, when first cleared to an altitude below the transition level; (2) approach clearances or clearances to enter the traffic circuit; (3) taxi clearances for departing aircraft.
(e) An QFE altimeter setting as described in point ATS.TR.125(b) shall be provided to aircraft on request or on a regular basis in accordance with local arrangements.
(f) The appropriate air traffic services units shall round down the altimeter settings provided to aircraft to the nearest lower whole hectopascal.
ATS.TR.145 Suspension of visual flight rules operations on and in the vicinity of an aerodrome
(a) Any or all VFR operations on and in the vicinity of an aerodrome may be suspended whenever safety requires such action by any of the following units, persons or authorities: (1) the approach control unit or the appropriate area control centre; (2) the aerodrome control tower; (3) the competent authority.
(b) When any or all VFR operations on and in the vicinity of an aerodrome are suspended, the aerodrome control tower shall observe the following procedures: (1) hold all VFR departures; (2) recall all local flights operating under VFR or obtain approval for special VFR operations; (3) notify the approach control unit or area control centre as appropriate of the action taken; (4) notify all operators, or their designated representatives, of the reason for taking such action, if necessary or requested.
ATS.TR.150 Aeronautical ground lights
An air traffic services provider shall establish procedures for the operation of aeronautical ground lights, whether or not they are on or in the vicinity of an aerodrome.
ATS.TR.155 ATS surveillance services
(a) An air traffic services provider may use ATS surveillance systems in the provision of air traffic services. In such case, the air traffic services provider shall specify the functions for which ATS surveillance information is used.
(b) When providing ATS surveillance services, an air traffic services provider shall: (1) ensure that the ATS surveillance system or systems in use provide for a continuously updated presentation of surveillance information, including position indications; (2) when air traffic control service is provided: (i) determine the number of aircraft simultaneously provided with ATS surveillance services which can be safely handled under the prevailing circumstances; (ii) provide air traffic controllers at all times with full and up-to-date information regarding: A. established minimum flight altitudes within the area of responsibility; B. the lowest usable flight level or levels determined in accordance with points ATS.TR.130 and ATS.TR.135; C. established minimum altitudes applicable to procedures based on tactical vectoring and direct routing, including the necessary temperature correction or method to correct the effect of low temperatures on minimum altitudes.
(c) An air traffic services provider shall, in accordance with the functions for which ATS surveillance information is used in the provision of air traffic services, establish procedures for: (1) establishing identification of aircraft; (2) providing position information to aircraft; (3) vectoring aircraft; (4) providing navigation assistance to aircraft; (5) providing information regarding adverse weather, if applicable; (6) transferring of control of aircraft; (7) failure of ATS surveillance system or systems; (8) SSR transponder failure, in accordance with the provisions of Section 13 of the Annex to Implementing Regulation (EU) No 923/2012; (9) ATS surveillance-based safety-related alerts and warnings, when implemented; (10) interruption or termination of ATS surveillance service.
(d) Before providing an ATS surveillance service to an aircraft, identification shall be established and the pilot informed. Thereafter, identification shall be maintained until the termination of the ATS surveillance service. If identification is subsequently lost, the pilot shall be informed accordingly and, when applicable, appropriate instructions shall be issued.
(e) When an identified controlled flight is observed to be on a conflicting path with an unknown aircraft, deemed to constitute a collision hazard, the pilot of the controlled flight shall, whenever practicable: (1) be informed of the unknown aircraft, and, if the pilot so requests or if the situation so warrants in the opinion of the controller, avoiding action shall be suggested; and (2) be notified when the conflict no longer exists.
(f) Unless otherwise prescribed by the competent authority, verification of the pressure-altitude-derived level information displayed shall be effected at least once by each suitably equipped air traffic services unit on initial contact with the aircraft concerned or, if this is not feasible, as soon as possible thereafter.
(g) Only verified pressure-altitude-derived level information shall be used to determine that aircraft performed either of the following actions: (1) maintain a level; (2) vacate a level; (3) pass a level in climb or descent; (4) reach a level.
ATS.TR.160 Provision of air traffic services for flight testing
Additional or alternative conditions and procedures to those contained in this Subpart B, to be applied by air traffic services units for the provision of air traffic services for flight testing, may be specified by the competent authority.
SECTION 2
AIR TRAFFIC CONTROL SERVICE
ATS.TR.200 Application
Air traffic control service shall be provided:
(a) to all IFR flights in airspace Classes A, B, C, D and E;
(b) to all VFR flights in airspace Classes B, C and D;
(c) to all special VFR flights;
(d) to all aerodrome traffic at controlled aerodromes.
ATS.TR.205 Provision of air traffic control service
The parts of air traffic control service described in point ATS.TR.105(a) shall be provided by the various units as follows:
(a) area control service by either of the following units: (1) an area control centre; (2) the unit providing approach control service in a control zone or in a control area of limited extent which is designated primarily for the provision of approach control service and where no area control centre is established;
(b) approach control service by either of the following units: (1) an approach control unit when it is necessary or desirable to establish a separate unit; (2) an aerodrome control tower or area control centre when it is necessary or desirable to combine under the responsibility of one unit the functions of the approach control service with those of the aerodrome control service or the area control service;
(c) aerodrome control service: by an aerodrome control tower.
ATS.TR.210 Operation of air traffic control service
(a) In order to provide air traffic control service, an air traffic control unit shall: (1) be provided with information on the intended movement of each aircraft, or variations therefrom, and with current information on the actual progress of each aircraft; (2) determine from the information received, the relative positions of known aircraft to each other; (3) issue clearances, instructions or information, or all of them, for the purpose of preventing collision between aircraft under its control and of expediting and maintaining an orderly flow of traffic; (4) coordinate clearances as necessary with other units: (i) whenever an aircraft might otherwise conflict with traffic operated under the control of such other units; (ii) before transferring control of an aircraft to such other units.
(b) Clearances issued by air traffic control units shall provide separation: (1) between all flights in airspace Classes A and B; (2) between IFR flights in airspace Classes C, D and E; (3) between IFR flights and VFR flights in airspace Class C; (4) between IFR flights and special VFR flights; (5) between special VFR flights unless otherwise prescribed by the competent authority. Where requested by the pilot of an aircraft and agreed by the pilot of the other aircraft and if so prescribed by the competent authority for the cases listed under point (2) of the first paragraph in airspace Classes D and E, a flight may be cleared subject to maintaining own separation in respect of a specific portion of the flight below 3 050 m (10 000 ft) during climb or descent, during day in visual meteorological conditions.
(c) Except for cases of operations on parallel or near-parallel runways referred to in point ATS.TR.255, or when a reduction in separation minima in the vicinity of aerodromes can be applied, separation by an air traffic control unit shall be obtained by at least one of the following: (1) vertical separation, obtained by assigning different levels selected from the table of cruising levels in Appendix 3 to the Annex to Implementing Regulation (EU) No 923/2012, except that the correlation of levels to track as prescribed therein shall not apply whenever otherwise indicated in appropriate aeronautical information publications or ATC clearances. The vertical separation minimum shall be a nominal 300 m (1 000 ft) up to and including FL 410 and a nominal 600 m (2 000 ft) above that level. Geometric height information shall not be used to establish vertical separation; (2) horizontal separation, obtained by providing either of the following: (i) longitudinal separation, by maintaining an interval between aircraft operating along the same, converging or reciprocal tracks, expressed in time or distance; (ii) lateral separation, by maintaining aircraft on different routes or in different geographical areas.
(d) When the air traffic controller becomes aware that the type of separation or minimum used to separate two aircraft cannot be maintained, the air traffic controller shall establish another type of separation or another minimum prior to the time when the current separation minimum would be infringed.
ATS.TR.215 Selection and notification of separation minima for the application of point ATS.TR.210(c)
(a) The selection of separation minima for application within a given portion of airspace shall be made by the air traffic services provider responsible for the provision of air traffic services and approved by the competent authority concerned.
(b) For traffic that will pass from one into the other of neighbouring airspaces and for routes that are closer to the common boundary of the neighbouring airspaces than the separation minima applicable in the circumstances, the selection of separation minima shall be made in consultation with the air traffic services providers responsible for the provision of air traffic services in neighbouring airspace.
(c) Details of the selected separation minima and of their areas of application shall be notified: (1) to the air traffic services units concerned; (2) to pilots and aircraft operators through aeronautical information publications, where separation is based on the use by aircraft of specified navigation aids or specified navigation techniques.
ATS.TR.220 Application of wake turbulence separation
(a) Air traffic control units shall apply wake turbulence separation minima to aircraft in the approach and departure phases of flight in either of the following circumstances: (1) an aircraft is operating directly behind another aircraft at the same altitude or less than 300 m (1 000 ft) below it; (2) both aircraft are using the same runway, or parallel runways separated by less than 760 m (2 500 ft); (3) an aircraft is crossing behind another aircraft, at the same altitude or less than 300 m (1 000 ft) below it.
(b) Paragraph (a) shall not apply to arriving VFR flights and to arriving IFR flights executing visual approach when the aircraft has reported the preceding aircraft in sight and has been instructed to follow and maintain own separation from that aircraft. In those cases, the air traffic control unit shall issue caution for wake turbulence.
ATS.TR.225 Responsibility for control
(a) A controlled flight shall be under the control of only one air traffic control unit at any given time.
(b) Responsibility for the control of all aircraft operating within a given block of airspace shall be vested in a single air traffic control unit. However, control of an aircraft or groups of aircraft may be delegated to other air traffic control units provided that coordination between all air traffic control units concerned is assured.
ATS.TR.230 Transfer of responsibility for control
(a) Place or time of transfer The responsibility for the control of an aircraft shall be transferred from one air traffic control unit to another as follows: (1) Between two units providing area control service The responsibility for the control of an aircraft shall be transferred from a unit providing area control service in a control area to the unit providing area control service in an adjacent control area at the time of crossing the common control area boundary as estimated by the area control centre having control of the aircraft or at such other point or time as has been agreed between the two units. (2) Between a unit providing area control service and a unit providing approach control service or between two units providing approach control service The responsibility for the control of an aircraft shall be transferred from one unit to another, and vice versa, at a point or time agreed between the two units. (3) Between a unit providing approach control service and an aerodrome control tower (i) Arriving aircraft – The responsibility for the control of an arriving aircraft shall be transferred, as specified in letters of agreement and operation manuals, as appropriate, from the unit providing approach control service to the aerodrome control tower when the aircraft is in either of the following states: (A) is in the vicinity of the aerodrome, and: (a) it is considered that approach and landing will be completed in visual reference to the ground, or (b) it has reached uninterrupted VMC; (B) is at a prescribed point or level; (C) has landed. (ii) Departing aircraft – The responsibility for control of a departing aircraft shall be transferred, as specified in letters of agreement and operation manuals, as appropriate, from the aerodrome control tower to the unit providing approach control service: (A) when VMC prevail in the vicinity of the aerodrome: (a) prior to the time the aircraft leaves the vicinity of the aerodrome, or (b) prior to the aircraft entering instrument meteorological conditions (IMC), or (c) at a prescribed point or level; (B) when IMC prevail at the aerodrome: (a) immediately after the aircraft is airborne, or (b) at a prescribed point or level. (4) Between control sectors or positions within the same air traffic control unit The responsibility for control of an aircraft shall be transferred from one control sector or position to another control sector or position within the same air traffic control unit at a point, level or time, as specified in air traffic services unit instructions.
(b) Coordination of transfer (1) Responsibility for control of an aircraft shall not be transferred from one air traffic control unit to another without the consent of the accepting control unit, which shall be obtained in accordance with points (2), (3), (4) and (5). (2) The transferring control unit shall communicate to the accepting control unit the appropriate parts of the current flight plan and any control information pertinent to the transfer requested. (3) Where transfer of control is to be effected using ATS surveillance systems, the control information pertinent to the transfer shall include information regarding the position and, if required, the track and speed of the aircraft, as observed by ATS surveillance systems immediately prior to the transfer. (4) Where transfer of control is to be effected using ADS-C data, the control information pertinent to the transfer shall include the four-dimensional position and other information as necessary. (5) The accepting control unit shall: (i) indicate its ability to accept control of the aircraft on the terms specified by the transferring control unit, unless by prior agreement between the two units concerned the absence of any such indication is understood to signify acceptance of the terms specified, or indicate any necessary changes thereto; (ii) specify any other information or clearance for a subsequent portion of the flight, which it requires the aircraft to have at the time of transfer. (6) Unless otherwise specified by an agreement between the two control units concerned, the accepting control unit shall not notify the transferring control unit when it has established two-way voice or data link communications, or both, with and assumed control of the aircraft concerned. (7) Standardised phraseology shall be used in the coordination between air traffic services units or sectors, or both. Only when standardised phraseology cannot serve an intended transmission, plain language shall be used.
(c) The coordination of transfer of control between units that provide area control service within the ICAO EUR region, or when so agreed with or between other air traffic control units, shall be supported by automated processes as defined in Appendix 2.
ATS.TR.235 ATC clearances
(a) ATC clearances shall be based solely on the requirements for providing air traffic control service. (1) Clearances shall be issued solely for expediting and separating air traffic and be based on known traffic conditions which affect safety in aircraft operation. Such traffic conditions include not only aircraft in the air and on the manoeuvring area over which control is being exercised, but also any vehicular traffic or other obstructions not permanently installed on the manoeuvring area in use. (2) Air traffic control units shall issue such ATC clearances as necessary to prevent collisions and to expedite and maintain an orderly flow of air traffic. (3) ATC clearances shall be issued early enough to ensure that they are transmitted to the aircraft in sufficient time for it to comply with them. (4) When the pilot-in-command of an aircraft informs an air traffic control unit that an ATC clearance is not satisfactory, the air traffic control unit shall issue an amended clearance, if practicable. (5) When vectoring or assigning a direct routing not included in the flight plan, which takes an IFR flight off published ATS route or instrument procedure, an air traffic controller providing ATS surveillance service shall issue clearances such that the prescribed obstacle clearance exists at all times until the aircraft reaches the point where the pilot re-joins the flight plan route, or joins a published ATS route or instrument procedure.
(b) Contents of clearances An ATC clearance shall indicate: (1) aircraft identification as shown in the flight plan; (2) clearance limit; (3) route of flight: (i) the route of flight shall be detailed in each clearance when deemed necessary; (ii) the phrase ‘cleared flight planned route’ shall not be used when granting a re-clearance; (4) level or levels of flight for the entire route or part thereof and changes of levels if required; (5) any necessary instructions or information on other matters, such as ATFM departure slot if applicable, approach or departure manoeuvres, communications and the time of expiry of the clearance.
(c) In order to facilitate the delivery of the elements in point (b), an air traffic services provider shall assess the necessity for establishing standard departure and arrival routes and associated procedures to facilitate the: (1) safe, orderly and expeditious flow of air traffic; (2) description of the route and procedure in ATC clearances.
(d) Clearances for transonic flight (1) The ATC clearance relating to the transonic acceleration phase of a supersonic flight shall extend at least to the end of that phase. (2) The ATC clearance relating to the deceleration and descent of an aircraft from supersonic cruise to subsonic flight shall seek to provide for uninterrupted descent, at least during the transonic phase.
(e) Changes in clearance regarding route or level (1) When issuing a clearance covering a requested change in route or level, the exact nature of the change shall be included in the clearance. (2) When traffic conditions will not permit clearance of a requested change, the word ‘UNABLE’ shall be used. When warranted by circumstances, an alternative route or level shall be offered.
(f) Conditional clearances Conditional phrases, such as ‘behind landing aircraft’ or ‘after departing aircraft’, shall not be used for movements affecting the active runway or runways except when the aircraft or vehicles concerned are seen by the appropriate air traffic controller and pilot. The aircraft or vehicle causing the condition in the clearance issued shall be the first aircraft or vehicle to pass in front of the other aircraft concerned. In all cases, a conditional clearance shall be given in the following order and consist of: (1) the call sign; (2) the condition; (3) the clearance; (4) a brief reiteration of the condition.
(g) Read-back of clearances, instructions and safety-related information (1) The air traffic controller shall listen to the read-back concerning safety-related parts of ATC clearances and instructions as specified in points SERA.8015(e)(1) and (2) of the Annex to Implementing Regulation (EU) No 923/2012, to ascertain that the clearance or instruction, or both, have been correctly acknowledged by the flight crew and shall take immediate action to correct any discrepancies revealed by the read-back. (2) Voice read-back of CPDLC messages shall not be required unless otherwise specified by the air traffic services provider.
(h) Coordination of clearances An ATC clearance shall be coordinated between air traffic control units to cover the entire route of an aircraft or a specified portion thereof as follows. (1) An aircraft shall be cleared for the entire route to the aerodrome of first intended landing in either of the following situations: (i) when it has been possible, prior to departure, to coordinate the clearance between all the units under whose control the aircraft will come; (ii) when there is reasonable assurance that prior coordination will be effected between those units under whose control the aircraft will subsequently come. (2) When coordination as in point (1) has not been achieved or is not anticipated, the aircraft shall be cleared only to that point where coordination is reasonably assured; prior to reaching such point, or at such point, the aircraft shall receive further clearance, holding instructions being issued as appropriate. (3) When prescribed by the air traffic services unit, aircraft shall contact a downstream air traffic control unit, for the purpose of receiving a downstream clearance prior to the transfer of control point. (i) Aircraft shall maintain the necessary two-way communication with the current air traffic control unit whilst obtaining a downstream clearance. (ii) A clearance issued as a downstream clearance shall be clearly identifiable as such to the pilot. (iii) Unless coordinated, downstream clearances shall not affect the aircraft’s original flight profile in any airspace, other than that of the air traffic control unit responsible for the delivery of the downstream clearance. (4) When an aircraft intends to depart from an aerodrome within a control area to enter another control area within a period of 30 minutes, or such other specific period of time as has been agreed between the area control centres concerned, coordination with the subsequent area control centre shall be effected prior to issuance of the departure clearance. (5) When an aircraft intends to leave a control area for flight outside controlled airspace, and will subsequently re-enter the same or another control area, a clearance from the point of departure to the aerodrome of first intended landing may be issued. Such clearance or revisions thereto shall apply only to those portions of the flight conducted within controlled airspace.
ATS.TR.237 Dynamic reconfiguration of the U-space airspace
Air traffic control units shall:
(a) temporarily limit the area within the designated U-space airspace where UAS operations can take place in order to accommodate short-term changes in manned traffic demand by adjusting the lateral and vertical limits of the U-space airspace;
(b) ensure that the relevant U-space service providers and, where applicable, single common information service providers are notified in a timely and effective manner of the activation, deactivation and temporary limitations of the designated U-space airspace.
ATS.TR.240 Control of persons and vehicles at controlled aerodromes
(a) The movement of persons or vehicles, including towed aircraft, on the manoeuvring area of an aerodrome shall be controlled by the aerodrome control tower as necessary to avoid hazard to them or to aircraft landing, taxiing or taking off.
(b) In conditions where low-visibility procedures are in operation: (1) persons and vehicles operating on the manoeuvring area of an aerodrome shall be restricted to the essential minimum, and particular regard shall be given to the requirements to protect the critical and sensitive area or areas of radio navigation aids; (2) subject to the provisions in point (c), the method or methods to separate vehicles and taxiing aircraft shall be as specified by the air traffic services provider and approved by the competent authority taking into account the aids available; (3) when mixed ILS and MLS Category II or Category III precision instrument operations are taking place to the same runway continuously, the more restrictive ILS or MLS critical and sensitive areas shall be protected.
(c) Emergency vehicles proceeding to the assistance of an aircraft in distress shall be afforded priority over all other surface movement traffic.
(d) Subject to the provisions in point (c), vehicles on the manoeuvring area shall be required to comply with the following rules: (1) vehicles and vehicles towing aircraft shall give way to aircraft which are landing, taking off or taxiing; (2) vehicles shall give way to other vehicles towing aircraft; (3) vehicles shall give way to other vehicles in accordance with air traffic services unit instructions; (4) notwithstanding the provisions of points (1), (2) and (3), vehicles and vehicles towing aircraft shall comply with instructions issued by the aerodrome control tower.
ATS.TR.245 Use of surface movement surveillance equipment at aerodromes
Where deemed necessary, in the absence of visual observation of all or part of the manoeuvring area or to supplement visual observation, advanced surface movement guidance and control systems (A-SMGCS) or other suitable surveillance equipment, shall be utilised by the air traffic services unit in order to:
(a) monitor the movements of aircraft and vehicles on the manoeuvring area;
(b) provide directional information to pilots and vehicle drivers as necessary;
(c) provide advice and assistance for the safe and efficient movement of aircraft and vehicles on the manoeuvring area.
ATS.TR.250 Essential traffic and essential local traffic information
(a) Essential traffic information shall be given to controlled flights concerned whenever they constitute essential traffic to each other.
(b) Essential local traffic information known to the air traffic controller shall be given without delay to departing and arriving aircraft concerned.
ATS.TR.255 Operations on parallel or near-parallel runways
When independent or dependent operations on instrument approach to or departure from parallel or near-parallel runways are conducted, procedures shall be established by the air traffic services provider and approved by the competent authority.
ATS.TR.260 Selection of the runway-in-use
The aerodrome control tower shall select the runway-in-use for take-off and landing of aircraft taking into consideration the surface wind speed and direction as well as other local relevant factors, such as:
(a) runway configuration;
(b) meteorological conditions;
(c) instrument approach procedures;
(d) approach and landing aids available;
(e) aerodrome traffic circuits and air traffic conditions;
(f) length of the runway or runways;
(g) other factors indicated in local instructions.
ATS.TR.265 Control of aerodrome surface traffic in low-visibility conditions
(a) When there is a requirement for traffic to operate on the manoeuvring area in conditions of visibility which prevent the aerodrome control tower from applying visual separation between aircraft, and between aircraft and vehicles, the following shall apply: (1) at the intersection of taxiways, an aircraft or vehicle on a taxiway shall not be permitted to hold closer to the other taxiway than the holding position limit defined by intermediate holding positions, stop bar or taxiway intersection marking, in accordance with the applicable aerodrome design specifications; (2) the longitudinal separation method on taxiways shall be as specified for each particular aerodrome by the air traffic services provider and approved by the competent authority, taking into account the characteristics of the aids available for surveillance and control of ground traffic, the complexity of the aerodrome layout and the characteristics of the aircraft using the aerodrome.
(b) Procedures applicable to the start and continuation of low-visibility operations shall be established in accordance with point ATS.OR.110 and shall be approved by the competent authority.
ATS.TR.270 Authorisation of special VFR
(a) Special VFR flights may be authorised to operate within a control zone, subject to an ATC clearance. Except when otherwise permitted by the competent authority for helicopters in special cases such as, but not limited to, police, medical, search and rescue operations and firefighting flights, the following additional conditions shall apply: (1) such special VFR flights may be conducted during day only, unless otherwise permitted by the competent authority; (2) by the pilot: (i) clear of cloud and with the surface in sight; (ii) the flight visibility is not less than 1 500 m or, for helicopters, not less than 800 m; (iii) fly at a speed of 140 kt IAS or less to give adequate opportunity to observe other traffic and any obstacles in time to avoid a collision; (3) An air traffic control unit shall not issue a special VFR clearance to aircraft to take off or land at an aerodrome within a control zone, or enter the aerodrome traffic circuit within a control zone, when the reported meteorological conditions at that aerodrome are below the following minima: (i) the ground visibility is less than 1 500 m or, for helicopters, less than 800 m; (ii) the ceiling is less than 180 m (600 ft).
(b) An air traffic control unit shall handle requests for such an authorisation individually.
SECTION 3
FLIGHT INFORMATION SERVICE
ATS.TR.300 Application
(a) Flight information service shall be provided by the appropriate air traffic services units to all aircraft which are likely to be affected by the information and which are in either of the following situations: (1) provided with air traffic control service; (2) otherwise known to the relevant air traffic services units.
(b) Where air traffic services units provide both flight information service and air traffic control service, the provision of air traffic control service shall have precedence over the provision of flight information service whenever the provision of air traffic control service so requires.
(c) A flight information service provider shall establish arrangements for: (1) recording and transmission of information on the progress of flights; (2) coordination and transfer of responsibility for the provision of flight information service.
ATS.TR.305 Scope of flight information service
(a) Flight information service shall include the provision of pertinent: (1) SIGMET and AIRMET information; (2) information concerning pre-eruption volcanic activity, volcanic eruptions and volcanic ash clouds; (3) information concerning the release into the atmosphere of radioactive materials or toxic chemicals; (4) information on changes in the availability of radio navigation services; (5) information on changes in the condition of aerodromes and associated facilities, including information on the state of the aerodrome movement areas when they are affected by snow, ice or significant depth of water; (6) information on unmanned free balloons; (7) information on abnormal aircraft configuration and condition; (7a) information on unmanned aircraft; (8) any other information likely to affect safety.
(b) Flight information service provided to flights shall include, in addition to that outlined in point (a), the provision of information concerning: (1) weather conditions reported or forecast at departure, destination and alternate aerodromes; (2) collision hazards, to aircraft operating in airspace Classes C, D, E, F and G; (3) for flight over water areas, in so far as practicable and when requested by a pilot, any available information such as radio call sign, position, true track, speed, etc. of surface vessels in the area; (4) messages, including clearances, received from other air traffic services units to relay to aircraft.
(c) AFIS provided to flights shall include, in addition to relevant items outlined in points (a) and (b), the provision of information concerning: (1) collision hazards with aircraft, vehicles and persons operating on the manoeuvring area; (2) the runway-in-use.
(d) Air traffic services units shall transmit, as soon as practicable, special and non-routine air-reports to: (1) other aircraft concerned; (2) the associated meteorological watch office in accordance with Appendix 5 to Implementing Regulation (EU) No 923/2012; (3) other air traffic services units concerned. Transmissions to aircraft shall be repeated at a frequency and continued for a period of time which shall be determined by the air traffic services unit concerned.
(e) Flight information service provided to VFR flights shall include, in addition to that outlined in point (a), the provision of available information concerning traffic and weather conditions along the route of flight that are likely to make operation under the visual flight rules impracticable.
(f) When so prescribed by the competent authority, the AFIS unit shall manage the movement of vehicles and persons on the manoeuvring area in accordance with the set or subset of provisions in point ATS.TR.240.
ATS.TR.310 Voice-automatic terminal information service (Voice-ATIS) broadcasts
(a) Voice-automatic terminal information service (Voice-ATIS) broadcasts shall be provided at aerodromes where there is a requirement to reduce the communication load on the air traffic services VHF air-ground communication channels. When provided, they shall comprise either of the following: (1) one broadcast serving arriving aircraft; (2) one broadcast serving departing aircraft; (3) one broadcast serving both arriving and departing aircraft; (4) two broadcasts serving arriving and departing aircraft respectively at those aerodromes where the length of a broadcast serving both arriving and departing aircraft would be excessively long.
(b) A discrete VHF frequency shall, whenever practicable, be used for Voice-ATIS broadcasts. If a discrete frequency is not available, the transmission may be made on the voice channel or channels of the most appropriate terminal navigation aid or aids, preferably a VOR, provided the range and readability are adequate and the identification of the navigation aid is sequenced with the broadcast so that the latter is not obliterated.
(c) Voice-ATIS broadcasts shall not be transmitted on the voice channel of an ILS.
(d) Whenever Voice-ATIS is provided, the broadcast shall be continuous and repetitive.
(e) The information contained in the current broadcast shall immediately be made known to the air traffic services unit or units concerned with the provision to aircraft of information relating to approach, landing and take-off, whenever the message has not been prepared by that unit or those units.
(f) Voice-ATIS broadcasts provided at designated aerodromes for use by international air services shall be available in the English language as a minimum.
ATS.TR.315 Data link-automatic terminal information service (D-ATIS)
(a) Where a D-ATIS supplements the existing availability of Voice-ATIS, the information shall be identical in both content and format to the applicable Voice-ATIS broadcast. Where real-time meteorological information is included but the data remains within the parameters of the significant change criteria established in points MET.TR.200(e) and (f) of Annex V, the content, for the purpose of maintaining the same designator, shall be considered identical.
(b) Where a D-ATIS supplements the existing availability of Voice-ATIS and the ATIS requires updating, Voice-ATIS and D-ATIS shall be updated simultaneously.
ATS.TR.320 Automatic terminal information service (voice and/or data link)
(a) Whenever Voice-ATIS or D-ATIS, or both, are provided: (1) the information communicated shall relate to a single aerodrome; (2) the information communicated shall be updated immediately when a significant change occurs; (3) the preparation and dissemination of the ATIS message shall be the responsibility of the air traffic services provider; (4) individual ATIS messages shall be identified by a designator in the form of a letter of the spelling alphabet in accordance with point SERA.14020 of the Annex to Implementing Regulation (EU) No 923/2012. Designators assigned to consecutive ATIS messages shall be in alphabetical order; (5) aircraft shall acknowledge receipt of the information upon establishing communication with the air traffic services unit providing approach control service or the aerodrome control tower or AFIS unit, as appropriate; (6) the appropriate air traffic services unit shall, when replying to the message in point (5) or, in the case of arriving aircraft, at such other time as may be prescribed by the competent authority, provide the aircraft with the current altimeter setting; (7) the meteorological information shall be extracted from the local routine report or local special report.
(b) When rapidly changing meteorological conditions make it inadvisable to include the meteorological information as in point (a)(7) in the ATIS, the ATIS messages shall indicate that the relevant meteorological information will be given on initial contact with the appropriate air traffic services unit.
(c) Information contained in a current ATIS, the receipt of which has been acknowledged by the aircraft concerned, need not be included in a directed transmission to the aircraft, with the exception of the altimeter setting, which shall be provided in accordance with point (a).
(d) If an aircraft acknowledges receipt of an ATIS that is no longer current, the air traffic services unit shall without delay take either of the following actions: (1) communicate to the aircraft any element of information which has to be updated; (2) instruct the aircraft to obtain the current ATIS information.
ATS.TR.325 VOLMET broadcasts and D-VOLMET broadcasts
When so prescribed by the competent authority, HF or VHF VOLMET broadcasts, or D-VOLMET service, or all of those, shall be provided, using standard radiotelephony phraseologies.
SECTION 4
ALERTING SERVICE
ATS.TR.400 Application
(a) Alerting service shall be provided by the air traffic services units: (1) for all aircraft provided with air traffic control service; (2) in so far as practicable, to all other aircraft having filed a flight plan or otherwise known to the air traffic services; (3) to any aircraft known or believed to be the subject of unlawful interference.
(b) Flight information centres or area control centres shall serve as the central point for collecting all information relevant to a state of emergency of an aircraft operating within the flight information region or control area concerned and for forwarding such information to the appropriate rescue coordination centre.
(c) In the event of a state of emergency arising to an aircraft while it is under the control of an aerodrome control tower or approach control unit or in contact with an AFIS unit, such unit shall notify immediately the flight information centre or area control centre responsible which shall in turn notify the rescue coordination centre, except that notification of the area control centre, flight information centre, or rescue coordination centre shall not be required if the nature of the emergency is such that the notification would be superfluous.
(d) Nevertheless, the aerodrome control tower or approach control unit responsible or the relevant AFIS unit shall first alert and take other necessary steps to set in motion all appropriate local rescue and emergency organisations which can give the immediate assistance required, in accordance with local instructions, whenever either of the following situations occurs: (1) an aircraft accident has occurred on or in the vicinity of the aerodrome; (2) information is received that the safety of an aircraft which is or will come under the jurisdiction of the aerodrome control tower or of the AFIS unit may have or has been impaired; (3) requested by the flight crew; (4) when otherwise deemed necessary or desirable or the urgency of the situation so requires.
ATS.TR.405 Notification to rescue coordination centres
(a) Without prejudice to any other circumstances that may render such notification advisable, air traffic services units shall, except as prescribed in point ATS.TR.420(a), notify rescue coordination centres immediately when an aircraft is considered to be in a state of emergency in accordance with the following: (1) Uncertainty phase when either of the following situations applies: (i) no communication has been received from an aircraft within a period of 30 minutes after the time a communication should have been received, or from the time an unsuccessful attempt to establish communication with such aircraft was first made, whichever is the earlier; (ii) an aircraft fails to arrive within 30 minutes of the estimated time of arrival last notified to or estimated by air traffic services units, whichever is the later. Uncertainty phase does not apply when no doubt exists as to the safety of the aircraft and its occupants. (2) Alert phase when either of the following situations applies: (i) following the uncertainty phase, subsequent attempts to establish communication with the aircraft or inquiries to other relevant sources have failed to reveal any news of the aircraft; (ii) an aircraft has been cleared to land and fails to land within 5 minutes of the estimated time of landing and communication has not been re-established with the aircraft; (iii) at AFIS aerodromes, under circumstances as prescribed by the competent authority; (iv) information has been received which indicates that the operating efficiency of the aircraft has been impaired, but not to the extent that a forced landing is likely; (v) an aircraft is known or believed to be the subject of unlawful interference. Points (i) to (iv) do not apply when evidence exists that would allay apprehension as to the safety of the aircraft and its occupants. (3) Distress phase when either of the following situations applies: (i) following the alert phase, further unsuccessful attempts to establish communication with the aircraft and more widespread unsuccessful inquiries point to the probability that the aircraft is in distress; (ii) the fuel on board is considered to be exhausted, or to be insufficient to enable the aircraft to reach safety; (iii) information is received which indicates that the operating efficiency of the aircraft has been impaired to the extent that a forced landing is likely; (iv) information is received or it is reasonably certain that the aircraft is about to make or has made a forced landing, Distress phase does not apply when there is reasonable certainty that the aircraft and its occupants are not threatened by grave and imminent danger and do not require immediate assistance.
(b) The notification shall contain such of the following information as is available in the order listed: (1) INCERFA, ALERFA or DETRESFA, as appropriate to the phase of the emergency; (2) agency and person calling; (3) nature of the emergency; (4) significant information from the flight plan; (5) unit which made last contact, time and means used; (6) last position report and how it was determined; (7) colour and distinctive marks of aircraft; (8) dangerous goods carried as cargo; (9) any action taken by the reporting office; (10) other pertinent remarks.
(c) Such part of the information specified in point (b), which is not available at the time the notification is made to a rescue coordination centre, shall be sought by an air traffic services unit prior to the declaration of a distress phase where time permits and where there is reasonable certainty that this phase will eventuate.
(d) Further to the notification specified in point (a), air traffic services units shall, without delay, furnish the rescue coordination centre with either of the following: (1) any useful additional information, especially on the development of the state of emergency through subsequent phases; (2) information that the emergency situation no longer exists.
ATS.TR.410 Use of communication facilities
Air traffic services units shall, as necessary, use all available communication facilities to endeavour to establish and maintain communication with an aircraft in a state of emergency, and to request news of the aircraft.
ATS.TR.415 Plotting aircraft in a state of emergency
When a state of emergency is considered to exist, the air traffic services unit or units aware of the emergency shall plot the flight of the aircraft involved on a chart or other appropriate tool in order to determine the probable future position of the aircraft and its maximum range of action from its last known position.
ATS.TR.420 Information to the operator
(a) When an area control centre or a flight information centre decides that an aircraft is in the uncertainty or the alert phase, it shall, when practicable, advise the aircraft operator prior to notifying the rescue coordination centre.
(b) Whenever practicable, an area control centre or flight information centre shall, without delay, communicate all information notified to the rescue coordination centre to the aircraft operator.
ATS.TR.425 Information to aircraft operating in the vicinity of an aircraft in a state of emergency
(a) When it has been established by an air traffic services unit that an aircraft is in a state of emergency, other aircraft known to be in the vicinity of the aircraft involved shall, except as provided in point (b), be informed of the nature of the emergency as soon as practicable.
(b) When an air traffic services unit knows or believes that an aircraft is being subjected to unlawful interference, no reference shall be made in air traffic services air-ground communications to the nature of the emergency unless it has first been referred to in communications from the aircraft involved and it is certain that such reference will not aggravate the situation.
Appendix 1 Identification of individual aircraft using the downlinked aircraft identification feature as required by point ATS.OR.446(b) The downlinked aircraft identification feature shall be used as follows to establish individual aircraft identification: (a) The air traffic services provider shall declare to the Network Manager the airspace volumes where individual aircraft identification is established using the downlinked aircraft identification feature. (b) The conspicuity SSR code A1000 shall be assigned to aircraft where individual aircraft identification is established by using the downlinked aircraft identification feature. (c) Except when one of the conditions set out in point (d) apply, the conspicuity SSR code A1000 shall be assigned to departing aircraft or to aircraft for which, in accordance with point (g), a code change is required, where the following conditions apply: (1) the downlinked aircraft identification matches the corresponding entry in the flight plan for that aircraft; (2) the Network Manager has communicated that the particular aircraft is eligible for the assignment of the conspicuity SSR code A1000. (d) The conspicuity SSR code A1000 shall not be assigned to aircraft referred to in point (c) if any of the following conditions apply: (1) contingency measures that require the assignment of discrete SSR codes to aircraft have been put in place by an air navigation service provider that experiences unplanned ground surveillance sensor outages; (2) exceptional military contingency measures require air navigation service providers to assign discrete SSR codes to aircraft; (3) an aircraft which is eligible for the assignment of the conspicuity SSR code A1000 established in accordance with point (c) exits or is otherwise diverted outside the airspace volume referred to in point (a). (e) Aircraft that are not assigned the conspicuity SSR code A1000 established in accordance with point (c) shall be assigned an SSR code that complies with a code allocation list agreed by the Member States and coordinated with third countries. (f) When an SSR code has been assigned to an aircraft, a check shall be made at the earliest opportunity to confirm that the SSR code set by the pilot is identical to that assigned to the flight. (g) SSR codes assigned to aircraft being transferred from air traffic services providers in neighbouring States shall be automatically checked to see whether the assignments can be retained in compliance with a code allocation list agreed by the Member States and coordinated with third countries. (h) Formal arrangements with the following minimum content shall be established with neighbouring air navigation service providers that establish individual aircraft identification by using discrete SSR codes: (1) an obligation on the neighbouring air navigation service providers to transfer aircraft with verified discrete SSR codes assigned in compliance with a code allocation list agreed by the Member States and coordinated with third countries; (2) an obligation to notify accepting units about any observed irregularity in the operation of airborne constituents of surveillance systems; (i) air traffic services providers shall ensure that the assignment of discrete SSR codes in compliance with a code allocation list agreed by the Member States and coordinated with third countries to establish individual aircraft identification complies with the following: (1) the SSR codes are automatically assigned to aircraft in compliance with a code allocation list agreed by the Member States and coordinated with third countries; (2) the SSR codes assigned to aircraft being transferred from air navigation service providers in neighbouring States are checked to see whether the assignments can be retained in compliance with a code allocation list agreed by the Member States and coordinated with third countries; (3) the SSR codes are classified into different categories to allow for differentiated code assignment; (4) the SSR codes from the different categories referred to in point (3) are assigned according to the directions of flights; (5) multiple simultaneous assignments of the same SSR code are made to flights that operate in code conflict-free directions; (6) the controllers are automatically informed when SSR code assignments are unintentionally duplicated.;
Appendix 2 Processes to be implemented for automated coordination as required by point ATS.TR.230(c) A. The mandatory processes to be implemented between units that provide area control service, or when so agreed with or between other air traffic control units, shall be the following: (a) Notification (1) The flight information subject to the notification process shall include as a minimum: (i) aircraft identification, (ii) SSR mode and code (if available), (iii) departure aerodrome, (iv) estimate data, (v) destination aerodrome, (vi) number and type of aircraft, (vii) type of flight, (viii) equipment capability and status. (2) The content of the ‘equipment capability and status’ information shall include reduced vertical separation minima (RVSM) and the 8,33 kHz channel spacing capability as a minimum. Other items may be included in accordance with the letters of agreement. (3) The notification process shall be performed at least once for each eligible flight planned to cross boundaries unless the flight is the subject of the pre-departure notification and coordination process. (4) The eligibility criteria for cross-boundary notification of flights shall be in accordance with the letters of agreement. (5) When the notification process cannot be performed by a bilaterally agreed time prior to the initial coordination process, it shall be included in the initial coordination process. (6) When performed, the notification process shall precede the initial coordination process. (7) The notification process shall take place again each time there is a change to any of the following data prior to the initial coordination process: (i) coordination point (COP); (ii) expected SSR code at the transfer of control point; (iii) destination aerodrome; (iv) type of aircraft; (v) equipment capability and status. (8) If a discrepancy is identified between the transmitted data and the corresponding data in the receiving system, or no such information is available that would result in the need for corrective action upon receipt of the following initial coordination data, the discrepancy shall be referred to an appropriate controller working position for resolution. (9) Time criteria for the initiation of the notification process: (i) The notification process shall be initiated at a parameter number of minutes before the estimated time at the COP. (ii) The notification parameter(s) shall be included in the letters of agreement between the ATC units concerned. (iii) The notification parameter(s) may be defined separately for each of the coordination points. (b) Initial coordination (1) For a flight subject to initial coordination, the agreed transfer conditions of a flight shall be operationally binding for both air traffic control units unless the coordination is abrogated or revised. (2) The information on the flight that is subject to the initial coordination process shall include as a minimum: (i) aircraft identification; (ii) SSR mode and code; (iii) departure aerodrome; (iv) estimate data; (v) destination aerodrome; (vi) number and type of aircraft; (vii) type of flight; (viii) equipment capability and status. (3) The content of the ‘equipment capability and status’ information shall include RVSM and the 8,33 kHz channel spacing capability as a minimum. Other items may be included as bilaterally agreed by the letters of agreement. (4) The initial coordination process shall be performed for all eligible flights planned to cross boundaries. (5) The eligibility criteria for cross-boundary initial coordination of flights shall be in accordance with the letters of agreement. (6) Unless already manually initiated, the initial coordination process shall be automatically initiated, in accordance with the letters of agreement, at: (i) a bilaterally agreed parameter time period before the estimated time at the coordination point; or (ii) the time at which the flight is at a bilaterally agreed distance from the coordination point. (7) The initial coordination process for a flight shall only be performed once unless the abrogation of the coordination process is initiated. (8) Following the abrogation of the coordination process, the initial coordination process may be initiated again with the same unit. (9) The completion of the initial coordination process, including confirmation from the receiving unit, shall be passed on to the transferring unit – the flight is then considered ‘coordinated’. (10) Failure of the initial coordination process to confirm completion, in accordance with the applicable quality-of-service requirements, shall result in a warning at the controller working position responsible for the coordination of the flight within the transferring unit. (11) The initial coordination information shall be made available to the appropriate controller working position at the accepting unit. (c) Revision of coordination (1) The revision-of-coordination process shall ensure association with the flight previously coordinated. (2) For a flight subject to the revision-of-coordination process, the agreed transfer conditions of a flight shall be operationally binding for both air traffic control units unless the coordination is abrogated or the conditions are further revised. (3) The revision-of-coordination process shall provide the following flight information, provided it has changed: (i) SSR mode and code; (ii) estimated time and flight level; (iii) equipment capability and status. (4) If bilaterally agreed, the revision-of-coordination data shall provide the following information provided it has changed: (i) coordination point; (ii) route. (5) The revision-of-coordination process may take place one or more times with the unit with which a flight is currently coordinated. (6) The revision-of-coordination process shall take place when: (i) the estimated time over the coordination point differs from that previously provided by more than a value bilaterally agreed; (ii) the transfer level(s), SSR code or equipment capability and status is (are) different from that (those) previously provided. (7) Where bilaterally agreed, the revision-of-coordination process shall take place when there is any change in the following: (i) coordination point; (ii) route. (8) The completion of the revision-of-coordination process, including confirmation from the receiving unit, shall be passed on to the transferring unit. (9) Failure of the revision-of-coordination process to confirm completion, in accordance with the applicable quality-of-service requirements, shall result in a warning at the controller working position responsible for the coordination of the flight within the transferring unit. (10) The revision-of-coordination process shall take place immediately following the relevant input or update. (11) The revision-of-coordination process shall be inhibited after the flight is at a bilaterally agreed time/distance from the transfer control point in accordance with the letters of agreement. (12) The revision-of-coordination information shall be made available to the appropriate controller working position within the receiving unit. (13) Where the completion of the revision-of-coordination process is not confirmed in accordance with the applicable quality-of-service requirements, the transferring unit shall initiate verbal coordination. (d) Abrogation of coordination (1) The abrogation-of-coordination process shall ensure association with the previous notification or coordination process that is being cancelled. (2) The abrogation-of-coordination process shall take place with a unit for a coordinated flight when: (i) the unit is no longer the next unit in the coordination sequence; (ii) the flight plan is cancelled in the sending unit and the coordination is no longer relevant; (iii) abrogation-of-coordination information is received from the previous unit in respect of the flight. (3) The abrogation-of-coordination process may take place with a unit for a notified flight when: (i) the unit is no longer the next unit in the coordination sequence; (ii) the flight plan is cancelled in the sending unit and the coordination is no longer relevant; (iii) abrogation-of-coordination information is received from the previous unit in respect of the flight; (iv) the flight is delayed en route, and a revised estimate cannot be determined automatically. (4) The completion of the abrogation-of-coordination process, including confirmation from the receiving unit, shall be passed on to the transferring unit. (5) Failure of the abrogation-of-coordination process to confirm completion, in accordance with the applicable quality-of-service requirements, shall result in a warning at the controller working position responsible for the coordination of the flight within the transferring unit. (6) The abrogation-of-coordination information shall be made available to the appropriate controller working position within the notified unit or within the unit with which the coordination is cancelled. (7) Where the completion of the abrogation-of-coordination process is not confirmed in accordance with the applicable quality-of-service requirements, the transferring unit shall initiate verbal coordination. (e) Basic flight data (1) The information subject to the basic-flight-data process shall provide as a minimum: (i) aircraft identification; (ii) SSR mode and code. (2) Any additional information provided by the basic-flight-data process shall be subject to bilateral agreement. (3) The basic-flight-data process shall be performed automatically for each eligible flight. (4) The eligibility criteria for basic-flight-data shall be in accordance with the letters of agreement. (5) The completion of the basic-flight-data process, including confirmation from the receiving unit, shall be passed on to the supplying unit. (6) Failure of the basic-flight-data process to confirm completion, in accordance with the applicable quality-of-service requirements, shall result in a warning at the appropriate controller working position within the supplying unit. (f) Change to basic flight data (1) The change-to-basic-flight-data process shall ensure association with the flight previously subject to a basic-flight-data process. (2) Any other information subject to the change-to-basic-flight-data process and the associated criteria for its provision shall be subject to bilateral agreement. (3) A change-to-basic-flight-data process shall only take place for a flight which has previously been notified by a basic-flight-data process. (4) A change-to-basic-flight-data process shall be initiated automatically in accordance with bilaterally agreed criteria. (5) The completion of the change-to-basic-flight-data process, including confirmation from the receiving unit, shall be passed on to the supplying unit. (6) Failure of the change-to-basic-flight-data process to confirm completion, in accordance with the applicable quality-of-service requirements, shall result in a warning at the appropriate controller working position within the supplying unit. (7) The change-to-basic-flight-data information shall be made available to the appropriate controller working position within the receiving unit. B. When agreed between the units concerned to conduct the pre-departure notification, the change-of-frequency or the manual-assumption-of-communication processes shall be as follows: (a) Pre-departure notification and coordination (1) The information subject to the pre-departure notification and coordination process shall include as a minimum: (i) aircraft identification; (ii) SSR mode and code (if available); (iii) departure aerodrome; (iv) estimated take-off time or estimate data, as bilaterally agreed; (v) destination aerodrome; (vi) number and type of aircraft. (2) The information subject to the pre-departure notification and coordination process from a terminal manoeuvring area (TMA) control unit or an ACC shall contain the following: (i) type of flight; (ii) equipment capability and status. (3) The content of the ‘equipment capability and status’ information shall include RVSM and the 8,33 kHz channel spacing capability as a minimum. (4) The ‘equipment capability and status’ information may contain other items as bilaterally agreed by the letters of agreement. (5) The pre-departure notification and coordination process shall take place one or more times for each eligible flight planned to cross the boundaries where the flight time from departure to the coordination point would not allow sufficient time for the initial coordination or notification processes to be executed. (6) The eligibility criteria for the cross-boundary pre-departure notification and coordination of flights shall be in accordance with the letters of agreement. (7) The pre-departure notification and coordination process shall take place again each time there is a change to any item of the data subject to the previous pre-departure notification and coordination process before departure. (8) The completion of the pre-departure notification and coordination process, including confirmation from the receiving unit, shall be passed on to the transferring unit. (9) Failure of the pre-departure notification and coordination process to confirm completion, in accordance with the applicable quality-of-service requirements, shall result in a warning at the controller working position responsible for the notification/coordination of the flight within the transferring unit. (10) The pre-departure notification and coordination information shall be made available at the appropriate controller working position within the notified unit. (b) Change of frequency (1) The information subject to the change-of-frequency process shall include the aircraft identification and any of the following, if available: (i) release indication; (ii) cleared flight level; (iii) assigned heading/track or direct clearance; (iv) assigned speed; (v) assigned rate of climb/descent. (2) If bilaterally agreed, change of frequency data shall contain the following: (i) current track position; (ii) instructed frequency. (3) The change-of-frequency process shall be manually initiated by the transferring controller. (4) The completion of the change-of-frequency process, including confirmation from the accepting unit, shall be passed on to the transferring ATC unit. (5) Failure of the change-of-frequency process to confirm completion, in accordance with the applicable quality-of-service requirements, shall result in a warning at the appropriate controller working position within the transferring ATC unit. (6) The change-of-frequency information shall be made available to the accepting controller without delay. (c) Manual assumption of communications (1) The information subject to the manual-assumption-of-communications process shall include as a minimum the aircraft identification. (2) The manual-assumption-of-communications process shall be initiated by the accepting unit when communication is established. (3) The completion of the manual-assumption-of-communications process, including confirmation from the transferring unit, shall be passed on to the accepting ATC unit. (4) Failure of the manual-assumption-of-communications process to confirm completion, in accordance with the applicable quality-of-service requirements, shall result in a warning at the appropriate controller working position within the accepting ATC unit. (5) The manual-assumption-of-communications information shall be presented immediately to the controller within the transferring unit. (d) Crossing intention notification (1) The information subject to the crossing-intention-notification process shall include as a minimum: (i) aircraft identification; (ii) SSR mode and code; (iii) number and type of aircraft; (iv) identifier of sector in charge; (v) crossing route including estimated times and flight levels for each point on the route. (2) The crossing-intention-notification process shall be initiated manually by the controller, or automatically as described in the letters of agreement. (3) The completion of the crossing-intention-notification process, including confirmation from the notified unit, shall be passed on to the notifying unit. (4) Failure of the crossing-intention-notification process to confirm completion, in accordance with the applicable quality-of-service requirements, shall result in a warning within the notifying unit. (5) The crossing-intention-notification information shall be made available to the appropriate controller working position within the notified unit. (e) Crossing clearance request (1) The information subject to the crossing-clearance-request process shall include as a minimum: (i) aircraft identification; (ii) SSR mode and code; (iii) number and type of aircraft; (iv) identifier of sector in charge; (v) crossing route including estimated times and flight levels for each point on the route. (2) If bilaterally agreed, a crossing clearance request shall contain the equipment capability and status. (3) The content of the ‘equipment capability and status’ information shall include the RVSM capability as a minimum, and may contain other items as bilaterally agreed. (4) The crossing clearance request shall be initiated at the controller’s discretion, in accordance with the conditions specified in the letters of agreement. (5) The completion of the crossing-clearance-request process, including confirmation from the unit receiving the request, shall be provided to the requesting unit. (6) Failure of the crossing-clearance-request process to confirm completion, in accordance with the applicable quality-of-service requirements, shall result in a warning at the appropriate controller working position within the requesting unit. (7) The crossing-clearance-request information shall be made available to the appropriate controller working position within the unit receiving the request. (8) A crossing-clearance-request process shall be replied to by any of the following: (i) the acceptance of the proposed route/airspace crossing details; (ii) a counter-proposal including different route/airspace crossing details as specified in Section 6 below; (iii) the rejection of the proposed route/airspace crossing details. (9) If an operational reply is not received within a bilaterally agreed interval, a warning shall be issued at the appropriate controller working position within the requesting unit. (f) Crossing counter-proposal (1) The crossing-counter-proposal process shall ensure association with the flight previously subject to coordination. (2) The information subject to the crossing-counter-proposal process shall include as a minimum: (i) aircraft identification; (ii) crossing route including estimated times and flight levels for each point on the route. (3) The counter-proposal shall include a proposed new flight level and/or route. (4) The completion of the crossing-counter-proposal process, including confirmation from the original requesting unit, shall be passed on to the counter-proposing unit. (5) Failure of the crossing-counter-proposal process to confirm completion, in accordance with the applicable quality-of-service requirements, shall result in a warning at the appropriate controller working position within the counter-proposing unit. (6) The crossing-counter-proposal information shall be made available to the appropriate controller working position within the original requesting unit. (7) The confirmation of the successful processing of the crossing-counter-proposal information by the original requesting unit shall be followed by an operational reply from the original requesting unit. (8) The operational reply to a crossing counter-proposal shall be acceptance or rejection, as appropriate. (9) If an operational reply is not received within a bilaterally agreed interval, a warning shall be issued at the appropriate controller working position within the counter-proposing unit. (g) Crossing cancellation (1) The crossing-cancellation process shall ensure association with the previous notification or coordination process that is cancelled. (2) A crossing-cancellation process shall be initiated by the unit responsible for the flight when one of the following occurs: (i) the flight previously notified by the basic-flight-data process will now not enter the airspace of the notified unit or is no longer of interest to the notified unit; (ii) the crossing will not be executed on the route expressed in the crossing-intention-notification information; (iii) the crossing will not be executed according to the conditions under negotiation or according to the conditions agreed after an airspace crossing dialogue. (3) A crossing-cancellation process shall be triggered automatically or manually by a controller input in accordance with the letters of agreement. (4) The completion of the crossing-cancellation process, including confirmation from the notified/requested unit, shall be passed on to the cancelling unit. (5) Failure of the crossing-cancellation process to confirm completion, in accordance with the applicable quality-of-service requirements, shall result in a warning at the appropriate working position within the cancelling unit. (6) The crossing-cancellation information shall be made available to the appropriate controller working position within the notified/requested unit. C. Between units that provide area control services required to operate the data link services as referred to in point AUR.COM.2005(1)(a) of Implementing Regulation (EU) 2023/1770, or when so agreed with or between other units, the following processes shall be supported by automation: (a) Logon forward (1) The information subject to the logon-forward process shall include as a minimum: (i) aircraft identification; (ii) departure aerodrome; (iii) destination aerodrome; (iv) logon type; (v) logon parameters. (2) One logon-forward process shall be performed for each data link logged-on flight planned to cross boundaries. (3) The logon-forward process shall be initiated at or as soon as possible after the earlier of the times determined, in accordance with the letters of agreement, from the following: (i) a parameter number of minutes before the estimated time at the coordination point; (ii) the time at which the flight is at a bilaterally agreed distance from the coordination point. (4) The eligibility criteria for the logon-forward process shall be in accordance with the letters of agreement. (5) The logon-forward information shall be included with the corresponding flight information in the receiving unit. (6) The logged-on status of the flight may be displayed at the appropriate controller working position within the receiving unit. (7) The completion of the logon-forward process, including confirmation from the receiving unit, shall be passed on to the transferring unit. (8) Failure of the logon-forward process to confirm completion, in accordance with the applicable quality-of-service requirements, shall result in the initiation of an air–ground data link contact request to the aircraft. (b) Next authority notified (1) The information subject to the next-authority-notified process shall include as a minimum: (i) aircraft identification; (ii) departure aerodrome; (iii) destination aerodrome. (2) One next-authority-notified process shall be performed for each eligible flight crossing boundaries. (3) The next-authority-notified process shall be initiated after the next data authority request with the aircraft has been acknowledged by the airborne system. (4) Following the successful processing of the next-authority-notified information, the receiving unit shall initiate a controller–pilot data link communication (CPDLC) start request with the aircraft. (5) If the next-authority-notified information has not been received in accordance with a bilaterally agreed parameter time, local procedures shall be applied by the receiving unit for the initiation of data link communications with the aircraft. (6) The completion of the next-authority-notified process, including confirmation from the receiving unit, shall be passed on to the transferring unit. (7) Failure of the next-authority-notified-process to confirm completion, in accordance with the applicable quality-of-service requirements, shall result in the initiation of local procedures within the transferring unit.