Commission Implementing Regulation (EU) 2017/373 of 1 March 2017 laying down common requirements for providers of air traffic management/air navigation services and other air traffic management network functions and their oversight, repealing Regulation (EC) No 482/2008, Implementing Regulations (EU) No 1034/2011, (EU) No 1035/2011 and (EU) 2016/1377 and amending Regulation (EU) No 677/2011 (Text with EEA relevance. )

• 1. taxiway edge and taxiway centre line lights;

• 1. secondary power supply including switchover time; and

• 1. remarks.

AD 2.16 Helicopter landing area

Detailed description of helicopter landing area provided at the aerodrome, including:

• 1. geographical coordinates in degrees, minutes, seconds and hundredths of seconds and, where appropriate, geoid undulation of the geometric centre of touchdown and lift-off (TLOF) or of each threshold of final approach and take-off (FATO) area:
• — for non-precision approaches, to the nearest metre or foot; and
• — for precision approaches, to the nearest tenth of a metre or tenth of a foot;

• 1. TLOF and/or FATO area elevation:
• — for non-precision approaches, to the nearest metre or foot; and
• — for precision approaches, to the nearest tenth of a metre or tenth of a foot;

• 1. TLOF and FATO area dimensions to the nearest metre or foot, surface type, bearing strength and marking;

• 1. true bearings to one-hundredth of a degree of FATO;

• 1. declared distances available, to the nearest metre or foot;

• 1. approach and FATO lighting; and

• 1. remarks.

AD 2.17 Air traffic services airspace

Detailed description of ATS airspace organised at the aerodrome, including:

• 1. airspace designation and geographical coordinates in degrees, minutes and seconds of the lateral limits;

• 1. vertical limits;

• 1. airspace classification;

• 1. call sign and language(s) of the ATS unit providing service;

• 1. transition altitude;

• 1. hours of applicability; and

• 1. remarks.

AD 2.18 Air traffic services communication facilities

Detailed description of ATS communication facilities established at the aerodrome, including:

• 1. service designation;

• 1. call sign;

• 1. channel(s);

• 1. SATVOICE number(s), if available;

• 1. logon address, as appropriate;

• 1. hours of operation; and

• 1. remarks.

AD 2.19 Radio navigation and landing aids

Detailed description of radio navigation and landing aids associated with the instrument approach and the terminal area procedures at the aerodrome, including:

• 1. • (a) type of aids;
• (b) magnetic variation to the nearest degree, as appropriate;
• (c) type of supported operation for ILS/MLS/GLS, basic GNSS and SBAS;
• (d) classification for ILS;
• (e) facility classification and approach facility designation(s) for GBAS;
• (f) for VOR/ILS/MLS, also station declination to the nearest degree used for technical line-up of the aid;

• 1. identification, if required;

• 1. frequency(ies), channel number(s), service provider and reference path identifier(s) (RPI(s)), as appropriate;

• 1. hours of operation, as appropriate;

• 1. geographical coordinates in degrees, minutes, seconds and tenths of seconds of the position of the transmitting antenna, as appropriate;

• 1. elevation of the DME transmitting antenna to the nearest 30 m (100 ft) and of the distance-measuring equipment precision (DME/P) to the nearest 3 m (10 ft), elevation of GBAS reference point to the nearest metre or foot, and the ellipsoid height of the point to the nearest metre or foot; for SBAS, the ellipsoid height of the landing threshold point (LTP) or the fictitious threshold point (FTP) to the nearest metre or foot;

• 1. service volume radius from the GBAS reference point to the nearest kilometre or nautical mile;

• 1. remarks. When the same aid is used for both en-route and aerodrome purposes, a description shall also be given in section ENR 4. If the ground-based augmentation system (GBAS) serves more than one aerodrome, a description of the aid shall be provided under each aerodrome. If the operating authority of the facility is other than the designated authority, the name of the operating authority shall be indicated in the remarks column. Facility coverage shall be indicated in the remarks column.

AD 2.20 Local aerodrome regulations

Detailed description of regulations applicable to the use of the aerodrome, including the acceptability of training flights, non-radio and microlight aircraft and similar, and to ground manoeuvring and parking but excluding flight procedures.

AD 2.21 Noise abatement procedures

Detailed description of noise abatement procedures established at the aerodrome.

AD 2.22 Flight procedures

Detailed description of the conditions and flight procedures, including radar and/or ADS-B procedures, established on the basis of airspace organisation at the aerodrome. When established, detailed description of the LVP at the aerodrome, including:

• 1. runway(s) and associated equipment authorised for use when LVP are in effect, including for operations with operational credits with RVR less than 550 m, if applicable;

• 1. defined meteorological conditions under which initiation, use and termination of LVP would be made;

• 1. description of ground marking/lighting for use under LVP;

• 1. remarks.

AD 2.23 Additional information

Additional information at the aerodrome, such as an indication of bird concentrations at the aerodrome, together with an indication of significant daily movement between resting and feeding areas, to the extent practicable.

Specific additional information regarding remote aerodrome ATS:

• 1. indication that remote aerodrome ATS is provided;

• 1. location of the signalling lamp by e.g. the phrase ‘signalling lamp positioned at [geographical fix]’ as well as a clear indication of the signalling lamp location in the aerodrome chart for each relevant aerodrome;

• 1. description of any specific communication methods as deemed necessary in case of multiple mode of operation, such as e.g. the inclusion of airport names/ATS unit call sign for all transmissions (i.e. not only for the first contact) between pilots and ATCOs/aerodrome flight information service offices (AFISOs);

• 1. description of any relevant actions required by the airspace users following an emergency/abnormal situation and possible contingency measures by the ATS provider in case of disruptions, if applicable (in point AD 2.22 ‘Flight Procedures’); and

• 1. description of the interdependencies of service availability or indication of aerodromes not suitable for diversion from the aerodrome (airspace users shall not plan an aerodrome as alternate when serviced by the same remote tower centre), if deemed applicable.

AD 2.24 Aeronautical charts related to an aerodrome

Aeronautical charts related to an aerodrome shall be included in the following order:

• 1. Aerodrome/Heliport Chart – ICAO;

• 1. Aircraft Parking/Docking Chart – ICAO;

• 1. Aerodrome Ground Movement Chart – ICAO;

• 1. Aerodrome Obstacle Chart – ICAO Type A (for each runway);

• 1. Aerodrome Terrain and Obstacle Chart – ICAO (Electronic);

• 1. Precision Approach Terrain Chart – ICAO (precision approach Category II and III runways);

• 1. Area Chart – ICAO (departure and transit routes);

• 1. Standard Departure Chart – Instrument – ICAO;

• 1. Area Chart – ICAO (arrival and transit routes);

• 1. Standard Arrival Chart – Instrument – ICAO;

• 1. ATC Surveillance Minimum Altitude Chart – ICAO;

• 1. Instrument Approach Chart – ICAO (for each runway and procedure type);

• 1. Visual Approach Chart – ICAO; and

• 1. bird concentrations in the vicinity of the aerodrome.

If some of the aeronautical charts are not produced, a statement to this effect shall be given in section GEN 3.2 ‘Aeronautical charts’.

AD 2.25 Visual segment surface (VSS) penetration

Visual segment surface (VSS) penetration, including procedure and procedure minima affected.

AD 3. HELIPORTS

When a helicopter landing area is provided at the aerodrome, associated data shall be listed only under point AD 2.16.

Note.— is to be replaced by the relevant ICAO location indicator.

AD 3.1 Heliport location indicator and name

The ICAO location indicator assigned to the heliport and to the names of the heliport shall be included in AIP. An ICAO location indicator shall be an integral part of the referencing system applicable to all subsections in section AD 3.

AD 3.2 Heliport geographical and administrative data

The requirement is for heliport geographical and administrative data, including:

• 1. heliport reference point (geographical coordinates in degrees, minutes and seconds) and its site;

• 1. direction and distance of heliport reference point from centre of the city or town that the heliport serves;

• 1. heliport elevation to the nearest metre or foot, and reference temperature;

• 1. where appropriate, geoid undulation at the heliport elevation position to the nearest metre or foot;

• 1. magnetic variation to the nearest degree, date of information and annual change;

• 1. name of heliport operator, address, telephone and telefax numbers, email address, AFS address and, if available, website address;

• 1. types of traffic permitted to use the heliport (IFR/VFR); and

• 1. remarks.

AD 3.3 Operational hours

Detailed description of the hours of operation of services at the heliport, including:

• 1. heliport operator;

• 1. customs and immigration;

• 1. health and sanitation;

• 1. AIS briefing office;

• 1. ATS reporting office (ARO);

• 1. MET briefing office;

• 1. ATS;

• 1. fuelling;

• 1. handling;

• 1. security;

• 1. de-icing; and

• 1. remarks.

AD 3.4 Handling services and facilities

Detailed description of the handling services and facilities available at the heliport, including:

• 1. cargo-handling facilities;

• 1. fuel and oil types;

• 1. fuelling facilities and capacity;

• 1. de-icing facilities;

• 1. hangar space for visiting helicopter;

• 1. repair facilities for visiting helicopter; and

• 1. remarks.

AD 3.5 Passenger facilities

Passenger facilities available at the heliport, provided as a brief description or as a reference to other information sources such as a website, including:

• 1. hotel(s) at or in the vicinity of the heliport;

• 1. restaurant(s) at or in the vicinity of the heliport;

• 1. transportation possibilities;

• 1. medical facilities;

• 1. bank and post office at or in the vicinity of the heliport;

• 1. tourist office; and

• 1. remarks.

AD 3.6 Rescue and firefighting services

Detailed description of the RFFSs and equipment available at the heliport, including:

• 1. heliport category for firefighting;

• 1. rescue equipment;

• 1. capability for removal of disabled helicopter; and

• 1. remarks.

AD 3.7 Seasonal availability – clearing

Detailed description of the equipment and operational priorities established for the clearance of heliport movement areas, including:

• 1. type(s) of clearing equipment;

• 1. clearance priorities; and

• 1. remarks.

AD 3.8 Aprons, taxiways and check locations/positions data

Details related to the physical characteristics of aprons, taxiways and locations/positions of designated checkpoints, including:

• 1. designation, surface and strength of aprons, helicopter stands;

• 1. designation, width, and surface type of helicopter ground taxiways;

• 1. width and designation of helicopter air taxiway and air transit route;

• 1. location and elevation to the nearest metre or foot of altimeter checkpoints;

• 1. location of VOR checkpoints;

• 1. position of INS checkpoints in degrees, minutes, seconds and hundredths of seconds; and

• 1. remarks.

If check locations/positions are presented on a heliport chart, a note to that effect shall be provided under this subsection.

AD 3.9 Markings and markers

Brief description of final approach and take-off area and taxiway markings and markers, including:

• 1. final approach and take-off markings;

• 1. taxiway markings, air taxiway markers and air transit route markers; and

• 1. remarks.

AD 3.10 Heliport obstacles

Detailed description of obstacles, including:

• 1. obstacle identification or designation;

• 1. type of obstacle;

• 1. obstacle position, represented by geographical coordinates in degrees, minutes, seconds and tenths of seconds;

• 1. obstacle elevation and height to the nearest metre or foot;

• 1. obstacle marking, and type and colour of obstacle lighting (if any);

• 1. if appropriate, an indication that the list of obstacles is available in electronic form, and a reference to point GEN 3.1.6; and

• 1. ‘NIL’ indication, if appropriate.

AD 3.11 Meteorological information provided

Detailed description of meteorological information provided at the heliport and an indication of which meteorological office is responsible for the service enumerated, including:

• 1. name of the associated meteorological office;

• 1. hours of service and, where applicable, the designation of the responsible meteorological office outside these hours;

• 1. office responsible for preparation of TAFs, and periods of validity of the forecasts;

• 1. availability of the TREND forecasts for the heliport, and interval of issuance;

• 1. information on how briefing and/or consultation is provided;

• 1. type of flight documentation supplied and language(s) used in flight documentation;

• 1. charts and other information displayed or available for briefing or consultation;

• 1. supplementary equipment available for providing information on meteorological conditions, such as weather radar and receiver for satellite images;

• 1. the ATS unit(s) provided with meteorological information; and

• 1. additional information such as any limitation of service, etc.

AD 3.12 Heliport data

Detailed description of heliport dimensions and related information, including:

• 1. heliport type – surface-level, elevated or helideck;

• 1. touchdown and lift-off (TLOF) area dimensions to the nearest metre or foot;

• 1. true bearings to one-hundredth of a degree of final approach and take-off (FATO) area;

• 1. dimensions to the nearest metre or foot of FATO, and surface type;

• 1. surface and bearing strength in tonnes (1 000 kg) of TLOF;

• 1. geographical coordinates in degrees, minutes, seconds and hundredths of seconds and, where appropriate, geoid undulation of the geometric centre of TLOF or of each threshold of FATO:
• — for non-precision approaches, to the nearest metre or foot; and
• — for precision approaches, to the nearest tenth of a metre or tenth of a foot;

• 1. TLOF and/or FATO slope and elevation:
• — for non-precision approaches, to the nearest metre or foot; and
• — for precision approaches, to the nearest tenth of a metre or tenth of a foot;

• 1. dimensions of safety area;

• 1. dimensions to the nearest metre or foot of helicopter clearway;

• 1. the existence of an obstacle-free sector; and

• 1. remarks.

AD 3.13 Declared distances

Detailed description of declared distances to the nearest metre or foot, where relevant for a heliport, including:

• 1. take-off distance available, and if applicable, alternative reduced declared distances;

• 1. rejected take-off distance available;

• 1. landing distance available; and

• 1. remarks, including entry or start point where alternative reduced declared distances have been declared.

AD 3.14 Approach and FATO lighting

Detailed description of approach and FATO lighting, including:

• 1. type, length and intensity of approach lighting system;

• 1. type of visual approach slope indicator system;

• 1. characteristics and location of FATO area lights;

• 1. characteristics and location of aiming point lights;

• 1. characteristics and location of TLOF lighting system; and

• 1. remarks.

AD 3.15 Other lighting, secondary power supply

Description of other lighting and secondary power supply, including:

• 1. location, characteristics and hours of operation of heliport beacon;

• 1. location and lighting of wind direction indicator (WDI);

• 1. taxiway edge and taxiway centre line lights;

• 1. secondary power supply including switchover time; and

• 1. remarks.

AD 3.16 Air traffic services airspace

Detailed description of ATS airspace organised at the heliport, including:

• 1. airspace designation and geographical coordinates in degrees, minutes and seconds of the lateral limits;

• 1. vertical limits;

• 1. airspace classification;

• 1. call sign and language(s) of ATS unit providing service;

• 1. transition altitude;

• 1. hours of applicability; and

• 1. remarks.

AD 3.17 Air traffic services communication facilities

Detailed description of ATS communication facilities established at the heliport, including:

• 1. service designation;

• 1. call sign;

• 1. frequency(ies);

• 1. hours of operation; and

• 1. remarks.

AD 3.18 Radio navigation and landing aids

Detailed description of radio navigation and landing aids associated with the instrument approach and the terminal area procedures at the heliport, including:

• 1. • (a) type of aids;
• (b) magnetic variation to the nearest degree, as appropriate;
• (c) type of supported operation for ILS/MLS/GLS, basic GNSS and SBAS;
• (d) classification for ILS;
• (e) facility classification and approach facility designation(s) for GBAS;
• (f) for VOR/ILS/MLS, also station declination to the nearest degree used for technical line-up of the aid;

• 1. identification, if required;

• 1. frequency(ies), channel number(s), service provider and reference path identifier(s) (RPI(s)), as appropriate;

• 1. hours of operation, as appropriate;

• 1. geographical coordinates in degrees, minutes, seconds and tenths of seconds of the position of the transmitting antenna, as appropriate;

• 1. elevation of the DME transmitting antenna to the nearest 30 m (100 ft) and of the distance-measuring equipment precision (DME/P) to the nearest 3 m (10 ft), elevation of GBAS reference point to the nearest metre or foot, and the ellipsoid height of the point to the nearest metre or foot; for SBAS, the ellipsoid height of the landing threshold point (LTP) or the fictitious threshold point (FTP) to the nearest metre or foot;

• 1. service volume radius from the GBAS reference point to the nearest kilometre or nautical mile;

• 1. remarks.

When the same aid is used for both en-route and heliport purposes, a description shall also be given in section ENR 4. If the GBAS serves more than one heliport, a description of the aid shall be provided under each heliport. If the operating authority of the facility is other than the designated authority, the name of the operating authority shall be indicated in the remarks column. Facility coverage shall be indicated in the remarks column.

AD 3.19 Local heliport regulations

Detailed description of regulations applicable to the use of the heliport, including the acceptability of training flights, non-radio and microlight aircraft and similar, and to ground manoeuvring and parking but excluding flight procedures.

AD 3.20 Noise abatement procedures

Detailed description of noise abatement procedures established at the heliport.

AD 3.21 Flight procedures

Detailed description of the conditions and flight procedures, including radar and/or ADS-B procedures, established on the basis of airspace organisation established at the heliport. When established, detailed description of the low visibility procedures at the heliport, including:

• 1. touchdown and lift-off (TLOF) area(s) and associated equipment authorised for use under low visibility procedures;

• 1. defined meteorological conditions under which initiation, use and termination of low visibility procedures would be made;

• 1. description of ground marking/lighting for use under low visibility procedures; and

• 1. remarks.

AD 3.22 Additional information

Additional information about the heliport, such as an indication of bird concentrations at the heliport together with an indication of significant daily movement between resting and feeding areas, to the extent practicable.

AD 3.23 Charts related to a heliport

Aeronautical charts related to a heliport shall be included in the following order:

• 1. Aerodrome/Heliport Chart – ICAO;

• 1. Area Chart – ICAO (departure and transit routes);

• 1. Standard Departure Chart – Instrument – ICAO;

• 1. Area Chart – ICAO (arrival and transit routes);

• 1. Standard Arrival Chart – Instrument – ICAO;

• 1. ATC Surveillance Minimum Altitude Chart – ICAO;

• 1. Instrument Approach Chart – ICAO (for each procedure type);

• 1. Visual Approach Chart – ICAO; and

• 1. bird concentrations in the vicinity of the heliport.

If some of the aeronautical charts are not produced, a statement to this effect shall be given in section GEN 3.2 ‘Aeronautical charts’.

Appendix 2

NOTAM FORMAT

Image omitted; see official source

INSTRUCTIONS FOR THE COMPLETION OF THE NOTAM FORMAT

1. General

The qualifier line (Item Q) and all identifiers (Items A to G inclusive) each followed by a closing parenthesis, as shown in the format, shall be transmitted unless there is no entry to be made against a particular identifier.

2. NOTAM numbering

Each NOTAM shall be allocated a series identified by a letter and a four-digit number followed by a stroke and a two-digit number for the year (e.g. A0023/03). Each series shall start on 1 January with the number 0001.

3. Qualifiers (Item Q)

Item Q is divided into eight fields, each separated by a stroke. An entry shall be made in each field. Examples of how fields are to be filled in are shown in the Aeronautical Information Services Manual (ICAO Doc 8126). The definition of the field is as follows:

• 1. FIR
• a) If the subject of the information is geographically located within one FIR, the ICAO location indicator shall be that of the FIR concerned. When an aerodrome is situated within the overlying FIR of another Member State, the first field of Item Q shall contain the code for that overlying FIR (e.g. Q) LFRR/…A) EGJJ); or, if the subject of the information is geographically located within more than one FIR, the FIR field shall be composed of the ICAO nationality letters of the Member State originating the NOTAM followed by ‘XX’. The location indicator of the overlying UIR shall not be used. The ICAO location indicators of the FIRs concerned shall then be listed in Item A or the indicator of the Member State or the delegated entity which is responsible for provision of a navigation service in more than one Member State.
• b) If one Member State issues a NOTAM affecting FIRs in a group of Member States, the first two letters of the ICAO location indicator of the issuing Member State plus ‘XX’ shall be included. The location indicators of the FIRs concerned shall then be listed in Item A or the indicator of the Member State or the delegated entity which is responsible for provision of a navigation service in more than one Member State.

• 1. NOTAM CODE All NOTAM Code groups contain a total of five letters, the first of which is always the letter ‘Q’. The second and third letters identify the subject, and the fourth and fifth letters denote the status or condition of the subject reported upon. The two-letter codes for subjects and conditions are those contained in ICAO Doc 8400 ‘Procedures for Air Navigation Services – ICAO Abbreviations and Codes (PANS-ABC)’. For combinations of second and third, and fourth and fifth letters, refer to the ‘NOTAM Selection Criteria’ contained in ICAO Doc 8126 or insert one of the following combinations, as appropriate:
• a) if the subject is not listed in the NOTAM Code (ICAO Doc 8400) or in the NOTAM Selection Criteria (ICAO Doc 8126), insert ‘XX’ as the second and third letters (e.g. QXXAK); if the subject is ‘XX’, use ‘XX’ also for condition (e.g. QXXXX).
• b) if the condition of the subject is not listed in the NOTAM Code (ICAO Doc 8400) or in the NOTAM Selection Criteria (ICAO Doc 8126), insert ‘XX’ as the fourth and fifth letters (e.g. QFAXX);
• c) when a NOTAM containing operationally significant information is issued and when it is used to announce the existence of AIRAC AIP Amendments or Supplements, insert ‘TT’ as the fourth and fifth letters of the NOTAM Code;
• d) when a NOTAM is issued containing a checklist of valid NOTAM, insert ‘KKKK’ as the second, third, fourth and fifth letters; and
• e) the following fourth and fifth letters of the NOTAM Code shall be used in NOTAM cancellations: AK = RESUMED NORMAL OPERATION AL = OPERATIVE (OR RE-OPERATIVE) SUBJECT TO PREVIOUSLY PUBLISHED LIMITATIONS/CONDITIONS AO = OPERATIONAL CC = COMPLETED CN = CANCELLED HV = WORK COMPLETED XX = PLAIN LANGUAGE As Q – - AO = Operational shall be used for NOTAM cancellation and NOTAM promulgating new equipment or services, use the following fourth and fifth letters Q – - CS = Installed. Q – - CN = CANCELLED shall be used to cancel planned activities, e.g. navigation warnings; Q – - HV = WORK COMPLETED shall be used to cancel work in progress.

• 1. TRAFFIC I = IFR V = VFR K = NOTAM is a checklist Depending on the NOTAM subject and content, the qualifier field TRAFFIC may contain combined qualifiers.

• 1. PURPOSE N = NOTAM selected for the immediate attention of flight crew members B = NOTAM of operational significance selected for PIB entry O = NOTAM concerning flight operations M = Miscellaneous NOTAM; not subject for a briefing, but available on request K = NOTAM is a checklist Depending on the NOTAM subject and content, the qualifier field PURPOSE may contain the combined qualifiers BO or NBO.

• 1. SCOPE A = Aerodrome E = En-route W = Nav Warning K = NOTAM is a checklist Depending on the NOTAM subject and content, the qualifier field SCOPE may contain combined qualifiers.

• 1. and 7. LOWER/UPPER LOWER and UPPER limits shall only be expressed in flight levels (FL) and shall express the actual vertical limits of the area of influence without the addition of buffers. In the case of navigation warnings and airspace restrictions, values entered shall be consistent with those provided under Items F and G. If the subject does not contain specific height information, insert ‘000’ for LOWER and ‘999’ for UPPER as default values.

• 1. COORDINATES, RADIUS The latitude and longitude accurate to one minute, as well as a three-digit distance figure giving the radius of influence in NM (e.g. 4700N01140E043). Coordinates present the approximate centre of circle whose radius encompasses the whole area of influence, and if the NOTAM affects the entire FIR/UIR or more than one FIR/UIR, enter the default value ‘999’ for radius.

4. Item A

Insert the ICAO location indicator as contained in ICAO Doc 7910 of the aerodrome or FIR in which the facility, airspace, or condition being reported on is located. More than one FIR/UIR may be indicated, when appropriate. If there is no available ICAO location indicator, use the ICAO nationality letter as given in ICAO Doc 7910, Part 2, plus ‘XX’ and followed up in Item E by the name, in plain language.

If information concerns GNSS, insert the appropriate ICAO location indicator allocated for a GNSS element or the common location indicator allocated for all elements of the GNSS (except GBAS).

In the case of GNSS, the location indicator may be used when identifying a GNSS element outage such as KNMH for a GPS satellite outage.

5. Item B

For date-time group, use a ten-figure group, giving year, month, day, hours and minutes in UTC. This entry is the date-time at which the NOTAMN comes into force. In the cases of NOTAMR and NOTAMC, the date-time group is the actual date and time of the NOTAM origination. The start of a day shall be indicated by ‘0000’.

6. Item C

With the exception of NOTAMC, a date-time group (a ten-figure group giving year, month, day, hours and minutes in UTC) indicating duration of information shall be used unless the information is of a permanent nature in which case the abbreviation ‘PERM’ is inserted instead. The end of a day shall be indicated by ‘2359’, ‘2400’ shall not be used. If the information on timing is uncertain, the approximate duration shall be indicated using a date-time group followed by the abbreviation ‘EST’. Any NOTAM which includes an ‘EST’ shall be cancelled or replaced before the date-time specified in Item C.

7. Item D

If the hazard, status of operation or condition of facilities being reported on will be active in accordance with a specific time and date schedule between the dates-times indicated in Items B and C, insert such information under Item D. If Item D exceeds 200 characters, consideration shall be given to providing such information in a separate, consecutive NOTAM.

8. Item E

Use decoded NOTAM Code complemented, where necessary, by ICAO abbreviations, indicators, identifiers, designators, call signs, frequencies, figures and plain language. When NOTAM is selected for international distribution, English text shall be included for those parts expressed in plain language. This entry shall be clear and concise in order to provide a suitable PIB entry. In the case of NOTAMC, a subject reference and status message shall be included to enable accurate plausibility checks.

9. Items F and G

These items are normally applicable to navigation warnings or airspace restrictions and are usually part of the PIB entry. Insert both lower and upper height limits of activities or restrictions, clearly indicating only one reference datum and unit of measurement. The abbreviations ‘GND’ or ‘SFC’ shall be used in Item F to designate ‘ground’ and ‘surface’ respectively. The abbreviation ‘UNL’ shall be used in Item G to designate ‘unlimited’.

Appendix 3

SNOWTAM Format

Image omitted; see official source

INSTRUCTIONS FOR THE COMPLETION OF THE SNOWTAM FORMAT

1. General

• (a) When reporting on more than one runway, repeat Items B to H (aeroplane performance calculation section).

• (b) The letters used to indicate items are only used for reference purpose and shall not be included in the messages. The letters, M (mandatory), C (conditional) and O (optional) mark the usage and information and shall be included as explained below.

• (c) Metric units shall be used and the unit of measurement shall not be reported.

• (d) The maximum validity of SNOWTAM is 8 hours. New SNOWTAM shall be issued whenever a new runway condition report is received.

• (e) A SNOWTAM cancels the previous SNOWTAM.

• (f) The abbreviated heading ‘TTAAiiii CCCC MMYYGGgg (BBB)’ is included to facilitate the automatic processing of SNOWTAM messages in computer databanks. The explanation of these symbols is: TT = data designator for SNOWTAM = SW; AA = geographical designator for Member States, e.g. LF = FRANCE; iiii = SNOWTAM serial number in a four-digit group; CCCC = four-letter location indicator of the aerodrome to which the SNOWTAM refers; MMYYGGgg = date/time of observation/measurement, whereby: MM = month, e.g. January = 01, December = 12; YY = day of the month; GGgg = time in hours (GG) and minutes (gg) UTC; (BBB) = optional group for: Correction, in the case of an error, to a SNOWTAM message previously disseminated with the same serial number = COR. Brackets in (BBB) shall be used to indicate that this group is optional. When reporting on more than one runway and individual dates/times of observation/assessment are indicated by repeated Item B, the latest date/time of observation/assessment shall be inserted in the abbreviated heading (MMYYGGgg).

• (g) The text ‘SNOWTAM’ in the SNOWTAM Format and the SNOWTAM serial number in a four-digit group shall be separated by a space, e.g. SNOWTAM 0124.

• (h) For readability purposes for the SNOWTAM message, a linefeed shall be included after the SNOWTAM serial number, after Item A, and after the aeroplane performance calculation section.

• (i) When reporting on more than one runway, repeat the information in the aeroplane performance calculation section from the date and time of assessment for each runway before the information in the situational awareness section.

• (j) Mandatory information is:
• (1) AERODROME LOCATION INDICATOR;
• (2) DATE AND TIME OF ASSESSMENT;
• (3) LOWER RUNWAY DESIGNATOR NUMBER;
• (4) RUNWAY CONDITION CODE FOR EACH RUNWAY THIRD; and
• (5) CONDITION DESCRIPTION FOR EACH RUNWAY THIRD (when runway condition code (RWYCC) is reported 0–6)

2. Aeroplane performance calculation section

• Item A — Aerodrome location indicator (four-letter location indicator).

• Item B — Date and time of assessment (eight-figure date/time group giving time of observation as month, day, hour and minute in UTC).

• Item C — Lower runway designator number ( nn[L] or nn[C] or nn[R]).

Only one runway designator shall be inserted for each runway and always the lower number.

• Item D — Runway condition code for each runway third. Only one digit (0, 1, 2, 3, 4, 5 or 6) is inserted for each runway third, separated by an oblique stroke (n/n/n).

• Item E — Per cent coverage for each runway third. When provided, insert 25, 50, 75 or 100 for each runway third, separated by an oblique stroke ([n]nn/[n]nn/[n]nn).

This information shall be provided only when there is a condition description for each runway third (Item G) that has been reported other than ‘DRY’.

When the conditions are not reported, this shall be signified by the insertion of ‘NR’ for the appropriate runway third(s).

• Item F — Depth of loose contaminant for each runway third. When provided, insert in millimetres for each runway third, separated by an oblique stroke (nn/nn/nn or nnn/nnn/nnn).

This information shall only be provided for the following contamination types:

• — standing water, values to be reported 04, then assessed value. Significant changes 3 mm;

• — slush, values to be reported 03, then assessed value. Significant changes 3 mm;

• — wet snow, values to be reported 03, then assessed value. Significant changes 5 mm; and

• — dry snow, values to be reported 03, then assessed value. Significant changes 20 mm.

When the conditions are not reported, this shall be signified by the insertion of ‘NR’ for the appropriate runway third(s).

• Item G — Condition description for each runway third. Any of the following condition descriptions for each runway third, separated by an oblique stroke, shall be inserted.

COMPACTED SNOW

DRY SNOW

DRY SNOW ON TOP OF COMPACTED SNOW

DRY SNOW ON TOP OF ICE

FROST

ICE

SLIPPERY WET

SLUSH

SPECIALLY PREPARED WINTER RUNWAY

STANDING WATER

WATER ON TOP OF COMPACTED SNOW

WET

WET ICE

WET SNOW

WET SNOW ON TOP OF COMPACTED SNOW

WET SNOW ON TOP OF ICE

DRY (only reported when there is no contaminant)

When the conditions are not reported, this shall be signified by the insertion of ‘NR’ for the appropriate runway third(s).

• Item H — Width of runway to which the runway condition codes apply. The width in metres, if less than the published runway width, shall be inserted.

3. Situational awareness section

Elements in the situational awareness section shall end with a full stop.

Elements in the situational awareness section for which no information exists, or where the conditional circumstances for publication are not fulfilled, shall be left out completely.

• Item I — Reduced runway length. The applicable runway designator and available length in metres shall be inserted (e.g. RWY nn [L] or nn [C] or nn [R] REDUCED TO [n]nnn).

This information is conditional when a NOTAM has been published with a new set of declared distances.

• Item J — Drifting snow on the runway. When reported, ‘DRIFTING SNOW’ shall be inserted with a space ‘DRIFTING SNOW’ (RWY nn or RWY nn[L] or nn[C] or nn[R] DRIFTING SNOW).

• Item K — Loose sand on the runway. When loose sand is reported on the runway, the lower runway designator shall be inserted with a space ‘LOOSE SAND’ (RWY nn or RWY nn[L] or nn[C] or nn[R] LOOSE SAND).

• Item L — Chemical treatment on the runway. When chemical treatment has been reported applied, the lower runway designator shall be inserted with a space ‘CHEMICALLY TREATED’ (RWY nn or RWY nn[L] or nn[C] or nn[R] CHEMICALLY TREATED).

• Item M — Snowbanks on the runway. When snowbanks are reported present on the runway, the lower runway designator shall be inserted with a space ‘SNOWBANK’ and with a space left ‘L’ or right ‘R’ or both sides ‘LR’, followed by the distance in metres from centre line separated by a space ‘FM CL’ (RWY nn or RWY nn[L] or nn[C] or nn[R] SNOWBANK Lnn or Rnn or LRnn FM CL).

• Item N — Snowbanks on a taxiway. When snowbanks are present on taxiway(s), the taxiway(s) designator(s) shall be inserted with a space ‘SNOWBANKS’ (TWY [nn]n or TWYS [nn]n/[nn]n/[nn]n… or ALL TWYS SNOWBANKS).

• Item O — Snowbanks adjacent to the runway. When snowbanks are reported present, penetrating the height profile in the aerodrome snow plan, the lower runway designator and ‘ADJ SNOWBANKS’ shall be inserted (RWY nn or RWY nn[L] or nn[C] or nn[R] ADJ SNOWBANKS).

• Item P — Taxiway conditions. When taxiway conditions are reported slippery or poor, the taxiway designator followed by a space ‘POOR’ shall be inserted (TWY [n or nn] POOR or TWYS [n or nn]/[n or nn]/[n or nn] POOR… or ALL TWYS POOR).

• Item R — Apron conditions. When apron conditions are reported slippery or poor, the apron designator followed by a space ‘POOR’ shall be inserted (APRON [nnnn] POOR or APRONS [nnnn]/[nnnn]/[nnnn] POOR or ALL APRONS POOR).

• Item S — (NR) Not reported.

• Item T — Plain-language remarks.

Appendix 4

ASHTAM FORMAT

Image omitted; see official source

INSTRUCTIONS FOR THE COMPLETION OF THE ASHTAM FORMAT

1. General

• 1.1 The ASHTAM provides information on the status of activity of a volcano when a change in its activity is, or is expected to be of operational significance. This information is provided using the volcano level of alert colour code given in 3.5 below.

• 1.2 In the event of a volcanic eruption producing ash cloud of operational significance, the ASHTAM also provides information on the location, extent and movement of the ash cloud and the air routes and flight levels affected.

• 1.3 Issuance of an ASHTAM giving information on a volcanic eruption, in accordance with section 3 below, shall not be delayed until complete information A to K is available but shall be issued immediately following receipt of notification that an eruption has occurred or is expected to occur, or a change in the status of activity of a volcano of operational significance has occurred or is expected to occur, or an ash cloud is reported. In the case of an expected eruption, and hence no ash cloud evident at that time, items A to E shall be completed and items F to I indicated as ‘not applicable’. Similarly, if a volcanic ash cloud is reported, e.g. by special air-report, but the source volcano is not known at that time, the ASHTAM shall be issued initially with items A to E indicated as ‘unknown’, and items F to K completed, as necessary, based on the special air-report, pending receipt of further information. In other circumstances, if information for a specific field A to K is not available indicate ‘NIL’.

• 1.4 The maximum period of validity of ASHTAM is 24 hours a day. New ASHTAM shall be issued whenever there is a change in the level of alert.

2. Abbreviated heading

• 2.1 Following the usual ‘Aeronautical fixed – telecommunications network (AFTN)’ communications header, the abbreviated heading ‘TT AAiiii CCCC MMYYGGgg (BBB)’ shall be included to facilitate the automatic processing of ASHTAM messages in computer databanks. The explanation of these symbols is: TT = data designator for ASHTAM = VA; AA = geographical designator for States, e.g. NZ = New Zealand; iiii = ASHTAM serial number in a four-figure group; CCCC = four-letter location indicator of the flight information region concerned; MMYYGGgg = date/time of report, whereby: MM = month, e.g. January = 01, December = 12; YY = day of the month; GGgg = time in hours (GG) and minutes (gg) UTC; (BBB) = Optional group for correction to an ASHTAM message previously disseminated with the same serial number = COR. Brackets in (BBB) shall be used to indicate that this group is optional.

3. Content of ASHTAM

• 3.1 Item A – Flight information region affected, plain-language equivalent of the location indicator given in the abbreviated heading, in this example: ‘Auckland Oceanic FIR’.

• 3.2 Item B – Date and time (UTC) of first eruption.

• 3.3 Item C – Name of volcano, and number of volcano as listed in ICAO Doc 9691 Manual on Volcanic Ash, Radioactive Material and Toxic Chemical Clouds, Appendix H, and on the World Map of Volcanoes and Principal Aeronautical Features.

• 3.4 Item D – Latitude/Longitude of the volcano in whole degrees or radial and distance of volcano from NAVAID, as listed in the ICAO Doc 9691 Manual on Volcanic Ash, Radioactive Material and Toxic Chemical Clouds, Appendix H, and on the World Map of Volcanoes and Principal Aeronautical Features.

• 3.5 Item E – Colour code for level of alert indicating volcanic activity, including any previous level of alert colour code as follows: Level of alert colour code Status of activity of volcano GREEN ALERT Volcano is in normal, non-eruptive state. or, after a change from a higher alert level: Volcanic activity considered to have ceased, and volcano reverted to its normal, non-eruptive state. YELLOW ALERT Volcano is experiencing signs of elevated unrest above known background levels. or, after a change from higher alert level: Volcanic activity has decreased significantly but continues to be closely monitored for possible renewed increase. ORANGE ALERT Volcano is exhibiting heightened unrest with increased likelihood of eruption. or, Volcanic eruption is underway with no or minor ash emission [specify ash-plume height, if possible]. RED ALERT Eruption is forecasted to be imminent with significant emission of ash into the atmosphere likely. or, Eruption is underway with significant emission of ash into the atmosphere [specify ash-plume height, if possible]. The colour code for the level of alert indicating the status of activity of the volcano and any change from a previous status of activity shall be provided to the area control centre by the responsible vulcanological agency in the Member State concerned, e.g. ‘RED ALERT FOLLOWING YELLOW’ OR ‘GREEN ALERT FOLLOWING ORANGE’.

• 3.6 Item F – If volcanic ash cloud of operational significance is reported, the horizontal extent and base/top of the ash cloud shall be indicated using latitude/longitude (in whole degrees) and altitudes in thousands of metres (feet) and/or radial and distance from source volcano. Information initially may be based only on special air-report, but subsequent information may be more detailed based on advice from the responsible meteorological watch office and/or volcanic ash advisory centre.

• 3.7 Item G – Forecast direction of movement of the ash cloud at selected levels shall be indicated based on advice from the responsible meteorological watch office and/or volcanic ash advisory centre.

• 3.8 Item H – Air routes and portions of air routes and flight levels affected, or expected to become affected, shall be indicated.

• 3.9 Item I – Closure of airspace, air routes or portions of air routes, and availability of alternative routes, shall be indicated.

• 3.10 Item J – Source of the information, e.g. ‘special air-report’ or ‘vulcanological agency’, etc. The source of information shall always be indicated, whether an eruption has actually occurred or ash cloud reported, or not.

• 3.11 Item K – Any operationally significant information, additional to the foregoing, shall be included in plain language.

ANNEX VII

SPECIFIC REQUIREMENTS FOR PROVIDERS OF DATA SERVICES

(Part-DAT)

SUBPART A — ADDITIONAL ORGANISATION REQUIREMENTS FOR PROVIDERS OF DATA SERVICES (DAT.OR)

SECTION 1 — GENERAL REQUIREMENTS

DAT.OR.100 Aeronautical data and information

• (a) The DAT provider shall receive, assemble, translate, select, format, distribute and/or integrate aeronautical data and information that is released by an authoritative source for use in aeronautical databases on certified aircraft application/equipment. In specific cases, if aeronautical data is not provided in the aeronautical information publication (AIP) or by an authoritative source or does not meet the applicable data quality requirements (DQRs), that aeronautical data may be originated by the DAT provider itself and/or by other DAT providers. In this context, that aeronautical data shall be validated by the DAT provider originating it.

• (b) When so requested by its customers, the DAT provider may process tailored data provided by the aircraft operator or originating from other DAT providers for use by that aircraft operator. The responsibility for this data and its subsequent update shall remain with the aircraft operator.

DAT.OR.105 Technical and operational competence and capability

• (a) In addition to ATM/ANS.OR.B.001, the DAT provider shall:
• (1) perform the reception, assembly, translation, selection, formatting, distribution and/or integration of aeronautical data and information that is released by aeronautical data source provider(s) into aeronautical databases for certified aircraft application/equipment under the applicable requirements. The type 2 DAT provider shall ensure that the DQRs are compatible with the intended use of the certified aircraft application/equipment through an appropriate arrangement with the specific equipment design approval holder or an applicant for an approval of that specific design;
• (2) issue a statement of conformity that the aeronautical databases it has produced are produced in accordance with this Regulation and the applicable industry standards;
• (3) provide assistance to the equipment design approval holder in dealing with any continuing airworthiness actions that are related to the aeronautical databases that have been produced.

• (b) For release of databases, the accountable manager shall nominate attesting staff identified in point DAT.TR.100(b) and allocate their responsibilities in an independent manner to attest through the statement of conformity that data meets the DQRs and processes are followed. The ultimate responsibility for the databases release statements signed by the attesting staff shall remain with the accountable manager of the DAT provider.

DAT.OR.110 Management system

In addition to point ATM/ANS.OR.B.005, the DAT provider, as applicable for the type of DAT provision, shall establish and maintain a management system that includes control procedures for:

• (a) document issue, approval or change;

• (b) DQRs change;

• (c) verification that incoming data has been produced in accordance with the applicable standards;

• (d) timely update of the data used;

• (e) identification and traceability;

• (f) processes for reception, assembly, translation, selection, formatting, distribution and/or integration of data into a generic database or database compatible with the specific aircraft application/equipment;

• (g) data verification and validation techniques;

• (h) identification of tools, including configuration management and tools qualification, as necessary;

• (i) handling of errors/deficiencies;

• (j) coordination with the aeronautical data source provider(s) and/or DAT provider(s), and with the equipment design approval holder or an applicant for an approval of that specific design when providing type 2 DAT services;

• (k) issue of statement of conformity;

• (l) controlled distribution of databases to users.

DAT.OR.115 Record-keeping

In addition to ATM/ANS.OR.B.030, the DAT provider shall include in its record-keeping system the elements indicated in DAT.OR.110.

SECTION 2 — SPECIFIC REQUIREMENTS

DAT.OR.200 Reporting requirements

• (a) The DAT provider shall:
• (1) report to the customer and, where applicable, the equipment design approval holder all the cases where aeronautical databases have been released by the DAT provider and have been subsequently identified to have deficiencies and/or errors, thus not meeting the applicable data requirements.;
• (2) report to the competent authority the deficiencies and/or errors identified according to point (1), which could lead to an unsafe condition. Such reports shall be made in a form and manner acceptable to the competent authority;
• (3) where the certified DAT provider is acting as a supplier to another DAT provider, report also to that other organisation all the cases where it has released aeronautical databases to that organisation and have been subsequently identified to have errors;
• (4) report to the aeronautical data source provider instances of erroneous, inconsistent or missing data in the aeronautical source.

• (b) The DAT provider shall establish and maintain an internal reporting system in the interest of safety to enable the collection and assessment of reports in order to identify adverse trends or to address deficiencies, and to extract reportable events and actions. This internal reporting system may be integrated into the management system as required in point ATM/ANS.OR.B.005.

SUBPART B — TECHNICAL REQUIREMENTS FOR PROVIDERS OF DATA SERVICES (DAT.TR)

SECTION 1 — GENERAL REQUIREMENTS

DAT.TR.100 Working methods and operating procedures

The DAT provider shall:

• (a) with regard to all the necessary aeronautical data:
• (1) establish DQRs that are agreed upon with the other DAT provider and in the case of a type 2 DAT provider, with the equipment design approval holder or an applicant for an approval of that specific design, to determine the compatibility of these DQRs with the intended use;
• (2) use data from an authoritative source(s) and, if required, other aeronautical data verified and validated by the DAT provider itself and/or by other DAT provider(s);
• (3) establish a procedure to ensure that the data is correctly processed;
• (4) establish and implement processes to ensure that the tailored data provided or requested by an aircraft operator or other DAT provider shall only be distributed to the requester itself; and

• (b) with regard to attesting staff that sign the statements of conformity issued under DAT.OR.105(b) ensure that:
• (1) the knowledge, background (including other functions in the organisation), and experience of the attesting staff are appropriate to their allocated responsibilities;
• (2) it maintains records of all attesting staff which include details of the scope of their authorisation;
• (3) attesting staff are provided with evidence of the scope of their authorisation.

DAT.TR.105 Required interfaces

The DAT provider shall ensure the necessary formal interfaces with:

• (a) aeronautical data source(s) and/or other DAT providers;

• (b) the equipment design approval holder for type 2 DAT provision, or an applicant for an approval of that specific design;

• (c) aircraft operators, as applicable.

ANNEX VIII

SPECIFIC REQUIREMENTS FOR PROVIDERS OF COMMUNICATION, NAVIGATION, OR SURVEILLANCE SERVICES

(Part-CNS)

SUBPART A — ADDITIONAL ORGANISATION REQUIREMENTS FOR PROVIDERS OF COMMUNICATION, NAVIGATION, OR SURVEILLANCE SERVICES (CNS.OR)

SECTION 1 — GENERAL REQUIREMENTS

CNS.OR.100 Technical and operational competence and capability

• (a) A communication, navigation or surveillance services provider shall ensure the availability, continuity, accuracy and integrity of their services.

• (b) A communication, navigation or surveillance services provider shall confirm the quality level of the services they are providing, and shall demonstrate that their equipment is regularly maintained and, where required, calibrated.

SUBPART B — TECHNICAL REQUIREMENTS FOR PROVIDERS OF COMMUNICATION, NAVIGATION OR SURVEILLANCE SERVICES (CNS.TR)

SECTION 1 — GENERAL REQUIREMENTS

CNS.TR.100 Working methods and operating procedures for providers of communication, navigation or surveillance services

A communication, navigation or surveillance services provider shall be able to demonstrate that its working methods and operating procedures are compliant with the standards of Annex 10 to the Chicago Convention on aeronautical telecommunications in the following versions as far as they are relevant to the provision of communication, navigation or surveillance services in the airspace concerned:

• (a) Volume I on radio navigation aids in its 6th edition of July 2006, including all amendments up to and including No 89;

• (b) 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;

• (c) Volume III on communications systems in its 2nd edition of July 2007, including all amendments up to and including No 89;

• (d) Volume IV on surveillance radar and collision avoidance systems in its 5th edition of July 2014, including all amendments up to and including No 91;

• (e) Volume V on aeronautical radio frequency spectrum utilisation in its 3rd edition of July 2013, including all amendments up to and including No 89.

SECTION 2 — TECHNICAL REQUIREMENTS FOR PROVIDERS OF SURVEILLANCE SERVICES

CNS.TR.205 Allocation and use of Mode S interrogator codes

• (a) A surveillance services provider shall only operate an eligible Mode S interrogator, using an eligible interrogator code (IC), if it has received an interrogator code allocation, for this purpose, from the Member State concerned.

• (b) A surveillance services provider that intends to operate, or operates, an eligible Mode S interrogator for which no interrogator code allocation has been received, shall submit to the Member State concerned an interrogator code application, include the following key items, as a minimum:
• (1) a unique application reference from the Member State concerned;
• (2) full contact details of the Member State’s representative responsible for the coordination of the Mode S interrogator code allocation;
• (3) full contact details of the Mode S operator’s point of contact for Mode S IC allocation matters;
• (4) Mode S interrogator name;
• (5) Mode S interrogator use (operational or test);
• (6) Mode S interrogator location;
• (7) Mode S interrogator planned date of first Mode S transmission;
• (8) requested Mode S coverage;
• (9) specific operational requirements;
• (10) SI code capability;
• (11) ‘II/SI code operation’ capability;
• (12) coverage map capability.

• (c) A surveillance services provider shall comply with the key items of the interrogator code allocations it has received, including the following items as a minimum:
• (1) the corresponding application reference from the Member State concerned;
• (2) a unique allocation reference from the interrogator code allocation service;
• (3) superseded allocation references, as required;
• (4) allocated interrogator code;
• (5) surveillance and lockout coverage restrictions under the form of sectored ranges or Mode S coverage map;
• (6) implementation period during which the allocation needs to be registered into the Mode S interrogator identified in the application;
• (7) implementation sequence which needs to be complied with;
• (8) optionally and associated with other alternatives: cluster recommendation;
• (9) specific operational restrictions, as required.

• (d) A surveillance services provider shall inform the Member State concerned at least every 6 months of any change in the installation planning or in the operational status of the eligible Mode S interrogators regarding any of the interrogator code allocation key items listed in point (c).

• (e) The surveillance services provider shall ensure that each of their Mode S interrogators uses exclusively its allocated interrogator code.

ANNEX IX

SPECIFIC REQUIREMENTS FOR PROVIDERS OF AIR TRAFFIC FLOW MANAGEMENT

(Part-ATFM)

TECHNICAL REQUIREMENTS FOR PROVIDERS OF AIR TRAFFIC FLOW MANAGEMENT (ATFM.TR)

SECTION 1 — GENERAL REQUIREMENTS

ATFM.TR.100 Working methods and operating procedures for providers of air traffic flow management

An air traffic flow management provider shall be able to demonstrate that its working methods and operating procedures are compliant with Commission Regulations (EU) No 255/2010 ([^E0054]) and (EU) 2019/123.

ANNEX X

SPECIFIC REQUIREMENTS FOR PROVIDERS OF AIRSPACE MANAGEMENT

(Part-ASM)

TECHNICAL REQUIREMENTS FOR PROVIDERS OF AIRSPACE MANAGEMENT (ASM.TR)

SECTION 1 — GENERAL REQUIREMENTS

ASM.TR.100 Working methods and operating procedures for providers of airspace management

An airspace management provider shall be able to demonstrate that its working methods and operating procedures are compliant with Commission Regulations (EC) No 2150/2005 ([^E0055]) and (EU) 2019/123.

ANNEX XI

SPECIFIC REQUIREMENTS FOR PROVIDERS OF FLIGHT PROCEDURE DESIGN SERVICES

(Part-FPD)

SUBPART A – ADDITIONAL ORGANISATION REQUIREMENTS FOR PROVIDERS OF FLIGHT PROCEDURE DESIGN SERVICES (FPD.OR)

SECTION 1 – GENERAL REQUIREMENTS

FPD.OR.100 Flight procedure design (FPD) services

• (a) A flight procedure design services provider shall perform design, documentation and validation of flight procedure(s) subject, if necessary, to approval by the competent authority thereof before being deployed and used. In this context, the aeronautical data and aeronautical information used by the FPD provider shall meet the requirements of accuracy, resolution, and integrity as specified in the aeronautical data catalogue in accordance with Appendix 1 to Annex III (Part-ATM/ANS.OR).

• (b) If aeronautical data for the design of flight procedures is not provided by an authoritative source or does not meet the applicable data quality requirements (DQRs), such aeronautical data may be obtained from other sources by the FPD provider. In this context, such aeronautical data shall be validated by the FPD provider intending to use it.

FPD.OR.105 Management system

In addition to point ATM/ANS.OR.B.005 of Annex III, the FPD provider shall establish and maintain a management system that includes control procedures for:

• (a) data acquisition;

• (b) flight procedure design in accordance with design criteria as set out in point FPD.TR.100;

• (c) flight procedure design documentation;

• (d) stakeholders consultation;

• (e) ground validation and, when appropriate, flight validation of flight procedure;

• (f) identification of tools, including configuration management and tools qualification, as necessary; and

• (g) maintenance and periodic review of the flight procedure(s), as applicable.

FPD.OR.110 Record-keeping

In addition to point ATM/ANS.OR.B.030 of Annex III, the FPD provider shall include in its record-keeping system the elements indicated in point FPD.OR.105 of this Annex.

FPD.OR.115 Technical and operational competence and capability

• (a) In addition to point ATM/ANS.OR.B.005(a)(6) of Annex III, the FPD provider shall ensure that its flight procedure designers:
• (1) have successfully completed a training course that provides competency in flight procedure design;
• (2) are suitably experienced to successfully apply the theoretical knowledge; and
• (3) successfully complete continuation training.

• (b) When flight validation is deemed necessary to be performed, the FPD provider shall ensure that it is undertaken by a competent pilot.

• (c) In addition to point ATM/ANS.OR.B.030 of Annex III, the FPD provider shall maintain records of all the training as well as any design activity completed by the employed flight procedure designers and make such records available on request:
• (1) to the flight procedure designers concerned; and
• (2) in agreement with the flight procedure designers, to the new employer when a flight procedure designer is employed by a new entity.

FPD.OR.120 Required interfaces

• (a) When obtaining the aeronautical data and aeronautical information in accordance with point FPD.OR.100, the FPD provider shall ensure the necessary formal arrangements are established, as applicable, with:
• (1) aeronautical data sources;
• (2) other service providers;
• (3) aerodrome operators; and
• (4) aircraft operators.

• (b) To ensure that the requests for flight procedure design are clearly defined and subject to review, the FPD service provider shall establish the necessary formal arrangements with the next intended user.

SUBPART B – TECHNICAL REQUIREMENTS FOR PROVIDERS OF FLIGHT PROCEDURE DESIGN SERVICES (FPD.TR)

SECTION 1 – GENERAL REQUIREMENTS

FPD.TR.100 Flight procedure design requirements

The flight procedures shall be designed by flight procedure design services provider in compliance with the requirements laid down in Appendix 1 and with the design criteria as determined by the competent authority, so as to ensure safe aircraft operations. The design criteria shall permit the establishment of appropriate obstacle clearance for flight procedures, where required.

FPD.TR.105 Coordinates and aeronautical data

• (a) In addition to point ATM/ANS.OR.A.090 of Annex III, geographical coordinates indicating latitude and longitude shall be determined and reported to the aeronautical information services provider(s) (AIS provider(s)) in terms of the World Geodetic System – 1984 (WGS-84) geodetic reference datum or equivalent.

• (b) The order of accuracy of the field work and the determinations and calculations derived therefrom shall be such that the resulting operational navigation data for the phases of flight are within the maximum deviations with respect to an appropriate reference frame, as specified in Appendix 1 to Annex III (Part-ATM/ANS.OR).

Appendix 1

REQUIREMENTS FOR AIRSPACE STRUCTURES AND FLIGHT PROCEDURES CONTAINED THEREIN

SECTION I

Specifications for flight information regions, control areas, control zones and flight information zones

• (a) FLIGHT INFORMATION REGIONS Flight information regions as defined in point 23 of Article 2 to Regulation (EC) No 549/2004 shall:
• (1) cover the whole of the air route structure to be served by such regions; and
• (2) include all airspace within its horizontal limits, except when limited by an upper flight information region. Member States shall retain their responsibilities towards the ICAO within the geographical limits of the flight information regions entrusted to them by the ICAO on the date of entry into force of this Regulation.

• (b) CONTROL AREAS
• (1) Control areas shall be delineated so as to encompass sufficient airspace to contain the flight paths of those instrument flight rules (IFR) flights or portions thereof to which the applicable parts of the air traffic control (ATC) service are provided, taking into account the capabilities of the navigation aids normally used in that area.
• (2) A lower limit of a control area shall be established at a height above the ground or water of not less than 200 m (700 ft), unless otherwise prescribed by the competent authority.
• (3) An upper limit of a control area shall be established when either:
• (i) ATC service will not be provided above such upper limit; or
• (ii) the control area is situated below an upper control area, in which case, the upper limit shall coincide with the lower limit of the upper control area.

• (c) CONTROL ZONES
• (1) The horizontal limits of a control zone shall encompass at least those portions of the airspace, which are not within control areas that contain the paths of IFR flights arriving at and departing from aerodromes to be used under instrument meteorological conditions (IMC).
• (2) If located within the horizontal limits of a control area, the control zone shall extend upwards from the surface of the earth to at least the lower limit of the control area.

• (d) FLIGHT INFORMATION ZONES
• (1) The horizontal limits of a flight information zone shall encompass at least those portions of the airspace, which are neither within control areas nor within control zone, that contain the paths of IFR and/or VFR flights arriving at and departing from aerodromes.
• (2) If located within the horizontal limits of a control area, the flight information zone shall extend upwards from the surface of the earth to at least the lower limit of the control area.

SECTION II

Identification of ATS routes other than standard departure and arrival routes

• (a) When ATS routes are established, a protected airspace along each ATS route and a safe spacing between adjacent ATS routes shall be provided.

• (b) ATS routes shall be identified through designators.

• (c) When identifying ATS routes other than standard departure and arrival routes, the designation system used shall:
• (1) permit the identification of any ATS route in a simple and unique manner;
• (2) avoid redundancy;
• (3) be usable by both ground and airborne automation systems;
• (4) permit utmost brevity in operational use; and
• (5) provide for a sufficient possibility of extension to cater for any future requirements without the need for fundamental changes;

• (d) Basic ATS route designators shall be assigned in accordance with the following principles:
• (1) the same basic designator shall be assigned to a main trunk route throughout its entire length, irrespective of terminal control areas, States or regions traversed;
• (2) where two or more trunk routes have a common segment, the segment in question shall be assigned each of the designators of the routes concerned, except where this would introduce difficulties in the provision of air traffic services (ATS), in which case, by common agreement, one designator only shall be assigned; and
• (3) a basic designator assigned to one route shall not be assigned to any other route.

SECTION III

Identification of standard departure and standard arrival routes and associated procedures

• (a) When identifying standard departure and standard arrival routes and associated procedures, it shall be ensured that:
• (1) the system of designators shall permit the identification of each route in a simple and unambiguous manner;
• (2) each route shall be identified by a plain language designator and a corresponding coded designator; and
• (3) in voice communications, the designators shall be easily recognisable as relating to a standard departure or standard arrival route and shall not create any difficulties in pronunciation for pilots and ATS personnel.

• (b) When composing designators for standard departure and standard arrival routes and associated procedures, the following shall be used:
• (1) a plain language designator;
• (2) a basic indicator;
• (3) a validity indicator that shall be a number from 1 to 9;
• (4) a route indicator that shall be one letter of the alphabet; the letters ‘I’ and ‘O’ shall not be used; and
• (5) a coded designator of a standard departure or standard arrival route, instrument or visual.

• (c) Assignment of designators
• (1) Each route shall be assigned a separate designator.
• (2) To distinguish between two or more routes that relate to the same significant point (and are therefore assigned the same basic indicator), a separate route indicator as described in point (b)(4) shall be assigned to each route.

• (d) Assignment of validity indicators
• (1) A validity indicator shall be assigned to each route to identify the route that is currently in effect.
• (2) The first validity indicator to be assigned shall be the number ‘1’.
• (3) Whenever a route is amended, a new validity indicator, which consists of the next higher number, shall be assigned. The number ‘9’ shall be followed by the number ‘1’.

SECTION IV

Establishment and identification of significant points

• (a) Significant points shall be established for the purpose of defining an ATS route or flight procedure and/or in relation to the ATS requirements for information on the progress of aircraft in flight.

• (b) Significant points shall be identified by designators.

SECTION V

Minimum flight altitudes

Minimum flight altitudes shall be determined for each ATS route and control area and shall be provided for promulgation. These minimum flight altitudes shall provide a minimum obstacle clearance within the areas concerned.

SECTION VI

Identification and delineation of prohibited, restricted and danger areas

When prohibited areas, restricted areas or danger areas are established, upon initial establishment, they shall be given an identification, and full details shall be provided for promulgation.

ANNEX XII

SPECIFIC REQUIREMENTS FOR THE NETWORK MANAGER

(Part-NM)

TECHNICAL REQUIREMENTS FOR THE NETWORK MANAGER (NM.TR)

SECTION 1 — GENERAL REQUIREMENTS

NM.TR.100 Working methods and operating procedures for the Network Manager

The Network Manager shall be able to demonstrate that its working methods and operating procedures are compliant with Regulations (EU) No 255/2010 and (EU) No 2019/123.

SECTION 2 — Technical requirements for the execution of air traffic management network functions (network functions)

NM.TR.105 Allocation and use of Mode S interrogator codes