dokumendiregister.ee
OtsingAsutusedMCP
Otsing›Lennuamet
Kiri sissetulevAvalik

NPA 2016-09(A), NPA 2016-09(B) Requirements for air traffic services

Lennuamet · 15. september 2016
Viit
2-4/16/3073-1
Registreeritud
15. september 2016
Dokumendi liik
Kiri sissetulev
Adressaat
Euroopa Lennundusohutusamet (EASA)
Saabumis/saatmisviis
e-post
Funktsioon
2 Õigusalane teenindamine
Sari
2-4 Kirjavahetus rahvusvaheliste lennundusnõuete küsimustes
Toimik
2-4/2016
Vastutaja
Kristo Vallimäe (Juhtkond, Lennuliiklusteeninduse ja lennuväljade osakond)
Lahendamise tähtaeg
28. veebruar 2017

Failid

  • 📎NPA 2016-09(A).pdf1307 KB
  • 📎NPA 2016-09(B).pdf3678 KB

Sisu (failidest)

European Aviation Safety Agency Notice of Proposed Amendment 2016-09(B) Requirements for air traffic services RMT.0464 — 14.9.2016 EXECUTIVE SUMMARY This Notice of Proposed Amendment (NPA) addresses safety and regulatory coordination issues related to the provision of air traffic services (ATS). The main objective of this NPA is to maintain a high level of safety in the European Union (EU) air navigation system, in particular with regard to the provision of ATS. In order to achieve this objective, the proposal aims at: — transposing the relevant International Civil Aviation Organization (ICAO) provisions on ATS into the EU aviation regulatory framework, thus contributing to their uniform implementation throughout the EU, and supporting EU Member States in fulfilling their obligations stemming from the Chicago Convention; and — defining proportionate and cost-efficient rules. The NPA introduces a detailed set of provisions to be placed in the ‘ATM/ANS Common Requirements Regulation’, in particular in Annex IV thereto, and thus removes the existing provision referencing to ICAO Annexes. These provisions provide implementation of the Essential Requirements in Annex Vb 2.(c) to Regulation (EC) No 216/2008. It also proposes associated AMC and GM to facilitate the application by the affected stakeholders. In addition to the transposition of the ICAO provisions, this NPA proposes a number of measures related to the aerodrome flight information service (AFIS), as this is not explicitly addressed in the ICAO Standards and Recommended Practices (SARPs). In this way, this service is proposed to be regulated in the EU context, thus reducing the high diversity of the existing implementation across the EU Member States. In this context, Member States may decide not to provide ATS (ATC or AFIS)at smaller airfields, where the so-called ‘UNICOM stations’, not addressed by EU ATS rules, may be established to support local and, in particular, General Aviation activities. As this NPA and Regulation (EU) No 923/2012 (standardised rules of the air (SERA)) are closely interrelated, the NPA also proposes minor amendments to said Regulation, which was recently amended by Regulation (EU) 2016/1185. Safety recommendations submitted to the Agency are also addressed by this proposal. NPA 2016-09 is divided in two parts. The present sub-NPA(B) includes the proposed amendments both at implementing rule and acceptable means of compliance/guidance material level. Applicability Process map Affected — Regulation (EU) 2016/1377; Concept paper: No regulations — the upcoming related ED Decision; Terms of Reference: 9.7.2014 and decisions: — Regulation (EU) No 923/2012; Rulemaking group: Yes — ED Decision 2013/013/R RIA type: Full Affected Member States; competent authorities; Technical consultation stakeholders: air navigation service providers; air during NPA drafting: No traffic controllers; aircraft operators; Duration of NPA consultation: 4 months professional organisations; trade unions; Review group: Yes pilots; passengers Focused consultation: Yes Driver/origin: Safety Publication date of the opinion: Q2/2017 Reference: Please refer to Section 2.3. of this NPA Publication date of the decision: Q4/2017 TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 1 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) Table of contents Table of contents 1. Proposed amendments......................................................................................................................... 3 1.1. Amendments to the ATM/ANS Common Requirements Regulation (draft opinion (PART-ATS)) ............ 3 1.1.1. Amendments to the Regulation ..........................................................................................3 1.1.2. Amendments to Annex I — Definitions ...............................................................................4 1.1.3. Amendments to Annex IV — Subpart A — Additional organisation requirements for providers of ATS (ATS.OR) .................................................................................................14 Section 1 — General requirements ...................................................................................................14 Section 4 — Requirements for communications ..............................................................................17 Section 5 — Requirements for information ......................................................................................23 1.1.4. Amendments to Annex IV — Subpart B — Technical requirements for providers of ATS (ATS.TR) .............................................................................................................................26 Section 1 — General ..........................................................................................................................26 Section 2 — ATC service ....................................................................................................................32 Section 3 — Flight information service .............................................................................................42 Section 4 — Alerting service..............................................................................................................45 1.1.5. Amendments to Annex V — Subpart A — Additional organisation requirements for providers of meteorological services (MET.OR) ................................................................48 1.2. Amendments to the SERA Regulation (draft Opinion) ........................................................................... 49 1.3. Amendments to the upcoming ED Decision issuing the AMC/GM to the ATM/ANS Common Requirements Regulation (draft decision (PART-ATS)) .......................................................................... 52 1.4. Amendments to ED Decision 2013/013/R — AMC/GM to the SERA Regulation (draft decision)........ 189 2. References ....................................................................................................................................... 190 2.1. Affected regulations............................................................................................................................. 190 2.2. Affected AMC and GM ......................................................................................................................... 190 2.3. Reference documents .......................................................................................................................... 190 TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 2 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments 1. Proposed amendments The text of the amendment is arranged to show deleted text, new or amended text as shown below: (a) deleted text is marked with strike through; (b) new or amended text is highlighted in grey; (c) an ellipsis (…) indicates that the remaining text is unchanged in front of or following the reflected amendment. 1.1. Amendments to the ATM/ANS Common Requirements Regulation (draft opinion (PART-ATS)) 1.1.1. Amendments to the Regulation (a) The following recital is introduced: Whereas the provisions contained in Commission Implementing Regulation (EU) No 923/2012 should be complemented with aspects related to the provision of air traffic services, to ensure consistency of service provision with pilot and ATS personnel actions, and requirements under that Regulation. (b) The following articles are introduced: Article 3(1b) — Determination of the need for ATS (a) The need for the provision of ATS shall be determined by the Member States by consideration of the following: (1) the types of air traffic involved; (2) the density of air traffic; (3) the meteorological conditions; (4) such other factors as may be relevant. (b) The carriage of airborne collision avoidance systems (ACAS) by aircraft in a given area shall not be a factor in determining the need for ATS in that area. (Annex 11— Sections 2.4.1 and 2.4.2) Article 3(1c) — Coordination between military authorities and ATS Member States shall ensure that special procedures are established so that: (a) ATS units are notified if a military unit observes that an aircraft which is, or might be, a civil aircraft is approaching, or has entered, any area in which interception might become necessary; (b) all possible efforts are made to confirm the identity of the aircraft and to provide it with the navigational guidance necessary to avoid the need for interception. (Annex 11— Section 2.17.3.2) Article 3(1d) — Coordination of activities potentially hazardous to civil traffic (a) Member States shall ensure that the arrangements for activities potentially hazardous to civil aircraft over their territory are coordinated. When over the high seas, potentially hazardous activities shall be coordinated with the competent authority of the State having accepted, TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 3 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments pursuant to an ICAO Regional Agreement, the responsibility to provide ATS within the airspace concerned. The coordination shall be effected early enough to permit timely promulgation of information regarding these activities. (b) Member States shall establish arrangements for the promulgation of information regarding such activities. (c) Member States shall take adequate measures to prevent emission of laser beams from adversely affecting flight operations. (Annex 11 — Sections 2.18.1, 2.18.3 and 2.18.5) 1.1.2. Amendments to Annex I — Definitions (a) Definition 6. is amended as follows: ‘Aerodrome flight information service (AFIS)’ means flight information service and alerting service for aerodrome traffic at an aerodrome provided at an aerodrome by an ATS provider designated in accordance with Article 8(1) of Regulation (EC) No 550/2004; (b) The following definitions are added: 'Accepting controller’ means air traffic controller next to take control of an aircraft. 'Accepting unit’ means ATC unit next to take control of an aircraft. ‘Accuracy’ means a degree of conformance between the estimated or measured value and the true value. ‘Advisory airspace’ means an airspace of defined dimensions, or designated route, within which air traffic advisory service is available. ‘ADS-C agreement’ means a reporting plan which establishes the conditions of ADS-C data reporting (i.e. data required by the air traffic services unit and frequency of ADS-C reports which have to be agreed to prior to using ADS-C in the provision of air traffic services). ‘Advisory route’ means a designated route along which air traffic advisory service is available. ‘Aerodrome control tower’ means a unit established to provide ATC service to aerodrome traffic. ‘Aerodrome traffic’ means all traffic on the manoeuvring area of an aerodrome and all aircraft flying in the vicinity of an aerodrome. An aircraft operating in the vicinity of an aerodrome includes but is not limited to aircraft entering or leaving an aerodrome traffic circuit. ‘Aerodrome traffic circuit’ means the specified path to be flown by aircraft operating in the vicinity of an aerodrome. ‘Aeronautical fixed station’ means a station in the aeronautical fixed service. ‘Aeronautical ground light’ means any light specially provided as an aid to air navigation, other than a light displayed on an aircraft. ‘Aeronautical mobile service’ means a mobile service between aeronautical stations and aircraft stations, or between aircraft stations, in which survival craft stations may participate; emergency position-indicating radio beacon stations may also participate in this service on designated distress and emergency frequencies. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 4 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments ‘Aeronautical station’ means a land station in the aeronautical mobile service. In certain instances, an aeronautical station may be located, for example, on board a ship or on a platform at sea. ‘Aeronautical telecommunication station’ means a station in the aeronautical telecommunication service. ‘Airborne collision avoidance system (ACAS)’ means an aircraft system based on secondary surveillance radar (SSR) transponder signals which operates independently of ground-based equipment to provide advice to the pilot on potential conflicting aircraft that are equipped with SSR transponders. ‘Aircraft address’ means a unique combination of 24 bits available for assignment to an aircraft for the purpose of air–ground communications, navigation and surveillance. ‘Aircraft identification’ means a group of letters, figures or a combination thereof which is either identical to, or the coded equivalent of, the aircraft call sign to be used in air–ground communications, and which is used to identify the aircraft in ground–ground ATS communications. ‘Aircraft proximity’ means a situation in which, in the opinion of a pilot or ATS personnel, the distance between aircraft as well as their relative positions and speed have been such that the safety of the aircraft involved may have been compromised. An aircraft proximity is classified as follows: (a) Risk of collision. The risk classification of an aircraft proximity in which serious risk of collision has existed. (b) Safety not assured. The risk classification of an aircraft proximity in which the safety of the aircraft may have been compromised. (c) No risk of collision. The risk classification of an aircraft proximity in which no risk of collision has existed. ‘Air–ground communication’ means two-way communication between aircraft and stations or locations on the surface of the earth. ‘Air-taxiing’ means movement of a helicopter/vertical take-off and landing (VTOL) above the surface of an aerodrome, normally in ground effect and at a ground speed normally less than 37 km/h (20 kts). ‘Air traffic’ means all aircraft in flight or operating on the manoeuvring area of an aerodrome. ‘Air traffic advisory service’ means a service provided within advisory airspace to ensure separation, in so far as practical, between aircraft which are operating on instrument flight rules (IFR) flight plans. ‘Air traffic control (ATC) clearance’ means authorisation for an aircraft to proceed under conditions specified by an ATC unit. ‘Air traffic control (ATC) instruction’ means directives issued by ATC for the purpose of requiring a pilot to take a specific action. ‘ATC unit’ is a generic term meaning variously, area control centre, approach control unit or aerodrome control tower. ‘ATS airspaces’ means airspaces of defined dimensions, alphabetically designated, within which specific types of flights may operate and for which ATS and rules of operation are specified. ‘Airway’ means a control area or portion thereof established in the form of a corridor. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 5 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments ‘ALERFA’ is the code word used to designate an alert phase. ‘Alert phase’ means a situation wherein apprehension exists as to the safety of an aircraft and its occupants. ‘Approach control unit’ means a unit established to provide ATC service to controlled flights arriving at, or departing from, one or more aerodromes. ‘Approach sequence’ means the order in which two or more aircraft are cleared to approach to land at the aerodrome. ‘ATIS’ is the symbol used to designate automatic terminal information service. ‘Automatic dependent surveillance — broadcast (ADS-B)’ means a means by which aircraft, aerodrome vehicles and other objects can automatically transmit and/or receive data such as identification, position and additional data, as appropriate, in a broadcast mode via a data link. ‘Automatic dependent surveillance — contract (ADS-C)’ means a means by which the terms of an ADS- C agreement will be exchanged between the ground system and the aircraft, via a data link, specifying under what conditions ADS-C reports would be initiated, and what data would be contained in the reports. ‘Automatic terminal information service (ATIS)’ means the automatic provision of current, routine information to arriving and departing aircraft throughout 24 hours or a specified portion thereof: (a) ‘Data link-automatic terminal information service (D-ATIS)’ means the provision of ATIS via data link; (b) ‘Voice-automatic terminal information service (Voice-ATIS)’ means the provision of ATIS by means of continuous and repetitive voice broadcasts. ‘ATS surveillance service’ means a service provided directly by means of an ATS surveillance system. ‘ATS surveillance system’ means a generic term meaning variously, ADS-B, PSR, SSR or any comparable ground-based system that enables the identification of aircraft. ‘Base turn’ means a turn executed by the aircraft during the initial approach between the end of the outbound track and the beginning of the intermediate or final approach track. The tracks are not reciprocal. ‘Broadcast’ means a transmission of information relating to air navigation that is not addressed to a specific station or stations. ‘Ceiling’ means the height above the ground or water of the base of the lowest layer of cloud below 6 000 m (20 000 ft) covering more than half of the sky. ‘Change-over point’ means the point at which an aircraft navigating on an ATS route segment defined by reference to very high frequency omnidirectional radio ranges is expected to transfer its primary navigational reference from the facility behind the aircraft to the next facility ahead of the aircraft. ‘Clearance limit’ means the point to which an aircraft is granted an ATC clearance. ‘Code (SSR)’ means the number assigned to a particular multiple pulse reply signal transmitted by a transponder in Mode A or Mode C. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 6 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments ‘Common point’ means a point on the surface of the earth common to the tracks of two aircraft, used as a basis for the application of separation (e.g. significant point, waypoint, navigation aid, fix). ‘Conference communications’ means communication facilities whereby direct speech conversation may be conducted between three or more locations simultaneously. ‘Controlled aerodrome’ means an aerodrome at which ATC service is provided to aerodrome traffic. ‘Controlled airspace’ means an airspace of defined dimensions within which ATC service is provided in accordance with the airspace classification. ‘Controlled flight’ means any flight which is subject to an ATC clearance. ‘Controller-pilot data link communications (CPDLC)’ means a means of communication between controller and pilot, using data link for ATC communications. ‘Cruise climb’ means an aeroplane cruising technique resulting in a net increase in altitude as the aeroplane mass decreases. ‘Cruising level’ means a level maintained during a significant portion of a flight. ‘Data link communications’ means a form of communication intended for the exchange of messages via a data link. ‘Data link-VOLMET (D-VOLMET)’ means the provision of current aerodrome routine meteorological reports (METAR) and aerodrome special meteorological reports (SPECI), aerodrome forecasts (TAF), SIGMET, special air-reports not covered by a SIGMET and, where available, AIRMET via data link. ‘Decision altitude (DA) or decision height (DH)’ means a specified altitude or height in a 3D instrument approach operation at which a missed approach must be initiated if the required visual reference to continue the approach has not been established. ‘Dependent parallel approaches’ means simultaneous approaches to parallel or near-parallel instrument runways where radar separation minima between aircraft on adjacent extended centre lines are prescribed. ‘DETRESFA’ is the code word used to designate a distress phase. ‘Discrete code’ means a four-digit SSR code with the last two digits not being ‘00’. ‘Distress phase’ means a situation wherein there is reasonable certainty that an aircraft and its occupants are threatened by grave and imminent danger or require immediate assistance. ‘Downstream clearance’ means a clearance issued to an aircraft by an ATC unit that is not the current controlling authority of that aircraft. ‘Elevation’ means the vertical distance of a point or a level, on or affixed to the surface of the earth, measured from mean sea level. ‘Emergency phase’ is a generic term meaning, as the case may be, uncertainty phase, alert phase or distress phase. ‘Estimated elapsed time’ means the estimated time required to proceed from one significant point to another. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 7 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments ‘Estimated off-block time’ means the estimated time at which the aircraft will commence movement associated with departure. ‘Estimated time of arrival’ means for IFR flights, the time at which it is estimated that the aircraft will arrive over that designated point, defined by reference to navigation aids, from which it is intended that an instrument approach procedure will be commenced, or, if no navigation aid is associated with the aerodrome, the time at which the aircraft will arrive over the aerodrome. For visual flight rules (VFR) flights, the time at which it is estimated that the aircraft will arrive over the aerodrome. ‘Expected approach time’ means the time at which ATC expects that an arriving aircraft, following a delay, will leave the holding fix to complete its approach for a landing. ‘Filed flight plan (FPL)’ means the flight plan as filed with an ATS unit by the pilot or a designated representative, without any subsequent changes. ‘Final approach’ means that part of an instrument approach procedure which commences at the specified final approach fix or point, or where such a fix or point is not specified, (a) at the end of the last procedure turn, base turn or inbound turn of a racetrack procedure, if specified; or (b) at the point of interception of the last track specified in the approach procedure, and ends at a point in the vicinity of an aerodrome from which: — a landing can be made; or — a missed approach procedure is initiated. ‘Flight path monitoring’ means the use of ATS surveillance systems for the purpose of providing aircraft with information and advice relative to significant deviations from nominal flight path, including deviations from the terms of their ATC clearances. ‘Flight plan’ means specified information provided to ATS units, relative to an intended flight or portion of a flight of an aircraft. ‘Flight visibility’ means the visibility forward from the cockpit of an aircraft in flight. ‘Glide path’ means a descent profile determined for vertical guidance during a final approach. ‘Ground effect’ means a condition of improved performance (lift) due to the interference of the surface with the airflow pattern of the rotor system when a helicopter or other VTOL aircraft is operating near the ground. ‘Ground visibility’ means the visibility at an aerodrome, as reported by an accredited observer or by automatic systems. ‘Heading’ means the direction in which the longitudinal axis of an aircraft is pointed, usually expressed in degrees from North (true, magnetic, compass or grid). ‘Holding fix’ means a geographical location that serves as a reference for a holding procedure. ‘Holding procedure’ means a predetermined manoeuvre which keeps an aircraft within a specified airspace while awaiting further clearance. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 8 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments ‘Identification’ means the situation which exists when the position indication of a particular aircraft is seen on a situation display and positively identified. ‘IFR’ is the symbol used to designate the instrument flight rules. ‘IFR flight’ means a flight conducted in accordance with the instrument flight rules. ‘IMC’ is the symbol used to designate instrument meteorological conditions. ‘INCERFA’ is the code word used to designate an uncertainty phase. ‘Independent parallel approaches’ means simultaneous approaches to parallel or near-parallel instrument runways where radar separation minima between aircraft on adjacent extended runway centre lines are not prescribed. ‘Independent parallel departures’ means simultaneous departures from parallel or near-parallel instrument runways. ‘Initial approach segment’ means that segment of an instrument approach procedure between the initial approach fix and the intermediate approach fix or, where applicable, the final approach fix or point. ‘Instrument approach operations’ means an approach and landing using instruments for navigation guidance based on an instrument approach procedure. There are two methods for executing instrument approach operations: (a) a two-dimensional (2D) instrument approach operation, using lateral navigation guidance only; and (b) a three-dimensional (3D) instrument approach operation, using both lateral and vertical navigation guidance. ‘Instrument approach procedure (IAP)’ means a series of predetermined manoeuvres by reference to flight instruments with specified protection from obstacles from the initial approach fix, or where applicable, from the beginning of a defined arrival route to a point from which a landing can be completed and thereafter, if a landing is not completed, to a position at which holding or en-route obstacle clearance criteria apply. Instrument approach procedures are classified as follows: (a) ‘Non-precision approach (NPA) procedure’ means an instrument approach procedure designed for 2D instrument approach operations Type A. (b) ‘Approach procedure with vertical guidance (APV)’ means an performance-based navigation (PBN) instrument approach procedure designed for 3D instrument approach operations Type A. (c) ‘Precision approach (PA) procedure’ means an instrument approach procedure based on navigation systems (ILS, MLS, GLS and SBAS Cat I) designed for 3D instrument approach operations Type A or B. ‘Instrument meteorological conditions (IMC)’ means meteorological conditions expressed in terms of visibility, distance from cloud, and ceiling, less than the minima specified for visual meteorological conditions. ‘Landing area’ means that part of a movement area intended for the landing or take-off of aircraft. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 9 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments ‘Location indicator’ means a four-letter code group formulated in accordance with rules prescribed by ICAO and assigned to the location of an aeronautical fixed station. ‘Manoeuvring area’ means that part of an aerodrome to be used for the take-off, landing and taxiing of aircraft, excluding aprons. ‘Minimum fuel’ is a term to be used to describe a situation in which an aircraft’s fuel supply has reached a state where the flight is committed to land at a specific aerodrome and no additional delay can be accepted. ‘Missed approach procedure’ means the procedure to be followed if the approach cannot be continued. ‘Mode (SSR)’ means the conventional identifier related to specific functions of the interrogation signals transmitted by an SSR interrogator. There are four modes specified in ICAO Annex 10: A, C, S and intermode. ‘Movement area’ means that part of an aerodrome to be used for the take-off, landing and taxiing of aircraft, consisting of the manoeuvring area and the apron(s). ‘Multilateration (MLAT) system’ means a group of equipment configured to provide position derived from the secondary surveillance radar (SSR) transponder signals (replies or squitters) primarily using time difference of arrival (TDOA) techniques. Additional information, including identification, can be extracted from the received signals. ‘Near-parallel runways’ means non-intersecting runways whose extended centre lines have an angle of convergence/divergence of 15 degrees or less. ‘Normal operating zone (NOZ)’ means airspace of defined dimensions extending to either side of an ILS localiser course and/or MLS final approach track. Only the inner half of the normal operating zone is taken into account in independent parallel approaches. ‘No transgression zone (NTZ)’ means, in the context of independent parallel approaches, a corridor of airspace of defined dimensions located centrally between the two extended runway centre lines, where a penetration by an aircraft requires a controller intervention to manoeuvre any threatened aircraft on the adjacent approach. ‘Obstacle clearance altitude (OCA)’ means the lowest altitude above the elevation of the relevant runway threshold or the aerodrome elevation as applicable, used in establishing compliance with appropriate obstacle clearance criteria. ‘Obstacle clearance height (OCH)’ means the lowest height above the elevation of the relevant runway threshold or the aerodrome elevation as applicable, used in establishing compliance with appropriate obstacle clearance criteria. ‘Onward clearance time’ means the time at which an aircraft can expect to leave the fix at which it is being held. ‘Pilot-in-command’ means the pilot designated by the operator, or in the case of General Aviation, the owner, as being in command and charged with the safe conduct of a flight. ‘Position indication’ means the visual indication, in non-symbolic and/or symbolic form, on a situation display, of the position of an aircraft, aerodrome vehicle or other object. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 10 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments ‘Position symbol’ means the visual indication in symbolic form, on a situation display, of the position of an aircraft, aerodrome vehicle or other object, obtained after automatic processing of positional data derived from any source. ‘Pressure-altitude’ means an atmospheric pressure expressed in terms of altitude which corresponds to that pressure in the Standard Atmosphere. ‘Primary radar’ means a radar system which uses reflected radio signals. ‘Primary surveillance radar (PSR)’ means a surveillance radar system which uses reflected radio signals. ‘Procedural control’ means a term used to indicate that information derived from an ATS surveillance system is not required for the provision of ATC service. ‘Procedural separation’ means the separation used when providing procedural control. ‘Procedure turn’ means a manoeuvre in which a turn is made away from a designated track followed by a turn in the opposite direction to permit the aircraft to intercept and proceed along the reciprocal of the designated track. ‘PSR blip’ means the visual indication, in non-symbolic form, on a situation display of the position of an aircraft obtained by primary radar. ‘Radar’ means a radio detection device which provides information on range, azimuth and/or elevation of objects. ‘Radar approach’ means an approach in which the final approach phase is executed under the direction of a controller using radar. ‘Radar clutter’ means the visual indication on a situation display of unwanted signals. ‘Radar contact’ means the situation which exists when the radar position of a particular aircraft is seen and identified on a situation display. ‘Radar separation’ means the separation used when aircraft position information is derived from radar sources. ‘Radio navigation service’ means a service providing guidance information or position data for the efficient and safe operation of aircraft supported by one or more radio navigation aids. ‘Radiotelephony’ means a form of radio communication primarily intended for the exchange of information in the form of speech. ‘Receiving controller’ means the air traffic controller to which a message is sent. Receiving unit’ means the ATS unit to which a message is sent. ‘Reporting point’ means a specified geographical location in relation to which the position of an aircraft can be reported. ‘Runway-holding position’ means a designated position intended to protect a runway, an obstacle limitation surface, or an instrument landing system (ILS)/microwave landing system (MLS) critical/sensitive area at which taxiing aircraft and vehicles shall stop and hold unless otherwise authorised by the aerodrome control tower. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 11 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments ‘Runway incursion’ means any occurrence at an aerodrome involving the incorrect presence of an aircraft, vehicle or person on the protected area of a surface designated for the landing and take-off of aircraft. ‘Runway-in-use’ means the runway or runways that, at a particular time, are considered by the ATS unit to be the most suitable for use by the types of aircraft expected to land or take off at the aerodrome. Separate or multiple runways may be designated runway-in-use for arriving aircraft and departing aircraft. ‘Secondary radar’ means a radar system wherein a radio signal transmitted from the radar station initiates the transmission of a radio signal from another station. ‘Secondary surveillance radar (SSR)’ means a surveillance radar system which uses transmitters/receivers (interrogators) and transponders. ‘Segregated parallel operations’ means simultaneous operations on parallel or near-parallel instrument runways in which one runway is used exclusively for approaches and the other runway is used exclusively for departures. ‘Sending controller’ means the air traffic controller transmitting a message. ‘Sending unit’ means the ATS unit transmitting a message. ‘Significant point’ means a specified geographical location used in defining an ATS route or the flight path of an aircraft and for other navigation and ATS purposes. ‘Situation display’ means an electronic display depicting the position and movement of aircraft and other information as required. ‘Special VFR flight’ means a VFR flight cleared by ATC to operate within a control zone in meteorological conditions below VMC. ‘SSR response’ means the visual indication, in non-symbolic form, on a situation display, of a response from an SSR transponder in reply to an interrogation. ‘Standard instrument arrival (STAR)’ means a designated instrument flight rule (IFR) arrival route linking a significant point, normally on an ATS route, with a point from which a published instrument approach procedure can be commenced. ‘Standard instrument departure (SID)’ means a designated instrument flight rule (IFR) departure route linking the aerodrome or a specified runway of the aerodrome with a specified significant point, normally on a designated ATS route, at which the en-route phase of a flight commences. ‘Stopway’ means a defined rectangular area on the ground at the end of take-off run available, prepared as a suitable area in which an aircraft can be stopped in the case of an abandoned take-off. ‘Surveillance radar’ means radar equipment used to determine the position of an aircraft in range and azimuth. ‘Taxiing’ means movement of an aircraft on the surface of an aerodrome or an operating site under its own power, excluding take-off and landing. ‘Taxiway’ means a defined path on a land aerodrome established for the taxiing of aircraft and intended to provide a link between one part of the aerodrome and another, including: TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 12 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (a) ‘aircraft stand taxilane’ which means a portion of an apron designated as a taxiway and intended to provide access to aircraft stands only; (b) ‘apron taxiway’ which means a portion of a taxiway system located on an apron and intended to provide a through taxi route across the apron; and (c) ‘rapid exit taxiway’ which means a taxiway connected to a runway at an acute angle and designed to allow landing aeroplanes to turn off at higher speeds than are achieved on other exit taxiways thereby minimising runway occupancy times. ‘Terminal control area (TMA)’ means a control area normally established at the confluence of ATS routes in the vicinity of one or more major aerodromes. ‘Total estimated elapsed time’ means for IFR flights, the estimated time required from take-off to arrive over that designated point, defined by reference to navigation aids, from which it is intended that an instrument approach procedure will be commenced, or, if no navigation aid is associated with the destination aerodrome, to arrive over the destination aerodrome. For VFR flights, the estimated time required from take-off to arrive over the destination aerodrome. ‘Touchdown’ means the point where the nominal glide path intercepts the runway. ‘Touchdown zone’ means the portion of a runway, beyond the threshold, where it is intended landing aircraft first contact the runway. ‘Track’ means the projection on the earth’s surface of the path of an aircraft, the direction of which path at any point is usually expressed in degrees from North (true, magnetic or grid). ‘Traffic avoidance advice’ means advice provided by an ATS unit specifying manoeuvres to assist a pilot to avoid a collision. ‘Traffic information’ means information issued by an ATS unit to alert a pilot to other known or observed air traffic which may be in proximity to the position or intended route of flight and to help the pilot avoid a collision. ‘Transfer of control point’ means a defined point located along the flight path of an aircraft, at which the responsibility for providing ATC service to the aircraft is transferred from one control unit or control position to the next. ‘Transferring controller’ means the air traffic controller in the process of transferring the responsibility for providing ATC service to an aircraft to the next ATC unit/air traffic controller along the route of flight. ‘Transferring unit’ means ATC unit in the process of transferring the responsibility for providing ATC service to an aircraft to the next ATC unit/air traffic controller along the route of flight. ‘Transition altitude’ means the altitude at or below which the vertical position of an aircraft is controlled by reference to altitudes. ‘Transition layer’ means the airspace between the transition altitude and the transition level. ‘Transition level’ means the lowest flight level available for use above the transition altitude. ‘Uncertainty phase’ means a situation wherein uncertainty exists as to the safety of an aircraft and its occupants. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 13 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments ‘Unmanned free balloon’ means a non-power-driven, unmanned, lighter-than-air aircraft in free flight. ‘Vectoring’ means the provision of navigational guidance to aircraft in the form of specific headings, based on the use of an ATS surveillance system. ‘VFR’ is the symbol used to designate the visual flight rules. ‘VFR flight’ means a flight conducted in accordance with the visual flight rules. ‘Visual approach’ means an approach by an IFR flight when either part or all of an instrument approach procedure is not completed and the approach is executed in visual reference to terrain. ‘Visual departure’ means a departure by an IFR flight when either part or all of an instrument departure procedure (e.g. standard instrument departure (SID)) is not completed and the departure is executed in visual reference to terrain. ‘Visual meteorological conditions (VMC)’ means meteorological conditions expressed in terms of visibility, distance from cloud, and ceiling, equal to or better than specified minima. ‘VMC’ is the symbol used to designate visual meteorological conditions. ‘VOLMET’ means meteorological information for aircraft in flight. ‘VOLMET broadcast’ means the provision, as appropriate, of current METAR, SPECI, TAF and SIGMET by means of continuous and repetitive voice broadcasts. ‘Waypoint’ means a specified geographical location used to define an area navigation route or the flight path of an aircraft employing area navigation. Waypoints are identified as either: (a) fly-by waypoint — a waypoint which requires turn anticipation to allow tangential interception of the next segment of a route or procedure, or (b) flyover waypoint — a waypoint at which a turn is initiated in order to join the next segment of a route or procedure. 1.1.3. Amendments to Annex IV — Subpart A — Additional organisation requirements for providers of ATS (ATS.OR) Section 1 — General requirements ATS.OR.110 Coordination between aerodrome operators and ATS providers The ATS provider shall establish arrangements with the operator of the aerodrome at which it provides ATS to ensure adequate coordination of activities and services provided as well as exchange of relevant data and information. ATS.OR.115 Coordination between military authorities and ATS providers Without prejudice to Article 6 of Commission Regulation (EC) No 2150/2005, ATS providers shall ensure that their ATS 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. (Annex 11 — Section 2.17.3.1, first sentence) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 14 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments ATS.OR.120 Coordination between meteorological and ATS providers (a) To ensure that aircraft receive the most up-to-date meteorological information for aircraft operations, the ATS provider shall arrange with the meteorological services provider for ATS personnel: (1) in addition to using indicating instruments, to report, if observed by ATS personnel or communicated by aircraft, such other meteorological elements as may be agreed upon; (2) to report as soon as possible to the associated meteorological office meteorological phenomena of operational significance, if observed by ATS personnel or communicated by aircraft, which have not been included in the aerodrome meteorological report; (3) to report as soon as possible to the associated meteorological office 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) The ATS 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. (Annex 11 — Sections 2.20.1 and 2.20.2) ATS.OR.125 Coordination between aeronautical information services and ATS providers (a) The ATS providers shall provide to the relevant aeronautical information services provider the aeronautical information to be published as necessary to permit the utilisation of such ATS. (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, the ATS provider shall arrange 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 ATS personnel or reported by aircraft; and (4) any other information considered to be of operational significance. (c) Before introducing changes to the air navigation system elements under its responsibility, the ATS 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. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 15 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (d) The ATS 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/data subject to AIRAC cycle. (Annex 11 — Sections 2.1.4, 2.21.1, 2.21.2, 2.21.3 second sentence) ATS.OR.130 Time in ATS (a) The ATS provider shall ensure that ATS units are equipped with clocks indicating the time in hours, minutes and seconds, clearly visible from each operating position in the unit concerned. (b) The ATS provider shall ensure that ATS 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 ATS 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. (Annex 11 — Sections 2.25.2, 2.25.3, 2.25.4 (second sentence of Section 2.25.3 transposed as SERA.3401(c) with a slightly modified text)) ATS.OR.135 Contingency arrangements The ATS provider shall develop contingency plans as required in ATM/ANS.OR.A.070 in close coordination with the ATS providers responsible for the provision of services in adjacent portions of airspace and with airspace users concerned. (Annex 11 — Section 2.30) ATS.OR.140 Failure and irregularity of systems and equipment The ATS provider shall establish appropriate arrangements for ATS 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 and/or the provision of ATS. (PANS ATM — Section 4.14) ATS.OR.145 Operation of ATC service (a) The ATS 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. (b) For all airspace between FL 290 and FL 410 inclusive, the ATS providers concerned shall participate to the Reduced Vertical Separation Minima (RVSM) Monitoring programme instituted for monitoring the height-keeping performance of aircraft operating at these levels, in order to ensure that the continued application of this vertical separation minimum meets the safety objectives. (Annex 11 — Sections 3.3.2 and 3.3.5.1) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 16 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments ATS.OR.150 Transfer of responsibility for control (a) The ATS provider(s) shall specify applicable coordination procedures for transfer of responsibility for control of flights, including transfer of control points, in letters of agreement and operation manuals, as appropriate. (b) The ATS provider(s) shall establish procedures between ATS units and/or sectors for the transfer of air– ground communication of aircraft in letters of agreement and operation manuals, as appropriate. Section 4 — Requirements for communications ATS.OR.400 Aeronautical mobile service (air–ground communications) — General (a) The ATS provider shall use voice and/or data link in air–ground communications for ATS purposes. (b) When providing ATS surveillance service, the ATS provider shall ensure that the level of reliability and availability of communication systems are such that the possibility of system failures or significant degradations is very remote, and that adequate backup facilities are provided. (c) When direct pilot–controller two-way voice or data link communications are used for the provision of ATC service, recording facilities shall be provided 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 FIS and AFIS, recording facilities on all such air–ground communication channels shall be provided by the ATS provider, when so prescribed by the competent authority. (Annex 11 — Sections 6.1.1.1 and 6.1.1.3, PANS ATM — Section 8.3.1) ATS.OR.405 Very high frequency (VHF) emergency channel (a) The emergency channel (121.500 MHz) shall be used only for genuine emergency purposes, as broadly outlined in the following, to provide: (1) a clear channel between aircraft in distress or emergency and a ground station when the normal channels are being utilised for other aircraft; (2) a VHF communication channel between aircraft and aerodromes, not normally used by international air services, in case of an emergency condition arising; (3) 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) air–ground communication with aircraft when airborne equipment failure prevents the use of the regular channels; (5) a channel for the operation of emergency locator transmitters (ELTs), and for communication between survival craft and aircraft engaged in search and rescue operations; and (6) a common VHF channel for communication between civil aircraft and intercepting aircraft or intercept control units and between civil or intercepting aircraft and ATS units in the event of interception of the civil aircraft. (b) The ATS provider shall provide the frequency 121.500 MHz at: TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 17 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (1) all area control centres and flight information centres; (2) aerodrome control towers and approach control offices serving international aerodromes and international alternate aerodromes; and (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). (Annex 10 — Volume V, Sections 4.1.3.1.1 and 4.1.3.1.2) ATS.OR.410 Aeronautical mobile service (air–ground communications) — For flight information service (a) The ATS 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 unit providing flight information service and appropriately equipped aircraft flying anywhere within the flight information region. (b) The ATS provider shall ensure, to the practicable extent and as approved by the competent authority, 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 defined as in ATS.TR.110(a)(3) or, when such airspace is not defined, in the vicinity of the aerodrome. (Annex 11 — Sections 6.1.2.1 and 6.1.2.2) ATS.OR.415 Aeronautical mobile service (air–ground communications) — For area control service The ATS provider shall ensure that air–ground communication facilities enable two-way communications to take place between a unit providing area control service and appropriately equipped aircraft flying anywhere within the control area(s). (Annex 11 — Section 6.1.3.1) ATS.OR.420 Aeronautical mobile service (air–ground communications) — For approach control service (a) The ATS 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. (Annex 11 — Sections 6.1.4.1 and 6.1.4.2) ATS.OR.425 Aeronautical mobile service (air–ground communications) — For aerodrome control service (a) The ATS 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. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 18 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (b) Where conditions warrant, the ATS provider shall provide separate communication channels for the control of traffic operating on the manoeuvring area. (Annex 11 — Sections 6.1.5.1 and 6.1.5.2) ATS.OR.430 Aeronautical fixed service (ground–ground communications) — General (a) The ATS service provider shall ensure that direct-speech and/or data link communications are used in ground–ground communications for ATS purposes. (b) When communication for ATC coordination purposes is supported by automation, the ATS provider shall ensure that the failure of such automated coordination is presented clearly to the controller(s) responsible for coordinating flights at a transferring unit. (Annex 11 — Section 6.2.1.1, PANS ATM — Section 10.1.6 first sentence) ATS.OR.435 Aeronautical fixed service (ground–ground communications) — Communication within a flight information region (a) Communications between ATS units (1) The ATS 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, unless co-located; (ii) approach control units; (iii) aerodrome control towers; (iv) AFIS units. (2) The ATS provider shall ensure that an area control centre, in addition to being connected to 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) The ATS provider shall ensure that an approach control unit, in addition to being connected to 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(s); (ii) with relevant AFIS unit(s); and (iii) when separately established, the associated air traffic services reporting office(s). (4) The ATS provider shall ensure that an aerodrome control tower or an AFIS unit, in addition to being connected to the flight information centre, the area control centre and the approach TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 19 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments 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 ATS units and other units (1) The ATS 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 office serving the centre; (iii) the aeronautical telecommunications station serving the centre; (iv) appropriate aircraft operator’s 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) The ATS 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, fire, etc.); (iii) the meteorological office serving the unit concerned; (iv) the aeronautical telecommunications 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 ATS unit concerned and the military unit(s) responsible for control of interception operations within the area of responsibility of the ATS unit, in order to fulfil obligations established in Section 11 of Commission 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 can be established instantaneously, and for other purposes the communications can normally be established within 15 seconds; and (ii) printed communications, when a written record is required; the message transit time for such communications being no longer than 5 minutes. (2) In all cases not covered by point (c)(1), the communication facilities shall include provisions for: TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 20 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (i) communications by direct speech alone, or in combination with data link communications, whereby the communications can normally be established within 15 seconds; and (ii) printed communications, when a written record is required; the message transit time for such communications being no longer than 5 minutes. (3) In all cases where automatic transfer of data to and/or from ATS computers is required, suitable facilities for automatic recording shall be provided. (4) The communication facilities required under points (b)(2)(i);(ii);(iii);(iv) shall include provisions for communications by direct speech arranged for conference communications whereby the communications can normally be established within 15 seconds. (5) All facilities for direct-speech or data link communications between ATS units and between ATS units and other units described under points (b)(1) and (b)(2) shall be provided with automatic recording. (Annex 11 — Sections 6.2.2.1.1, 6.2.2.1.2, 6.2.2.1.3, 6.2.2.1.4, 6.2.2.2.1, 6.2.2.2.2, 6.2.2.2.3, 6.2.2.3.1, 6.2.2.3.2, 6.2.2.3.3, 6.2.2.3.5, 6.2.2.3.6 and 6.2.2.3.7) ATS.OR.440 Aeronautical fixed service (ground–ground communications) — Communication between flight information regions (a) The ATS 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. These 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) The ATS providers 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 can be established instantaneously, and for other purposes the communications can normally be 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, the ATS 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; and (3) are provided with automatic recording. (d) The ATS providers concerned shall ensure that adjacent ATS units are connected in all cases where special circumstances exist. (e) Wherever local conditions are such that it is necessary to clear aircraft into an adjacent control area prior to departure, the ATS providers concerned shall ensure that an approach control unit and/or aerodrome control tower are connected with the area control centre serving the adjacent area. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 21 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (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 or ADS-C data, the communications can be established instantaneously, and for other purposes, the communications can normally be established within 15 seconds. (g) The ATS provider shall provide suitable facilities for automatic recording in all cases where automatic exchange of data between ATS computers is required. (Annex 11 — Sections 6.2.3.1, 6.2.3.1.1, 6.2.3.1.2, 6.2.3.1.3, 6.2.3.1.4, 6.2.3.2, 6.2.3.3, 6.2.3.4 and 6.2.3.5) ATS.OR.445 Aeronautical fixed service (ground–ground communications) — Procedures for direct-speech communications The ATS provider shall develop appropriate procedures for direct-speech communications to permit immediate connections to be made for very urgent calls concerning the safety of aircraft, and the interruption, if necessary, of less urgent calls in progress at the time. (Annex 11 — Section 6.2.4) ATS.OR.450 Communications for the control of vehicles other than aircraft on manoeuvring areas at controlled aerodromes (a) The ATS provider shall provide two-way radiotelephony communication facilities for aerodrome control service for the control of vehicles on the manoeuvring area, except where communication by a system of visual signals is deemed to be adequate. (b) When conditions warrant, separate communication channels for the control of vehicles on the manoeuvring area shall be provided. (c) Automatic recording facilities on all channels in point (b) shall be provided. (Annex 11 — Sections 6.3.1.1 and 6.3.1.2) ATS.OR.455 Automatic recording of surveillance data The ATS 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 ATS, are automatically recorded for use in accident and incident investigations, search and rescue, ATC and surveillance systems evaluation and training. (Annex 11 — Section 6.4.1.1) ATS.OR.460 Retention of recorded information and data (a) The ATS provider shall retain for a period of at least 30 days the following: (1) recordings of communications channels, as specified in ATS.OR.400(b); (2) recordings of data and communications, as specified in ATS.OR.435(c)(3), (4) and (5); (3) recordings of data and communications, as specified in ATS.OR.440(g); (4) recordings of communications, as specified in ATS.OR.450; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 22 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (5) recordings of data, as specified in ATS.OR.455; (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. (Annex 11 — Sections 6.1.1.4, 6.2.2.3.8, 6.2.3.6, 6.3.1.3 and 6.4.1.2 identical to Annex 10 — Volume II, Section 3.5.1.5 ‘Records of communications’, PANS ATM — Section 4.13.4) ATS.OR.465 Background communication and aural environment recording Air traffic control units shall be equipped with devices that record background communication and the aural environment at air traffic controller work stations, capable of retaining the information recorded during at least the last 24 hours of operation. (Annex 11 — Section 3.3.3) Section 5 — Requirements for information ATS.OR.500 Meteorological information — General (a) The ATS provider shall ensure that up-to-date information on existing and forecast meteorological conditions are made available to the relevant ATS units as necessary for the performance of their respective functions. (b) 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, shall be supplied to the relevant ATS 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 ATS personnel and with a frequency which satisfies the requirements of the ATS units concerned. (Annex 11 — Sections 7.1.1.1 and 7.1.1.2) ATS.OR.505 Meteorological information for flight information centres and area control centres (a) The ATS provider shall ensure that flight information centres and area control centres are supplied with the meteorological information stipulated in MET.OR.245(f) and (g), particular emphasis being given to the occurrence or expected occurrence of deterioration in a weather element as soon as this can be determined. These reports and forecasts shall cover the flight information region or control area and, if so required by the competent authority, such other areas. (b) The ATS 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. (Annex 11 — Sections 7.1.2.1 and 7.1.2.2) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 23 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments ATS.OR.510 Meteorological information for units providing approach control service (a) The ATS 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 MET.OR.242(b). (b) Special reports and amendments to forecasts shall be communicated to the units providing approach control service as soon as they are necessary in accordance with established criteria, without waiting for the next routine report or forecast. (c) The ATS 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. (d) The ATS 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. (e) The ATS provider shall ensure that units providing approach control service for final approach, landing and take-off are equipped with surface wind display(s). The display(s) shall be related to the same location(s) of observation and be fed from the same sensor(s) as the corresponding display(s) in the aerodrome control tower and in the meteorological station, where such a station exists. (f) The ATS 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(s) permitting read-out of the current runway visual range value(s). The display(s) shall be related to the same location(s) of observation and be fed from the same sensor(s) as the corresponding display(s) in the aerodrome control tower and in the meteorological station, where such a station exists. (g) The ATS 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(s) permitting read-out of the current value(s) of the height of cloud base. The displays shall be related to the same location(s) of observations and be fed from the same sensor(s) as the corresponding display(s) in the aerodrome control tower and in the meteorological station, where such a station exists. (h) The ATS provider shall ensure that units providing approach control service for final approach, landing and take-off are supplied with information on wind shear which could adversely affect aircraft on the approach or take-off paths or during circling approach. (Annex 11 — Sections 7.1.3.1, 7.1.3.2, 7.1.3.3, 7.1.3.4, 7.1.3.5 and 7.1.3.6) ATS.OR.515 Meteorological information for aerodrome control towers and AFIS units (a) The ATS 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 MET.OR.242(a). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 24 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (b) Special reports and amendments to forecasts shall be communicated to the aerodrome control towers and AFIS units as soon as they are necessary in accordance with established criteria, without waiting for the next routine report or forecast. (c) The ATS provider shall ensure that aerodrome control towers and AFIS units are provided with current pressure data for setting altimeters for the aerodrome concerned. (d) The ATS provider shall ensure that aerodrome control towers and AFIS units are equipped with surface wind display(s). The display(s) shall be related to the same location(s) of observation and be fed from the same sensor(s) as the corresponding display(s) in the 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. (e) The ATS 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(s) permitting read-out of the current runway visual range value(s). The display(s) shall be related to the same location(s) of observation and be fed from the same sensor(s) as the corresponding display(s) in the meteorological station, where such a station exists. (f) The ATS 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(s) permitting read-out of the current value(s) of the height of cloud base. The displays shall be related to the same location(s) of observations and be fed from the same sensor(s) as the corresponding display(s) in the aerodrome control tower and AFIS units and in the meteorological station, where such a station exists. (g) The ATS provider shall ensure that aerodrome control tower and AFIS units are supplied with 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. (h) The ATS provider shall ensure that aerodrome control towers and AFIS units and/or other appropriate units are supplied with aerodrome warnings, in accordance with MET.OR.215(b). (Annex 11 — Sections 7.1.4.1, 7.1.4.2, 7.1.4.3, 7.1.4.4, 7.1.4.5, 7.1.4.6 and 7.1.4.7) ATS.OR.520 Information on aerodrome conditions and the operational status of associated facilities The ATS 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(s) with which they are concerned, as reported by the aerodrome operator. (Annex 11 — Section 7.2) ATS.OR.525 Information on the operational status of navigation services (a) The ATS provider shall ensure that ATS units are kept currently 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. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 25 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (b) The ATS providers shall ensure that information referred to in point (a) is received by the appropriate ATS unit(s) on a timely basis consistent with the use of the service(s) and aid(s) involved. (Annex 11 — Sections 7.3.1 and 7.3.2) 1.1.4. Amendments to Annex IV — Subpart B — Technical requirements for providers of ATS (ATS.TR) Section 1 — General ATS.TR.100 Working methods and operating procedures for providers of air traffic services (a) An air traffic services provider shall be able to demonstrate that its working methods and operating procedures are compliant with: (1) Commission Implementing Regulation (EU) No 923/20121; and (2) the standards laid down in the following Annexes to the Chicago Convention, as far as they are relevant to the provision of air traffic services in the airspace concerned: (i) Annex 10 on aeronautical telecommunications, Volume II on communication procedures including those with PANS Status in its 6th edition of October 2001, including all amendments up to and including No 89; and (ii) without prejudice to Regulation (EU) No 923/2012, Annex 11 on air traffic services in its 13 th edition of July 2001, including all amendments up to and including No 49. (b) Notwithstanding point (a), for air traffic services units providing services for flight testing, the competent authority may specify additional or alternative conditions and procedures to those contained in point (a) when so required for the provision of services for flight testing. ATS.TR.100 Objectives of the air traffic services (ATS) The objectives of the ATS 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. (Annex 11 — Section 2.2) (transposed as SERA.7001) 1 Commission Implementing Regulation (EU) No 923/2012 of 26 September 2012 laying down the common rules of the air and operational provisions regarding services and procedures in air navigation and amending Implementing Regulation (EU) No 1035/2011 and Regulations (EC) No 1265/2007, (EC) No 1794/2006, (EC) No 730/2006, (EC) No 1033/2006 and (EU) No 255/2010 (OJ L 281, 13.10.2012, p. 1). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 26 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments ATS.TR.105 Divisions of the ATS The ATS shall comprise the services identified as follows: (a) The air traffic control (ATC) service, to accomplish objectives as in points (a), (b) and (c) of ATS.TR.100, this service being divided in three parts as follows: (1) Area control service: the provision of ATC service for controlled flights, except for those parts of such flights described in points (a)(2) and (a)(3), in order to accomplish the objectives established in points (a) and (c) of ATS.TR.100; (2) Approach control service: the provision of ATC 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 ATS.TR.100; (3) Aerodrome control service: the provision of ATC service for aerodrome traffic, except for those parts of flights described in point (a)(2), in order to accomplish the objectives established in points (a), (b) and (c) of ATS.TR.100. (b) The flight information service (FIS) and/or air traffic advisory service, to accomplish the objective established in point (d) of ATS.TR.100; (c) The alerting service, to accomplish the objective established in point (e) of ATS.TR.100. (Annex 11 — Sections 2.3, 2.3.1, 2.3.2 and 2.3.3, PANS ATM — Section 9.1.4) ATS.TR.110 Establishment of the units providing ATS (a) The ATS 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 ATC unit having adequate facilities for the discharge of such responsibility; (2) ATC units shall be established to provide ATC service, flight information service and alerting service within control areas, control zones and at controlled aerodromes. (3) Aerodrome flight information service (AFIS) units shall be established to provide flight information service and alerting service at AFIS aerodromes and within the portion of airspace associated with such aerodromes. (b) Air traffic services reporting office(s) or other arrangements shall be established for the purpose of receiving reports concerning ATS and flight plans before departure. (Annex 11 — Sections 2.9.1 and 2.9.2, PANS ATM definition of ‘air traffic services reporting office’) ATS.TR.115 Identification of ATS units and airspaces (a) ATS units shall be unambiguously named by the competent authority, 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; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 27 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (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 ATS units shall be complemented by one of the following, as appropriate: (1) area control centre — CONTROL; (2) approach control — APPROACH; (3) aerodrome control — TOWER; (4) surface movement control — GROUND; (5) flight information centre — INFORMATION; and (6) aerodrome flight information unit — AFIS. (Annex 11 —Sections 2.11.1 and 2.11.2, Annex 10 — Volume II, Section 5.2.1.7.1) ATS.TR.120 Coordination between military authorities and ATS In order to eliminate or reduce the need for interceptions, the ATS provider shall ensure that all pertinent data concerning flight plans, two-way communications and position reporting stipulated in Commission Implementing Regulation (EU) No 923/2012, which apply to any area or route as determined by the competent authority, is available to the appropriate ATS units specifically for the purpose of facilitating identification of civil aircraft. (Annex 11 — Section 2.17.3.1 second sentence) ATS.TR.125 Language for communication between ATS units Except when communications between ATS units are conducted in a mutually agreed language, the English language shall be used for such communications. (Annex 11 — Section 2.29.2) ATS.TR.130 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) below, 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 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; and TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 28 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (2) for precision approach runways. (PANS ATM — Sections 4.10.1.1, 4.10.1.2, 4.10.1.3)(4.10.1.1 and 4.10.1.3 transposed as SERA.8015(eb)(1), 4.10.1.2 transposed as SERA.8015(eb)(5)) ATS.TR.135 Determination of the transition level (a) The appropriate ATS 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 at least 300 m (1 000 ft) above the transition altitude to permit the transition altitude and the transition level to be used concurrently in cruising flight, with vertical separation ensured. (PANS ATM — Section 4.10.2.1, Doc.7030 (EUR) — Section 6.3.1.2) ATS.TR.140 Minimum cruising level for IFR flights (a) The ATC 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) ATC 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; and (3) pass the lowest usable flight level or levels on to pilots on request. (PANS ATM — Sections 4.10.3.1 and 4.10.3.2) ATS.TR.145 Provision of altimeter setting information (a) The appropriate ATS 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 ACCs shall have available for transmission to aircraft, on request, an appropriate number of QNH reports or forecast pressures for the FIRs 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) A QNH altimeter setting shall be included in the descent clearance when first cleared at an altitude below the transition level, in approach clearances or clearances to enter the traffic circuit, and in taxi clearances for departing aircraft except when it is known that the aircraft has already received the information in a directed transmission. (e) A QFE altimeter setting as described in ATS.TR.130(b) shall be provided to aircraft on request or on a regular basis in accordance with local arrangements. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 29 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (f) The appropriate ATS units shall round down the altimeter settings provided to aircraft to the nearest lower whole hectopascal. (PANS ATM — Sections 4.10.4.1, 4.10.4.2, 4.10.4.3, 4.10.4.5, 4.10.4.6 and 4.10.4.7) (Section 4.10.4.3 transposed as SERA.8015(eb)(2), Section 4.10.4.5 transposed as SERA.8015(eb)(3), Section 4.10.4.6 transposed as SERA.8015(eb)(4)) ATS.TR.150 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 by any of the following units, persons or authorities whenever safety requires such action: (1) the approach control unit or the appropriate ACC; (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 ACC 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. (PANS ATM — Sections 7.13.1 and 7.13.3) ATS.TR.155 Aeronautical ground lights The ATS provider shall establish procedures for the operation of aeronautical ground lights, whether or not they are on or in the vicinity of an aerodrome. (PANS ATM — Section 7.15.1) ATS.TR.160 ATS surveillance services (a) The ATS provider may use ATS surveillance systems in the provision of ATS. (b) When providing ATS surveillance services, the ATS provider shall ensure that: (1) the ATS surveillance system(s) in use provides (provide) for a continuously updated presentation of surveillance information, including position indications; (2) the number of aircraft simultaneously provided with ATS surveillance services which can be safely handled under the prevailing circumstances is determined; (3) controllers are at all times in possession of full and up-to-date information regarding: (i) established minimum flight altitudes within the area of responsibility, including the necessary temperature correction; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 30 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (ii) the lowest usable flight level or levels determined in accordance with ATS.TR.135 and ATS.TR.140; and (iii) established minimum altitudes applicable to procedures based on tactical vectoring, including the necessary temperature correction. (c) 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. (d) When providing ATS surveillance services, the ATS provider shall, when relevant, 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(s); (8) SSR transponder failure, in accordance with the provisions of Section 13 of Commission Implementing Regulation (EU) No 923/2012; (9) ATS surveillance-based safety-related alerts and warnings, when implemented. (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. (PANS ATM — Sections 8.2.2 and 8.4.2 (the principle, not the exact text), 8.6.2.1.1, 8.6.2.1.2, 8.6.8.1 and 8.8.2.1)(PANS ATM Section 8.8.2.1 transposed as SERA.7002) ATS.TR.165 ATS provision for flight testing Notwithstanding the provisions in Subpart B of this Annex, for ATS units providing services for flight testing, the competent authority may specify additional or alternative conditions and procedures to those contained in Subpart B of this Annex when so required for the provision of services for flight testing. (ATM/ANS Common Requirements Regulation Annex IV, Subpart B, ATS.TR.100(b)) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 31 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Section 2 — ATC service ATS.TR.200 Application ATC 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. (Annex 11 — Section 3.1) (transposed as SERA.8001) ATS.TR.205 Provision of ATC service The parts of ATC service described in ATS.TR.105(a) shall be provided by the various units as follows: (a) Area control service: (1) by an area control centre; or (2) by 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: (1) by 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; (2) by an approach control unit when it is necessary or desirable to establish a separate unit. (c) Aerodrome control service: by an aerodrome control tower. (Annex 11 — Section 3.2) ATS.TR.210 Operation of ATC service (a) In order to provide ATC service, an ATC 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 and/or information 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. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 32 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (b) Clearances issued by ATC 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; except that, when 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) above 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 as in ATS.TR.255, or when a reduction in separation minima in the vicinity of aerodromes can be applied, separation by an ATC 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 Commission 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 this level. Geometric height information shall not be used to establish vertical separation; (2) horizontal separation, obtained by providing: (i) longitudinal separation, by maintaining an interval between aircraft operating along the same, converging or reciprocal tracks, expressed in time or distance; or (ii) lateral separation, by maintaining aircraft on different routes or in different geographical areas. (d) When the controller becomes aware that the type of separation or minimum used to separate two aircraft cannot be maintained, the controller shall establish another type of separation or another minimum prior to the time when the current separation minimum would be infringed. (Annex 11 — Sections 3.3.1, 3.3.4 and 3.3.5, PANS ATM — Section 5.2.1.4, PANS ATM — Section 8.5.5.1.1 third sentence) (Section 3.3.1 transposed as SERA.8005(a), Section 3.3.4 transposed as SERA.8005(b), Section 3.3.5 transposed as SERA.8005(c)) ATS.TR.215 Selection and notification of separation minima (a) The selection of separation minima for application within a given portion of airspace shall be made by the ATS provider responsible for the provision of ATS 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 TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 33 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments circumstances, the selection of separation minima shall be made in consultation between the ATS providers responsible for the provision of ATS in neighbouring airspace. (c) Details of the selected separation minima and of their areas of application shall be notified: (1) to the ATS units concerned; and (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. (Annex 11 — Sections 3.4.1 and 3.4.2) (3.4.1 transposed as SERA.8010(a) and (b), and 3.4.2 transposed as SERA.8010(c)) ATS.TR.220 Application of wake turbulence separation ATC units shall apply wake turbulence separation minima to aircraft in the approach and departure phases of flight under the following circumstances: (a) an aircraft is operating directly behind another aircraft at the same altitude or less than 300 m (1 000 ft) below it; or (b) both aircraft are using the same runway, or parallel runways separated by less than 760 m (2 500 ft); or (c) an aircraft is crossing behind another aircraft, at the same altitude or less than 300 m (1 000 ft) below it, except for arriving VFR flights, and for 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, for which the ATC unit shall issue caution for wake turbulence. (PANS ATM — Sections 5.8.1.1, 5.8.1.2 first sentence, 8.7.3.4.1) (Section 8.7.3.4.1 transposed in SERA.8012, the text not being identical) ATS.TR.225 Responsibility for control (a) A controlled flight shall be under the control of only one ATC 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 ATC unit. However, control of an aircraft or groups of aircraft may be delegated to other ATC units provided that coordination between all ATC units concerned is assured. (Annex 11 — Sections 3.5.1 and 3.5.2) 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 ATC 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 TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 34 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments 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 from the unit providing approach control service to the aerodrome control tower, when the aircraft: (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 visual meteorological conditions, or (B) is at a prescribed point or level; or (C) has landed, as specified in letters of agreement and operation manuals, as appropriate. (ii) Departing aircraft — The responsibility for control of a departing aircraft shall be transferred from the aerodrome control tower to the unit providing approach control service: (A) when visual meteorological conditions 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, or (c) at a prescribed point or level, (B) when instrument meteorological conditions prevail at the aerodrome: (a) immediately after the aircraft is airborne, or (b) at a prescribed point or level, as specified in letters of agreement and operation manuals, as appropriate. (4) Between control sectors/positions within the same ATC unit The responsibility for control of an aircraft shall be transferred from one control sector/position to another control sector/position within the same ATC unit at a point, level or time, as specified in ATS unit instructions. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 35 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (b) Coordination of transfer (1) Responsibility for control of an aircraft shall not be transferred from one ATC unit to another without the consent of the accepting control unit, which shall be obtained in accordance with points (b)(2), (b)(3), (b)(4) and (b)(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; and (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 and/or data link communications with and assumed control of the aircraft concerned. (7) Standardised phraseology shall be used in the coordination between ATS units and/or sectors. Only when standardised phraseology cannot serve an intended transmission, plain language shall be used. (Annex 11 — Sections 3.6.1, 3.6.1.1, 3.6.1.2, 3.6.1.3.1, 3.6.1.3.2 3.6.1.4, 3.6.2.1, 3.6.2.2, 3.6.2.2.1, 3.6.2.2.2, 3.6.2.3, 3.6.2.4 and 3.6.2.5)(Point (b)(7) partially duplicated from SERA.14001) ATS.TR.235 ATC clearances (a) ATC clearances shall be based solely on the requirements for providing ATC 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) ATC 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. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 36 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (4) When the pilot-in-command of an aircraft informs an ATC unit that an ATC clearance is not satisfactory, the ATC 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, a controller providing ATS surveillance service shall issue clearances such that the prescribed obstacle clearance will exist at all times until the aircraft reaches the point where the pilot will re-join the flight plan route, or join 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; and (ii) The phrase ‘cleared flight planned route’ shall not be used when granting a re-clearance. (4) level(s) 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 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), the ATS provider shall assess the necessity for establishing standard departure and arrival routes and associated procedures to facilitate: (1) the safe, orderly and expeditious flow of air traffic; (2) the 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(s) except when the aircraft or vehicles concerned are seen by the appropriate controller and pilot. The aircraft or vehicle causing the condition in the clearance issued TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 37 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments shall be the first aircraft/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; and (4) a brief reiteration of the condition. (g) Read-back of clearances and safety-related information (1) The controller shall listen to the read-back concerning safety-related parts of ATC clearances and instructions as defined in SERA.8015(e)(1) and (2) of Commission Implementing Regulation (EU) No 923/2012, to ascertain that the clearance and/or instruction has 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 ATS provider. (h) Coordination of clearances An ATC clearance shall be coordinated between ATC 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: (i) when it has been possible, prior to departure, to coordinate the clearance between all the units under whose control the aircraft will come; or (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 ATS unit, aircraft shall contact a downstream ATC 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 ATC 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 ATC 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 TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 38 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments 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. (Annex 11 — Sections 3.7, 3.7.1.1, 3.7.1.2, 3.7.2.1, 3.7.2.2, 3.7.3.1.2, 3.7.3.2, 3.7.4, 3.7.4.1, 3.7.4.2, 3.7.4.2.1, , 3.7.4.2.1.1, 3.7.4.2.1.2, 3.7.4.2.1.3 3.7.4.3 and 3.7.4.4, PANS ATM — Sections 4.5.1.1, 4.5.1.2, 4.5.1.4, 4.5.1.5, 4.5.7.2.1 (first sentence), 4.5.7.2.2, 4.5.7.4.1, 4.5.7.4.2, 8.6.5.2 as amended by EANPG #57 Final Report, 12.2.7, Annex 2 — Section 3.6.1.1) (Section 3.7 transposed as SERA.8015(a), Section 3.7.1.1 transposed as SERA.8015(d), Sections 3.7.2.1 and 3.7.2.2 transposed as SERA.8015(c), Section 3.7.3.1.2 transposed as SERA.8015(e)(3), Section 3.7.3.2 transposed as SERA.8015(e)(3), Sections 3.7.4, 3.7.4.1, 3.7.4.2, 3.7.4.2.1, 3.7.4.2.1.1, 3.7.4.2.1.2, 3.7.4.2.1.3, 3.7.4.3 and 3.7.4.4 transposed as SERA.8015(f)) (Annex 2 — Section 3.6.1.1 transposed as SERA.8015(b)(2)) (PANS ATM — Sections 4.5.1.1, 4.5.1.2, 4.5.1.4, 4.5.1.5 transposed as SERA.8015(a), Sections 4.5.7.2.1 (first sentence) and 4.5.7.2.2 transposed as SERA.8015(d)(3), Sections 4.5.7.4.1 and 4.5.7.4.2 transposed as SERA.8015(ea), Section 12.2.7 transposed as SERA.8015(ec)) 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 ILS/MLS sensitive area(s) when Category II or Category III precision instrument operations are in progress; (2) subject to the provisions in point (c), the minimum separation between vehicles and taxiing aircraft shall be as specified by the ATS 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, taxiing or being towed; (2) vehicles shall give way to other vehicles towing aircraft; (3) vehicles shall give way to other vehicles in accordance with ATS unit instructions; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 39 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (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. (Annex 11 — Sections 3.8.1, 3.8.2, 3.8.3 and 3.8.4) (Sections 3.8.1, 3.8.2, 3.8.3 and 3.8.4 transposed as SERA.3210(d)(4)) 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 ATS provider 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; and (c) provide advice and assistance for the safe and efficient movement of aircraft and vehicles on the manoeuvring area. (Annex 11 — Section 3.10) ATS.TR.250 Essential traffic information (a) Essential traffic information shall be given to controlled flights concerned whenever they constitute essential traffic to each other. (b) Information on essential local traffic known to the controller shall be given to departing and arriving aircraft concerned. (PANS ATM — Sections 5.10.1.2 and 6.2.1) ATS.TR.255 Operations on parallel or near-parallel runways Independent or dependent approaches or departures to/from parallel or near-parallel runways shall be established by the ATS provider and approved by the competent authority. (New provision establishing general principle to allow such types of operations. PANS ATM — Section 6.7 is relevant) ATS.TR.260 Selection of the runway in use The unit providing aerodrome control service 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(s); TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 40 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (g) other factors indicated in local instructions. (PANS ATM — Section 7.2.2 (second sentence)) ATS.TR.265 Control of aerodrome surface traffic in conditions of low visibility (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 according to the applicable aerodrome design specifications; (2) the longitudinal separation on taxiways shall be as specified for each particular aerodrome by the ATS provider and approved by the competent authority. This separation shall take 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) In coordination with the aerodrome operator, provisions applicable to the start and continuation of precision approach category II/III operations as well as departure operations in RVR conditions less than a value of 550 m shall be established by the ATS provider and approved by the competent authority. (PANS ATM — Sections 7.12.1.1, 7.12.1.1.1,.1.2 and 7.12.2.1) 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 permitted by the competent authority for helicopters in special cases such as, but not limited to, police, medical, search and rescue operations and fire-fighting flights, the following additional conditions shall be applied: (1) such 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 kts IAS or less to give adequate opportunity to observe other traffic and any obstacles in time to avoid a collision; and (b) An ATC 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 zone or aerodrome traffic circuit when the reported meteorological conditions at that aerodrome are below the following minima: (1) the ground visibility is less than 1 500 m or, for helicopters, less than 800 m; (2) the ceiling is less than 180 m (600 ft). (c) An ATC unit shall handle requests for such authorisation individually. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 41 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (PANS ATM — Sections 7.14.1, 7.14.1.1 and 7.14.1.3) (Sections 7.14.1 and 7.14.1.3 transposed with modifications in SERA.5010) ATS.TR.275 Pressure-altitude-derived level information (a) Unless otherwise prescribed by the competent authority, verification of the pressure-altitude-derived level information displayed to the controller shall be effected at least once by each suitably equipped ATC unit on initial contact with the aircraft concerned or, if this is not feasible, as soon as possible thereafter. (b) Verified pressure-altitude-derived level information shall only be used in the provision of ATS surveillance services to determine that aircraft: (1) maintain a level; (2) vacate a level; (3) pass a level in climb or descent; or (4) reach a level. (PANS ATM — Section 8.5.5.1.2 (first sentence)) (Section 8.5.5.1.2 (first sentence) transposed as SERA.13010(b)) Section 3 — Flight information service ATS.TR.300 Application (a) Flight information service shall be provided by the appropriate ATS units to all aircraft which are likely to be affected by the information and which are: (1) provided with ATC service; or (2) otherwise known to the relevant ATS units. (b) Where ATS units provide both flight information service and ATC service, the provision of ATC service shall have precedence over the provision of flight information service whenever the provision of ATC service so requires. (c) The 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. (Annex 11 — Sections 4.1.1 and 4.1.2, PANS ATM — Sections 9.1.1 and 9.1.2) (Sections 4.1.1 and 4.1.2 transposed as SERA.9001) 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; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 42 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (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; and (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. (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 to aircraft and vehicles operating on the manoeuvring area; (2) the runway in use; (3) messages, including clearances, received from other ATS units to relay to aircraft. (d) ATS units shall transmit, as soon as practicable, special and non-routine air-reports to: (1) other aircraft concerned; (2) the associated meteorological watch office (MWO) in accordance with Appendix 5 to Commission Implementing Regulation (EU) No 923/2012; and (3) other ATS units concerned. Transmissions to aircraft shall be repeated at a frequency and continued for a period of time which shall be determined by the ATS 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. (Annex 11 — Sections 4.2.1, 4.2.2, Recommendation in 4.2.3 and 4.2.4, Circular 211-AN/128, PANS ATM — Section 7.4.1.7 (Title)) (Section 4.2.1 transposed as SERA.9005(a), Section 4.2.2 transposed as SERA.9005(b), Section 4.2.4 transposed as SERA.9005(c), Recommendation in Section 4.2.3 transposed as SERA.12020(a) and (b)) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 43 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments 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 ATS VHF air–ground communication channels. When provided, they shall comprise: (1) one broadcast serving arriving aircraft; or (2) one broadcast serving departing aircraft; or (3) one broadcast serving both arriving and departing aircraft; or (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(s) of the most appropriate terminal navigation aid(s), 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 ATS unit(s) concerned with the provision to aircraft of information relating to approach, landing and take-off, whenever the message has not been prepared by that (those) unit(s). (f) Voice-ATIS broadcasts provided at designated aerodromes for use by international air services shall be available in the English language as a minimum. (g) The Voice-ATIS broadcast message shall, whenever practicable, not exceed 30 seconds, care being taken that the readability of the ATIS message is not impaired by the speed of the transmission or by the identification signal of a navigation aid used for transmission of ATIS. (Annex 11 — Sections 4.3.4.1, 4.3.4.2, 4.3.4.3, 4.3.4.4, 4.3.4.5, 4.3.4.6 and 4.3.4.8 (first sentence)) 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 MET.TR.200(e) and (f), 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. (Annex 11 — Section 4.3.5.1, 4.3.5.1.1 and 4.3.5.2) ATS.TR.320 Automatic terminal information service (voice and/or data link) (a) Whenever Voice-ATIS and/or D-ATIS is provided: TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 44 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (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 ATS provider; (4) individual ATIS messages shall be identified by a designator in the form of a letter of the ICAO spelling alphabet. Designators assigned to consecutive ATIS messages shall be in alphabetical order; (5) aircraft shall acknowledge receipt of the information upon establishing communication with the ATS unit providing approach control service or the aerodrome control tower or AFIS unit, as appropriate; (6) the appropriate ATS 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; and (7) the meteorological information shall be extracted from the local meteorological routine or special report. (b) When rapidly changing meteorological conditions make it inadvisable to include a weather report in the ATIS, the ATIS messages shall indicate that the relevant weather information will be given on initial contact with the appropriate ATS 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 ATS unit shall transmit without delay to the aircraft any element of information that needs updating. (Annex 11 — Sections 4.3.6.1, 4.3.6.2, 4.3.6.3 and 4.3.6.4) (Introductory sentence, points e) and f) of Section 4.3.6.1 transposed as SERA.9010(a)(2), Section 4.3.6.3 transposed as SERA.9010 (a)(3)), Section 4.3.6.4 transposed as SERA.9010 (a)(4)) ATS.TR.325 VOLMET broadcasts and D-VOLMET broadcasts When so prescribed by the competent authority, HF and/or VHF VOLMET broadcasts and/or D-VOLMET service shall be provided, using standard radiotelephony phraseologies. (Annex 11 — Section 4.4, Recommendations in Sections 4.4.1 and 4.4.2) Section 4 — Alerting service ATS.TR.400 Application (a) Alerting service shall be provided by the ATS units: (1) for all aircraft provided with ATC service; (2) in so far as practicable, to all other aircraft having filed a flight plan or otherwise known to the ATS; and TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 45 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (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 when the nature of the emergency is such that the notification would be superfluous. (d) Nevertheless, whenever the urgency of the situation so requires, 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. (Annex 11 — Sections 5.1.1, 5.1.2, 5.1.3 and 5.1.3.1, PANS ATM — Section 7.1.2.2, first sentence) (Section 5.1.1 transposed as SERA.10001(a)) ATS.TR.405 Notification to rescue coordination centres (a) Without prejudice to any other circumstances that may render such notification advisable, ATS units shall, except as prescribed in 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: (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; or (ii) an aircraft fails to arrive within 30 minutes of the estimated time of arrival last notified to or estimated by ATS units, whichever is the later; except when no doubt exists as to the safety of the aircraft and its occupants. (2) Alert phase when: (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; or (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; or (iii) at AFIS aerodromes, under circumstances as prescribed by the competent authority; or TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 46 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (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, except when evidence exists that would allay apprehension as to the safety of the aircraft and its occupants; or (v) an aircraft is known or believed to be the subject of unlawful interference. (3) Distress phase when: (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; or (ii) the fuel on board is considered to be exhausted, or to be insufficient to enable the aircraft to reach safety; or (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; or (iv) information is received or it is reasonably certain that the aircraft is about to make or has made a forced landing, except 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; and (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 ATS 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 in point (a), ATS units shall, without delay, furnish the rescue coordination centre with: (1) any useful additional information, especially on the development of the state of emergency through subsequent phases; or (2) information that the emergency situation no longer exists. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 47 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (Annex 11 — Sections 5.2.1, 5.2.2, 5.2.2.1 and 5.2.3) ATS.TR.410 Use of communication facilities ATS 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. (Annex 11 — Section 5.3) ATS.TR.415 Plotting aircraft in a state of emergency When a state of emergency is considered to exist, the ATS unit(s) 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. (Annex 11 — Section 5.4) 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. (Annex 11 — Sections 5.5.1 and 5.5.2) 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 ATS 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 ATS unit knows or believes that an aircraft is being subjected to unlawful interference, no reference shall be made in ATS 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. (Annex 11 — Sections 5.6.1 and 5.6.2) (5.6.1 transposed as SERA.10005(a), 5.6.2 transposed as SERA.10005(b)) 1.1.5. Amendments to Annex V — Subpart A — Additional organisation requirements for providers of meteorological services (MET.OR) MET.OR.242 Information to be provided to air traffic services units (a) An aerodrome meteorological office shall provide, as necessary, its associate aerodrome control tower and AFIS unit with: (1) […] TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 48 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments MET.OR.245 Meteorological watch and other information Within its area of responsibility, the meteorological watch office shall: […] (f) provide its associated area control centre […] (8) information received on pre-eruption volcanic activity and/or a volcanic eruption as agreed between the meteorological watch office and the ACC/FIC.; (g) when available, provide the relevant ATS units, in accordance with local agreement, information regarding the release into the atmosphere of radioactive materials or toxic chemicals which could affect the airspace used by flights within their area of responsibility. (Annex 11 — Section 7.6) 1.2. Amendments to the SERA Regulation (draft Opinion) (1) The following recital is added: […] (Whereas) the provisions contained in this Regulation should support and complement rules related to the provision of air traffic services contained in Annex 10 Volume II and Annex 11 to the Chicago Convention, ICAO Doc.4444 (PANS ATM) and Commission Implementing Regulation (EU) 2016/1377, to ensure consistency of service provision with pilot actions under this Regulation. […] (2) The definition of ‘controlled aerodrome’ is amended as follows: ‘Controlled aerodrome’ means an aerodrome at which ATC service is provided to aerodrome traffic regardless whether or not a control zone exists. (3) SERA.8005 is amended as follows: SERA.8005 Operation of air traffic control service (a) In order to provide ATC service, an ATC 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 and/or information for the purpose of preventing collision between aircraft under its control and of expediting and maintaining an orderly flow of traffic; (4) […] (b) […] (c) Except for cases of operations on parallel or near-parallel runways as in ATS.TR.255 of Commission Implementing Regulation (EU) 2016/1377, or when a reduction in separation TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 49 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments minima in the vicinity of aerodromes can be applied, separation by an ATC 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 Commission 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 (1000 ft) up to and including FL 410 and a nominal 600 m (2000 ft) above this level. Geometric height information shall not be used to establish vertical separation; (2) […] (4) SERA.8012 (introduced with Regulation (EU) 2016/1185) is amended as follows: SERA.8012 Application of wake turbulence separation Wake turbulence separation minima shall be applied to aircraft in the approach and departure phases of flight under the following circumstances: (a) an aircraft is operating directly behind another aircraft at the same altitude or less than 300 m (1 000 ft) below it; or (b) both aircraft are using the same runway, or parallel runways separated by less than 760 m (2 500 ft); or (c) an aircraft is crossing behind another aircraft, at the same altitude or less than 300 m (1 000 ft) below it., except for arriving VFR flights, and for 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, for which the ATC unit shall issue caution for wake turbulence. (5) SERA.8015 (as amended by Regulation (EU) 2016/1185) is amended as follows: SERA.8015 Air traffic control clearances (a) […] (b) ATC clearances shall be based solely on the requirements for providing ATC service. (1) …. (2) …. (3) …. (4) …… (5) …… (6) 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, a controller providing ATS surveillance service shall issue clearances such that the prescribed obstacle clearance will TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 50 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments exist at all times until the aircraft reaches the point where the pilot will re-join the flight plan route, or join a published ATS route or instrument procedure. (c) […] (d) Contents of clearances An ATC clearance shall indicate: (1) ……; (2) ……; (3) ……; (i) The route of flight shall be detailed in each clearance when deemed necessary, and (ii) The phrase ‘cleared via flight planned route’ shall not be used when granting a re- clearance. (4) […] (6) SERA.9005 is amended as follows: SERA.9005 Scope of flight information service (a) Flight information service shall include the provision of pertinent: (1) ……; (2) …..; (3) …..; (4) …..; (5) …..; (6) …..; (7) information on abnormal aircraft configuration and condition; and (8) …... (b) […] (7) SERA.14095 is amended as follows: SERA.14095 Distress and urgency radiotelephony communication procedures (a) The emergency channel (121.500 MHz) shall be used only for genuine emergency purposes, as broadly outlined in 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; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 51 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (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 ATS units in the event of interception of the civil aircraft. (a) (b) […] (b) (c) […] (d) (d) […] 1.3. Amendments to the upcoming ED Decision issuing the AMC/GM to the ATM/ANS Common Requirements Regulation (draft decision (PART-ATS)) GM1 to Article 3(1b)(a) Determination of the need for ATS ELEMENTS TO DETERMINE THE NEED FOR ATS PROVISION The determination of the need for ATS in a given area and/or aerodrome may be subject to consideration and evaluation of a great number and typology of elements, such as: (a) a mixture of different types of air traffic with aircraft of varying speeds (conventional, jet, etc.) might necessitate the provision of ATS, whereas a relatively greater density of traffic where only one type of operation is involved would not; (b) meteorological conditions might have considerable effect in areas where there is a constant flow of air traffic (e.g. scheduled traffic), whereas similar or worse meteorological conditions might be relatively unimportant in an area where air traffic would be discontinued in such conditions (e.g. local VFR flights); (c) open stretches of water, mountainous, uninhabited or desert areas might necessitate the provision of ATS even though the frequency of operations is extremely low; (d) the complexity of the airspace concerned; and (e) the language(s) to be used in air–ground communications, in the case of AFIS. (Annex 11 — Note to Section 2.4.1, ICAO Circular 211-AN/128 ‘General’ — paragraph 2.) GM2 to Article 3(1b)(a) Determination of the need for ATS UNICOM AERONAUTICAL STATION Where a Member State determines that no requirement exists for the provision of ATS at an aerodrome and its vicinity or in other airspace, a ‘UNICOM’ type aeronautical station may be established, following the Member State arrangements, to facilitate the activities of the aircraft. Such TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 52 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments UNICOM stations may be established in an airspace where Member States have decided that flight information service will be provided, but there is no requirement for mandatory two-way radio communication. In such cases, the Member State should ensure that the aeronautical station established does not provide ATS but acts as an informal facility for exchanges on, for example, aerodrome conditions or other activities at the aerodrome. GM1 to Article 3(1d)(a) Coordination of activities potentially hazardous to civil traffic In determining these arrangements, the following should be applied: (a) the locations or areas, times and durations for the activities should be selected to avoid closure or realignment of established ATS routes, blocking of the most economic flight levels, or delays of scheduled aircraft operations, unless no other options exist; (b) the size of the airspace designated for the conduct of the activities should be kept as small as possible. (Annex 11 — Recommendation in Section 2.18.2.1) GM2 to Article 3(1d)(a) Coordination of activities potentially hazardous to civil traffic COORDINATION OF MILITARY ACTIVITIES POTENTIALLY HAZARDOUS TO CIVIL TRAFFIC Guidance for the coordination of such activities is provided in ICAO Doc 9554 ‘Manual Concerning Safety Measures Relating to Military Activities Potentially Hazardous to Civil Aircraft Operations’ GM1 to the definition of ‘accuracy’ For measured positional data the accuracy is normally expressed in terms of a distance from a stated position within which there is a defined confidence of the true position falling. GM1 to the definition of ‘aerodrome flight information service (AFIS)' AFIS, being part of ATS, is provided in accordance with the applicable EU Regulations and should be distinguished from non-designated facilities, such as ‘Universal Communications (UNICOM)’ which comprise a frequency used by pilots to announce their intentions at an aerodrome where ATS are not provided. A ground station may exist at such a ‘UNICOM’ aerodrome but it does not provide a designated and certified or declared flight information service. GM1 to the definition of ‘ATC clearance’ For convenience, the term ‘air traffic control clearance’ is frequently abbreviated to ‘clearance’ when used in appropriate contexts. The abbreviated term ‘clearance’ may be prefixed by the words ‘taxi’, ‘take-off’, ‘departure’, ‘en- route’, ‘approach’ or ‘landing’ to indicate the particular portion of flight to which the air traffic control clearance relates. GM1 to the definition of ‘ADS-C’ The abbreviated term ‘ADS contract’ is commonly used to refer to ‘ADS event contract’, ‘ADS demand contract’, ‘ADS periodic contract’ or an emergency mode. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 53 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM1 to the definition of ‘ATS surveillance system’ A comparable ground-based system is one that has been demonstrated, by comparative assessment or other methodology, to have a level of safety and performance equal to or better than monopulse secondary surveillance radar (SSR). GM1 to the definition of ‘decision altitude’ Decision altitude (DA) is referenced to mean sea level, and decision height (DH) is referenced to the threshold elevation. The required visual reference is that section of the visual aids or of the approach area which should have been in view for sufficient time for the pilot to have made an assessment of the aircraft position and rate of change of position, in relation to the desired flight path. In Category III operations with a decision height, the required visual reference is that specified for the particular procedure and operation. GM1 to the definition of ‘expected approach time’ The actual time of leaving the holding fix will depend upon the approach clearance. GM1 to the definition of ‘obstacle clearance altitude’ Obstacle clearance altitude is referenced to mean sea level. GM1 to the definition of ‘obstacle clearance height’ Obstacle clearance height is referenced to the threshold elevation or in the case of non-precision approach procedures to the aerodrome elevation or the threshold elevation if that is more than 2 m (7 ft) below the aerodrome elevation. An obstacle clearance height for a circling approach procedure is referenced to the aerodrome elevation. GM1 to the definition of ‘procedure turn’ Procedure turns are designated ‘left’ or ‘right’ according to the direction of the initial turn. Procedure turns may be designated as being made either in level flight or while descending, according to the circumstances of each individual procedure. GM1 to the definition of ‘runway-holding position’ In radiotelephony phraseologies, the expression ‘holding point’ is used to designate the runway- holding position. GM1 to the definition of ‘significant point’ There are three categories of significant points: ground-based navigation aid, intersection and waypoint. In the context of this definition, intersection is a significant point expressed as radials, bearings and/or distances from ground-based navigation aids. GM1 to the definition of ‘touchdown’ ‘Touchdown’ as defined above is only a datum and is not necessarily the actual point at which the aircraft will touch the runway. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 54 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC1 ATS.OR.110 Coordination between aerodrome operators and ATS providers ESTABLISHMENT AND IDENTIFICATION OF STANDARD TAXI ROUTES (a) The ATS provider, in coordination with the aerodrome operator, should assess the necessity for establishing standard routes for taxiing aircraft on an aerodrome between runways, aprons and maintenance areas. (b) When established, such routes should be direct, simple and, where practicable, designed to avoid traffic conflicts. (c) Standard routes for taxiing aircraft should be identified by designators distinctively different from those of the runways and ATS routes. (Annex 11 — Sections 2.15.1 and 2.15.2) AMC2 ATS.OR.110 Coordination between aerodrome operators and ATS providers INFORMATION EXCHANGE ON THE AERODROME CONDITIONS AND OPERATIONAL STATUS OF AERODROME FACILITIES The ATS provider should establish arrangements with the aerodrome operator for the exchange of information regarding the aerodrome conditions, in particular the operational conditions of the movement area, including the existence of temporary hazards, and the operational status of any associated facilities at the aerodrome(s) with which they are concerned. AMC3 ATS.OR.110 Coordination between aerodrome operators and ATS providers APRON MANAGEMENT SERVICES The ATS provider should establish arrangements, including a coordination procedure, with the aerodrome operator and, when applicable, with the other organisation(s) providing apron management services. The coordination procedure between the provider(s) of apron management services and the ATS provider should contain at least the following: (a) the boundaries of the respective areas of responsibilities as described according to ADR.OPS.D.020 of Regulation (EU) No 139/2014; (b) the handover points between apron and manoeuvring area; (c) the holding areas; (d) the means of guidance for the aircraft taxiing; (e) the operational information to be exchanged between both parties; and (f) the push back operations, when interfering with the manoeuvring area. AMC4 ATS.OR.110 Coordination between aerodrome operators and ATS providers COORDINATION FOR LOW-VISIBILITY OPERATIONS The ATS provider should establish arrangements with the aerodrome operator and, where established, with the apron management services provider(s) for the relevant aspects and the definition of the respective responsibilities in conducting low-visibility operations, in addition to those established in ATS.TR.265(b). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 55 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC5 ATS.OR.110 Coordination between aerodrome operators and ATS providers RUNWAYS INSPECTIONS The ATS provider should coordinate with the aerodrome operator the conduct of routine and non- routine runways inspections. (PANS ATM — Section 7.4.1.7.2 (partially)) AMC6 ATS.OR.110 Coordination between aerodrome operators and ATS providers INFORMATION ON THE SAFE USE OF THE MANOEUVRING AREA When a not previously notified condition pertaining to the safe use by aircraft of the manoeuvring area is reported to or observed by the air traffic controllers or by AFIS officers, the ATS provider should inform the aerodrome operator, and operations on that part of the manoeuvring area should be terminated until otherwise advised by the aerodrome operator. (PANS ATM — Section 7.5.4) GM1 ATS.OR.110 Coordination between aerodrome operators and ATS providers COORDINATION FOR THE AERODROME MANUAL The ATS provider should establish close coordination with the aerodrome operator to participate in the development of the elements of the Aerodrome Manual pertaining to the services it provides. GM1 ATS.OR.125(a) Coordination between aeronautical information services and ATS providers PUBLICATION OF REDUCED RUNWAY SEPARATION MINIMA The ATS provider should arrange to publish all applicable procedures related to the application of reduced runway separation minima as in AMC9 ATS.TR.210(c)(2)(i) in the aeronautical information publication (AIP) and to include them also in the local ATC instructions. (PANS ATM — Section 7.11.2 (first sentence)) GM2 ATS.OR.125(a) Coordination between aeronautical information services and ATS providers PROMULGATION OF INFORMATION ON AFIS The ATS provider should arrange to report information regarding the availability of AFIS and related procedures for its inclusion in the relevant parts of the AIP in the same manner as in the case of aerodromes provided with ATC service, in accordance with Appendix I to Annex VI (Part AIS). The information includes but is not limited to the following: (a) identification of the aerodrome; (b) location and identification of the AFIS unit; (c) hours of operation of the AFIS unit; (d) lateral and vertical limits of the associated airspace, when defined; (e) language(s) used; (f) detailed description of the services provided, including alerting service and, if applicable, use of direction-finding; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 56 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (g) special procedures for application by pilots; and (h) any other pertinent information. (ICAO Circular 211-AN/128 — ‘Promulgation of information’, 36.) GM3 ATS.OR.125(a) Coordination between aeronautical information services and ATS providers PROMULGATION OF INFORMATION FOR UNICOM AERONAUTICAL STATIONS NOT PROVIDING ATS The arrangements established as outlined in GM2 to Article 3(1b) should ensure that information regarding the availability of the ‘UNICOM’ are included in the relevant parts of the AIP. The information should include the following: (a) identification of the aerodrome, where applicable; (b) location and identification of the aeronautical station, where applicable; (c) hours of operation of the aeronautical station, where applicable; (d) language(s) used; (e) detailed description of the facilitation provided and its limitations; (f) special procedures for application by pilots; and (g) any other pertinent information. GM1 ATS.OR.125(c) Coordination between aeronautical information services and ATS providers ORIGIN OF AERONAUTICAL INFORMATION Information to be reported to the AIS provider may originate also from other entities, such as the aerodrome operator, the apron management service provider, CNS service providers, etc. GM1 ATS.OR.125(d) Coordination between aeronautical information services and ATS providers Of particular importance are changes to aeronautical information that affect charts and/or computer- based navigation systems which qualify to be notified by the aeronautical information regulation and control (AIRAC) system, as stipulated in AIS.OR.505 and AIS.TR.505. (Annex 11 — Section 2.21.3 (first sentence)) GM1 ATS.OR.135 Contingency arrangements The various circumstances surrounding each ATS contingency situation preclude the establishment of exact detailed procedures to be followed. (PANS ATM — Section 15.6) GM2 ATS.OR.135 Contingency arrangements RADIO COMMUNICATION CONTINGENCIES IN AIR TRAFFIC CONTROL SERVICE (a) General ATC contingencies related to communications, i.e. circumstances preventing a controller from communicating with aircraft under control, may be caused by either a failure of ground radio TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 57 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments equipment, a failure of airborne equipment, or by the control frequency being inadvertently blocked by an aircraft or a ground transmitter, or any unauthorised use. The duration of such events may be for prolonged periods and appropriate action to ensure that the safety of aircraft is not affected should therefore be taken immediately. (b) Ground radio failure (1) In the event of complete failure of the ground radio equipment used for ATC, the controller should: (i) attempt to establish radio communications on the emergency frequency 121.500 MHz; (ii) without delay inform all adjacent control positions or ATC units, as applicable, of the failure; (iii) apprise such positions or units of the current traffic situation; (iv) request their assistance, in respect of aircraft which may establish communications with those positions or units, in establishing and maintaining separation between such aircraft; and (v) instruct adjacent control positions or ATC units to hold or re-route all controlled flights outside the area of responsibility of the position or ATC unit that has experienced the failure until such time that the provision of normal services can be resumed, unless able to continue to provide ATS by means of other available communication channels. (2) In order to reduce the impact of complete ground radio equipment failure on the safety of air traffic, the ATS provider should establish contingency procedures to be followed by control positions and ATC units in the event of such failures. Where agreed between affected ATS providers, such contingency procedures should provide for the delegation of control to an adjacent control position or ATC unit in order to permit a minimum level of services to be provided as soon as possible, following the ground radio failure and until normal operations can be resumed. (c) Blocked frequency In the event that the control frequency is inadvertently blocked by an aircraft transmitter, the following additional steps should be taken: (1) attempt to identify the aircraft concerned; (2) if the aircraft blocking the frequency is identified, attempts should be made to establish communication with that aircraft, e.g. on the emergency frequency 121.500 MHz, by SELCAL, through the aircraft operator’s company frequency if applicable, on any VHF frequency designated for air-to-air use by flight crews or any other communication means or, if the aircraft is on the ground, by direct contact; and TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 58 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (3) if communication is established with the aircraft concerned, the flight crew should be instructed to take immediate action to stop inadvertent transmissions on the affected control frequency. (d) Unauthorised use of ATC frequency Instances of false and deceptive transmissions on ATC frequencies which may impair the safety of aircraft can occasionally occur. In the event of such occurrences, the ATC unit concerned should: (1) correct any false or deceptive instructions or clearances which have been transmitted; (2) advise all aircraft on the affected frequency(ies) that false and deceptive instructions or clearances are being transmitted; (3) instruct all aircraft on the affected frequency(ies) to verify instructions and clearances before taking action to comply; (4) if practical, instruct aircraft to change to another frequency; and (5) if possible, advise all aircraft affected when the false and deceptive instructions or clearances are no longer being transmitted. (PANS ATM — Sections 8.8.6.1/15.6.1.1, 8.8.6.2/15.6.1.2.1, 15.6.1.2.2, 15.6.1.3 and 15.6.1.4) GM3 ATS.OR.135 Contingency arrangements CONTINGENCY PROCEDURES FOR ATS UNITS WHEN A VOLCANIC ASH CLOUD IS REPORTED OR FORECAST If a volcanic ash cloud is reported or forecast in the airspace for which the ATS unit is responsible, the following actions should be taken, as appropriate: (a) relay pertinent information immediately to flight crews whose aircraft could be affected to ensure that they are aware of the ash cloud’s current and forecast position and the flight levels affected; (b) accommodate requests for re-routing or level changes to the extent practicable; (c) suggest re-routing to avoid or exit areas of reported or forecast ash clouds when requested by the pilot or deemed necessary by the controller; and (d) when practicable, request a special air-report when the route of flight takes the aircraft into or near the forecast ash cloud and provide such special air-reports to the appropriate agencies. (PANS ATM — Section 15.8.1) GM4 ATS.OR.135 Contingency arrangements Guidance on contingency planning for air navigation services providers may be found in the ‘EUROCONTROL Guidelines for Contingency Planning of Air Navigation Services (including Service Continuity)’ Edition 2.0 of 06.04.2009, available at: https://www.eurocontrol.int/sites/default/files/article/content/documents/nm/safety/safety- guidelines-contingency-planning-ans-2009.pdf TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 59 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments and in its complementary document named ‘Reference Guide to EUROCONTROL Guidelines for Contingency Planning of Air Navigation Services (including Service Continuity)’ Edition 2.0 of 06.04.2009, available at: https://www.eurocontrol.int/sites/default/files/article/content/documents/nm/safety/reference- guide-contingency-planning-ans-2009.pdf AMC1 ATS.OR.145(a) Operation of ATC service PRESENTATION AND UPDATING OF FLIGHT PLAN AND CONTROL DATA AND OTHER RELEVANT INFORMATION FOR THE ATC PROVISION (a) The ATS provider should ensure that sufficient information and data are presented in such a manner as to enable the controller to have a complete representation of the current air traffic situation within the controller’s area of responsibility and, when relevant, movements on the manoeuvring area of aerodromes. (b) The presentation should be updated in accordance with the progress of aircraft, in order to facilitate the timely detection and resolution of conflicts as well as to facilitate and provide a record of coordination with adjacent ATS units and control sectors. (c) An appropriate representation of the airspace configuration, including significant points and information related to such points, should be provided. (d) Data to be presented should include relevant information from flight plans and position reports as well as clearance and coordination data. (e) The information display may be generated and updated automatically, or the data may be entered and updated by authorised personnel. (f) Data generated automatically should be presented to the controller in a timely manner. The presentation of information and data for individual flights should continue until such time as the data is no longer required for the purpose of providing control, including conflict detection and the coordination of flights, or until terminated by the controller. (g) All information and data as in point (a), including data related to individual aircraft, should be presented in a manner minimising the potential for misinterpretation or misunderstanding. (PANS ATM — Sections 4.13.2.1, 4.13.2.2, 4.13.3.2 (second sentence) and 4.13.3.5) GM1 ATS.OR.145(a) Operation of ATC service PRESENTATION AND UPDATING OF FLIGHT PLAN AND CONTROL DATA AND OTHER RELEVANT INFORMATION FOR THE ATC PROVISION Human Factors principles should be considered when establishing the provisions and procedures stipulated in ATS.TR.145(a). (PANS ATM — Sections 4.13.3.2 (first sentence) and 4.13.3.3) GM2 ATS.OR.145(a) Operation of ATC service PRESENTATION AND UPDATING OF FLIGHT PLAN AND CONTROL DATA AND OTHER RELEVANT INFORMATION FOR THE ATCPROVISION TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 60 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Other information required or desirable for the provision of ATS may be but are not limited to: (a) relevant meteorological information; (b) NOTAMs; (c) airspace-related information; (d) status of radio navigation services and visual aids; (e) aerodrome conditions and the operational status of associated facilities, where appropriate; (f) unmanned free balloons; and (g) others. GM3 ATS.OR.145(a) Operation of ATC service PRESENTATION AND UPDATING OF FLIGHT PLAN AND CONTROL DATA AND OTHER RELEVANT INFORMATION FOR THE ATC PROVISION (a) The required flight plan and control data may be presented through the use of paper flight progress strips or electronic flight progress strips, by other electronic presentation forms or by a combination of presentation methods. (b) The ATS provider should specify the procedures for annotating data and provisions specifying the types of data to be entered on flight progress strips, including the use of symbols. (PANS ATM — Sections 4.13.3.1 and 4.13.3.4 (third sentence)) GM1 ATS.OR.150(a) Transfer of responsibility for control GUIDANCE ON LETTERS OF AGREEMENT BETWEEN ATS UNITS Guidance on the drafting of operational Letters of Agreement between ATS units may be found in the EUROCONTROL ‘Common Format Letter of Agreement Between Air Traffic Services Units’ Edition 4.0 of 15.03.2012, available at: https://www.eurocontrol.int/sites/default/files/field_tabs/content/documents/nm/airspace/airspace- atmprocedures-common-format-loa-4.0.pdf GM1 ATS.OR.150(b) Transfer of responsibility for control TRANSFER OF COMMUNICATION (a) Except when separation minima based on ATS surveillance systems specified in AMC1 ATS.TR.210(c)(2) and AMC6 ATS.TR.220 are being applied, the transfer of air–ground communications of an aircraft from the transferring to the accepting ATC unit should be made 5 minutes before the time at which the aircraft is estimated to reach the common control area boundary unless otherwise agreed between the two ATC units concerned. (b) When separation minima based on ATS surveillance systems specified in AMC1 ATS.TR.210(c)(2) and AMC6 ATS.TR.220 are being applied at the time of transfer of control, the transfer of air– ground communications of an aircraft from the transferring to the accepting ATC unit should be made immediately after the accepting ATC unit has agreed to assume control. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 61 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (c) The accepting ATC unit should notify the transferring unit in the event that communication with the aircraft is not established as expected. (d) In cases where a portion of a control area is so situated that the time taken by aircraft to traverse it is of a limited duration, agreement should be reached to provide for direct transfer of communication between the units responsible for the adjacent control areas, provided that the intermediate unit is fully informed of such traffic. The intermediate unit should retain responsibility for coordination and for ensuring that separation is maintained between all traffic within its area of responsibility. (e) An aircraft may be permitted to communicate temporarily with a control unit other than the unit controlling the aircraft. (PANS ATM — Sections 10.1.2.4.1, 10.1.2.4.2, 10.1.2.4.3 (second sentence), 10.1.2.4.4 and 10.1.2.4.5) AMC1 ATS.OR.400(a) Aeronautical mobile service (air–ground communications) — General Direct pilot-controller communications should be established prior to the provision of ATS surveillance services unless special circumstances, such as emergencies, dictate otherwise. (PANS ATM — Section 8.3.2) (Section 8.3.2 has been transposed as AMC1 SERA.8035) GM1 ATS.OR.405 Very high frequency (VHF) emergency channel LISTENING WATCH OF VHF EMERGENCY CHANNEL Requirements for ATS units to maintain continuous guard on the emergency channel 121.500 MHz are specified in SERA.14080(b) of Commission Implementing Regulation (EU) No 923/2012. (Annex 11 — Note to Section 6.1.1.1) GM1 ATS.OR.405(a)(3) Very high frequency (VHF) emergency channel USE OF VHF EMERGENCY CHANNEL IN CASE OF HANDLING OF DISTRESS TRAFFIC The use of the frequency 121.500 MHz for the purpose outlined in point (a)(3) of ATS.OR.405 is to be avoided if it interferes in any way with the efficient handling of distress traffic. (Annex 10 — Volume V, Note 1 to Section 4.1.3.1.1) GM1 ATS.OR.405(b) Very high frequency (VHF) emergency channel VHF EMERGENCY CHANNEL Where two or more of the ATS units listed in point (b) of ATS.OR.405 are co-located, provision of 121.500 MHz at one would meet the requirement. (Annex 10 — Volume V, Note to Section 4.1.3.1.2) GM1 ATS.OR.410(a) Aeronautical mobile service (air–ground communications) — For flight information service Whenever practicable, air–ground communication facilities for flight information service should permit direct, rapid, continuous and static-free two-way communications. (Annex 11 — Recommendation in Section 6.1.2.2) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 62 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC1 ATS.OR.415 Aeronautical mobile service (air–ground communications) — For area control service Whenever practicable, air–ground communication facilities for area control service should permit direct, rapid, continuous and static-free two-way communications. (Annex 11 — Recommendation in Section 6.1.3.2) GM1 ATS.OR.415 Aeronautical mobile service (air–ground communications) — For area control service Where air–ground voice communication channels are used for area control service by air–ground communicators, suitable arrangements should be made to permit direct pilot–controller voice communications, as and when required. (Annex 11 — Recommendation in Sections 6.1.3.3) GM1 ATS.OR.430(a) Aeronautical fixed service (ground–ground communications) — General Indication by time of the speed with which the communication should be established is provided as a guide to communication services, particularly to determine the types of communication channels required, e.g. that ‘instantaneous’ is intended to refer to communications which effectively provide for immediate access between controllers; ‘15 seconds’ to accept switchboard operation and ‘5 minutes’ to mean methods involving retransmission. (Annex 11 — Note 1 to Section 6.2.1.1) GM1 ATS.OR.430(b) Aeronautical fixed service (ground–ground communications) — General FAILURE OF AUTOMATED COORDINATION In case of failure of the automated coordination, the controller should facilitate the required coordination using prescribed alternative methods, as established by the ATS provider in operation manuals. (PANS ATM — Section 10.1.6 (second sentence)) GM1 ATS.OR.435(a);(b) Aeronautical fixed service (ground-ground communications) — Communication within a flight information region SUPPLEMENTARY FACILITIES TO THOSE PRESCRIBED FOR COMMUNICATION The communication facilities in points (a) and (b) of ATS.OR.435 could be supplemented, as and where necessary, by facilities for other forms of visual or audio communications; for example, closed circuit television or separate information processing systems. (Annex 11 — Recommendation in Section 6.2.2.3.4) GM1 ATS.OR.435(c)(4) Aeronautical fixed service (ground–ground communications) — Communication within a flight information region FACILITY FOR DIRECT SPEECH The facility for direct speech does not necessarily refer to permanently dedicated point-to-point telephone lines. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 63 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM1 ATS.OR.440(d) Aeronautical fixed service (ground–ground communications) — Communication between flight information regions Special circumstances may be due to traffic density, types of aircraft operations and/or the manner in which the airspace is organised and may exist even if the control areas and/or control zones are not contiguous or have not (yet) been established. (Annex 11 — Note to Section 6.2.3.2) AMC1 ATS.OR.450(a) Communications for the control of vehicles other than aircraft on manoeuvring areas at controlled aerodromes SYSTEM OF VISUAL SIGNALS FOR COMMUNICATION BETWEEN AERODROME CONTROL TOWER AND VEHICLES ON THE MANOEUVRING AREA (a) When communications by a system of visual signals is deemed to be adequate, or in the case of radio communication failure, the signals given hereunder should have the meaning indicated therein: LIGHTS SIGNAL FROM AERODROME MEANING CONTROL Green flashes Permission to cross landing area or to move onto taxiway Steady red Stop Red flashes Move off the landing area or taxiway and watch out for aircraft White flashes Vacate manoeuvring area in accordance with local instructions (b) In emergency conditions or if the signals in point (a) are not observed, the signal given hereunder should be used for runways or taxiways equipped with a lighting system and should have the meaning indicated therein. LIGHT SIGNAL MEANING Flashing runway or taxiway lights Vacate the runway and observe the tower for light signal (PANS ATM — Sections 7.6.3.2.3.2 and 7.6.3.2.3.3) GM1 ATS.OR.450(a) Communications for the control of vehicles other than aircraft on manoeuvring areas at controlled aerodromes COMMUNICATIONS BETWEEN AERODROME CONTROL TOWER AND VEHICLES ON THE MANOEUVRING AREA At controlled aerodromes, all vehicles operating on the manoeuvring area should be capable of maintaining two-way radio communication with the aerodrome control tower, except when the vehicle is only occasionally used on the manoeuvring area and is: (a) accompanied by a vehicle with the required communications capability; or (b) employed in accordance with a pre-arranged plan established with the aerodrome control tower. (PANS ATM — Section 7.6.3.2.3.1) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 64 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM1 ATS.OR.505(a) Meteorological information for flight information centres and area control centres INFORMATION CONCERNING WEATHER DETERIORATION Certain changes in meteorological conditions are construed as deterioration in a weather element, although they are not ordinarily considered as such. An increase in temperature may, for example, adversely affect the operation of certain types of aircraft. (Annex 11 — Note to Section 7.1.2.1) GM1 ATS.OR.525 Information on the operational status of navigation services PROVISION OF INFORMATION WITH RESPECT TO RADIO AND VISUAL AND NON-VISUAL NAVIGATION AIDS Guidance material regarding the provision of information to ATS units with respect to visual and non- visual navigation aids is contained in Appendix A to Chapter 10, Part I of the ICAO Air Traffic Services Planning Manual (Doc 9426). (Annex 11 — Note to Section 7.3.2) AMC1 ATS.TR.105(b) Divisions of the ATS AIR TRAFFIC ADVISORY SERVICE IMPLEMENTATION (a) The air traffic advisory service within airspace class F may be provided with the objective of making information on collision hazards more effective than it would be in the mere provision of flight information service. (b) Class F airspace should only be implemented where the ATS are inadequate for the provision of ATC, and the limited advice on collision hazards otherwise provided by flight information service is not adequate. Where air traffic advisory service is implemented, this should be considered as a temporary measure only until such time as it can be replaced by ATC service or, in cases where the traffic situation changes such that advisory service is no longer required, replaced by flight information service. (PANS ATM — Sections 9.1.4.1.1 (first sentence) and 9.1.4.1.2) (Section 9.1.4.1.2 has been transposed as AMC1 SERA.6001(h)) AMC2 ATS.TR.105(b) Divisions of the ATS COORDINATION IN RESPECT OF THE PROVISION OF AIR TRAFFIC ADVISORY SERVICE ATS units providing air traffic advisory service should apply the coordination procedures in ATS.TR.230 and ATS.OR.150 with respect to such aircraft having elected to use this type of service. (PANS ATM — Section 10.3) GM1 ATS.TR.105(b) Divisions of the ATS AIR TRAFFIC ADVISORY SERVICE (a) The air traffic advisory service may be provided to aircraft conducting IFR flights in advisory airspace or on advisory routes (class F airspace), specified by the State concerned. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 65 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (b) Air traffic advisory service does not afford the degree of safety and cannot assume the same responsibilities as ATC service in respect of the avoidance of collisions, since information regarding the disposition of traffic in the area concerned available to the unit providing air traffic advisory service may be incomplete. (c) The efficiency of air traffic advisory service will depend largely on the procedures and practices in use. Its establishment in line with the organisation, procedures and equipment of area control service, taking into account the basic differences of the two services, will help to ensure a high degree of efficiency and promote uniformity in the various provisions of air traffic advisory service. For example, exchange of information by the units concerned on the progress of an aircraft from one advisory area into an adjacent control area or terminal control area, and vice versa, will help to relieve pilots from repeating details of their flight plans already filed; also, use of standard ATC phraseology, preceded by the verbs ‘suggest’ or ‘advise’, will facilitate the pilot’s understanding of air traffic advisory service intelligence. (d) ATS units providing air traffic advisory service: (1) advise the aircraft to depart at the time specified and to cruise at the levels indicated in the flight plan if it does not foresee any conflict with other known traffic; (2) suggest to aircraft a course of action by which a potential hazard may be avoided, giving priority to an aircraft already in advisory airspace over other aircraft desiring to enter such advisory airspace; and (3) pass to aircraft traffic information comprising the same information as that prescribed for area control service. (e) The criteria used as a basis for action under points (d)(2) and (d)(3) should be at least those laid down for aircraft operating in controlled airspace and should take into account the limitations inherent in the provision of air traffic advisory service, navigation facilities and air–ground communications prevailing in the region. (PANS ATM — Sections 9.1.4.1.1 (second sentence), 9.1.4.1.3 (first sentence) 9.1.4.3 (Note to Section), 9.1.4.3.1, and 9.1.4.3.2) (Sections 9.1.4.1.3 (first sentence) and 9.1.4.3.1 have been proposed for transposition with NPA 2015-14 as points (a) and (c) respectively of GM1 SERA.14090(b)) GM2 ATS.TR.105(b) Divisions of the ATS Flight information service includes flight information service provided for the en-route traffic in the FIR and AFIS provided to the aerodrome traffic at specified aerodromes. GM1 ATS.TR.110(b) Establishment of the units providing ATS AIR TRAFFIC SERVICES REPORTING OFFICE The reference to an air traffic services reporting office denotes the functions to be performed by such an office. When addressing the provision of ATS, States are to ensure that the functions of ARO are fully implemented by: (a) establishing physical offices; and/or (b) assigning the duties to any ATS unit; and/or TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 66 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (c) agreeing with one or more Contracting State(s) to provide a joint service; and/or (d) delegating the provision of the service to an external agency or external agencies. (EANPG 57 Final Report) GM1 ATS.TR.115 Identification of ATS units and airspaces IDENTIFICATION OF UNICOM AERONAUTICAL STATIONS AT AERODROMES Where a Member State determines that no requirement exists for the provision of ATS and a UNICOM aeronautical station is established as guided in GM2 to Article 3(1b): (a) aeronautical stations should normally be identified by the name of the aerodrome at which they are providing air–ground, or air–air communication, or by the name of a nearby town or city or geographic feature or area. (b) the name of the aeronautical station should be complemented by the suffix ‘UNICOM’. GM1 ATS.TR.135 Determination of the transition level DETERMINATION OF A COMMON TRANSITION LEVEL FOR TWO OR MORE AERODROMES Where a common transition altitude has been established for two or more aerodromes which are so closely located as to require coordinated procedures, the appropriate ATS units should establish a common transition level to be used at any given time in the vicinity of the aerodrome and, when relevant, in the TMA concerned. (PANS ATM — Section 4.10.2.2 (second sentence)) GM1 ATS.TR.140(b) Minimum cruising level for IFR flights The lowest usable flight level is that flight level which corresponds to, or is immediately above, the established minimum flight altitude. (PANS ATM — Note 1 to Section 4.10.3.2) GM1 ATS.TR.145(c) Provision of altimeter setting information The transition level may be included in the approach clearances or provided when requested by the pilot. (PANS ATM — Section 4.10.4.4) GM2 ATS.TR.145(c) Provision of altimeter setting information The provision of transition level may be accomplished by voice communications, ATIS broadcast or data link. (PANS ATM — Section 4.10.4.3, second sentence, has been proposed as GM1 SERA.8015(eb)(2) PROVISIONS FOR CLEARANCES AND INSTRUCTIONS — ALTIMETRY’ with NPA 2015-14) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 67 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM1 ATS.TR.150 Suspension of visual flight rules operations on and in the vicinity of an aerodrome All such suspensions of VFR operations should be accomplished through or notified to the aerodrome control tower. (PANS ATM — Section 7.13.2) AMC1 ATS.TR.155 Aeronautical ground lights PROCEDURES FOR THE OPERATION OF AERONAUTICAL GROUND LIGHTS (a) Except as provided in point (b), all aeronautical ground lights should be operated: (1) continuously during the hours of darkness or during the time the centre of the sun’s disc is more than 6 degrees below the horizon, whichever requires the longer period of operation, unless otherwise provided hereafter or otherwise required for the control of air traffic; (2) at any other time when their use, based on meteorological conditions, is considered desirable for the safety of air traffic. (b) Lights on and in the vicinity of aerodromes that are not intended for en-route navigation purposes may be turned off, subject to further provisions hereafter, if no likelihood of either regular or emergency operation exists, provided that they can be again brought into operation at least one hour before the expected arrival of an aircraft. (c) At aerodromes equipped with lights of variable intensity, a table of intensity settings, based on conditions of visibility and ambient light, should be provided for the guidance of ATS personnel in effecting adjustment of these lights to suit the prevailing conditions. When so requested by an aircraft, further adjustment of the intensity should be made whenever possible. (d) In addition to point (a), approach lighting should also be operated: (1) by day when requested by an approaching aircraft; (2) when the associated runway lighting is operated. (e) The lights of a visual approach slope indicator system should be operated during the hours of daylight as well as of darkness and irrespective of the visibility conditions when the associated runway is being used. (f) Runway lighting should not be operated if that runway is not in use for landing, take-off or taxiing purposes unless required for runway inspections or maintenance. (g) If runway lighting is not operated continuously, lighting following a take-off should be provided as specified below: (1) at aerodromes where ATC service is provided and where lights are centrally controlled, the lights of one runway should remain lighted after take-off as long as is considered necessary for the return of the aircraft due to an emergency occurring during or immediately after take-off; (2) at aerodromes without ATC service or without centrally controlled lights, the lights of one runway should remain lighted until such time as would normally be required to reactivate TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 68 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments the lights in the likelihood of the departing aircraft returning for an emergency landing, and in any case not less than 15 minutes after take-off. (h) Stopway lights should be operated whenever the associated runway lights are operated. (i) Where required to provide taxi guidance, taxiway lighting should be turned on in such order that a continuous indication of the taxi path is presented to taxiing aircraft. Taxiway lighting or any portion thereof may be turned off when no longer needed. (j) Stop bars should be switched on to indicate that all traffic shall stop, and switched off to indicate that traffic may proceed. (k) Obstacle lighting associated with the approach to or departure from a runway or channel, where the obstacle does not project through the inner horizontal surface, as described in the applicable aerodrome design specifications may be turned off and on simultaneously with the runway or channel lights. (l) Unserviceability lights should not be turned off as permitted under point (k) while the aerodrome is open. (m) ATS personnel should make use of automatic monitoring facilities, when provided, to ascertain whether the lighting is in good order and functioning according to selection. (n) In the absence of an automatic monitoring system or to supplement such a system, ATS personnel should visually observe such lighting as can be seen from the aerodrome control tower and use information from other sources such as visual inspections or reports from aircraft to maintain awareness of the operational status of the visual aids. (o) On receipt of information indicating a lighting fault, ATS personnel should take such action as is warranted to safeguard any affected aircraft or vehicles, and initiate action to have the fault rectified. (PANS ATM — Sections 7.15.2.1, 7.15.2.2, 7.15.2.3, 7.15.3.1, 7.15.3.2, 7.15.4.1, 7.15.4.2, 7.15.5, 7.15.6, 7.15.7, 7.15.8.1, 7.15.8.2, 7.15.9.1, 7.15.9.2 and 7.15.9.3) GM1 to AMC1 ATS.TR.155 Aeronautical ground lights OPERATION OF AERONAUTICAL GROUND LIGHTS (a) Approach lighting includes such lights as simple approach lighting systems, precision approach lighting systems, visual approach slope indicator systems, circling guidance lights, approach light beacons and runway alignment indicators. (b) Runway lighting includes such lights as edge, threshold, centre line, end, touchdown zone and wing bar lights. (c) Where obstacle lighting is operated simultaneously with runway lighting as provided in point (k) of AMC1 ATS.TR.155, particular care should be taken to ensure that it is not turned off until no longer required by the aircraft. (d) Taxiway lighting includes such lights as edge lights, centre line lights, stop bars and clearance bars. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 69 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (e) Stop bars are located across taxiways at the point where it is desired that traffic stop, and consist of lights, showing red, spaced across the taxiway. (f) Obstacle lighting includes such lights as obstacle and unserviceability lights and hazard beacons. (PANS ATM — Sections 7.15.3, 7.15.4, 7.15.4.2 (Note to Section), 7.15.6 (Note to Section), 7.15.7 (Note to Section), and 7.15.8 (Note to Section)) GM1 ATS.TR.160 ATS surveillance services USE OF INFORMATION DERIVED FROM ATS SURVEILLANCE SYSTEMS FOR ATC SERVICE PURPOSES Information derived from ATS surveillance systems, including safety-related alerts and warnings such as conflict alert and minimum safe altitude warning, should be used to the extent possible in the provision of ATC service in order to improve capacity and efficiency as well as to enhance safety. (PANS ATM — Section 8.4.1) AMC1 ATS.TR.160(a) ATS surveillance services FUNCTIONS OF THE ATS SURVEILLANCE SYSTEMS IN ATS (a) Functions in the area control service and approach control services The information provided by ATS surveillance systems and presented on a situation display may be used to perform one or more of the following functions in the provision of area control service or approach control service: (1) provide ATS surveillance services as necessary in order to improve airspace utilisation, reduce delays, provide for direct routings and more optimum flight profiles, as well as to enhance safety; (2) provide vectoring to departing aircraft for the purpose of facilitating an expeditious and efficient departure flow and expediting climb to cruising level; (3) provide vectoring to aircraft for the purpose of resolving potential conflicts; (4) provide vectoring to arriving aircraft for the purpose of establishing an expeditious and efficient approach sequence; (5) provide vectoring to assist pilots in their navigation, e.g. to or from a radio navigation aid, away from or around areas of adverse weather; (6) provide separation and maintain normal traffic flow when an aircraft experiences communication failure within the area of coverage; (7) maintain flight path monitoring of air traffic; (8) when applicable, maintain a watch on the progress of air traffic, in order to provide a procedural controller with: (i) improved position information regarding aircraft under control; (ii) supplementary information regarding other traffic; and TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 70 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (iii) information regarding any significant deviations by aircraft from the terms of their respective ATC clearances, including their cleared routes as well as levels, when appropriate. (b) Additional functions in the approach control service In addition to the functions listed in point (a), the position indications presented on a situation display may be used to perform one or more of the following functions in the provision of approach control service: (1) provide vectoring of arriving traffic on to pilot-interpreted final approach aids; (2) provide flight path monitoring of parallel ILS approaches and instruct aircraft to take appropriate action in the event of possible or actual penetrations of the no transgression zone (NTZ); (3) provide vectoring of arriving traffic to a point from which a visual approach can be completed; (4) provide vectoring of arriving traffic to a point from which a surveillance radar approach can be made; (5) provide flight path monitoring of other pilot-interpreted approaches; (6) in accordance with prescribed procedures, conduct surveillance radar approaches; and (7) provide separation between: (i) succeeding departing aircraft; (ii) succeeding arriving aircraft; and (iii) a departing aircraft and a succeeding arriving aircraft. (c) Functions in the aerodrome control service (1) When authorised by and subject to procedures and conditions prescribed by the competent authority, ATS surveillance systems may be used in the provision of aerodrome control service to perform the following functions: (i) flight path monitoring of aircraft on final approach; (ii) flight path monitoring of other aircraft in the vicinity of the aerodrome; (iii) establishing an appropriate longitudinal and/or distance-based separation based on ATS surveillance systems in between succeeding departing aircraft; (iv) maintaining separation between succeeding aircraft on the same final approach; and (v) providing navigation assistance to VFR flights (2) In prescribing conditions and procedures for the use of ATS surveillance systems in the provision of aerodrome control service, the ATS provider should ensure that the availability and use of an ATS surveillance system will not be detrimental to visual observation of aerodrome traffic. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 71 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (d) Functions in the flight information service The information presented on a situation display may be used to provide identified aircraft with: (1) information regarding any aircraft observed to be on a conflicting path with the identified aircraft and suggestions or advice regarding avoiding action; (2) information on the position of significant weather and, as practicable, advice to the aircraft on how best to circumnavigate any such areas of adverse weather. When doing so, attention is to be paid to the fact that under certain circumstances the most active area of adverse weather may not be displayed; (3) information to assist the aircraft in its navigation. (PANS ATM — Sections 8.7.1, 8.9.2, 8.10.1.1, 8.10.1.4, 8.11.1, and 8.6.9.2 (Note to Section), EANPG 56 Final Report – Section 4.4.6 and Appendix H) (PANS ATM Section 8.1.11 (introductory sentence and first bullet point) has been transposed as GM3 SERA.7002(a)(1)) GM1 ATS.TR.160(a) ATS surveillance services PROVISION OF ATS SURVEILLANCE SERVICES IN PRESENCE OF CONTROLLED BUT UNIDENTIFIED AIRCRAFT In the event that the controller has been notified of a controlled flight entering or about to enter the airspace within which a separation minimum based on ATS surveillance systems is applied, but has not identified the aircraft, the controller may, if so prescribed by the ATS provider, continue to provide an ATS surveillance service to identified aircraft, provided that: (a) reasonable assurance exists that the unidentified controlled flight will be identified using SSR and/or ADS-B and/or MLAT or the flight is being operated by an aircraft of a type which may be expected to give an adequate return on primary radar in the airspace within which the separation is applied; and (b) the separation is maintained between identified flights and any other observed ATS surveillance system position indications until either the unidentified controlled flight has been identified or procedural separation has been established. (PANS ATM — Section 8.7.2.8) AMC1 ATS.TR.160(b)(1) ATS surveillance services MEASUREMENT OF DISTANCES BETWEEN POSITION INDICATIONS The ATS provider should define in local instructions the criteria to measure distances between position indications. GM1 ATS.TR.160(b)(1) ATS surveillance services ATS SURVEILLANCE SYSTEM — PERFORMANCE CHECKS (a) The ATS personnel utilising ATS surveillance systems should adjust the situation display(s) and carry out adequate checks on the accuracy thereof, in accordance with the technical instructions prescribed by the ATS provider. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 72 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (b) The ATS personnel utilising ATS surveillance systems should be satisfied that the available functional capabilities of the ATS surveillance system as well as the information presented on the situation display(s) is adequate for the functions to be performed. (PANS ATM — Sections 8.6.1.1 and 8.6.1.2) AMC1 ATS.TR.160(b)(2) ATS surveillance services FACTORS DETERMINING THE NUMBER OF AIRCRAFT SIMULTANEOUSLY PROVIDED WITH ATS SURVEILLANCE SERVICES When determining the number of aircraft simultaneously provided with ATS surveillance services, the ATS provider should take into account, as a minimum: (a) the structural complexity of the control area or sector concerned; (b) the functions to be performed within the control area or sector concerned; (c) assessments of controller workloads, taking into account different aircraft capabilities, and sector capacity; and (d) the degree of technical reliability and availability of the primary and backup communications, navigation and surveillance systems, both in the aircraft and on the ground. (PANS ATM — Section 8.4.2) AMC1 ATS.TR.160(c) ATS surveillance services INTERRUPTION OR TERMINATION OF ATS SURVEILLANCE SERVICE The controller should immediately inform an aircraft which has previously been informed that it is provided with ATS surveillance service when, for any reason, the service is interrupted or terminated. (PANS ATM — Section 8.6.7.1) AMC1 ATS.TR.160(d)(1) ATS surveillance services METHODS OF IDENTIFICATION Identification of aircraft should be established by at least one of the following methods: (a) ADS-B identification procedures Where ADS-B is used for identification, aircraft may be identified by one or more of the following procedures: (1) direct recognition of the aircraft identification in an ADS-B label; (2) transfer of ADS-B identification; and (3) observation of compliance with an instruction to TRANSMIT ADS-B IDENT. (b) SSR and/or MLAT identification procedures (1) Where SSR and/or MLAT is used for identification, aircraft may be identified by one or more of the following procedures: TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 73 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (i) recognition of the aircraft identification in an SSR and/or MLAT label, in accordance with Article 4 of Commission Implementing Regulation (EU) No 1206/20112; (ii) recognition of an assigned discrete code, the setting of which has been verified, in an SSR and/or MLAT label, in accordance with Article 4 of Commission Implementing Regulation (EU) No 1206/2011; (iii) direct recognition of the aircraft identification of a Mode S-equipped aircraft in an SSR and/or MLAT label, in accordance with Article 4 of Commission Implementing Regulation (EU) No 1206/2011; (iv) by transfer of identification; (v) observation of compliance with an instruction to set a specific code; (vi) observation of compliance with an instruction to squawk IDENT. (2) When a discrete code has been assigned to an aircraft, a check should be made at the earliest opportunity to ensure that the code set by the pilot is identical to that assigned for the flight. Only after this check has been made, the discrete code should be used as a basis for identification. (c) PSR identification procedures (1) Where PSR is used for identification, aircraft may be identified by one or more of the following procedures: (i) by correlating a particular radar position indication with an aircraft reporting its position over, or as bearing and distance from, a point shown on the situation display, and by ascertaining that the track of the particular radar position is consistent with the aircraft path or reported heading; (ii) by correlating an observed radar position indication with an aircraft which is known to have just departed, provided that the identification is established within 2 km (1 NM) from the end of the runway used. Particular care should be taken to avoid confusion with aircraft holding over or overflying the aerodrome, or with aircraft departing from or making a missed approach over adjacent runways; (iii) by transfer of identification; (iv) when ATC service is provided, by ascertaining the aircraft heading, if circumstances require, and following a period of track observation: (A) instructing the pilot to execute one or more changes of heading of 30 degrees or more and correlating the movements of one particular radar position indication with the aircraft’s acknowledged execution of the instructions given; or 2 Commission Implementing Regulation (EU) No 1206/2011 of 22 November 2011 laying down requirements on aircraft identification for surveillance for the single European sky (OJ L 305, 23.11.2011, p. 23) (http://eur-lex.europa.eu/legal- content/EN/TXT/?qid=1467625880593&uri=CELEX:32011R1206) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 74 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (B) correlating the movements of a particular radar position indication with manoeuvres currently executed by an aircraft having so reported. (2) When using these methods, the controller/FIS officer/AFIS officer, as appropriate, should: (i) verify that the movements of not more than one radar position indication correspond with those of the aircraft; and (ii) ensure that the manoeuvre(s) will not carry the aircraft outside the coverage of the radar or the situation display. (d) Additional identification method When two or more position indications are observed in close proximity, or are observed to be making similar movements at the same time, or when doubt exists as to the identity of a position indication for any other reason, changes of heading should be prescribed or repeated as many times as necessary, or additional methods of identification should be employed, until all risk of error in identification is eliminated. (PANS ATM — Sections 8.6.2.1.3, 8.6.2.2, 8.6.2.3.1, 8.6.2.3.2, 8.6.2.4.1 and 8.6.2.5) GM1 ATS.TR.160(d)(1) ATS surveillance services METHODS OF IDENTIFICATION — SSR AND/OR MLAT IDENTIFICATION PROCEDURES When applying this method of identification, the controller/FIS officer/AFIS officer should consider that some aircraft equipped with first generation ADS-B avionics do not have the capability of squawking IDENT while the emergency and/or urgency mode is selected. (PANS ATM — Note 1 to Section 8.6.2.2) GM2 ATS.TR.160(d)(1) ATS surveillance services METHODS OF IDENTIFICATION — PSR IDENTIFICATION PROCEDURE (a) Caution is to be exercised when employing this method since a position reported in relation to a point may not coincide precisely with the radar position indication of the aircraft on the situation display. The ATS provider may, therefore, prescribe additional conditions for the application of this method, e.g.: (1) a level or levels above which this method may not be applied in respect of specified navigation aids; or (2) a distance from the radar site beyond which this method may not be applied. (b) The term ‘a point’ refers to a geographical point suitable for the purposes of identification. It is normally a reporting point defined by reference to a radio navigation aid or aids. (PANS ATM — Notes 1 and 2 to Section 8.6.2.4.1) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 75 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC2 ATS.TR.160(d)(1) ATS surveillance services METHODS OF IDENTIFICATION — USE OF ATS SURVEILLANCE SYSTEMS IN SURFACE MOVEMENT CONTROL Where an ATS surveillance system is used in surface movement control, the controller/AFIS officer may identify aircraft by one or more of the following procedures: (a) by correlating a particular position indication with: (1) an aircraft position visually observed by the controller/AFIS officer; (2) an aircraft position reported by the pilot; or (3) an identified position indication displayed on a situation display; (b) by transfer of identification when authorised by the competent authority; and (c) by automated identification procedures when authorised by the competent authority. (PANS ATM — Section 8.10.2.3) AMC3 ATS.TR.160(d)(1) ATS surveillance services METHOD OF IDENTIFICATION — TRANSFER OF IDENTIFICATION (a) Transfer of identification from one controller/FIS officer/AFIS officer to another should only be attempted when it is considered that the aircraft is within the accepting controller’s/FIS officer’s/AFIS officer’s surveillance coverage. (b) Transfer of identification should be effected by one of the following methods: (1) designation of the position indication by automated means, provided that only one position indication is thereby indicated and there is no possible doubt of correct identification; (2) notification of the aircraft’s discrete SSR code; (3) notification of the automated or system-to-system aircraft address; (4) notification that the aircraft is SSR Mode S-equipped with an aircraft identification feature when SSR Mode S coverage is available; (5) notification that the aircraft is ADS-B-equipped with an aircraft identification feature when compatible ADS-B coverage is available; (6) direct designation (pointing with the finger) of the position indication if the two situation displays are adjacent, or if a common ‘conference’ type of situation display is used; (7) designation of the position indication by reference to, or in terms of bearing and distance from, a geographical position or navigational facility accurately indicated on both situation displays, together with the track of the observed position indication if the route of the aircraft is not known to both controllers/FIS officers/AFIS officers; (8) where applicable, issuance of an instruction to the aircraft by the transferring controller/FIS officer/AFIS/AFIS officer to change SSR code and the observation of the change by the accepting controller/FIS officer/AFIS officer; or TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 76 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (9) issuance of an instruction to the aircraft by the transferring controller/FIS officer/AFIS officer to squawk/transmit IDENT and observation of this response by the accepting controller/FIS officer/AFIS officer. (PANS ATM — Sections 8.6.3.1 and 8.6.3.2) GM1 ATS.TR.160(d)(1) ATS surveillance services METHODS OF IDENTIFICATION — TRANSFER OF IDENTIFICATION (a) When applying the identification method described in point (b)(5) of AMC3 ATS.TR.160(d)(1), attention is to be paid to any errors which might occur due to parallax effects. (b) When applying the identification method described in point (b)(6) of AMC3 ATS.TR.160(d)(1), caution is to be exercised before transferring identification using this method, particularly if other position indications are observed on similar headings and in close proximity to the aircraft under control. Inherent radar deficiencies, such as inaccuracies in bearing and distance of the radar position indications displayed on individual situation displays and parallax errors, may cause the indicated position of an aircraft in relation to the known point to differ between the two situation displays. The ATS provider may therefore prescribe additional conditions for the application of this method, e.g.: (1) a maximum distance from the common reference point used by the two controllers; and (2) a maximum distance between the position indication as observed by the accepting controller and the one stated by the transferring controller. (c) The use of procedures in points (b)(7) and (b)(8) of AMC3 ATS.TR.160(d)(1) requires prior coordination between the controllers/FIS officers/AFIS officers, since the indications to be observed by the accepting controller/FIS officer/AFIS officer are of short duration. (PANS ATM — Section 8.6.3.2 (Note to paragraph (e), Note to paragraph (f), Note to paragraphs (g) and (h))) AMC1 ATS.TR.160(d)(2) ATS surveillance services POSITION INFORMATION (a) Aircraft provided with ATS surveillance service should be informed of its position in the following circumstances: (1) upon identification, except when the identification is established: (i) based on the pilot’s report of the aircraft position or within one nautical mile of the runway upon departure and the observed position on the situation display is consistent with the aircraft’s time of departure; or (ii) by use of ADS-B aircraft identification, Mode S aircraft identification or assigned discrete SSR codes and the location of the observed position indication is consistent with the current flight plan of the aircraft; or (iii) by transfer of identification; (2) when the pilot requests this information; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 77 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (3) when a pilot’s estimate differs significantly from the controller’s estimate based on the observed position; (4) when the pilot is instructed to resume own navigation after vectoring if the current instructions had diverted the aircraft from a previously assigned route; (5) immediately before termination of ATS surveillance service if the aircraft is observed to deviate from its intended route. (b) Position information should be passed on to aircraft in one of the following forms: (1) as a well-known geographical position; (2) magnetic track and distance to a significant point, an en-route navigation aid, or an approach aid; (3) direction (using points of the compass) and distance from a known position; (4) distance to touchdown if the aircraft is on final approach; or (5) distance and direction from the centre line of an ATS route. (c) Whenever practicable, position information should relate to positions or routes pertinent to the navigation of the aircraft concerned and shown on the situation display map. (PANS ATM — Sections 8.6.4.1, 8.6.4.2 and 8.6.4.3) AMC1 ATS.TR.160(d)(3) ATS surveillance services VECTORING — GENERAL (a) When vectoring an aircraft, an air traffic controller should comply with the following: (1) when an aircraft is given its initial vector diverting it from a previously assigned route, the pilot should be informed what the vector is to accomplish, and, when practicable, the limit of the vector should be specified (e.g. to ... position, for ... approach); (2) except when transfer of control is to be effected, aircraft should not be vectored closer than 4.6 km (2.5 NM) or, where the minimum permissible separation is greater than 9.3 km (5 NM), a distance equivalent to one-half of the prescribed separation minimum, from the limit of the airspace for which the controller is responsible, unless local arrangements have been made to ensure that separation will exist with aircraft operating in adjoining areas; (3) controlled flights should not be vectored into uncontrolled airspace except in the case of emergency or in order to circumnavigate adverse meteorological conditions (in which case the pilot should be so informed), or at the specific request of the pilot; and (4) when an aircraft has reported unreliable directional instruments, the pilot should be requested, prior to the issuance of manoeuvring instructions, to make all turns at an agreed rate and to carry out the instructions immediately upon receipt. (b) Special VFR flights should not be vectored unless special circumstances, such as emergencies, dictate otherwise. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 78 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (c) In terminating vectoring of an aircraft, the controller should instruct the pilot to resume own navigation, giving the pilot the aircraft’s position and appropriate instructions, as necessary, in the form prescribed in point (b)(2) of AMC1 ATS.TR.160(d)(2), if the current instructions had diverted the aircraft from a previously assigned route. (PANS ATM — Sections 8.6.5.1 (bullet point list as from bullet (b)), 8.6.5.5 and 8.10.1.2) GM1 to AMC1 ATS.TR.160(d)(3) ATS surveillance services VECTORING — GENERAL (a) Vectoring is achieved by issuing to the pilot specific headings which will enable the aircraft to maintain the desired track. (b) Whenever practicable, controllers should vector aircraft along tracks on which the pilot can monitor the aircraft position with reference to pilot-interpreted navigation aids; this will minimise the amount of navigational assistance required and alleviate the consequences resulting from an ATS surveillance system failure. (c) Controllers should exercise caution when vectoring VFR flights so as to ensure that the aircraft concerned does not inadvertently enter instrument meteorological conditions. (PANS ATM — Section 8.6.5.1 (First sentence and bullet point (a) of the list) and 8.10.1.3) AMC2 ATS.TR.160(d)(3) ATS surveillance services VECTORING FOR APPROACH CONTROL — GENERAL (a) Prior to, or upon commencement of, vectoring for approach, the controller should advise the pilot of the type of approach as well as the runway to be used. (b) The controller should advise the pilot of an aircraft being vectored for an instrument approach of its position at least once prior to commencement of final approach. (c) When giving distance information, the controller should specify the point or navigation aid to which the information refers. (d) Aircraft vectored for final approach should be given a heading or a series of headings calculated to close with the final approach track. The final vector should enable the aircraft to be established on the final approach track prior to intercepting the specified or nominal glide path of the approach procedure from below, and should provide an intercept angle with the final approach track of 45 degrees or less. (e) Whenever an aircraft is assigned a vector which will take it through the final approach track, it should be advised accordingly, stating the reason for the vector. (f) When an aircraft is vectored to a pilot-interpreted final approach aid, the transfer of communications to the aerodrome controller should be effected at such a point or time that clearance to land or alternative instructions can be issued to the aircraft in a timely manner. (PANS ATM — Sections 8.9.3.2, 8.9.3.3, 8.9.3.4, 8.9.3.6, 8.9.3.7 and 8.9.4.5) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 79 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM1 ATS.TR.160(d)(3) ATS surveillance services VECTORING — DEFINITION OF INITIAL AND INTERMEDIATE APPROACH PHASES The initial and intermediate approach phases of an approach executed under the direction of a controller comprise those parts of the approach from the time vectoring is initiated for the purpose of positioning the aircraft for a final approach until the aircraft is on final approach and: (a) established on the final approach path of a pilot-interpreted aid; or (b) reports that it is able to complete a visual approach; or (c) ready to commence a surveillance radar approach. (PANS ATM —Section 8.9.3.5) GM1 to AMC2 ATS.TR.160(d)(3) ATS surveillance services VECTORING TO PILOT-INTERPRETED FINAL APPROACH AIDS (a) An aircraft vectored to intercept a pilot-interpreted final approach aid should be instructed to report when established on the final approach track. Clearance for the approach should be issued prior to the time the aircraft reports are established unless circumstances preclude the issuance of the clearance at such time. Vectoring will normally terminate at the time the aircraft leaves the last assigned heading to intercept the final approach track. (b) When clearance for the approach is issued, aircraft is expected to maintain last assigned level until intercepting the specified or nominal glide path of the approach procedure. If the controller requires an aircraft to intercept the glide path at a level other than a level flight segment depicted on the instrument approach chart, the controller should instruct the pilot to maintain the particular level until established on the glide path. (c) The approach controller is normally responsible for maintaining separation based on ATS surveillance systems between succeeding aircraft on the same final approach, except that the responsibility may be transferred to the aerodrome controller in accordance with procedures prescribed by the ATS provider, and provided an ATS surveillance system is available to the aerodrome controller. (PANS ATM — Sections 8.9.4.1, 8.9.4.2 and 8.9.4.3) GM2 to AMC2 ATS.TR.160(d)(3) ATS surveillance services VECTORING FOR VISUAL APPROACH (a) The controller may initiate vectoring of an aircraft for visual approach provided the reported ceiling is above the minimum altitude applicable to vectoring and meteorological conditions are such that, with reasonable assurance, a visual approach and landing can be completed. (b) Clearance for visual approach should be issued only after the pilot has reported that contact with the terrain is achieved and can be maintained, at which time vectoring would normally be terminated. (PANS ATM — Section 8.9.5.1 and 8.9.5.2) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 80 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM3 to AMC2 ATS.TR.160(d)(3) ATS surveillance services PROCEDURES FOR RADAR APPROACHES (a) During the period that a controller is engaged in giving surveillance radar approaches, he or she should not be responsible for any duties other than those directly connected with such approaches. (b) Controllers conducting radar approaches should be in possession of information regarding the obstacle clearance altitudes/heights established for the types of approach to be conducted. (c) Prior to commencement of a radar approach, the controller should inform the aircraft of: (1) the runway to be used; (2) the applicable obstacle clearance altitude/height; (3) the angle of the nominal glide path and the approximate rate of descent to be maintained; (4) the procedure to be followed in the event of radio communication failure unless the procedure has been published in AIPs. (d) When a radar approach cannot be continued due to any circumstance, the aircraft should be immediately informed that a radar approach or continuation thereof is not possible. The approach should be continued if this is possible using non-radar facilities or if the pilot reports that the approach can be completed visually; otherwise an alternative clearance should be given. (e) Aircraft making a radar approach should be reminded, when on final approach, to check that the wheels are down and locked. (f) Unless otherwise prescribed by the ATS provider, the controller conducting the approach should notify the aerodrome controller or, when applicable, the procedural controller when an aircraft making a radar approach is approximately 15 km (8 NM) from touchdown. If landing clearance is not received at this time, a subsequent notification should be made at approximately 8 km (4 NM) from touchdown and landing clearance requested. (g) Clearance to land or any alternative clearance received from the aerodrome controller or, when applicable, the procedural controller should normally be passed on to the aircraft before it reaches a distance of 4 km (2 NM) from touchdown. (h) An aircraft making a radar approach should: (1) be directed to execute a missed approach in the following circumstances: (i) when the aircraft appears to be dangerously positioned on final approach; or (ii) for reasons involving traffic conflictions; or (iii) if no clearance to land has been received from the procedural controller by the time the aircraft reaches a distance of 4 km (2 NM) from touchdown or such other distance as has been agreed with the aerodrome control tower; or (iv) on instructions by the aerodrome controller; or (2) be advised to consider executing a missed approach in the following circumstances: TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 81 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (i) when the aircraft reaches a position from which it appears that a successful approach cannot be completed; or (ii) if the aircraft is not visible on the situation display for any significant interval during the last 4 km (2 NM) of the approach; or (iii) if the position or identification of the aircraft is in doubt during any portion of the final approach. In all such cases, the reason for the instruction or the advice should be given to the pilot. (i) Unless otherwise required by exceptional circumstances, radar instructions concerning a missed approach should be in accordance with the prescribed missed approach procedure and should include the level to which the aircraft is to climb and heading instructions to keep the aircraft within the missed approach area during the missed approach procedure. (PANS ATM — Sections 8.9.6.1.1, 8.9.6.1.2, 8.9.6.1.3, 8.9.6.1.4, 8.9.6.1.5, 8.9.6.1.6, 8.9.6.1.7, 8.9.6.1.8 and 8.9.6.1.9) GM4 to AMC2 ATS.TR.160(d)(3) ATS surveillance services FINAL APPROACH PROCEDURES — SURVEILLANCE RADAR APPROACH (a) A surveillance radar approach should only be performed with equipment suitably sited and a situation display specifically marked to provide information on position relative to the extended centre line of the runway to be used and distance from touchdown, and which is specifically approved for the purpose by the competent authority. (b) When conducting a surveillance radar approach, the controller should comply with the following: (1) at or before the commencement of the final approach, the aircraft should be informed of the point at which the surveillance radar approach will be terminated; (2) the aircraft should be informed when it is approaching the point at which it is computed that descent should begin, and just before reaching that point it should be informed of the obstacle clearance altitude/height and instructed to descend and check the applicable minima; (3) azimuth instructions should be given as follows: (i) the pilot should be informed at regular intervals of the aircraft’s position in relation to the extended centre line of the runway. Heading corrections should be given as necessary to bring the aircraft back on to the extended centre line; (ii) in the case of azimuth deviations, the pilot should not take corrective action unless specifically instructed to do so; (4) except as provided in point (c), distance from touchdown should normally be passed at every 2 km (each NM); (5) pre-computed levels through which the aircraft should be passing to maintain the glide path should also be transmitted at every 2 km (each NM) at the same time as the distance; (6) the surveillance radar approach should be terminated: TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 82 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (i) at a distance of 4 km (2 NM) from touchdown, except as provided in point (c); or (ii) before the aircraft enters an area of continuous radar clutter; or (iii) when the pilot reports that a visual approach can be effected; whichever is the earliest. (c) When, as determined by the competent authority, the accuracy of the radar equipment permits, surveillance radar approaches may be continued to the threshold of the runway, or to a prescribed point less than 4 km (2 NM) from touchdown, in which case: (1) distance and level information should be given at each km (each half NM); (2) transmission should not be interrupted for intervals of more than 5 seconds while the aircraft is within a distance of 8 km (4 NM) from touchdown; (3) the controller should not be responsible for any duties other than those directly connected with a particular approach. (d) Levels through which the aircraft should pass to maintain the required glide path, and the associated distances from touchdown, should be pre-computed and displayed in such a manner as to be readily available to the controller concerned. (PANS ATM — Sections 8.9.7.1.2, 8.9.7.1.3, 8.9.7.1.4 and 8.9.7.1.5) AMC1 ATS.TR.160(d)(4) ATS surveillance services NAVIGATION ASSISTANCE An identified aircraft observed to deviate significantly from its intended route or designated holding pattern should be advised accordingly. Appropriate action should also be taken if, in the opinion of the controller or, when applicable, the FIS officer/AFIS officer, such deviation is likely to affect the service being provided. (PANS ATM — Section 8.6.6.1) GM1 ATS.TR.160(d)(5) ATS surveillance services INFORMATION REGARDING ADVERSE WEATHER (a) Information that an aircraft appears likely to penetrate an area of adverse weather should be issued in sufficient time to permit the pilot to decide on an appropriate course of action, including that of requesting advice on how best to circumnavigate the adverse weather area, if so desired. (b) Depending on the capabilities of the ATS surveillance system, areas of adverse weather may not be presented on the situation display. An aircraft’s weather radar will normally provide better detection and definition of adverse weather than radar sensors in use by ATS. (c) In vectoring an aircraft for circumnavigating any area of adverse weather, the controller should ascertain that the aircraft can be returned to its intended or assigned flight path within the coverage of the ATS surveillance system and, if this does not appear possible, inform the pilot of the circumstances. (PANS ATM — Sections 8.6.9.1, 8.6.9.1 (Note to Section) and 8.6.9.2) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 83 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC1 ATS.TR.160(d)(6) ATS surveillance services ATS SURVEILLANCE SERVICES — PROCEDURES FOR TRANSFER OF CONTROL (a) Where an ATS surveillance service is being provided, transfer of control should be effected, whenever practicable, so as to enable the uninterrupted provision of the ATS surveillance service. (b) Where SSR and/or ADS-B and/or MLAT is used and the display of position indications with associated labels is provided for, transfer of control of aircraft between adjacent control positions or between adjacent ATC units may be effected without prior coordination, provided that: (1) updated flight plan information on the aircraft about to be transferred, including the discrete assigned SSR code or, with respect to Mode S and ADS-B, the aircraft identification, is provided to the accepting controller prior to transfer; (2) the ATS surveillance system coverage provided to the accepting controller is such that the aircraft concerned is presented on the situation display before the transfer is effected and is identified on, but preferably before, receipt of the initial call; (3) when the controllers are not physically adjacent, two-way direct speech facilities, which permit communications to be established instantaneously, are available between them at all times; (4) the transfer point or points and all other conditions of application, such as direction of flight, specified levels, transfer of communication points, and especially an agreed minimum separation between aircraft, including that applicable to succeeding aircraft on the same route, about to be transferred as observed on the situation display, have been made the subject of specific instructions (for intra-unit transfer) or of a specific letter of agreement between two adjacent ATC units; (5) the instructions or letter of agreement specify explicitly that the application of this type of transfer of control may be terminated at any time by the accepting controller, normally with an agreed advance notice; (6) the accepting controller is informed of any level, speed or vectoring instructions given to the aircraft prior to its transfer and which modify its anticipated flight progress at the point of transfer. (c) The minimum agreed separation between aircraft about to be transferred (see point (b)(4)) and the advance notice (see point (b)(5)) should be determined taking into account all relevant technical, operational and other circumstances. If circumstances arise in which these agreed conditions can no longer be satisfied, controllers should revert to the procedure in point (d) until the situation is resolved. (d) Where primary radar is being used, and where another type of ATS surveillance system is employed but the provisions in point (b) are not applied, the transfer of control of aircraft between adjacent control positions or between two adjacent ATS units may be effected, provided that: TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 84 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (1) identification has been transferred to or has been established directly by the accepting controller; (2) when the controllers are not physically adjacent, two-way direct-speech facilities between them are at all times available which permit communications to be established instantaneously; (3) separation from other controlled flights conforms to the minima authorised for use during transfer of control between the sectors or units concerned; (4) the accepting controller is informed of any level, speed or vectoring instructions applicable to the aircraft at the point of transfer; (5) radio communication with the aircraft is retained by the transferring controller until the accepting controller has agreed to assume responsibility for providing the ATS surveillance service to the aircraft. Thereafter, the aircraft should be instructed to change over to the appropriate channel and from that point the responsibility is of the accepting controller. (PANS ATM — Sections 8.7.4.1, 8.7.4.2, 8.7.4.3 and 8.7.4.4) GM1 to AMC1 ATS.TR.160(d)(6) ATS surveillance services ATS SURVEILLANCE SERVICES — PROCEDURES FOR TRANSFER OF CONTROL Transfer of control based on the procedures specified in AMC1 ATS.TR.160(d)(6) may be carried out without systematic use of the bidirectional speech facilities available between the adjacent units concerned, provided that: (a) the detailed conditions applicable for the transfer are the subject of a bilateral agreement; and (b) the minimum distance between successive aircraft during the period of transfer is agreed as one of the following values: (1) 19 km (10 NM) when SSR information is used in accordance with the provisions of AMC1 ATS.TR.160(d)(6), provided that an overlapping radar coverage of at least 56 km (30 NM) between units involved exists; or (2) 9.3 km (5 NM) when the conditions of point (b)(1) apply and both units involved possess electronic aids for immediate recognition of release and acceptance of aircraft under radar transfer. (Doc 7030 — Section 6.2.5.1) GM1 ATS.TR.160(d)(6) ATS surveillance services PROCEDURES FOR TRANSFER OF CONTROL IN ATS SURVEILLANCE SERVICES Guidance on procedures for transfer of control in the provision of ATS surveillance services may be found in the EUROCONTROL document titled ‘Guidelines for the Application of European Coordination and Transfer Procedures’ Edition 1.0 of 25.10.2012. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 85 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC1 ATS.TR.160(d)(7) ATS surveillance services PROCEDURES FOR ATC SERVICE IN CASE OF ATS SURVEILLANCE SYSTEM FAILURE In the event of complete failure of the ATS surveillance system, where air–ground communications remain, the controller should plot the positions of all aircraft already identified, take the necessary action to establish procedural separation between the aircraft and, if necessary, limit the number of aircraft permitted to enter the area. (PANS ATM — Section 8.8.4.1) GM1 ATS.TR.160(d)(7) ATS surveillance services SEPARATION APPLICATION IN CASE OF ATS SURVEILLANCE SYSTEM FAILURE As an emergency measure, in the event of complete failure of the ATS surveillance system, where air– ground communications remain, the use of flight levels spaced by half the applicable vertical separation minimum may be resorted to temporarily if standard procedural separation cannot be provided immediately. (PANS ATM — Section 8.8.4.2) GM2 ATS.TR.160(d)(7) ATS surveillance services ATS SURVEILLANCE SYSTEM FAILURE — DATA DEGRADATION In order to reduce the impact of a degradation of aircraft position source data, for example, a receiver autonomous integrity monitoring (RAIM) outage for GNSS, the ATS provider should establish contingency procedures to be followed by control positions and ATC units in the event of data degradation. (PANS ATM — Section 8.8.5) GM1 ATS.TR.160(d)(9) ATS surveillance services DISPLAY OF ATS SURVEILLANCE-BASED SAFETY-RELATED ALERTS AND WARNINGS ATS surveillance systems should provide for the display of safety-related alerts and warnings, including conflict alert, conflict prediction, minimum safe altitude warning and unintentionally duplicated SSR codes. (Annex 11 — Section 3.9, PANS ATM — Section 8.1.4) GM2 ATS.TR.160(d)(9) ATS surveillance services SHORT-TERM CONFLICT ALERT (STCA) PROCEDURES The generation of STCAs is a function based on surveillance data, integrated into an ATC system. The objective of the STCA function is to assist the controller in preventing collision between aircraft by generating, in a timely manner, an alert of a potential or actual infringement of separation minima. Procedures and related instructions concerning use of the STCA function should specify, inter alia: (a) the types of flight which are eligible for generation of alerts; (b) the sectors or areas of airspace within which the STCA function is implemented; (c) the method of displaying the STCA to the controller; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 86 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (d) in general terms, the parameters for generation of alerts as well as alert warning time; (e) the volumes of airspace within which STCA can be selectively inhibited and the conditions under which this will be permitted; (f) conditions under which specific alerts may be inhibited for individual flights; and (g) procedures applicable in respect of volume of airspace or flights for which STCA or specific alerts have been inhibited. (PANS ATM — Sections 15.7.2 (Note 1 to Section) and 15.7.2.1) GM3 ATS.TR.160(d)(9) ATS surveillance services MINIMUM SAFE ALTITUDE WARNING (MSAW) PROCEDURES (a) The generation of MSAWs is a function of an ATC radar data-processing system. The objective of the MSAW function is to assist in the prevention of controlled flight into terrain accidents by generating, in a timely manner, a warning of the possible infringement of a minimum safe altitude. Procedures and related instructions concerning use of the MSAW function should specify, inter alia: (b) the types of flight which are eligible for generation of MSAW; (c) the sectors or areas of airspace for which MSAW minimum safe altitudes have been defined and within which the MSAW function is implemented; (d) the values of the defined MSAW minimum safe altitudes; (e) the method of displaying the MSAW to the controller; (f) the parameters for generation of MSAW as well as warning time; and (g) conditions under which the MSAW function may be inhibited for individual aircraft tracks as well as procedures applicable in respect of flights for which MSAW has been inhibited. (PANS ATM — Sections 15.7.4 (Note 1 to Section) and 15.7.4.1) AMC1 ATS.TR.160(e) ATS surveillance services INFORMATION REGARDING TRAFFIC ON CONFLICTING PATH (a) Information regarding traffic on a conflicting path should be given, whenever practicable, in the following form: (1) relative bearing of the conflicting traffic in terms of the 12-hour clock; (2) distance from the conflicting traffic in kilometres (nautical miles); (3) direction in which the conflicting traffic appears to be proceeding; (4) level and type of aircraft or, if unknown, relative speed of the conflicting traffic, e.g. slow or fast. (b) Pressure-altitude-derived level information, even when unverified, should be used in the provision of collision hazard information because such information, particularly if available from an otherwise unknown aircraft (e.g. a VFR flight) and given to the pilot of a known aircraft, could TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 87 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments facilitate the location of a collision hazard. Erroneous level information should not be used in providing collision hazard information. (c) When the pressure-altitude-derived level information has been verified, the information should be passed to pilots in a clear and unambiguous manner. When, subsequent to the verification, it has been ascertained that the pressure-altitude-derived level information is erroneous, such value should not be used in providing traffic information. In such case, the level information provided by the pilot should be used. If the level information has not been verified, the accuracy of the information should be considered uncertain and the pilot should be informed accordingly. (PANS ATM — Sections 8.8.2.3, 8.8.2.4 and 8.8.2.4.1) (PANS ATM — Sections 8.8.2.3, 8.8.2.4, and 8.8.2.4.1 have been transposed as AMC1 SERA.7002(a)(1) in NPA 2015-14) GM1 ATS.TR.160(e) ATS surveillance services INFORMATION REGARDING TRAFFIC ON CONFLICTING PATH When an identified IFR flight operating outside controlled airspace is observed to be on a conflicting path with another aircraft, the pilot should: (a) be informed as to the need for collision avoidance action to be initiated, and if so requested by the pilot or if, in the opinion of the air traffic controller, the situation warrants, a course of avoiding action should be suggested; and (b) be notified when the conflict no longer exists. (PANS ATM — Section 8.8.2.2) (PANS ATM —Section 8.8.2.2 has been transposed as GM2 SERA.7002(a)(1) in NPA 2015-14) AMC1 ATS.TR.205 Provision of ATC service The ATS provider should: (a) determine the area of responsibility for individual control sectors within an ATC unit, when applicable; (b) where there is more than one ATC working position within a unit or sector, define the duties and responsibilities of the individual working positions. (PANS ATM — Section 4.3.1) GM1 ATS.TR.205 Provision of ATC service Approach control service may be provided by a unit co-located with an ACC, or by a control sector within an ACC. (PANS ATM — Note to Section 4.1.2) AMC1 ATS.TR.205(c) Provision of ATC service FUNCTIONS OF AERODROME CONTROL TOWERS (a) Aerodrome control towers should issue information, instructions and clearances to aircraft under their control to achieve a safe, orderly and expeditious flow of air traffic on and in the vicinity of an aerodrome with the object of preventing collision(s) between: TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 88 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (1) aircraft flying within the designated area of responsibility of the control tower, including the aerodrome traffic circuits; (2) aircraft operating on the manoeuvring area; (3) aircraft landing and taking off; (4) aircraft and vehicles operating on the manoeuvring area; (5) aircraft on the manoeuvring area and obstructions on that area. (b) Aerodrome controllers should maintain a continuous watch on all flight operations on and in the vicinity of an aerodrome as well as on vehicles and personnel on the manoeuvring area. (c) Watch should be maintained by visual observation, augmented in low visibility conditions by an ATS surveillance system, when available. (d) If there are other aerodromes within a control zone, traffic at all aerodromes within such a zone should be coordinated so that traffic circuits do not conflict. (PANS ATM — Sections 7.1.1.1 and 7.1.1.2) GM1 ATS.TR.205(c) Provision of ATC service POSITIONS AT THE AERODROME CONTROL TOWER (a) The functions of an aerodrome control tower may be performed by different control or working positions, such as: (1) aerodrome controller, normally responsible for operations on the runway and aircraft flying within the area of responsibility of the aerodrome control tower; (2) ground controller, normally responsible for traffic on the manoeuvring area with the exception of runways; (3) clearance delivery position, normally responsible for delivery of start-up and ATC clearances to departing IFR flights. (b) Where parallel or near-parallel runways are used for simultaneous operations, individual aerodrome controllers should be responsible for operations on each of the runways. (PANS ATM — Sections 7.1.1.3 and 7.1.1.4) AMC1 ATS.TR.210(a)(3) Operation of ATC service HORIZONTAL SPEED CONTROL INSTRUCTIONS — GENERAL (a) In order to facilitate a safe and orderly flow of traffic, the ATC unit may, subject to conditions specified by the competent authority, instruct aircraft to adjust speed in a specified manner. (b) Flight crews should be given adequate notice of planned speed control. (c) Speed control instructions should remain in effect unless explicitly cancelled or amended by the controller. (d) Speed control should not be applied to aircraft entering or established in a holding pattern. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 89 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (e) Speed adjustments should, as far as practicable, be limited to those necessary to establish and/or maintain a desired separation minimum or spacing. Instructions involving frequent changes of speed, including alternate speed increases and decreases, should be avoided. (f) When the flight crew informs the ATC unit concerned that they are unable to comply with a speed instruction, the controller should apply an alternative method to achieve the desired spacing between the aircraft concerned. (g) At levels at or above 7 600 m (FL 250), speed adjustments should be expressed in multiples of 0.01 Mach; at levels below 7 600 m (FL 250), speed adjustments should be expressed in multiples of 20 km/h (10 kt) based on indicated airspeed (IAS). (h) The controller should advise the flight crew when a speed control restriction is no longer required. (PANS ATM — Sections 4.6.1.1, 4.6.1.2, 4.6.1.3, 4.6.1.4, 4.6.1.5, 4.6.1.6 and 4.6.1.7) GM1 to AMC1 ATS.TR.210(a)(3) Operation of ATC service HORIZONTAL SPEED CONTROL INSTRUCTIONS — GENERAL (a) In order to establish a desired spacing between two or more successive aircraft, the controller should first either reduce the speed of the last aircraft, or increase the speed of the lead aircraft, then adjust the speed(s) of the other aircraft in order. (b) In order to maintain a desired spacing using speed control techniques, specific speeds need to be assigned to all the aircraft concerned. (c) The true airspeed (TAS) of an aircraft will decrease during descent when maintaining a constant IAS. When two descending aircraft maintain the same IAS, and the leading aircraft is at the lower level, the TAS of the leading aircraft will be lower than that of the following aircraft. The distance between the two aircraft will thus be reduced unless a sufficient speed differential is applied. For the purpose of calculating a desired speed differential between two succeeding aircraft, 11 km/h (6 kt) IAS per 300 m (1 000 ft) height difference may be used as a general rule. At levels below 2 450 m (FL 80), the difference between IAS and TAS is negligible for speed control purposes. (d) Time and distance required to achieve a desired spacing will increase with higher levels, higher speeds, and when the aircraft is in a clean configuration. (PANS ATM — Sections 4.6.2.1, 4.6.2.2 and Notes 1 and 2 to Section 4.6.2.2) GM2 to AMC1 ATS.TR.210(a)(3) Operation of ATC service HORIZONTAL SPEED CONTROL INSTRUCTIONS — AIRCRAFT PERFORMANCE AT HIGH LEVEL When an aircraft is heavily loaded and at a high level, its ability to change speed may, in cases, be very limited. (PANS ATM — Note 2 to Section 4.6.1.6) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 90 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC2 ATS.TR.210(a)(3) Operation of ATC service HORIZONTAL SPEED CONTROL INSTRUCTIONS — DESCENDING AND ARRIVING AIRCRAFT (a) The controller should only apply speed reductions to less than 460 km/h (250 kt) IAS for turbojet aircraft during initial descent from cruising level with the concurrence of the flight crew. (b) The controller should use only minor speed adjustments not exceeding plus/minus 40 km/h (20 kt) IAS for aircraft on intermediate and final approach. (c) The controller should not apply speed control to aircraft after passing a point 7 km (4 NM) from the threshold on final approach. (PANS ATM — Sections 4.6.3.3, 4.6.3.6 and 4.6.3.7) GM1 to AMC2 ATS.TR.210(a)(3) Operation of ATC service HORIZONTAL SPEED CONTROL INSTRUCTIONS — DESCENDING AND ARRIVING AIRCRAFT (a) The controller should, when practicable, authorise an aircraft to absorb a period of notified terminal delay by cruising at a reduced speed for the latter portion of its flight. (b) The controller may instruct an aircraft to maintain its ‘maximum speed’, ‘minimum clean speed’, ‘minimum speed’, a specified speed or a speed equal or less/more than a specified speed. ‘Minimum clean speed’ signifies the minimum speed at which an aircraft can be flown in a clean configuration, i.e. without deployment of lift-augmentation devices, speed brakes or landing gear. (c) The controller should avoid issuing instructions for an aircraft to simultaneously maintain a high rate of descent and reduce its speed, as such manoeuvres are normally not compatible. Any significant speed reduction during descent may require the aircraft to temporarily level off to reduce speed before continuing descent. (d) The controller should permit arriving aircraft to operate in a clean configuration for as long as possible. Below 4 550 m (FL 150), speed reductions for turbojet aircraft to not less than 410 km/h (220 kt) IAS, which will normally be very close to the minimum speed of turbojet aircraft in a clean configuration, may be used. (PANS ATM — Sections 4.6.3.1, 4.6.3.2, 4.6.3.2 (Note to Section), 4.6.3.4 and 4.6.3.5) AMC3 ATS.TR.210(a)(3) Operation of ATC service VERTICAL SPEED CONTROL INSTRUCTIONS — GENERAL (a) In order to facilitate a safe and orderly flow of traffic, the controller may instruct aircraft to adjust rate of climb or rate of descent. The controller may apply vertical speed control between two or more climbing aircraft or two or more descending aircraft in order to establish or maintain a specific vertical separation minimum. (b) The controller should, as far as practicable, limit vertical speed adjustments to those necessary to establish and/or maintain a desired separation minimum, and should avoid instructions involving frequent changes of climb/descent rates. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 91 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (c) When the flight crew informs the ATC unit concerned that they are unable to comply with a specified rate of climb or descent, the controller should apply an alternative method to achieve an appropriate separation minimum between aircraft, without delay. (d) The controller should advise aircraft when a rate of climb/descent restriction is no longer required. (PANS ATM — Sections 4.7.1.1, 4.7.1.2, 4.7.1.3 and 4.7.1.4) GM1 to AMC3 ATS.TR.210(a)(3) Operation of ATC service VERTICAL SPEED CONTROL INSTRUCTIONS — GENERAL (a) The controller may instruct an aircraft to expedite climb or descent as appropriate to or through a specified level, or to reduce its rate of climb or rate of descent. (b) The controller may instruct climbing aircraft to maintain a specified rate of climb, a rate of climb equal to or greater than a specified value or a rate of climb equal to or less than a specified value. (c) The controller may instruct descending aircraft to maintain a specified rate of descent, a rate of descent equal to or greater than a specified value or a rate of descent equal to or less than a specified value. (d) In applying vertical speed control, the controller should ascertain to which level(s) climbing aircraft can sustain a specified rate of climb or, in the case of descending aircraft, the specified rate of descent which can be sustained. (e) Controllers should be aware of aircraft performance characteristics and limitations in relation to a simultaneous application of horizontal and vertical speed limitations. (PANS ATM — Sections 4.7.2.1, 4.7.2.2, 4.7.2.3, and 4.7.2.4 and the associated Note) AMC4 ATS.TR.210(a)(3) Operation of ATC service HOLDING CLEARANCE AND INSTRUCTIONS When delay is expected, the ACC should clear aircraft to the holding fix, and: (a) include holding instructions; and (b) communicate in such clearances an expected approach time or onward clearance time, as applicable. (PANS ATM — Section 6.5.5.2) GM1 to AMC4 ATS.TR.210(a)(3) Operation of ATC service HOLDING CLEARANCE AND INSTRUCTIONS (a) In the event of extended delays, aircraft should be advised of the anticipated delay as early as possible and, when practicable, be instructed or given the option to reduce speed en-route in order to absorb delay. (b) Holding and holding pattern entry should be accomplished in accordance with procedures published in AIPs. If entry and holding procedures have not been published or if the procedures TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 92 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments are not known to a flight crew, the appropriate ATC unit should specify the designator of the location or aid to be used, the inbound track, radial or bearing, direction of turn in the holding pattern as well as the time of the outbound leg or the distances between which to hold. (c) ATS units should normally hold aircraft a designated holding fix. (d) For the purpose of maintaining a safe and orderly flow of traffic, an aircraft may be instructed to orbit at its present or at any other position, provided the required obstacle clearance is ensured. (PANS ATM — Sections 6.5.5.1, 6.5.5.5, 6.5.5.6 (first sentence) and 6.5.5.10) AMC5 ATS.TR.210(a)(3) Operation of ATC service APPROACH SEQUENCE (a) The approach sequence should be established in a manner which will facilitate arrival of the maximum number of aircraft with the least average delay. Priority in the approach sequence should be given to: (1) an aircraft which anticipates being compelled to land because of factors affecting the safe operation of the aircraft (engine failure, shortage of fuel, etc.); (2) hospital aircraft or aircraft carrying any sick or seriously injured person requiring urgent medical attention; (3) aircraft engaged in search and rescue operations; and (4) other aircraft as may be determined by the competent authority. (b) Succeeding aircraft should be cleared for approach: (1) when the preceding aircraft has reported that it is able to complete its approach without encountering instrument meteorological conditions; or (2) when the preceding aircraft is in communication with and sighted by the aerodrome control tower, and reasonable assurance exists that a normal landing can be accomplished; or (3) when timed approaches are used, the preceding aircraft has passed the defined point inbound, and reasonable assurance exists that a normal landing can be accomplished; or (4) when the use of an ATS surveillance system confirms that the required longitudinal spacing between succeeding aircraft has been established. (PANS ATM — Sections 6.5.6.1.1 and 6.5.6.1.2) GM1 to AMC5 ATS.TR.210(a)(3) Operation of ATC service APPROACH SEQUENCE — SEQUENCING AND SPACING OF INSTRUMENT APPROACHES (a) Timed approach procedures (1) The following procedure should be utilised as necessary to expedite the approaches of a number of arriving aircraft: TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 93 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (i) a suitable point on the approach path, which shall be capable of being accurately determined by the pilot, should be specified, to serve as a checkpoint in timing successive approaches; (ii) aircraft should be given a time at which to pass the specified point inbound, which time should be determined with the aim of achieving the desired interval between successive landings on the runway while respecting the applicable separation minima at all times, including the period of runway occupancy. (2) The time at which aircraft shall pass the specified point should be determined by the unit providing approach control service and notified to the aircraft sufficiently in advance to permit the pilot to arrange the flight path accordingly. (3) Each aircraft in the approach sequence should be cleared to pass the specified point inbound at the previously notified time, or any revision thereof, after the preceding aircraft has reported passing the point inbound. (b) Interval between successive approaches In determining the time interval or longitudinal distance to be applied between successive approaching aircraft, the relative speeds between succeeding aircraft, the distance from the specified point to the runway, the need to apply wake turbulence separation, runway occupancy times, the prevailing meteorological conditions as well as any condition which may affect runway occupancy times should be considered. When an ATS surveillance system is used to establish an approach sequence, the minimum distance to be established between succeeding aircraft should be specified in local instructions. Local instructions should additionally specify the circumstances under which any increased longitudinal distance between approaches may be required as well as the minima to be used under such circumstances. (PANS ATM — Sections 6.5.6.2.1.1, 6.5.6.2.1.2, 6.5.6.2.1.3 and 6.5.6.2.2) AMC6 ATS.TR.210(a)(3) Operation of ATC service EXPECTED APPROACH TIME (a) The appropriate ATS unit should determine an expected approach time for an arriving aircraft that will be subjected to a delay of 10 minutes or more. (b) The expected approach time should be transmitted to the aircraft as soon as practicable and preferably not later than at the commencement of its initial descent from cruising level. (c) A revised expected approach time should be transmitted to the aircraft without delay whenever it differs from that previously transmitted by 5 minutes or more, or such lesser period of time as has been established by the competent authority or agreed between the ATS units concerned. (d) An expected approach time should be transmitted to the aircraft by the most expeditious means whenever it is anticipated that the aircraft will be required to hold for 30 minutes or more. (e) The holding fix to which an expected approach time relates should be identified together with the expected approach time whenever circumstances are such that this would not otherwise be evident to the pilot. (PANS ATM — Sections 6.5.7.1, 6.5.7.2 and 6.5.7.3) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 94 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC7 ATS.TR.210(a)(3) Operation of ATC service ONWARD CLEARANCE TIME In the event that an aircraft is held en-route or at a location or aid other than the initial approach fix, the appropriate ATS unit should, as soon as practicable, give the aircraft concerned an expected onward clearance time from the holding fix. The aircraft should also be advised if further holding at a subsequent holding fix is expected. (PANS ATM — Section 6.5.8) AMC8 ATS.TR.210(a)(3) Operation of ATC service INSTRUMENT APPROACH (a) The approach control unit should specify the instrument approach procedure to be used by arriving aircraft. When a flight crew requests an alternative instrument approach procedure, the approach control unit should clear it accordingly, if circumstances permit. (b) If a pilot reports or it is clearly apparent to the ATC unit that the pilot is not familiar with an instrument approach procedure, the initial approach level, the point (in minutes from the appropriate reporting point) at which base turn or procedure turn will be started, the level at which the procedure turn is to be carried out and the final approach track should be specified, except that only the last-mentioned need be specified if the aircraft is to be cleared for a straight-in approach. The frequency(ies) of the navigation aid(s) to be used as well as the missed approach procedure should also be specified when deemed necessary. (PANS ATM — Sections 6.5.4.1 and 6.5.4.2) GM1 to AMC8 ATS.TR.210(a)(3) Operation of ATC service INSTRUMENT APPROACH If visual reference to terrain is established before completion of the approach procedure, the entire procedure should nevertheless be executed unless the aircraft requests and is cleared for a visual approach. (PANS ATM — Section 6.5.4.3) AMC9 ATS.TR.210(a)(3) Operation of ATC service VISUAL APPROACH (a) Subject to the conditions described in point (b), clearance for an IFR flight to execute a visual approach may be requested by a flight crew or initiated by the controller. In the latter case, the concurrence of the flight crew should be required. (b) An IFR flight should only be cleared to execute a visual approach, provided the pilot can maintain visual reference to the terrain and: (1) the reported ceiling is at or above the level of the beginning of the initial approach segment for the aircraft so cleared; or (2) the pilot reports at the level of the beginning of the initial approach segment or at any time during the instrument approach procedure that the meteorological conditions are such that with reasonable assurance a visual approach and landing can be completed. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 95 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (c) Except between aircraft performing successive visual approaches as described in point (d), separation should be provided between an aircraft cleared to execute a visual approach and other arriving and departing aircraft. (d) For successive visual approaches, separation should be maintained by the controller until the pilot of a succeeding aircraft reports having the preceding aircraft in sight. The aircraft should then be instructed to follow and maintain own separation from the preceding aircraft. (e) In case of aircraft performing successive visual approaches and instructed to maintain own separation as in point (d), and the distance between such aircraft is less than the appropriate wake turbulence minimum, the controller should issue a caution of possible wake turbulence. (PANS ATM — Sections 6.5.3.1, 6.5.3.3, 6.5.3.4 and 6.5.3.5 (first, second and third sentence)) GM1 to AMC9 ATS.TR.210(a)(3) Operation of ATC service VISUAL APPROACH Controllers should exercise caution in initiating a visual approach when there is a reason to believe that the flight crew concerned is not familiar with the aerodrome and its surrounding terrain. Controllers should also take into consideration the prevailing traffic and meteorological conditions when initiating visual approaches. (PANS ATM — Section 6.5.3.2) AMC10 ATS.TR.210(a)(3) Operation of ATC service INFORMATION FOR ARRIVING AIRCRAFT (a) As early as practicable after an aircraft has established communication with the unit providing approach control service, the following elements of information, in the order listed, should be transmitted to the aircraft, with the exception of such elements which are known to have been already received by the aircraft: (1) type of approach and runway-in-use; (2) meteorological information, as follows: (i) surface wind direction and speed, including significant variations; (ii) visibility and, when applicable, runway visual range (RVR); (iii) present weather; (iv) cloud below 1 500 m (5 000 ft) or below the highest minimum sector altitude, whichever is greater; cumulonimbus; if the sky is obscured, vertical visibility when available; (v) air temperature; (vi) dew point temperature, inclusion determined on the basis of a regional air navigation agreement; (vii) altimeter setting(s); TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 96 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (viii) any available information on significant meteorological phenomena in the approach area; and (ix) trend-type landing forecast, when available. (3) current runway surface conditions, in case of precipitants or other temporary hazards; (4) changes in the operational status of visual and non-visual aids essential for approach and landing. (b) At the commencement of final approach, the following information should be transmitted to aircraft: (1) significant changes in the mean surface wind direction and speed; (2) the latest information, if any, on wind shear and/or turbulence in the final approach area; (3) the current visibility representative of the direction of approach and landing or, when provided, the current runway visual range value(s) and the trend. (c) During final approach, the following information should be transmitted without delay: (1) the sudden occurrence of hazards (e.g. unauthorised traffic on the runway); (2) significant variations in the current surface wind, expressed in terms of minimum and maximum values; (3) significant changes in runway surface conditions; (4) changes in the operational status of required visual or non-visual aids; and (5) changes in observed RVR value(s), in accordance with the reported scale in use, or changes in the visibility representative of the direction of approach and landing. (PANS ATM — Sections 6.6.1, 6.6.4 and 6.6.5) GM1 to AMC10 ATS.TR.210(a)(3) Operation of ATC service INFORMATION FOR ARRIVING AIRCRAFT Significant variations are specified in MET.TR.205(a)(3). However, if the controller possesses wind information in the form of components, the significant changes are: (a) Mean headwind component: 19 km/h (10 kt); (b) Mean tailwind component: 4 km/h (2 kt); and (c) Mean crosswind component: 9 km/h (5 kt). (PANS ATM — Note to Section 6.6.4) AMC11 ATS.TR.210(a)(3) Operation of ATC service START UP TIME PROCEDURES (a) When so requested by the pilot prior to engine start, the aerodrome control tower should give an expected take-off time, unless engine start-up time procedures are employed. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 97 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (b) The aerodrome control tower should implement start-up time procedures where necessary to avoid congestion and excessive delays on the manoeuvring area or when necessary to comply with applicable ATFM regulations. Start-up time procedures should be contained in local instructions, and should specify the criteria and conditions for determining when and how start- up times should be calculated and issued to departing flights. (c) A start-up clearance should only be withheld under circumstances or conditions specified by the competent authority. (d) If a start-up clearance is withheld, the aerodrome control tower should advise the flight crew of the reason. (PANS ATM — Sections 7.4.1.1.1, 7.4.1.1.2, 7.4.1.1.6 and 7.4.1.1.7) AMC12 ATS.TR.210(a)(3) Operation of ATC service INFORMATION TO AIRCRAFT BY AERODROME CONTROL TOWERS — AERODROME AND METEOROLOGICAL INFORMATION (a) Prior to taxiing for take-off, the aerodrome control tower should advise aircraft of the following elements of information, in the order listed, with the exception of such elements which are known to have been already received by the aircraft: (1) the runway to be used; (2) the surface wind direction and speed, including significant variations therefrom; (3) the QNH altimeter setting and, either on a regular basis in accordance with local arrangements or if so requested by the aircraft, the QFE altimeter setting; (4) the air temperature for the runway to be used, in the case of turbine-engined aircraft; (5) the visibility representative of the direction of take-off and initial climb, if less than 10 km, or, when applicable, the RVR value(s) for the runway to be used; (6) the correct time. (b) Prior to take-off, the aerodrome control tower should advise aircraft of: (1) any significant changes in the surface wind direction and speed, the air temperature, and the visibility or RVR value(s) given in accordance with point (a); (2) significant meteorological conditions in the take-off and climb-out area, except when it is known that the information has already been received by the aircraft. (c) Prior to entering the traffic circuit or commencing its approach to land, the relevant ATC unit should provide aircraft with the following elements of information, in the order listed, with the exception of such elements which are known to have been already received by the aircraft: (1) the runway to be used; (2) the surface wind direction and speed, including significant variations therefrom; (3) the QNH altimeter setting and, either on a regular basis in accordance with local arrangements or if so requested by the aircraft, the QFE altimeter setting. (PANS ATM — Sections 7.4.1.2.1, 7.4.1.2.2 and 7.4.1.2.3) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 98 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM1 to AMC12 ATS.TR.210(a)(3) Operation of ATC service SIGNIFICANT METEOROLOGICAL CONDITIONS IN THE TAKE-OFF AND CLIMB-OUT AREA Significant meteorological conditions include the occurrence or expected occurrence of cumulonimbus or thunderstorm, moderate or severe turbulence, wind shear, hail, moderate or severe icing, severe squall line, freezing precipitation, severe mountain waves, sandstorm, dust storm, blowing snow, tornado or waterspout in the take-off and climb-out area. (PANS ATM — Note to Section 7.4.1.2.2) AMC13 ATS.TR.210(a)(3) Operation of ATC service TAXI CLEARANCE (a) Prior to issuing a taxi clearance, the controller should determine where the aircraft concerned is parked. Taxi clearances should contain concise instructions and adequate information so as to assist the flight crew to follow the correct taxi routes, to avoid collision with other aircraft or objects and to minimise the potential for the aircraft inadvertently entering an active runway. (b) When a taxi clearance contains a taxi limit beyond a runway, it should contain an explicit clearance to cross or an instruction to hold short of that runway. (PANS ATM — Sections 7.6.3.1.1.1 and 7.6.3.1.1.2) GM1 to AMC13 ATS.TR.210(a)(3) Operation of ATC service TAXI CLEARANCE Where standard taxi routes have not been published, the controller should, whenever possible, describe a taxi route, for example, by use of taxiway and runway designators or alternative identifiers. Other relevant information, such as an aircraft to follow or give way to, should also be provided to a taxiing aircraft. (PANS ATM — Section 7.6.3.1.1.4) GM2 to AMC13 ATS.TR.210(a)(3) Operation of ATC service HELICOPTER TAXI OPERATIONS (a) The provisions in points (b) to (f) may be considered and applied when a wheeled helicopter or vertical take-off and landing (VTOL) aircraft taxi on the surface. (b) Ground taxiing uses less fuel than air-taxiing and minimises air turbulence. However, under certain conditions, such as rough, soft or uneven terrain, it may become necessary to air-taxi for safety considerations. Helicopters with articulating rotors (usually designs with three or more main rotor blades) are subject to ‘ground resonance’ and may, on rare occasions, suddenly lift off the ground to avoid severe damage or destruction. (c) When it is requested or necessary for a helicopter to proceed at a slow speed above the surface, normally below 37 km/h (20 kt) and in ground effect, air-taxiing may be authorised. (d) Instructions which require small aircraft or helicopters to taxi in close proximity to taxiing helicopters should be avoided and consideration should be given to the effect of turbulence from taxiing helicopters on arriving and departing light aircraft. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 99 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (e) A frequency change should not be issued to single-pilot helicopters hovering or air-taxiing. Whenever possible, control instructions from the next ATS unit should be relayed as necessary until the pilot is able to change frequency. (f) Most light helicopters are flown by one pilot and require the constant use of both hands and feet to maintain control during low-altitude/low-level flight. Although flight control friction devices assist the pilot, changing frequency near the ground could result in inadvertent ground contact and consequent loss of control. (PANS ATM — Sections 7.6.3.1.4.1, 7.6.3.1.4.1 (Note to Section), 7.6.3.1.4.2, 7.6.3.1.4.3, 7.6.3.1.4.4, and 7.6.3.1.4.4 (Note to Section)) AMC14 ATS.TR.210(a)(3) Operation of ATC service TAXIING ON A RUNWAY IN USE (a) For the purpose of expediting air traffic, aircraft may be permitted to taxi on the runway-in-use, provided no delay or risk to other aircraft will result. Where control of taxiing aircraft is provided by a ground controller and the control of runway operations by an aerodrome controller, the use of a runway by taxiing aircraft should be coordinated with and approved by the aerodrome controller. Communication with the aircraft concerned should be transferred from the ground controller to the aerodrome controller prior to the aircraft entering the runway. (b) If the aerodrome control tower is unable to determine, either visually or via an ATS surveillance system, that a vacating or crossing aircraft has cleared the runway, the aircraft should be requested to report when it has vacated the runway. The report should be made when the entire aircraft is beyond the relevant runway-holding position. (PANS ATM — Sections 7.6.3.1.2.1 and 7.6.3.1.2.2) AMC15 ATS.TR.210(a)(3) Operation of ATC service USE OF RUNWAY-HOLDING POSITIONS (a) The controller should not hold aircraft closer to a runway-in-use than at a runway-holding position, except as in cases specified in point (b). (b) Aircraft should not be permitted to line up and hold on the approach end of a runway-in-use whenever another aircraft is effecting a landing, until the landing aircraft has passed the point of intended holding (See Figure 1). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 100 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 1 — Method of holding aircraft (PANS ATM — Sections 7.6.3.1.3.1 and 7.6.3.1.3.2) GM1 to AMC15 ATS.TR.210(a)(3) Operation of ATC service RUNWAY HOLDING POSITIONS The locations of runway holding positions in relation to runways are specified in CS ADR-DSN.D.335 ‘Holding bays, runway-holding positions, intermediate holding positions, and road-holding positions’ and CS ADR-DSN.D.340 ‘Location of holding bays, runway-holding positions, intermediate holding positions, and road-holding positions’ of EASA ED Decision 2014/013/R ‘Certification Specifications and Guidance Material For Aerodromes Design’, as amended. AMC16 ATS.TR.210(a)(3) Operation of ATC service RUNWAY INCURSION OR OBSTRUCTED RUNWAY In the event that the aerodrome controller, after a take-off clearance or a landing clearance has been issued, becomes aware of a runway incursion or the imminent occurrence thereof, or the existence of any obstruction on or in close proximity to the runway likely to impair the safety of an aircraft taking off or landing, he or she should take appropriate action as follows: (a) cancel the take-off clearance for a departing aircraft; (b) instruct a landing aircraft to execute a go-around or missed approach; (c) in all cases inform the aircraft of the runway incursion or obstruction and its location in relation to the runway. (PANS ATM — Section 7.4.1.4.1) GM1 to AMC16 ATS.TR.210(a)(3) Operation of ATC service RUNWAY INCURSION OR OBSTRUCTED RUNWAY Animals and flocks of birds may constitute an obstruction with regard to runway operations. In addition, an aborted take-off or a go-around executed after touchdown may expose the aeroplane to the risk of overrunning the runway. Moreover, a low altitude missed approach may expose the aeroplane to the risk of a tail strike. Pilots may therefore have to exercise their judgement in TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 101 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments accordance with SERA.2015 in Commission Implementing Regulation (EU) No 923/2012, concerning the authority of the pilot-in-command of an aircraft. (PANS ATM — Note to Section 7.4.1.4.1) GM2 to AMC16 ATS.TR.210(a)(3) Operation of ATC service CANCELLING TAKE-OFF CLEARANCE FOR DEPARTING AIRCRAFT (a) If take-off clearance has to be cancelled before the take-off run has commenced, the pilot should be instructed to hold position and to acknowledge the instruction. (b) In certain circumstances, the aerodrome controller may consider that it is necessary to cancel take-off clearance after the aircraft has commenced the take-off run. In this event, the pilot should be instructed to stop immediately and to acknowledge the instruction. (c) The cancellation of a take-off clearance after an aircraft has commenced its take-off run should only occur when the aircraft will be in serious and imminent danger should it continue. Controllers should be aware of the potential for an aircraft to overrun the end of the runway if the take-off is abandoned at a late stage; this is particularly so with large aircraft or those operating close to their performance limit, such as at maximum take-off mass, in high ambient temperatures or when the runway braking action may be adversely affected. Because of this risk, even if a take-off clearance is cancelled, the commander of the aircraft may consider it safer to continue the take-off than to attempt to stop the aircraft. (d) Controllers should also be aware of the possibility that an aircraft that abandons its take-off may suffer overheated brakes or another abnormal situation and should be prepared to declare the appropriate category of emergency or to provide other suitable assistance. (UK CAP 493 — Section 2, Chapter 1, Paragraph 16) AMC17 ATS.TR.210(a)(3) Operation of ATC service AERODROME CONTROL — TAKE-OFF CLEARANCE (a) The aerodrome control tower may issue a take-off clearance to an aircraft when there is reasonable assurance that the separation for departing aircraft as in AMC7 ATS.TR.210(c)(2)(i), or the separation prescribed in accordance with AMC9 ATS.TR.210(c)(2)(i) for reduced runway separation minima between aircraft using the same runway, will exist when the aircraft commences take-off. (b) When an ATC clearance is required prior to take-off, the aerodrome control tower should not issue the take-off clearance until the ATC clearance has been transmitted to and acknowledged by the aircraft concerned. The ATC clearance should be forwarded to the aerodrome control tower with the least possible delay after receipt of a request made by the tower or prior to such request if practicable. (c) Subject to point (b), the take-off clearance should be issued when the aircraft is ready for take- off and at or approaching the departure runway, and the traffic situation permits. To reduce the potential for misunderstanding, the take-off clearance should include the designator of the departure runway. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 102 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (d) In the interest of expediting traffic, a clearance for immediate take-off may be issued to an aircraft before it enters the runway. (PANS ATM — Sections 7.9.3.1, 7.9.3.2, 7.9.3.4 and 7.9.3.5 (first sentence)) AMC18 ATS.TR.210(a)(3) Operation of ATC service AERODROME CONTROL — CLEARANCE TO LAND The aerodrome control tower may clear an aircraft to land when there is reasonable assurance that the separation of landing aircraft and preceding landing and departing aircraft using the same runway established in AMC8 ATS.TR.210(d)(2)(i), or the separation prescribed in accordance with AMC9 ATS.TR.210(c)(2)(i) for reduced runway separation minima between aircraft using the same runway, will exist when the aircraft crosses the runway threshold, provided that a clearance to land is not be issued until a preceding landing aircraft has crossed the runway threshold. To reduce the potential for misunderstanding, the landing clearance should include the designator of the landing runway. (PANS ATM — Section 7.10.2) GM1 ATS.TR.210(a)(3) Operation of ATC service AERODROME CONTROL — CLEARANCES IN THE TRAFFIC CIRCUIT (a) The clearance to enter the traffic circuit should be issued to an aircraft whenever it is desired that the aircraft approach the landing area in accordance with current traffic circuits but traffic conditions do not yet allow a landing clearance to be issued. Depending on the circumstances and traffic conditions, an aircraft may be cleared to join at any position in the traffic circuit. (b) A controller may, inter alia, clear an aircraft to enter the traffic circuit by instructing the aircraft to continue in an upwind direction, parallel to the runway before crossing the runway axis to join the downwind leg. (c) An arriving aircraft executing an instrument approach should normally be cleared to land straight in unless visual manoeuvring to the landing runway is required. (PANS ATM — Sections 7.7.2.1 and 7.7.2.2, EANPG/56 WP 18 of 12/11/14) GM2 ATS.TR.210(a)(3) Operation of ATC service AERODROME CONTROL — INSTRUCTIONS FOR TURNING ON TO CIRCUIT LEGS When so instructed by the controller, pilots should obtain approval prior to turning on to any of the aerodrome traffic circuit legs. When extending an aerodrome traffic circuit leg, pilots should report to ATC as soon as there is a risk that the visual contact with the runway cannot be maintained. (EANPG/56 — WP18 of 12/11/14) GM3 ATS.TR.210(a)(3) Operation of ATC service AERODROME CONTROL — INSTRUCTIONS FOR LANDING AND ROLL OUT MANOEUVRES (a) When necessary or desirable in order to expedite traffic, the aerodrome control tower may request a landing aircraft to: (1) hold short of an intersecting runway after landing; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 103 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (2) land beyond the touchdown zone of the runway; (3) vacate the runway at a specified exit taxiway; (4) expedite vacating the runway. (b) In requesting a landing aircraft to perform a specific landing and/or roll-out manoeuvre, the type of aircraft, runway length, location of exit taxiways, reported braking action on runway and taxiway, and prevailing meteorological conditions should be considered. A HEAVY aircraft should not be requested to land beyond the touchdown zone of a runway. (c) When necessary or desirable, e.g. due to low visibility conditions, a landing or a taxiing aircraft may be instructed to report when a runway has been vacated. The report should be made when the entire aircraft is beyond the relevant runway-holding position. (PANS ATM — Sections 7.10.3.1, 7.10.3.2 and 7.10.3.4) GM4 ATS.TR.210(a)(3) Operation of ATC service FORMULATION OF INSTRUCTIONS AND INFORMATION TO AIRCRAFT ON THE GROUND As the view from the flight deck of an aircraft is normally restricted, the controller should ensure that instructions and information which require the flight crew to employ visual detection, recognition and observation are phrased in a clear, concise and complete manner. (PANS ATM — Section 7.6.1) GM5 ATS.TR.210(a)(3) Operation of ATC service INFORMATION ON JET BLAST AND PROPELLER SLIPSTREAM (a) In issuing clearances or instructions, air traffic controllers should take into account the hazards caused by jet blast and propeller slipstream to taxiing aircraft, to aircraft taking off or landing, particularly when intersecting runways are being used, and to vehicles and personnel operating on the aerodrome. (b) Jet blast and propeller slipstream can produce localised wind velocities of sufficient strength to cause damage to other aircraft, vehicles and personnel operating within the affected area. (PANS ATM — Section 7.4.1.6.2 and Note to Section 7.4.1.6.2) GM6 ATS.TR.210(a)(3) Operation of ATC service DESIGNATED POSITIONS OF AIRCRAFT IN THE AERODROME TRAFFIC AND TAXI CIRCUIT IN RELATION TO AERODROME CONTROL TOWER CLEARANCES The following positions of aircraft in the traffic and taxi circuits, as showed in Figure 2, are the positions where aircraft normally receive aerodrome control tower clearances. Aircraft should be watched closely as they approach these positions so that proper clearances may be issued without delay. Where practicable, all clearances should be issued without waiting for aircraft to initiate the call. — Position 1. Aircraft initiates call to taxi for departing flight. Runway-in-use information and taxi clearances given. — Position 2. If there is conflicting traffic, the departing aircraft will be held at this position. Engine run-up will, when required, normally be performed here. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 104 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments — Position 3. Take-off clearance is issued here if not practicable at position 2. — Position 4. Clearance to land is issued here as practicable. — Position 5. Clearance to taxi to apron is issued here. — Position 6. Parking information issued here if necessary. Figure 2 (PANS ATM — Section 7.6.2) AMC19 ATS.TR.210(a)(3) Operation of ATC service AERODROME CONTROL — PRIORITY FOR LANDING In the provision of aerodrome control service, priority for landing should be given to: (a) an aircraft which anticipates being compelled to land because of factors affecting the safe operation of the aircraft (engine failure, shortage of fuel, etc.); (b) hospital aircraft or aircraft carrying any sick or seriously injured persons requiring urgent medical attention; (c) aircraft engaged in search and rescue operations; and (d) other aircraft as may be determined by the competent authority. (PANS ATM — Section 7.7.3.3) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 105 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM1 to AMC19 ATS.TR.210(a)(3) Operation of ATC service AERODROME CONTROL — PRIORITY FOR LANDING (a) An aircraft landing or in the final stages of an approach to land should normally have priority over an aircraft intending to depart from the same or an intersecting runway. (b) If an aircraft enters an aerodrome traffic circuit without proper authorisation, it should be permitted to land if its actions indicate that it so desires. If circumstances warrant, aircraft which are in contact with the controller may be instructed to give way so as to remove as soon as possible the hazard introduced by such unauthorised operation. In no case should permission to land be withheld indefinitely. (c) In cases of emergency, it may be necessary, in the interests of safety, for an aircraft to enter a traffic circuit and effect a landing without proper authorisation. Controllers should recognise the possibilities of emergency action and render all assistance possible. (PANS ATM — Sections 7.7.3.1, 7.7.3.2 and 7.8) GM7 ATS.TR.210(a)(3) Operation of ATC service AERODROME CONTROL — PRIORITY FOR DEPARTURE Departures should normally be cleared in the order in which they are ready for take-off, except that deviations may be made from this order of priority to facilitate the maximum number of departures with the least average delay. Factors which should be considered in relation to the departure sequence include, inter alia: (a) types of aircraft and their relative performance; (b) routes to be followed after take-off; (c) any specified minimum departure interval between take-offs; (d) need to apply wake turbulence separation minima; (e) aircraft which should be afforded priority; and (f) aircraft subject to ATFM requirements. (PANS ATM — Section 7.9.1) GM8 ATS.TR.210(a)(3) Operation of ATC service AERODROME CONTROL — PRIORITY FOR DEPARTURE AND ATFM MEASURES For aircraft subject to ATFM requirements, it is the responsibility of the pilot and the operator to ensure that the aircraft is ready to taxi in time to meet any required departure time, bearing in mind that once a departure sequence is established on the taxiway system, it can be difficult, and sometimes impossible, to change the order. (PANS ATM — Note 2 to Section 7.9.1) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 106 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC20 ATS.TR.210(a)(3) Operation of ATC service VISUAL DEPARTURE (a) An IFR flight may be cleared to execute a visual departure: (1) when requested by the pilot; or (2) prior to take-off, when initiated by the controller and accepted by the pilot by a read-back of the ATC clearance. (b) When implemented, visual departure should be applied under the following conditions: (1) the meteorological conditions in the direction of take-off and the following climb-out are such that they do not impair the procedure up to an altitude to be established and published by the appropriate authority, e.g. minimum flight altitude (MFA) or minimum sector altitude (MSA); (2) the procedure is to be applied during the daytime; (3) the pilot is responsible for maintaining obstacle clearance until the specified altitude. Further clearance (route, heading, point) should be specified by ATC; and (4) separation is provided between an aircraft cleared to execute a visual departure and other aircraft, in accordance with the airspace classification. (c) Any additional local restrictions should be agreed on in consultation between the ATS provider and operators. (Doc 7030 — Sections 6.5.4.2, 6.5.4.3, and 6.5.4.4) GM1 to AMC20 ATS.TR.210(a)(3) Operation of ATC service VISUAL DEPARTURE If the aircraft is in or may enter airspace class D during the application of the visual departure, attention is drawn to the requirement to provide timely VFR traffic information deemed relevant for the aircraft executing the visual departure. Flight crews should be made aware when the application of the visual departure may lead the departing aircraft to enter airspace classes E, F or G. (Doc 7030 — Note to Section 6.5.4.3(d)) GM2 to AMC20 ATS.TR.210(a)(3) Operation of ATC service FLIGHT CREW ACCEPTANCE OF VISUAL DEPARTURE Flight crew acceptance of the clearance for visual departure will indicate that the aircraft take-off performance characteristics allow an early turn after take-off. (Doc 7030 — Section 6.5.4.3) AMC21 ATS.TR.210(a)(3) Operation of ATC service MISSED APPROACHES INSTRUCTIONS When issuing instruction for a missed approach to flight conducting an instrument approach procedure, the controller should adhere to the published missed approach procedure. The controller TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 107 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments should issue modifications to the published missed approach procedure only in presence of safety reasons. (In response to Safety Recommendation FRAN-2013-045 (BEA) addressed to EASA) AMC1 ATS.TR.210(b) Operation of ATC service CLEARANCES TO FLY MAINTAINING OWN SEPARATION WHILE IN VISUAL METEOROLOGICAL CONDITIONS When so requested by an aircraft and provided it is agreed by the pilot of the other aircraft and so authorised by the competent authority, an ATC unit may clear a controlled flight, including departing and arriving flights, operating in airspace Classes D and E in visual meteorological conditions during the hours of daylight to fly subject to maintaining own separation from the other aircraft and remaining in visual meteorological conditions. When a controlled flight is so cleared, the following should apply: (a) the clearance should be for a specified portion of the flight at or below 3 050 m (10 000 ft), during climb or descent and subject to further restrictions as and when prescribed by the competent authority; (b) if there is a possibility that flight under visual meteorological conditions may become impracticable, an IFR flight should be provided with alternative instructions to be complied with in the event that flight in VMC cannot be maintained for the term of the clearance; (c) the pilot of an IFR flight, on observing that conditions are deteriorating and considering that operation in VMC will become impossible, should inform ATC before entering instrument meteorological conditions (IMC) and should proceed in accordance with the alternative instructions given. (PANS ATM — Section 5.9) GM1 to AMC1 ATS.TR.210(b) Operation of ATC service CLEARANCES TO FLY MAINTAINING OWN SEPARATION WHILE IN VISUAL METEOROLOGICAL CONDITIONS (a) The provision of vertical or horizontal separation by an ATC unit is not applicable in respect of any specified portion of a flight cleared subject to maintaining own separation and remaining in visual meteorological conditions. It is for the aircraft so cleared to ensure, for the duration of the clearance, that it is not operated in such proximity to other flights as to create a collision hazard. (b) It is axiomatic that a VFR flight must remain in visual meteorological conditions at all times. Accordingly, the issuance of a clearance to a VFR flight to fly subject to maintaining own separation and remaining in visual meteorological conditions has no other object than to signify that, for the duration of the clearance, separation from other aircraft by ATC is not provided. (c) The objectives of the ATC service as prescribed in ATS.TR.100 do not include prevention of collision with terrain. Pilots are responsible to ensure that any clearances issued by ATC units are safe in this respect. 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, the procedures in ATS.TR.235(a)(5) apply. (PANS ATM — Notes 1, 2 and 3 to Section 5.9) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 108 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC1 ATS.TR.210(c) Operation of ATC service EMERGENCY SEPARATION APPLICATION (a) If, during an emergency situation, it is not possible to ensure that the applicable horizontal separation can be maintained, emergency separation of half the applicable vertical separation minimum may be used, i.e. a nominal 150 m (500 ft) between aircraft in airspace where a vertical separation minimum of 300 m (1 000 ft) is applied, and a nominal 300 m (1 000 ft) between aircraft in airspace where a 600 m (2 000 ft) vertical separation minimum is applied. (b) When emergency separation is applied, the flight crews concerned should be advised that emergency separation is being applied, and informed of the actual minimum used. Additionally, all flight crews concerned should be provided with essential traffic information. (PANS ATM — Sections 15.7.1.1 and 15.7.1.2) GM1 to AMC1 ATS.TR.210(c) Operation of ATC service SEPARATION APPLICATION IN CASE OF ATS SURVEILLANCE SYSTEM FAILURE As an emergency measure, in the event of complete failure of the ATS surveillance system where air– ground communications remain, the use of flight levels spaced by half the applicable vertical separation minimum may be resorted to temporarily if standard procedural separation cannot be provided immediately. (PANS ATM — Section 8.8.4.2) GM1 ATS.TR.210(c) Operation of ATC service PROCEDURAL SEPARATION — APPLICATION OF LARGER SEPARATION MINIMA UNDER SPECIFIC CIRCUMSTANCES Larger separations than the specified minima should be applied whenever exceptional circumstances such as unlawful interference or navigational difficulties call for extra precautions. This should be done with due regard to all relevant factors so as to avoid impeding the flow of air traffic by the application of excessive separations. (PANS ATM — Section 5.2.1.3) AMC1 ATS.TR.210(c)(1) Operation of ATC service PROCEDURAL SEPARATION — SEPARATION OF AIRCRAFT HOLDING IN FLIGHT (a) Except when lateral separation between the holding areas exists, the controller should separate aircraft established in adjacent holding patterns by the applicable vertical separation minimum. (b) Except when lateral separation exists, the controller should apply vertical separation between aircraft holding in flight and other aircraft, whether arriving, departing or en-route, whenever the other aircraft concerned are within 5 minutes flying time of the holding area or within a distance established by the ATS provider and approved by the competent authority (see Figure 3). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 109 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 3 — Separation between holding aircraft and en-route aircraft (PANS ATM — Sections 5.5.1 and 5.5.2) GM1 to AMC1 ATS.TR.210(c)(1) Operation of ATC service SEPARATION OF AIRCRAFT HOLDING IN FLIGHT Criteria and procedures for the simultaneous use of adjacent holding patterns should be prescribed in local instructions. (PANS ATM — Section 6.5.5.6 (third sentence)) GM1 ATS.TR.210(c)(1) Operation of ATC service VERTICAL SEPARATION APPLICATION Vertical separation is obtained by requiring aircraft using prescribed altimeter setting procedures to operate at different levels expressed in terms of flight levels or altitudes, in accordance with the provisions in ATS.TR.130, ATS.TR.135, ATS.TR.140, and ATS.TR.145. (PANS ATM — Section 5.3.1) GM2 ATS.TR.210(c)(1) Operation of ATC service APPLICATION OF VERTICAL SEPARATION DURING CLIMB OR DESCENT (a) An aircraft may cleared to a level previously occupied by another aircraft after the latter has reported vacating it, except when: (1) severe turbulence is known to exist; (2) the higher aircraft is effecting a cruise climb; or (3) the difference in aircraft performance is such that less than the applicable separation minimum may result; in which case such clearance should be withheld until the aircraft vacating the level has reported at or passing another level separated by the required minimum. (b) When the aircraft concerned are entering or established in the same holding pattern, consideration should be given to aircraft descending at markedly different rates and, if necessary, additional measures such as specifying a maximum descent rate for the higher TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 110 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments aircraft and a minimum descent rate for the lower aircraft should be applied to ensure that the required separation is maintained. (PANS ATM — Sections 5.3.4.1 and 5.3.4.1.1) GM3 ATS.TR.210(c)(1) Operation of ATC service GEOMETRIC HEIGHT INFORMATION Geometric height information is generated by airborne systems, for instance GPS or radio altimeters. AMC1 ATS.TR.210(c)(2) Operation of ATC service HORIZONTAL SEPARATION MINIMA BASED ON ATS SURVEILLANCE SYSTEM (a) Unless otherwise prescribed in accordance with point (b), or AMC6 ATS.TR.220, or ATS.TR.255, the horizontal separation minimum based on radar and/or ADS-B and/or MLAT systems should be 9.3 km (5.0 NM). (b) If so established by the ATS provider and approved by the competent authority, the separation minimum in point (a) may be reduced but not below: (1) 5.6 km (3.0 NM) when radar and/or ADS-B and/or MLAT systems’ capabilities at a given location so permit; and (2) 4.6 km (2.5 NM) between succeeding aircraft which are established on the same final approach track within 18.5 km (10 NM) of the runway threshold. A reduced separation minimum of 4.6 km (2.5 NM) may be applied, provided: (i) the average runway occupancy time of landing aircraft is proven, by means such as data collection and statistical analysis and methods based on a theoretical model, not to exceed 50 seconds; (ii) braking action is reported as good and runway occupancy times are not adversely affected by runway contaminants such as slush, snow or ice; (iii) an ATS surveillance system with appropriate azimuth and range resolution and an update rate of 5 seconds or less is used in combination with suitable displays; (iv) the aerodrome controller is able to observe, visually or by means of surface movement radar (SMR), MLAT system or a surface movement guidance and control system (SMGCS), the runway in use and associated exit and entry taxiways; (v) wake turbulence separation minima in AMC6 ATS.TR.220, or as may be prescribed by the ATS provider and approved by the competent authority (e.g. for specific aircraft types), do not apply; (vi) aircraft approach speeds are closely monitored by the controller and when necessary adjusted so as to ensure that separation is not reduced below the minimum; (vii) aircraft operators and pilots have been made fully aware of the need to exit the runway in an expeditious manner whenever the reduced separation minimum on final approach is applied; and TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 111 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (viii) procedures concerning the application of the reduced minimum are published in AIPs. (PANS ATM — Sections 8.7.3.1 and 8.7.3.2) GM1 to AMC1 ATS.TR.210(c)(2) Operation of ATC service CRITERIA FOR APPLICATION OF HORIZONTAL SEPARATION BASED ON RADAR AND/OR ADS-B AND/OR MLAT SYSTEMS (a) The separation minimum or minima based on radar and/or ADS-B and/or MLAT systems to be applied should be prescribed by the ATS provider and approved by the competent authority according to the capability of the particular ATS surveillance system or sensor to accurately identify the aircraft position in relation to the centre of a position symbol, PSR blip, SSR response and taking into account factors which may affect the accuracy of the ATS surveillance system- derived information, such as aircraft range from the radar site and the range scale of the situation display in use. (b) Separation based on the use of ADS-B, SSR and/or MLAT, and/or PSR position symbols and/or PSR blips should be applied so that the distance between the centres of the position symbols and/or PSR blips, representing the positions of the aircraft concerned, is never less than a prescribed minimum. (c) Separation based on the use of PSR blips and SSR responses should be applied so that the distance between the centre of the PSR blip and the nearest edge of the SSR response (or centre, when authorised by the competent authority) is never less than a prescribed minimum. (d) Separation based on the use of ADS-B position symbols and SSR responses should be applied so that the distance between the centre of the ADS-B position symbol and the nearest edge of the SSR response (or the centre, when authorised by the competent authority) is never less than a prescribed minimum. (e) Separation based on the use of SSR responses should be applied so that the distance between the closest edges of the SSR responses (of the centres, when authorised by the competent authority) is never less than a prescribed minimum. (f) In no circumstances, should the edges of the position indications touch or overlap unless vertical separation is applied between the aircraft concerned, irrespective of the type of position indication displayed and separation minimum applied. (PANS ATM — Sections 8.7.2.3, 8.7.2.4, 8.7.2.5, 8.7.2.6, 8.7.2.7 and 8.7.3.3) AMC2 ATS.TR.210(c)(2) Operation of ATC service SPECIFIC CONDITIONS AND LIMITATIONS FOR THE APPLICATION OF SEPARATION MINIMA BASED ON ATS SURVEILLANCE SYSTEM (a) The separation minima based on ATS surveillance systems specified in AMC1 ATS.TR.210(c)(2) and AMC6 ATS.TR.220 may be applied between an aircraft taking off and a preceding departing aircraft or other identified traffic, provided there is reasonable assurance that the departing aircraft will be identified within 2 km (1 NM) from the end of the runway, and that, at the time, the required separation will exist. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 112 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (b) The separation minima specified based on ATS surveillance systems should not be applied between aircraft holding over the same holding fix. (PANS ATM — Sections 8.7.2.9 and 8.7.2.10 (first sentence)) AMC3 ATS.TR.210(c)(2) Operation of ATC service PROCEDURAL SEPARATION — REDUCTION IN LATERAL AND LONGITUDINAL SEPARATION MINIMA (a) Provided prior consultation with airspace users is undertaken and that an appropriate safety assessment has shown that an acceptable level of safety is maintained, the lateral and longitudinal separation minima established in: — AMC1 ATS.TR.210(c)(2)(i); — AMC2 ATS.TR.210(c)(2)(i); — AMC3 ATS.TR.210(c)(2)(i); — AMC4 ATS.TR.210(c)(2)(i); — AMC5 ATS.TR.210(c)(2)(i); — AMC6 ATS.TR.210(c)(2)(i); and — AMC1 ATS.TR.210(c)(2)(ii) may be reduced in the following circumstances: (1) when special electronic or other aids enable the pilot-in-command of an aircraft to determine accurately the aircraft’s position and when adequate communication facilities exist for that position to be transmitted without delay to the appropriate ATC unit; or (2) when, in association with rapid and reliable communication facilities, information of an aircraft’s position, derived from an ATS surveillance system, is available to the appropriate ATC unit; or (3) when special electronic or other aids enable the air traffic controller to predict rapidly and accurately the flight paths of aircraft, and adequate facilities exist to verify frequently the actual aircraft positions with the predicted positions; or (4) when RNAV-equipped aircraft operate within the coverage of electronic aids that provide the necessary updates to maintain navigation accuracy. (b) In addition to circumstances mentioned in point (a), the lateral and longitudinal separation minima established in: — AMC1 ATS.TR.210(c)(2)(i); — AMC2 ATS.TR.210(c)(2)(i); — AMC3 ATS.TR.210(c)(2)(i); — AMC4 ATS.TR.210(c)(2)(i); — AMC5 ATS.TR.210(c)(2)(i); — AMC6 ATS.TR.210(c)(2)(i); and TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 113 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments — AMC1 ATS.TR.210(c)(2)(ii) may be reduced in the vicinity of aerodromes if: (1) adequate separation can be provided by the aerodrome controller when each aircraft is continuously visible to this controller; or (2) each aircraft is continuously visible to flight crews of the other aircraft concerned and the pilots thereof report that they can maintain their own separation; or (3) in the case of one aircraft following another, the flight crew of the succeeding aircraft reports that the other aircraft is in sight and separation can be maintained. (PANS ATM — Sections 5.11.1, 5.11.1.1 and 6.1) GM1 ATS.TR.210(c)(2)(i) Operation of ATC service PROCEDURAL SEPARATION — LONGITUDINAL SEPARATION APPLICATION (a) Longitudinal separation should be applied so that the spacing between the estimated positions of the aircraft being separated is never less than a prescribed minimum. Longitudinal separation between aircraft following the same or diverging tracks may be maintained by application of speed control, including the Mach number technique. When applicable, use of the Mach number technique should be prescribed on the basis of a regional air navigation agreement. (b) Longitudinal separation between supersonic aircraft during the transonic acceleration and supersonic phases of flight should normally be established by appropriate timing of the start of transonic acceleration rather than by the imposition of speed restrictions in supersonic flight. (c) Time-based separation applied in accordance with AMC1 ATS.TR.210(c)(2)(i), AMC2 ATS.TR.210(c)(2)(i) and AMC5 ATS.TR.210(c)(2)(i) may be based on position information and estimates derived from voice reports, controller–pilot data link communications (CPDLC) or ADS- C. (d) For the purpose of application of longitudinal separation, the terms ‘same track’, ‘reciprocal tracks’ and ‘crossing tracks’ have the following meanings: (1) Same track (see Figure 4) same direction tracks and intersecting tracks or portions thereof, the angular difference of which is less than 45 degrees or more than 315 degrees, and whose protected airspaces overlap. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 114 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 4 — Aircraft on same track (2) Reciprocal tracks (see Figure 5): opposite tracks and intersecting tracks or portions thereof, the angular difference of which is more than 135 degrees but less than 225 degrees, and whose protected airspaces overlap. Figure 5 — Aircraft on reciprocal tracks (3) Crossing tracks (see Figure 6): intersecting tracks or portions thereof other than those specified in points (1) and (2). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 115 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 6 — Aircraft on crossing tracks (PANS ATM — Sections 5.4.2.1.1, 5.4.2.1.4, 5.4.2.1.5, and 5.4.2.1.6) AMC1 ATS.TR.210(c)(2)(i) Operation of ATC service PROCEDURAL SEPARATION — LONGITUDINAL SEPARATION MINIMA BASED ON TIME — AIRCRAFT MAINTAINING THE SAME LEVEL For aircraft flying at the same level, the longitudinal separation minima based on time should be one of the following: (a) Aircraft flying on the same track (1) 15 minutes (see Figure 7); or Figure 7 — 15-minute separation between aircraft on same track and same level (2) 10 minutes if navigation aids permit frequent determination of position and speed (see Figure 8); or TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 116 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 8 — 10-minute separation between aircraft on same track and same level (3) 5 minutes in the following cases, provided that in each case the preceding aircraft is maintaining a true airspeed of 37 km/h (20 kt) or more faster than the succeeding aircraft (see Figure 9): Figure 9 — 5-minute separation between aircraft on same track and same level (i) between aircraft that have departed from the same aerodrome; (ii) between en-route aircraft that have reported over the same exact significant point; (iii) between departing and en-route aircraft after the en-route aircraft has reported over a fix that is so located in relation to the departure point as to ensure that 5- minute separation can be established at the point the departing aircraft will join the air route; or (4) 3 minutes in the cases listed under point (a)(3), provided that in each case the preceding aircraft is maintaining a true airspeed of 74 km/h (40 kt) or more faster than the succeeding aircraft (see Figure 10). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 117 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 10 — 3-minute separation between aircraft on same track and same level (b) Aircraft flying on crossing tracks (1) 15 minutes at the point of intersection of the tracks (see Figure 11); or Figure 11 — 15-minute separation between aircraft on crossing tracks and same level (2) 10 minutes if navigation aids permit frequent determination of position and speed (see Figure 12). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 118 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 12 — 10-minute separation between aircraft on crossing tracks and same level (PANS ATM — Sections 5.4.2.2.1.1 and 5.4.2.2.1.2) AMC2 ATS.TR.210(c)(2)(i) Operation of ATC service PROCEDURAL SEPARATION — LONGITUDINAL SEPARATION MINIMA BASED ON TIME — AIRCRAFT CLIMBING OR DESCENDING For aircraft climbing or descending, the longitudinal separation minima based on time should be one of the following: (a) Aircraft on the same track When an aircraft will pass through the level of another aircraft on the same track, the following minimum longitudinal separation should be provided: (1) 15 minutes while vertical separation does not exist (see Figures 13 and 14); or Figure 13 — 15-minute separation between aircraft climbing and on same track TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 119 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 14 — 15-minute separation between aircraft descending and on same track (2) 10 minutes while vertical separation does not exist, provided that such separation is authorised only where ground-based navigation aids or GNSS permit frequent determination of position and speed (see Figures 15 and 16); or Figure 15 — 10-minute separation between aircraft climbing and on same track Figure 16 — 10-minute separation between aircraft descending and on same track (3) 5 minutes while vertical separation does not exist, provided that: TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 120 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (i) the level change is commenced within 10 minutes of the time the second aircraft has reported over a common point which should be derived from ground-based navigation aids or by GNSS; and (ii) when issuing the clearance through third-party communication or CPDLC, a restriction should be added to the clearance to ensure that the 10-minute condition is satisfied (see Figures 17 and 18). Figure 17 — 5-minute separation between aircraft climbing and on same track Figure 18 — 5-minute separation between aircraft descending and on same track (b) Aircraft on crossing tracks (1) 15 minutes while vertical separation does not exist (see Figures 19 and 20); or TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 121 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 19 — 15-minute separation between aircraft climbing and on crossing tracks Figure 20 — 15-minute separation between aircraft descending and on crossing tracks (2) 10 minutes while vertical separation does not exist if navigation aids permit frequent determination of position and speed (see Figures 21 and 22). Figure 21 — 10-minute separation between aircraft climbing and on crossing tracks TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 122 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 22 — 10-minute separation between aircraft descending and on crossing tracks (c) Aircraft on reciprocal tracks Where lateral separation is not provided, vertical separation should be provided for at least 10 minutes prior to and after the time the aircraft are estimated to pass, or are estimated to have passed (see Figure 23). Provided it has been determined that the aircraft have passed each other, this minimum need not apply. Figure 23 — 10-minute separation between aircraft on reciprocal tracks (PANS ATM — Sections 5.4.2.2.2.1, 5.4.2.2.2.2 and 5.4.2.2.2.3) AMC3 ATS.TR.210(c)(2)(i) Operation of ATC service PROCEDURAL SEPARATION — LONGITUDINAL SEPARATION MINIMA BASED ON DISTANCE USING DISTANCE MEASURING EQUIPMENT (DME) AND/OR GNSS — AIRCRAFT AT THE SAME CRUISING LEVEL Longitudinal separation minima based on distance using distance measuring equipment (DME) and/or GNSS should be established between aircraft at the same cruising level, as follows: (a) Aircraft on the same track (1) 37 km (20 NM), provided: (i) each aircraft utilises: TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 123 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (A) the same ‘on-track’ DME station when both aircraft are utilising DME; or (B) an ‘on-track’” DME station and a collocated waypoint when one aircraft is utilising DME and the other is utilising GNSS; or (C) the same waypoint when both aircraft are utilising GNSS; and (ii) separation is checked by obtaining simultaneous DME and/or GNSS readings from the aircraft at frequent intervals to ensure that the minimum will not be infringed (see Figure 24); Figure 24 — 37 Km (20 NM) DME and/or GNSS-based separation between aircraft on same track and same level (2) 19 km (10 NM), provided: (i) the leading aircraft maintains a true airspeed of 37 km/h (20 kt) or more faster than the succeeding aircraft; (ii) each aircraft utilises: (A) the same ‘on-track’ DME station when both aircraft are utilising DME; or (B) an ‘on-track’ DME station and a collocated waypoint when one aircraft is utilising DME and the other is utilising GNSS; or (C) the same waypoint when both aircraft are utilising GNSS; and (iii) separation is checked by obtaining simultaneous DME and/or GNSS readings from the aircraft at such intervals as are necessary to ensure that the minimum is established and will not be infringed (see Figure 25). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 124 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 25 — 19 Km (10 NM) DME and/or GNSS-based separation between aircraft on same track and same level (b) Aircraft on crossing tracks The longitudinal separation prescribed in point (a) should also apply, provided each aircraft reports distance from the DME station and/or collocated waypoint or same waypoint located at the crossing point of the tracks and that the relative angle between the tracks is less than 90 degrees (see Figures 26 and 27). Figure 26 — 37 Km (20 NM) DME and/or GNSS-based separation between aircraft on crossing tracks and same level TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 125 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 27 — 19 Km (10 NM) DME and/or GNSS-based separation between aircraft on crossing tracks and same level (PANS ATM — Sections 5.4.2.3.3.1 and 5.4.2.3.3.2) AMC4 ATS.TR.210(c)(2)(i) Operation of ATC service PROCEDURAL SEPARATION — LONGITUDINAL SEPARATION MINIMA BASED ON DISTANCE USING DISTANCE MEASURING EQUIPMENT (DME) AND/OR GNSS — AIRCRAFT CLIMBING OR DESCENDING Longitudinal separation minima based on distance using distance measuring equipment (DME) AND/OR GNSS should be established between aircraft climbing or descending, as follows: (a) Aircraft on the same track 19 km (10 NM) while vertical separation does not exist, provided: (1) each aircraft utilises: (i) the same ‘on-track’ DME station when both aircraft are utilising DME; or (ii) an ‘on-track’ DME station and a collocated waypoint when one aircraft is utilising DME and the other is utilising GNSS; or (iii) the same waypoint when both aircraft are utilising GNSS; and (2) one aircraft maintains a level while vertical separation does not exist; and (3) separation is established by obtaining simultaneous DME and/or GNSS readings from the aircraft (see Figures 28 and 29). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 126 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 28 — 19 Km (10 NM) DME and/or GNSS-based separation between aircraft climbing and on same track Figure 29 — 19 Km (10 NM) DME and/or GNSS-based separation between aircraft descending and on same track (b) Aircraft on reciprocal tracks Aircraft utilising on-track DME and/or collocated waypoint or same waypoint may be cleared to climb or descend through the levels occupied by other aircraft utilising on-track DME and/or collocated waypoint or same waypoint, provided that it has been positively established that the aircraft have passed each other and are at least 10 NM apart, or such other value determined by the ATS provider and approved by the competent authority. (PANS ATM — Sections 5.4.2.3.4.1 and 5.4.2.3.4.2) GM1 to AMC3 ATS.TR.210(c)(2)(i) and to AMC4 ATS.TR.210(c)(2)(i) Operation of ATC service PROCEDURAL SEPARATION — LONGITUDINAL SEPARATION MINIMA BASED ON DISTANCE USING DISTANCE MEASURING EQUIPMENT (DME) AND/OR GNSS — APPLICATION (a) Where the term ‘on track’ is used in the provisions relating to the application of longitudinal separation minima using DME and/or GNSS, it means that the aircraft is flying either directly inbound to or directly outbound from the station/waypoint. (b) Separation should be established by maintaining not less than the specified distance(s) between aircraft positions as reported by reference to DME in conjunction with other appropriate TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 127 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments navigation aids and/or GNSS. This type of separation should be applied between two aircraft using DME, or two aircraft using GNSS, or one aircraft using DME and one aircraft using GNSS. Direct controller-pilot VHF voice communication should be maintained while such separation is used. (c) For the purpose of applying GNSS-based separation minimum, a distance derived from an integrated navigation system incorporating GNSS input is regarded as equivalent to GNSS distance. (d) When applying these separation minima between any aircraft with area navigation capability, controllers should specifically request GNSS-derived distance. (PANS ATM — Sections 5.4.2.3 (Note to Section), 5.4.2.3.1, 5.4.2.3.1 (Note to Section) and 5.4.2.3.2) AMC5 ATS.TR.210(c)(2)(i) Operation of ATC service PROCEDURAL SEPARATION — LONGITUDINAL SEPARATION MINIMA WITH MACH NUMBER TECHNIQUE BASED ON TIME When the Mach number technique is applied and provided that: (a) the aircraft concerned have reported over the same common point and follow the same track or continuously diverging tracks until some other form of separation is provided; or (b) if the aircraft have not reported over the same common point and it is possible to ensure, by radar, ADS-B or other means, that the appropriate time interval will exist at the common point from which they either follow the same track or continuously diverging tracks, minimum longitudinal separation between turbojet aircraft on the same track, whether in level, climbing or descending flight should be: (1) 10 minutes. In this case, the preceding aircraft should maintain a true Mach number equal to or greater than that maintained by the following aircraft; or (2) between 9 and 5 minutes inclusive, provided that the preceding aircraft is maintaining a true Mach number greater than the following aircraft in accordance with the following: (i) 9 minutes if the preceding aircraft is Mach 0.02 faster than the following aircraft; (ii) 8 minutes if the preceding aircraft is Mach 0.03 faster than the following aircraft; (iii) 7 minutes if the preceding aircraft is Mach 0.04 faster than the following aircraft; (iv) 6 minutes if the preceding aircraft is Mach 0.05 faster than the following aircraft; (v) 5 minutes if the preceding aircraft is Mach 0.06 faster than the following aircraft. (PANS ATM — Sections 5.4.2.4.3 and 5.4.2.4.4) AMC6 ATS.TR.210(c)(2)(i) Operation of ATC service PROCEDURAL SEPARATION — LONGITUDINAL SEPARATION MINIMA WITH MACH NUMBER TECHNIQUE BASED ON DISTANCE USING RNAV (a) The controller should not apply RNAV distance-based separation minima after having received pilot advice indicating navigation equipment deterioration or failure. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 128 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (b) A 150 km (80 NM) RNAV distance-based separation minimum with Mach number technique may be used on same-direction tracks in lieu of a 10-minute longitudinal separation minimum with Mach number technique, provided that: (1) each aircraft reports its distance to or from the same ‘on-track’ common point; (2) separation between aircraft at the same level is checked by obtaining simultaneous RNAV distance readings from the aircraft at frequent intervals to ensure that the minimum will not be infringed (see Figure 30); Figure 30 — 150 Km (80 NM) RNAV-based separation between aircraft at the same level (3) separation between aircraft climbing or descending is established by obtaining simultaneous RNAV distance readings from the aircraft (see Figures 31 and 32); and Figure 31 — 150 Km (80 NM) RNAV-based separation between aircraft climbing and on same track TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 129 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 32 — 150 Km (80 NM) RNAV-based separation between aircraft descending and on same track (4) in the case of aircraft climbing or descending, one aircraft maintains a level while vertical separation does not exist. (c) Aircraft on reciprocal tracks Aircraft utilising RNAV may be cleared to climb or descend to or through the levels occupied by other aircraft utilising RNAV, provided it has been positively established by simultaneous RNAV distance readings to or from the same ‘on-track’ common point that the aircraft have passed each other and are at least 150 km (80 NM) apart (see Figure 33). Figure 33 — 150 Km (80 NM) RNAV-based separation between aircraft on reciprocal tracks (PANS ATM — Sections 5.4.2.5.2, 5.4.2.5.5, and 5.4.2.5.7) GM1 to AMC6 ATS.TR.210(c)(2)(i) Operation of ATC service LONGITUDINAL SEPARATION MINIMA WITH MACH NUMBER TECHNIQUE BASED ON DISTANCE USING RNAV — APPLICATION (a) Separation should be established by maintaining not less than the specified distance between aircraft positions as reported by reference to RNAV equipment. Direct controller-pilot communications should be maintained, while such separation is used. Where high frequency or general purpose extended range very high frequency air–ground communication channels are used for area control service and are worked by air–ground communicators, suitable TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 130 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments arrangements should be made to permit direct controller-pilot communications, or monitoring by the controller of all air–ground communications. (b) To assist pilots to readily provide the required RNAV distance information, such position reports should, wherever possible, be referenced to a common waypoint ahead of both aircraft. (c) RNAV distance-based separation may be applied between RNAV-equipped aircraft when operating on designated RNAV routes or on ATS routes defined by VOR. (d) To facilitate application of the procedure where a considerable change of level is involved, a descending aircraft may be cleared to some convenient level above the lower aircraft, or a climbing aircraft to some convenient level below the higher aircraft, to permit a further check on the separation that will be obtained while vertical separation does not exist. (PANS ATM — Sections 5.4.2.5.3, 5.4.2.5.3.1, 5.4.2.5.4 and 5.4.2.5.6 (Note to Section)) AMC7 ATS.TR.210(c)(2)(i) Operation of ATC service RUNWAY SEPARATION MINIMA BETWEEN DEPARTING AIRCRAFT AND OTHER AIRCRAFT USING THE SAME RUNWAY Except as provided in AMC9 ATS.TR.210(c)(2)(i) as regards reduced runway separation minima between aircraft using the same runway, and in ATS.TR.220 as regards time-based wake turbulence separation minima, the aerodrome control tower should not permit a departing aircraft to commence take-off until the preceding departing aircraft has crossed the end of the runway in use or has started a turn or until all preceding landing aircraft are clear of the runway in use. Position limits to be reached by a landed aircraft (A) or a departing aircraft (B or C) before an arriving aircraft may be cleared to cross the threshold of the runway-in-use or a departing aircraft may be cleared to take off, unless otherwise prescribed. Figure 34 — Separation between departing and arriving aircraft (PANS ATM — Section 7.9.2) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 131 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC8 ATS.TR.210(c)(2)(i) Operation of ATC service RUNWAY SEPARATION OF LANDING AIRCRAFT AND PRECEDING LANDING AND DEPARTING AIRCRAFT USING THE SAME RUNWAY Except as provided AMC9 ATS.TR.210(c)(2)(i) as regards reduced runway separation minima between aircraft using the same runway, and in ATS.TR.220 as regards time-based wake turbulence separation minima, the aerodrome control tower should not permit a landing aircraft to cross the runway threshold on its final approach until the preceding departing aircraft has crossed the end of the runway in use, or has started a turn, or until all preceding landing aircraft are clear of the runway in use. (PANS ATM — Section 7.10.1) AMC9 ATS.TR.210(c)(2)(i) Operation of ATC service REDUCED RUNWAY SEPARATION MINIMA BETWEEN AIRCRAFT USING THE SAME RUNWAY (a) The ATS provider may prescribe lower minima than those established in AMC7 ATS.TR.210(c)(2)(i) concerning separation of departing aircraft, and in AMC8 ATS.TR.210(c)(2)(i) concerning separation of landing aircraft and preceding landing and departing aircraft using the same runway, after consultation with the operators. The safety assessment to be performed in support of the application of reduced separation minima should be carried out for each runway for which the reduced minima are intended, taking into account factors such as: (1) runway length; (2) aerodrome layout; and (3) types/categories of aircraft involved. (b) Reduced runway separation minima should only be applied during the hours of daylight from 30 minutes after local sunrise to 30 minutes before local sunset. (c) For the purpose of reduced runway separation, aircraft should be classified as follows: (1) Category 1 aircraft: single-engine propeller aircraft with a maximum certificated take-off mass of 2 000 kg or less; (2) Category 2 aircraft: single-engine propeller aircraft with a maximum certificated take-off mass of more than 2 000 kg but less than 7 000 kg; and twin-engine propeller aircraft with a maximum certificated take-off mass of less than 7 000 kg; (3) Category 3 aircraft: all other aircraft. (d) Reduced runway separation minima should not apply between a departing aircraft and a preceding landing aircraft. (e) Reduced runway separation minima should be subject to the following conditions: (1) wake turbulence separation minima should be applied; (2) visibility should be at least 5 km and ceiling shall not be lower than 300 m (1 000 ft); (3) tailwind component should not exceed 5 kt; (4) there should be available means, such as suitable landmarks, to assist the controller in assessing the distances between aircraft. A surface surveillance system that provides the TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 132 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments air traffic controller with position information on aircraft may be utilised, provided that approval for operational use of such equipment includes a safety assessment to ensure that all requisite operational and performance requirements are met; (5) minimum separation continues to exist between two departing aircraft immediately after take-off of the second aircraft; (6) traffic information should be provided to the flight crew of the succeeding aircraft concerned; and (7) the braking action should not be adversely affected by runway contaminants such as ice, slush, snow and water. (f) Reduced runway separation minima which may be applied at an aerodrome should be determined for each separate runway. The separation to be applied should in no case be less than the following minima: (1) landing aircraft: (i) a succeeding landing Category 1 aircraft may cross the runway threshold when the preceding aircraft is a Category 1 or 2 aircraft which either: (A) has landed and has passed a point at least 600 m from the threshold of the runway, is in motion and will vacate the runway without backtracking; or (B) is airborne and has passed a point at least 600 m from the threshold of the runway; (ii) a succeeding landing Category 2 aircraft may cross the runway threshold when the preceding aircraft is a Category 1 or 2 aircraft which either: (A) has landed and has passed a point at least 1 500 m from the threshold of the runway, is in motion and will vacate the runway without backtracking; or (B) is airborne and has passed a point at least 1 500 m from the threshold of the runway; (iii) a succeeding landing aircraft may cross the runway threshold when a preceding Category 3 aircraft: (A) has landed and has passed a point at least 2 400 m from the threshold of the runway, is in motion and will vacate the runway without backtracking; or (B) is airborne and has passed a point at least 2 400 m from the threshold of the runway; (2) departing aircraft: (i) a Category 1 aircraft may be cleared for take-off when the preceding departing aircraft is a Category 1 or 2 aircraft which is airborne and has passed a point at least 600 m from the position of the succeeding aircraft; (ii) a Category 2 aircraft may be cleared for take-off when the preceding departing aircraft is a Category 1 or 2 aircraft which is airborne and has passed a point at least 1 500 m from the position of the succeeding aircraft; and TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 133 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (iii) an aircraft may be cleared for take-off when a preceding departing Category 3 aircraft is airborne and has passed a point at least 2 400 m from the position of the succeeding aircraft. (PANS ATM — Sections 7.11.1, 7.11.3, 7.11.4, 7.11.5, 7.11.6 and 7.11.7) AMC10 ATS.TR.210(c)(2)(i) Operation of ATC service PROCEDURAL CONTROL — MINIMUM SEPARATION BETWEEN DEPARTING AIRCRAFT (a) The aerodrome controller should apply an 1-minute separation if aircraft are to fly on tracks diverging by at least 45 degrees immediately after take-off so that lateral separation is provided (see Figure 5-37). (b) When: (1) aircraft are using parallel runways; or (2) in a context of operations on diverging runways which do not cross, the pilot has accepted a take-off direction which is not into the wind, in accordance with the procedure described in point (b) of GM1 ATS.TR.260, this minimum may be reduced, provided instructions covering the procedure have been established by the ATS provider and approved by the competent authority and lateral separation is effected immediately after take-off. Figure 35 — 1-minute separation between departing aircraft following tracks diverging by at least 45 degrees (c) The controller should apply a 2-minute separation between take-offs when the preceding aircraft is 74 km/h (40 kt) or more faster than the following aircraft and both aircraft will follow the same track (see Figure 36). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 134 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 36 — 2-minute separation between aircraft following same track (d) The controller should apply a 5-minute separation while vertical separation does not exist if a departing aircraft will be flown through the level of a preceding departing aircraft and both aircraft propose to follow the same track (see Figure 37). The controller should take action to ensure that the 5-minute separation will be maintained or increased while vertical separation does not exist. Figure 37 — 5-minute separation of departing aircraft following same track (PANS ATM — Sections 5.6.1, 5.6.2 and 5.6.3) AMC11 ATS.TR.210(c)(2)(i) Operation of ATC service PROCEDURAL CONTROL — SEPARATION OF DEPARTING AIRCRAFT FROM ARRIVING AIRCRAFT The aerodrome controller should apply the following separation when take-off clearance is based on the position of an arriving aircraft: (a) If an arriving aircraft is making a complete instrument approach, a departing aircraft may take off: (1) in any direction until an arriving aircraft has started its procedure turn or base turn leading to final approach; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 135 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (2) in a direction which is different by at least 45 degrees from the reciprocal of the direction of approach after the arriving aircraft has started procedure turn or base turn leading to final approach, provided that the take-off will be made at least 3 minutes before the arriving aircraft is estimated to be over the beginning of the instrument runway (see Figure 38). Figure 38 — Separation of departing aircraft from arriving aircraft (b) If an arriving aircraft is making a straight-in approach, a departing aircraft may take off: (1) in any direction until 5 minutes before the arriving aircraft is estimated to be over the instrument runway; (2) in a direction which is different by at least 45 degrees from the reciprocal of the direction of approach of the arriving aircraft: (i) until 3 minutes before the arriving aircraft is estimated to be over the beginning of the instrument runway (see Figure 38); or (ii) before the arriving aircraft crosses a designated fix on the approach track; the location of such fix should be determined by the ATS provider after consultation with the operators, and approved by the competent authority. (PANS ATM — Sections 5.7.1, 5.7.1.1 and 5.7.1.2) AMC1 ATS.TR.210(c)(2)(ii) Operation of ATC service PROCEDURAL CONTROL — LATERAL SEPARATION CRITERIA AND MINIMA Lateral separation should be applied by one of the following means: (a) By reference to the same or different geographic locations By position reports which positively indicate that the aircraft are over different geographic locations as determined visually or by reference to a navigation aid (see Figure 39). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 136 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 39 — Using same or different geographic locations (b) By use of NDB, VOR or GNSS on intersecting tracks or ATS routes By requiring aircraft to fly on specified tracks which are separated by a minimum amount appropriate to the navigation aid employed. Lateral separation between two aircraft exists when: (1) VOR: both aircraft are established on radials diverging by at least 15 degrees and at least one aircraft is at a distance of 28 km (15 NM) or more from the facility (see Figure 40); Figure 40 — Separation using the same VOR (2) NDB: both aircraft are established on tracks to or from the NDB which are diverging by at least 30 degrees and at least one aircraft is at a distance of 28 km (15 NM) or more from the facility (see Figure 41); TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 137 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 41 — Separation using the same NDB (3) GNSS/GNSS: each aircraft is confirmed to be established on a track with zero offset between two waypoints and at least one aircraft is at a minimum distance from a common point as specified in Table 1 below; or (4) VOR/GNSS: the aircraft using VOR is established on a radial to or from the VOR and the other aircraft using GNSS is confirmed to be established on a track with zero offset between two waypoints and at least one aircraft is at a minimum distance from a common point as specified in Table 1 below. Table 1 Aircraft 1: VOR or GNSS Aircraft 2: GNSS Angular difference between tracks FL010–FL090 FL200–FL600 measured at the common point (degrees) Distance from a common point Distance from a common point 15–135 27.8 km (15 NM) 43 km (23 NM) The distances in the table are ground distances. States must take into account the distance (slant range) from the source of a DME signal to the receiving antenna when DME is being utilised to provide range information. (c) By use of different navigation aids or methods Lateral separation between aircraft using different navigation aids, or when one aircraft is using RNAV equipment, should be established by ensuring that the derived protected airspaces for the navigation aid(s) or RNP do not overlap. (d) Lateral separation of aircraft on published instrument flight procedures for arrivals and departures Lateral separation of departing and/or arriving aircraft, using instrument flight procedures, will exist: (1) where the distance between any combination of RNAV 1 with RNAV 1, or RNP 1, RNP APCH or RNP AR APCH tracks is not less than 13 km (7 NM); or (2) where the distance between any combination of RNP 1, RNP APCH or RNP AR APCH tracks is not less than 9.3 km (5 NM); or (3) where the protected areas of tracks designed using obstacle clearance criteria do not overlap and provided operational error is considered. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 138 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (e) RNAV operations where RNP is specified on parallel tracks or ATS routes Within designated airspace or on designated routes, where RNP is specified, lateral separation between RNAV-equipped aircraft may be obtained by requiring aircraft to be established on the centre lines of parallel tracks or ATS routes spaced at a distance which ensures that the protected airspace of the tracks or ATS routes does not overlap. (f) Transitioning into airspace where a greater lateral separation minimum applies Lateral separation will exist when aircraft are established on specified tracks which: (1) are separated by an appropriate minimum; and (2) diverge by at least 15 degrees until the applicable lateral separation minimum is established; provided that it is possible to ensure, by means approved by the competent authority, that aircraft have the navigation capability necessary to ensure accurate track guidance. (PANS ATM — Sections 5.4.1.2.1, 5.4.1.2.1.1, 5.4.1.2.1.2, 5.4.1.2.1.3, 5.4.1.2.1.4. 5.4.1.2.1.5 and 5.4.1.2.1.9) GM1 to AMC1 ATS.TR.210(c)(2)(ii) Operation of ATC service PROCEDURAL CONTROL — LATERAL SEPARATION OF AIRCRAFT ON PUBLISHED INSTRUMENT FLIGHT PROCEDURES FOR ARRIVALS AND DEPARTURES ICAO Circular 324 ‘Guidelines for Lateral Separation of Arriving and Departing Aircraft on Published Adjacent Instrument Flight Procedures’ contains information on separation of arrival and departure tracks using non-overlapping protected areas based on obstacle clearance criteria, as provided for in the Procedures for Air Navigation Services — Aircraft Operations, Volume II — Construction of Visual and Instrument Flight Procedures (PANS-OPS, Doc 8168). (PANS ATM — Section 5.4.1.2.1.4.1) GM1 ATS.TR.210(c)(2)(ii) Operation of ATC service PROCEDURAL CONTROL — LATERAL SEPARATION APPLICATION (a) Lateral separation should be applied so that the distance between those portions of the intended routes for which the aircraft are to be laterally separated is never less than an established distance to account for navigational inaccuracies plus a specified buffer. This buffer should be determined by the ATS provider and approved by the competent authority and included in the lateral separation minima as an integral part thereof. (b) Lateral separation of aircraft is obtained by requiring operation on different routes or in different geographical locations as determined by visual observation, by the use of navigation aids or by the use of area navigation (RNAV) equipment. (c) When an aircraft turns onto an ATS route via a flyover waypoint, a separation other than the normally prescribed lateral separation is to be applied for that portion of the flight between the flyover waypoint where the turn is executed and the next waypoint (see Figures 42 and 43). (d) For flyover waypoints, aircraft are required to first fly over the waypoint before executing the turn. After the turn the aircraft may either navigate to join the route immediately after the turn TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 139 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments or navigate to the next defined waypoint before re-joining the route. This will require additional lateral separation on the overflown side of the turn. Figure 42 — Turn over flyover waypoint Figure 43 — Turn at fly-by waypoint TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 140 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (PANS ATM — Sections 5.4.1.1.1, 5.4.1.1.2, 5.4.1.1.4 and 5.4.1.1.4 (Note to Section)) GM1 ATS.TR.210(d) Operation of ATC service APPLICATION OF SEPARATION MINIMA TO IDENTIFIED AIRCRAFT (a) When the control of an identified aircraft is to be transferred to a control sector that will provide the aircraft with procedural separation, the transferring controller should ensure that appropriate procedural separation is established between that aircraft and any other controlled aircraft before the transfer is effected. (b) When control of an identified aircraft is to be transferred to a control sector that will provide the aircraft with procedural separation, such separation should be established by the transferring controller before the aircraft reaches the limits of the transferring controller’s area of responsibility, or before the aircraft leaves the relevant area of surveillance coverage. (PANS ATM — Sections 8.6.7.2 and 8.7.2.2) AMC1 ATS.TR.220 Application of wake turbulence separation CATEGORISATION OF AIRCRAFT FOR THE PURPOSES OF WAKE TURBULENCE SEPARATION MINIMA APPLICATION Wake turbulence separation minima should be based on a grouping of aircraft types into four categories according to the maximum certificated take-off mass as follows: (a) SUPER (S) if so identified by the competent authority; (b) HEAVY (H) — all aircraft types of 136 000 kg or more; (c) MEDIUM (M) — aircraft types less than 136 000 kg but more than 7 000 kg; and (d) LIGHT (L) — aircraft types of 7 000 kg or less. (PANS ATM — Section 4.9.1.1, ICAO TEC/OPS/SEP – 08-0294.SLG ‘Wake turbulence aspects of Airbus A380-800 aircraft’, dated 08 July 2008) GM1 to AMC1 ATS.TR.220 Application of wake turbulence separation For the Airbus A380-800, with a maximum take-off mass in the order of 560 000 kg, it is recommended to apply an increase of the wake turbulence separation minima associated to the HEAVY category. (ICAO TEC/OPS/SEP – 08-0294.SLG ‘Wake turbulence aspects of Airbus A380-800 aircraft’, dated 08 July 2008) AMC2 ATS.TR.220 Application of wake turbulence separation TIME-BASED WAKE TURBULENCE LONGITUDINAL SEPARATION MINIMA — ARRIVING AIRCRAFT Except for arriving VFR flights, and for arriving IFR flights executing visual approach, the following separation minima should be applied to aircraft landing behind a HEAVY or a MEDIUM aircraft: (a) MEDIUM aircraft behind SUPER aircraft: 3 minutes; (b) MEDIUM aircraft behind HEAVY aircraft: 2 minutes; (c) LIGHT aircraft behind SUPER aircraft: 4 minutes; and TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 141 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (d) LIGHT aircraft behind a HEAVY or MEDIUM aircraft: 3 minutes. (PANS ATM — Sections 5.8.2.1 and 5.8.2.1.1, ICAO TEC/OPS/SEP – 08-0294.SLG ‘Wake turbulence aspects of Airbus A380-800 aircraft’, dated 08 July 2008) AMC3 ATS.TR.220 Application of wake turbulence separation TIME-BASED WAKE TURBULENCE LONGITUDINAL SEPARATION MINIMA — DEPARTING AIRCRAFT (a) A separation minimum of 3 minutes should be applied for a LIGHT or MEDIUM aircraft and 2 minutes for a HEAVY aircraft taking off behind a SUPER aircraft when the aircraft are using: (1) the same runway; (2) parallel runways separated by less than 760 m (2 500 ft); (3) crossing runways if the projected flight path of the second aircraft will cross the projected flight path of the first aircraft at the same altitude or less than 300 m (1 000 ft) below; (4) parallel runways separated by 760 m (2 500 ft) or more if the projected flight path of the second aircraft will cross the projected flight path of the first aircraft at the same altitude or less than 300 m (1 000 ft) below. (b) A separation minimum of 4 minutes should be applied for a LIGHT or MEDIUM aircraft when taking off behind an SUPER aircraft from: (1) an intermediate part of the same runway; or (2) an intermediate part of a parallel runway separated by less than 760 m (2 500 ft). (c) A separation minimum of 2 minutes should be applied between a LIGHT or MEDIUM aircraft taking off behind a HEAVY aircraft or a LIGHT aircraft taking off behind a MEDIUM aircraft when the aircraft are using: (1) the same runway (see Figure 44); (2) parallel runways separated by less than 760 m (2 500 ft) (see Figure 44); (3) crossing runways if the projected flight path of the second aircraft will cross the projected flight path of the first aircraft at the same altitude or less than 300 m (1 000 ft) below (see Figure 45); (4) parallel runways separated by 760 m (2 500 ft) or more if the projected flight path of the second aircraft will cross the projected flight path of the first aircraft at the same altitude or less than 300 m (1 000 ft) below (see Figure 45). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 142 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 44 — 2-minute separation for following aircraft Figure 45 — 2-minute wake turbulence separation for crossing aircraft (d) A separation minimum of 3 minutes should be applied (see Figure 46) between a LIGHT or MEDIUM aircraft when taking off behind a HEAVY aircraft or a LIGHT aircraft when taking off behind a MEDIUM aircraft from: (1) an intermediate part of the same runway; or (2) an intermediate part of a parallel runway separated by less than 760 m (2 500 ft). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 143 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 46 — 3-minute wake turbulence separation for following aircraft (PANS ATM — Sections 5.8.3.1 and 5.8.3.2, ICAO TEC/OPS/SEP – 08-0294.SLG ‘Wake turbulence aspects of Airbus A380-800 aircraft’, dated 08 July 2008) AMC4 ATS.TR.220 Application of wake turbulence separation TIME-BASED WAKE TURBULENCE LONGITUDINAL SEPARATION MINIMA — DISPLACED LANDING THRESHOLD (a) A separation minimum of 3 minutes should be applied between a LIGHT or MEDIUM aircraft and a SUPER aircraft when operating on a runway with a displaced landing threshold when: (1) a departing LIGHT or MEDIUM aircraft follows an SUPER aircraft arrival; or (2) an arriving LIGHT or MEDIUM aircraft follows an SUPER aircraft departure if the projected flight paths are expected to cross. (b) A separation minimum of 2 minutes should be applied between a LIGHT or MEDIUM aircraft and a HEAVY aircraft and between a LIGHT aircraft and a MEDIUM aircraft when operating on a runway with a displaced landing threshold when: (1) a departing LIGHT or MEDIUM aircraft follows a HEAVY aircraft arrival and a departing LIGHT aircraft follows a MEDIUM aircraft arrival; or (2) an arriving LIGHT or MEDIUM aircraft follows a HEAVY aircraft departure and an arriving LIGHT aircraft follows a MEDIUM aircraft departure if the projected flight paths are expected to cross. (PANS ATM — Section 5.8.4, ICAO TEC/OPS/SEP – 08-0294.SLG ‘Wake turbulence aspects of Airbus A380-800 aircraft’, dated 08 July 2008) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 144 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC5 ATS.TR.220 Application of wake turbulence separation TIME-BASED WAKE TURBULENCE LONGITUDINAL SEPARATION MINIMA — OPPOSITE DIRECTION (a) A separation minimum of 3 minutes should be applied between a LIGHT or MEDIUM aircraft and a SUPER aircraft when the SUPER aircraft is making a low or missed approach and the LIGHT or MEDIUM aircraft is: (1) utilising an opposite-direction runway for take-off; or (2) landing on the same runway in the opposite direction, or on a parallel opposite-direction runway separated by less than 760 m (2 500 ft). (b) A separation minimum of 2 minutes should be applied between a LIGHT or MEDIUM aircraft and a HEAVY aircraft and between a LIGHT aircraft and a MEDIUM aircraft when the heavier aircraft is making a low or missed approach and the lighter aircraft is: (1) utilising an opposite-direction runway for take-off (see Figure 47); or Figure 47 — 2-minute wake turbulence separation for opposite-direction take-off (2) landing on the same runway in the opposite direction, or on a parallel opposite-direction runway separated by less than 760 m (2 500 ft) (see Figure 48). Figure 48 — 2-minute wake turbulence separation for opposite-direction landing TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 145 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (PANS ATM — Section 5.8.5, ICAO TEC/OPS/SEP – 08-0294.SLG ‘Wake turbulence aspects of Airbus A380-800 aircraft’, dated 08 July 2008) AMC6 ATS.TR.220 Application of wake turbulence separation DISTANCE-BASED WAKE TURBULENCE SEPARATION MINIMA BASED ON ATS SURVEILLANCE SYSTEM (a) The following distance-based wake turbulence separation minima should be applied to aircraft being provided with an ATS surveillance service in the approach and departure phases: PRECEDING AICRAFT SUCCEEDING AIRCRAFT WAKE TURBULENCE RADAR SEPARATION MINIMA SUPER or HEAVY SUPER Not required. In this case, separation reverts to radar separation minima as established by the ATS provider and approved by the competent authority. SUPER HEAVY 11.1 km (6.0 NM) SUPER MEDIUM 13.0 km (7.0 NM) SUPER LIGHT 14.8 km (8.0 NM) HEAVY HEAVY 7.4 km (4.0 NM) HEAVY MEDIUM 9.3 km (5.0 NM) HEAVY LIGHT 11.1 km (6.0 NM) MEDIUM LIGHT 9.3 km (5 NM) (b) Separation minima as in point (a) between SUPER aircraft and other aircraft should be applied when: (1) an aircraft is operating directly behind an A380-800 aircraft at the same altitude or less than 300 m (1 000 ft) below; or (2) both aircraft are using the same runway, or parallel runways separated by less than 760 m; or (3) an aircraft is crossing behind an A380-800 aircraft, at the same altitude or less than 300 m (1 000 ft) below. (PANS ATM — Section 8.7.3.4, ICAO TEC/OPS/SEP – 08-0294.SLG ‘Wake turbulence aspects of Airbus A380-800 aircraft’, dated 08 July 2008) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 146 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM1 to AMC6 ATS.TR.220 Application of wake turbulence separation Figures 49 and 50 provide a visualisation of the application of the aforementioned separation minima between HEAVY, MEDIUM and LIGHT aircraft. Figure 49 — Operating directly behind Figure 50 — Crossing behind TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 147 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM1 ATS.TR.220 Application of wake turbulence separation WAKE TURBULENCE EFFECTS INDUCED BY HELICOPTERS (a) Helicopters should be kept well clear off light aircraft when hovering or while air taxiing. (b) Helicopters produce vortices when in flight and there is some evidence that, per kilogram of gross mass, their vortices are more intense than those of fixed-wing aircraft. (From PANS ATM — Sections 4.9.1.2 and 4.9.1.2 (Note 1 to Section)) AMC1 ATS.TR.230 Transfer of responsibility for control COORDINATION IN RESPECT OF THE PROVISION OF ATC SERVICE — GENERAL Agreements between ATC units or sectors and local instructions concerning coordination and transfer of control of flights should cover the following, as applicable: (a) definition of areas of responsibility and common interest, airspace structure and airspace classification(s); (b) any delegation of responsibility for the provision of ATS; (c) procedures for the exchange of flight plan and control data, including use of automated and/or verbal coordination messages; (d) means of communication; (e) requirements and procedures for approval requests; (f) significant points, levels or times for transfer of control; (g) significant points, levels or times for transfer of communication; (h) conditions applicable to the transfer and acceptance of control, such as specified altitudes/flight levels, specific separation minima or spacing to be established at the time of transfer, and the use of automation; (i) ATS surveillance system coordination procedures; (j) SSR code assignment procedures; (k) procedures for departing traffic; (l) designated holding fixes and procedures for arriving traffic; (m) applicable contingency procedures; and (n) any other provisions or information relevant to the coordination and transfer of control of flights. (PANS ATM — Section 10.1.1.3) GM1 ATS.TR.230 Transfer of responsibility for control COORDINATION IN RESPECT OF THE PROVISION OF ATC SERVICE — GENERAL (a) The coordination and transfer of control of a flight between successive ATC units and control sectors should be effected by a dialogue comprising the following stages: (1) notification of the flight in order to prepare for coordination, as necessary; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 148 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (2) coordination of conditions of transfer of control by the transferring ATC unit; (3) coordination, if necessary, and acceptance of conditions of transfer of control by the accepting ATC unit; and (4) the transfer of control to the accepting ATC unit or control sector. (b) ATC units should, to the extent possible, establish and apply standardised procedures for the coordination and transfer of control of flights, in order, inter alia, to reduce the need for verbal coordination. Such coordination procedures should be specified in letters of agreement and local instructions, as applicable. (PANS ATM — Sections 10.1.1.1 and 10.1.1.2) GM2 ATS.TR.230 Transfer of responsibility for control LETTERS OF AGREEMENT AND OPERATION MANUALS Relevant information contained in letters of agreement should be included in the operation manual of the ATS units concerned. AMC1 ATS.TR.230(a) Transfer of responsibility for control COORDINATION BETWEEN ATC UNITS PROVIDING AIR TRAFFIC SERVICE WITHIN CONTIGUOUS CONTROL AREAS — TRANSFER OF CONTROL (a) The responsibility for the control of an aircraft should be transferred from the ATC unit to the next unit at the time of crossing the common control area boundary as determined by the unit having control of the aircraft or at such other point or time as has been agreed between the two units. (b) Where specified in letters of agreement between the ATC units concerned, and when transferring an aircraft, the transferring unit should notify the accepting unit that the aircraft is in position to be transferred, and specify that the responsibility for control should be assumed by the accepting unit forthwith at the time of crossing the control boundary or other transfer control point specified in letters of agreement between the ATC units or at such other point or time coordinated between the two units. (c) If the transfer of control time or point is other than forthwith, the accepting ATC unit should not alter the clearance of the aircraft prior to the agreed transfer of control time or point without the approval of the transferring unit. (d) If transfer of communication is used to transfer an aircraft to a receiving ATC unit, responsibility for control should not be assumed until the time of crossing the control area boundary or other transfer of control point specified in letters of agreement between the ATC units. (PANS ATM — Sections 10.1.2.2.1, 10.1.2.2.2, 10.1.2.2.3 and 10.1.2.2.4) GM1 ATS.TR.230(a)(2) Transfer of responsibility for control DIVISION OF CONTROL BETWEEN A UNIT PROVIDING AREA CONTROL SERVICE AND A UNIT PROVIDING APPROACH CONTROL SERVICE (a) Except when otherwise specified in letters of agreement or local instructions, or by the ACC concerned in individual cases, a unit providing approach control service may issue clearances to TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 149 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments any aircraft released to it by an ACC without reference to the ACC. However, when an approach has been missed the ACC should, if affected by the missed approach, be advised immediately and subsequent action should be coordinated between the ACC and the unit providing approach control service as necessary. (b) An ACC may, after coordination with the unit providing approach control service, release aircraft directly to aerodrome control towers if the entire approach will be made under visual meteorological conditions. (PANS ATM — Sections 10.1.3.1.1 and 10.1.3.1.2) GM1 ATS.TR.230(a)(3) Transfer of responsibility for control DIVISION OF CONTROL BETWEEN A UNIT PROVIDING APPROACH CONTROL SERVICE AND A UNIT PROVIDING AERODROME CONTROL SERVICE (a) A unit providing approach control service should retain control of arriving aircraft until such aircraft have been transferred to the aerodrome control tower and are in communication with the aerodrome control tower. Letters of agreement or local instructions, appropriate to the airspace structure, terrain, meteorological conditions and ATS facilities available, should establish rules for the transfer of arriving aircraft. (b) A unit providing approach control service may authorise an aerodrome control tower to release an aircraft for take-off subject to the discretion of the aerodrome control tower with respect to arriving aircraft. (c) Aerodrome control towers should, when so prescribed in letters of agreement or local instructions, obtain approval from the unit providing approach control service prior to authorising operation of special VFR flights. (PANS ATM — Sections 10.1.4.1.1, 10.1.4.1.2 and 10.1.4.1.3) GM2 ATS.TR.230(a)(3) Transfer of responsibility for control TRANSFER OF FLIGHTS BETWEEN AREA CONTROL CENTRE AND AERODROME CONTROL TOWER Even though there is an approach control unit, control of certain flights may be transferred directly from an area control centre (ACC) to an aerodrome control tower and vice versa, by prior arrangement between the units concerned for the relevant part of approach control service to be provided by the ACC or the aerodrome control tower, as applicable. (Annex 11 — Note to Section 3.6.1.3.1 and 3.6.1.3.2) GM1 ATS.TR.230(a)(3)(i) Transfer of responsibility for control COORDINATION OF STANDARD CLEARANCES FOR ARRIVING AIRCRAFT (a) Wherever possible, the ATS providers concerned should establish standardised procedures for transfer of control between the ATC units concerned and standard clearances for arriving aircraft. (b) Where standard clearances for arriving aircraft are in use and, provided no terminal delay is expected, clearance to follow the appropriate STAR will normally be issued by the ACC without TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 150 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments prior coordination with or approval from the approach control unit or the aerodrome control tower as applicable. (c) Prior coordination of clearances should be required only in the event that a variation to the standard clearance or the standardised transfer of control procedures is necessary or desirable for operational reasons. (d) Provision should be made to: (1) ensure that the approach control unit is at all times kept informed of the sequence of aircraft following the same STAR; and (2) display the designators of assigned STARs to the ACC, the approach control unit and/or the aerodrome control tower, as applicable. (PANS ATM — Sections 6.5.2.1, 6.5.2.2.1, 6.5.2.2.2, 6.5.2.2.3 and 6.5.2.2.4) GM1 ATS.TR.230(a)(1)(ii) Transfer of responsibility for control COORDINATION OF STANDARD CLEARANCES FOR DEPARTING AIRCRAFT (a) Wherever possible, the ATS providers concerned should establish standardised procedures for transfer of control between the ATC units concerned and standard clearances for departing aircraft. (b) Where standard clearances for departing aircraft have been agreed to between the units concerned, the aerodrome control tower will normally issue the appropriate standard clearance without prior coordination with or approval from the approach control unit or ACC. (c) Prior coordination of clearances should be required only in the event that a variation to the standard clearance or the standardised transfer of control procedures is necessary or desirable for operational reasons. (d) Provision should be made to: (1) ensure that the approach control unit at all times is kept informed of the sequence in which aircraft will depart as well as the runway to be used; and (2) display the designators of assigned SIDs to the aerodrome control tower, the approach control unit and/or the ACC as applicable. (PANS ATM — Sections 6.3.2.1, 6.3.2.2.1, 6.3.2.2.2, 6.3.2.2.3 and 6.3.2.2.4) AMC1 ATS.TR.230(a)(4) Transfer of responsibility for control COORDINATION BETWEEN CONTROL POSITIONS WITHIN THE SAME UNIT Appropriate flight plan and control information should be exchanged between control positions within the same ATC unit, in respect of: (a) all aircraft for which responsibility for control will be transferred from one control position to another; (b) aircraft operating in such close proximity to the boundary between control sectors that control of traffic within an adjacent sector may be affected; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 151 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (c) all aircraft for which responsibility for control has been delegated by a controller using procedural methods to a controller using an ATS surveillance system, as well as other aircraft affected. (PANS ATM — Section 10.1.5.1) AMC1 ATS.TR.230(b)(2) Transfer of responsibility for control COORDINATION BETWEEN ATC UNITS PROVIDING ATS WITHIN CONTIGUOUS CONTROL AREAS — GENERAL (a) ATC units should forward from unit to unit, as the flight progresses, necessary flight plan and control information. When so required by agreement between ATS providers concerned, flight plan and flight progress information for flights along specified routes or portions of routes in close proximity to flight information region boundaries should also be provided to the ATC units in charge of the flight information regions adjacent to such routes or portions of routes. (b) The flight plan and control information in point (b) of ATS.TR.230 should be transmitted in sufficient time to permit reception and analysis of the data by the receiving unit(s) and necessary coordination between the units concerned. (PANS ATM — Sections 10.1.2.1.1 and 10.1.2.1.2) AMC2 ATS.TR.230(b)(2) Transfer of responsibility for control EXCHANGE OF MOVEMENT AND CONTROL DATA BETWEEN A UNIT PROVIDING AREA CONTROL SERVICE AND A UNIT PROVIDING APPROACH CONTROL SERVICE (a) The unit providing approach control service should keep the ACC promptly advised of pertinent data on controlled traffic. (b) The ACC should keep the unit providing approach control service promptly advised of pertinent data on controlled traffic. (c) The ACC should normally forward to the unit providing approach control service information on arriving aircraft not less than 15 minutes before estimated time of arrival and should revise such information as necessary. (PANS ATM — Sections 10.1.3.3.1 (first sentence), 10.1.3.3.2 and 10.1.3.3.3) GM1 to AMC2 ATS.TR.230(b)(2) Transfer of responsibility for control EXCHANGE OF MOVEMENT AND CONTROL DATA FROM A UNIT PROVIDING APPROACH CONTROL SERVICE TO A UNIT PROVIDING AREA CONTROL SERVICE Pertinent data on controlled traffic should include: (a) runway(s) in use and expected type of instrument approach procedure; (b) lowest vacant level at the holding fix available for use by the ACC; (c) average time interval or distance between successive arrivals as determined by the unit providing approach control service; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 152 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (d) revision of the expected approach time issued by the ACC when the calculation of the expected approach time by the unit providing approach control service indicates a variation of 5 minutes or such other time as has been agreed between the two ATC units concerned; (e) arrival times over the holding fix when these vary by 3 minutes, or such other time as has been agreed between the two ATC units concerned, from those previously estimated; (f) cancellations by aircraft of IFR flight if these will affect levels at the holding fix or expected approach times of other aircraft; (g) aircraft departure times or, if agreed between the two ATC units concerned, the estimated time at the control area boundary or other specified point; (h) all available information relating to overdue or unreported aircraft; and (i) missed approaches which may affect the ACC. (PANS ATM — Section 10.1.3.3.1 (second sentence)) GM2 to AMC2 ATS.TR.230(b)(2) Transfer of responsibility for control EXCHANGE OF MOVEMENT AND CONTROL DATA FROM A UNIT PROVIDING AREA CONTROL SERVICE TO A UNIT PROVIDING APPROACH CONTROL SERVICE Pertinent data on controlled traffic should include: (a) identification, type and point of departure of arriving aircraft; (b) estimated time and proposed level of arriving aircraft over holding fix or other specified point; (c) actual time and proposed level of arriving aircraft over holding fix if aircraft is released to the unit providing approach control service after arrival over the holding fix; (d) requested type of IFR approach procedure if different from that specified by the approach control unit; (e) expected approach time issued; (f) when required, statement that aircraft has been instructed to contact the unit providing approach control service; (g) when required, statement that an aircraft has been released to the unit providing approach control service including, if necessary, the time and conditions of release; and (h) anticipated delay to departing traffic due to congestion. (PANS ATM — Section 10.1.3.3.2 (second sentence)) AMC3 ATS.TR.230(b)(2) Transfer of responsibility for control EXCHANGE OF MOVEMENT AND CONTROL DATA BETWEEN A UNIT PROVIDING APPROACH CONTROL SERVICE AND A UNIT PROVIDING AERODROME CONTROL SERVICE (a) An aerodrome control tower should keep the unit providing approach control service promptly advised of pertinent data on relevant controlled traffic. (b) The unit providing approach control service should keep the aerodrome control tower promptly advised of pertinent data on controlled traffic. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 153 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (PANS ATM — Sections 10.1.4.2.1 (first sentence) and 10.1.4.2.2 (first sentence)) GM1 to AMC3 ATS.TR.230(b)(2) Transfer of responsibility for control EXCHANGE OF MOVEMENT AND CONTROL DATA FROM AN AERODROME CONTROL TOWER TO A UNIT PROVIDING APPROACH CONTROL SERVICE Pertinent data on controlled traffic should include: (a) arrival and departure times; (b) when required, statement that the first aircraft in an approach sequence is in communication with and is sighted by the aerodrome control tower, and that reasonable assurance exists that a landing can be accomplished; (c) all available information relating to overdue or unreported aircraft; (d) information concerning missed approaches; and (e) information concerning aircraft that constitute essential local traffic to aircraft under the control of the unit providing approach control service. (PANS ATM — Section 10.1.4.2.1 (second sentence)) GM2 to AMC3 ATS.TR.230(b)(2) Transfer of responsibility for control EXCHANGE OF MOVEMENT AND CONTROL DATA FROM A UNIT PROVIDING APPROACH CONTROL SERVICE TO AN AERODROME CONTROL TOWER Pertinent data on controlled traffic should include: (a) estimated time and proposed level of arriving aircraft over the aerodrome, at least 15 minutes prior to estimated arrival; (b) when required, a statement that an aircraft has been instructed to contact the aerodrome control tower and that control shall be assumed by that unit; and (c) anticipated delay to departing traffic due to congestion. (PANS ATM — Section 10.1.4.2.2 (second sentence)) GM1 ATS.TR.230(b)(2) Transfer of responsibility for control COORDINATION BETWEEN ATC UNITS FOR APPROVAL REQUESTS (a) If the flying time from the departure aerodrome of an aircraft to the boundary of an adjacent control area is less than the specified minimum required to permit transmission of the necessary flight plan and control information to the accepting ATC unit after take-off and allow adequate time for reception, analysis and coordination, the transferring ATC unit should, prior to departure, forward that information to the accepting ATC unit together with a request for approval. The required time period should be specified in letters of agreement or local instructions, as appropriate. In the case of revisions to a previously transmitted current flight plan, and control data being transmitted earlier than this specified time period, no approval from the accepting ATC unit should be required. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 154 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (b) In the case of an aircraft in flight requiring an initial clearance when the flying time to the boundary of an adjacent control area is less than a specified minimum, the aircraft should be held within the transferring ATC unit’s control area until the flight plan and control information have been forwarded together with a request for approval, and coordination effected with the adjacent ATC unit. (c) In the case of an aircraft requesting a change in its current flight plan, or of a transferring ATC unit proposing to change the current flight plan of an aircraft, and the flying time of the aircraft to the control area boundary is less than a specified minimum, the revised clearance should be withheld pending approval of the proposal by the adjacent ATC unit. (d) When boundary estimate data are to be transmitted for approval by the accepting unit, the time in respect of an aircraft not yet departed should be based upon the estimated time of departure as determined by the ATC unit in whose area of responsibility the departure aerodrome is located. In respect of an aircraft in flight requiring an initial clearance, the time should be based on the estimated elapsed time from the holding fix to the boundary plus the time expected to be needed for coordination. (PANS ATM — Sections 10.1.2.3.1, 10.1.2.3.2, 10.1.2.3.3, and 10.1.2.3.4) GM2 ATS.TR.230(b)(2) Transfer of responsibility for control COORDINATION BETWEEN ATC UNITS FOR TAKE-OFF AND CLEARANCE EXPIRY TIMES (a) Time of take-off should be specified by the ACC when it is necessary to: (1) coordinate the departure with traffic not released to the unit providing approach control service; and (2) provide en-route separation between departing aircraft following the same track. (b) If time of take-off is not specified, the unit providing approach control service should determine the take-off time when necessary to coordinate the departure with traffic released to it. (c) A clearance expiry time should be specified by the ACC if a delayed departure would conflict with traffic not released to the unit providing approach control service. If, for traffic reasons of its own, a unit providing approach control service has to specify in addition its own clearance expiry time, this should not be later than that specified by the ACC. (PANS ATM — Sections 10.1.3.2.1, 10.1.3.2.2 and 10.1.3.2.3) GM3 ATS.TR.230(b)(2) Transfer of responsibility for control COORDINATION BETWEEN ATS UNITS FOR CHANGE FROM IFR TO VFR An ATC unit receiving notification of an aircraft’s intention to change from IFR to VFR flight should, as soon as practicable thereafter, so inform all other ATS units to whom the IFR flight plan was addressed, except those units through whose regions or areas the flight has already passed. (PANS ATM — Section 4.8.4) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 155 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC1 ATS.TR.230(b)(7) Transfer of responsibility for control PHRASEOLOGIES TO BE USED IN THE COORDINATION BETWEEN ATS UNITS The following phraseology should be used in the coordination between ATS units or sectors: TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 156 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 157 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (PANS ATM — Section 12.3.5) GM1 ATS.TR.235 ATC clearances The issuance of air traffic control clearances by air traffic control units constitutes authority for an aircraft to proceed only in so far as known air traffic is concerned. ATC clearances do not constitute authority to violate any applicable regulations for promoting the safety of flight operations or for any other purpose; neither do clearances relieve a pilot-in-command of any responsibility whatsoever in connection with a possible violation of applicable rules and regulations. (PANS ATM Section 4.5.1.3) GM1 ATS.TR.235(a)(5) ATC clearances ASSURANCE OF OBSTACLE CLEARANCE IN VECTORING Prescribed obstacle clearance will exist at all times when controller issues clearances at or above the established minimum flight altitudes. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 158 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments When an IFR flight is being vectored, the pilot may be unable to determine the aircraft’s exact position in respect of obstacles in this area and consequently the altitude which provides the required obstacle clearance. (PANS ATM — Note 1 to Section 8.6.5.2, EANPG 57 Final Report) AMC1 ATS.TR.235(b) ATC clearances CONTENT OF CLEARANCES FOR DEPARTING AIRCRAFT Clearances for departing aircraft should specify, when necessary for the separation of aircraft: (a) direction of take-off and turn after take-off; (b) heading or track to be made good before taking up the cleared departure track; (c) level to maintain before continuing climb to assigned level; (d) time, point and/or rate at which a level change shall be made; and (e) any other necessary manoeuvre consistent with safe operation of the aircraft. (PANS ATM — Section 6.3.1.1) GM1 to AMC1 ATS.TR.235(b) ATC clearances CORRECTION TO HEADING OR TRACK PRIOR TO TAKING UP THE CLEARED DEPARTURE TRACK ‘Track to be made good’ means that the pilot should correct for the wind effect and to fly a heading that would ensure keeping that track. AMC2 ATS.TR.235(b) ATC clearances CONTENTS OF STANDARD CLEARANCES FOR DEPARTING AIRCRAFT Standard clearances for departing aircraft should contain the following items: (a) aircraft identification; (b) clearance limit, normally destination aerodrome; (c) designator of the assigned standard instrument departure (SID), if applicable; (d) cleared level; (e) allocated SSR code; and (f) any other necessary instructions or information not contained in the SID description, e.g. instructions relating to change of frequency. (PANS ATM — Section 6.3.2.3) GM1 to AMC2 ATS.TR.235(b) ATC clearances CONTENTS OF STANDARD CLEARANCES FOR DEPARTING AIRCRAFT — COMMUNICATION FAILURE (a) Clearances for departing aircraft may specify a cleared level other than that indicated in the filed flight plan for the en-route phase of flight, without a time or geographical limit for the cleared level. Such clearances will normally be used to facilitate the application of tactical control methods by ATC, normally through the use of an ATS surveillance system. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 159 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (b) Where clearances for departing aircraft which contain no time or geographical limit for a cleared level are utilised, the action to be taken by an aircraft experiencing air–ground communication failure in the event that the aircraft has been radar-vectored away from the route specified in its current flight plan, should be prescribed on the basis of a regional air navigation agreement and included in the SID description or published in AIPs. (PANS ATM — Sections 6.3.2.5.1 and 6.3.2.5.2) AMC3 ATS.TR.235(b) ATC clearances CLEARANCES FOR ARRIVING IFR FLIGHTS An IFR flight should neither be cleared for an initial approach below the appropriate minimum altitude as specified by the State concerned nor descend below that altitude unless: (a) the pilot has reported passing an appropriate point defined by a navigation aid or as a waypoint; or (b) the pilot reports that the aerodrome is and can be maintained in sight; or (c) the aircraft is conducting a visual approach; or (d) the controller has determined the aircraft’s position by the use of an ATS surveillance system, and a lower minimum altitude has been specified for use when providing ATS surveillance services. (PANS ATM — Section 6.5.1.3) AMC4 ATS.TR.235(b) ATC clearances CONTENTS OF STANDARD CLEARANCES FOR ARRIVING AIRCRAFT Standard clearances for arriving aircraft should contain the following items: (a) aircraft identification; (b) designator of the assigned STAR if applicable; (c) runway in use, except when part of the STAR description; (d) cleared level; and (e) any other necessary instructions or information not contained in the STAR description, e.g. change of communications. (PANS ATM — Section 6.5.2.3) AMC1 ATS.TR.235(b)(2) ATC clearances SPECIFICATION OF CLEARANCE LIMIT A clearance limit should be described by specifying the name of an appropriate significant point, or aerodrome, or controlled airspace boundary. (PANS ATM — Section 4.5.7.1.1) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 160 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM1 to AMC1 ATS.TR.235(b)(2) ATC clearances SPECIFICATION OF CLEARANCE LIMIT (a) When prior coordination has been effected with units under whose control the aircraft will subsequently come, or if there is reasonable assurance that it can be effected a reasonable time prior to their assumption of control, the clearance limit should be the destination aerodrome or, if not practicable, an appropriate intermediate point, and coordination should be expedited so that a clearance to the destination aerodrome may be issued as soon as possible. (b) If an aircraft has been cleared to an intermediate point in adjacent controlled airspace, the appropriate ATC unit will then be responsible for issuing, as soon as practicable, an amended clearance to the destination aerodrome. (c) When the destination aerodrome is outside controlled airspace, the ATC unit responsible for the last controlled airspace through which an aircraft will pass should issue the appropriate clearance for flight to the limit of that controlled airspace. (PANS ATM — Sections 4.5.7.1.2, 4.5.7.1.3 and 4.5.7.1.4) GM1 ATS.TR.235(b)(3)(i) ATC clearances The phrase ‘cleared flight planned route’ may be used to describe any route or portion thereof, provided the route or portion thereof is identical to that filed in the flight plan and sufficient routing details are given to definitely establish the aircraft on its route. The phrases ‘cleared (designation) departure’ or ‘cleared (designation) arrival’ may be used when standard departure or arrival routes have been established and published in AIPs. (PANS ATM — Sections 4.5.7.2.1 (Second and third sentences)) AMC1 ATS.TR.235(b)(4) ATC clearances INSTRUCTIONS IN CLEARANCES RELATING TO LEVELS Instructions included in clearances relating to levels should consist of: (a) cruising level(s) or, for cruise climb, a range of levels, and, if necessary, the point to which the clearance is valid with regard to the level(s); (b) levels at which specified significant points are to be crossed, when necessary; (c) the place or time for starting climb or descent, when necessary; (d) the rate of climb or descent, when necessary; and (e) detailed instructions concerning departure or approach levels, when necessary. (PANS ATM — Section 11.4.2.6.2.2) GM1 ATS.TR.235(b)(4) ATC clearances ASSIGNMENT OF FLIGHT LEVELS FOR CONTROLLED FLIGHTS (a) Except when traffic conditions and coordination procedures permit authorisation of cruise climb, an ATC unit should normally authorise only one level for an aircraft beyond its control area, i.e. that level at which the aircraft will enter the next control area whether contiguous or not. It is TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 161 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments the responsibility of the accepting ATC unit to issue clearance for further climb as appropriate. When relevant, aircraft will be advised to request en-route any cruising level changes desired. (b) In so far as practicable, cruising levels of aircraft flying to the same destination should be assigned in a manner that will be correct for an approach sequence at destination. (c) An aircraft at a cruising level should normally have priority over other aircraft requesting that cruising level. When two or more aircraft are at the same cruising level, the preceding aircraft should normally have priority. (PANS ATM — Sections 5.3.3.1, 5.3.3.6 and 5.3.3.7) GM1 ATS.TR.235(b)(5) ATC clearances CONTENT OF THE CLEARANCES — TIME OF EXPIRY The time of expiry of the clearance indicates the time after which the clearance will be automatically cancelled if the flight has not been commenced. (Annex 11 — Note to Section 3.7.1.1(e)) (Said Note has been transposed as GM1 SERA.8015(d)(5)) GM1 ATS.TR.235(c) ATC clearances ESTABLISHMENT AND PROCEDURES FOR STANDARD ARRIVAL AND DEPARTURE ROUTES Guidance related to the establishment of standard departure and arrival routes and associated procedures is available in ICAO Doc 9426 (Chapter 4, Appendix A). (Annex 11 Note to Section 3.7.1.2(b)) AMC1 ATS.TR.235(d) ATC clearances CLEARANCES FOR TRANSONIC FLIGHT (a) The ATC units should, whenever practicable, deliver clearance for the transonic acceleration phase to aircraft intending supersonic flight prior to departure. (b) During the transonic and supersonic phases of a flight, amendments to the clearance should be kept to a minimum and should take due account of the operational limitations of the aircraft in these flight phases. (PANS ATM — Sections 4.5.6.2.1 and 4.5.6.2.2) GM1 ATS.TR.235(e) ATC clearances CHANGE IN CLEARANCE REGARDING ROUTE The nature of the change should include a description of the route and levels to the point where it joins the previously cleared route, or, if the aircraft will not re-join the previous route, to the destination. (PANS ATM — Section 4.5.7.4.3) (Section 4.5.7.4.3 also transposed as GM to SERA.8015(e)(1)) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 162 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM2 ATS.TR.235(e) ATC clearances CHANGE IN CLEARANCE REGARDING CRUISING LEVEL If it is necessary to change the cruising level of an aircraft operating along an established ATS route extending partly within and partly outside controlled airspace and where the respective series of cruising levels are not identical, the change should, whenever possible, be effected within controlled airspace. (PANS ATM — Section 5.3.3.3) GM1 ATS.TR.235(g)(2) ATC clearances READ-BACK OF CPDLC MESSAGES When so indicated by local safety assessments, the ATS provider may require that the receipt of some of the CPDLC message types (in particular those addressing trajectory changes) be acknowledged by voice. (GM1 SERA.8015(e)(4)) GM1 ATS.TR.235(h)(1) ATC clearances CLEARANCE UPDATE Where a clearance is issued covering the initial part of the flight solely as a means of expediting departing traffic, the succeeding en-route clearance will be as specified in point (h)(1) of ATS.TR.235 even though the aerodrome of first intended landing is under the jurisdiction of an ACC other than the one issuing the en-route clearance. (Annex 11 — Note to Section 3.7.4.1) GM1 ATS.TR.235(h)(2)(i) ATC clearances AIR–GROUND COMMUNICATION FOR DELIVERY OF DOWNSTREAM CLEARANCES Where practicable, and where data link communications are used to facilitate downstream clearance delivery, two-way voice communications between the pilot and the ATC unit providing the downstream clearance should be available. (Annex 11 — Section 3.7.4.2.1.4) AMC1 ATS.TR.240(a) Control of persons and vehicles at controlled aerodromes CONTROL OF OTHER THAN AIRCRAFT TRAFFIC ON THE MANOEUVRING AREA (a) The movement of pedestrians or vehicles on the manoeuvring area should be subject to authorisation by the aerodrome control tower. Persons, including drivers of all vehicles, should be required to obtain authorisation from the aerodrome control tower before entry to the manoeuvring area. Notwithstanding such an authorisation, entry to a runway or runway strip or change in the operation authorised should be subject to a further specific authorisation by the aerodrome control tower. (b) When an aircraft is landing or taking off, the controller should not permit vehicles to hold closer to the runway in use than: (1) at a taxiway/runway intersection — at a runway-holding position; and TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 163 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (2) at a location other than a taxiway/runway intersection — at a distance equal to the separation distance of the runway-holding position. (PANS ATM — Sections 7.6.3.2.1 and 7.6.3.2.2.2) AMC2 ATS.TR.240(a) Control of persons and vehicles at controlled aerodromes UNCERTAINTY ON AIRCRAFT AND/OR VEHICLES POSITION ON THE MANOEUVRING AREA In the event that the aerodrome controller becomes aware of an aircraft or vehicle that is lost or uncertain of its position on the manoeuvring area, he or she should immediately take appropriate action to safeguard operations and assist the aircraft or vehicle concerned to determine its position. (PANS ATM — Section 7.4.1.5.4) GM1 ATS.TR.240(b)(2) Control of persons and vehicles at controlled aerodromes CONTROL OF PERSONS AND VEHICLES AT AERODROMES In prescribing the minimum separation between vehicles and taxiing aircraft, the availability of lighting, markings, signals and signage should normally be taken into account. (GM1 SERA.3210(d)(4)(ii)(B) Right-of-way) GM1 ATS.TR.240(c) Control of persons and vehicles at controlled aerodromes PRIORITY TO EMERGENCY VEHICLES When emergency vehicles are proceeding to the assistance of an aircraft in distress, all other movement of surface traffic should, to the extent practicable, be halted until it is determined that the progress of the emergency vehicles will not be impeded. (PANS ATM — Section 7.6.3.2.2.1) GM1 ATS.TR.245 Use of surface movement surveillance equipment at aerodromes FUNCTIONS OF SURFACE MOVEMENT RADAR IN SURFACE MOVEMENT CONTROL The information displayed on an SMR display may be used to assist in: (a) monitoring of aircraft and vehicles on the manoeuvring area for compliance with clearances and instructions; (b) determining that a runway is clear of traffic prior to a landing or take-off; (c) providing information on essential local traffic on or near the manoeuvring area; (d) determining the location of aircraft and vehicles on the manoeuvring area; (e) providing directional taxi information to aircraft when requested by the pilot or deemed necessary by the controller. Except under special circumstances, e.g. emergencies, such information should not be issued in the form of specific heading instructions; and (f) providing assistance and advice to emergency vehicles. (PANS ATM — Section 8.10.2.2.2) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 164 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM2 ATS.TR.245 Use of surface movement surveillance equipment at aerodromes FUNCTIONS OF ADVANCED SURFACE MOVEMENT GUIDANCE AND CONTROL SYSTEMS — A-SMGCS IN SURFACE MOVEMENT CONTROL When authorised and subject to conditions prescribed by the competent authority, the information provided on an A-SMGCS display may be used for the purpose of: (a) determining the location of aircraft on the movement area and vehicles on the manoeuvring area. Where visual observation by the aerodrome controller is not possible, or whenever deemed beneficial by the aerodrome controller, the information provided by A-SMGCS may be used to replace visual observation; (b) monitoring aircraft and vehicles on the manoeuvring area for compliance with clearances and instructions; (c) determining that a runway is clear of traffic or assisting in the assessment that a runway will be clear of traffic prior to a landing or take-off; (d) providing information on essential local traffic on or near the manoeuvring area; (e) providing directional taxi information to aircraft when requested by the pilot or deemed necessary by the controller. Such information should not be issued in the form of specific heading instructions (except in special circumstances, e.g. emergencies); and (f) providing assistance and advice to emergency vehicles. (Doc 7030 EUR — Section 6.5.6.2) AMC1 ATS.TR.250(a) Essential traffic information ESSENTIAL TRAFFIC INFORMATION — CONTENT Essential traffic information should include the following information if relevant and available: (a) direction of flight of aircraft concerned; (b) type and wake turbulence category of aircraft concerned; (c) cruising level of aircraft concerned; and (d) one of the following: (1) estimated time over the reporting point nearest to where the level will be crossed; or (2) relative bearing of the aircraft concerned in terms of the 12-hour clock as well as distance from the conflicting traffic; or (3) actual or estimated position of the aircraft concerned. (PANS ATM — Section 5.10.2) GM1 ATS.TR.250(a) Essential traffic information ESSENTIAL TRAFFIC INFORMATION — CONTENT (a) Essential traffic is that controlled traffic to which the provision of separation by ATC is applicable, but which, in relation to a particular controlled flight is not, or will not be, separated from other controlled traffic by the appropriate separation minimum. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 165 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (b) Subject to provisions in ATS.TR.210(b), ATC is required to provide separation between IFR flights in airspace Classes A to E, and between IFR and VFR flights in Classes B and C. ATC is not required to provide separation between VFR flights, except within airspace Class B. Therefore, IFR or VFR flights may constitute essential traffic to IFR traffic, and IFR flights may constitute essential traffic to VFR traffic. However, a VFR flight would not constitute essential traffic to other VFR flights except within Class B airspace. (PANS ATM — Section 5.10.1.1 and Note to Section 5.10.1.1) AMC1 ATS.TR.250(b) Essential traffic information ESSENTIAL LOCAL TRAFFIC INFORMATION (a) The relevant ATC unit should issue in a timely manner information on essential local traffic, either directly or through the unit providing approach control service when, in the judgement of the aerodrome controller, such information is necessary in the interests of safety, or when requested by aircraft. (b) The relevant ATC unit should describe essential local traffic so as to be easily identified. (PANS ATM — Sections 7.4.1.3.1 and 7.4.1.3.3) GM1 ATS.TR.250(b) Essential traffic information ESSENTIAL LOCAL TRAFFIC INFORMATION Essential local traffic should be considered to consist of any aircraft, vehicle or personnel on or near the manoeuvring area, or traffic in the take-off and climb-out area or the final approach area, which may constitute a hazard to the aircraft concerned. (PANS ATM — Note to Section 6.2.1) AMC1 ATS.TR.255 Operations on parallel or near-parallel runways REQUIREMENTS AND PROCEDURES FOR INDEPENDENT PARALLEL DEPARTURES (a) Parallel runways may be used for independent instrument departures as follows: (1) both runways are used exclusively for departures (independent departures); or (2) one runway is used exclusively for departures while the other runway is used for a mixture of arrivals and departures (semi-mixed operation); or (3) both runways are used for mixed arrivals and departures (mixed operation). (b) Independent instrument departures should only be conducted from parallel runways where: (1) the runway centre lines are spaced by the distance specified in CS ADR-DSN.B.055 ‘Minimum distance between parallel instrument runways’ in EASA ED Decision 2014/013/R ‘Certification Specifications and Guidance Material For Aerodromes Design’, as amended; (2) the departure tracks diverge by at least 15 degrees immediately after take-off; (3) ATS surveillance system capable of identifying the aircraft within 2 km (1.0 NM) from the end of the runway is available; and TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 166 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (4) ATS operational procedures ensure that the required track divergence is achieved. (PANS ATM — Sections 6.7.2.1 and 6.7.2.2) AMC2 ATS.TR.255 Operations on parallel or near-parallel runways REQUIREMENTS AND PROCEDURES FOR INDEPENDENT PARALLEL APPROACHES (a) Whenever parallel approaches are carried out, separate controllers should be responsible for the sequencing and spacing of arriving aircraft to each runway. (b) Independent parallel approaches should only be conducted to parallel runways where: (1) the runway centre lines are spaced by the distance specified in CS ADR-DSN.B.055 ‘Minimum distance between parallel instrument runways’ in EASA ED Decision 2014/013/R ‘Certification Specifications and Guidance Material For Aerodromes Design’, as amended; (i) where runway centre lines are spaced by less than 1 310 m but not less than 1 035 m, suitable SSR equipment, with a minimum azimuth accuracy of 0.06 degrees (one sigma), an update period of 2.5 seconds or less, and a high resolution display providing position prediction and deviation alert is available; or (ii) where runway centre lines are spaced by less than 1 525 m but not less than 1 310 m, SSR equipment with performance specifications other than the foregoing may be applied, provided they are equal to or better than those stated under point (iii) below, and when it is determined that the safety of aircraft operation would not be adversely affected; or (iii) where runway centre lines are spaced by 1 525 m or more, suitable surveillance radar with a minimum azimuth accuracy of 0.3 degrees (one sigma) or better and update period of 5 seconds or less is available; (2) as early as practicable after an aircraft has established communication with approach control, the aircraft is advised that independent parallel approaches are in force; (3) instrument landing system (ILS) and/or microwave landing system (MLS) approaches are being conducted on both runways; (4) the missed approach track for one approach diverges by at least 30 degrees from the missed approach track of the adjacent approach; (5) an obstacle survey and evaluation is completed, as appropriate, for the areas adjacent to the final approach segments; (6) aircraft are advised of the runway identification and ILS localiser or MLS frequency as early as possible; (7) vectoring is used to intercept the ILS localiser course or the MLS final approach track, at an angle not greater than 30 degrees and providing at least 2 km (1.0 NM) straight and level flight prior to the intercept. The vector should also enable the aircraft to be established on the ILS localiser course or MLS final approach track in level flight for at least 3.7 km (2.0 NM) prior to intercepting the ILS glide path or specified MLS elevation angle; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 167 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (8) a minimum of 300 m (1 000 ft) vertical separation or, subject to radar system and situation display capabilities, a minimum of 5.6 km (3.0 NM) radar separation is provided until aircraft are established: (i) inbound on the ILS localiser course and/or MLS final approach track; and (ii) within the normal operating zone (NOZ); (9) an NTZ at least 610 m (2 000 ft) wide is established equidistant between extended runway centre lines and is depicted on the situation display; (10) separate controllers use surveillance to monitor the approaches to each runway; (11) controller ensures that when the 300 m (1 000 ft) vertical separation is reduced: (i) aircraft do not penetrate the depicted NTZ; and (ii) the applicable minimum longitudinal separation between aircraft on the same ILS localiser course or MLS final approach track is maintained; and (12) flight path monitoring using surveillance is provided until: (i) visual separation is applied, and procedures ensure that both controllers are advised whenever visual separation is applied; (ii) the aircraft has landed, or in case of a missed approach, is at least 2 km (1.0 NM) beyond the departure end of the runway and adequate separation with any other traffic is established. (13) if no dedicated radio channels are available for the controllers to control the aircraft until landing: (i) transfer of communication of aircraft to the respective aerodrome controller’s channel is effected before the higher of two aircraft on adjacent final approach tracks intercepts the ILS glide path or the specified MLS elevation angle; and (ii) the controllers monitoring the approaches to each runway are provided with the capability to override transmissions of aerodrome control on the respective radio channels for each arrival flow. (c) The meteorological conditions under which the independent parallel approaches to parallel runways spaced by less than 1 525 m between their centre lines are to be suspended, should be proposed by the ATS provider and approved by the competent authority. These conditions include but are not limited to wind shear, turbulence, downdrafts, crosswind and significant meteorological conditions such as thunderstorms, which might otherwise increase ILS localiser course and/or MLS final approach track deviations to the extent that safety may be impaired. (PANS ATM — Sections 6.7.3.1.2, 6.7.3.2.1, 6.7.3.2.2 (first sentence), 6.7.3.2.3, 6.7.3.2.4, 6.7.3.2.10 and 6.7.3.3) GM1 to AMC2 ATS.TR.255 Operations on parallel or near-parallel runways With reference to point (b)(1) of AMC2 ATS.TR.255, other equivalent ATS surveillance systems (e.g. ADS-B or MLAT) may be used to provide the services, provided that a performance capability equal to or better than that required can be demonstrated. (PANS ATM — Section 6.7.3.2.1 (second sentence)) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 168 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM2 to AMC2 ATS.TR.255 Operations on parallel or near-parallel runways With reference to point (b)(2) of AMC2 ATS.TR.255, the information that independent parallel operations are in force may be provided through the ATIS broadcasts. (PANS ATM — Section 6.7.3.2.2 (second sentence)) GM3 to AMC2 ATS.TR.255 Operations on parallel or near-parallel runways This GM refers to provisions in points (b)(7) and (b)(8) of AMC2 ATS.TR.255. (a) When assigning the final heading to intercept the ILS localiser course or MLS final approach track, the runway will be confirmed, and the aircraft will be advised of: (1) its position relative to a fix on the ILS localiser course or MLS final approach track; (2) the altitude to be maintained until established on the ILS localiser course or MLS final approach track to the ILS glide path or specified MLS elevation angle intercept point; and (3) if required, clearance for the appropriate ILS or MLS approach. (b) When an aircraft is observed to overshoot the turn-on or to continue on a track which will penetrate the NTZ, the aircraft will be instructed to return immediately to the correct track. (c) When an aircraft is observed penetrating the NTZ, the aircraft on the adjacent ILS localiser course or MLS final approach track will be instructed to immediately climb and turn to the assigned altitude/height and heading in order to avoid the deviating aircraft. Where parallel approach obstacle assessment surfaces (PAOAS) criteria are applied for the obstacle assessment, the air traffic controller will not issue the heading instruction to the aircraft below 120 m (400 ft) above the runway threshold elevation, and the heading instruction will not exceed 45 degrees track difference with the ILS localiser course or MLS final approach track. (PANS ATM — Sections 6.7.3.2.6, 6.7.3.2.8 and 6.7.3.2.9) GM4 to AMC2 ATS.TR.255 Operations on parallel or near-parallel runways This GM refers to provisions in point (b)(8) of AMC2 ATS.TR.255. Subject to radar system and situation display capabilities, a minimum of 5.6 km (3.0 NM) radar separation as established in point (a) of AMC1 ATS.TR.210(c)(2), will be provided between aircraft on the same ILS localiser course or MLS final approach track unless increased longitudinal separation is required due to wake turbulence or for other reasons. An aircraft established on an ILS localiser course or MLS final approach track is separated from another aircraft established on an adjacent parallel ILS localiser course or MLS final approach track provided neither aircraft penetrates the NTZ as depicted on the situation display. (PANS ATM — Section 6.7.3.2.5 and Note 2 to Section 6.7.3.2.5) GM5 to AMC2 ATS.TR.255 Operations on parallel or near-parallel runways With reference to point (b)(10) of AMC2 ATS.TR.255, the primary responsibility for navigation on the ILS localiser course and /or MLS final approach track rests with the pilot. Control instructions and TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 169 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments appropriate information should be issued to ensure that separation between aircraft exists at all times and that aircraft do not enter the NTZ. (PANS ATM — Section 6.7.3.2.7 (second sentence) and Note 1 to Section 6.7.3.2.7) GM6 to AMC2 ATS.TR.255 Operations on parallel or near-parallel runways With reference to point (c) of AMC2 ATS.TR.255, guidance material relating to meteorological conditions is contained in the Manual on Simultaneous Operations on Parallel or Near-Parallel Instrument Runways (SOIR) (Doc 9643). (PANS ATM — Note 2 to Section 6.7.3.3) AMC3 ATS.TR.255 Operations on parallel or near-parallel runways REQUIREMENTS AND PROCEDURES FOR DEPENDENT PARALLEL APPROACHES (a) Dependent parallel approaches should only be conducted to parallel runways where: (1) the runway centre lines are spaced by the distance specified in CS ADR-DSN.B.055 ‘Minimum distance between parallel instrument runways’ in EASA ED Decision 2014/013/R ‘Certification Specifications and Guidance Material For Aerodromes Design’, as amended; (2) the aircraft are vectored to intercept the final approach track; (3) suitable surveillance radar with a minimum azimuth accuracy of 0.3 degrees (one sigma) and an update period of 5 seconds or less is available; (4) ILS and/or MLS approaches are being conducted on both runways; (5) aircraft are advised that approaches are in use to both runways; (6) the missed approach track for one approach diverges by at least 30 degrees from the missed approach track of the adjacent approach; and (7) approach control has a frequency override capability to aerodrome control. (b) A minimum of 300 m (1000ft) vertical separation or a minimum of 5.6km (3.0NM) surveillance separation should be provided between aircraft during turn-on to parallel ILS localiser courses and/or MLS final approach tracks. (c) The minimum surveillance separation to be provided between aircraft established on the ILS localiser course and/or MLS final approach track should be: (1) 5.6 km (3.0NM) between aircraft on the same ILS localiser course or MLS final approach track unless increased longitudinal separation is required due to wake turbulence; and (2) 3.7 km (2.0NM) between successive aircraft on adjacent ILS localiser courses or MLS final approach tracks. (PANS ATM — Sections 6.7.3.4.1, 6.7.3.4.2 and 6.7.3.4.3) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 170 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM1 to AMC3 ATS.TR.255 Operations on parallel or near-parallel runways With reference to point (a)(5) of AMC3 ATS.TR.255, the information that dependent parallel operations are in force may be provided through the ATIS broadcasts. (PANS ATM — Section 6.7.3.4.1 (paragraph (e))) GM2 to AMC3 ATS.TR.255Operations on parallel or near-parallel runways With reference to point (a)(3) of AMC2 ATS.TR.255, other equivalent ATS surveillance systems (e.g. ADS-B or MLAT) may be used to provide the services, provided that a performance capability equal to or better than that required can be demonstrated. (PANS ATM — Section 6.7.3.2.1 (second sentence)) AMC4 ATS.TR.255 Operations on parallel or near-parallel runways REQUIREMENTS AND PROCEDURES FOR SEGREGATED PARALLEL OPERATIONS (a) Segregated parallel operations should only be conducted on parallel runways when: (1) the runway centre lines are spaced by the distance specified in CS ADR-DSN.B.055 ‘Minimum distance between parallel instrument runways’ in EASA ED Decision 2014/013/R ‘Certification Specifications and Guidance Material For Aerodromes Design’, as amended; and (2) the nominal departure track diverges immediately after take-off by at least 30 degrees from the missed approach track of the adjacent approach (see Figure 51). Figure 51 — Segregated parallel operations (b) The minimum distance between parallel runway centre lines for segregated parallel operations may be decreased by 30 m for each 150 m that the arrival runway is staggered toward the arriving aircraft, to a minimum of 300 m (see Figure 52) and should be increased by 30 m for each 150 m that the arrival runway is staggered away from the arriving aircraft (see Figure 53). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 171 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments Figure 52 — Segregated parallel operations where runways are staggered Figure 53 — Segregated parallel operations where runways are staggered (c) The following types of approaches may be conducted in segregated parallel operations, provided suitable surveillance radar and the appropriate ground facilities conform to the standard necessary for the specific type of approach: (1) ILS and/or MLS precision approach; (2) surveillance radar approach (SRA); and (3) visual approach. (PANS ATM — Sections 6.7.3.5.1, 6.7.3.5.2 and 6.7.3.5.3) GM1 ATS.TR.255 Operations on parallel or near-parallel runways Guidance material relating to operations on parallel or near-parallel runways is contained in the Manual on Simultaneous Operations on Parallel or Near-Parallel Instrument Runways (SOIR) (Doc 9643). (PANS ATM — Note to Section 6.7.1) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 172 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC1 ATS.TR.260(g) Selection of the runway in use CONSIDERATION OF NOISE ABATEMENT IN THE SELECTION OF RUNWAY IN USE (a) The unit providing aerodrome control service should select runways for noise abatement purposes for landing operations only when they are equipped with suitable glide path guidance, e.g. ILS, or a visual approach slope indicator system for operations in visual meteorological conditions. (b) Noise abatement should not be a determining factor in runway nomination under the following circumstances: (1) if the runway surface conditions are adversely affected (e.g. by snow, slush, ice, water, mud, rubber, oil or other substances); (2) for landing in conditions: (i) when the ceiling is lower than 150 m (500 ft) above aerodrome elevation, or the visibility is less than 1 900 m; or (ii) when the approach requires use of vertical minima greater than 100 m (300 ft) above aerodrome elevation and: (A) the ceiling is lower than 240 m (800 ft) above aerodrome elevation; or (B) the visibility is less than 3 000 m; (3) for take-off when the visibility is less than 1 900 m; (4) when wind shear has been reported or forecast or when thunderstorms are expected to affect the approach or departure; and (5) when the crosswind component, including gusts, exceeds 28 km/h (15 kt), or the tailwind component, including gusts, exceeds 9 km/h (5 kt). (PANS ATM — Section 7.2.4 and 7.2.6) GM1 ATS.TR.260 Selection of the runway in use SELECTION OF THE RUNWAY IN USE (a) Normally, an aircraft will land and take off into wind. (b) Departing aircraft may be expedited by suggesting a take-off direction which is not into the wind. It is the responsibility of the pilot-in-command of an aircraft to decide between making such a take-off or waiting for take-off in a preferred direction. (PANS ATM — Sections 7.2.2 (initial part of the first sentence) and Section 6.3.3.1) GM1 ATS.TR.265(a)(1) Control of aerodrome surface traffic in conditions of low visibility HOLDING POSITION LIMITS The definition of holding position limits by intermediate holding positions, stop bar or taxiway intersection marking is established in accordance with EASA ED Decision 2014/013/R ‘Certification Specification and Guidance Material for Aerodrome Design’, as amended. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 173 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC1 ATS.TR.265(b) Control of aerodrome surface traffic in conditions of low visibility PROCEDURES FOR CONTROL OF AERODROME TRAFFIC WHEN CATEGORY II/III APPROACHES ARE IN USE (a) Low visibility operations should be initiated by or through the aerodrome control tower. (b) The aerodrome control tower should inform the approach control unit concerned when procedures for precision approach category II/III and departure operations in RVR conditions less than a value of 550 m will be applied and also when such procedures are no longer in force. (c) Provisions regarding low visibility operations should specify: (1) the RVR value(s) at which the low visibility operations procedures are to be implemented; (2) the minimum ILS/MLS equipment requirements for category II/III operations; (3) other facilities and aids required for category II/III operations, including aeronautical ground lights, which are to be monitored for normal operation; (4) the criteria for and the circumstances under which downgrading of the ILS/MLS equipment from category II/III operations capability is to be made; (5) the requirement to report any relevant equipment failure and degradation, without delay, to the flight crews concerned, the approach control unit, and any other appropriate organisation; (6) special procedures for the control of traffic on the manoeuvring area, including: (i) the runway-holding positions to be used; (ii) the minimum distance between an arriving and a departing aircraft to ensure protection of the sensitive and critical areas; (iii) procedures to verify that aircraft and vehicles have vacated the runway; and (iv) procedures applicable to the separation of aircraft and vehicles; (7) the applicable spacing between successive approaching aircraft; (8) the action(s) to be taken in the event that low visibility operations need to be discontinued, e.g. due to equipment failures; and (9) any other relevant procedures or requirements. (d) The aerodrome control tower should, prior to a period of application of low visibility procedures, establish a record of vehicles and persons currently on the manoeuvring area and maintain this record during the period of application of these procedures to assist in assuring the safety of operations on that area. (PANS ATM — Sections 7.12.3, 7.12.4, 7.12.5 and 7.12.6) GM1 ATS.TR.270 Authorisation of special VFR SPECIAL VFR IN CONTROL ZONES The list of type of operations subject to permit by the competent authority to deviate from the requirements for special VFR flights is not exhaustive. The competent Authority may grant a permit for other kinds of helicopter operations such as power line inspections, helicopter hoist operations, etc. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 174 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (Also proposed as GM1 SERA.5010 in NPA 2015-14) GM1 ATS.TR.270(a)(3) Authorisation of special VFR SPECIAL VFR IN CONTROL ZONES When the reported ground visibility at the aerodrome is less than 1 500 m, ATC units may issue a special VFR clearance for a flight crossing the control zone and not intending to take off or land at an aerodrome within a control zone, or enter the aerodrome traffic zone or aerodrome traffic circuit when the flight visibility reported by the pilot is not less than 1 500 m. (Also proposed as GM2 to SERA.5010(b) in NPA 2015-14) GM1 ATS.TR.275 Pressure-altitude-derived level information These provisions may also apply to flight information service when so prescribed by the competent authority. AMC1 ATS.TR.275(a) Pressure-altitude-derived level information TOLERANCE VALUE FOR PRESSURE-ALTITUDE-DERIVED INFORMATION The tolerance value used to determine that the pressure-altitude-derived level information displayed to the controller is accurate should be ±60 m (±200 ft) in RVSM airspace. In other airspace, it should be ±90 m (±300 ft), except that the competent authority may specify a smaller criterion, but not less than ±60 m (±200 ft), if this is found to be more practical. (PANS ATM — Section 8.5.5.1.1 (first and second sentence)) AMC2 ATS.TR.275(a) Pressure-altitude-derived level information VERIFICATION OF PRESSURE ALTITUDE DERIVED INFORMATION The verification should be effected by simultaneous comparison with altimeter-derived level information received from the same aircraft by radiotelephony. (PANS ATM — Section 8.5.5.1.2 (second sentence)) GM1 ATS.TR.275(a) Pressure-altitude-derived level information ERRONEOUS LEVEL INFORMATION (a) If the displayed level information is not within the approved tolerance value or when a discrepancy in excess of the approved tolerance value is detected subsequent to verification, the pilot should be advised accordingly and requested to check the pressure setting and confirm the aircraft’s level. (b) If, following confirmation of the correct pressure setting the discrepancy continues to exist, the following action should be taken by ATC according to circumstances: (1) request the pilot to stop Mode C or ADS-B altitude data transmission, provided this does not cause the loss of position and identity information, and notify the next control positions or ATC unit concerned with the aircraft of the action taken; or (2) inform the pilot of the discrepancy and request that the relevant operation continue in order to prevent loss of position and identity information of the aircraft and, when so TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 175 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments prescribed by the local instructions, override the label-displayed level information with the reported level. In addition, the ATC unit should notify the next control position or ATC unit concerned with the aircraft of the action taken. (PANS ATM — Sections 8.5.5.1.3 and 8.5.5.1.4) (Sections 8.5.5.1.3 and 8.5.5.1.4 have been transposed as GM1 SERA.13010(b) with NPA 2015-14) AMC1 ATS.TR.275(b) Pressure-altitude-derived level information VERIFICATION OF LEVEL OCCUPANCY (a) In accordance with AMC1 ATS.TR.275(a), the criterion which should be used to determine that a specific level is occupied by an aircraft is be ±60 m (±200 ft) in RVSM airspace. In other airspace, this criterion should be ±90 m (±300 ft), except that the competent authority may specify a smaller criterion, but not less than ±60 m (±200 ft), if this is found to be more practical. (b) Aircraft maintaining a level. An aircraft should be considered to be maintaining its assigned level as long as the pressure-altitude-derived level information indicates that it is within the appropriate tolerances of the assigned level, as specified in point (a). (c) Aircraft vacating a level. An aircraft cleared to leave a level should be considered to have commenced its manoeuvre and vacated the previously occupied level when the pressure- altitude-derived level information indicates a change of more than 90 m (300 ft) in the anticipated direction from its previously assigned level. (d) Aircraft passing a level in climb or descent. An aircraft in climb or descent should be considered to have crossed a level when the pressure-altitude-derived level information indicates that it has passed this level in the required direction by more than 90 m (300 ft). (e) Aircraft reaching a level. An aircraft should be considered to have reached the level to which it has been cleared when the elapsed time of three display updates, three sensor updates or 15 seconds, whichever is the greater, has passed since the pressure-altitude-derived level information has indicated that it is within the appropriate tolerances of the assigned level, as specified in point (a). (PANS ATM — Sections 8.5.5.2.1, 8.5.5.2.2, 8.5.5.2.3, 8.5.5.2.4 and 8.5.5.2.5) GM1 ATS.TR.300(b) Application It is recognised that in certain circumstances an aircraft on final approach, landing, take-off and climb may require to receive without delay essential information other than that pertaining to the provision of ATC service. (Annex 11 — Note to Section 4.1.2) AMC1 ATS.TR.300(c)(1) Application RECORDING AND TRANSMISSION OF INFORMATION ON THE PROGRESS OF FLIGHTS Information on the actual progress of flights, including those of heavy or medium unmanned free balloons, under neither ATC service nor air traffic advisory service should be: TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 176 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (a) recorded by the ATS unit serving the FIR within which the aircraft is flying in such a manner that it is available for reference and in case it is requested for search and rescue action; and (b) transmitted by the ATS unit receiving the information to other ATS units concerned, when so required for the purposes of the coordination between ATS units providing flight information service in adjacent FIRs in respect of IFR and VFR flights (See points (a) and (b) of GM2 ATS.TR.300(c)(2)). (PANS ATM — Section 9.1.1) AMC1 ATS.TR.300(c)(2) Application TRANSFER OF RESPONSIBILITY FOR THE PROVISION OF FLIGHT INFORMATION SERVICE BETWEEN FLIGHT INFORMATION CENTRES The responsibility for the provision of flight information service to a flight should normally pass from the appropriate ATS unit in an FIR to the appropriate ATS unit in the adjacent FIR at the time of crossing the common FIR boundary. However, when coordination is required in accordance with point (b) of AMC1 ATS.TR.300(c)(1), but communication facilities are inadequate, the former ATS unit should, as far as practicable, continue to provide flight information service to the flight until it has established two-way communication with the appropriate ATS unit in the FIR it is entering. (PANS ATM — Section 9.1.2) GM1 ATS.TR.300(c)(2) Application INFORMATION EXCHANGE IN CASE OF TERMINATION OF A CONTROLLED FLIGHT In the case where a flight ceases to be operated as a controlled flight, i.e. by leaving controlled airspace or by cancelling its IFR flight and proceeding on VFR in airspace where VFR flights are not controlled, the ATC unit concerned should ensure that appropriate information on the flight is forwarded to ATS unit(s) responsible for the provision of flight information and alerting services for the remaining portion of the flight, in order to ensure that such services will be provided to the aircraft. (PANS ATM — Section 10.1.2.5) GM2 ATS.TR.300(c)(2) Application COORDINATION IN RESPECT OF THE PROVISION OF FLIGHT INFORMATION SERVICE AND ALERTING SERVICE (a) Coordination between ATS units providing flight information service in adjacent FIRs should be effected in respect of IFR and VFR flights, in order to ensure continued flight information service to such aircraft in specified areas or along specified routes. Such coordination should be effected in accordance with an agreement between the ATS units concerned. (b) The coordination of flights effected in accordance with point (a) should include transmission of the following information on the flight concerned: (1) appropriate items of the current flight plan; and (2) the time at which last contact was made with the aircraft concerned. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 177 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (c) This information should be forwarded to the ATS unit in charge of the next FIR in which the aircraft will operate prior to the aircraft entering such FIR. (d) In order to assist in the identification of strayed or unidentified aircraft and thereby eliminate or reduce the need for interception, flight plan and flight progress information for flights along specified routes or portions of routes in close proximity to FIR boundaries should also be provided to the ATS units in charge of the FIRs adjacent to such routes or portions of routes. (e) In circumstances where an aircraft has declared minimum fuel or is experiencing an emergency or in any other situation wherein the safety of the aircraft is not assured, the type of emergency and/or the circumstances experienced by the aircraft should be reported by the transferring unit to the accepting unit and any other ATS unit that may be concerned with the flight and to the associated rescue coordination centres, if necessary. (PANS ATM — Sections 10.2.1, 10.2.2, 10.2.3, 10.2.4 and 10.2.5) AMC1 ATS.TR.305 Scope of flight information service TRANSMISSION OF INFORMATION (a) Means of transmission (1) Information should be disseminated to aircraft by one or more of the following means: (i) the preferred method of directed transmission on the initiative of the appropriate ATS unit to an aircraft, ensuring that receipt is acknowledged; or (ii) a general call, unacknowledged transmission to all aircraft concerned; or (iii) broadcast; or (iv) data link. (2) The use of general calls should be limited to cases where it is necessary to disseminate essential information to several aircraft without delay, e.g. the sudden occurrence of hazards, a change of the runway in use, or the failure of a key approach and landing aid. (b) Transmission of special air-reports, SIGMET and AIRMET information (1) Appropriate SIGMET and AIRMET information, as well as special air-reports which have not been used for the preparation of a SIGMET, should be disseminated to aircraft by one or more of the means specified in point (a) as established by the competent authority. Special air-reports should be disseminated to aircraft for a period of 60 minutes after their issuance. (2) The special air-report, SIGMET and AIRMET information to be passed on to aircraft on ground initiative should cover a portion of the route up to one hour’s flying time ahead of the aircraft except when another period has been determined on the basis of regional air navigation agreements. (c) Transmission of information concerning volcanic activity Information concerning pre-eruption volcanic activity, volcanic eruptions and volcanic ash clouds (position of clouds and flight levels affected) should be disseminated to aircraft by one or more of the means specified in point (a) as established by the competent authority. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 178 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (d) Transmission of information concerning radioactive materials and toxic chemical clouds Information on the release into the atmosphere of radioactive materials or toxic chemicals which could affect airspace within the area of responsibility of the ATS unit should be transmitted to aircraft by one or more of the means specified in point (a). (e) Transmission of SPECI and amended TAF (1) Special reports in the SPECI code form and amended TAF should be transmitted on request and supplemented by: (i) directed transmission from the appropriate ATS unit of selected special reports and amended TAF for the departure, destination and its alternate aerodromes, as listed in the flight plan; or (ii) a general call on appropriate frequencies for the unacknowledged transmission to affected aircraft of selected special reports and amended TAF; or (iii) continuous or frequent broadcast or the use of data link to make available current METAR and TAF in areas determined on the basis of regional air navigation agreements where traffic congestion dictates. VOLMET broadcasts and/or D- VOLMET should be used to serve this purpose. (2) The passing of amended aerodrome forecasts to aircraft on the initiative of the appropriate ATS unit should be limited to that portion of the flight where the aircraft is within a specified time from the aerodrome of destination, such time being established on the basis of regional air navigation agreements. (f) Transmission of information on heavy or medium unmanned free balloons Appropriate information on heavy or medium unmanned free balloons should be disseminated to aircraft by one or more of the means specified in point (a). (g) Transmission of information to supersonic aircraft The following information should be available at appropriate ACCs or flight information centres for aerodromes determined by the competent authority and should be transmitted on request to supersonic aircraft prior to commencement of deceleration/descent from supersonic cruise: (1) current meteorological reports and forecasts, except that where communications difficulties are encountered under conditions of poor propagation, the elements transmitted may be limited to: (i) mean surface wind, direction and speed (including gusts); (ii) visibility or runway visual range; (iii) amount and height of base of low clouds; (iv) other significant information; and (v) if appropriate, information regarding expected changes; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 179 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (2) operationally significant information on the status of facilities relating to the runway in use, including the precision approach category in the event that the lowest approach category promulgated for the runway is not available; (3) sufficient information on the runway surface conditions to permit assessment of the runway braking action. (PANS ATM — Sections 9.1.3.1.1, 9.1.3.1.2, 9.1.3.2.1, 9.1.3.2.2, 9.1.3.3, 9.1.3.4, 9.1.3.5.1, 9.1.3.5.2, 9.1.3.6 and 9.1.3.7) AMC1 ATS.TR.305(a);(b) Scope of flight information service INFORMATION FOR DEPARTING AIRCRAFT — METEOROLOGICAL CONDITIONS Information regarding significant changes in the meteorological conditions in the take-off or climb-out area, obtained by the unit providing approach control service after a departing aircraft has established communication with such unit, should be transmitted to the aircraft without delay, except when it is known that the aircraft already has received the information. (PANS ATM — Section 6.4.1) GM1 to AMC1 ATS.TR.305(a);(b) Scope of flight information service INFORMATION FOR DEPARTING AIRCRAFT — METEOROLOGICAL CONDITIONS Significant changes in this context include those relating to surface wind direction or speed, visibility, runway visual range or air temperature (for turbine-engined aircraft), and the occurrence of thunderstorm or, moderate or severe turbulence, wind shear, hail, moderate or severe icing, severe squall line, freezing precipitation, severe mountain waves, sandstorm, dust storm, blowing snow, tornado or waterspout. (PANS ATM — Note to Section 6.4.1) GM1 ATS.TR.305(a);(b);(c) Scope of flight information service INFORMATION ON AERODROME CONDITIONS IN THE AFIS CONTEXT Information on AFIS aerodrome conditions and changes thereto which is essential to the safe operation of aircraft, should, to the extent possible, relate to the following: (a) construction or maintenance work on, or immediately adjacent to, the manoeuvring area; (b) rough or broken surfaces on a runway or a taxiway, whether marked or not; (c) water, snow, slush, ice or frost on a runway or a taxiway; (d) anti-icing or de-icing liquid chemicals or other contaminants on a runway, taxiway or apron; (e) snow banks or drifts adjacent to a runway or a taxiway; (f) other temporary hazards, including parked aircraft and birds on the ground or in the air; (g) failure or irregular operation of part or all of the aerodrome lighting system; and (h) any other pertinent information. (ICAO Circular 211-AN/128, ‘General’, 6. (d)) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 180 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM2 ATS.TR.305(a);(b);(c) Scope of flight information service TRAFFIC INFORMATION TO AIRCRAFT IN THE AFIS CONTEXT The AFIS unit should provide the following information, as appropriate: (a) direction of flight of aircraft concerned (b) type and wake turbulence category (if known) of aircraft concerned; (c) level of aircraft concerned, including possible changes; (d) relative bearing of the aircraft concerned in terms of the 12-hour clock as well as distance from the conflicting traffic; or (1) actual or estimated position of the aircraft concerned; or (2) estimated times; and (e) any other information considered relevant (e.g. approaching, crossing the traffic information area/traffic information zone (TIA/TIZ), estimated take-off or landing time). (EUROCONTROL AFIS Manual, Section 3.4.1) GM3 ATS.TR.305(a);(b);(c) Scope of flight information service LOCAL TRAFFIC INFORMATION TO AIRCRAFT IN THE AFIS CONTEXT AFIS units should issue traffic information on local traffic in a timely manner, either directly or through the unit providing approach control service when, in the judgement of the AFIS unit, such information is necessary in the interests of safety, or when requested by aircraft. Local traffic shall be described so as to be easily identified by the pilot. (EUROCONTROL AFIS Manual, Section 3.4.2) GM4 ATS.TR.305(a);(b);(c) Scope of flight information service WAKE TURBULENCE AND JET BLAST HAZARDS INFORMATION TO AIRCRAFT IN THE AFIS CONTEXT (a) The responsibility for wake turbulence avoidance rests entirely with the pilot-in-command. AFIS units should, to the extent practicable, advise aircraft of the expected occurrence of hazards caused by turbulent wake. Such information will be provided by the warning ‘caution wake turbulence’ and may also include relevant information on the aircraft concerned. (b) In providing information, AFIS units should take into account the hazards caused by jet blast, helicopter downwash turbulence and propeller slipstream to taxiing aircraft, to aircraft taking off or landing, particularly when intersecting runways are being used, and to vehicles and personnel operating on the aerodrome. (EUROCONTROL AFIS Manual, — Sections 3.4.5.1 and 3.4.5.2) AMC1 ATS.TR.305(a)(5) Scope of flight information service ESSENTIAL INFORMATION ON AERODROME CONDITIONS Essential information on aerodrome conditions should be given to every aircraft, except when it is known that the aircraft already has received all or part of the information from other sources, including NOTAM, ATIS broadcasts, and the display of suitable signals. The information should be given in TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 181 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments sufficient time for the aircraft to make proper use of it, and the hazards should be identified as distinctly as possible. (PANS ATM — Section 7.5.3) GM1 to AMC1 ATS.TR.305(a)(5) Scope of flight information service ESSENTIAL INFORMATION ON AERODROME CONDITIONS (a) Essential information on aerodrome conditions is information necessary to safety in the operation of aircraft, which pertains to the movement area or any facilities usually associated therewith. For example, construction work on a taxi strip not connected to the runway in use would not be essential information to any aircraft except one that might be taxied in the vicinity of the construction work. As another example, if all traffic must be confined to runways, that fact should be considered as essential aerodrome information to any aircraft not familiar with the aerodrome. (b) Essential information on aerodrome conditions should include information relating to the following: (1) construction or maintenance work on, or immediately adjacent to, the movement area; (2) rough or broken surfaces on a runway, a taxiway or an apron, whether marked or not; (3) water, snow, slush, ice or frost on a runway, a taxiway or an apron; (4) water on a runway, a taxiway or an apron; (5) anti-icing or de-icing liquid chemicals or other contaminants on a runway, taxiway or apron; (6) other temporary hazards, including parked aircraft and birds on the ground or in the air; (7) failure or irregular operation of part or all of the aerodrome lighting system; and (8) any other pertinent information. (c) Up-to-date information on the conditions on aprons may not always be available to the aerodrome control tower or to the AFIS unit. The responsibility of the aerodrome control tower or the AFIS unit in relation to aprons is, with respect to the provision of information as described in points (a) and (b), limited to the transmission to aircraft of the information which is provided to it by the operator responsible for the aprons. (PANS ATM — Sections 7.5.1, 7.5.2 and Note to Section 7.5.2) AMC2 ATS.TR.305(a)(5) Scope of flight information service INFORMATION FOR DEPARTING AIRCRAFT — OPERATIONAL STATUS OF VISUAL AND NON-VISUAL AIDS Information regarding changes in the operational status of visual or non-visual aids essential for take- off and climb should be transmitted without delay to a departing aircraft, except when it is known that the aircraft has already received the information. (PANS ATM — Section 6.4.2) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 182 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM1 ATS.TR.305(a)(6) Scope of flight information service INFORMATION ON UNMANNED FREE BALLOONS (a) On receipt of notification of the intended flight of a medium or heavy unmanned free balloon, the ATS unit should arrange for the information to be disseminated to all concerned. The information should include: (1) the balloon flight identification or project code name; (2) balloon classification and description; (3) SSR code or NDB frequency as applicable; (4) the launch site; (5) the estimated time of the commencement of the launch or the planned period of the launches; (6) the expected direction of ascent; (7) the cruising level(s) (pressure-altitude); and (8) the estimated elapsed time to pass 18 000 m (60 000 ft) pressure-altitude, or to reach cruising level if at or below 18 000 m (60 000 ft), together with the estimated location. (b) On receipt of notification that a medium or heavy unmanned free balloon has been launched, the ATS unit should arrange for the information to be disseminated to all concerned. The information should include: (1) the balloon flight identification or project code name; (2) balloon classification and description; (3) SSR code or NDB frequency as applicable; (4) the launch site; (5) the time of launch(es); (6) the estimated time at which 18 000 m (60 000 ft) pressure-altitude will be passed, or the estimated time at which the cruising level will be reached if at or below 18 000 m (60 000 ft), and the estimated location; (7) the estimated date and time of termination of the flight; and (8) the planned location of ground contact, when applicable. (c) When there is reasonable expectation that a heavy or medium unmanned free balloon will cross international borders, the appropriate ATS unit should arrange for the pre-launch and the launch notifications to be sent by NOTAM to the ATS unit(s) in the State(s) concerned. If agreed between the States concerned, the launch notification may be transmitted orally by direct ATS speech circuit between the ACCs/flight information centres involved. (PANS ATM — Sections 16.2.1, 16.2.2 and 16.2.3) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 183 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments AMC1 ATS.TR.305(a)(7) Scope of flight information service INFORMATION ON ABNORMAL AIRCRAFT CONFIGURATION AND CONDITION (a) Whenever an abnormal configuration or condition of an aircraft, including conditions such as landing gear not extended or only partly extended, or unusual smoke emissions from any part of the aircraft, is observed by or reported to the aerodrome controller or the AFIS officer, the aircraft concerned should be advised without delay. (b) When requested by the flight crew of a departing aircraft suspecting damage to the aircraft, the departure runway used should be inspected without delay and the flight crew advised in the most expeditious manner as to whether any aircraft debris or bird or animal remains have been found or not. (PANS ATM — Sections 7.4.1.7.1 and 7.4.1.7.2) GM1 ATS.TR.305(b)(1) Scope of flight information service INFORMATION RELATED TO WEATHER CONDITIONS AT DEPARTURE, DESTINATION, AND ALTERNATE AERODROMES Pilots normally obtain information on the weather conditions from the appropriate office before the flight. Outstanding or safety-relevant information is normally provided by radio communication when available. (GM1 SERA.9005(b)(1)) GM1 ATS.TR.305(b)(2) Scope of flight information service INFORMATION CONCERNING COLLISION HAZARDS Information relating to collision hazards includes only known activities that constitute risks to the aircraft concerned. The availability of such information to ATS may sometimes be incomplete (e.g. limitations in radar or radio coverage, optional radio contact by pilots, limitations in the accuracy of reported information by pilots, or unconfirmed level of information) and, therefore, ATS cannot assume responsibility for its issuance at all times or for its accuracy. (Annex 11 — Note to Section 4.2.2(b)) (Said Note has been transposed as GM1 SERA.9005(b)(2) GM1 ATS.TR.305(c)(1) Scope of flight information service RUNWAY INCURSION OR OBSTRUCTED RUNWAY In the event that the AFIS officer becomes aware of a runway incursion or the imminent occurrence thereof, or the existence of any obstruction on or in close proximity to the runway likely to impair the safety of an aircraft taking off or landing, appropriate action should be taken to inform the aircraft of the runway incursion or obstruction and its location in relation to the runway. (EUROCONTROL AFIS Manual — Section 4.2.7) GM1 ATS.TR.305(c)(2) Scope of flight information service SELECTION OF THE RUNWAY IN USE AT AFIS AERODROMES Normally, an aircraft will land and take off into wind unless safety, the runway configuration, meteorological conditions and available instrument approach procedures or air traffic conditions TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 184 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments determine that a different direction is preferable. In selecting the runway however, besides surface wind speed and direction, other relevant factors such as the aerodrome traffic circuits, the length of runways, and the approach and landing aids available are to be taken into consideration. (EUROCONTROL AFIS Manual — Section 3.2.2) GM1 ATS.TR.305(d)(3) Scope of flight information service OTHER ATS UNITS CONCERNED Other ATS units concerned are those that have flights under their jurisdiction which are expected to enter the airspace concerned at a later stage of flight. Those flights could, for instance, require rerouting before entering the airspace concerned. As an example, a special air-report concerning volcanic ash or volcanic eruption could be necessary to be transmitted to aircraft by ATS units in the FIR adjacent to that affected by the air-report. (GM1 SERA.12020(a)(3)) GM1 ATS.TR.310(f) Voice-automatic terminal information service (Voice-ATIS) broadcasts ATIS BROADCAST CHANNELS Where Voice-ATIS broadcasts are available in more than one language, a discrete channel should be used for each language. (Annex 11 — Recommendation in Section 4.3.4.7) GM1 ATS.TR.310(g) Voice-automatic terminal information service (Voice-ATIS) broadcasts ATIS BROADCAST MESSAGES The ATIS broadcast message should take into consideration human performance. (Annex 11 — Second sentence of Recommendation in Section 4.3.4.8) GM1 ATS.TR.315 Data link-automatic terminal information service (D-ATIS) Guidance material relating to D-ATIS is contained in the ICAO Manual of Air Traffic Services Data Link Applications (Doc 9694). (Annex 11 — Note to Section 4.3.5.2) GM1 ATS.TR.320 Automatic terminal information service (voice and/or data link) CONTENT OF ATIS MESSAGES (a) Contents of ATIS messages are established in provision SERA.9010 of Commission Implementing Regulation (EU) No 923/2012, and more specifically: (1) the elements of information of ATIS messages containing both arrival and departure information are specified in provision SERA.9010(b) of Commission Implementing Regulation (EU) No 923/2012, in the order listed. (2) the elements of information ATIS messages containing arrival information only are specified in provision SERA.9010(c) of Commission Implementing Regulation (EU) No 923/2012, in the order listed; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 185 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (3) the elements of information of ATIS messages containing departure information only are specified in provision SERA.9010(d) of Commission Implementing Regulation (EU) No 923/2012, in the order listed. (b) Contents of ATIS messages should be kept as brief as possible. (c) Information additional to that specified in SERA.9010 of Commission Implementing Regulation (EU) No 923/2012; for example information already available in AIPs and NOTAM, should only be included when justified in exceptional circumstances. (Annex 11 — Sections 4.3.7, 4.3.8, 4.3.9 and Note to Section 4.3.6.5) (Sections 4.3.7, 4.3.8, 4.3.9 have been transposed as SERA.9010) GM1 ATS.TR.320(d) Automatic terminal information service (voice and/or data link) UPDATE OF CHANGED ATIS MESSAGES ELEMENTS The ATS unit should: (a) communicate to the aircraft any element of information which has to be updated; or (b) instruct the aircraft to obtain the current ATIS information. GM1 ATS.TR.325 VOLMET broadcasts and D-VOLMET broadcasts VOLMET BROADCAST PHRASEOLOGIES Guidance on standard radiotelephony phraseologies to be used in VOLMET broadcasts is available in the ICAO Manual on Coordination between Air Traffic Services, Aeronautical information Services and Aeronautical Meteorological Services (Doc 9377), Appendix 1. (Annex 11 — Note to Section 4.4.2) GM1 ATS.TR.400(b) Application COORDINATION FOR ALERTING SERVICE (a) When alerting service is required in respect of a flight operated through more than one FIR or control area, and when the position of the aircraft is in doubt, responsibility for coordinating such service should rest with the ATS unit of the FIR or control area: (1) within which the aircraft was flying at the time of last air–ground radio contact; (2) that the aircraft was about to enter when last air–ground contact was established at or close to the boundary of two FIRs or control areas; (3) within which the aircraft’s intermediate stop or final destination point is located if the aircraft was not: (i) equipped with suitable two-way radio communication equipment; or (ii) under obligation to transmit position reports. (b) The unit responsible for alerting service, in accordance with point (a), should: (1) notify units providing alerting service in other affected FIRs or control areas of the emergency phase or phases, in addition to notifying the rescue coordination centre associated with it; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 186 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments (2) request those units to assist in the search for any useful information pertaining to the aircraft presumed to be in an emergency, by all appropriate means and available communication facilities; (3) collect the information gathered during each phase of the emergency and, after verifying it as necessary, transmit it to the rescue coordination centre; and (4) announce the termination of the state of emergency as circumstances dictate. (c) In obtaining the necessary information as required under ATS.TR.405(b) and (c), attention is to particularly be given to informing the relevant rescue coordination centre of the distress frequencies available to survivors. Said information is listed in Item 19 of the flight plan but not normally transmitted. (PANS ATM — Sections 9.2.2.2, 9.2.2.3 and 9.2.2.4) AMC1 ATS.TR.400(d) Application ALERTING OF RESCUE AND FIREFIGHTING SERVICES Aerodrome control towers, approach control units or AFIS units should alert the rescue and firefighting services whenever: (a) an aircraft accident has occurred on or in the vicinity of the aerodrome; or (b) 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; or (c) requested by the flight crew; or (d) when otherwise deemed necessary or desirable. (PANS ATM — Section 7.1.2.1) AMC2 ATS.TR.400(d) Application ALERTING OF RESCUE AND FIRE FIGHTING SERVICES Local instructions, as in ATS.TR.400(d), should specify the type of information to be provided by the aerodrome control tower or approach control unit responsible or the relevant AFIS unit to the rescue and firefighting services, including type of aircraft and type of emergency and, when available, number of persons on board, and any dangerous goods carried on the aircraft. (PANS ATM — Section 7.1.2.2 (second sentence)) GM1 ATS.TR.405(a)(1) Notification to rescue coordination centres AIRCRAFT REPORT FOR THE PURPOSES OF UNCERTAINTY PHASE When no report from an aircraft has been received within a reasonable period of time (which may be a specified interval prescribed on the basis of regional air navigation agreements) after a scheduled or expected reporting time, the ATS unit should, within the stipulated period of 30 minutes, endeavour to obtain such report in order to be in a position to apply the provisions relevant to the ‘Uncertainty Phase’ should circumstances warrant such application. (PANS ATM — Section 9.2.2.1) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 187 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments GM1 ATS.TR.405(a)(2)(ii) Notification to rescue coordination centres MISSED AICRAFT REPORT — ACTIONS OF THE AERODROME CONTROL TOWERS When an aircraft fails to report after having been transferred to an aerodrome control tower, or, having once reported, ceases radio contact and in either case fails to land 5 minutes after the expected landing time, the same aerodrome control tower should, in accordance with ATS.TR.400(c), report the situation to the approach control unit, ACC or flight information centre, or to the rescue coordination centre or rescue sub-centre. (PANS ATM — Section 7.1.2.3) GM1 ATS.TR.405(a)(2)(iii) Notification to rescue coordination centres MISSED AICRAFT REPORT — ACTIONS OF THE AFIS UNIT When an aircraft fails to report to or ceases radio contact with an AFIS unit under the circumstances established by the competent authority, the same AFIS unit should, in accordance with ATS.TR.400(c), report the situation to the approach control unit, ACC or flight information centre, or to the rescue coordination centre or rescue sub-centre. (PANS ATM — Section 7.1.2.3) GM1 ATS.TR.405(c) Notification to rescue coordination centres INFORMATION FOR THE PURPOSES OF ALERTING SERVICE In case of missing information as specified in ATS.TR.405(b), the ATS units should clearly indicate to the rescue coordination centre the information not available at the time of the notification of the distress phase. GM1 ATS.TR.405(d) Notification to rescue coordination centres CANCELLATION OF ACTION(S) RELATED TO ALERTING SERVICE The cancellation of action(s) initiated by the rescue coordination centre is the responsibility of that centre. (Annex 11 — Note to Section 5.2.3) AMC1 ATS.TR.415 Plotting aircraft in a state of emergency PLOTTING AIRCRAFT IN A STATE OF EMERGENCY WHERE ATS SURVEILLANCE SERVICE IS PROVIDED The progress of an aircraft in emergency should be monitored and (whenever possible) plotted on the situation display until the aircraft passes out of coverage of the ATS surveillance system, and position information should be provided to all ATS units which may be able to give assistance to the aircraft. (PANS ATM — Section 8.8.1.2) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 188 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 1. Proposed amendments 1.4. Amendments to ED Decision 2013/013/R — AMC/GM to the SERA Regulation (draft decision) It is proposed to amend the ED Decision by introducing the following: GMX to SERA.8005(c)(1) Operation of air traffic control service GEOMETRIC HEIGHT INFORMATION Geometric height information is generated by airborne systems, for instance, GPS or radio altimeters. GMY to SERA.14095 Distress and urgency radiotelephony communication procedures USE OF VHF EMERGENCY CHANNEL IN CASE OF HANDLING OF DISTRESS TRAFFIC The use of the frequency 121.500 MHz for the purpose outlined in point (a)(3) is to be avoided if it interferes in any way with the efficient handling of distress traffic. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 189 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 2. References 2. References 2.1. Affected regulations — Commission Implementing Regulation (EU) 2016/1377 of 4 August 2016 laying down common requirements for service providers and the oversight in air traffic management/air navigation services and other air traffic management network functions, repealing Regulation (EC) No 482/2008, Implementing Regulations (EU) No 1034/2011 and (EU) No 1035/2011 and amending Regulation (EU) No 677/2011 (OJ L 226, 19.8.2016, p. 1) — Commission Implementing Regulation (EU) No 923/2012 of 26 September 2012 laying down the common rules of the air and operational provisions regarding services and procedures in air navigation and amending Implementing Regulation (EU) No 1035/2011 and Regulations (EC) No 1265/2007, (EC) No 1794/2006, (EC) No 730/2006, (EC) No 1033/2006 and (EU) No 255/2010 (OJ L 281, 13.10.2012, p. 1) — Commission Implementing Regulation (EU) 2016/1185 of 20 July 2016 amending Implementing Regulation (EU) No 923/2012 as regards the update and completion of the common rules of the air and operational provisions regarding services and procedures in air navigation (SERA Part C) and repealing Regulation (EC) No 730/2006 (OJ L 196, 21.7.2016, p. 3) 2.2. Affected AMC and GM Decision 2013/013/R of the Executive Director of the European Aviation Safety Agency of 17 July 2013 adopting the Acceptable Means of Compliance and Guidance Material to Commission Implementing Regulation (EU) No 923/2012 of 26 September 2012 laying down the common rules of the air and operational provisions regarding services and procedures in air navigation and amending Implementing Regulation (EU) No 1035/2011 and Regulations (EC) No 1265/2007, (EC) No 1794/2006, (EC) No 730/2006, (EC) No 1033/2006 and (EU) No 255/20101 ‘Acceptable Means of Compliance and Guidance Material to the rules of the air’ 2.3. Reference documents — Regulation (EC) No 216/2008 of the European Parliament and of the Council of 20 February 2008 on common rules in the field of civil aviation and establishing a European Aviation Safety Agency, and repealing Council Directive 91/670/EEC, Regulation (EC) No 1592/2002 and Directive 2004/36/EC (OJ L 79, 19.3.2008, p. 1) — Regulation (EC) No 550/2004 of the European Parliament and of the Council of 10 March 2004 on the provision of air navigation services in the single European sky (the service provision Regulation) (OJ L 96, 31.3.2004, p. 10) — Regulation (EC) No 551/2004 of the European Parliament and of the Council of 10 March 2004 on the organisation and use of the airspace in the single European sky (the airspace Regulation) (OJ L 96, 31.3.2004, p. 20) — Regulation (EU) No 376/2014 of the European Parliament and of the Council of 3 April 2014 on the reporting, analysis and follow-up of occurrences in civil aviation, amending Regulation (EU) No 996/2010 of the European Parliament and of the Council and repealing Directive 2003/42/EC TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 190 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 2. References of the European Parliament and of the Council and Commission Regulations (EC) No 1321/2007 and (EC) No 1330/2007 (OJ L 122, 24.4.2014, p. 18) — Commission Regulation (EU) 2015/340 of 20 February 2015 laying down technical requirements and administrative procedures relating to air traffic controllers' licences and certificates pursuant to Regulation (EC) No 216/2008 of the European Parliament and of the Council, amending Commission Implementing Regulation (EU) No 923/2012 and repealing Commission Regulation (EU) No 805/2011 (OJ L 63, 6.3.2015, p. 1) — Commission Regulation (EC) No 2150/2005 of 23 December 2005 laying down common rules for the flexible use of airspace (OJ L 342, 24.12.2005, p. 20) — Commission Implementing Regulation (EU) No 1206/2011 of 22 November 2011 laying down requirements on aircraft identification for surveillance for the single European sky (OJ L 305, 23.11.2011, p. 23) — Commission Regulation (EC) No 2096/2005 of 20 December 2005 laying down common requirements for the provision of air navigation services (OJ L 335, 21.12.2005, p. 13) — Commission Implementing Regulation (EU) No 1035/2011 of 17 October 2011 laying down common requirements for the provision of air navigation services and amending Regulations (EC) No 482/2008 and (EU) No 691/2010 (OJ L 271, 18.10.2011, p. 23) — Commission Regulation (EU) No 139/2014 of 12 February 2014 laying down requirements and administrative procedures related to aerodromes pursuant to Regulation (EC) No 216/2008 of the European Parliament and of the Council (OJ L 44, 14.2.2014, p. 1) — ED Decision 2015/014/R of 3 July 2015 ‘Guidance Material on the implementation of the remote tower concept for single mode of operation’ — ED Decision 2014/013/R of 27 February 2014 adopting Certification Specifications and Guidance Material for Aerodromes Design ‘CS-ADR-DSN — Initial issue’ — EASA Opinion No 02/2014 ‘Requirements for apron management services at aerodromes’ — EASA NPA 2016-02 ‘Technical requirements and operational procedures for aeronautical information services and aeronautical information management’ — EASA Safety Information Bulletin (SIB) 2014-07R1: Unexpected Autopilot Behaviour on Instrument Landing System (ILS) Approach — ICAO Doc 7300 ‘Convention of International Civil Aviation’ — ICAO Annex 2 ‘Rules of the Air’ — ICAO Annex 3 ‘Meteorological Service for International Air Navigation’ — ICAO Annex 10 ‘Aeronautical Telecommunications’ (Volume II ‘Communication Procedures’ including those with PANS status) — ICAO Annex 10 ‘Aeronautical Telecommunications’ (Volume V ‘Aeronautical Radio Frequency Spectrum Utilization’) — ICAO Annex 11 ‘Air Traffic Services’ — ICAO Doc. 4444 ‘Procedures for Air Navigation Services — Air Traffic Management’ (PANS ATM) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 191 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 2. References — ICAO Doc 8168 ‘Procedures for Air Navigation Services — Aircraft Operations’(PANS OPS) (Volume II) — ICAO Doc 9377 ‘Manual on Coordination between Air Traffic Services, Aeronautical Information Services and Aeronautical Meteorological Services’ — ICAO Doc 9426 ‘Air Traffic Services Planning Manual’ — ICAO Doc 7030 EUR ‘European (EUR) Regional Supplementary Procedures’ — ICAO Doc 9554 ‘Manual Concerning Safety Measures Relating to Military Activities Potentially Hazardous to Civil Aircraft Operations’ — ICAO Doc 9643 ‘Manual on Simultaneous Operations on Parallel or Near-Parallel Instrument Runways (SOIR)’ — ICAO Doc 9694 ‘Manual of Air Traffic Services Data Link Applications’ — ICAO Circular 211-AN/128 ‘Aerodrome Flight Information Service (AFIS)’ — ICAO TEC/OPS/SEP — 08-0294.SLG ‘Wake turbulence aspects of Airbus A380-800 aircraft’ — ICAO Working Paper AN-WP/9014 dated 18 February 2016 — ICAO EANPG/54 — WP/15 of 16.11.12 — ICAO EANPG/54 — Flimsy 08 of 04.12.12 — ICAO EANPG/56 — WP 18 of 12.11.14 — ICAO EANPG/56 — Final Report — ICAO EANPG/57 — Final Report — EUROCONTROL ‘Manual for Aerodrome Flight Information Service (AFIS)’ Edition 1.0 of 17.06.2010 — EUROCONTROL ‘Guidelines for Contingency Planning of Air Navigation Services (including Service Continuity)’ Edition 2.0 of 06.04.2009 — ‘Reference Guide to EUROCONTROL Guidelines for Contingency Planning of Air Navigation Services (including Service Continuity)’ Edition 2.0 of 06.04.2009 — EUROCONTROL ‘Common Format Letter of Agreement Between Air Traffic Services Units’ Edition 4.0 of 15.03.2012 — EUROCONTROL ‘Guidelines for the Application of European Coordination and Transfer Procedures’ Edition 1.0 of 25.10.2012 — Investigation Report C 2/2003 L ‘Incident between an airliner and airport maintenance vehicle at Kuusamo airport on 29 January 2003’ Issued by the Finnish Investigation Commission — Translation of the original Finnish report — Investigation Report AX001-1-2/02 published by the German Federal Bureau of Aircraft Accidents Investigation (BFU) in May 2004 regarding the mid-air collision between a Boeing 757- 200 and a Tupolev TU154M on 1 July 2002 near Überlingen, Germany — UK CAP 493 ‘Manual of Air Traffic Services’ TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 192 of 193 An agency of the European Union European Aviation Safety Agency NPA 2016-09(B) 2. References — Study on Aeroplane State Awareness during Go-Around (ASAGA) – Published in August 2013 by Bureau d'Enquêtes et d'Analyses (BEA) pour la Sécurité de l'Aviation civile TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 193 of 193 An agency of the European Union NPA 2016-09(A) Description: NPA 2016-09(A) Language: English Expiration date for 14/01/2016 comments: NPA number: NPA 2016-09(A) European Aviation Safety Agency: Ottoplatz 1, D-50679 Cologne, Germany - easa.europa.eu An agency of the European Union European Aviation Safety Agency Notice of Proposed Amendment 2016-09(A) Requirements for air traffic services RMT.0464 — 14.9.2016 EXECUTIVE SUMMARY This Notice of Proposed Amendment (NPA) addresses safety and regulatory coordination issues related to the provision of air traffic services (ATS). The main objective of this NPA is to maintain a high level of safety in the European Union (EU) air navigation system, in particular with regard to the provision of ATS. In order to achieve this objective, the proposal aims at: — transposing the relevant International Civil Aviation Organization (ICAO) provisions on ATS into the EU aviation regulatory framework, thus contributing to their uniform implementation throughout the EU, and supporting EU Member States in fulfilling their obligations stemming from the Chicago Convention; and — defining proportionate and cost-efficient rules. The NPA introduces a detailed set of provisions to be placed in the ‘ATM/ANS Common Requirements Regulation’, in particular in Annex IV thereto, and thus removes the existing provision referencing to ICAO Annexes. These provisions provide implementation of the Essential Requirements in Annex Vb 2.(c) to Regulation (EC) No 216/2008. It also proposes associated AMC and GM to facilitate the application by the affected stakeholders. In addition to the transposition of the ICAO provisions, this NPA proposes a number of measures related to the aerodrome flight information service (AFIS) as this is not explicitly addressed in the ICAO Standards and Recommended Practices (SARPs). In this way, this service is proposed to be regulated in the EU context, thus reducing the high diversity of the existing implementation across the EU Member States. In this context, Member States may decide not to provide ATS (ATC or AFIS) at smaller airfields, where the so-called ‘UNICOM stations’, not addressed by EU ATS rules, may be established to support local and, in particular, General Aviation activities. As this NPA and Regulation (EU) No 923/2012 (standardised rules of the air (SERA)) are closely interrelated, the NPA also proposes minor amendments to said Regulation, which was recently amended by Regulation (EU) 2016/1185. Safety recommendations submitted to the Agency are also addressed by this proposal. NPA 2016-09 is divided in two parts. The present sub-NPA(A) includes: — the procedural information pertaining to the regulatory proposal; — the explanatory note to the proposed amendments; and — the regulatory impact assessment. Applicability Process map Affected — Regulation (EU) 2016/1377; Concept paper: No regulations — the upcoming related ED Decision; Terms of Reference: 9.7.2014 and decisions: — Regulation (EU) No 923/2012; Rulemaking group: Yes — ED Decision 2013/013/R RIA type: Full Affected Member States; competent authorities; Technical consultation stakeholders: air navigation service providers; air during NPA drafting: No traffic controllers; aircraft operators; Duration of NPA consultation: 4 months professional organisations; trade unions; Review group: Yes pilots; passengers Focused consultation: Yes Driver/origin: Safety Publication date of the opinion: Q2/2017 Reference: Please refer to Section 4.3. of this NPA Publication date of the decision: Q4/2017 TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 1 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) Table of contents Table of contents 1. Procedural information ........................................................................................................................ 4 1.1. The rule development procedure............................................................................................................ 4 1.2. The structure of this NPA and related documents .................................................................................. 4 1.3. How to comment on this NPA ................................................................................................................. 5 1.4. The next steps in the procedure .............................................................................................................. 5 2. Explanatory note .................................................................................................................................. 6 2.1. Overview of the issues to be addressed .................................................................................................. 6 2.2. Objectives ................................................................................................................................................ 7 2.3. Summary of the regulatory impact assessment (RIA) ............................................................................. 7 2.4. Transposition of ICAO provisions into PART-ATS .................................................................................... 8 2.5. Interrelation with the SERA Regulation ................................................................................................. 10 2.6. AFIS requirements ................................................................................................................................. 11 2.7. Overview of the proposed amendments............................................................................................... 12 2.7.1. Amendments to the ATM/ANS Common Requirements Regulation and to the upcoming ED Decision issuing the related AMC/GM ..........................................................................................13 2.7.1.1. Amendments to the Regulation ................................................................................................13 2.7.1.2. Amendments to Annex I — Definitions .....................................................................................15 2.7.1.3. Amendments to Annex IV — Subpart A ‘Additional organisation requirements for providers of ATS’ ............................................................................................................................................16 2.7.1.3.1. Section 1 — General requirements ...........................................................................................16 2.7.1.3.2. Section 4 — Requirements for communications.......................................................................19 2.7.1.3.3. Section 5 — Requirements for information ..............................................................................22 2.7.1.4. Amendments to Annex IV — Subpart B ‘Technical requirements for providers of ATS’ ..........23 2.7.1.4.1. Section 1 — General ..................................................................................................................24 2.7.1.4.2. Section 2 — ATC service ............................................................................................................29 2.7.1.4.3. Section 3 — Flight information service .....................................................................................44 2.7.1.4.4. Section 4 — Alerting service ......................................................................................................48 2.7.1.5. Amendments to Annex V — Subpart A ‘Additional organisation requirements for providers of meteorological services (MET.OR)’ ...........................................................................................50 2.7.2. Amendments to the SERA Regulation ...........................................................................................50 2.7.3. Amendments to ED Decision 2013/013/R (AMC/GM to the SERA Regulation) ............................51 3. Regulatory impact assessment (RIA) ................................................................................................... 53 3.1. Problem definition ................................................................................................................................. 53 3.1.1. ATS regulatory framework.............................................................................................................53 3.1.1.1. The ICAO ATS regulatory context ..............................................................................................53 TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 2 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) Table of contents 3.1.1.2. The current EU ATS regulatory context .....................................................................................53 3.1.1.3. Transposing ICAO ATS provisions into the EU aviation safety regulatory framework ..............54 3.1.2. AFIS ................................................................................................................................................55 3.1.2.1. Introduction ...............................................................................................................................55 3.1.2.2. Current regulatory framework on AFIS .....................................................................................55 3.1.2.3. The EASA AFIS survey ................................................................................................................56 3.1.2.4. Issues to be addressed ..............................................................................................................58 3.1.2.5. Safety risk assessment ...............................................................................................................61 3.1.2.6. Who is affected? ........................................................................................................................63 3.1.2.7. Problem tree ..............................................................................................................................63 3.1.2.8. How could the issue/problem evolve ........................................................................................65 3.1.2.9. AFIS in third countries ...............................................................................................................65 3.2. Objectives .............................................................................................................................................. 67 3.3. Policy options......................................................................................................................................... 68 3.4. Analysis of impacts ................................................................................................................................ 69 3.4.1. Safety impacts ...............................................................................................................................69 3.4.2. Environmental impacts ..................................................................................................................70 3.4.3. Social impacts ................................................................................................................................70 3.4.4. Economic impacts ..........................................................................................................................70 3.4.5. General Aviation and proportionality issues .................................................................................72 3.4.6. ‘Better regulation’ and harmonisation impacts ............................................................................73 3.4.7. Open questions to stakeholders ....................................................................................................75 3.5. Comparison and conclusion .................................................................................................................. 76 3.6. Monitoring and ex post evaluation ....................................................................................................... 77 4. References ......................................................................................................................................... 79 4.1. Affected regulations .............................................................................................................................. 79 4.2. Affected AMC and GM ........................................................................................................................... 79 4.3. Reference documents............................................................................................................................ 79 TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 3 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 1. Procedural information 1. Procedural information 1.1. The rule development procedure The European Aviation Safety Agency (hereinafter referred to as the ‘Agency’) developed this NPA in line with Regulation (EC) No 216/20081 (hereinafter referred to as the ‘Basic Regulation’) and the Rulemaking Procedure2. This rulemaking activity is included in the Agency’s 5-year Rulemaking Programme under RMT.0464. The text of this NPA has been developed by the Agency, based on the inputs of the Rulemaking Group (RMG) for RMT.0464. It is hereby submitted for consultation of all interested parties3. The process map on the title page contains the major milestones of this rulemaking activity to date and provides an outlook of the timescales of the next steps. 1.2. The structure of this NPA and related documents NPA 2016-09(A) is structured as follows: — Chapter 1 contains the procedural information related to this task; — Chapter 2 (explanatory note) explains the core technical content; — Chapter 3 contains the regulatory impact assessment (RIA) showing which options were considered and what impacts were identified, thereby providing the detailed justification for this NPA; and — Chapter 4 contains a list of reference documents. NPA 2016-09(B) contains the proposed text for the new requirements (implementing rules (IRs), acceptable means of compliance (AMC), and guidance material (GM)). Additionally, for information purposes only, the Agency is providing the following documents on the webpage where the present NPA is published: — a table containing the comparisons between the ICAO Annex 11 provisions and the proposed text (hereinafter referred to as the ‘Annex 11 Checklist’); — a table containing the comparisons between the ICAO PANS ATM provisions and the proposed text (hereinafter referred to as the ‘PANS ATM Checklist’); and 1 Regulation (EC) No 216/2008 of the European Parliament and of the Council of 20 February 2008 on common rules in the field of civil aviation and establishing a European Aviation Safety Agency, and repealing Council Directive 91/670/EEC, Regulation (EC) No 1592/2002 and Directive 2004/36/EC (OJ L 79, 19.3.2008, p. 1) (http://eur-lex.europa.eu/legal- content/EN/TXT/?qid=1464170711619&uri=CELEX:32008R0216). 2 The Agency is bound to follow a structured rulemaking process as required by Article 52(1) of the Basic Regulation. Such a process has been adopted by the Agency’s Management Board (MB) and is referred to as the ‘Rulemaking Procedure’. See MB Decision No 18-2015 of 15 December 2015 replacing Decision 01/2012 concerning the procedure to be applied by the Agency for the issuing of opinions, certification Specifications and guidance material (http://www.easa.europa.eu/system/files/dfu/EASA%20MB%20Decision%2018-2015%20on%20Rulemaking%20Procedure.pdf). 3 In accordance with Article 52 of the Basic Regulation and Articles 6(3) and 7 of the Rulemaking Procedure. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 4 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 1. Procedural information — the ‘Summary of the survey on Aerodrome Flight Information Service’, including the analysis of the responses received to said survey issued by the Agency during 2015 to support the decision-making on regulatory activities concerning AFIS. 1.3. How to comment on this NPA Please submit your comments using the automated comment-response tool (CRT) available at http://hub.easa.europa.eu/crt/. The deadline for the submission of comments is 16 January 2017. Furthermore, it is important to be noted that throughout Chapter 2 (explanatory note) and Chapter 3 (RIA) there are issues on which the Agency explicitly invites stakeholders to answer to questions and express their opinion. The Agency is addressing said questions to stakeholders in order to receive further guidance during the consultation of this NPA with a view to gaining additional information and the opinion of a wider audience. 1.4. The next steps in the procedure Following the closing of the NPA public consultation period, the Agency will review all comments and perform, as necessary, a focused consultation which will consist of involving relevant technical experts in the review of the comments and in the drafting of the revised rule text. The outcome of the NPA public consultation, as well as of the focused consultation, will be reflected in a comment-response document (CRD). The Agency will publish the CRD concurrently with the opinion. The opinion, based on this NPA and on the outcome of the consultation, contains the proposed amendments to: — Regulation (EU) 2016/13774 (hereinafter referred to as the ‘ATM/ANS Common Requirements Regulation’). This Regulation is currently being reviewed by the European Commission and is expected to be reissued in due course; and — Regulation (EU) No 923/20125 as amended by Regulation (EU) 2016/1185 (hereinafter referred to as the ‘SERA Regulation’), and is submitted to the European Commission to be used as a technical basis in order to prepare an EU regulation. Following the adoption of the regulation, the Agency will issue a decision containing the related AMC and GM. 4 Commission Implementing Regulation (EU) 2016/1377 of 4 August 2016 laying down common requirements for service providers and the oversight in air traffic management/air navigation services and other air traffic management network functions, repealing Regulation (EC) No 482/2008, Implementing Regulations (EU) No 1034/2011 and (EU) No 1035/2011 and amending Regulation (EU) No 677/2011 (OJ L 226, 19.8.2016, p. 1) (http://eur-lex.europa.eu/legal- content/EN/TXT/?qid=1473425290921&uri=CELEX:32016R1377). 5 Commission Implementing Regulation (EU) No 923/2012 of 26 September 2012 laying down the common rules of the air and operational provisions regarding services and procedures in air navigation and amending Implementing Regulation (EU) No 1035/2011 and Regulations (EC) No 1265/2007, (EC) No 1794/2006, (EC) No 730/2006, (EC)No 1033/2006 and (EU) No 255/2010 (OJ L 281, 13.10.2012, p. 1) (http://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1465217255874&uri=CELEX:32012R0923). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 5 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note 2. Explanatory note This NPA proposes a set of rules for the provision of ATS, which include air traffic control (ATC) service, flight information service (FIS) and alerting service. 2.1. Overview of the issues to be addressed Since decades, ATS have been provided worldwide in accordance with the SARPs included in Annex 2, Annex 10 Volume II, and in particular in Annex 11 to the Chicago Convention. In order to establish more detailed guidance on the implementation of the ATS provisions established in the Annexes, which are often expressed in the form of principles, ICAO publishes and maintains a set of related documents. The most relevant of such documents for the purposes of ATS is Doc 4444 ‘Procedures for Air Navigation Services — Air Traffic Management’ (hereinafter referred to as the ‘PANS ATM’), which specifies, in greater detail than in the aforementioned Annexes, the actual procedures to be applied by the relevant units in providing the various ATS to air traffic. At the time of publication of this NPA, the provision of ATS in the EU is regulated primarily by Commission Implementing Regulation (EU) No 1035/20116 (Chapter 4 of Annex II), which, with a direct reference, stipulates that ATS providers shall demonstrate to apply working methods and operating procedures compliant with those in ICAO Annex 10 Volume II and Annex 11, as well as with provisions in the SERA Regulation. The latter transposed, inter alia, the relevant ICAO Annex 2 into the EU legislation with the purpose of establishing standardised European rules of the air. As of 1 January 2019, Regulation (EU) No 1035/2011 will be repealed by the ATM/ANS Common Requirements Regulation, which establishes, under a single regulatory source, the requirements for the provision and oversight of ATM/ANS, including ATS. This new Regulation aims at ensuring full implementation of the principles of the Basic Regulation and of the relevant Essential Requirements in Annex Vb thereto; in the case of ATS, the Essential Requirements are included in Chapter 2.(c) of Annex Vb. Within the structure of the ATM/ANS Common Requirements Regulation, Annex IV ‘PART-ATS’ contains the requirements for the provision of ATS. Subpart A of this Annex establishes organisation requirements specific for the ATS providers, in addition to those applicable to all ATM/ANS providers defined in Annex II to the aforementioned Regulation. Subpart B of Annex IV contains the technical requirements for the provision of ATS. In the absence of detailed and comprehensive rules in this field, and in anticipation of the outcome of this regulatory activity as per this NPA, technical requirements in Subpart B are still established by mere reference to the SERA Regulation and to the working methods and operation procedures in ICAO Annex 10 Volume II and Annex 11, as was the case for Regulation (EU) No 1035/2011. This NPA proposes to close the intentional gap detailed above, by performing the necessary transposition of ICAO provisions into the EU regulatory framework. This step, although inevitable as elementary for setting the regulatory foundation within the EU framework and for meeting the obligations stemming from the Basic Regulation, particularly with regard to the Essential Requirements in Chapter 2.(c) of Annex Vb thereto, is furthermore beneficial as: 6 Commission Implementing Regulation (EU) No 1035/2011 of 17 October 2011 laying down common requirements for the provision of air navigation services and amending Regulations (EC) No 482/2008 and (EU) No 691/2010 (OJ L 271, 18.10.2011, p. 23) (http://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1465218526795&uri=CELEX:32011R1035). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 6 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note — the content of the subject ICAO Annexes alone is not sufficiently detailed to fully satisfy the aforementioned Essential Requirements; — the formulation in passive voice of many ICAO SARPs does not always fit with the regulatory framework established by the Basic Regulation and by the ATM/ANS Common Requirements Regulation, which require the explicit allocation of the ‘active’ responsibility to undertake action; and — it fosters the harmonisation of ATS provision throughout the EU, as it will lead to a reduction of the differences filed under the Chicago Convention. Therefore, this NPA proposes to replace the provision with the references to ICAO Annexes, as in Subpart B of Annex IV, with a detailed and comprehensive set of measures adapted to the EU regulatory framework and operational context (IRs, AMC, and GM), derived mainly from the ICAO relevant provisions, not limited to those in Annex 10 Volume II and Annex 11, but considering also the relevant content of other ICAO Documents, primarily PANS ATM. 2.2. Objectives The overall objectives of the EASA system are defined in Article 2 of the Basic Regulation. This proposal will contribute to the achievement of the overall objectives by addressing the issues outlined in Section 2.1. The specific objective of this proposal is to ensure that ATS are provided safely across the EU. In order to achieve this objective, the proposal aims at: — transposing the relevant ICAO provisions on ATS, thus contributing to their harmonised implementation, which will serve as a basis for EU aviation law; — establishing a sufficient level of harmonisation throughout the EU, based on mandatory and flexible requirements; and — defining proportionate and cost-efficient rules. 2.3. Summary of the regulatory impact assessment (RIA) For the reasons explained in Section 3.1.1, the Agency did not perform a detailed RIA on the establishment of EU ATS requirements through the transposition of the ICAO relevant material, unlike what has happened concerning the proposed introduction of provisions for AFIS. The RIA, which is available in Chapter 3, considers the impact analysis of the following options: Option 0 ‘No policy change’: No change to the actual EU rules; risks remain as outlined in the issue analysis. Option 1 ‘Essential and flexible AFIS rules’: Definition of AFIS and its essential requirements consistent with existing ICAO ATS principles and EU legislation and practices, while ensuring certain flexibility. Option 2 ‘Comprehensive and prescriptive AFIS rules’: Definition of AFIS and its complete mandatory requirements consistent with existing ICAO ATS principles and EU legislation. The selected Option 1 establishes clarity on the provision of AFIS by proposing an explicit and balanced set of essential rules (IRs, AMC, and GM), which are flexible to the extent possible within the ATS context to accommodate local needs. The proposed rules are based on relevant ICAO principles and on TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 7 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note the EU legislation applicable to ATS, as well as on the existing practice throughout EU Member States. The inherent proportionality and flexibility of the proposal enables the selection of the appropriate service or facilitation for aviation operations at aerodromes, without generating limitations when no ATS (ATC or AFIS) is considered suitable or convenient. The resulting harmonisation of AFIS would bring safety benefits for aircraft operators and pilots as it will establish uniform operational principles throughout the EU, reducing thus the possibility for misinterpretation of the operational characteristics of the service provided. 2.4. Transposition of ICAO provisions into PART-ATS In compliance with the task of the Agency to assist the EU Member States in fulfilling their obligations under the Chicago Convention, when developing rules for the implementation of the principles and the Essential Requirements of the Basic Regulation, the relevant ICAO provisions needed to be transposed into the EU legislation, with the necessary adaptations. While this has been duly and nearly exhaustively performed in other technical domains by now (operations (OPS), flight crew licensing (FCL), aerodromes (ADR) etc.), and as explained in Section 2.1 above and 3.1.2 below, this approach also needs to be followed for the establishment of PART-ATS. In order to select the provisions suitable for transposition as EU ATS requirements, the Agency, supported by RMG.0464, performed a very detailed and comprehensive analysis of the content of the following documents: — ICAO Annex 11 including all the amendments up to and including No 49. This NPA does not include the content of Amendment No 50, introduced with the ICAO letter AN 13/13.1-16/39 of 11 April 2016, because the provisions subject to modifications have not been selected for transposition into ATS requirements with this NPA. The subjects dealt with by Amendment No 50, namely:  performance-based communication and surveillance (PBCS) to revise the existing provision regarding required communication performance (RCP);  procedure design and oversight; and  fatigue management for air traffic controllers (ATCOs), will be addressed by the Agency under separate rulemaking tasks; — PANS ATM, including the modifications introduced with the ICAO Working Paper AN-WP/9014 dated 18 February 2016, approved by the ICAO Air Navigation Commission and resulting in Amendment 7 to PANS ATM; — Doc 7030 EUR; — ICAO Annex 10 Volume II; and — other ATS-relevant ICAO and EUROCONTROL documents, listed in Section 4.3. An analysis of the differences to Standards of Annex 11 notified by the EU Members States in accordance with Article 38 of the Chicago Convention was also performed, with the objective of identifying commonalities in such differences and, when appropriate, formulating proposals for common EU differences from the ICAO provisions. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 8 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note As a general principle followed in drafting this proposal, ICAO Standards elected for transposition are proposed as IRs in recognition of their status under the Chicago Convention. The placement of the necessary Recommended Practices from the ICAO Annexes, PANS ATM and other material selected for transposition into IRs, AMC, and GM is determined on a case-by-case basis, according to their relevance in the given context, so that those parts where full harmonisation is desired were transposed as IRs, whereas the majority of the material is classified as AMC/GM. The Agency decided not to transpose those PANS ATM provisions which were assessed to be better suited as guidance contained in operations manuals rather than as regulatory material and did not require full harmonisation as they were neither affecting interoperability with airspace users nor safety to a great extent. The proposed transposition introduces a few differences from the original ICAO Standards; such differences are highlighted in the ‘Annex 11 Checklist’. As the original ICAO provisions are often formulated with the use of passive voice, the selected measures were organised and, when necessary, textually modified to allocate the responsibility for action unambiguously (to Member State, competent authority, ATS provider, ATS unit, ATCO/FIS/AFIS officer, etc.) in accordance with the EU regulatory drafting practice and, in particular, with the structure of the ATM/ANS Common Requirements Regulation, thus improving clarity. The transposition was performed with a view to ensuring that measures are fully consistent with the relevant EU legislation, in particular with the ATM/ANS Common Requirements Regulation and with the SERA Regulation (see Section 2.5. ‘Interrelation with the SERA Regulation’). The detailed analysis of Annex 11 allowed the identification of provisions which, in the opinion of the Agency and of RMG.0464, are not within the scope of PART-ATS as established by the Terms of Reference for RMT.04647, but which would need to be considered and, if deemed appropriate, transposed by other EU regulatory activities, in particular those concerning SERA, Part-AIS, and Part-ASD. For example, provisions addressing both pilots and ATS units or ATCOs/FIS officers/AFIS officers, such as those related to flight plans in Section 4.4. of PANS ATM, or those related to controller-pilot data link communications (CPDLC) in Chapter 14 of PANS ATM, are by their nature better located in SERA; SARPs in Section 2.5 of Annex 11 concerning the designation of airspace and controlled aerodromes for the ATS provision purposes are considered suitable for transposition in PART-ASD. The Agency ensured and will continue to ensure appropriate coordination between the affected RMTs for this purpose. When deemed necessary, a few amendments to the ATM/ANS Common Requirements Regulation or to the SERA Regulation are proposed by this NPA in order to ensure full alignment with the proposed provisions in PART-ATS. The RMG.0464 members indicated the difficulties encountered in the transposition exercise, in particular those generated by the difference between the two regulatory systems (EU and ICAO). Such difficulties were faced in particular when performing the transposition of Procedures from PANS ATM, as in the context of this document the use of action verbs such as ‘shall’ and ‘should’ does not necessarily have the same meaning as that of these verbs in the EU regulatory framework. In the ICAO context, PANS are frequently designed to be flexible, in order to accommodate specific scenarios and environments. On the other hand, sometimes ICAO provisions originally destined as Standards have been relocated in Recommended Practices due to lack of agreement on binding implementation. 7 http://www.easa.europa.eu/system/files/dfu/ToR%20RMT.0464%20Issue%201.pdf TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 9 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note Despite the very careful assessment and the best effort to ensure an effective transposition, the experts considered that the legal instruments available (IR, AMC, and GM) in the EU regulatory context could not always replicate the granularity and the nuances fit for a PANS, resulting in an either over- regulating or under-regulating provision. For these reasons, the RMG members requested the Agency to provide these explanations, so that the readers are aware of the limitations of the transposition exercise. In order to facilitate the readers in tracking the transposition of ICAO provisions, at the bottom of each proposed measure in this NPA, there is the indication of the ICAO provision from which it originated. In addition, the Agency has developed and issues as information material, on the webpage where the present NPA is published, the complete Annex 11 Checklist and PANS ATM Checklist, which provide a general cross-referencing between the ICAO original and the proposed regulation. For each provision of these ICAO documents, the checklists indicate the proposed transposition as ATS requirement within this NPA or the reason for not having been transposed (e.g. relevant other ATM/ANS-related or SERA regulatory activities, already transposed or covered by other existing EU requirements). 2.5. Interrelation with the SERA Regulation The provision of ATS is closely interrelated with the application of the rules of the air. In the EU context, such rules are established by the SERA Regulation and the associated AMC/GM of ED Decision 2013/013/R8, which are based mainly on the transposition of relevant provisions from various ICAO documents, including Annex 2, and partial transposition of Annex 3, Annex 10 Volume II, Annex 11 and PANS ATM. With the introduction of detailed and comprehensive ATS requirements within Annex IV (PART-ATS) to the ATM/ANS Common Requirements Regulation, the existing reference to the SERA Regulation is removed. The proposed introduction of recitals in both the SERA Regulation and the ATM/ANS Common Requirements Regulation, as explained in Sections 2.7.1.1 and 2.7.2 below, indicate that these two Regulations have to be read and applied in conjunction with each other. The regulatory activities for the issue of the SERA regulatory package and of its successive amendments were undertaken far in advance of the initiation of RMT.0464. A number of provisions from Annex 11 and PANS ATM, when envisaging collective action for both aircrew and ATS, were transposed as EU measures, in the SERA Regulation. When performing the analysis of Annex 11 and PANS ATM, the Agency found that some of those ICAO provisions already transposed as IRs within the SERA Regulation are also fundamental in the context of Annex IV (PART-ATS), as they would ensure the completeness and the coherence of the EU ATS requirements. Moreover, their presence in PART-ATS would facilitate the transposition of other ICAO provisions considered to be suitable and necessary as AMC or GM, while their transposition within the SERA regulatory package was not considered appropriate, as they address only ATS provision and do not envisage a collective aircrew/ATS action. After careful consideration, the Agency opted to propose the duplication of a number of relevant SERA requirements as EU ATS requirements to ensure the completeness of the text and to improve readability. In this context, the Agency also identified the need to amend the original text of a limited number of SERA provisions duplicated as ATS provisions. The rationale behind these proposed amendments and the proposed text are included in Sections 2.7.2, 2.7.3 of this NPA 2016-09(A) and in 8 http://www.easa.europa.eu/document-library/agency-decisions/ed-decision-2013013r TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 10 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note Sections 1.2 and 1.4 of NPA 2016-09(B) respectively. The Agency is committed to ensure full consistency between the duplicated provisions and between the respective AMC/GM in the two regulatory packages throughout the development of this Rulemaking Task as well as through the future rules maintenance activities. 2.6. AFIS requirements AFIS, being an integral part of ATS, has been introduced into the EU regulatory framework by Regulation (EC) No 550/20049. With this, AFIS is currently subject to the same general requirements as a full ATS service, including certification/declaration obligations, which may appear disproportionate, especially for small local airfields. At the same time, and as described in Section 3.1.2.2 below in more details, the current EU regulatory framework, referring to ICAO Annex 10 Volume II and Annex 11, does not include explicit and specific requirements for the provision of AFIS, for which Member States have developed national models with very different characteristics. Taking into account the above- mentioned deficiencies, as well as identified safety issues, the Agency aims at providing clearer and more proportionate rules for the provisions of AFIS within the scope of ATS and at harmonising, to an adequate extent, this type of ATS throughout the EU. In addition, it is clarified that not every aerodrome operation, particularly at the smaller end, is subject to ATS/AFIS and related provisions. Therefore, a set of provisions which better define and explicitly address AFIS, and which delineate the common mandatory elements of this service, is proposed. These provisions are built upon the ICAO FIS principles, applied and adapted, as necessary, to the aerodrome context. The proposal was developed also on the basis of the outcome of the EASA AFIS Survey (see Section 3.1.2.3 below), issued by the Agency in 2015, to which stakeholders from the very large part of EASA Member States responded. With the approach adopted, it is made clear that, except when dictated otherwise, or when flexibility is explicitly allowed in the provisions, requirements addressed to ATS providers are intended to include also the AFIS providers, subject to conditions established for their certification or declaration. Moreover, the proposed provisions explicitly indicate the applicability of technical requirements, where appropriate, to the AFIS unit, when the originating ICAO provisions were only considering ATC units and/or flight information centres (FICs). In order to ensure proportionality and to avert negative impacts on local and, in particular, General Aviation activities at small airfields, GM is proposed describing that States may also allow the operation of aeronautical stations/facilities other than ATS units at selected aerodromes. These units, named UNICOM stations, are not intended to provide ATS, but to facilitate aviation activities. Such type of facilities are commonly found across the EU and varyingly they are referred to as ‘Air–Ground’ radio, ‘Flugleiter’ or by some other name, though providing a facility that has some similarities with AFIS, but is not guaranteed by common ATS standards and is often provided by non-professional staff. The definition of requirements for these UNICOM stations, if considered appropriate at all, is left to the initiative of the Member States as such stations are not included in the scope of ATS. Assuming that smaller airfields would be addressed in the UNICOM way detailed above — hence not be subject to the AFIS rules at stake — and given the wide variety of sizes of the actual AFIS aerodromes and their operation, the Agency recognises the importance of ensuring the highest most 9 Regulation (EC) No 550/2004 of the European Parliament and of the Council of 10 March 2004 on the provision of air navigation services in the single European sky (the service provision Regulation) (OJ L 96, 31.3.2004, p. 10) (http://eur-lex.europa.eu/legal- content/EN/TXT/?qid=1467113381244&uri=CELEX:32004R0550). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 11 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note adequate level of proportionality and value added through the future rules on AFIS. In this light, it is particularly important for the Agency to receive feedback on this subject through the consultation of this NPA. Therefore, the Agency kindly invites its stakeholders to clearly indicate, as appropriate, the need as well as the ways to potentially add further clarity to the proposed AFIS requirements and enhance their level of proportionality. In addition to the lack of uniformity in the respective responsibilities of pilots and AFIS officers in different States, the lack of common phraseology has been an issue affecting the safety and appropriateness of operations at AFIS aerodromes, serving also international traffic. It was therefore considered that the explicit inclusion of common air–ground phraseologies supporting the provision of AFIS would be beneficial. As air–ground ATS phraseology is located in the SERA Regulation, the Agency will ensure that such specific phraseology is developed under the rules maintenance mechanism for the SERA Regulation during 2016–2017, based on existing ICAO phraseology, the Eurocontrol AFIS manual and national AFIS phraseologies. In the absence of an explicit regulatory mandate in the Basic Regulation, this proposal does not include a set of provisions addressing the qualification and training of AFIS officers. It should be kept in mind that ATM/ANS.OR.B.005 ‘Management system’ in Annex II to the ATM/ANS Common Requirements Regulation stipulates that providers (and therefore also AFIS providers) shall ensure that their personnel are trained and competent to perform their duties in a safe, efficient, continuous and sustainable manner. The establishment of explicit AFIS requirements is considered as an enabler for the harmonisation of AFIS training and qualification schemes, which themselves will help maintain flexibility taking into account the local characteristics of such service provision. Within its activities concerning the consideration of human performance in the context of ATM/ANS, the Agency will further carefully evaluate whether any specific and detailed EU regulation is necessary. 2.7. Overview of the proposed amendments This NPA puts forward amendments to: — the ATM/ANS Common Requirements Regulation and the Annexes thereto, and more specifically to:  the recitals and articles;  Annex I ‘Definitions’;  Annex IV ‘PART-ATS’; and  Annex V ‘PART-MET’; — the SERA Regulation, and more specifically to:  the recitals thereof;  definition 57. of ‘controlled aerodrome’; and  the Annex thereto, and more specifically: o SERA.8005; o SERA.8012; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 12 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note o SERA.8015; o SERA.9005; and o SERA.14095; — the upcoming ED Decision issuing AMC/GM to the ATM/ANS Common Requirements Regulation; and — ED Decision 2013/013/R (AMC/GM to the SERA Regulation), by introducing relevant GM. 2.7.1. Amendments to the ATM/ANS Common Requirements Regulation and to the upcoming ED Decision issuing the related AMC/GM This section contains the explanatory notes concerning the IRs amending the ATM/ANS Common Requirements Regulation, which are included in Section 1.1 of NPA 2016-09(B), and more specifically: — a recital and general requirements (three new articles) applicable to Member States; — definitions relevant to the provision of ATS, transposed within Annex I; — specific organisation requirements for ATS providers, transposed within Section 1 in addition to the already existing requirements and within the newly established Sections 4 and 5 of Subpart A of Annex IV; — technical requirements for ATS providers, transposed within Subpart B of Annex IV by repealing the current content of Section 1 and by replacing it with 4 Sections, as follows:  Section 1 — General  Section 2 — Air traffic control service  Section 3 — Flight information service  Section 4 — Alerting service — amendments to MET.OR.242 ‘Information to be provided to air traffic services units’ and MET.OR.245 ‘Meteorological watch and other information’ included in Annex V ‘Part-MET’. This Section also integrates the explanatory notes for the AMC and GM to the IRs described above; such AMC and GM are included in Section 1.3 of NPA 2016-09(B). 2.7.1.1. Amendments to the Regulation The Agency proposes the introduction of a recital which underlines the need to consider the strong interrelation and complementarity between the requirements in the SERA Regulation and those in PART-ATS. The analysis of Chapter 2 of Annex 11 led to the identification of ATS provisions according to which, even in the EU regulatory context, the responsibility is to be allocated to the Member States, as said provisions envisage the involvement of entities which are not under the scope of the Basic Regulation (e.g. the military); therefore, these provisions are proposed for transposition as articles of the ATM/ANS Common Requirements Regulation. Article 3(1b), resulting from the transposition of Section 2.4 of Annex 11, stipulates that the responsibility for determining the need for the provision of ATS lies with the Member States, and TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 13 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note indicates the factors which need to be taken into account in determining that. It clarifies that the need for the provision of ATS is to be determined regardless of the carriage of ACAS system by aircraft. GM1 to Article 3(1b) better describes such factors; it is derived from the Note to Section 2.4.1 of Annex 11 and further complemented by additional elements identified by the Agency. GM2 to Article 3(1b) pertains to the possibility for Member States to allow the facilitation of aviation operations at those aerodromes where the provision of ATS has not been determined as necessary at any time. In this case, aeronautical stations named UNICOM, may be established under specific conditions prescribed by the Member States. These UNICOM, which are not to be considered as units providing any ATS and therefore are not subject to the EU ATS regulatory framework, may operate in airspace designated for the provision of FIS, but only where the obligation for two-way radio communication with the responsible FIC is not established. Article 3(1c), which transposes the content of Section 2.17.3.2 of Annex 11, requires the Member States to warrant that particular procedures are established between military entities and the ATS with regard to the information exchange on aircraft potentially subject to an interception. These procedures have to be designed with the purpose of minimising the need for interception and of assisting aircraft as necessary. The provision is closely linked with provisions ATS.OR.115 and ATS.TR.120, transposed from the same section of Annex 11 and establishing the requirements enabling the prompt communication between ATS units and relevant military entities, allowing the required flow of flight plan information and flight data for identification purposes. Article 3(1d) concerns the coordination of activities which could potentially prove hazardous to the civil traffic, including but not limited to those activities that may be undertaken by the military. The provision, which is an adapted transposition of Sections 2.18.1 and 2.18.3 on Annex 11, requires the Member States to establish arrangements between all affected parties, including the ATS providers, for the timely coordination of such activities and for their notification to all concerned. In accordance with the principle established in Article 1(3) of Regulation (EU) No 551/200410, the article clarifies that the arrangements for the coordination and the notification of this type of activities, when taking place within the airspace over the high seas, shall be established by the Member State which has accepted the responsibility to provide ATS therein. GM2 to Article 3(1d) refers to ICAO Doc 9554 ‘Manual Concerning Safety Measures Relating to Military Activities Potentially Hazardous to Civil Aircraft Operations’, including detailed guidance on the coordination subject to the provision. Point (c) of Article 3(1d), transposed from Section 2.18.5 of Annex 11, requires the Member States to undertake appropriate actions to prevent any negative effect of laser beam emissions on the flight operations. This is a safety issue for which there is evidence of an increase of occurrence reports. The Agency proposes to allocate the responsibility for action to the Member States because of the nature of the original ICAO provision, which is not specifically attributed to service providers or any other 10 Regulation (EC) No 551/2004 of the European Parliament and of the Council of 10 March 2004 on the organisation and use of the airspace in the single European sky (the airspace Regulation) (OJ L 96, 31.3.2004, p. 20) (http://eur-lex.europa.eu/legal- content/EN/TXT/?qid=1465287212157&uri=CELEX:32004R0551). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 14 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note regulated entity. It is to be noted that Article 9(c) of Regulation (EU) No 139/201411 requires the Member States to ensure that ‘consultations are conducted with regard to human activities and land use such as (…). (…) the use of hazardous, confusing and misleading lights’, including lasers. Such requirement, however, does not seem to fully address the safety issue in question and the relevant ICAO provisions. In this light, in order to determine the best course of action, the Agency invites its stakeholders to: — comment on the need to include this provision in the EU regulatory framework; — in case the proposal is considered to be appropriate and necessary, comment as to whether the ATM/ANS Common Requirements Regulation is the most appropriate place to include such requirement, or if it should be included in a different regulation (existing or future); and — provide information on the arrangements at State level, in particular as regards the allocation of responsibilities. 2.7.1.2. Amendments to Annex I — Definitions In order to clarify the meaning of the various terms related to PART-ATS introduced by this NPA in the ATM/ANS Common Requirements Regulation, it is proposed to amend Annex I thereto to include the necessary definitions. The proposed definitions, selected from the relevant ICAO Annexes (mainly Annex 11) and from PANS ATM, are fully consistent, with the exception of the definition of ‘controlled aerodrome’, with the definitions set in the SERA Regulation and in its successive amendments introduced with Regulation (EU) 2016/1185, as well as with definitions and requirements included in the ATM/ANS Common Requirements Regulation, of which they will become integral part. For a number of definitions and when deemed appropriate, GM is proposed for better clarification, derived from the notes associated with the ICAO definitions from which they are transposed. The Agency proposes a definition of ‘controlled aerodrome’ which is different from that in the SERA Regulation. The definition aims to adhere to the principle laid down in Article 8.1 of Regulation (EC) No 550/2004, stipulating: ‘Member States shall ensure the provision of air traffic services on an exclusive basis within specific airspace blocks in respect of the airspace under their responsibility. For this purpose, Member States shall designate an air traffic service provider holding a valid certificate in the Community’. This principle is implemented in the regulatory proposals for PART-ATS (in this NPA) and the forthcoming NPA on Part-ASD to be published in the course of 2016 in the context of the regulatory activities of RMT.0445. With this proposed amendment, it is clarified that in presence of an aerodrome where ATS is provided, including controlled aerodromes, it is expected to have at all times an associated airspace and the designation of a provider in charge of rendering the services. The necessity for designating the airspace around a controlled aerodrome derives also from the definition of ‘aerodrome traffic’ in the SERA Regulation (and proposed with this NPA for inclusion in Annex I to the ATM/ANS Common Requirements Regulation) to which ATC service is provided at 11 Commission Regulation (EU) No 139/2014 of 12 February 2014 laying down requirements and administrative procedures related to aerodromes pursuant to Regulation (EC) No 216/2008 of the European Parliament and of the Council (OJ L 44, 14.2.2014, p. 1) (http://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1465287446104&uri=CELEX:32014R0139). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 15 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note controlled aerodromes. Aerodrome traffic is defined as ‘all traffic on the manoeuvring area of an aerodrome and all aircraft flying in the vicinity of an aerodrome. An aircraft operating in the vicinity of an aerodrome includes but is not limited to aircraft entering or leaving an aerodrome traffic circuit’. The proposed definition of ‘controlled aerodrome’ reinstitutes adherence to the original ICAO Annex 11 definition but disregards the associated Note. Such Note, while allowing for flexibility in the decision to designate a control zone associated with a controlled aerodrome, is not consistent with the aforementioned principle of Regulation (EC) No 550/2004. Consequently, it is proposed to amend the definition of ‘controlled aerodrome’ as in point 57. of Article 2 of the SERA Regulation, accordingly. In addition, the Agency proposes to amend the definition of ‘aerodrome flight information service’ established in point 6. of Annex I to the ATM/ANS Common Requirements Regulation. The new definition, which does not contradict the existing, clarifies that AFIS is a service which is to be delivered by a provider designated in accordance with the relevant Single European Sky legislation. The associated GM explains the difference between AFIS, which is integral part of ATS and which is to be provided in accordance with the applicable EU legislation, and UNICOM, which is not under the ATS scope and therefore requires neither certification nor designation, and may be established on the basis of national rules. 2.7.1.3. Amendments to Annex IV — Subpart A ‘Additional organisation requirements for providers of ATS’ The amendments proposed to Subpart A of Annex IV complement the existing provisions in Section 1 ‘General requirements’ and establish the new Sections 4 ‘Requirements for communications’ and 5 ‘Requirements for Information’. These organisation requirements are applicable to all ATS providers, including AFIS providers, except when flexibility is explicitly allowed or when the provisions address the provider of a specific ATS (e.g. ATC). 2.7.1.3.1. Section 1 — General requirements ATS.OR.110 requires the providers of ATS at aerodromes to establish arrangements with the operators of those aerodromes to define and coordinate the respective responsibilities and procedures concerning the services provided, as well as to set the necessary information and data exchange. This provision mirrors the corresponding requirement ADR.OR.C.005(b)(1) in Regulation (EU) No 139/2014 addressing the aerodrome operator. A set of AMC is proposed to address in detail the most important aspects to be defined by these arrangements, in particular the establishment of identification of standard taxi routes (in AMC1 ATS.OR.110), the coordination for low visibility operations (in AMC3 ATS.OR.110), and the exchange of information on the safe use of the manoeuvring area (in AMC6 ATS.OR.110) which could lead to the closure of operations on parts of such area. AMC3 ATS.OR.110 addresses the coordination with the provider(s) of apron management services, by establishing the elements which are to be coordinated. This AMC mirrors the content of the draft provision ADR.OPS.D.020, within the requirements for apron management services published with Opinion 02/201412, which proposes the amendment of Regulation (EU) No 139/2014. This Opinion is currently under the comitology process. 12 http://www.easa.europa.eu/document-library/opinions/opinion-022014 TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 16 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note ATS.OR.115, which transposes part of the content of Section 2.17.3.1 of Annex 11, is to be read in relation to Article 3(1c) and to ATS.TR.120; it establishes the obligation for the ATS providers, with the related conditions, to ensure that information on the flight plans and the flight data possessed by ATS units under their responsibility are made available to the relevant military entities, to facilitate the identification of aircraft. In order to ensure that they deliver services which meet the applicable requirements, ATM/ANS.OR.B.005(f) in Annex III requires the ATS providers to establish formal interfaces with the providers of other relevant services. This requirement covers, inter alia, the obligation for the ATS provider to establish a formal agreement with the providers of meteorological services for the provision of meteorological information and products. While the provision of meteorological information to ATS units is addressed in Annex V (Part-MET), as well as in Section 5 ‘Requirements for information’ of Subpart A, ATS.OR.120, which transposes the content of Section 2.20 of Annex 11, requires the ATS provider to establish arrangements allowing ATS personnel to report to the relevant meteorological service provider specific meteorological information or elements. Such information or elements could be directly observed by ATS personnel or reported to ATS units by aircraft. Particular emphasis is drawn to the necessary coordination between ATS and meteorological services to ensure consistency as regards the issue of messages concerning volcanic ash. ATS.OR.125 has to be read in the context of the requirements proposed by the Agency with NPA 2016-02 ‘Technical requirements and operational procedures for aeronautical information services and aeronautical information management’13. It transposes the principle in Section 2.1.4 of Annex 11, and establishes the obligation for ATS providers to make available to the relevant aeronautical information services (AIS) provider the aeronautical information concerning the services under their responsibility. It further details the elements of information which have to be timely reported, replicating those in Section 2.21.1 of Annex 11, and requires the ATS providers to appropriately coordinate with the AIS provider for the timely provision and promulgation of information concerning changes to the air navigation system for which they are responsible, before such changes are introduced. GM2 ATS.OR.125(a) indicates that the set of information concerning AFIS provision and the processes for the delivery of such information to the AIS provider are identical to those established for aerodrome ATC service. GM3 ATS.OR.125(a) proposes that information regarding the availability of UNICOM, even though such stations are not providing ATS, are also published in the appropriate section of the AIP, and lists the elements of information concerned. ATS.OR.130, established on the basis of the provisions in Section 2.25 of Annex 11, addresses the time in the provision of ATS and has to be read in conjunction with SERA.3401 of the SERA Regulation. It specifies the time-related information to be displayed at ATS units, and the location of the clocks indicating the time within the ATS operational rooms. Detailed rules are provided as far as the check of the clocks are concerned, in order to ensure that this information is accurate and aligned as much as possible amongst all ATS units. For this purpose, it is required that the correct timing for the clocks’ checks is obtained from a standard time station, or from another unit which obtained the check from such a station. 13 https://www.easa.europa.eu/document-library/notices-of-proposed-amendment/npa-2016-02 TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 17 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note The general requirement for ATM/ANS providers to develop contingency plans in the case of events which result in significant degradation or interruption of their operations is established in ATM/ANS.OR.A.070 of Annex III. ATS.OR.135 adheres to this principle but, responding to the provisions in Section 2.30 of Annex 11, stipulates that ATS providers develop such plans in close coordination with neighbouring ATS providers and with the airspace users concerned. With GM1 ATS.OR.135, the Agency reproduces the consideration as in Section 15.6 of PANS ATM about the fact that detailed procedures for the various types of contingencies could not be developed, as any contingency may develop subject to a number of circumstances which would make it unique. However, following the analysis of ICAO documents, the Agency proposes guidance on specific types of contingencies. GM2 ATS.OR.135, transposed from Sections 8.8.6 and 15.6.1 of PANS ATM, indicates actions to be undertaken for radiocommunication contingencies in ATC provision, while GM3 ATS.OR.135 includes guidance for ATS units in case of reported or forecast volcanic ash cloud. The general requirement for ATM/ANS providers to report to the competent authority and to the organisation responsible for the design of system and constituents, any malfunction, technical defect, exceedance of technical limitations, occurrence, or other irregular circumstance that has or may have endangered the safety of services is set in ATM/ANS.OR.A.070(b) of Annex III, for occurrence investigation purposes. ATS.OR.140 aims at the quick mitigation of malfunctions of communication, navigation and surveillance systems which may impact the safety and efficiency of flights. For this purpose, the ATS providers shall establish arrangements through which the units under their responsibility have to notify without delay such malfunctions, so that appropriate action can be undertaken. This provision, transposed from Section 4.14 of PANS ATM, was originally addressing only ATC units; by virtue of the potential safety impact of a failure of communication, navigation and surveillance systems on the services provided by FIC and AFIS units, the Agency proposes to extend its applicability to all ATS units. ATS.OR.145 concerns specific organisation requirements related to the provision of ATC. Point (a), transposed from Section 3.3.2 of Annex 11, requires that all the relevant information and control data concerned with the progress of flights are adequately displayed to controllers, to accomplish the respective tasks. AMC1 ATS.OR.145(a), including selected provisions from PANS ATM Sections 4.13.2 and 4.13.3, defines the sort of information and the arrangements necessary to enable the controllers to have a complete and up-to-date representation of the traffic situation and of the airspace, or the aerodrome, within which they are responsible to provide services. GM2 ATS.OR.145 further details additional categories of information the availability of which to controllers is considered desirable. Point (b) requires the providers to join and contribute to the European Reduced Vertical Separation Minima (RVSM) Monitoring programme, led by the established European Regional Monitoring Agency, as stipulated under Section 3.3.5.1 of Annex 11. ATS.OR.150, which is to be read in conjunction with ATS.TR.230, also addresses only providers of ATC service, which are required to establish in letters of agreement and operation manuals, as appropriate, the procedures for the coordination and transfer of responsibility for controlled flights as well as for the transfer of air–ground communications of aircraft. GM1 ATS.OR.150(b), derived from Section10.1.2.4 of PANS ATM, proposes additional details to be taken into considerations when establishing procedures for transfer of air–ground communication both in presence and in absence of ATS surveillance systems, as well as when a third unit is involved. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 18 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note 2.7.1.3.2. Section 4 — Requirements for communications This section, which is based primarily on the transposition of Standards from Chapter 6 of ICAO Annex 11, includes organisation requirements for ATS providers concerning the aeronautical mobile (air–ground) and the aeronautical fixed (ground–ground) services, as well as the communications of units providing aerodrome control service with vehicles on the manoeuvring area. It also defines the ATS providers’ responsibilities for the automatic recording of air–ground communications, ground– ground communications and surveillance data. It addresses the retention of such records of communication, data and other control data and documentation. ATS.OR.400, transposed from Section 6.1.1.1 of Annex 11, establishes the general principles for the provision of the aeronautical mobile service, which is the communication between the aircraft and ATS units. The ATS provider is required to use voice or data link, or a combination of them, for air– ground communications. The term ‘radiotelephony’ used by the original ICAO provision is replaced by the term ‘voice’ for consistency with provisions in Section 6 of the SERA Regulation, and in particular with SERA.6001. Point (c), transposing Section 6.1.1.3 of Annex 11, requires the provider to record all communications for the purpose of ATC provision. Additionally, in consideration of the relevance of such communication records for occurrence investigation purposes, and in line with the scope of Regulation (EU) No 376/201414 which includes ATM/ANS-related occurrences, with point (d) the Agency proposes to expand the application of this requirement to FIS and AFIS provision, at the discretion of the competent authority. By virtue of the fundamental importance of the two-way air– ground communication in the provision of ATS surveillance service, point (b), transposed from Section 8.3.1 of PANS ATM, sets the level of availability, reliability and redundancy of the communication systems when such ATS is provided. ATS.OR.405 point (a), transposed from Section 4.1.3.1.1 of Annex 10 Volume V, addresses the utilisation of the VHF emergency channel. As explained in Section 2.7.2, it is proposed to introduce the same requirement also in the SERA Regulation by amending SERA.14095. ATS.OR.405 point (b), from Section 4.1.3.1.1 of Annex 10 Volume V, indicates the ATS units at which the VHF emergency channel has to be made available; it is left to the competent authority to mandate the availability of the said channel at additional locations, such as AFIS units, when considered appropriate. GM is provided to better specify the use of such channel, including the reference to requirements for the continuous watch of the VHF emergency channel (in SERA.14080(b)). Based on the general principles as in ATS.OR.400, provisions ATS.OR.410, ATS.OR.415, ATS.OR.420 and ATS.OR.425, transposed from Section 6.1 of Annex 11, establish the specific requirements for the aeronautical mobile service for the various ATS units with the related main technical characteristics. While the original provision in Section 6.1.2.1 of Annex 11 prescribes the establishment of radio coverage anywhere within the flight information region (FIR) for the purposes of FIS, with ATS.OR.410 point (a), in recognition of the objective limitations which may be encountered to respond to such requirement, as for instance the impossibility to establish full radio coverage due to the orography of the territory, the Agency proposes that such radio coverage is ensured to ‘the practical extent’ and under the conditions prescribed by the competent authority. The Agency 14 Regulation (EU) No 376/2014 of the European Parliament and of the Council of 3 April 2014 on the reporting, analysis and follow- up of occurrences in civil aviation, amending Regulation (EU) No 996/2010 of the European Parliament and of the Council and repealing Directive 2003/42/EC of the European Parliament and of the Council and Commission Regulations (EC) No 1321/2007 and (EC) No 1330/2007 (OJ L 122, 24.4.2014, p. 18) (http://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1465291216361&uri=CELEX:32014R0376). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 19 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note advises to apply the given flexibility only when necessary, and keeping in mind the imperative need to ensure the availability of the aeronautical mobile service as a necessary means for the provision of FIS. ATS.OR.410 point (b) introduces the novelty of explicit requirements on the aeronautical mobile service for AFIS units. With the same flexibility established for FIS in point (a), the provider is required to ensure the air–ground communication between the AFIS unit and aircraft within the airspace associated with the AFIS aerodrome. ATS.OR.430 establishes the general requirements for the aeronautical fixed service, which supports the communications between ground-based units and/or entities involved for the purpose of ATS provision. Point (a), transposed from Section 6.2.1.1 of Annex 11, determines that such service is to be provided by means of direct speech and/or via data link communications, while point (b), which originates from Section 10.1.6 of PANS ATM and focuses on a specific safety issue, requires that failures of automated coordination systems established at ATC units for the coordination of flights are clearly displayed to the ATCOs, so that they may apply alternative methods, as indicated in the related GM1 ATS.OR.430(b). ATS.OR.435, transposed almost entirely from Sections 6.2.1 and 6.2.2 of Annex 11, describes in detail and mandates the communication facilities to be established between the various ATS units, including the relevant air traffic services reporting offices, within an FIR, as well as the communication facilities with other units or entities to which the ATS units have to timely and efficiently provide services under their responsibility or to fulfil other tasks assigned. Such units or entities include inter alia the military units in charge of identification and interception of aircraft, meteorological offices, rescue and emergency services. In addition to the original ICAO text, the requirement explicitly indicates when such communication facilities have to be made available and used at AFIS units. ATS.OR.435 point (c) describes the mandatory characteristics and capabilities of the communication facilities and identifies those whose communication shall be recorded. In particular, point (c)(4) merges the content of Sections 6.2.2.3.5 and 6.2.2.3.6 and dictates that the specified communication facilities, made available at approach control units, aerodrome control towers and AFIS units for communication within the FIR, have direct speech capabilities for conference communications. The facilities shall enable the establishment of communications within 15 seconds. In recognition of the technological state of the art, GM1 ATS.OR.435(c)(4) clarifies that such facilities may be other than point-to-point telephone lines. ATS.OR.440, transposed almost entirely from Section 6.2.3 of Annex 11, relates to the establishment of communication between ATS units providing services in neighbouring FIRs. The provision addresses in detail the establishment, characteristics and capabilities of the facilities enabling communications between adjacent area control centres (ACCs) and FICs, as well as other ATS units when their location and the specific operational context necessitate the availability of reliable and efficient connectivity. For all the communication facilities addressed by this provision, recording is required. ATS.OR.445, originating from Section 6.2.4 of Annex 11, requires the ATS provider to establish procedures for the appropriate use of the direct speech communication facilities when circumstances so require for the sake of safety of aircraft. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 20 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note ATS.OR.450, transposed from Section 6.3.1 of Annex 11, has to be read in the context defined in ATS.OR.110, and mandates the ATS providers to make available to the aerodrome control towers two-way voice communication facilities for the control of vehicles on the manoeuvring area, or in alternative, to establish a communication system with such vehicles based on visual sign, if considered adequate to the local operational environment. When appropriate, such two-way voice communications are to be undertaken making use of ad hoc channels, which shall be provided with recording facilities. AMC1 ATS.OR.450(a), which transposes Sections 7.6.3.2.3.2 and 7.6.3.2.3.3 of PANS ATM, establishes a standard communication system based on visual light signals, which can be used also in case of failure of voice communication facilities. GM1 ATS.OR.450(a), transposed from Section 7.6.3.2.3.1, indicates the need to ensure that vehicles operating on the manoeuvring area are provided with adequate voice communication capability with the aerodrome control tower unless specific arrangements allow them to operate without. This provision seems to address the aerodrome operator and not the ATS provider; however in the absence of a similar requirement within the EU aerodrome requirements (Regulation (EU) No 139/2014), it is proposed for consideration of the ATS providers, in the context defined in ATS.OR.110. ATS.OR.455, transposed from Section 6.4.1.1 of Annex 11, requires the ATS providers to ensure that surveillance data used for the provision of ATS under their responsibility is recorded, as it may prove fundamental for different purposes, and in particular occurrence investigation and search and rescue. ATS.OR.460 establishes the obligation for the ATS provider concerning the retaining of records of communications and data described in various provisions of Subpart A Section 4, as well as of paper and electronic flight strips and coordination data, as detailed in ICAO documents in various instances, in particular in Chapter 6 of Annex 11. All these records have to be retained for a minimum of 30 days, except when they relate to occurrences. In this case, they have to be retained for the period necessary to fulfil the actions concerned with the investigation of such occurrences. ATS.OR.465, originating from the recommended practice in Section 3.3.3 of Annex 11, requires the providers of air traffic control service to install systems which allow the recording of background communication and the aural environment at ATCO work stations; such systems should be capable of retaining the records during at least the last 24 hours of operations. This requirement stemmed from Safety Recommendation No 09/2004 of the Investigation Report AX001-1-2/02 published by the German Federal Bureau of Aircraft Accidents Investigation (BFU) in May 2004 regarding the mid-air collision between a Boeing 757-200 and a Tupolev TU154M on 1 July 2002 near Überlingen, Germany. ICAO does not provide guidance on the scope and implementation of this requirement, and evidence gathered by the Agency with the contribution of the RMG.0464 members suggests that the majority of the EU Member States has not yet implemented this provision, and that even when they have, there is a great diversity in the way it is implemented. Therefore, the Agency invites the stakeholders to comment on the transposition of this recommended practice as proposed in ATS.OR.465, in particular with regard to: — the appropriateness of this requirement to the current operational environment at EU ATC units; — the need to extend the application of this requirement to all ATS units; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 21 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note — the consideration about the fact that costs for the fulfilment of such requirement could override the expected benefits in terms of safety; and — the need to explicitly limit the requirement for the use of such recordings only for occurrence investigation purposes. 2.7.1.3.3.Section 5 — Requirements for information This section proposes organisation requirements for ATS providers concerning meteorological information, information on aerodrome conditions and operational status of navigation aids, whose knowledge by an ATS unit is essential for the purpose of supporting the provision of the FIS. This kind of information represents a part of all the relevant information supplied by FICs, ATC units and AFIS units to the aircraft, so as to contribute to the safe and efficient conduct of flights. By nature, this information needs to be obtained by the ATS provider after coordination with the appropriate stakeholders, so several organisation requirements are proposed to ensure its subsequent availability and use by the ATS units. In achieving a consistent approach with ICAO, the following requirements and their associated GM are based on applicable SARPs currently published in Chapter 7 of ICAO Annex 11. The formulation of the requirements was amended to underline that the responsibility to ensure the supply of meteorological information rests with the ATS provider. ATS.OR.500, based on Sections 7.1.1.1 and 7.1.1.2 of Annex 11, is concerned with the supply of up- to-date information on existing and forecast meteorological conditions that needs to be made available to ATS units in order to support the performance of their functions. In particular, it addresses the need for detailed information on meteorological phenomena taking place in the vicinity of the aerodrome that could adversely affect aircraft, e.g. approach and departure operations. It also emphasises the importance of the form and frequency, by which the information is presented to the ATS personnel. ATS.OR.505, transposed from Sections 7.1.2.1 and 7.1.2.2 of Annex 11, addresses the supply of information stipulated in MET.OR.245(f) and (g) for FICs and ACCs concerning the airspace when such units are designated to provide ATS, underlining the need to make available information related to weather deterioration as soon as it can be observed or anticipated by the associated meteorological watch office. The provision of meteorological information concerning other airspaces not under the responsibilities of such ATS units may be prescribed by the competent authority. It also requires a regular provision of pressure data for setting altimeters for specific locations indicated by the FIC or ACC concerned.GM1 ATS.OR.505(a), transposed from Note to Section 7.1.2.1 of Annex 11, explains why changes in weather conditions should be evaluated in the aviation context, so as to anticipate any adverse impact on aircraft operations. ATS.OR.510, originating from Sections 7.1.3.1, 7.1.3.2, 7.1.3.3, 7.1.3.4, 7.1.3.5 and 7.1.3.6 of Annex 11, requires the supply of information considered in MET.OR.242(b) for an approach control unit through its associated aerodrome meteorological office, as well as the necessary updates in accordance with established criteria. In addition, it regulates a number of meteorological inputs that need to be displayed and monitored at an approach control unit, like wind speed associated with runways or their sections and pressure data for setting altimeters for specific locations. Besides, units providing services for final approach, landing and take-off are required to display surface wind data, TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 22 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note runway visual range value(s), value(s) of the height of cloud base and wind shear. It is also established which of these data are to be obtained from the same sensors and correspond to the meteorological information displayed in the aerodrome control tower and in the meteorological station, where such a station exists. ATS.OR.515, transposing Sections 7.1.4.1, 7.1.4.2, 7.1.4.3, 7.1.4.4, 7.1.4.5, 7.1.4.6, and 7.1.4.7 of Annex 11, requires the supply of information considered in MET.OR.242(a) for aerodrome control towers and AFIS units through the associated aerodrome meteorological office, as well as the necessary updates in accordance with established criteria. The proposal includes the explicit reference to the AFIS units as recipient of the supply of meteorological information about the aerodrome, in consideration of the safety relevance of meteorological information for aerodrome operations. Taking account of the specificity of the AFIS provision, discretionary powers are given to the competent authority to allow justified derogations from the provision of information in MET.242(a) to AFIS units. In order to reflect the inclusion of AFIS units in the scope of this provision, this NPA proposes to amend MET.OR.242(b) accordingly, as explained in Section 2.7.1.5 below. The scope of this requirement is very similar to ATS.OR.510 in relation to meteorological information that needs to be made available to the aerodrome control tower or AFIS unit, like pressure data for setting altimeters for the aerodrome concerned. In a similar way, it regulates the availability of displays, so as to show surface wind data associated with runways or their sections, runway visual range value(s), value(s) of the height of cloud base and wind shear. It also stipulates which of this data is to be obtained from the same sensors and corresponds to the meteorological information displayed in the meteorological station, where such a station exists. Finally, the supply of aerodrome warnings for local meteorological conditions on the aerodrome concerned is required as well. ATS.OR.520, transposing Section 7.2 of Annex 11, establishes the obligation for the ATS provider to duly inform aerodrome control towers, AFIS units and units providing approach control service about the operational conditions of the movement area and of the associated facilities at the aerodrome(s) concerned with the services delivered by these units. The elements of information, established in ADR.OPS.010 and ADR.OPS.015 of Regulation (EU) No 139/2014 is to be made available to the ATS provider by the aerodrome operator concerned, by virtue of the agreement mandated under ATS.OR.110 and better specified by the associated AMC2 ATS.OR.110. ATS.OR.525, originating from Sections 7.3.1 and 7.3.2 of Annex 11, stipulates the obligation for the ATS provider to ensure that all ATS units, including AFIS units, are duly and timely informed of the operational status of key radio navigation and visual aids within their respective area of responsibility related to take-off, departure, approach and landing procedures, as well as to surface movement. GM1 ATS.OR.525 incorporates ICAO Air Traffic Services Planning Manual (Doc 9426), Part I, Appendix A to Chapter 10, as a valid reference in relation to the provision of information to ATS units with respect to visual and non-visual navigation aids. 2.7.1.4. Amendments to Annex IV — Subpart B ‘Technical requirements for providers of ATS’ The requirements proposed in this Subpart set the principles of the working methods and operating procedures for the provision of ATS, both at general level (in Section 1 ‘General’) and for each of the services in the scope of ATS (in Sections 2 ‘ATC service’, 3 ‘Flight information service’ and 4 ‘Alerting service’). They are based mainly on the transposition of the relevant Annex 11 and PANS ATM provisions, with the necessary adaptations to the EU regulatory and operational context, and take TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 23 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note also into account the content of ICAO European (EUR) Regional Supplementary Procedures (Doc 7030 EUR) and the feedback obtained from the RMG.0464 Members on existing practices and procedures. With the introduction of a complete and more detailed set of requirements in Subpart B, ATS.TR.100(a) of the ATM/ANS Common Requirements Regulation, which generically addressed ATS providers to establish working methods and operating procedures compliant with the Standards in Annex 10 Volume II and Annex 11, is repealed. The reference to the compliance with the SERA Regulation for the provision of ATS is repealed as well, but the proposed introduction of the recitals referring to the ATM/ANS Common Requirements Regulation and to the SERA Regulation as explained in Sections 2.7.1.1 and 2.7.2 indicates the close interdependency and complementarity of these two sets of rules. Instead, the specific requirement in ATS.TR.100(b) of the ATM/ANS Common Requirements Regulation addressing the provision of ATS for flight testing is maintained in the newly established provision ATS.TR.165. 2.7.1.4.1. Section 1 — General The provisions in this section address the fundamentals of the various ATS, including the related objectives, the description of each service, the units in charge, as well as the common technical requirements to be applied by ATS providers, as appropriate. ATS.TR.100 establishes the objectives to be achieved in the provision of ATS to aircraft. This requirement, originating from Section 2.2 of Annex 11 and transposed also in SERA.7001, is duplicated in PART-ATS in consideration of its relevance in the regulatory context. ATS.TR.105, which is based on Sections 2.3.1, 2.3.2, and 2.3.3 of Annex 11, institutes the services in the scope of ATS and unambiguously associates them with the achievement of the objectives established in ATS.TR.100. Therefore, ATS comprise ATC service, further detailed into area, approach and aerodrome control service, FIS and Alerting Service. In addition to the original text of Annex 11, paragraph (b) explicitly links the air traffic advisory service, which ICAO defines in Section 9.1.4 of PANS ATM, to FIS. In line with the purpose of this NPA to unequivocally recognise and address AFIS provisions, GM2 ATS.TR.105(b) clarifies that FIS may be provided to traffic operating en-route as well as at aerodromes and its vicinity, thus indicating the two environments for which specific FIS provisions are proposed. AMC1 ATS.TR.105(b), transposed from Sections 9.1.4.1.1 and 9.1.4.1.2, the latter also being duplicated as AMC1 SERA.6001(h), addresses the implementation of the air traffic advisory service. It stipulates that such information service, which should be implemented only on a temporary basis, may be provided to IFR flights under specified circumstances and within advisory airspace (Class F), when air traffic control service is not deemed to be suitable. GM1 ATS.TR.105(b) is transposed from various textual parts of Sections 9.1.4.1 and 9.4.1.3 of PANS ATM, some of which were also proposed as GM1 SERA.14090(b) with NPA 2015-14. It offers additional details on the objectives, the tasks, the arrangements and the procedures for the provision of the air traffic advisory service, and emphasises the advice-giving nature of this information service. Nonetheless, in consideration of the specific safety-related nature of the service, with AMC2 ATS.TR.105(b), which transposes Section 10.3 of PANS ATM, the ATS units concerned are required to apply the same procedures established for the provision of ATC for the coordination of traffic to which air traffic advisory service is provided. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 24 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note ATS.TR.110 institutes the various ATS units and describes the services each of them is in charge of providing as well as the associated airspace and area of responsibility. In point (a), transposed from Sections 2.9.1 and 2.9.2 of Annex 11 which originally comprised only the ATC units and the FIC, the Agency proposes to include also the AFIS unit, which is responsible for the provision of FIS and alerting service at specified aerodromes where a Member State deems necessary to provide ATS, but not ATC service. Point (b), derived from the related definition in PANS ATM, establishes the functions of the ATS reporting office as integral part of ATS. GM1 ATS.TR.110(b), based on the Final Report of the 57th meeting of the European Air Navigation Planning Group (EANPG), further elaborates on the suitable set-ups for the implementation of such functions, which does not necessarily envisage establishing a physical office. ATS.TR.115, derived from Sections 2.11.1 and 2.11.2 of Annex 11 and from Section 5.2.1.7.1 of Annex 10 Volume II, stipulates the criteria for the naming of the various ATS units, including the AFIS units, which were not considered in the aforementioned reference ICAO provisions. GM1 ATS.TR.115 suggests the principles for the naming of UNICOM aeronautical stations, when established in lieu of ATS units as described in Section 2.6. ATS.TR.120 is transposed from the second sentence in Section 2.17.3.1 of Annex 11; it requires the ATS providers to make sure that ATS units have available all the necessary data and information to fulfil the obligations set in ATS.OR.115 with regard to coordination with military units, for the purposes of the identification of aircraft operating within portions of airspace specified by the competent authority. ATS.TR.125, transposing Section 2.29.2 of Annex 11, stipulates that the communications between ATS units are to be effected in English language, or in another language agreed between the involved units and/or providers. In consideration of the importance of the effective communication in ATS, the Agency proposes to extend its application to all ATS units, including FIC and AFIS units, while the original ICAO provision was addressed only to ATC units. Provisions from ATS.TR.130 to ATS.TR.145 establish a comprehensive and coherent set of rules related to altimetry, to the information on vertical position of aircraft and to flight level management by ATS units. ATS.TR.130, derived from Sections 4.10.1.1, 4.10.1.2, and 4.10.13 of PANS ATM, defines the criteria to determine and express the vertical position of aircraft in the various phases of flight, specifying when such vertical position has to be expressed in terms of flight levels, altitudes or specified heights. These requirements duplicate the contents of provisions SERA.8015(eb)(1) and (eb)(5), introduced with Regulation (EU) 2016/1185. ATS.TR.135 requires the ATS units concerned to determine the transition level and defines the criteria to be used for this purpose. In order to be consistent with ATS.TR.130(a), point (a) clarifies that the transition level is to be used in areas where the transition altitude is established, and not ‘in the vicinity of aerodrome concerned and, when relevant, the terminal control area (TMA) concerned’, as instead indicated in the originating Section 4.10.2.1 of PANS ATM. GM1 ATS.TR.135 points out the need for coordination between ATS units with the purpose of establishing a common transition level for aerodromes located nearby. Point (b) of ATS.TR.135, derived from Section 6.3.1.2 of ICAO Doc 7030 EUR, determines the location of the transition level in respect of the transition altitude with the purpose of allowing their safe simultaneous utilisation. The Agency discussed the TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 25 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note proposal made by a member of RMG.0464 to add the phrase ‘a nominal’ to the minimum separation value between the given transition altitude and the transition level. The rationale behind this proposal was that if the 'correct' values of 1013.25 hPa for the Standard and 27.3 ft per hPa in calculating the transition level are used, in certain pressure conditions, a whole flight level is lost for the sake of 7 ft (quarter of an hPa). The addition of 'a nominal' would incorporate the 7 ft 'deviation' described above and would allow more flexibility. The Agency invites stakeholders to express their views on the subject and to indicate if the addition of the phrase ‘a nominal’ would be acceptable. ATS.TR.140, transposed from Sections 4.10.3.1 and 4.10.3.2 of PANS ATM, addresses the ATC units concerning the determination, the assignment and the provision of information to aircrew on the minimum cruising levels for IFR flights. In consideration of the safety relevance of the requirements in point (b), the Agency proposes to remove the optional nature of the original PANS ATM provision by making the application of this requirement mandatory at all times in the EU context. GM1 ATS.TR.140(b) clarifies the meaning of lowest usable flight level in this context. ATS.TR.145, which transposes the very large part of Section 4.10.4 of PANS ATM, stipulates the requirements for the ATS units concerning the provision of altimeter setting information, such as the transition level and the QNH and QFE for the various phases of air and ground operations of aircraft. This information includes the necessary elements to determine the lowest usable flight level, where necessary, and for ACCs and FICs the actual or forecast QNH reports for the airspaces under their responsibility and for those adjacent. Finally, it stipulates the criterion to round down the altimeter setting. Points (c), (d), and (e) of ATS.TR.145 are duplicated respectively from SERA.8015(eb)(2), (eb)(3) and (eb)(4). GM2 ATS.TR.145(c), originating from the second sentence of Section 4.10.4.3 of PANS ATM, clarifies that the ATS units may communicate the transition level to aircraft by the use of voice communications, ATIS broadcast or data link. ATS.TR.150, transposed from Sections 7.13.1 and 7.13.3 of PANS ATM, establishes the requirements concerning the authorities and the circumstances for the total or partial suspension of VFR operation on and in the vicinity of an aerodrome, as well as the procedures to be applied when such suspension is in effect. GM1 ATS.TR.150, derived from Section 7.13.2 of PANS ATM, clarifies the pivotal role of the aerodrome control tower when such suspensions occur. ATS.TR.155 prescribes the relevant ATS providers to set procedures for the operation of the aeronautical ground lights, regardless of their distance from the aerodrome for which they are concerned. The associated AMC1 ATS.TR.155, transposed from the very large part of Section 7.15 of PANS ATM, addresses in detail the procedures for the operation of the various aeronautical ground lights, which are described in GM1 to such AMC. While the original PANS ATM provisions were addressing only the aerodrome control tower personnel, the text of this AMC extends its applicability to the AFIS unit personnel, when relevant. ATS.TR.160 establishes the principles for the use of ATS surveillance systems, which in accordance with the related definition transposed in Annex I from PANS ATM include ADS-B, PSR, SSR or any comparable ground-based system that enables the identification of aircraft, in the provision of ATS. In this case, such services are referred to as ATS surveillance services. AMC1 ATS.TR.160(a) describes in detail the functions of ATS surveillance systems which can be implemented in the provision of area control, approach control and aerodrome control services, as well as of the FIS, which is intended to TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 26 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note implicitly include also AFIS. The content of this AMC is derived from various Sections of Chapter 8 of PANS ATM. Its point (c), addressing the functions of ATS surveillance systems in the provision of aerodrome control service, contains an amendment to the original PANS ATM provision proposed and approved by ICAO EANPG at its 56th meeting held in November 2014, allowing the use, in the European context, of ATS surveillance systems to maintain separation between succeeding aircraft on the same final approach. Point (b) of ATS.TR.160, transposed from Sections 8.2.2, 8.4.2 and 8.6.8.1 of PANS ATM, requires the ATS providers to ensure that specific arrangements are established to support the provision of ATS surveillance services, such as the continuous update of the surveillance information and particularly of position indications, the definition of the capacity of the services provided in relation of the various situations, the timely availability to controllers of relevant information, particularly those concerning lowest minimum levels, minimum flight altitudes and minimum altitudes to be applied when vectoring. With regard to the determination of these altitudes, in addition to the original PANS ATM text, the requirement stipulates that the necessary temperature corrections have to be applied. In support of the implementation of these requirements, AMC1 ATS.TR.160(b)(1) addresses the ATS provider to establish the criteria to measure distances between position indications, while AMC1 ATS.TR.160(b)(2), transposed from Section 8.4.2 of PANS ATM, indicates the essential factors to be considered by the ATS providers when determining the number of aircraft to which ATS surveillance services can be simultaneously provided. Point (c) of ATS.TR.160, based on Sections 8.6.2.1.1 and 8.6.2.1.2 of PANS ATM, mandates the establishment and maintenance of the identification of aircraft, for which a definition derived from PANS ATM is provided in Annex I, as an essential requirement for the provision of ATS surveillance services; it also stipulates that when such identification is unintentionally lost, the ATS shall inform without delay the pilot and issue appropriate instructions for the continuation of the flight. Point (d) of ATS.TR.160 addresses the various operational aspects of ATS surveillance services, for which the ATS providers are required to establish procedures appropriate to the service rendered. The Agency proposes a comprehensive set of AMC and GM, mainly transposed from Chapter 8 of PANS ATM, supporting the implementation of these procedures. AMC1 ATS.TR.160(d)(1), originating from Sections 8.6.2.1.3, 8.6.2.2, 8.6.2.3.1, 8.6.2.3.2, 8.6.2.4.1, and 8.6.2.5, describes the methods for the identification of aircraft for the various types of surveillance system available, such as ADS-B, SSR and/or MLAT, PSR. The Agency does not deem necessary to propose the use of direction finding bearings, proposed in Section 8.6.2.4.2 of PANS ATM, as a method to establish the identification of aircraft because it does not seem to be a common practice in the EU context. AMC2 ATS.TR.160(d)(1), transposing Section 8.10.2.3 of PANS ATM, describes the methods of identification of aircraft on the ground subject to surface movement control. AMC3 ATS.TR.160(d)(1), originating from Sections 8.6.3.1 and 8.6.3.2 of PANS ATM, establishes the procedures, and the necessary conditions, to be applied when effecting a transfer of identification of aircraft between units providing ATS surveillance services. GM1 ATS.TR.160(d)(1) provides further explanation on the various methods of transfer proposed. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 27 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note The three AMC and the associated GM to point (d)(1) of ATS.TR.160 explicitly allow the application of the identification methods by the FIS and AFIS officers, where appropriate, while with the original PANS ATM provisions they could only be applied by ‘the controller’. AMC1 ATS.TR.160(d)(2), based on Sections 8.6.4.1, 8.6.4.2, and 8.6.4.3 of PANS ATM, stipulates the circumstances and the methods for the communication of position information to aircraft. AMC1 ATS.TR.160(d)(3), transposing part of Sections 8.6.5.1, 8.6.5.5, and 8.10.1.2 of PANS ATM, institutes the general principles for the establishment of procedures for vectoring aircraft, for which a definition is provided in Annex I, in particular with regard to the information on the objective and the limit of the vector assigned, to the precautions the controllers should apply with regard to the airspace boundaries, to the vectoring in uncontrolled airspace. This AMC also points out that normally special VFR flights are not to be vectored, and details the instructions and information the controller has to issue to the pilot when vectoring is ended. AMC2 ATS.TR.160(d)(3), derived from Sections 8.9.3.2, 8.9.3.3, 8.9.3.4, 8.9.3.6, 8.9.3.7, and 8.9.4.5 of PANS ATM, further specifies the principles to be applied by the approach control units when vectoring aircraft. It is to be noted that the content of point (d) of this AMC addressing vectoring for final approach, originating from Section 8.9.3.6 of PANS ATM, is amended to be aligned with the amendments proposed by ICAO AN- WP/9014. The proposed text of this specific provision also responds to the recommendation made in the EASA Safety Information Bulletin (SIB) 2014-07R1 : Unexpected Autopilot Behaviour on Instrument Landing System (ILS) Approach15, as far as vectoring aircraft for the final approach is concerned. A set of GM to this AMC, mainly transposed from the relevant sections of Section 8.9 of PANS ATM, is proposed to provide detailed guidance for the establishment of procedures which envisage vectoring of aircraft in the approach phases. They relate to: — vectoring to pilot-interpreted final approach aids (GM1 to AMC2 ATS.TR.160(d)(3)); — vectoring for visual approach (GM2 to AMC2 ATS.TR.160(d)(3)); — procedures for radar approaches (GM3 to AMC2 ATS.TR.160(d)(3)); and — procedures for surveillance radar approach (GM4 to AMC2 ATS.TR.160(d)(3)). AMC1 ATS.TR.160(d)(4), derived from Section 8.6.6.1 of PANS ATM, stipulates that the ATS units providing ATS surveillance services, including FIC and AFIS units, should inform aircraft which are observed to depart significantly from their intended flight path and, where necessary, undertake appropriate action. GM1 ATS.TR.160(d)(5), based on Sections 8.6.9.1 and 8.6.9.2 of PANS ATM, indicates that units providing ATS surveillance services are entitled to timely inform aircraft about detected areas of adverse weather which may impact their intended flight path and, specifically for ATC units, highlights the necessity to evaluate the impact of vectoring to avoid such areas on the intended flight path of aircraft, and to inform the pilots accordingly. AMC1 ATS.TR.160(d)(6), entirely transposing Section 8.7.4 of PANS ATM, sets the principles and the conditions for the establishment of procedures concerning the transfer of control of aircraft between units providing ATS surveillance services, in order to ensure continuity in the provision of such 15 http://ad.easa.europa.eu/ad/2014-07R1 TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 28 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note services. The AMC provides details for both cases when SSR and/or ADS-B and/or MLAT and when primary radar is used. The associated GM1 to AMC1 ATS.TR.160(d)(6), derived from Section 6.2.5.1 of Doc 7030 EUR, clarifies that the procedures specified in the AMC may be applied without systematic use of the bidirectional speech facilities available between the adjacent units concerned, under specified conditions. AMC1 ATS.TR.160(d)(7), transposed from Section 8.8.4.1 of PANS ATM and applicable only to ATC units, establishes the relevant elements of the procedure to be applied in the event of a complete failure of ATS surveillance systems, in particular with regard to the determination of the position of aircraft and to the establishment of an applicable and appropriate procedural separation. For the latter, GM1 ATS.TR.160(d)(7) indicates the application of the half of the applicable vertical separation minima in terms of flight levels, as an immediate and temporary solution. In order to provide guidance on the availability and on the use of ATS surveillance-based safety- related alerts and warnings, the Agency proposes the following GM: — GM1 ATS.TR.160(d)(9), transposed from the recommendation in Section 3.9 of Annex 11, represents the safety significance of building in ATS surveillance systems specific features and functionalities, such as conflict alert, conflict prediction, minimum safe altitude warning and unintentionally duplicated SSR codes. — GM2 ATS.TR.160(d)(9), based on the content of Note 1 to Section 15.7.2 and of Section 15.7.2.1, describes the purposes of short-term conflict alert (STCA) functions and the elements to be included when developing the related procedures. — in a similar fashion, GM3 ATS.TR.160(d)(9), based on the content of Note 1 to Section 15.7.4 and of Section 15.7.4.1, addresses the minimum safe altitude warning (MSAW) functions and procedures. Point (e) of ATS.TR.160, transposed from Section 8.8.2.1 of PANS ATM and already transposed as SERA.7002 with Regulation (EU) 2016/1185, mandates the actions to be undertaken by ATC units when an unknown aircraft is deemed to constitute a collision hazard for an identified and controlled aircraft. In addition, GM1 ATS.TR.160(e), transposed from Section 8.8.2.2 of PANS ATM and proposed as GM2 to SERA.7002(a)(1) with NPA 2015-14, indicates the actions to be undertaken by a unit providing ATS surveillance services in case an identified IFR flight outside controlled airspace is observed to be in a conflicting path with other traffic. ATS.TR.165 replicates, without any substantial change, the requirements concerning the provision of ATS to flight testing operations previously included in point (b) of ATS.TR.100 in the ATM/ANS Common Requirements Regulation. 2.7.1.4.2.Section 2 — ATC service This section includes the requirements concerning the provision of ATC service, which, in accordance with the objectives set in points (a), (b) and (c) of ATS.TR.100, is delivered with the purpose of preventing collisions between aircraft in the air and on the manoeuvring area, as well as of expediting and maintaining an orderly flow of air traffic. In consideration of the safety relevance of this service, the proposed IRs are further accompanied by a comprehensive set of AMC and GM mainly, but not exclusively, transposed from PANS ATM. These AMC and GM address with the appropriate level of detail the procedures and the tasks for ATC provision to be applied, as TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 29 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note appropriate, by the provider, the unit or, when so specified, by the ATCOs. The section includes a number of IRs duplicated from SERA, in accordance with the rationale explained in Section 2.5; for these IRs, the related set of AMC and GM proposed with this NPA are not those included in ED Decision 2013/013/R, but are introduced ex novo and concern directly the ATS requirements. ATS.TR.200, identical to SERA.8001 and transposed from Section 3.1 of Annex 11, establishes the mandatory scope of application of the ATC service, which is to be provided to IFR and VFR flights operating within specified airspace classes as defined by SERA.6001, as well as to all special VFR flights and to all aerodrome traffic operating at controlled aerodromes. On the basis of the subdivision of the ATC service into area control service, approach control service and aerodrome control service stipulated in ATS.TR.105(a), ATS.TR.205, which is derived from Section 3.2 of Annex 11, determines the units which are entitled to provide each of these services. A certain degree of flexibility is offered with regard to the units authorised to provide area control service and approach control service, subject to specified conditions. AMC1 ATS.TR.205, derived from Section 4.3.1 of PANS ATM, requires the provider to arrange the details of the operational set-up of the ATC unit, including when necessary, the sectorisation and the duties and responsibilities of the various working positions. AMC1 ATS.TR.205(c), based on Sections 7.1.1.1 and 7.1.1.2 of PANS ATM, elaborates on the functions of the aerodrome control tower for the achievement of the assigned objectives. For this purpose, continuous watch on aircraft, vehicles and persons operating on the manoeuvring area has to be maintained at all times by visual observation, which may be augmented by ATS surveillance systems, where circumstances (e.g. low visibility) so require. With RMT.0624 ‘Technical requirements for remote tower operations’, the Agency aims at establishing a regulatory framework allowing the provision of aerodrome ATS from a remote facility, and no longer from an aerodrome control tower physically located at the aerodrome for which it renders the services. As a result of the work undertaken under RMT.0624, the Agency has already published ED Decision 2015/014/R16, including GM concerning inter alia an initial definition of visual observation from a remote location, supported by the synthetic representation of the operational environment to the controllers/AFIS officers. At the moment of the publication of this NPA, the activities for the next phase of RMT.0624 which should further develop the concept and the related requirements for remote aerodrome ATS provision are being initiated. The Agency will ensure that full consistency is maintained between the deliverables of these two regulatory packages. GM1 ATS.TR.205(c), derived from Sections 7.1.1.3 and 7.1.1.4 of PANS ATM, indicates the working positions which may be established within a aerodrome control tower to fulfil the relevant functions, and addresses the responsibilities of the controllers in case of simultaneous operations on parallel or near-parallel runways. ATS.TR.210 represents a fundamental requirement in the context of ATC service provision, as it establishes the main tasks and responsibilities of ATC units, including the use of appropriate information for the control of the aircraft subject to the service, the issuance of clearances for separation purposes and the application of horizontal and vertical separation minima. Most of the contents of ATS.TR.210 are duplicated from points (a), (b) and (c) of SERA.8005; however, as a result of the analysis of the ATS-relevant ICAO provisions undertaken under RMT.0464, the proposed IR 16 https://www.easa.europa.eu/document-library/agency-decisions/ed-decision-2015014r TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 30 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note includes some amendments compared to the aforementioned original SERA provisions, for which consequently appropriate modifications are also proposed to ensure full consistency between the two regulatory packages, as explained in Section 2.7.2. Point (a) of ATS.TR.210, transposed from Section 3.3.1 of Annex 11 and duplicated in SERA.8005(a), prescribes in detail the tasks which the relevant units have to fulfil when providing ATC service. Such tasks concern the gathering, the processing and the use of the relevant information to determine the intended and actual progress of flights and their position in respect to each other’s, the issuance of clearances, instructions and information in order to achieve the objectives of the ATC service, as well as the coordination of clearances, when appropriate. The Agency proposes to insert the word ‘instructions’ to point (a)(3) to reflect the extensive use of ATC instructions as a means to achieve the established ATS objectives, as evident also in the context of PANS ATM, and to amend SERA.8005(a) accordingly. Due to the nature of this provision, a significant number of associated AMC and GM are proposed, addressing in detail the issuance of clearances, instructions and information in the various contexts of the ATC service provision. AMC1, AMC2 and AMC3 to ATS.TR.210(a)(3) address the principles and the elements of the procedures concerning the issuance of instructions for the horizontal and vertical speed control of aircraft in the various phases of the flight (en-route, departure, arrival), to be applied when necessary for the achievement of the objectives of the ATC service. A set of related GM is proposed to offer additional details on the application of such procedures. The provisions addressing speed control instructions are transposed from Sections 4.6 and 4.7 of PANS ATM; AMC1 ATS.TR.210(a)(3) includes the requirement introduced with ICAO AN-WP/9014 (Amendment 7 to PANS ATM) as the newly introduced Section 4.6.1.2, specifying that speed control instructions remain in effect until they are explicitly cancelled or amended by the responsible controller. AMC4 ATS.TR.210(a)(3) and the associated GM1, transposed from the relevant contents of Section 6.5.5 of PANS ATM, address the issuance of clearances and instructions for holding aircraft, when it is known that the flight is subject to delay. AMC5 ATS.TR.201(a)(3), originating from Sections 6.5.6.1.1 and 6.5.6.1.2 of PANS ATM, defines the criteria for the establishment of the approach sequence, including the specification of particular types of flights which should be afforded priority over the others. It also indicates the operational circumstances and conditions when flights may be cleared for the approach. GM1 to AMC5 ATS.TR.210(a)(3), derived from Sections 6.5.6.2.1 and 6.5.6.2.2 of PANS ATM, offers guidance on the so-called timed approach procedures to be applied in presence of a sequence of multiple arriving aircraft, as well as on the factors to be considered for the establishment of the time interval between successive approaching aircraft, with and without the use of ATS surveillance systems in the provision of ATC. AMC6 ATS.TR.210(a)(3), transposed from Section 6.5.7 of PANS ATM, addresses the circumstances and the procedures for the issuance and the communication of an expected approach time (EAT) to flights which are expected to be subject to a delay above a specified minimum. The original PANS ATM provision (Section 6.5.7.1) stipulates that the EAT should be determined and communicated to aircraft when the delay is estimated to be of 10 minutes or more, unless otherwise specified by the appropriate authority. As a result of the analysis and the discussions with the RMG.0464, the Agency TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 31 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note proposes to remove the element of flexibility and to maintain the standard 10-minute value, with the objective of standardising this procedure throughout the EU Member States. However, there is evidence that in a few Member States the procedure to determine and communicate the EAT is applied only when there is a delay of 20 minutes or more. In consideration of the situation described above, the Agency invites the stakeholders to express their views as to whether the 10-minute value is appropriate and currently in use for the determination of the EAT, or, in case it should be amended, what would be the correct time value to be introduced in AMC6 ATS.TR.210(a)(3). As AMC8 ATS.TR.210(a)(3) and its related GM1, originating from Section 6.5.4 of PANS ATM, address the general responsibility for the selection and the communication to aircraft of the instrument approach procedure to be used by arriving aircraft, AMC9 ATS.TR.210(a)(3) establishes the requirements concerning visual approach. This AMC, which is transposed from Sections 6.5.3.1, 6.5.3.3, 6.5.3.4, and from the large part of Section 6.5.3.5 of PANS ATM, establishes: — the responsibilities of the controller and of the flight crew of an IFR flight in selecting and approving the visual approach; — the conditions under which a visual approach can be cleared, with particular reference to the ability of the pilot to maintain visual reference with the terrain and to the reported and actual meteorological conditions; — the application of appropriate separation between the aircraft performing a visual approach and other arriving and/or departing traffic; — the responsibilities and the conditions with regard to separation between successive visual approaches; — the controller’s actions with regard to the issuance to pilots of a caution of possible wake turbulence, under specified circumstances when aircraft performing successive visual approaches are instructed to maintain own separation. GM1 to AMC9 ATS.TR.210(a)(3), based on Section 6.5.3.2 of PANS ATM, advises controllers to consider the familiarity of the flight crew with the aerodrome and its surrounding terrain, as well as the prevailing traffic and meteorological conditions, when they have the intention to propose the initiation of a visual approach. AMC10 ATS.TR.210(a)(3), transposed from Sections 6.6.1, 6.6.4, and 6.6.5 of PANS ATM, establishes the sets of information to be transmitted by the unit providing approach control service to arriving aircraft upon the establishment of initial communication, at the commencement of the final approach and, for specified elements when subject to significant variations or at the sudden occurrence of hazards, during the final approach. The related GM1, which transposes the Note to Section 6.6.4 of PANS ATM and which refers to MET.TR.205(a)(3), clarifies the meaning of ‘significant variations’ in the context of point (c) of the AMC. AMC11, derived from Sections 7.4.1.1.1, 7.4.1.1.2, 7.4.1.1.6, and 7.4.1.1.7 of PANS ATM, addresses the establishment and the implementation of start-up time procedures, which should be implemented with the objective of avoiding ground delays and of complying with the applicable ATFM measures. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 32 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note AMC12 ATS.TR.201(a)(3), transposed from Section 7.4.1.2 of PANST ATM, establishes the set of aerodrome and meteorological information to be transmitted by the relevant ATC units to aircraft on the ground before taxiing and before take-off, as well as prior to entering the traffic circuit or approaching the runway for landing. GM1 to this AMC, based on the note to Section 7.4.1.2.2 of PANS ATM, lists the meteorological phenomena the appearance of which may constitute a significant change to the meteorological information transmitted to aircraft prior to taxiing, which have to be notified to aircraft. AMC13 and AMC14 to ATS.TR.210(a)(3), transposed from various parts of Section 7.6.3.1 of PANS ATM, concern the principles and procedures for the issuance of clearances, instructions and information for aircraft taxiing on the manoeuvring area, with a specific focus on the procedures to be applied when aircraft are permitted to taxi on a runway in use. GM2 to AMC13 ATS.TR.210(a)(3) considers the entirety of Section 7.6.3.1.4 of PANS ATM to describe the principles of helicopter taxi operations. AMC16 ATS.TR.210(a)(3) and its associated GM1, transposed from Section 7.4.1.4.1 of PANS ATM, specify the actions the controller should undertake when an effective or a potential runway incursion or a runway obstruction are detected after the issuance of clearances for take-off or landing on the same runway. GM1 to ATS.TR.210(a)(3) clarifies that, in consideration of the safety-critical nature of these situations and of the risks to which an aborted take-off or a late go-around may expose the aircraft, it is a prerogative of the pilot-in-command to exercise their judgement in the given situation and to ultimately act to safeguard the safe conduct of flight in these situations. GM2 to ATS.TR.210(a)(3), which the Agency proposes for transposition from Section 2, Chapter 1, Paragraph 16 of the UK CAP 493 ‘Manual of Air Traffic Services – Part 1’, provides guidance for the circumstances when the controllers have to cancel a take-off clearance previously issued. AMC17 ATS.TR.210(a)(3), originating from Sections 7.9.3.1, 7.9.3.2, 7.9.3.4, and 7.9.3.5 of PANS ATM, establishes the circumstances and the conditions for the issuance of a take-off clearance to departing aircraft, in particular subject to the assurance of the existence of a suitable separation from other aircraft. Similarly, on the basis of Section 7.10.2 of PANS ATM, AMC18 ATS.TR.210(a)(3) addresses the issuance of landing clearance to arriving aircraft. AMC19 ATS.TR.210(a)(3), derived from Section 7.7.3.3 of PANS ATM, stipulates that specific categories of flights or aircraft subject to specified problems which could affect their safety should be afforded priority for landing over other traffic. The related GM1 provides additional guidance for controllers for the management of specific situations involving aircraft which may need priority for landing; it also recommends that landing aircraft should normally have priority over departing aircraft, when they all operate from the same runway or from intersecting runways. AMC20 ATS.TR.210(a)(3) establishes the requirements for procedures on visual departures, and more specifically: — the responsibilities of the controller and of the flight crew of an IFR flight in selecting and approving the visual departure; — the applicability of visual departure only during the daytime and under specified meteorological conditions; — the responsibility of the pilot as regards obstacle clearance; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 33 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note — the responsibilities of the ATC as regards the issuance of appropriate ATC clearance and the separation between the aircraft concerned and other traffic; and — the establishment of additional requirements to be agreed between the ATS provider and the operators concerned. GM1 to AMC20 ATS.TR.210(a)(3) draws the attention on the importance of timely providing the aircraft performing a visual departure with relevant information concerning VFR flights affecting its intended route as well as their penetration into airspace classes E, F or G. These provisions addressing visual departures are transposed from Sections 6.5.4.2, 6.5.4.3 and 6.5.4.4 of ICAO Doc 7030 EUR, as amended by ICAO EANPG/54 – WP/15 of 16.11.12 and EANPG/54 – Flimsy 08 of 04.12.12. AMC21 ATS.TR.210(a)(3) is developed to respond to the safety recommendation ‘FRAN-2013-045’ issued by the Bureau d'Enquêtes et d'Analyses (BEA) to the Agency in the context of the so-called ASAGA (on Aeroplane State Awareness during Go-Around) Study published in August 2013; it stipulates that controllers should issue the instructions for the missed approach in accordance with the published missed approach procedures, in order to help minimising the workload on the flight deck in such a critical phase of flight. Instructions with modifications to such published procedures should be reduced to the essential minimum and be issued only for safety reasons. The Agency proposes a number of GM to ATS.TR.210(a)(3) to better describe the issuance of clearances, instructions and information in the operational context of the aerodrome control service. In particular: — GM1 ATS.TR.210(a)(3), transposed from Sections 7.7.2.1 and 7.7.2.2 of PANS ATM and amended in accordance with the content of ICAO EANPG/56 – WP18 of 12/11/14, which addresses the issuance of clearances in the context of the aerodrome traffic circuit; — GM2 ATS.TR.201(a)(3) indicates that the controller may require pilots to obtain the ATC permission before turning for any of the legs of the traffic circuit and to report when extending any of such legs, in order to avoid losing visual contact with the runway. On the basis of its applicability to the EU operational context, the Agency decided to propose this provision, originating by ICAO EANPG/56 – WP18 of 12/11/14 but not included in the recent Amendment 7 of PANS ATM; — GM3 ATS.TR.210(a)(3), based on Sections 7.10.3.1, 7.10.3.2, and 7.10.3.4 of PANS ATM, which provides guidance on the issuance of instructions to aircraft for landing and roll out manoeuvres; and — GM7 and GM8 to ATS.TR.210(a)(3), derived from Section 7.9.1 of PANS ATM, describing the criteria to establish priority for take-off between aircraft. Point (b) of ATS.TR.210, transposed from Section 3.3.4 of Annex 11 and duplicated in SERA.8005(b), clarifies the purpose of the ATC clearances with regard to the achievement of separation between aircraft operating in accordance different flight rules (IFR, VFR, special VFR) and within various airspace classes, with the exception of a specific case when aircraft, subject to well defined conditions, may be authorised to maintain own separation from other traffic. AMC1 ATS.TR.210(b) and its associated GM1, transposed from Section 5.9 and the related Notes of PANS ATM, stipulates the elements of the procedure to be applied in this case, and emphasises the responsibilities of the TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 34 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note pilot with regard to the maintenance of visual meteorological conditions, the separation from other traffic and the prevention of collision with terrain when such procedure is applied. Point (c) of ATS.TR.210 establishes the principles and the criteria for the application by ATC units of a vertical or horizontal separation between aircraft, except in the case of operations on parallel or near-parallel runways or when a reduction of the separation minima in the vicinity of the aerodrome is allowed. For vertical separation, the applicable separation minima are specified in IR; for horizontal separation, which is further subdivided in lateral and longitudinal separation, only the criteria are defined, while the minima in the various circumstances are proposed in several AMC. The provision, originating from Section 3.3.5 of Annex 11, is also transposed as SERA.8005(c) and does not include the requirements concerning the application of composite separation established in point (c) of the original ICAO standard, as it is not considered suitable to the EU context. As a result of the analysis of PANS ATM performed under RMT.0464, the Agency proposes the further development of this provision as follows: — in the introductory sentence, to explicitly extend the possibility to apply a reduced separation minimum to operations on parallel or near-parallel runways, for which the requirements are proposed in ATS.TR.255, on the basis of the contents of Section 6.7 of PANS ATM; and — in point (c)(1), to explicitly prohibit the use of geometric height information when establishing and maintaining vertical separation, as required in Section 8.5.5.1.1 PANS ATM. GM3 ATS.TR.210(c)(1) clarifies that such information is that generated by airborne systems, for instance, GPS or radio altimeters. As explained in Section 2.7.2, the Agency proposes to amend SERA.8005(c) accordingly in order to ensure consistency. With the purpose of establishing detailed requirements for the application of the given separation methods under the various operational circumstances, the Agency proposes a comprehensive set of AMC and GM to ATS.TR.210(c). AMC1 ATS.TR.210(c), derived from Sections 15.7.11 and 15.7.1.2 of PANS ATM, prescribes that in the event of an emergency situation which renders impossible the application of any horizontal separation, the ATC units concerned may apply a vertical separation of a half of the prescribed minima. In this case, the flight crew is to be made aware of the situation, of the minima applied and provided with appropriate essential traffic information. GM1 to this AMC clarifies that this emergency measure may be applied, as far as flight level allocation is concerned, also in case of complete failure of the ATS surveillance systems, when they support ATC service provision. AMC1 ATS.TR.210(c)(1), transposed from Sections 5.5.1 and 5.5.2 of PANS ATM, addresses the principles for the application of procedural separation between aircraft holding in flight and other traffic, in particular with regard to separation between aircraft in adjacent holding patterns and between aircraft holding in flight and other arriving, departing or en-route traffic. It is important to remark that in this context, in accordance with point (b) of AMC2 ATS.TR.210(c)(2), separation minima based on ATS surveillance systems should not be applied between aircraft holding over the same holding fix. GM1 and GM2 to ATS.TR.210(c)(1), based on Sections 5.3.1, 5.3.4.1 and 5.3.4.1.1 of PANS ATM, provides guidance on the application of the vertical separation to aircraft in the various phases of TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 35 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note their flight, in particular as regards the allocation of different flight levels or altitudes, spaced by the appropriate minimum. AMC1 ATS.TR.210(c)(2), transposed from Sections 8.7.3.1 and 8.7.3.2 of PANS ATM, prescribes the horizontal separation minima to be applied in the various circumstances when ATC service is provided with the support of ATS surveillance systems. The associated GM1, derived from Sections 8.7.2.3, 8.7.2.4, 8.7.2.5, 8.7.2.6, 8.7.2.7, and 8.7.3.3 of PANS ATM, provides additional details on the application of such separation minima, on the basis of the type of ATS surveillance system available. GM1 ATS.TR.210(c)(2)(i), originating from Sections 5.4.2.1.1, 5.4.2.1.4, 5.4.2.1.5, and 5.4.2.1.6 of PANS ATM, provides guidance on the application of procedural longitudinal separation to aircraft, for which the related separation minima for the various circumstances are proposed in the following: — AMC1 ATS.TR.210(c)(2)(i), from Sections 5.4.2.2.1.1 and 5.4.2.2.1.2 of PANS ATM, addressing longitudinal separation minima based on time — aircraft maintaining the same level; — AMC2 ATS.TR.210(c)(2)(i), from Sections 5.4.2.2.2.1, 5.4.2.2.2.2, and 5.4.2.2.2.3 of PANS ATM, addressing longitudinal separation minima based on time — aircraft climbing or descending; — AMC3 ATS.TR.210(c)(2)(i), from Sections 5.4.2.3.3.1 and 5.4.2.3.3.2 of PANS ATM, addressing longitudinal separation minima based on distance using distance measuring equipment (DME) and/or GNSS — aircraft at the same cruising level; — AMC4 ATS.TR.210(c)(2)(i), from Sections 5.4.2.3.4.1 and 5.4.2.3.4.2 of PANS ATM, addressing longitudinal separation minima based on distance using distance measuring equipment (DME) and/or GNSS — aircraft climbing or descending; — AMC5 ATS.TR.210(c)(2)(i), from Sections 5.4.2.4.3 and 5.4.2.4.4 of PANS ATM, addressing longitudinal separation minima with Mach number technique based on time; — AMC6 ATS.TR.210(c)(2)(i), from Sections 5.4.2.5.2, 5.4.2.5.5, and 5.4.2.5.7 of PANS ATM, addressing longitudinal separation minima with Mach number technique based on distance using RNAV, for the application of which additional explanatory material is provided in the related GM1, transposed from the relevant content of Section 5.4.2.5 of PANS ATM. AMC3 ATS.TR.210(c)(2), based on Sections 5.11.1, 5.11.1.1 and 6.1 of PANS ATM, establishes the circumstances and the conditions for the application of a reduction to separation minima, as in the AMC related to procedural longitudinal separation minima listed above. With regard to the application of the longitudinal separation minima based on Mach number in AMC5 and AMC6 to ATS.TR.210(c)(2)(i), the discussions held with the RMG members concluded that their applicability and use within the EU context in uncertain. Therefore, in order to verify the applicability of these separation methods and minima in the EU context, the Agency invites the stakeholders to indicate whether these separation methods and minima are applied in their State and to what extent. AMC7, AMC8 and AMC9 to ATS.TR.210(c)(2(i), transposed respectively from the relevant contents of Sections 7.9.2, 7.10.1, and 7.11 of PANS ATM, establish the methods, with the related minima, for the application of longitudinal separation between aircraft for the use of the same runway for landing and/or departure, except when time-based wake turbulence separation, as in ATS.TR.220, is TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 36 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note applied. Detailed and articulated requirements for the reduction of such longitudinal runway separation minima under specified conditions are also provided. AMC10 and AMC11 to ATS.TR.210(c)(2)(i), derived from the relevant contents of Sections 5.6 and 5.7 of PANS ATM, prescribe methods and minima for the longitudinal separation between departing aircraft and between departing and arriving aircraft during the course of their flights, without prejudice to the runway separation methods and minima established in AMC7, AMC8 and AMC9 to ATS.TR.210(c)(2(i). AMC1 ATS.TR.210(c)(2)(ii), transposing various contents of Section 5.4.1.2.1 of PANS ATM, establishes the separation criteria lateral separation, which may be applied by various means, for which separation minima and associated conditions are provided. This AMC has to be read in conjunction with GM1 ATS.TR.210(c)(2)(ii), originating from Sections 5.4.1.1.1, 5.4.1.1.2, 5.4.1.1.4, which proposes general guidance for the application of lateral separation. Furthermore, the Agency has not deemed necessary to propose the transposition of the following horizontal separation methods and minima included in Chapter 5 of PANS ATM, as they have not been considered suitable in the context of the proposed EU ATS requirements: — ‘Lateral separation of aircraft on parallel or non-intersecting tracks or ATS routes’ in Section 5.4.1.2.1.6; — ‘Lateral separation of aircraft on intersecting tracks or ATS routes’ in Sections 5.4.1.2.1.7 and 5.4.1.2.1.8; — ‘Longitudinal separation minima based on distance using RNAV where RNP is specified’ in Section 5.4.2.6; — ‘Longitudinal separation minima based on distance using ADS-B in-trail procedure (ITP)’ in Section 5.4.2.7; — ‘Longitudinal separation minima based on distance using ADS-C climb and descend procedure (CDP)’ in Section 5.4.2.8, newly introduced with ICAO AN-WP/9014 (Amendment 7); and — ‘Performance-based longitudinal separation minima’ in Section 5.4.2.9, newly introduced with ICAO AN-WP/9014 (Amendment 7). ATS.TR.215, transposed from Sections 3.4.1 and 3.4.2 of Annex 11 and duplicated in SERA.8010, establishes the responsibilities of the ATS provider and the competent authority concerning the selection of the appropriate separation minima to be applied within given portions of airspace, the consultation with neighbouring ATS providers under specified conditions, and the notification of the established separation minima and their areas of application to the parties concerned. ATS.TR.220 stipulates the circumstances for the application of wake turbulence separation to aircraft in the approach and in the departure phases. This requirement is already included in SERA.8012 with a text which was transposing the principles, and not the exact content, of Section 8.7.3.4.1 of PANS ATM. The analysis of the content of PANS ATM led to the conclusion that the text of SERA.8012 requires an amendment to specify, in accordance with Sections 5.8.1.1 and 5.8.1.2 of PANS ATM, that wake turbulence separation does not have to be applied to arriving VFR flights, as well as to arriving IFR flights executing a visual approach, when the pilot of these flights has declared to have the preceding aircraft in sight and has been cleared to maintain own separation. In these cases, the TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 37 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note ATC unit concerned has to issue a warning of possible wake turbulence to the following aircraft. The proposed text of ATS.TR.220 includes these principles and, for consistency, it is proposed to amend SERA.8012 accordingly, as also explained in Section 2.7.2 below. AMC1 ATS.TR.220, based on Section 4.9.1.1 of PANS ATM, establishes a categorisation of aircraft based on the maximum certificated take-off mass for the purposes of the application of the appropriate wake turbulence separation minima. AMC2, AMC3, AMC4 and AMC5 to ATS.TR.220, transposed from various parts of Section 5.8 of PANS ATM, stipulate the time-based wake turbulence separation minima to be applied between aircraft of the established wake turbulence categories in various circumstances, namely: — between arriving aircraft; — between departing aircraft; — in case of displaced landing threshold; and — aircraft flying in opposite direction. AMC6 ATS.TR.220, derived from Section 8.7.3.4 of PANS ATM, prescribes the distance-based wake turbulence separation minima to be applied to landing and departing aircraft when ATS surveillance services are provided. With the entry into service of the Airbus A380-800, an aircraft which generates vortices more substantial than for other aircraft in the HEAVY wake turbulence category, on 8 July 2008, ICAO issued a letter (identified as ICAO TEC/OPS/SEP – 08-0294.SLG ‘Wake turbulence aspects of Airbus A380-800 aircraft’) in relation to the requirements on wake turbulence separation minima published in the PANS-ATM. With this letter, ICAO provided guidance concerning the recognition of such aircraft type through a specific designation (SUPER) in the call sign for the purposes of radiotelephony procedures, and indicated specific wake turbulence separation minima to be applied between such aircraft and those of the other wake turbulence categories. ICAO strongly encouraged States to implement this guidance pending an amendment to the PANS-ATM. At the time of the publication of this NPA, such recommendations have not been included in PANS ATM yet. In consideration of the safety relevance of this issue, and in order to ensure consistency with provisions in SERA.14065 ‘Radiotelephony procedures for air–ground voice communication channel changeover’ referring to the aircraft of ‘SUPER’ category, the Agency proposes to address the aforementioned recommendations in the AMC and GM related to ATS.TR.220. In order to minimise the impact on the Member States, AMC1 ATS.TR.220 leaves to the competent authority the prerogative to add a ‘SUPER’ category in addition to those established in accordance with PANS ATM; moreover, separation minima proposed for the Airbus A380-800 with the aforementioned ICAO letter are included in the AMC stipulating wake turbulence separation minima and associated with the optional ‘SUPER’ category. ATS.TR.225, transposed from Sections 3.5.1 and 3.5.2 of Annex 11, institutes the principle that each aircraft has to be provided with ATC service by a single ATC unit at any given time. In addition, it stipulates that ATC service has to be provided within a given block of airspace on an exclusive basis by a single ATC unit. Delegation of control to other ATC units is allowed subject to prior coordination between affected parties. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 38 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note ATS.TR.230, derived from the entirety of Section 3.6 of Annex 11, establishes the principles and the requirements for the transfer of the responsibility of control of aircraft between ATC units. Point (a) of this provision indicates in detail the modality (place and/or time) of the transfer of control between the various ATC units, or between control sectors or position within the same unit. In point (a)(2), the Agency proposes to explicitly address the transfer of control between two units providing approach control service, which was not contemplated in the original ICAO standard, by assimilating this case to the transfer of control between a unit providing area control service and a unit providing approach control service. Point (b) of the provision concerns the fundamental principles for the coordination between ATC units purposed to the transferring of control of aircraft, with particular regard to the specification of the responsibility of the transferring and accepting units, as well as of the exchange of relevant information concerning the flights subject to the transfer, in particular when this is effected by the use of ATS surveillance systems. In consideration of the advanced capabilities in the EU context of systems supporting the coordination between ATC units, the transposition of Section 3.6.2.4 of Annex 11 into point (b)(6) is proposed with a different formulation, which imposes the accepting unit to notify the transferring unit of the assumed control and the positive radio contact with a transferred aircraft only when so agreed between the ATC units concerned. Point (b)(7), which is aligned with the objectives of SERA.14001, requires the use of standardised phraseology for coordination between ATS units or sectors, and allows the use of plain language only is the absence of phraseologies suitable for the purposes of the coordination. AMC1 ATS.TR.230, based on Section 10.1.1.3 of PANS ATM, lists the elements which ATC units should address when setting the agreements for the coordination and the transfer of control of aircraft, while GM1 ATS.TR.230, originating from Sections 10.1.1.1 and 10.1.1.2 of PANS ATS, indicates the sequence of steps by which the units should effect the coordination and transfer process, and recommends the implementation of standardised procedures for this purpose. Accordingly, GM1 ATS.TR.230(a)(3)(i) and GM1 ATS.TR.230(a)(3)(ii), transposed respectively from the relevant provisions of Sections 6.5.2 and 6.3.2, provide guidance for the establishment of standardised procedures for transfer of control between the ATC units concerned and standard clearances for arriving and departing aircraft. A number of AMC and GM, mainly transposed from Chapter 10 of PANS ATM, is proposed to address in detail the procedures for the coordination and the exchange of information pertaining to the transfer of control of aircraft between the various ATC units, and, in particular: — AMC1 ATS.TR.230(b)(2) ‘Coordination between ATC units providing ATS within contiguous control areas — General’ derived from Sections 10.1.2.1.1 and 10.1.2.1.2 of PANS ATM; — AMC2 ATS.TR.230(b)(2) ‘Exchange of movement and control data between a unit providing area control service and a unit providing approach control service’, derived from Sections 10.1.3.3.1 (first sentence), 10.1.3.3.2, and 10.1.3.3.3 of PANS ATM; and — AMC3 ATS.TR.230(b)(2) ‘Exchange of movement and control data between a unit providing approach control service and a unit providing aerodrome control service’, derived from Sections 10.1.4.2.1 and 10.1.4.2.2 of PANS ATM. GM1 and GM2 to ATS.TR.230(b)(2), transposed from the relevant content of Sections 10.1.2.3 and 10.1.3.2, are proposed to address respectively the coordination for approval requests and for take- TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 39 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note off and clearance expiry time. GM3 ATS.TR.230(b)(2), based on Section 4.8.4 of PANS ATM, puts forward the coordination actions to be undertaken by an ATC unit upon notification of the intention of an aircraft to change from VFR to IFR. AMC1 ATS.TR.230(b)(7) prescribes the set of phraseologies, transposed without any modification from Section 12.3.5 of PANS ATM, to be used for the coordination between ATS units or sectors. It is recalled that this AMC proposes the transposition of phraseologies for coordination between ATS units in the context of PART-ATS, while phraseologies for air–ground communication are included in the SERA Regulation as they envisage collective pilot/ATS action. ATS.TR.235 stipulates the contents of the ATC clearances and addresses their utilisation in various operational contexts; additionally, it includes specific requirements for the read back of clearances by the controllers, as well as for clearance coordination between ATC units. The provision replicates a consistent portion of ATS-applicable requirements in SERA.8015, as amended by Regulation (EU) 2016/1185. Its contents are derived from various parts of Section 3.7 of Annex 11, as well as from relevant contents from Sections 4.5.1, 4.5.7.2, 4.5.7.4, 8.6.5.2 (with some modifications consistent with the proposal for amendment in the Final Report of ICAO EANPG meeting #57) and 12.2.7 of PANS ATM. In addition to the relevant provisions duplicated from SERA.8015, the following additional requirements are proposed: — Point (a)(5), points out the responsibility of controllers providing ATS surveillance services with respect to the assurance of obstacle clearance for IFR flights vectored or assigned a direct route which takes them off published ATS routes or instrument procedures. The associated GM1 clarifies that the prescribed obstacle clearance is assured when the flights concerned are cleared at or above the established minimum flight altitudes. The proposed requirement includes some modifications from the original Section 8.6.5.2 of PANS ATM, proposed in the Final Report of ICAO EANPG meeting #57, which specify in further detail the circumstances under which such provision is applicable; — Point (c), transposed from Section 3.7.1.2 of Annex 11, requires the ATS provider to assess the need to establish standard arrival and departure routes, in order to facilitate the issuance of ATC clearance and the handling of the traffic. As also explained in Section 2.7.2 below, it is proposed to introduce appropriate amendments to SERA.8015 points (a) and (d)(3)(ii) to ensure complete alignment with ATS-related provisions included in ATS.TR.235. A set of AMC and GM further details the application of the requirements in ATS.TR.235, in particular: — AMC1 ATS.TR.235(b) ‘Content of clearances for departing aircraft’, based on Section 6.3.1.1 of PANS ATM; — AMC2 ATS.TR.235(b) ‘Contents of standard clearances for departing aircraft’, based on Section 6.3.2.3 of PANS ATM; — AMC3 ATS.TR.235(b) ‘Clearances for arriving IFR flights’, based on Section 6.5.1.3 on PANS ATM; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 40 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note — AMC4 ATS.TR.235(b) ‘Contents of standard clearances for arriving aircraft’, based on Section 6.5.2.3 of PANS ATM; — AMC1 ATS.TR.235(b)(2) ‘Specification of clearance limit’, further elaborated by the related GM1, based on the contents of Section 4.5.7.1 of PANS ATM; — AMC1 ATS.TR.235(b)(4) ‘Instructions in clearances relating to levels’, based on Section 11.4.2.6.2.2 of PANS ATM; and — GM1 ATS.TR.235(b)(4) ‘Assignment of flight levels for controlled flights’, based on Sections 5.3.3.1, 5.3.3.6 ,and 5.3.3.7 of PANS ATM. ATS.TR.240, transposing the entirety of standards in Section 3.8 of Annex 11 and duplicated from SERA.3210(d)(4), requires the aerodrome control tower to control the movements of persons and vehicles on the manoeuvring area in order to avoid hazards to them or to aircraft operating on such area. For this purpose, points (c) and (d) afford maximum priority to vehicles assisting aircraft in distress, and establish the right of way among the various surface movements. Point (b) addresses the principles to be followed to manage the movement of persons and vehicles when low visibility procedures are applied. AMC1 ATS.TR.240(a), originating from Sections 7.6.3.2.1 and 7.6.3.2.2 of PANS ATM, further details the principles to be applied in the control of persons or vehicles, in particular as regards the need for an authorisation from the tower to access to the manoeuvring area and principally to a runway, and with regard to the criteria for holding distance of persons and vehicles from a runway when an aircraft is landing or taking off. AMC2 ATS.TR.240, transposed from Section 7.4.1.5.4 of PANS ATM, dictates to the aerodrome controller to undertake immediate action in case an aircraft or a vehicle is lost or is uncertain of its position on the manoeuvring area. ATS.TR.245 mandates the utilisation of the advanced surface movement guidance and control systems (A-SMGCS) or other suitable equipment when considered necessary to ensure a complete and adequate visual observation of the manoeuvring area, for the fulfilment of the objectives of the ATC service. While the originating Section 3.10 of Annex 11 referred to the use of ‘surface movement radar (SMR)’, the Agency explicitly proposes the use of A-SMGCS as a preferred technological solution in consideration of the related requirement in ADR.OPS.B.030 of Commission Regulation (EU) No 139/2014 and of the associated AMC and GM, as well as of the content of Section 6.5.6 of ICAO Doc 7030 EUR (part of which is proposed as GM1 ATS.TR.245) including specific requirements for the utilisation of such system in the European context. Point (a) of ATS.TR.250, transposed from Section 5.10.1.2, establishes the requirements for the provision of essential traffic information to controlled flights, for which a description is provided in GM1 ATS.TR.250(a). AMC1 ATS.TR.250(a), originating from Section 5.10.2 of PANS ATM, prescribes the elements of essential traffic information for transmission to aircraft concerned. Point (b) of ATS.TR.250, based on Section 6.2.1 of PANS ATM, addresses the provision of essential local traffic information, which in accordance with GM1 ATS.TR.250(b) consists of aircraft, vehicles or personnel on or near the manoeuvring area or in the airspace used for arrivals and departures, which may constitute an hazard to the aircraft concerned. AMC1 ATS.TR.250(b), derived from Sections 7.4.1.3.1 and 7.4.1.3.3 of PANS ATM, advises the timely and unambiguous provision of such information to aircraft for the sake of the safety of flights. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 41 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note ATS.TR.255 stipulates the requirements for the ATS providers concerning independent or dependent approaches or departures from parallel or near-parallel runways. The ICAO provisions for operations on parallel or near-parallel runways, principally included in Section 6.7 of PANS ATM, are a collection of specific requirements for communication, surveillance, and navigation integrated with a proven set of operational procedures and instructions. These provisions, when applied in the specified conditions, can be used to establish and maintain lateral separation of aircraft operating on parallel or near-parallel runways. All the details therein were part of the assumptions or identified as mitigating factors in the safety assessment of the specific subsets of the operations on parallel or near-parallel runways. When considering the application of these provisions, the underlying objective to maximise the throughput on the aerodromes with such runway layout should also be considered, in addition to the achievement of the objectives of ATC service. Consequently, following a thorough analysis of Section 6.7, in support of the implementation of ATS.TR.255, the Agency proposes its transposition into various AMC and GM which address the relevant aspects, including inter alia the necessary conditions to be met to conduct the various types of operations, the use of ATS surveillance systems, the separation minima, the information to be provided to aircraft, in particular: — GM1 ATS.TR.255, suggesting to consult the ICAO Manual on Simultaneous Operations on Parallel or Near-Parallel Instrument Runways (SOIR) (Doc 9643), to obtain guidance on operations on parallel or near-parallel runways; — AMC1 ATS.TR.255 ‘Requirements and procedures for independent parallel departures’, originating from Sections 6.7.2.1 and 6.7.2.2 of PANS ATM; — AMC2 ATS.TR.255 ‘Requirements and procedures for independent parallel approaches’, originating from Sections 6.7.3.1.2, 6.7.3.2.1, 6.7.3.2.2 first sentence, 6.7.3.2.3, 6.7.3.2.4, 6.7.3.2.10, and 6.7.3.3. The application of specific aspects of this AMC is further supported by 6 GM; — AMC3 ATS.TR.255 ‘Requirements and procedures for dependent parallel approaches’, originating from Sections 6.7.3.4.1, 6.7.3.4.2, and 6.7.3.4.3 of PANS ATM; and — AMC4 ATS.TR.255 ‘Requirements and procedures for segregated parallel operations’, originating from Sections 6.7.3.5.1, 6.7.3.5.2, and 6.7.3.5.3 of PANS ATM. It is pointed out that changes in the assumptions, functionalities or performances of the systems and procedures laid down in the ICAO provisions transposed under ATS.TR.255, have to be subject to a comprehensive safety assessment where such changes, including the additional failure modes, are identified and fully assessed, if variation to the existing provisions for the separation procedures in the proposed AMC is to be implemented. ATS.TR.260, transposed from Section 7.2.2 of PANS ATM, establishes the elements to be considered by a unit providing aerodrome control service when selecting the runway in use for the take-off and landing of aircraft. The related AMC1, based on Sections 7.2.4 and 7.2.6 of PANS ATM, addresses the interrelation between noise abatement and the selection of the runway in use. ATS.TR.265, based on Sections 7.12.1.1, 7.12.1.1.1, 7.12.1.1.2, and 7.12.2.1 of PANS ATM, includes specific measures to be applied in the provision of aerodrome ATC service, when the visibility conditions are such that prevent the application of a visual separation from the tower. Such TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 42 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note measures concern the definition of limits to hold at specified locations of the manoeuvring areas and the application of specific longitudinal separation minima, which have to be determined for each aerodrome and approved by the competent authority. It also institutes the ATS provider responsibilities with regard to the provisions for the conduct of Cat II and Cat III operations and for departure operations in RVR conditions less than 550 m, to be coordinated with the aerodrome operator and submitted to the competent authority for approval. AMC1 ATS.TR.265, based on Sections 7.12.3, 7.12.4, 7.12.5, and 7.12.6 of PANS ATM, prescribes the elements to be specified when addressing low visibility operations, and represents the pivotal role of the aerodrome control tower for the initiation of such operational mode, for the notification of its activation and deactivation and for the continuous monitoring of persons and vehicles allowed to enter the manoeuvring area. The provisions concerning low visibility operations proposed with this NPA may be subject to amendments as a result of the regulatory activities undertaken by the Agency under RMT.0379 ‘All- weather operations’, in particular as regards the definition of limits for low visibility operations. ATS.TR.270, transposed with textual modifications from Sections 7.14.1, 7.14.1.1, and 7.14.1.3 of PANS ATM, dictates the conditions for the issuance of authorisations to operate special VFR flights. With the exception of point (b) which requires the ATC unit to handle requests for special VFR individually, the remaining content of the provision is duplicated from SERA.5010. GM1 ATS.TR.270(a)(3), identical to GM2 SERA.5010(b), as proposed by the Agency with NPA 2015-14, clarifies that aircraft not intending to take off or land or enter the traffic circuit at the aerodrome when the ground visibility is less than 1 500 m may be cleared for special VFR to cross the affected control zone. ATS.TR.275 stipulates the requirements concerning the verification and the use of pressure-altitude- derived level information in the provision of ATC service when ATS surveillance systems are available. Point (a), derived from Section 8.5.5.1.2 of PANS ATM and duplicated from SERA 13010(b) introduced with Regulation (EU) 2016/1185, addresses the frequency at which such information is to be verified by ATCOs. AMC1 ATS.TR.275(a) establishes a tolerance value to be used in the verification of the accuracy of this information, while AMC2 ATS.TR.275(a) stipulates that the verification is to be done by comparing simultaneously the value observed and the value reported by the same aircraft. Point (b) prescribes the exclusive use of pressure-altitude-derived level information to determine that aircraft have acquired specific positions in respect of a given level. The application of this provision is further described in AMC1 ATS.TR.275(b), transposed from Sections 8.5.5.2.1, 8.5.5.2.2, 8.5.5.2.3, 8.5.5.2.4, and 8.5.5.2.5 of PANS ATM, in order to ascertain that aircraft: — maintain a level; — vacate a level; — pass a level in climb or descent; — reach a level. on the basis of given level occupancy criteria. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 43 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note 2.7.1.4.3. Section 3 — Flight information service This section pertains to rules that enable the provision of FIS, whose purpose is to provide advice and information useful for the safe and efficient conduct of flights. Therefore, an adequate provision of this service by the ATS units concerned is essential for the successful progress of aircraft operations. A number of technical references have been taken into account to regulate this particular service. As in other cases, ICAO Annex 11 and PANS ATM represent the core source of information to develop the proposed technical requirements and their corresponding AMC/GM; however, ICAO Circular 211- AN/128 and EUROCONTROL Manual for Aerodrome Flight Information Service (AFIS) have also been considered, so as to ensure the inclusion of specific provisions for AFIS. ATS.TR.300 establishes provisions for the application of FIS. Points (a) and (b), which are transposed from Sections 4.1.1 and 4.1.2 of Annex 11 and which duplicate those in SERA.9001 in the SERA Regulation, stipulate to what aircraft flight information is to be rendered and how ATC is to be assigned a higher priority over the provision of FIS when the relevant ATS units are responsible for both services. GM1 ATS.TR.300(b), derived from the Note to Section 4.1.2 of PANS, recognises that there might be circumstances taking place on the final approach, landing, take-off and climb, in which the provision of essential information can have precedence over ATC service. Point (c) pertains to the establishment of arrangements to record and transmit information on the progress of flights, as well as to ensure coordination and transfer of responsibility for the provision of the FIS. These contents are founded on the principles in Sections 9.1.1 and 9.1.2 of PANS ATM, though the proposed requirement underlines that the responsibility for putting in place the associated procedures rests with the FIS provider. AMC1 ATS.TR.300(c)(1), transposing the content of Section 9.1.1 of PANS ATM, addresses responsibility of the ATS unit serving the FIR for recording information on the progress of flights, as well as for transmitting it to other ATS units concerned with the provision of flight information and alerting services in adjacent FIRs, so as to ensure coordination in respect of IFR and VFR flights. AMC1 ATS.TR.300(c)(2), based on Section 9.1.2 of PANS ATM, addresses the coordination and transfer of responsibility between ATS units providing services in adjacent FIRs, so as to ensure that, as far as practicable, flight information can be provided to the aircraft at all times. GM1 ATS.TR.300(c)(2) transposes Section 10.1.2.5 of PANS ATM with the purpose of indicating that ATC units should make available the necessary information to other ATS units concerned with the flight, whenever an aircraft is no longer operated as a controlled flight. GM2 ATS.TR.300(c)(2), which is based on Sections 10.2.1, 10.2.2, 10.2.3, 10.2.4 and 10.2.5 of PANS ATM, explains the need for ATS units to establish appropriate agreements addressing the coordination for the provision of flight information and alerting services to aircraft operating across adjacent FIRs in specified routes or areas, in order to ensure continuity of FIS. In particular, this provision describes some essential information to be transmitted in respect of IFR and VFR flights operating in specified areas or along specified routes, in order to facilitate the transfer of responsibility between ATS units providing those services in adjacent FIRs. It also addresses the exchange of information in relation to aircraft operating along specified areas in close proximity to FIR boundaries, with the purpose of limiting the need for interception. Finally, it underlines the importance of reporting on an emergency situation to any ATS unit concerned with the flight and, if necessary, to the associated rescue coordination centre. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 44 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note ATS.TR.305 defines the scope of FIS, and, as a novelty compared to the original Annex 11 provisions from which it originated, includes explicit requirements for AFIS. Points (a) and (b), which are based on Sections 4.2.1 and 4.2.2 of Annex 11, describe general information pertaining to the provision of the FIS. Both had already been transposed as SERA.9005(a) and SERA.9005(b) respectively into the SERA Regulation. However, the Agency proposes to introduce, in addition, the requirement to inform the pilots of any abnormal aircraft configuration and condition known by the ATCO or by the AFIS officer, as considered in Section 7.4.1.7 of PANS ATM, which is in turn transposed as AMC1 ATS.TR.305(a)(7) to ensure its implementation and provide clarification on this matter. Consequently, the Agency proposes to amend SERA.9005(a) as explained also in Section 2.7.2 below. Furthermore, point (c) specifies the additional information to be provided to aircraft by AFIS units, in consideration of the specific aerodrome environment. Such additional information is derived from the ICAO Circular 211-AN/128. It is important to point out that AFIS units are in charge of providing FIS and alerting service, and that in no circumstances are they authorised to undertake actions related to the provision of ATC, such as issuing instructions to aircraft and vehicles on the ground, or selecting the runway to be used for take-off and landing at the aerodrome, which should remain a prerogative of the pilots. With respect to the need for transmission of special and non-routine air-reports, point (d) reproduces SERA.12020 of the SERA Regulation and adds a reference to Appendix 5 to the SERA Regulation in order to improve its understanding. Its content is based on the recommended practice in Section 4.2.3 of Annex 11. Duplicating SERA.9005(c) of the SERA Regulation, point (e) equally transposes Section 4.2.4 of Annex 11, so as to ensure that information on traffic and weather conditions that may adversely affect the progress of VFR flights along their routes are also contemplated within the scope of the service. AMC1 ATS.TR.305, based on Sections 9.1.3.1.1, 9.1.3.1.2, 9.1.3.2.1, 9.1.3.2.2, 9.1.3.3, 9.1.3.4, 9.1.3.5.1, 9.1.3.5.2, 9.1.3.6, and 9.1.3.7 of PANS ATM, sets out means of transmission in order to enable the provision of flight information; it specifically addresses procedures for the transmission of information concerning air-reports, SIGMET, AIRMET, volcanic activity, radioactive materials, toxic chemical clouds, SPECI, amended TAF, heavy or medium unmanned free balloons to aircraft, as well as supersonic aircraft, when applicable. AMC1 ATS.TR.305(a);(b) transposes Section 6.4.1 of PANS ATM with the purpose of making up-to- date information available to departing aircraft by the unit providing approach control service, whenever significant changes in meteorological conditions occur. The associated GM1 to AMC1 ATS.TR.305(a);(b), based on the Note to Section 6.4.1 of PANS ATM, specifies what is meant by ‘significant changes’ by providing a list of relevant meteorological phenomena. In line with the general objective of better defining and harmonising the provision of AFIS, four GM are proposed to indicate the information to be issued by AFIS units to the aircraft concerned; such GM are derived from the ICAO Circular 211-AN/128 and from the EUROCONTROL AFIS Manual. More specifically: — GM1 ATS.TR.305(a);(b);(c), based on the contents of paragraph 6.d) ‘General’ of the ICAO Circular 211-AN/128, provides a list of relevant information on aerodrome conditions and changes in such conditions that an AFIS unit should transmit to aircraft; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 45 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note — GM2 ATS.TR.305(a);(b);(c), reflecting the content of Section 3.4.1 of the EUROCONTROL AFIS Manual, points out specific traffic information that an AFIS unit should provide to aircraft; — GM3 ATS.TR.305(a);(b);(c), based on Section 3.4.2 of the EUROCONTROL AFIS Manual, addresses the need to make available information on local traffic to the aircraft concerned in order to ensure safety; — GM4 ATS.TR.305(a);(b);(c), originating from Section 3.4.5 of the EUROCONTROL AFIS Manual, provides information on wake turbulence and jet blast with the purpose of indicating AFIS units to:  take due account of hazards associated with these phenomena, and  as far as practicable, advise aircraft, vehicles or personnel potentially affected by them. AMC1 ATS.TR.305(a)(5), transposed from Section 7.5.3 of PANS ATM, underlines the importance of a timely and clear transmission of essential information with regard to aerodrome conditions unless it is known that information has already been received by the aircraft from other sources. The related GM1 to AMC1 ATS.TR.305(a)(5) explains what is meant by ‘essential information on aerodrome conditions’ and provides a list of examples to illustrate this matter on the basis of the contents of Sections 7.5.1, 7.5.2 and of the Note to Section 7.5.2 of PANS ATM. AMC2 ATS.TR.305(a)(5), which transposes Section 6.4.2 of PANS ATM, underlines the need to transmit changes in the operational status of essential visual and non-visual aids to departing aircraft whenever these changes remain unknown by the flight crew and may have an impact on take-off and climb operations. GM1 ATS.TR.305(a)(6), transposed from Sections 16.2.1, 16.2.2 and 16.2.3 of PANS ATM, describes the list of information concerning the intended flight of medium or heavy free balloons and the circumstances under which the ATS units are required to disseminate such information to all concerned, which may include also recipients other than aircraft and other ATS units (e.g. military organisations). In this case, the notification could be configured as an action outside the scope of FIS, which related to the provision of information to aircraft. GM1 ATS.TR.305(b)(2) is a duplication of GM1 SERA.9005(b)(2), whose contents were based on the Note to Section 4.2.2(b) of ICAO Annex 11. It draws attention to the fact that ATS units may not always be totally aware of every activity that may constitute a collision hazard. Thereby, it represents the limitation in terms of accuracy of information, and clarifies the limited responsibilities of ATS units in this context. GM1 ATS.TR.305(c)(1), on the basis of the content of Section 4.2.7 of the EUROCONTROL AFIS Manual, addresses the AFIS units to advise landing or departing aircraft of any potential runway incursion or obstruction. GM1 ATS.TR.305(c)(2) provides guidance to AFIS units on the factors and on the operational elements to be considered in the selection of the most suitable runway for use at AFIS aerodromes. Its content has its origin in Section 3.2.2 of the EUROCONTROL AFIS Manual. ATS.TR.310, based on Sections 4.3.4.1, 4.3.4.2, 4.3.4.3, 4.3.4.4, 4.3.4.5, 4.3.4.6, and 4.3.4.8 of Annex 11, regulates the various aspects of the provision of Voice-ATIS broadcasts, such as the allocation of messages to departing and/or arriving aircraft depending on local circumstances, the proper use of TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 46 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note the frequencies for transmission, the duration of broadcast message, the broadcast language which should be as a minimum in English, etc. GM1 ATS.TR.310(f), transposing the recommended practice in Section 4.3.4.7 of Annex 11, suggests the use of different channels when an ATIS message is broadcast in different languages. GM1 ATS.TR.310(g), reflecting the second part of the recommended practice in Section 4.3.4.8 of Annex 11, emphasises the need to take human factors into account when preparing Voice-ATIS message in order to ensure pilot’s understanding. ATS.TR.315, based on Sections 4.3.5.1, 4.3.5.1.1, and 4.3.5.2 of Annex 11, regulates the transmission of ATIS via data link and stipulates that, when D-ATIS is provided, full consistency has to be ensured with the content of Voice-ATIS broadcasts. It also indicates the criteria to keep the message designator when changes to meteorological information has to be incorporated. The related GM1 ATS.TR.315 indicates the ICAO Manual of Air Traffic Services Data Link Applications (Doc 9694) as a source of information concerning D-ATIS broadcasts. ATS.TR.320, whose content is based on Sections 4.3.6.1, 4.3.6.2, 4.3.6.3, and 4.3.6.4 of Annex 11, prescribes some relevant aspects of ATIS (both voice and data link) broadcasts regarding messages preparation and update, dissemination process, acknowledgment of receipt and complementary transmissions to provide the aircraft with additional information or, whenever necessary, to correct ATIS messages. Points (a)(5), (a)(6), (c) and (d) of ATS.TR.320 had been previously transposed as SERA.9010(a)(2), SERA.9010 (a)(3), and SERA.9010 (a)(4), respectively. GM1 ATS.TR.320 refers to SERA.9010(b), (c) and (d) of the SERA Regulation, which prescribe in detail the contents of ATIS messages for arriving aircraft, departing aircraft or both. GM1 ATS.TR.320(d) proposes that updates to information included in the ATIS messages are always made available to aircraft, either by instructing the aircraft to find them via the ATIS broadcast available or specifically transmitted by the ATS unit. ATS.TR.325 adopts the recommended practices in Sections 4.4.1 and 4.4.2 of Annex 11, related to the use of VOLMET and D-VOLMET broadcasts, which have to be provided at the discretion of the competent authority and, in any case, using standard radiotelephony phraseologies. In addition, GM1 ATS.TR.325, derived from the Note to Section 4.4.2 of Annex 11, provides a reference to ICAO Doc 9377 as a source of guidance material on standard radiotelephony phraseologies to be used in VOLMET broadcasts. As a result of the analysis of the content and the application of Section 4.3 ‘Operational flight information service broadcasts’ of Annex 11, the Agency, supported by RMG.0464, concluded that there was no evidence that HF and VHF operational flight information service (OFIS) broadcasts, as described respectively in Sections 4.3.2 and 4.3.3, are provided anywhere in the EU. On these grounds, the Agency decided not to propose requirements for these information services. In order to validate this approach, the Agency requests its stakeholders: — to indicate if they agree with this approach; and — to indicate if they are aware of any provision of HF and VHF OFIS broadcasts in the EU, and, should this be the case, to provide more detailed information. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 47 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note 2.7.1.4.4.Section 4 — Alerting service Alerting service consists of the notification to appropriate organisations regarding aircraft in need of search and rescue aid, and of support to such organisations as required. Alerting service is provided by FICs, ATC units and AFIS units to assist aircraft considered or known to be in a state of emergency. Due to the importance of alerting service, there is a clear need to set out specific technical requirements, complemented by AMC and GM. The proposed rules are based on applicable SARPs included in Chapter 5 of ICAO Annex 11, together with specific procedures derived from PANS ATM, particularly Section 9.2, as well as other sections addressing the necessary ATS coordination to render assistance and prompt notification of an emergency situation to rescue coordination centres and nearby rescue and firefighting services. ATS.TR.400, established on the transposition of Sections 5.1.1, 5.1.2, 5.1.3, and 5.1.3.1 of Annex 11, determines what aircraft are to be provided with alerting service and addresses essential responsibilities and coordination amongst stakeholders involved in the assistance. This provision explicitly includes AFIS units in its scope. It is important to mention that ATS.TR.400(a) duplicates SERA.10001(a). In addition, ATS.TR.400(d) adds the requirement, derived from the transposition of the first sentence of Section 7.1.2.2 of PANS ATM, to determine in local instructions the coordination procedures with the rescue and firefighting services. More details on the local instructions are provided in AMC2 ATS.TR.400(d), which transposes the remaining content of Section 7.1.2.2 of PANS ATM. AMC1 ATS.TR.400(d) identifies what circumstances should make an ATS unit to alert the rescue and firefighting services. It is based on Section 7.1.2.1 of PANS ATM, but introduces some differences in respect of the ATS units that could alert the local rescue and emergency services. Instead of limiting its scope to an aerodrome control tower, the proposal also includes approach control units and AFIS units in order to: — set in motion the local emergency procedures, whenever the need for assistance is already known or anticipated by the corresponding approach control unit; and — take into account aerodromes where AFIS is provided instead of aerodrome control service. GM1 ATS.TR.400(b), transposed from Sections 9.2.2.2, 9.2.2.3, and 9.2.2.4 of PANS ATM, aims at determining what ATS unit is responsible for the coordination of the alerting service whenever a flight is operated through more than one FIR or control area, and when the position of the aircraft is in doubt. It also points out the main actions to be taken by the unit responsible so as to ensure the provision of the alerting service. ATS.TR.405, based on Sections 5.2.1, 5.2.2, 5.2.2.1, and 5.2.3 of Annex 11, pertains to the definition of emergencies subject to notification to the rescue coordination centre in accordance with certain emergency phases (uncertainty, alert and distress phases), which are described one by one in details. It also stipulates the information that needs to be made available and the order in which each of the elements of the messages is to be conveyed when the emergency phases are reported to the rescue coordination centre. AFIS aerodromes are addressed explicitly in respect of the declaration of the alert phase due to the operational context described in the provision, in order to take account of any specific circumstances prescribed by the competent authority, as described in GM1 ATS.TR.405(a)(2)(iii). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 48 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note GM1 ATS.TR.405(a)(1), transposed from Section 9.2.2.1 of PANS ATM, emphasises the need to try to obtain a report from an aircraft within the stipulated period of 30 minutes prior to the declaration of the ‘uncertainty phase’ whether circumstances warrant such application. GM1 ATS.TR.405(a)(2)(ii), based on Section 7.1.2.3 of PANS ATM, is specific for aerodrome control towers and addresses coordination with all relevant units or centres and the need to launch the alert phase in respect of arriving aircraft that fail to land 5 minutes after the expected landing time and radio contact is no longer possible. GM1 ATS.TR.405(a)(2)(iii) indicates that the same procedure is applicable by the AFIS units, but the 5-minute element is replaced by a time interval to be determined by the competent authority. GM1 ATS.TR.405(c) is not derived from ICAO provisions, but its development together with ATS.TR.405 was necessary to make clear that any anticipated information not available at the time the notification of the distress phase is made to a rescue coordination centre should be clearly indicated by the ATS unit. GM1 ATS.TR.405(d), transposing a note to Section 5.2.3 of Annex 11, clarifies that cancellation of actions initiated by the rescue coordination centres is responsibility of that centre, irrespective of any information received from the ATS units regarding the state of aircraft involved. ATS.TR.410, transposed from Section 5.3 of Annex 11, mandates that ATS units make use of any available communication facilities to keep in contact with the aircraft involved and also to collect all information relevant to its state of emergency. ATS.TR.415 stipulates the obligation to continuously determine or estimate the position of an aircraft considered to be in a state of emergency by all ATS units aware of the existing situation. Its content is based on the first sentence of Section 5.4 of Annex 11, but this proposal additionally contemplates the use of any possible means to monitor the estimated position of the aircraft rather than being restricted to the use of charts, so as to make the most of available technology. AMC1 ATS.TR.415 established by the transposition of the first sentence of Section 8.8.1.2 of PANS ATM, points out the use, whenever available, of ATS surveillance systems to assist in tracking the position of an aircraft subject to an emergency situation. It also contemplates the need to share this kind of information with other ATS units that could render assistance to the aircraft involved. ATS.TR.420, based on Sections 5.5.1 and 5.5.2 of Annex 11, is pertinent to coordination to be established by the ACC or FIC with the aircraft operator prior to the notification to the rescue coordination centre of the uncertainty or alert phase, whenever practicable. Also, it establishes that all information communicated to the rescue coordination centre has also to be shared with the aircraft operator as soon as practicable. ATS.TR.425, transposed from Sections 5.6.1 and 5.6.2 of Annex 11 and duplicated as in SERA.10005, addresses the requirement for ATS units to share information on aircraft in a state of emergency with other aircraft in its vicinity, and prescribes specific limitations for air–ground communication from the ATS units in case of aircraft subject to unlawful interference. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 49 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note 2.7.1.5. Amendments to Annex V — Subpart A ‘Additional organisation requirements for providers of meteorological services (MET.OR)’ MET.OR.242 Having explicitly recognised the AFIS unit within the scope of ATS units, the Agency proposes to amend the content of point (a) of MET.OR.242 ‘Information to be provided to air traffic services units’, in order to define the set of meteorological information which the relevant meteorological office has to provide to the AFIS unit. Such information is identical to that to be provided to aerodrome control tower, unless otherwise specified by the competent authority, under the conditions stipulated in point (a) of ATS.OR.515. MET.OR.245 Section 7.6 of Annex 11 stipulates, inter alia, that information concerning the release into the atmosphere of toxic chemicals is to be made available to ATS units when such phenomenon could affect the airspace under their responsibility. Provisions in Chapter 3 of Section 2 of Subpart A of Annex V ‘Part-MET’ do not include such requirement when establishing the set of information to be provided by the meteorological watch office to the various ATS units. For this purpose, it is proposed to amend MET.OR.245 in Annex V by introducing a new point (g) dictating the meteorological watch office to provide such information to the ATS units concerned. 2.7.2. Amendments to the SERA Regulation This section contains the explanatory notes to the amendments to the SERA Regulation, which are included in Section 1.2 of NPA 2016-09(B), and more specifically: Additional recital Serving the same purpose as that of the proposed introduction of a recital in the ATM/ANS Common requirements Regulation, this recital is introduced to represent and highlight the very close interrelation between the proposed requirements in PART-ATS and those in the SERA Regulation, as successively amended. Definition of ‘controlled aerodrome’ The rationale behind and the content of the proposed modification to the definition of ‘controlled aerodrome’ are provided in Section 2.7.1.2 above. In order to ensure consistency, it is proposed to amend such definition also in the SERA Regulation. SERA.8005 The amendments to SERA.8005, considered necessary to better clarify the existing provisions, are proposed to ensure full consistency with ATS.TR.210. The term ‘instructions’ is introduced in SERA.8005(a)(3) to make explicit that the issuance of instructions, for which a definition originating from PANS ATM is proposed for inclusion in Annex I, is a specific task of the ATC units, as resulted also from the analysis of the relevant ICAO ATC-related provisions. The amendment in the opening sentence of SERA.8005(c) is proposed as a consequence of the introduction in ATS.TR.255 of requirements for operations on parallel or near-parallel runways derived TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 50 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note from the transposition of Section 6.7 of PANS ATM, which include separation minima and criteria representing an exception to the general principle expressed in this context. The amendment to SERA.8005(c)(1), transposed from Section 5.2.1.4 of PANS ATM, prevents that geometric height information is used to establish vertical separation. SERA.8012 The proposed amendment aims at completing the original SERA provision addressing the application of wake turbulence separation and is full consistent with ATS.TR.220. The analysis of Section 5.8 of PANS ATM allowed the identification of categories of flights in specific phases, for which wake turbulence is not to be applied and for which instead ATC is required to notify the pilots concerned about the risk to encounter wake turbulence. SERA.8015 The proposed amendment to SERA.8015(b)(6), fully consistent with ATS.TR.235(a)(5), results from the transposition of Section 8.6.5.2 of PANS ATM, including the modifications agreed in the Final Report of ICAO EANPG #57. It stipulates the responsibility for the ATC to issue, under specific circumstances, clearances assuring the prescribed obstacle clearance. The proposed amendment to SERA.8015(d)(3)(ii), consistent with ATS.TR.235(b)(3)(ii), aligns the text of the provision with the current version of Section 4.5.7.2 of PANS ATM from which it is transposed, which has been subject to modification by ICAO AN-WP/9014 (Amendment 7 to PANS ATM). SERA.9005 The proposed amendment, fully consistent with ATS.TR.305(a)(7), introduces the obligation to provide, within the scope of FIS, information to aircraft when the aerodrome control tower or the AFIS unit observes or becomes aware that such aircraft displays an abnormal condition or configuration (e.g. landing gear not extended, unusual smoke emission). SERA.14095 This provision, originating from Section 4.1.3.1.1 of Annex 10 Volume V and also proposed as ATS requirement (ATS.OR.405(a)), establishes the conditions for the use of the VHF emergency channel. As the requirement addresses various entities (e.g. aircraft, entities involved in search and rescue operations, etc.), and not only ATS units, it is considered appropriate to include it in SERA.14095 as well. 2.7.3. Amendments to ED Decision 2013/013/R (AMC/GM to the SERA Regulation) This section contains the explanatory notes to the amendments to the ED Decision 2013/013/R (AMC/GM to the SERA Regulation) included in Section 1.4 of NPA 2016-09(B), and more specifically: GMX SERA.14095 The proposed amendment, fully consistent with GM2 ATS.TR.210(c)(1) indicates the possible sources of geometric height information which, according to the amendment to SERA.8005(c) described above, are not to be used for the purposes of establishing vertical separation between aircraft. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 51 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 2. Explanatory note GMY SERA.14095 The introduction of this GM, fully consistent with GM1 ATS.OR.405(a)(3), also in relation to SERA.14095, better specifies the condition for the use of the VHF emergency channel in case of search and rescue operations. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 52 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) 3. Regulatory impact assessment (RIA) 3.1. Problem definition 3.1.1. ATS regulatory framework 3.1.1.1. The ICAO ATS regulatory context Since decades, ATS have been provided globally in accordance with the SARPs included in Annex 2 and in particular in Annex 11 to the Chicago Convention. ICAO Contracting States, including all EU States, are required to apply such SARPs, or to notify ICAO of any difference between the Standards and the national regulation and practices, and invited to do so as far as Recommended Practices are concerned. In order to establish more detailed guidance on the implementation of the ATS provisions established in the Annexes, which are often expressed in the form of principles, ICAO publishes and maintains a set of related documents (e.g. Doc 9426 ‘Air Traffic Services Planning Manual’). The most relevant of such documents for the purposes of ATS is Doc 4444 ‘Air Traffic Management’, also known as PANS ATM, which specifies, in greater detail than in the SARPs, the actual procedures to be applied by the relevant units in providing the various ATS to air traffic. Procedures for Air Navigation Services (PANS) may contain material which may eventually become Standards or Recommended Practices when it has reached the maturity and stability necessary for adoption as such. PANS may also comprise material prepared as an amplification of the basic principles in the corresponding SARPs, and designed particularly to assist the user in their application. The implementation of PANS is the responsibility of the Contracting States, which are not obliged to notify differences in the event of non-implementation, as instead is the case for SARPs; ICAO, however, recommends States to publish differences from such PANS in the national Aeronautical Information Publication (AIP). 3.1.1.2. The current EU ATS regulatory context Since the initial introduction of EU legislation addressing the provision of ATS (Regulation (EC) No 2096/2005), the aforementioned ICAO documents, and in particular the SARPs, were considered as the regulatory reference for the provision of ATS. Therefore, within Regulation (EC) No 2096/2005, a requirement (in Chapter 4 of Annex II) stipulated that providers had to apply working methods and operating procedures compliant with those in ICAO Annex 2, Annex 10 Volume II, and Annex 11, when providing ATS. The same provision (with updated references to successive editions of the said ICAO material) was replicated in Regulation (EU) No 1035/2011 which repealed Regulation (EC) No 2096/2005, and successively amended by replacing the reference to ICAO Annex 2 with a reference to the SERA Regulation which in the meantime transposed ICAO Annex 2 into the EU legislation with the purpose of establishing the common European rules of the air. The ATM/ANS Common Requirements Regulation has maintained this provision referencing to ICAO (in Annex IV, Subpart B, Section 1), with the updated reference to the latest editions of the Annex 10 Volume II and Annex 11. Said provision is expected to be replaced by a comprehensive set of requirements addressing the provision of ATS, proposed with this NPA. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 53 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) 3.1.1.3. Transposing ICAO ATS provisions into the EU aviation safety regulatory framework In recognition of the fundamental reference of the ICAO SARPs and PANS for the provision of ATS, and of the related obligations of the EU Member States towards the Chicago Convention, when developing rules for the implementation of the principles and of the Essential Requirements on ATM/ANS stipulated in Annex Vb to the Basic Regulation, the Agency decided to transpose the relevant ICAO provisions into the EU legislation. This approach supports the achievement of the objective established in Article 2(d), which is ‘to assist Member States in fulfilling their obligations under the Chicago Convention, by providing a basis for a common interpretation and uniform implementation of its provisions, and by ensuring that its provisions are duly taken into account in this Regulation and in the rules drawn up for its implementation’. With this approach, a full harmonisation of the implementation of the ICAO provisions throughout EU would be achieved, by eliminating the numerous differences established by the divergent national interpretations and implementation of ICAO SARPs and PANS. Differences in the implementation would still be possible at a local level under the EU legal mechanisms allowed by Article 14 of the Basic Regulation and/or, when applicable, by the submission of alternative means of compliance. The SERA Regulation including the amendments introduced with Regulation (EU) 2016/1185, and the ATM/ANS Common Requirements Regulation, specifically for MET requirements and AIS requirements (proposed with NPA 2016-02 ‘Technical requirements and operational procedures for aeronautical information services and aeronautical information management’), with the associated AMC and GM, were in fact developed by transposing the relevant ICAO provisions into the EU legislation, in accordance with the principles described above. In particular, there is a strong interrelation between PART-ATS and the SERA Regulation, due to the complementary nature of the two regulatory packages; SERA has already transposed a significant number of Annex 11 and PANS ATM provisions, which are duplicated in or complementary to those proposed in PART-ATS with this NPA. In the given context, the decision to transpose the ICAO reference material to establish EU ATS requirements was not an option, but an approach established and consolidated by other ATM/ANS- related regulatory activities which preceded the initiation of this rulemaking task. For this reason, a pre-RIA on the need for and on the most appropriate method to develop RMT.0464 was not performed; hence, the Terms of Reference for RMT.0464, issued following the Agency’s Advisory Bodies’ consultation without substantial comments, did explicitly mandate the transposition approach. Therefore, the regulatory package proposed with this NPA responds to the regulatory mandate of the Basic Regulation with regard to the provision of ATS, in particular by implementing the Essential Requirements in Chapter 2.(c) of Annex Vb. It substitutes the reference to ICAO Annex 10 Volume II and Annex 11, and to the SERA Regulation with a complete package of IRs, and the associated AMC and GM. The proposed measures were developed by analysing and transposing, on a case-by-case basis and in full respect of their original regulatory force under the ICAO framework, the content of Annex 10 Volume II, Annex 11, PANS ATM, Doc 7030 EUR and other relevant material. The package transposes TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 54 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) those ICAO provisions which were considered by the Agency and RMG.0464 as suitable for the EU context, with the necessary modifications to fit into the EU regulatory framework. In this context, the Agency does not consider necessary to perform a detailed RIA on the establishment of EU ATS requirements transposing the ICAO relevant material. Instead, a full RIA is performed with regard to the introduction of measures addressing the provision of AFIS, which is not explicitly addressed by the referenced transposed ICAO material. 3.1.2. AFIS 3.1.2.1. Introduction AFIS is included in the scope of ATS; more specifically it is a subset of FIS, when such service is provided at an aerodrome and in its vicinity. AFIS units provide information and advice to aircraft to achieve a safe, orderly and expeditious flow of air traffic at and close to an aerodrome in order to assist pilots in preventing collision between aircraft flying within their area of responsibility. AFIS includes, inter alia, traffic information, information on the meteorological conditions at and in the vicinity of the aerodrome, information on the aerodrome conditions. AFIS is a widespread practice throughout the world, and is also widely implemented across the EASA Member States. This is particularly the case in Scandinavian countries. In the case of Norway, information gathered indicated that in 2015 there were 33 airports where AFIS is provided, with about 181 000 movements. Spain is progressively opening the door to this type of service provision and as of September 2014, more than 30 airports were awaiting for the approval from the competent authority. In France, there are 67 aerodromes where AFIS is provided full time or in alternation with ATC service. Such alternation, which is established also at aerodromes in other States, follows differing criteria (e.g. weekends versus working days, different timeframes during the same day according to the type and demand of traffic or seasonal alternation). 3.1.2.2. Current regulatory framework on AFIS AFIS in the ICAO context At international level, the relevant ICAO documentation, and in particular Chapter 4 of Annex 11 Chapter 4 and Section 9.1 of PANS ATM, both titled ‘Flight Information Service’, does not contain specific and comprehensive requirements for the provision of AFIS for binding or recommended application in accordance with the Chicago Convention. The sole ICAO document explicitly addressing this subject matter is the Circular 211-AN/128 ‘Aerodrome Flight Information Service’ issued in 1988 (and never amended since), which includes guidance material of a non-binding nature, recommended for application at ‘aerodromes used by international General Aviation where the type and density of traffic clearly do not justify the provision of aerodrome control service’. The same Circular recommends not to implement AFIS at aerodromes with international commercial air operations. Consequently, when establishing and providing AFIS, States are only required to fulfil their obligations under the Chicago Convention with regard to FIS, which in some cases are not suitable or not specific enough for the aerodrome environment where AFIS is provided. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 55 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) The EUROCONTROL AFIS Manual As a recognition of the need for better definition and harmonisation of the provision of AFIS at least in the European Civil Aviation Conference (ECAC) area, in 2010 EUROCONTROL published the EUROCONTROL Manual for Aerodrome Flight Information Service (AFIS). This document, which is also of non-binding nature, builds on ICAO subject matter provisions as well as on feedback from affected European stakeholders on the various aspects of AFIS provision, as a result of an extensive consultation process. The evidence in the EASA AFIS survey as in Section 3.1.2.3 showed that this document is considered as reference document for many aspects by some, but not by all, EU Member States when implementing and delivering such a service. AFIS in the EU legislation As explained in Section 3.1.1, when the ATM/ANS Common Requirements Regulation comes into force, the technical requirements for the provision of ATS, and implicitly for the provision of AFIS, will be established in Section 1 of Subpart B of Annex IV, by reference to ICAO Annex 10 Volume II, Annex 11 and to the SERA Regulation. As such, the status quo compared to Regulation (EU) No 1035/2011 is maintained, with the lack of an explicit set of requirements addressing the various aspects of AFIS provision. The EU legislation will still refer to ICAO documentation which does not match the providers' needs or match actual practice in the European context. In accordance with the applicable EU regulations, the certification of AFIS providers, being ATM/ANS providers, is mandatory (Regulation (EU) No 1035/2011), as well as their designation by the State concerned (Regulation (EC) No 550/2004). In addition, Article 5(4) of Regulation (EU) No 1035/2011 enables the competent authorities to grant derogations for the certification of AFIS providers under specified circumstances. The ATM/ANS Common Requirements Regulation maintains the obligation for the certification of AFIS providers, but enables an enhanced flexibility, by introducing the possibility for these providers to apply for a limited certificate or for a declaration, subject to specific circumstances and conditions. The derogations option is therefore removed. 3.1.2.3. The EASA AFIS survey Within the activities of RMT.0464, and according to the principle of evidence-based legislation, in 2015 the Agency launched a survey (hereinafter referred to as ‘the EASA AFIS survey’) addressed to the members of the ATM/ANS and Aerodromes (ADR) TAG and Sub-SSCC, with the purpose of collecting additional information on existing practices and trends throughout the EASA Members States on the provision of AFIS. The questionnaire of the survey was built around the issues identified by RMG.0464, as well as on the outcome of Standardisation Inspections routinely performed by the Agency. The survey received responses from civil aviation authorities, associations, air navigation service providers, airport operators, trade unions, manufacturers and AFIS operators from 27 EASA Member States covering most of the European territory. The analysis of the feedback received by respondents supports this RIA and is published as information material on the Agency website along with the present NPA. As evident in Figure 1, the survey indicated that the majority of the responding EASA Member States have implemented AFIS. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 56 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) Figure 1: Replies to the EASA AFIS survey Replies to the EASA AFIS survey show that the majority of AFIS aerodromes score medium/low traffic figures (hundreds or a few thousands movements per year). However, some aerodromes scored significant movements figures (even more than 54 000 movements on a yearly basis), but this was recorded at aerodromes with alternation of AFIS and ATC, without a specification of traffic figures related to timeframes when AFIS was provided. Figure 2 summarises replies from States which declared to have aerodromes with alternation between AFIS and ATC service. Figure 2: AFIS/ATC alternation17 17 The total of the States equals to 26, that is one less compared to the total States mentioned above (27). This is due to the fact that a respondent did not provide a detailed answer on the questionnaire (e.g. on the question under concern of Figure 2). The same reasoning applies to the following graphs from the EASA AFIS survey. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 57 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) Many of the responses received indicated that, when alternation is established, ATC is usually provided when and where the traffic flow is expected to be significant and in presence of scheduled traffic, normally during the working days (frequently Monday to Friday), or in certain cases on a seasonal basis. AFIS instead is often provided during weekends or during those periods of the day when the traffic is expected to be low. From some responses it results that attention is paid to minimise fragmentation of periods and frequent alternation between the two services, in order to establish clarity and certainty on the ATS type provided at the aerodrome at any time. Responses indicated that there are several States which have not established any limitation with regard to the type of operations and traffic which may operate at AFIS aerodromes (therefore supporting GAT IFR and/or VFR flights, commercial and non-commercial operations, military, etc.). In addition, traffic types do not seem to constitute a decisive factor or a limitation in making a decision to provide this type of ATS. Responses received indicate that the interest and the expectations for the work undertaken under RMT.0464 to better define AFIS provision is high. Various categories of stakeholders highlighted a significant number of issues for which harmonisation is expected via EU legislation, amongst which e.g.: — A clear definition of AFIS, with the basic elements of the service clearly established (provision of information and/or instructions, use of surveillance support, etc.); — The definition of criteria for determining when an aerodrome has to be provided with AFIS; — The definition of requirements for an (ad hoc) airspace designation and classification for the airspace surrounding the AFIS aerodrome; — The definition of the Meteorological Services requirements specific for AFIS; — The definition of communication requirements for AFIS, including recording and retention of records; and — The definition of operational procedures for mixed IFR/VFR operations, for multiple IFR operations, for the interface with ground movements (vehicles, persons, aircraft). Two respondents highlighted the fact that the introduction of a set of common AFIS requirements could increase pilots’ awareness and certainty of the fundamental characteristics of the types of services and procedures in place at any AFIS aerodrome throughout the EU. Some respondents invited the Agency to consider establishing EU rules only to the extent necessary to establish harmonisation concerning the fundamental elements of AFIS provision, and to leave the necessary flexibility to States and service providers to address the specific local aspects. 3.1.2.4. Issues to be addressed Issues with lack of harmonisation in EU legislation The EASA AFIS survey revealed that, in the absence of specific and explicit ICAO and/or EU requirements, AFIS is currently provided on the basis of national legislation which a significant number of EU Member States have developed over the years. Such legislation extrapolate ICAO provisions about FIS and complement them with requirements which satisfy local national requirements or arrangements on AFIS provision. This situation leads to a wide diversity of practices TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 58 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) in various aspects, (e.g. operational procedures, typology of service provided to air traffic, operating hours, airspace and aerodrome structure, training and qualification of AFIS officers, equipment, etc.). The survey revealed that some EU Member States are deviating from the non-binding, but still significant, guidance provided by ICAO Circular 211-AN/128 on key topics, such as allowing international commercial aviation operations at AFIS aerodrome or, in the case of 4 States, allowing AFIS operators to issue instructions to aircraft and vehicles on the ground. Figure 3: Criteria to determine the ATS type at aerodromes Figure 4: National AFIS regulation other than ICAO The situation described above shows that AFIS provision meets neither the principal objectives established in Article 2 of the Basic Regulation, such as to establish and maintain a high uniform level of civil aviation safety in Europe and to assist Member States in fulfilling their obligations under the Chicago Convention, by providing a basis for a common interpretation and uniform implementation of its provisions, nor the safety principles and objectives, in particular those established in the Essential Requirements in Chapter 2.(c) of Annex Vb. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 59 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) Issues with operational procedures The fragmented AFIS provision often shows inconsistencies and gaps across Member States that could play a very important role in e.g. interoperability and communication. For instance, the type of services provided to flights operating cross-border flights at AFIS aerodromes may differ, and sometimes significantly, on the basis of the implementation of the AFIS model established in the national acts. There is evidence from the EASA AFIS survey that in some cases such differences are significant, as for the responsibility for the selection of the runway in use (See Figure 5), or for the facilities for the aeronautical mobile service (See Figure 6) or of the actions that AFIS Officers are empowered to take (issuing information or instructions and clearances to aircraft on the manoeuvring area) when providing the service. These variations might reduce the pilots’ awareness, in particular for the type of ATS provided (ATC or AFIS), and potentially represent a serious risk to safety, in particular when the aerodrome supports international aviation operations, and in the absence of clear and explicit requirements on the notification of the appropriate aeronautical information concerning the AFIS provision (See Section 3.1.2.5 Safety risk assessment). Figure 5: Procedure for selection of runway at AFIS aerodromes Figure 6: Aeronautical mobile service facilities TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 60 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) Issues with EASA Standardisation inspections — Compliance with EU legislation In this regulatory context, AFIS is regarded as an area of concern also on the basis of the feedback received from EASA Standardisation inspections. In 5 EASA Member States, it was found that AFIS providers were neither certified nor declared as ATS providers, as it should be in accordance with the applicable EU legislation (the Basic Regulation, Regulation (EC) No 550/2004, and Regulation (EU) No 1035/2011); consequently, oversight was not conducted. Other findings against the aforementioned Regulations were issued, concerning the missed designation of AFIS providers to render services within a specified portion of airspace (the ATZ associated to the aerodrome), the lack of demonstration of English language proficiency of AFIS operators where AFIS was provided in that language, the authority given to AFIS units to issue instructions (typical for ATC provision) to aircraft on the ground. The latter situation described is neither compliant with the FIS principles and requirements established in Annex 11, nor with Article 3(1) of Regulation (EU) 2015/34018 stipulating that ATC service, which includes the issuance of clearances and instructions, shall only be provided by ATCOs qualified and licensed in accordance with the requirements of that Regulation. Feedback from EASA Standardisation inspections indicates that there is a lack of a more robust EU regulatory framework and/or guidance concerning the provision of AFIS. Issues with the appropriate selection of aerodromes ATS In consideration of the ANSPs’ concerns about the costs for the implementation of ATC provision, AFIS could be regarded as a less burdensome option for providing aerodrome ATS due to the reduced number of obligations and to the fewer resources and less effort required compared to an ATC service. An example is the significant difference in the requirements for qualification of staff (ATCO addressed in details by Regulation (EU) 2015/340 vs AFIS officers addressed only in principle by Regulation (EU) No 1035/2011, and consequently by local, often very diverse directives) providing such services. In the absence of a common regulatory framework, there is the risk that AFIS, not being harmonised at EU level, is defined and provided on the basis of local needs and practices, driven primarily by economic factors rather than by safety objectives. 3.1.2.5. Safety risk assessment For the purposes of this RIA, the Agency has analysed the available data19 of occurrences reported at 22 aerodromes within the EASA Member States where AFIS is provided, over the last 5 years. This sample of 22 aerodromes was selected based on the feedback received with the EASA AFIS Survey, with the aim of establishing a balanced representation of different AFIS operations and considering specific characteristics (e.g. traffic load, typology of flight operations, geographical scope); some of these aerodromes are with mixed ATC/AFIS operations. 18 Commission Regulation (EU) 2015/340 of 20 February 2015 laying down technical requirements and administrative procedures relating to air traffic controllers' licences and certificates pursuant to Regulation (EC) No 216/2008 of the European Parliament and of the Council, amending Commission Implementing Regulation (EU) No 923/2012 and repealing Commission Regulation (EU) No 805/2011 (OJ L 63, 6.3.2015, p. 1) (http://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1467201985014&uri=CELEX:32015R0340). 19 Data extracted from the European Central Repository (ECR). It is to be noted that pursuant to Article 8(2) of Regulation (EU) No 376/2014, since 15 November 2014 Member States are obliged to insert relevant data on occurrences into this repository. The list of accidents and serious incidents were completed with data from the EASA database, which resulted in two additional serious incidents added (‘Incident between an airliner and airport maintenance vehicle at Kuusamo airport on 29 January 2003’ (Ref. C 2/2003 L) and ‘Serious incident at Kittilä airport on 4 January 2005’ (Ref. B 1/2005 L)). TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 61 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) The analysis focused only on occurrences related to ATM/ANS-related aspects. A total of 234 occurrence reports were detected, subdivided as follows by their severity: 1 accident, 5 serious incidents, 22720 incidents or other occurrences. From the analysis, it resulted that: — the most frequent type of occurrence reported at those AFIS aerodromes were near collisions and runway incursions; — a significant amount of events related to aerodrome and/or ATM/ANS equipment failures were recorded in the occurrences analysed. In total 29.5 % of reports contained some kind of ground equipment failure, among which the communications equipment account for more than 10 % of the cases; — the provision of information to pilots was also pervasive in the reports, and together with the flight crew communications and flight crew following ATM procedures and clearances issued, these events occurred in 13,3 % of the reports. Events reported in accidents and serious incidents showed that ATM-flight crew coordination, flight crew’s knowledge of services provided and the related procedures were contributing factors in some of those events. In particular, it was found that the pilot did not follow AFIS procedures either due to lack of knowledge of the procedure (e.g. landing without “runway free” message from AFIS officer), or due to erroneous assumption from the pilot (e.g. assumed that he got a clearance); — even though the percentage of events related to AIS provision is limited in the sample, it was found that AFIS-related procedures did not reach the pilot, either because:  the pilot did not check the AIP or other relevant Aeronautical Information (e.g. NOTAMs concerning the AFIS aerodrome); and/or  the crew manuals did not appropriately reflect the AFIS procedures; and/or  the procedures were published in the national AIS only in the local language. — Communication issues were found also in the review of some serious incidents, where the lack of standard phraseology, inadequate communication with AFIS unit (e.g. not provided all required information such as RWY to land), or missed correction of incorrect read-back or lack of clarification of unclear communications upon request from the pilot, played a role. It is worth noting that among the aerodromes selected, the reporting culture into ECR plays a significant role. 5 out of 22 aerodromes did not report any occurrence, 9 aerodromes reported 19 occurrences, while 8 aerodromes reported 213. The safety risk analysis shows that there is no impelling safety driver to regulate AFIS; however, it shows that several occurrences are linked indirectly or directly to the current AFIS requirements, and it also indicates that harmonisation may have helped in some circumstances (e.g. setting up pilot expectations about the received service). As also recommended by the Finnish Investigation Commission in the conclusions of Investigation Report C 2/2003 L, a clear definition and harmonisation of AFIS throughout EASA Member States would be required to improve flight safety. 20 For those incidents and other occurrences, included in this figure, reported at aerodromes with mixed ATC/AFIS operations, the information in the ECR does not specify if the occurrence occurred when AFIS was provided. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 62 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) 3.1.2.6. Who is affected? — The Agency, as being responsible for the oversight of competent authorities; — Member States as they are responsible for the fulfilment of the obligations towards the Chicago Convention, for the application of the relevant EU legislation and, in this very case, for having established national legislation to address AFIS provision; — Competent authorities as they are responsible for the enforcement and oversight of the national and/or EU legislation concerning AFIS and of the regulated subjects; — Air navigation service providers as they have to establish all the arrangements to deliver AFIS in accordance with the applicable national and/or EU legislation. This includes the availability of system support, the definition of procedures, personnel qualification and training, etc.; — ATS personnel (AFIS officers as they have to be recruited, qualified and trained to operationally provide AFIS; ATCOs and FIS officers as they have to be trained to operationally interact with AFIS units); — Aircraft operators (commercial, freight, business, General Aviation, etc.) as they are responsible for the aircraft to which AFIS is provided. The service level and the related arrangements are relevant in order to elect if to operate at AFIS aerodromes; — Pilots as they are the direct beneficiary of AFIS for the safe and expeditious conduct of their flights; they interact with AFIS units; — Aerodrome operators as the decision of providing AFIS and the application of the related requirements affect the aerodrome configuration and development, at organisational and operational level; — Passengers (of commercial aviation operations at AFIS aerodromes) as they could benefit from a safer and more efficient service, as well as from the extension of the aviation system and therefore the mobility of the population; — Local communities as the definition of a common EU AFIS regulatory framework might have an impact on the extension of the aviation system and subsequently, by supporting the implementation of AFIS aerodromes, on the economy of the areas surrounding such aerodromes. 3.1.2.7. Problem tree The following problem tree helps visualising the identified problems, their underlying drivers and likely consequences. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 63 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 64 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) 3.1.2.8. How could the issue/problem evolve If the regulatory framework is not changed, the situation could evolve as follows: — In the absence of the definition of a clear and proportionate EU regulatory framework, and in the continuing absence of explicit ICAO provisions the provision of AFIS throughout the EU would not be harmonised. — Under the present conditions, the certification and oversight of AFIS would continue to differ across EASA Member States, based on sometimes differing national legislation. This is due to a lack of common understanding as to what constitutes AFIS. — In the absence of a defined safety regulatory framework which explicitly recognises AFIS as an ATS with its own peculiar characteristics and requirements, the decision as to whether to implement AFIS or ATC, and the related conditions, could be taken by the ATS provider and subsequently endorsed by the competent authority based primarily upon economic rather than upon safety aspects. This is a concern as from the provider’s perspective, ATC implementation is a more burdensome and potentially more expensive proposition compared to AFIS. — Issues related to the lack of harmonisation in operational procedures would remain or, in case of an increase of traffic at AFIS aerodromes, could become more frequent, in particular in case of international flights to AFIS aerodromes, as pilots could not be aware of the specificities of a local AFIS provision (e.g. runway in use; air–ground communication, responsibilities for maintaining separation on the ground). On the basis of the safety risk assessment in Section 3.1.2.5, the identified safety issues linked to AFIS would persist and potentially lead to the detriment of flight safety operations. 3.1.2.9. AFIS in third countries According to the information gathered, AFIS or similar types of services, which may widely vary, are implemented in over 70 countries in the 5 continents around the world. Some examples: — Some States have well-defined airspace ATZ, TIZ or even CTR. Some have no airspace designated for AFIS aerodromes. The airspace size varies from about 5 NM in diameter and 1 500 ft high to 60 NM miles in radius and up to 10 000 ft high; — Airspace classification used ranges from G and F to E and even D; — The call signs for AFIS aerodromes used are, variously, ‘RADIO’, ‘INFORMATION’ or ‘AFIS’; — Some (like the US, Canada and Japan) do not even call it AFIS but use other names e.g. Flight Service Stations (FSS); — The traffic served ranges from only unscheduled private VFR to all types of traffic including international scheduled IFR passenger traffic and even military traffic; — Service varies from only providing meteorological information to providing meteorological information, traffic information, navigational assistance and suggestions and advice (briefly described); TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 65 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) — Some have minimum equipment, grass or gravel runways, no approach or navigational aids, no lights and only HF radio. And some have ILS and other precision approach instruments, hard surface runways and radar/surveillance equipment for provision of AFIS with radar; — Training of AFIS officers can vary in length from 2 weeks to 3 years. Some include simulator and some others only theory; — Some States have established a licensing scheme for their AFIS officers with ratings and well- published training schemes. Some have some type of certificate of competence and some have nothing at all. Recently, some States, such as the United States and Canada, have been consolidating flight services into large regional centres, replacing former local flight service stations with remote communications outlets (RCOs) connected to the centres. Hereinafter, three descriptive examples of how aerodrome FIS are established in non-EASA States. Indonesia Indonesia has 100 AFIS aerodromes serviced by 418 licensed AFIS officers. AFIS aerodromes have no designated airspace but work in surrounding airspace that is now classified F. Indonesia is working towards creating ATZ with G airspace as a consequence of getting findings in ICAO audits. The call sign for the AFIS stations is ‘Information’. Indonesia is currently modernising its AFIS service, which today is conducted at minimum equipped airfields with only HF radio and very little regulation. It is planned to introduce the Eurocontrol AFIS manual as national subject matter regulation. United States The USA has 5 AFIS aerodromes. In the USA, the unit providing such service is named FSS — flight service station. An FSS is an air traffic facility that provides information and services to aircraft pilots before, during, and after flights, but unlike ATC, is not responsible for giving instructions or clearances or providing separation. They do, however, relay clearances from ATC for departure or approaches. The people who communicate with pilots from an FSS are referred to as flight service specialists. The services offered by typical FSS services may include: — providing preflight briefings including weather and notices to airmen (NOTAMs); — filing, opening and closing flight plans; — monitoring navigational aids (NAVAIDs); — collecting and disseminating pilot reports (PIREPs) and airport surface weather observations; — offering traffic advisories to aircraft on the ground or in flight; — relaying instructions or clearances from air traffic control; — relaying information from or about airborne aircraft to their home bases, military bases or homeland security; — providing weather advisories to aircraft inflight; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 66 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) — initiating search and rescue on missing VFR aircraft; and — providing assistance in an emergency. Flight service stations also operate at mandatory frequency airports to help coordinate traffic in the absence of ATCOs, and may take over a control tower frequency at a controlled airport when the tower is closed. In most cases, it is possible to reach FSS either by radio in flight, or by telephone on the ground. The US also provides something called RAA (Remote Airport Advisory) and RAIS (Remote Airport Information Service). Both provide weather services and cannot be compared with what in Europe is intended to be defined as AFIS. Canada Canada has established units named flight service stations (FSS) to provide: — aerodrome advisory services (AAS); — vehicle control services; — ATC support; — local weather and aeronautical information; — surface weather observation; — equipment monitoring; and — emergency services A typical example of an FSS is a station in Class E airspace surrounded by uncontrolled airspace with a mix of commercial and General Aviation traffic. The FSS often has a control zone associated. Radar/MLAT is utilised at these stations, where available. 3.2. Objectives General objective The overall objective of the EASA system is to establish and maintain a high uniform level of civil aviation safety in Europe (Article 2(1) of the Basic Regulation); this proposal will contribute to this overall objective by addressing the issues outlined in Section 3.1. Specific objectives In the light of the mandate of the EU legislator concerning ATS, there is a need to define explicit and fundamental requirements for AFIS in the EU context, by setting an efficient, effective and proportionate framework consistent with the FIS principles established by ICAO and by the existing EU legislation (e.g. SERA). More specifically, the objectives are to: — establish clarity as regards the rules applicable to AFIS; — ensure a sufficient level of harmonisation for AFIS provision throughout the EASA Member States; TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 67 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) — ensure consistency between the proposed AFIS requirements and the existing applicable ICAO provisions and EU legislation; — establish a proportionate and cost-efficient framework, applicable to different aerodromes with different types of operating traffic; and — maintain high aviation safety level by ensuring adequate implementation of AFIS provisions linked to safety and tackling the issues identified by standardisation inspections. 3.3. Policy options Table 1 — Options considered Option Short title Description No 0 No policy change Baseline scenario (no change in EU rules; risks remain as outlined in the issue analysis). 1 Essential and flexible Definition of AFIS and its essential requirements consistent AFIS rules with existing ICAO ATS principles and EU legislation and practices, while ensuring certain flexibility 2 Comprehensive and Definition of AFIS and its complete mandatory requirements prescriptive AFIS rules consistent with existing ICAO ATS principles and EU legislation Note: It is important to notice that the regulatory proposal in this NPA neither includes detailed and ad hoc requirements on the recruitment, qualification and training of AFIS officers, as they are not within the scope of RMT.0464, nor establishes a specific air–ground phraseology for the provision of AFIS, which should be further considered by SERA regulatory activities. It is recalled that for the recruitment, qualification and training of AFIS officers, the general provisions in the ATM/ANS Common Requirements apply. OPTION 0 — NO POLICY CHANGE — BASELINE SCENARIO No specific requirement for the provision of AFIS would be proposed, therefore a common description of and regulatory framework for AFIS in the EU context would not established. AFIS would keep being provided on the basis of the general ICAO FIS principles, which are not intended to fit in the aerodrome context. In general, AFIS would be provided in accordance with national legislations which are not harmonised at EU level with regard to various conceptual, organisational and operational aspects. OPTION 1 — DEFINITION OF AFIS AND ITS ESSENTIAL REQUIREMENTS CONSISTENT WITH EXISTING ICAO ATS PRINCIPLES AND EU LEGISLATION AND PRACTICES, WHILE ENSURING CERTAIN FLEXIBILITY A definition of AFIS would be proposed, together with the basic organisation and technical requirements to specifically address the provision of FIS at the aerodrome and in the airspace in its vicinity. Such requirements would be consistent and establish an explicit alignment with the existing ICAO provisions on FIS, as well as compliance with the EU legislation in force or under development (e.g. SES Framework, ATM/ANS Common Requirements, SERA). The regulatory proposal would take also into account the results of the EASA AFIS survey, with the aim of harmonising only the TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 68 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) fundamental elements of the service, while ensuring the necessary flexibility to reflect the various typologies of AFIS operations in place throughout the EASA Member States. Furthermore, GM would be proposed, representing the possibility to establish aeronautical stations (UNICOM) not providing ATS but facilitating aviation operations at aerodromes where no ATS is established. The proposal aims at establishing clarity on the options available when selecting the most appropriate arrangement (ATC, FIS, AFIS or aeronautical stations not providing ATS). OPTION 2 — DEFINITION OF AFIS AND ITS COMPLETE MANDATORY REQUIREMENTS A definition of AFIS would be proposed, together with a comprehensive set of prescriptive organisation and technical requirements to specifically address the provision of FIS at the aerodrome and in the airspace in its vicinity. Such requirements, consistent with the existing ICAO provisions on FIS, as well as on the EU legislation in force or under development (e.g. SES Framework, ATM/ANS Common Requirements, SERA), would be as prescriptive as possible, in order to establish a unique EU ‘AFIS model’. Such model would be implemented at any aerodrome where the Member State has decided that ATS, but not ATC, is to be provided, regardless of the local characteristics (e.g. typology and traffic demand, aerodrome layout, operational hours). 3.4. Analysis of impacts 3.4.1. Safety impacts Option 0 The potential to generate safety risks as identified in Section 3.1.2.5 (Safety risk assessment) would remain or even increase, with a possible growth of AFIS flights. Option 1 The harmonisation of AFIS requirements would contribute to the improvement of flight safety, in particular with regard to the explicit definition and description of various organisational and operational aspects of the service (issuance of appropriate information, air-to-ground communication procedures, aeronautical mobile service requirements, inclusion and appropriate use by pilots of AFIS related information in AIS) which nowadays are not uniform and therefore represent a safety concern, in particular for cross-border flights. Option 2 The safety impact would be similar to that of Option 1. However, with an even more defined and prescriptive set of requirements, room for local interpretations and implementation of specific organisational and operational aspects linked to safety would not be allowed. Table 2 — Safety impacts per option Criteria Option 0 — Option 1 —Essential Option 2 — Comprehensive and Take no action and flexible AFIS rules prescriptive AFIS rules Safety 0/- + + TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 69 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) 3.4.2. Environmental impacts Not relevant. 3.4.3. Social impacts When assessing the social impact of the three given options, it is to be considered that this regulatory proposal does not include detailed provisions on the recruitment, qualification and training of AFIS personnel, as these fields are not within the scope of RMT.0464. However, the ATM/ANS Common Requirements Regulation includes a generic obligation for providers to recruit, qualify and train personnel employed in the provision of the services, which include also AFIS. Option 0 No impacts are expected. The situation would remain as is today. Option 1 The introduction of explicit AFIS requirements might support the harmonised definition of criteria for the selection and recruitment of AFIS personnel, as well as the establishment of consistent qualification and training paths. The flexibility offered by the proposed provisions would allow the AFIS providers to tailor the qualification and training paths to the specific local needs. More in general, the definition of a regulatory framework would contribute to raising the recognition at EU level of AFIS personnel as ATS professionals. Option 2 The introduction of explicit AFIS requirements might support the better definition of criteria for the selection and recruitment of AFIS personnel, as well as the establishment of consistent qualification and training paths. The rigidity of the proposed ‘EU AFIS model’ would support the development of similar schemes and, consequently, theoretically support the mobility of AFIS officers. As for Option 1, the definition of a regulatory framework would contribute to raising the recognition at EU level of AFIS personnel as ATS professionals. On the other hand, the burden on providers to comply with the prescriptive regulatory framework could lead to the termination of the provision of AFIS at certain aerodromes, with possible reduction of air traffic and of the associated jobs. Table 3 — Social impacts per option Criteria Option 0 — Option 1 —Essential Option 2 — Comprehensive and Take no action and flexible AFIS rules prescriptive AFIS rules Social 0 + 0/+ 3.4.4. Economic impacts Option 0 No major impacts are expected. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 70 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) Option 1 Competent authorities The introduction of a common set of EU AFIS requirements would imply initial costs for the competent authorities which will have to make available appropriate resources and manage the administrative burden of certification and oversight of AFIS providers in accordance with a new regulatory framework; such expected burden would be reduced if the national legislation on AFIS is already aligned with the ICAO principles which drive the proposed rules and if the certification and oversight of such service is already routinely conducted, in accordance with the applicable EU legislation. AFIS providers Assessing the economic impacts of this option on AFIS providers is challenging, in particular in consideration of the existing differences in specific characteristics such as the typology and numbers of traffic demand, the type of aircraft operations, the aerodrome layout. Another factor which would make the assessment variable is the existing national legislation and arrangements for AFIS. The larger the alignment of the existing national legislation with the regulatory proposal, which includes flexible arrangements, the less significant the economic impact for the AFIS provider to establish compliance with the proposal. Moreover, a change from the national legislation could imply costs for the revision of operation manuals and training courses and material for AFIS officers. In general, a variable economic impact would be expected in particular as regards establishing compliance with the proposed ATS organisation requirements (e.g. fixed and mobile communication service, meteorological requirements). However, it is recalled that in accordance with Regulation (EU) No 1035/2011, AFIS providers are already required to be certified (or to apply for derogations in accordance with established provisions) and to provide AFIS in accordance with applicable ICAO working methods and procedures, which are at the basis of this regulatory proposal. Based on the EASA AFIS survey, there is evidence of an existing significant level of compliance with those ICAO provisions throughout EASA Member States; therefore the overall economic impact should be limited for AFIS providers. Aircraft operators It is unlikely that aircraft operators would suffer a negative economic impact by the requirements in the proposal, in particular as regards the increase of air navigation charges which should not be modified as a result of the introduction of this regulatory proposal, unless the current AFIS provision differs significantly from the ICAO FIS and from the EU legislation applicable; in this case, the necessary investments to ensure compliance might lead to an increase of the air navigation charges. The establishment of a flexible regulatory framework, applicable at multiple typologies of aerodromes, could encourage the further expansion of AFIS provisions throughout the EASA Member States, as also evidenced by the feedback received via the EASA AFIS survey. This could create the conditions for the economic development of the regions concerned, which would benefit from the existence of an operating logistic infrastructure, with the potential to favour the economic development of surrounding communities and with the related generation of new jobs. It may have a positive economic impact in those EASA Member States where no AFIS is provided, by giving the opportunity to replace ATC with AFIS where so considered advantageous (e.g. at aerodromes with limited traffic demand and low complexity) and acceptable from a safety perspective. This would lower the costs for the service provision and could, as an effect, lower also air navigation charges for TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 71 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) aircraft operators (commercial, freight, business, General Aviation, etc.), with possible economic benefits for passengers. Option 2 The economic impact for the competent authorities would be the same as that of Option 1. Compared to Option 1, as regards AFIS providers, in presence of a comprehensive and prescriptive regulatory framework, the economic impact could be more negative as much as the current national AFIS regulation deviates from the current ICAO AFIS provisions. Establishing compliance with this regulatory package could represent a relevant burden for some AFIS providers, which could therefore decide to terminate the provision of such service. The economic impact for aircraft operators could be worse than that of Option 1, due to the possible increase in the air navigation charges which could result from the necessary investments the AFIS provider would need to make to establish compliance with the full set of rules (e.g. aeronautical fixed/mobile service, certified meteorological information). The economic impact of the establishment of a comprehensive and prescriptive AFIS regulatory framework could be twofold: on the one hand it would establish clarity on the applicable requirements and as a result encourage the further expansion of AFIS provisions, with the inherent benefits for the aviation system and, therefore, for the economy; on the other hand, in presence of AFIS providers which would terminate the service provision due to the excessive burden introduced by the proposal, the effects on the local economies would be detrimental (limitation/closure of AFIS aerodrome operations, negative impact on companies supporting the aerodrome, consequent loss of jobs). More negative economic impacts are expected, compared to Option 1. Table 4: Economic impacts per option Criteria Option 0 — Option 1 —Essential Option 2 — Comprehensive and Take no action and flexible AFIS rules prescriptive AFIS rules Economic 0 -/+ - 3.4.5. General Aviation and proportionality issues Option 0 The provision of AFIS is based on national legislation, which is focused on the local characteristics, operational needs and capabilities of aerodromes concerned. General Aviation would keep operating as with the current national regulatory framework; for local operations, it would have no impact, while for non-resident pilots, in particular in case of cross-border flights, the lack of harmonisation in operational procedures and information dissemination at the various AFIS aerodromes could represent an operational issue (in addition to the safety issues outlined in Section 3.1.2.5). Option 1 In presence of the various organisational and operational factors affecting the establishment of AFIS provisions (different aerodromes layouts, different typology of aircraft operations VFR/IFR, national TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 72 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) international flights, commercial, non-commercial, military, General Aviation, gliders, balloons, etc.), the inherent flexibility of the proposal would support the principle of proportionality. The proposal would neither pose any limitation for the General Aviation operations, nor restrict access to aerodromes or to ATS. The rationale provided under the ‘Economic impact’ of Option 1 concerning aircraft operators is applicable to General Aviation as well, being a category which makes extensive use of AFIS aerodromes. In case of an increase of the air navigation charges due to the necessary investments to meet the proposed AFIS requirements, the impact on General Aviation would be proportionally higher than that on CAT, as the economic onus is on the pilots who would not get any revenue from the flight. On the contrary, the harmonisation introduced by the establishment of essential common rules would facilitate the understanding of the General Aviation community of what AFIS principles and procedures are to be expected at any of such aerodromes. Additionally, the introduction in GM of the UNICOM concept would support the existence of aerodromes where no ATS is established, but where the Member State could allow a degree of facilitation for local operations, which are expected to be mainly General Aviation operations. Option 2 The comprehensive and prescriptive nature of the requirements would have a negative impact on the principle of proportionality as all providers would be required to comply with the complete framework, regardless of the characteristics and typology of operations at the aerodromes concerned. As with Option 1, General Aviation would benefit from the even greater harmonisation of AFIS provision. However, as discussed under the ‘Economic impact’, the implementation of this Option could represent a ‘showstopper’ for those providers which could not afford or not consider cost- effective the provision of AFIS at certain aerodromes. This would have a negative impact on the General Aviation operations because it could lead to the lack of ATS at such aerodromes. In addition, the possible increase of air navigation charges to comply with the requirements, which based on the scope and the binding nature of the proposal would be expected to be higher and more likely than with Option 1, would generate a detrimental economic impact on General Aviation. Table 5: General Aviation and proportionality impacts per option Criteria Option 0 — Option 1 —Essential Option 2 — Comprehensive and Take no action and flexible AFIS rules prescriptive AFIS rules General aviation and 0 + - proportionality 3.4.6. ‘Better regulation’ and harmonisation impacts Option 0 With the current situation and in the absence of a common EU framework explicitly recognising and addressing the provision of AFIS, such service would keep being provided on the basis of the national interpretation of ICAO principles on FIS, which in many cases resulted in lack of harmonisation in various aspects throughout the EASA Member States. With the introduction of this regulatory proposal for PART-ATS, transposing the relevant provisions of ICAO Annex 10 Volume II, Annex 11 and PANS ATM into the EU regulatory framework but without an explicit reference to AFIS, there is the risk that the existing national legislation on AFIS is not aligned with the EU ATS principles. Moreover, the lack of TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 73 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) an explicit common EU regulatory framework would prevent establishing clarity with regard to the certification and the oversight of AFIS providers on the basis of the applicable EU legislation. Option 1 Bearing in mind the lack of ICAO SARPs with regard to AFIS, the proposal would define at least a set of high-level AFIS requirements, established within the scope of the FIS. It would accomplish the regulatory mandate of the Basic Regulation to establish a common regulatory framework for ATS in accordance with the relevant Essential Requirements in Annex Vb 2(c). All affected stakeholders (in particular competent authorities, ATS providers, and aircraft operators) would benefit from the harmonisation of AFIS for which different interpretations have been given so far. Said differentiation leads to implementation sometimes partially divergent from the ICAO FIS principles which instead are fully followed by the proposal. The harmonisation introduced with these common rules would facilitate the understanding of what AFIS principles and procedures are to be expected at any of such aerodromes (e.g. determination of the runway in use; air–ground communication). The proposal would establish the essential elements of the common EU regulatory framework for the provision of AFIS, and at the same time grant certain flexibility to accommodate local characteristics and needs. It would be coherent with the other ATS requirements resulting from the transposition of the ATS-relevant ICAO material, and in particular with the principles of the FIS provision. Member States and other affected stakeholders would benefit from the clarity on the options available to select the type of ATS at aerodromes, including the explicit recognition of the possibility to establish arrangements facilitating aviation operations without providing ATS (UNICOM aeronautical stations). The Agency and the national competent authorities would benefit from the definition of a coherent set of provisions for activities concerning the standardisation, certification and oversight of AFIS under the EU regulatory framework. AFIS providers would benefit from the definition of a defined set of rules to implement and deliver this service, which at the same time stipulates the essential mandatory elements and allows for the flexibility to accommodate specific local needs. Pilots will benefit from a unique definition of the fundamental characteristics of AFIS, which would enable a common awareness of the services provided and support the harmonisation of operational procedures at EU AFIS aerodromes. On the basis of the information gathered via the EASA AFIS survey, the proposed measures should not prove too burdensome for the affected stakeholders in the majority of the EASA Member States. They would be required to assess if their national legislation on AFIS is aligned with the EU AFIS requirements (built upon the ICAO principles already applicable) and to undertake appropriate action, as necessary. This could include the initiative to modify the national arrangements for AFIS provision when they would not be compliant with the general requirements in the proposal, and to request the competent authority (-ies) and the affected AFIS providers to act accordingly. EASA Member States where, for the time being, AFIS is not provided may seize the occasion of the additional clarity and consistency brought by the requirements included in the proposal and consider opting for the implementation of AFIS instead of ATC at specific aerodromes, where they have determined that ATS is to be provided incurring less operational costs. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 74 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) Option 2 As with Option 1, the proposal would define AFIS and formally and explicitly recognise it as a subset of FIS, as well as accomplish the regulatory mandate of the EASA Basic Regulation to establish a common regulatory framework for ATS in accordance with the relevant Essential Requirements in Annex Vb. In this respect, the impact on all affected stakeholders (in particular competent authorities, ATS providers, Aircraft operators) would be similar. The comprehensive scope of the provisions and their prescriptive nature would establish a well- defined regulatory framework for the provision of AFIS, coherent with the relevant EU regulations and ICAO ATS principles; this would definitely contribute to its harmonisation and represent a detailed guidance for Members States, competent authorities and service providers in the activities of designation, certification, oversight, standardisation and provision of such service. As with Option 1, pilots will benefit from an established clarity on AFIS. The prescriptive nature of the proposal could create difficulties in accommodating specific local characteristics and needs. Such lack of flexibility could result in the imposition of a significant administrative and economic burden to AFIS providers, in particular at small aerodromes or at aerodromes with reduced/local traffic, to meet all the proposed requirements. A consequence of this could be that AFIS is no longer provided at those aerodromes. As with Option 1, EASA Member States would be required to assess if their national legislation on AFIS is aligned with the EU AFIS regulatory framework and to undertake appropriate action, as necessary. In consideration of the comprehensive and prescriptive nature of the provisions, it could be possible that the impact on the existing national regulatory systems would be significant, and that would require Member States to introduce significant changes to the existing AFIS arrangements and legislation, when these would not be compliant with the general requirements in the proposal. The transitional costs to achieve this level of harmonisation could be non-commensurate with the potential benefits; in this case, the principles of ‘better regulation’ would not be respected. Table 6 — ‘Better regulation’ and harmonisation impacts per option Criteria Option 0 — Option 1 —Essential Option 2 — Comprehensive and Take no action and flexible AFIS rules prescriptive AFIS rules ‘Better regulation’ - ++ 0/+ and harmonisation 3.4.7. Open questions to stakeholders In order to enable an even more detailed assessment of the impacts of the options described in this RIA, the Agency invites the stakeholders to respond to the following questions: Questions for AFIS providers: (a) Would the compliance with the proposed AFIS provisions introduce additional costs and/or burden (e.g. revision of AFIS training courses/material; extra resources in FTEs)? (b) If the answer to the previous question is affirmative, could you detail the sources of costs and quantify them? TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 75 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) Questions for all stakeholders: (a) Do you believe that the harmonised implementation of AFIS provision will bring safety benefits (e.g. pilot situational awareness)? (b) If the answer to the previous question is affirmative, please specify. (c) Do you expect an increase in the use of AFIS in the future? (d) If the answer to the previous question is affirmative, please specify on which assumptions you base your judgement. In addition to the above questions, stakeholders are kindly invited to provide any other quantitative information they may find necessary to bring to the attention of the Agency with regard to this RIA. As a result, the relevant parts of the RIA might be adjusted on a case-by-case basis. 3.5. Comparison and conclusion Comparison of options Table 7 — Final scores of the qualitative impact Option 0 Option 1 Option 2 No policy change Essential and flexible Comprehensive and AFIS rules prescriptive AFIS rules Safety -/0 + + Social 0 + 0/+ Economic 0 -/+ - GA & Proportionality 0 + - Better Regulation & - ++ 0/+ Harmonisation TOTAL -/0 + 0 As a result of the analysis of the impacts as in Section 3.4, Option 1 is preferred over the other two options. Option 0 could not be selected as the actual regulatory framework requires the establishment of clear and explicit EU regulatory framework on AFIS. In particular, the impact on safety and better regulation and harmonisation resulted negative. Option 2 could not be selected as its prescriptive nature would imply a significant impact and burden for many stakeholders without fully meeting the principles of ‘better regulation’. In addition, said option would not allow the necessary proportionality. On the other hand, it would introduce benefits in terms of harmonisation in AFIS provision. The proposal with Option 1 establishes clarity on the AFIS provision by setting a comprehensive and explicit set of requirements, which is based on relevant ICAO principles and on the EU legislation TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 76 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) applicable to ATS. Therefore, it meets the safety objectives set in Article 2 of the Basic Regulation, in particular to establish a high uniform level of aviation safety in the EU, and to assist Member States in fulfilling their obligations under the Chicago Convention by providing a basis for a common interpretation and uniform implementation of its provisions. Additionally, the proposal implements the Essential Requirements in Annex Vb Chapter 2.(c) as far as AFIS is concerned. The harmonisation of AFIS would bring safety benefits for aircraft operators and pilots as it will establish uniform operational principles throughout EU, reducing thus the possibility for misinterpretation of the operational characteristics of the service provided. The proposal supports the principle of proportionality, as it is established by the balanced set of rules (IRs, AMC, GM), which are flexible to the extent possible within the ATS context to accommodate local needs, and which are built upon feedback received for actual AFIS practices showing a limited impact on existing AFIS provision. By clarifying AFIS fundamental characteristics, and by recognising the possibility for non-ATS units indicated by Member States to facilitate local aviation operations, the proposal establishes clarity and supports the selection of the appropriate service or facilitation for aviation operations at aerodromes, without generating limitations when no ATS (ATC or AFIS) is considered suitable or convenient. All these factors make the proposal proportionate for the affected stakeholders. The economic impact on competent authorities and AFIS providers could be significant, and for a transitional period, only in presence of an existing non-compliance with the existing and applicable EU regulations and if the flexibility provisions are not well implemented. Aircraft operators could only be economically impacted in case of a raise in the air navigation charges resulting from investments by the AFIS providers to meet the new requirements. Therefore, Option 1 is the preferred option. 3.6. Monitoring and ex post evaluation Monitoring is a continuous and systematic process of data collection and analysis about the implementation/application of a rule/activity. It generates factual information for future possible evaluations and impact assessments and helps identifying actual implementation problems. With respect to this proposal, the Agency would suggest to monitor: — The quantitative and harmonised implementation of AFIS throughout EASA Member States, more specifically:  if the regulatory proposal had a negative impact on the AFIS provision (decrease or increase of AFIS provision);  benchmark the harmonisation in the operational provision of AFIS. — The amount of safety occurrences at AFIS aerodromes and associated airspaces in order to verify if the regulatory proposal would have introduced an enhancement in the safety of aviation operations. The monitoring could take the form of collecting and analysing data from different available sources via several tools e.g. standardisation inspections, analysis of the application for flexibility provisions as in Article 14 of the Basic Regulation as well as of alternative means of compliance approved, analysis of TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 77 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 3. Regulatory impact assessment (RIA) occurrence reports in the AFIS context, queries received by the Agency and the Commission about the interpretation of the AFIS provisions. TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 78 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 4. References 4. References 4.1. Affected regulations — Commission Implementing Regulation (EU) 2016/1377 of 4 August 2016 laying down common requirements for service providers and the oversight in air traffic management/air navigation services and other air traffic management network functions, repealing Regulation (EC) No 482/2008, Implementing Regulations (EU) No 1034/2011 and (EU) No 1035/2011 and amending Regulation (EU) No 677/2011 (OJ L 226, 19.8.2016, p. 1) — Commission Implementing Regulation (EU) No 923/2012 of 26 September 2012 laying down the common rules of the air and operational provisions regarding services and procedures in air navigation and amending Implementing Regulation (EU) No 1035/2011 and Regulations (EC) No 1265/2007, (EC) No 1794/2006, (EC) No 730/2006, (EC) No 1033/2006 and (EU) No 255/2010 (OJ L 281, 13.10.2012, p. 1) — Commission Implementing Regulation (EU) 2016/1185 of 20 July 2016 amending Implementing Regulation (EU) No 923/2012 as regards the update and completion of the common rules of the air and operational provisions regarding services and procedures in air navigation (SERA Part C) and repealing Regulation (EC) No 730/2006 (OJ L 196, 21.7.2016, p. 3) 4.2. Affected AMC and GM Decision 2013/013/R of the Executive Director of the European Aviation Safety Agency of 17 July 2013 adopting the Acceptable Means of Compliance and Guidance Material to Commission Implementing Regulation (EU) No 923/2012 of 26 September 2012 laying down the common rules of the air and operational provisions regarding services and procedures in air navigation and amending Implementing Regulation (EU) No 1035/2011 and Regulations (EC) No 1265/2007, (EC) No 1794/2006, (EC) No 730/2006, (EC) No 1033/2006 and (EU) No 255/20101 ‘Acceptable Means of Compliance and Guidance Material to the rules of the air’ 4.3. Reference documents — Regulation (EC) No 216/2008 of the European Parliament and of the Council of 20 February 2008 on common rules in the field of civil aviation and establishing a European Aviation Safety Agency, and repealing Council Directive 91/670/EEC, Regulation (EC) No 1592/2002 and Directive 2004/36/EC (OJ L 79, 19.3.2008, p. 1) — Regulation (EC) No 550/2004 of the European Parliament and of the Council of 10 March 2004 on the provision of air navigation services in the single European sky (the service provision Regulation) (OJ L 96, 31.3.2004, p. 10) — Regulation (EC) No 551/2004 of the European Parliament and of the Council of 10 March 2004 on the organisation and use of the airspace in the single European sky (the airspace Regulation) (OJ L 96, 31.3.2004, p. 20) — Regulation (EU) No 376/2014 of the European Parliament and of the Council of 3 April 2014 on the reporting, analysis and follow-up of occurrences in civil aviation, amending Regulation (EU) No 996/2010 of the European Parliament and of the Council and repealing Directive 2003/42/EC TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 79 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 4. References of the European Parliament and of the Council and Commission Regulations (EC) No 1321/2007 and (EC) No 1330/2007 (OJ L 122, 24.4.2014, p. 18) — Commission Regulation (EU) 2015/340 of 20 February 2015 laying down technical requirements and administrative procedures relating to air traffic controllers' licences and certificates pursuant to Regulation (EC) No 216/2008 of the European Parliament and of the Council, amending Commission Implementing Regulation (EU) No 923/2012 and repealing Commission Regulation (EU) No 805/2011 (OJ L 63, 6.3.2015, p. 1) — Commission Regulation (EC) No 2150/2005 of 23 December 2005 laying down common rules for the flexible use of airspace (OJ L 342, 24.12.2005, p. 20) — Commission Implementing Regulation (EU) No 1206/2011 of 22 November 2011 laying down requirements on aircraft identification for surveillance for the single European sky (OJ L 305, 23.11.2011, p. 23) — Commission Regulation (EC) No 2096/2005 of 20 December 2005 laying down common requirements for the provision of air navigation services (OJ L 335, 21.12.2005, p. 13) — Commission Implementing Regulation (EU) No 1035/2011 of 17 October 2011 laying down common requirements for the provision of air navigation services and amending Regulations (EC) No 482/2008 and (EU) No 691/2010 (OJ L 271, 18.10.2011, p. 23) — Commission Regulation (EU) No 139/2014 of 12 February 2014 laying down requirements and administrative procedures related to aerodromes pursuant to Regulation (EC) No 216/2008 of the European Parliament and of the Council (OJ L 44, 14.2.2014, p. 1) — ED Decision 2015/014/R of 3 July 2015 ‘Guidance Material on the implementation of the remote tower concept for single mode of operation’ — ED Decision 2014/013/R of 27 February 2014 adopting Certification Specifications and Guidance Material for Aerodromes Design ‘CS-ADR-DSN — Initial issue’ — EASA Opinion No 02/2014 ‘Requirements for apron management services at aerodromes’ — EASA NPA 2016-02 ‘Technical requirements and operational procedures for aeronautical information services and aeronautical information management’ — EASA Safety Information Bulletin (SIB) 2014-07R1: Unexpected Autopilot Behaviour on Instrument Landing System (ILS) Approach — ICAO Doc 7300 ‘Convention of International Civil Aviation’ — ICAO Annex 2 ‘Rules of the Air’ — ICAO Annex 3 ‘Meteorological Service for International Air Navigation’ — ICAO Annex 10 ‘Aeronautical Telecommunications’ (Volume II ‘Communication Procedures’ including those with PANS status) — ICAO Annex 10 ‘Aeronautical Telecommunications’ (Volume V ‘Aeronautical Radio Frequency Spectrum Utilization’) — ICAO Annex 11 ‘Air Traffic Services’ — ICAO Doc. 4444 ‘Procedures for Air Navigation Services — Air Traffic Management’ (PANS ATM) TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 80 of 81 An agency of the European Union European Aviation Safety Agency NPA 2016-09(A) 4. References — ICAO Doc 8168 ‘Procedures for Air Navigation Services — Aircraft Operations’(PANS OPS) (Volume II) — ICAO Doc 9377 ‘Manual on Coordination between Air Traffic Services, Aeronautical Information Services and Aeronautical Meteorological Services’ — ICAO Doc 9426 ‘Air Traffic Services Planning Manual’ — ICAO Doc 7030 EUR ‘European (EUR) Regional Supplementary Procedures’ — ICAO Doc 9554 ‘Manual Concerning Safety Measures Relating to Military Activities Potentially Hazardous to Civil Aircraft Operations’ — ICAO Doc 9643 ‘Manual on Simultaneous Operations on Parallel or Near-Parallel Instrument Runways (SOIR)’ — ICAO Doc 9694 ‘Manual of Air Traffic Services Data Link Applications’ — ICAO Circular 211-AN/128 ‘Aerodrome Flight Information Service (AFIS)’ — ICAO TEC/OPS/SEP — 08-0294.SLG ‘Wake turbulence aspects of Airbus A380-800 aircraft’ — ICAO Working Paper AN-WP/9014 dated 18 February 2016 — ICAO EANPG/54 — WP/15 of 16.11.12 — ICAO EANPG/54 — Flimsy 08 of 04.12.12 — ICAO EANPG/56 — WP 18 of 12.11.14 — ICAO EANPG/56 — Final Report — ICAO EANPG/57 — Final Report — EUROCONTROL ‘Manual for Aerodrome Flight Information Service (AFIS)’ Edition 1.0 of 17.06.2010 — EUROCONTROL ‘Guidelines for Contingency Planning of Air Navigation Services (including Service Continuity)’ Edition 2.0 of 06.04.2009 — ‘Reference Guide to EUROCONTROL Guidelines for Contingency Planning of Air Navigation Services (including Service Continuity)’ Edition 2.0 of 06.04.2009 — EUROCONTROL ‘Common Format Letter of Agreement Between Air Traffic Services Units’ Edition 4.0 of 15.03.2012 — EUROCONTROL ‘Guidelines for the Application of European Coordination and Transfer Procedures’ Edition 1.0 of 25.10.2012 — Investigation Report C 2/2003 L ‘Incident between an airliner and airport maintenance vehicle at Kuusamo airport on 29 January 2003’ Issued by the Finnish Investigation Commission — Translation of the original Finnish report — Investigation Report AX001-1-2/02 published by the German Federal Bureau of Aircraft Accidents Investigation (BFU) in May 2004 regarding the mid-air collision between a Boeing 757- 200 and a Tupolev TU154M on 1 July 2002 near Überlingen, Germany — UK CAP 493 ‘Manual of Air Traffic Services’ — Study on Aeroplane State Awareness during Go-Around (ASAGA) – Published in August 2013 by Bureau d'Enquêtes et d'Analyses (BEA) pour la Sécurité de l'Aviation civile TE.RPRO.00034-004 © European Aviation Safety Agency. All rights reserved. ISO 9001 certified. Proprietary document. Copies are not controlled. Confirm revision status through the EASA intranet/internet. Page 81 of 81 An agency of the European Union
Allikas: Lennuamet dokumendiregister →
dokumendiregister.eeAsutusedEesti avalike dokumendiregistrite otsing · nimistu.ee andmetel