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 Text with EEA relevance

Type Implementing Regulation
Publication 2012-10-13
Last updated 2025-05-01
State In force
Department European Commission
Source EUR-Lex
articles 11
Reform history JSON API
  • (a) A flight plan shall include all information considered relevant by the competent authority as regards the following:
  • (1) aircraft identification;
  • (2) flight rules and type of flight;
  • (3) number and type(s) of aircraft and wake turbulence category;
  • (4) aircraft equipment and capabilities;
  • (5) departure aerodrome or operating site;
  • (6) estimated off-block date and time;
  • (7) cruising speed(s);
  • (8) cruising level(s);
  • (9) route to be followed;
  • (10) destination aerodrome or operating site and total estimated elapsed time;
  • (11) alternate aerodrome(s) or operating site(s);
  • (12) fuel/energy endurance;
  • (13) total number of persons on board;
  • (14) emergency and survival equipment, including ballistic parachute recovery system;
  • (15) other information.
  • (b) For flight plans submitted during flight, the departure aerodrome or operating site provided shall be the location from which supplementary information concerning the flight may be obtained, if required. Additionally, the information to be provided in lieu of the estimated off-block time shall be the time over the first point of the route to which the flight plan relates.
SERA.4010   Completion of a flight plan
  • (a) A flight plan shall contain information, as applicable, on relevant items listed in point SERA.4005(a)(1) to (11) regarding the whole route or the portion thereof for which the flight plan is submitted.
  • (b) Aircraft operators, flight plan originators and air traffic services units following the necessary instructions referred to in point SERA.4001(c)(1)(i) shall comply with the following:
  • (1) the instructions for completion of the flight plan form contained in Appendix 6;
  • (2) any constraints identified in relevant Aeronautical Information Publications (AIPs).
  • (c) Aircraft operators, or the agents that act on their behalf, which intend to operate within the single European sky airspace for a portion of or the entire route in accordance with IFR shall insert the appropriate indicator for the aircraft equipment available on board and its capabilities in accordance with Commission Implementing Regulation (EU) 2023/1770 ([^E0003]) in the relevant item in the flight plan as required in point SERA.4005(a)(4).
  • (d) Operators of aircraft not equipped in accordance with Implementing Regulation (EU) 2023/1770 which intend to operate within the single European sky airspace shall insert the appropriate indicator for the aircraft equipment available on board and its capabilities, and any potential exemptions in the relevant items in the flight plan as per points SERA.4005(a) (4) and SERA.4005(a) (15) respectively. The flight plan shall, in addition, contain information, as applicable, on all other items when so prescribed by the competent authority or when otherwise deemed necessary by the person submitting the flight plan.
SERA.4013   Acceptance of a flight plan
  • (a) The Network Manager, for the portion of the route operated in accordance with IFR, and the air traffic services reporting office shall take the necessary measures to ensure that when a flight plan is received, or when changes are made to it, it is:
  • (1) in compliance with the applicable format and data conventions;
  • (2) complete and, to the extent possible, accurate;
  • (3) if necessary, made acceptable to the air traffic services; and
  • (4) accepted, or the changes made to it are also accepted, and this is indicated to the originator of the flight plan.
  • (b) ATC units shall provide the Network Manager with any necessary changes of a flight plan affecting items related to the route or flight level as listed in point SERA.4005 (a) (1) to (10) that could affect the safe conduct of a flight, for flight plans and associated update messages previously received by them from the Network Manager. No other changes to, or cancellation of, a flight plan shall be made by an ATC unit in the pre-flight phase without coordination with the aircraft operator.
  • (c) The Network Manager shall communicate to all affected ATS units the accepted flight plan and any accepted pre-flight-phase changes made to the items listed in point SERA.4005 (a) (1) to (10) of the flight plan and associated update messages.
  • (d) The Network Manager shall communicate to the aircraft operator any necessary pre-flight-phase changes made to the flight plan affecting items listed in point SERA.4005 (a) (1) to (10) related to the route or flight level that could affect the safe conduct of a flight, for flight plans and associated update messages previously received.
  • (e) The originator of a flight plan, when not being the aircraft operator or the pilot, shall ensure that the conditions of acceptance of a flight plan and any necessary changes to these conditions as notified by the Network Manager for the portion of the flight operated in accordance with IFR, or by the air traffic services reporting offices, are made available to the aircraft operator or the pilot that has submitted the flight plan.
  • (f) The aircraft operator shall ensure that the conditions of acceptance of a flight plan and any necessary changes to it as notified by the Network Manager or by the air traffic services reporting office to the originator of the flight plan are incorporated into the planned flight operation and communicated to the pilot.
  • (g) The aircraft operator shall ensure prior to the operation of the flight that the content of the flight plan correctly reflects the operational intentions.
  • (h) The Network Manager shall process and distribute the information on the 8,33 kHz channel spacing capability received in the flight plans.
  • (i) Requirements laid down in points (a) to (h) shall not apply in the Single European Sky airspace that is not part of the ICAO EUR region.
SERA.4015   Changes to a flight plan
  • (a) All changes to a flight plan submitted for an IFR flight, or a VFR flight operated as a controlled flight, shall be reported:
  • (1) during the pre-flight phase, to the Network Manager for flights intended to operate in accordance with IFR for a portion of or the entire route, and to air traffic services reporting offices as soon as practicable;
  • (2) during the flight, subject to the provisions of point SERA.8020(b), to the appropriate air traffic services unit. For other VFR flights, significant changes to a flight plan shall be reported as soon as practicable to the appropriate air traffic services unit.
  • (b) Information submitted prior to departure regarding fuel or energy endurance or total number of persons carried on board, if incorrect at time of departure, constitutes a significant change to the flight plan and as such shall be reported.
  • (c) In the case of a change in the aircraft equipment and its capability status for a flight, aircraft operators, or the agents that act on their behalf, shall send a modification message to the Network Manager or the air traffic services reporting offices with the appropriate indicator inserted in the relevant item of the flight plan form.
  • (d) Information submitted prior to departure regarding fuel endurance or total number of persons carried on board, if incorrect at the time of departure, constitutes a significant change to the flight plan and, as such, shall be reported.
  • (e) Requirements laid down in points (a) to (d) shall not apply in Single European Sky airspace that is not part of the ICAO EUR region.
SERA.4020   Closing a flight plan
  • (a)An arrival report shall be made in person, by radiotelephony, via data link or by other means as prescribed by the competent authority at the earliest possible moment after landing, to the appropriate air traffic services unit at the arrival aerodrome, by any flight for which a flight plan has been submitted covering the entire flight or the remaining portion of a flight to the destination aerodrome.
  • (1) Submission of an arrival report is not required after landing on an aerodrome where air traffic services are provided on condition that radio communication or visual signals indicate that the landing has been observed.
  • (b)When a flight plan has been submitted only in respect of a portion of a flight, other than the remaining portion of a flight to destination, it shall, when required, be closed by an appropriate report to the relevant air traffic services unit.
  • (c)When no air traffic services unit exists at the arrival aerodrome or operating site, the arrival report, when required, shall be made as soon as practicable after landing and by the quickest means available to the nearest air traffic services unit.
  • (d)When communication facilities at the arrival aerodrome or operating site are known to be inadequate and alternate arrangements for the handling of arrival reports on the ground are not available, the following action shall be taken. Immediately prior to landing the aircraft shall, if practicable, transmit to the appropriate air traffic services unit, a message comparable to an arrival report, where such a report is required. Normally, this transmission shall be made to the aeronautical station serving the air traffic services unit in charge of the flight information region in which the aircraft is operated.
  • (e)Arrival reports made by aircraft shall contain the following elements of information:
  • (1) aircraft identification;
  • (2) departure aerodrome or operating site;
  • (3) destination aerodrome or operating site (only in the case of a diversionary landing);
  • (4) arrival aerodrome or operating site;
  • (5) time of arrival.

SECTION 5

Visual meteorological conditions, visual flight rules, special VFR and instrument flight rules

SERA.5001   VMC visibility and distance from cloud minima

VMC visibility and distance from cloud minima are contained in Table S5-1.

Table S5-1 [^E0004] Table S5-1 [^E0004] Table S5-1 [^E0004] Table S5-1 [^E0004]
Altitude band Airspace class Flight visibility Distance from cloud
At and above 3 050 m (10 000 ft) AMSL A [^E0005] B C D E F G 8 km 1 500 m horizontally 300 m (1 000 ft) vertically
Below 3 050 m (10 000 ft) AMSL and above 900 m (3 000 ft) AMSL, or above 300 m (1 000 ft) above terrain, whichever is the higher A [^E0005] B C D E F G 5 km 1 500 m horizontally 300 m (1 000 ft) vertically
At and below 900 m (3 000 ft) AMSL, or 300 m (1 000 ft) above terrain, whichever is the higher A [^E0005] B C D E 5 km 1 500 m horizontally 300 m (1 000 ft) vertically
At and below 900 m (3 000 ft) AMSL, or 300 m (1 000 ft) above terrain, whichever is the higher F G 5 km [^E0006] Clear of cloud and with the surface in sight

When the height of the transition altitude is lower than 3 050 m (10 000 ft) AMSL, FL 100 shall be used in lieu of 10 000 ft.

The VMC minima in Class A airspace are included for guidance to pilots and do not imply acceptance of VFR flights in Class A airspace.

When so prescribed by the competent authority: (a) flight visibilities reduced to not less than 1 500 m may be permitted for flights operating: (1) at speeds of 140 kts IAS or less to give adequate opportunity to observe other traffic or any obstacles in time to avoid collision; or (2) in circumstances in which the probability of encounters with other traffic would normally be low, e.g. in areas of low volume traffic and for aerial work at low levels; (b) helicopters may be permitted to operate in less than 1 500 m but not less than 800 m flight visibility, if manoeuvred at a speed that will give adequate opportunity to observe other traffic or any obstacles in time to avoid collision.

SERA.5005   Visual flight rules
  • (a)Except when operating as a special VFR flight, VFR flights shall be conducted so that the aircraft is flown in conditions of visibility and distance from clouds equal to or greater than those specified in Table S5-1.
  • (b) Except when a clearance is obtained from an air traffic control unit, VFR flights shall not 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 ceiling is less than 450 m (1 500 ft); or
  • (2) the ground visibility is less than 5 km.
  • (c)When so prescribed by the competent authority, VFR flights at night may be permitted under the following conditions:
  • (1) if leaving the vicinity of an aerodrome, a flight plan shall be submitted in accordance with SERA.4001(b)(6);
  • (2) flights shall establish and maintain two-way radio communication on the appropriate ATS communication channel, when available;
  • (3) the VMC visibility and distance from cloud minima as specified in Table S5-1 shall apply except that:
  • (i) the ceiling shall not be less than 450 m (1 500 ft);
  • (ii) the reduced flight visibility provisions specified in Table S5-1(a) and (b) shall not apply;
  • (iii) in airspace classes B, C, D, E, F and G, at and below 900 m (3 000 ft) AMSL or 300 m (1 000 ft) above terrain, whichever is the higher, the pilot shall maintain continuous sight of the surface; and —————
  • (v) for mountainous area, higher VMC visibility and distance from cloud minima may be prescribed by the competent authority;
  • (5) except when necessary for take-off or landing, or except when specifically authorised by the competent authority, a VFR flight at night shall be flown at a level which is not below the minimum flight altitude established by the State whose territory is overflown, or, where no such minimum flight altitude has been established:
  • (i) over high terrain or in mountainous areas, at a level which is at least 600 m (2 000 ft) above the highest obstacle located within 8 km of the estimated position of the aircraft;
  • (ii) elsewhere than as specified in i), at a level which is at least 300 m (1 000 ft) above the highest obstacle located within 8 km of the estimated position of the aircraft.
  • (d)VFR flights shall not be operated:
  • (1) at transonic and supersonic speeds unless authorised by the competent authority;
  • (2) above FL 195. Exceptions to this requirement are the following:
  • (i) an airspace reservation has been established, where practical, by the Member States, in which VFR flights may be allowed; or
  • (ii) airspace up to and including flight level 285, when VFR traffic in that airspace has been authorised by the responsible ATS unit in accordance with the authorisation procedures established by the Member States and published in the relevant aeronautical information publication.
  • (e)Authorisation for VFR flights to operate above FL 285 shall not be granted where a vertical separation minimum of 300 m (1 000 ft) is applied above FL 290.
  • (f)Except when necessary for take-off or landing, or except by permission from the competent authority, a VFR flight shall not be flown:
  • (1) over the congested areas of cities, towns or settlements or over an open-air assembly of persons at a height less than 300 m (1 000 ft) above the highest obstacle within a radius of 600 m from the aircraft;
  • (2) elsewhere than as specified in (1), at a height less than 150 m (500 ft) above the ground or water, or 150 m (500 ft) above the highest obstacle within a radius of 150 m (500 ft) from the aircraft.
  • (g)Except where otherwise indicated in air traffic control clearances or specified by the competent authority, VFR flights in level cruising flight when operated above 900 m (3 000 ft) from the ground or water, or a higher datum as specified by the competent authority, shall be conducted at a cruising level appropriate to the track as specified in the table of cruising levels in Appendix 3.
  • (h)VFR flights shall comply with the provisions of Section 8:
  • (1) when operated within Classes B, C and D airspace;
  • (2) when forming part of aerodrome traffic at controlled aerodromes; or
  • (3) when operated as special VFR flights.
  • (i)A VFR flight operating within or into areas or along routes designated by the competent authority, in accordance with SERA.4001(b)(3) or (4), shall maintain continuous air-ground voice communication watch on the appropriate communication channel of, and report its position as necessary to, the air traffic services unit providing flight information service.
  • (j)An aircraft operated in accordance with the visual flight rules which wishes to change to compliance with the instrument flight rules shall:
  • (1) if a flight plan was submitted, communicate the necessary changes to be effected to its current flight plan; or
  • (2) as required by SERA.4001(b), submit a flight plan to the appropriate air traffic services unit as soon as practicable and obtain a clearance prior to proceeding IFR when in controlled airspace.
SERA.5010   Special VFR in control zones

Special VFR flights may be authorised to operate within a control zone, subject to an ATC clearance. Except when otherwise permitted by the competent authority for helicopters in special cases such as, but not limited to, police, medical, search and rescue operations and firefighting flights, the following additional conditions shall apply:

  • (a) such special VFR flights may be conducted during day only, unless otherwise permitted by the competent authority;
  • (b) by the pilot:
  • (1) clear of cloud and with the surface in sight;
  • (2) the flight visibility is not less than 1 500 m or, for helicopters, not less than 800 m;
  • (3) 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
  • (c) an air traffic control unit shall not issue a special VFR clearance to aircraft to take off or land at an aerodrome within a control zone, or enter the aerodrome traffic circuit within a control zone, when the reported meteorological conditions at that aerodrome are below the following minima:
  • (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).
SERA.5015   Instrument flight rules (IFR) — Rules applicable to all IFR flights
(a) Aircraft equipment

Aircraft shall be equipped with suitable instruments and with navigation equipment appropriate to the route to be flown and in accordance with the applicable air operations legislation.

(b) Minimum levels

Except when necessary for take-off or landing, or except when specifically authorised by the competent authority, an IFR flight shall be flown at a level which is not below the minimum flight altitude established by the State whose territory is overflown, or, where no such minimum flight altitude has been established:

  • (1) over high terrain or in mountainous areas, at a level which is at least 600 m (2 000 ft) above the highest obstacle located within 8 km of the estimated position of the aircraft;
  • (2) elsewhere than as specified in (1), at a level which is at least 300 m (1 000 ft) above the highest obstacle located within 8 km of the estimated position of the aircraft.
(c) Change from IFR flight to VFR flight
  • (1)An aircraft electing to change the conduct of its flight from compliance with the instrument flight rules to compliance with the visual flight rules shall notify the appropriate air traffic services unit specifically that the IFR flight is cancelled and communicate thereto the changes to be made to its current flight plan.
  • (2)When an aircraft operating under the instrument flight rules is flown in or encounters visual meteorological conditions it shall not cancel its IFR flight unless it is anticipated, and intended, that the flight will be continued for a reasonable period of time in uninterrupted visual meteorological conditions.
  • (3)Change from IFR flight to VFR flight shall only be acceptable when a message initiated by the pilot-in-command containing the specific expression ‘CANCELLING MY IFR FLIGHT’, together with the changes, if any, to be made to the current flight plan, is received by an ATS unit. No invitation to change from IFR flight to VFR flight shall be made by ATS either directly or by inference.
SERA.5020   IFR — Rules applicable to IFR flights within controlled airspace
  • (a)IFR flights shall comply with the provisions of Section 8 when operated in controlled airspace.
  • (b)An IFR flight operating in cruising flight in controlled airspace shall be flown at a cruising level, or, if authorised by ATS unit to employ cruise climb techniques, between two levels or above a level, selected from the table of cruising levels in Appendix 3, except that the correlation of levels to track prescribed therein shall not apply whenever otherwise indicated in air traffic control clearances or specified by the competent authority in aeronautical information publications.
SERA.5025   IFR — Rules Applicable to IFR flights outside controlled airspace
(a) Cruising levels

An IFR flight operating in level cruising flight outside of controlled airspace shall be flown at a cruising level appropriate to its track as specified in the table of cruising levels in Appendix 3, except when otherwise specified by the competent authority for flight at or below 900 m (3 000 ft) above mean sea level.

(b) Communications

An IFR flight operating outside controlled airspace but within or into areas, or along routes, designated by the competent authority in accordance with SERA.4001(b)(3) or (4) shall maintain an air-ground voice communication watch on the appropriate communication channel and establish two-way communication, as necessary, with the air traffic services unit providing flight information service.

(c) Position reports

An IFR flight operating outside controlled airspace and required by the competent authority to maintain an air-ground voice communication watch on the appropriate communication channel and establish two-way communication, as necessary, with the air traffic services unit providing flight information service, shall report position, as specified in SERA.8025 for controlled flights.

SECTION 6

Airspace classification

SERA.6001   Classification of airspaces
  • (a) Member States shall designate airspace in accordance with the following airspace classification and in accordance with Appendix 4:
  • (1) Class A. IFR flights only are permitted. All flights are provided with air traffic control service and are separated from each other. Continuous air- ground voice communications are required for all flights. All flights shall be subject to ATC clearance.
  • (2) Class B. IFR and VFR flights are permitted. All flights are provided with air traffic control service and are separated from each other. Continuous air- ground voice communications are required for all flights. All flights shall be subject to ATC clearance.
  • (3) Class C. IFR and VFR flights are permitted. All flights are provided with air traffic control service and IFR flights are separated from other IFR flights and from VFR flights. VFR flights are separated from IFR flights and receive traffic information in respect of other VFR flights and traffic avoidance advice on request. Continuous air-ground voice communications are required for all flights. For VFR flights a speed limitation of 250 kts indicated airspeed (IAS) applies below 3 050 m (10 000 ft) AMSL, except where approved by the competent authority for aircraft types, which for technical or safety reasons, cannot maintain this speed. All flights shall be subject to ATC clearance.
  • (4) Class D. IFR and VFR flights are permitted and all flights are provided with air traffic control service. IFR flights are separated from other IFR flights, receive traffic information in respect of VFR flights and traffic avoidance advice on request. VFR flights receive traffic information in respect of all other flights and traffic avoidance advice on request. Continuous air-ground voice communications are required for all flights and a speed limitation of 250 kts IAS applies to all flights below 3 050 m (10 000 ft) AMSL, except where approved by the competent authority for aircraft types, which for technical or safety reasons, cannot maintain this speed. All flights shall be subject to ATC clearance.
  • (5) Class E. IFR and VFR flights are permitted. IFR flights are provided with air traffic control service and are separated from other IFR flights. All flights receive traffic information, as far as is practical. Continuous air-ground voice communications are required for IFR flights. A speed limitation of 250 kts IAS applies to all flights below 3 050 m (10 000 ft) AMSL, except where approved by the competent authority for aircraft types, which for technical or safety reasons cannot maintain this speed. All IFR flights shall be subject to ATC clearance. Class E shall not be used for control zones.
  • (6) Class F. IFR and VFR flights are permitted. All participating IFR flights receive an air traffic advisory service and all flights receive flight information service if requested. Continuous air-ground voice communications are required for IFR flights participating in the advisory service and all IFR flights shall be capable of establishing air-ground voice communications. A speed limitation of 250 kts IAS applies to all flights below 3 050 m (10 000 ft) AMSL, except where approved by the competent authority for aircraft types, which for technical or safety reasons cannot maintain this speed. ATC clearance is not required.
  • (7) Class G. IFR and VFR flights are permitted and receive flight information service if requested. All IFR flights shall be capable of establishing air- ground voice communications. A speed limitation of 250 kts IAS applies to all flights below 3 050 m (10 000 ft) AMSL, except where approved by the competent authority for aircraft types, which for technical or safety reasons cannot maintain this speed. ATC clearance is not required.
  • (8) Implementation of Class F shall be considered as a temporary measure until such time as it can be replaced by an alternative classification.
  • (b) The designation of the airspace classification shall be appropriate to the needs of the Member States, except that all airspace above FL 195 shall be classified as Class C airspace.
SERA.6005   Requirements for communications, SSR transponder and electronic conspicuity in U-space airspace
  • (a) Radio mandatory zone (RMZ)
  • (1) VFR flights operating in parts of Classes E, F or G airspace and IFR flights operating in parts of Classes F or G airspace designated as a radio mandatory zone (RMZ) by the competent authority shall maintain continuous air-ground voice communication watch and establish two-way communication, as necessary, on the appropriate communication channel, unless in compliance with alternative provisions prescribed for that particular airspace by the ANSP.
  • (2) Before entering a radio mandatory zone, an initial call containing the designation of the station being called, call sign, type of aircraft, position, level, the intentions of the flight and other information as prescribed by the competent authority, shall be made by pilots on the appropriate communication channel.
  • (b) Transponder mandatory zone (TMZ) All flights operating in airspace designated by the competent authority as a transponder mandatory zone (TMZ) shall carry and operate SSR transponders capable of operating on Modes A and C or on Mode S, unless in compliance with alternative provisions prescribed for that particular airspace by the ANSP.
  • (c) U-space airspace Manned aircraft operating in airspace designated by the competent authority as a U-space airspace, and not provided with an air traffic control service by the ANSP, shall continuously make themselves electronically conspicuous to the U-space service providers.
  • (d) Airspaces designated as radio mandatory zone, transponder mandatory zone or U-space airspace shall be duly promulgated in the aeronautical information publications.

SECTION 7

Air traffic services

SERA.7001   General — Objectives of the air traffic services

The objectives of the air traffic services shall be to:

  • (a) prevent collisions between aircraft;
  • (b) prevent collisions between aircraft on the manoeuvring area and obstructions on that area;
  • (c) expedite and maintain an orderly flow of air traffic;
  • (d) provide advice and information useful for the safe and efficient conduct of flights;
  • (e) notify appropriate organisations regarding aircraft in need of search and rescue aid, and assist such organisations as required.
SERA.7002   Collision hazard information when ATS based on surveillance are provided
  • (a)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.
SERA.7005   Coordination between the aircraft operator and air traffic services
  • (a)Air traffic services units, in carrying out their objectives, shall have due regard for the requirements of the aircraft operators consequent on their obligations as specified in the relevant Union legislation on Air Operations, and, if so required by the aircraft operators, shall make available to them or their designated representatives such information as may be available to enable them or their designated representatives to carry out their responsibilities.
  • (b)When so requested by an aircraft operator, messages (including position reports) received by air traffic services units and relating to the operation of the aircraft for which operational control service is provided by that aircraft operator shall, so far as practicable, be made available immediately to the aircraft operator or a designated representative in accordance with locally agreed procedures.

SECTION 8

Air traffic control service

SERA.8001   Application

Air traffic control service shall be provided:

  • (a) to all IFR flights in airspace Classes A, B, C, D and E;
  • (b) to all VFR flights in airspace Classes B, C and D;
  • (c) to all special VFR flights;
  • (d) to all aerodrome traffic at controlled aerodromes.
SERA.8005   Operation of air traffic control service
  • (a)In order to provide air traffic control service, an air traffic control unit shall:
  • (1) be provided with information on the intended movement of each aircraft, or variations therefrom, and with current information on the actual progress of each aircraft;
  • (2) determine from the information received, the relative positions of known aircraft to each other;
  • (3) issue one or more of the following: clearances, instructions 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.
  • (b)Clearances issued by air traffic control units shall provide separation:
  • (1) between all flights in airspace Classes A and B;
  • (2) between IFR flights in airspace Classes C, D and E;
  • (3) between IFR flights and VFR flights in airspace Class C;
  • (4) between IFR flights and special VFR flights;
  • (5) between special VFR flights unless otherwise prescribed by the competent authority;
  • 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 b) 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 point ATS.TR.255 of Annex IV to Commission Implementing Regulation (EU) 2017/373 ([^E0007]), 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, except that the correlation of levels to track as prescribed therein shall not apply whenever otherwise indicated in appropriate aeronautical information publications or ATC clearances. The vertical separation minimum shall be a nominal 300 m (1 000 ft) up to and including FL 410 and a nominal 600 m (2 000 ft) above that level. Geometric height information shall not be used to establish vertical separation;
  • (2) horizontal separation, obtained by providing:
  • (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.
SERA.8010   Separation minima
  • (a)The selection of separation minima for application within a given portion of airspace shall be made by the ANSP responsible for the provision of air traffic services and approved by the competent authority concerned.
  • (b)For traffic that will pass from one into the other of neighbouring airspaces and for routes that are closer to the common boundary of the neighbouring airspaces than the separation minima applicable in the circumstances, the selection of separation minima shall be made in consultation between the ANSPs responsible for the provision of air traffic services in neighbouring airspace.
  • (c)Details of the selected separation minima and of their areas of application shall be notified:
  • (1) to the air traffic services units concerned; 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.
SERA.8012   Application of wake turbulence separation
  • (a) Air traffic control units shall apply wake turbulence separation minima to aircraft in the approach and departure phases of flight in any of the following circumstances:
  • (1) an aircraft is operating directly behind another aircraft at the same altitude or less than 300 m (1 000 ft) below it;
  • (2) both aircraft are using the same runway or parallel runways separated by less than 760 m (2 500 ft);
  • (3) an aircraft is crossing behind another aircraft at the same altitude or less than 300 m (1 000 ft) below it.
  • (b) Paragraph (a) shall not apply to arriving VFR flights and to arriving IFR flights executing visual approach when the aircraft has reported the preceding aircraft in sight and has been instructed to follow and maintain own separation from that aircraft. In those cases, the air traffic control unit shall issue caution for wake turbulence.
SERA.8015   Air traffic control clearances
  • (a) Air traffic control clearances shall be based solely on the following requirements for providing air traffic control service:
  • (1) Clearances shall be issued solely for expediting and separating air traffic and be based on known traffic conditions which affect safety in aircraft operation. Such traffic conditions include not only aircraft in the air and on the manoeuvring area over which control is being exercised, but also any vehicular traffic or other obstructions not permanently installed on the manoeuvring area in use.
  • (2) 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.
  • (b) Operation subject to clearance:
  • (1) An air traffic control clearance shall be obtained prior to operating a controlled flight, or a portion of a flight as a controlled flight. Such clearance shall be requested through the submission of a flight plan to an air traffic control unit.
  • (2) When a flight plan specifies that the initial portion of a flight will be uncontrolled, and that the subsequent portion of the flight will be subject to air traffic control service, the flight crew shall obtain the clearance from the appropriate air traffic control unit prior to entering the area where controlled flight will be commenced.
  • (3) When a flight plan specifies that the initial portion of a flight will be subject to air traffic control service, and that the subsequent portion will be uncontrolled, the aircraft shall normally be cleared to the point at which the controlled flight terminates.
  • (4) Potential reclearance in flight. If, prior to departure, it is anticipated that, depending on fuel/energy endurance and subject to reclearance in flight, a decision may be taken to proceed to a revised destination aerodrome, the appropriate air traffic control units shall be so notified by the insertion in the flight plan of information concerning the revised route (where known) and the revised destination.
  • (5) Whenever an aircraft has requested a clearance involving priority, a report explaining the necessity for such priority shall be submitted, if requested by the appropriate air traffic control unit.
  • (6) Potential reclearance in flight. If, prior to departure, it is anticipated that, depending on fuel endurance and subject to reclearance in flight, a decision may be taken to proceed to a revised destination aerodrome, the appropriate air traffic control units shall be so notified by the insertion in the flight plan of information concerning the revised route (where known) and the revised destination.
  • (7) An aircraft operated on a controlled aerodrome shall not taxi on the manoeuvring area without clearance from the aerodrome control tower and shall comply with any instructions given by that unit.
  • (8) When vectoring or assigning a direct routing not included in the flight plan, which takes an IFR flight off published ATS route or instrument procedure, an air traffic controller providing ATS surveillance service shall issue clearances such that the prescribed obstacle clearance exists at all times until the aircraft reaches the point where the pilot re-joins the flight plan route or joins a published ATS route or instrument procedure.
  • (c) Clearances for transonic flight
  • (1)The air traffic control clearance relating to the transonic acceleration phase of a supersonic flight shall extend at least to the end of that phase.
  • (2)The air traffic control 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.
  • (d) Contents of clearances

An air traffic control clearance shall indicate:

  • (1) aircraft identification as shown in the flight plan;
  • (2) clearance limit;
  • (3) route of flight:
  • (i) the route of flight shall be detailed in each clearance when deemed necessary;
  • (ii) the phrase ‘cleared flight planned route’ shall not be used when granting a re-clearance;
  • (4) level or levels of flight for the entire route or part thereof and changes of levels if required;
  • (5) any necessary instructions or information on other matters, such as ATFM departure slot if applicable, approach or departure manoeuvres, communications and the time of expiry of the clearance.
  • (e) Read back of clearances, instructions and safety-related information
  • (1)The flight crew shall read back to the air traffic controller safety-related parts of ATC clearances and instructions which are transmitted by voice. The following items shall always be read back:
  • (i) ATC route clearances;
  • (ii) clearances and instructions to enter, land on, take off from, hold short of, cross, taxi and backtrack on any runway; and
  • (iii) runway-in-use, altimeter settings, SSR codes, newly assigned communication channels, level instructions, heading and speed instructions; and
  • (iv) transition levels, whether issued by the controller or contained in ATIS broadcasts.
  • (2)Other clearances or instructions, including conditional clearances and taxi instructions, shall be read back or acknowledged in a manner to clearly indicate that they have been understood and will be complied with.
  • (3)The controller shall listen to the read-back to ascertain that the clearance or instruction has been correctly acknowledged by the flight crew and shall take immediate action to correct any discrepancies revealed by the read-back.
  • (4)Voice read-back of CPDLC messages shall not be required, unless otherwise specified by the ANSP.
  • (5)Vehicle drivers operating or intending to operate on the manoeuvring area shall read back to the air traffic controller safety-related parts of instructions which are transmitted by voice, e.g. instructions to enter, hold short of, cross and operate on any operational runway or taxiway.
  • (6)The controller shall listen to the read-back to ascertain that the instruction has been correctly acknowledged by the vehicle driver and shall take immediate action to correct any discrepancies revealed by the read-back.
  • (ea) 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.
  • (eb) Clearance related to altimetry
  • (1) For flights in areas where a transition altitude is established, the vertical position of the aircraft shall, except as provided for in (5) 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.
  • (2) The flight crew shall be provided with the transition level in due time prior to reaching it during descent.
  • (3) Except when it is known that the aircraft has already received the information in a directed transmission, an QNH altimeter setting shall be included in:
  • (i) the descent clearance, when first cleared to an altitude below the transition level;
  • (ii) the approach clearance or the clearance to enter the traffic circuit;
  • (iii) the taxi clearance for departing aircraft.
  • (4) A QFE altimeter setting shall be provided to aircraft on request or on a regular basis in accordance with local arrangements.
  • (5) When an aircraft has been given clearance to land or where an aircraft has been informed that the runway is available for landing at AFIS aerodromes and that aircraft is completing its approach using atmospheric pressure at aerodrome elevation (QFE), the vertical position of that 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:
  • (i) for instrument runways if the threshold is 2 m (7 ft) or more below the aerodrome elevation; and
  • (ii) for precision approach runways.
  • (ec) 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 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.
  • (f) Coordination of clearances
  • (1)An air traffic control clearance shall be coordinated between air traffic control units to cover the entire route of an aircraft or a specified portion thereof as described in provisions (2) to (6).
  • (2)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.
  • (3)When coordination as in (2) 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.
  • (4)When prescribed by the ATS unit, aircraft shall contact a downstream air traffic control unit, for the purpose of receiving a downstream clearance prior to the transfer of control point.
  • (i) Aircraft shall maintain the necessary two-way communication with the current air traffic control unit whilst obtaining a downstream clearance.
  • (ii) A clearance issued as a downstream clearance shall be clearly identifiable as such to the pilot.
  • (iii) Unless coordinated, downstream clearances shall not affect the aircraft’s original flight profile in any airspace, other than that of the air traffic control unit responsible for the delivery of the downstream clearance.
  • (5)When an aircraft intends to depart from an aerodrome within a control area to enter another control area within a period of thirty minutes, or such other specific period of time as has been agreed between the area control centres concerned, coordination with the subsequent area control centre shall be effected prior to issuance of the departure clearance.
  • (6)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.
SERA.8020   Adherence to flight plan
  • (a)Except as provided for in (b) and (d) an aircraft shall adhere to the current flight plan or the applicable portion of a current flight plan submitted for a controlled flight unless a request for a change has been made and clearance obtained from the appropriate air traffic control unit, or unless an emergency situation arises which necessitates immediate action by the aircraft, in which event as soon as circumstances permit, after such emergency authority is exercised, the appropriate air traffic services unit shall be notified of the action taken and that this action has been taken under emergency authority.
  • (1) Unless otherwise authorised by the competent authority, or directed by the appropriate air traffic control unit, controlled flights shall, in so far as practicable:
  • (i) when on an established ATS route, operate along the defined centre line of that route; or
  • (ii) when on any other route, operate directly between the navigation facilities and/or points defining that route.
  • (2) Unless otherwise authorised by the competent authority, or directed by the appropriate air traffic control unit, an aircraft operating along an ATS route segment defined by reference to very high frequency omnidirectional radio ranges shall change over for its primary navigation guidance from the facility behind the aircraft to that ahead of it at, or as close as operationally feasible to, the changeover point, where established.
  • (3) Deviation from the requirements in point (1) shall be notified to the appropriate ATS unit.
  • (b) Deviations from the current flight plan. In the event that a controlled flight inadvertently deviates from its current flight plan, the following action shall be taken:
  • (1) Deviation from track: if the aircraft is off track, action shall be taken forthwith to adjust the heading of the aircraft to regain track as soon as practicable.
  • (2) Deviation from the air traffic control assigned Mach number/indicated airspeed: the appropriate air traffic services unit shall be informed immediately.
  • (3) Deviation from Mach number/true airspeed: if the sustained Mach number/true airspeed at cruising level varies by plus or minus Mach 0,02 or more, or plus or minus 19 km/h (10 kt) true airspeed or more from the current flight plan, the appropriate air traffic services unit shall be so informed.
  • (4) Change in time estimate: except where ADS-C is activated and serviceable in airspace where ADS-C services are provided, if the time estimate for the next applicable reporting point, flight information region boundary or destination aerodrome, whichever comes first, changes in excess of 2 minutes from that previously notified to air traffic services, or such other period of time as is prescribed by the competent authority, the flight crew shall notify the appropriate air traffic services unit as soon as possible.
  • (5) Additionally, when an ADS-C agreement is in place, the air traffic services unit shall be informed automatically via data link whenever changes occur beyond the threshold values stipulated by the ADS-C event contract.
  • (c) Intended changes. Requests for flight plan changes shall include information as indicated hereunder:
  • (1) Change of cruising level: aircraft identification; requested new cruising level and cruising speed at this level, revised time estimates (when applicable) at subsequent flight information region boundaries.
  • (2) Change of route:
  • (i) Destination unchanged: aircraft identification; flight rules; description of new route of flight including related flight plan data beginning with the position from which requested change of route is to commence; revised time estimates; any other pertinent information.
  • (ii) Destination changed: aircraft identification; flight rules; description of revised route of flight to revised destination aerodrome including related flight plan data, beginning with the position from which requested change of route is to commence; revised time estimates; alternate aerodrome(s); any other pertinent information.
  • (3) Change of Mach number/true airspeed: aircraft identification; requested Mach number/true airspeed.
  • (d) Weather deterioration below the VMC. When it becomes evident that flight in VMC in accordance with its current flight plan will not be practicable, a VFR flight operated as a controlled flight shall:
  • (1) request an amended clearance enabling the aircraft to continue in VMC to destination or to an alternative aerodrome or operating site, or to leave the airspace within which an ATC clearance is required; or
  • (2) if no clearance in accordance with point (1) can be obtained, continue to operate in VMC and notify the appropriate ATC unit of the action being taken either to leave the airspace concerned or to land at the nearest suitable aerodrome or operating site; or
  • (3) if operated within a control zone, request authorisation to operate as a special VFR flight; or
  • (4) request clearance to operate in accordance with the instrument flight rules.
SERA.8025   Position reports
  • (a)Unless exempted by the competent authority or by the appropriate air traffic services unit under conditions specified by that authority, a controlled flight shall report to the appropriate air traffic services unit, as soon as possible, the time and level of passing each designated compulsory reporting point, together with any other required information. Position reports shall similarly be made in relation to additional points when requested by the appropriate air traffic services unit. In the absence of designated reporting points, position reports shall be made at intervals prescribed by the competent authority or specified by the appropriate air traffic services unit.
  • (1) Controlled flights providing position information to the appropriate air traffic services unit via data link communications shall only provide voice position reports when requested.
  • (2) When a controlled flight has been exempted from the requirement to report at compulsory reporting points, pilots shall, unless automated position reporting is in effect, resume voice or CPDLC position reporting:
  • (i) when so instructed;
  • (ii) when advised that the ATS surveillance service has been terminated; or
  • (iii) when advised that the ATS surveillance identification is lost.
  • (b)With due regard to requirements in SERA.14065 for communications change over, the position report shall contain the following elements:
  • (1) aircraft identification;
  • (2) position;
  • (3) time;
  • (4) speed, if assigned by ATC; and
  • (5) other elements as instructed by ATC.
  • (c)The elements described in point (b) shall be reported as described in point 2 of Point A of Appendix 5.
SERA.8030   Termination of control

A controlled flight shall, except when landing at a controlled aerodrome, advise the appropriate ATC unit as soon as it ceases to be subject to air traffic control service.

SERA.8035   Communications
  • (a)An aircraft operated as a controlled flight shall maintain continuous air-ground voice communication watch on the appropriate communication channel of, and establish two-way communication as necessary with, the appropriate air traffic control unit, except as may be prescribed by the relevant ANSP in respect of aircraft forming part of aerodrome traffic at a controlled aerodrome.
  • (1) The requirement for an aircraft to maintain an air-ground voice communication watch shall remain in effect when CPDLC has been established.
  • (b)If a communication failure precludes compliance with point (a), the procedures on communication failures shall be followed, as specified in SERA.14083.

SECTION 9

Flight information service

SERA.9001   Application
  • (a)Flight information service shall be provided by the appropriate air traffic services units to all aircraft which are likely to be affected by the information and which are:
  • (1) provided with air traffic control service; or
  • (2) otherwise known to the relevant air traffic services units.
  • (b)The reception of flight information service does not relieve the pilot-in-command of an aircraft of any responsibilities and the pilot-in-command shall make the final decision regarding any suggested alteration of flight plan.
  • (c)Where air traffic services units provide both flight information service and air traffic control service, the provision of air traffic control service shall have precedence over the provision of flight information service whenever the provision of air traffic control service so requires.
SERA.9005   Scope of flight information service
  • (a)Flight information service shall include the provision of pertinent:
  • (1) SIGMET and AIRMET information;
  • (2) information concerning pre-eruption volcanic activity, volcanic eruptions and volcanic ash clouds;
  • (3) information concerning the release into the atmosphere of radioactive materials or toxic chemicals;
  • (4) information on changes in the availability of radio navigation services;
  • (5) information on changes in condition of aerodromes and associated facilities, including information on the state of the aerodrome movement areas when they are affected by snow, ice or significant depth of water;
  • (6) information on unmanned free balloons;
  • (7) information on abnormal aircraft configuration and condition;
  • (7a) information on unmanned aircraft;
  • (8) any other information likely to affect safety.
  • (b)Flight information service provided to flights shall include, in addition to that outlined in (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; and
  • (4) messages, including clearances, received from other air traffic services units to relay to aircraft.
  • (c)Flight information service provided to VFR flights shall include, in addition to that outlined in (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.
  • (d)AFIS provided to flights shall include, in addition to relevant items outlined in points (a) and (b), the provision of the information concerning:
  • (1) collision hazards with aircraft, vehicles and persons operating on the manoeuvring area;
  • (2) the runway-in-use.
SERA.9010   Automatic terminal information service (ATIS)
(a) Use of the ATIS messages in directed request/reply transmissions
  • (1)When requested by the pilot, the applicable ATIS message(s) shall be transmitted by the appropriate air traffic services unit.
  • (2)Whenever Voice-ATIS and/or D-ATIS is provided:
  • (i) aircraft shall acknowledge receipt of the information upon establishing communication with the ATS unit providing approach control service, the aerodrome control tower or Aerodrome Flight Information Service (AFIS), as appropriate; and
  • (ii) the appropriate air traffic services unit shall, when replying to an aircraft acknowledging receipt of an ATIS message 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.
  • (3)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 (2).
  • (4)If an aircraft acknowledges receipt of an ATIS that is no longer current, the ATS unit shall without delay take one of the following actions:
  • (i) communicate to the aircraft any element of information which has to be updated;
  • (ii) instruct the aircraft to obtain the current ATIS information.
(b) ATIS for arriving and departing aircraft

ATIS messages containing both arrival and departure information shall contain the following elements of information in the order listed:

  • (1) name of aerodrome;
  • (2) arrival and/or departure indicator;
  • (3) contract type, if communication is via D-ATIS;
  • (4) designator;
  • (5) time of observation, if appropriate;
  • (6) type of approach(es) to be expected;
  • (7) the runway(s) in use; status of arresting system constituting a potential hazard, if any;
  • (8) runway surface conditions;
  • (9) holding delay, if appropriate;
  • (10) transition level, if applicable;
  • (11) other essential operational information;
  • (12) surface wind direction (in degrees magnetic) and speed, including significant variations and, if surface wind sensors related specifically to the sections of runway(s) in use are available and the information is required by aircraft operators, the indication of the runway and the section of the runway to which the information refers;
  • (13) visibility and, when applicable, RVR ([^E0008]) and, if visibility/RVR sensors related specifically to the sections of runway(s) in use are available and the information is required by operators, the indication of the runway and the section of the runway to which the information refers;
  • (14) present weather (5) ;
  • (15) 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 (5) ;
  • (16) air temperature;
  • (17) dew point temperature;
  • (18) altimeter setting(s);
  • (19) any available information on significant meteorological phenomena in the approach and climb-out areas including wind shear, and information on recent weather of operational significance;
  • (20) trend forecast, when available; and
  • (21) specific ATIS instructions.
(c) ATIS for arriving aircraft

ATIS messages containing arrival information only shall contain the following elements of information in the order listed:

  • (1) name of aerodrome;
  • (2) arrival indicator;
  • (3) contract type, if communication is via D-ATIS;
  • (4) designator;
  • (5) time of observation, if appropriate;
  • (6) type of approach(es) to be expected;
  • (7) main landing runway(s); status of arresting system constituting a potential hazard, if any;
  • (8) runway surface conditions;
  • (9) holding delay, if appropriate;
  • (10) transition level, if applicable;
  • (11) other essential operational information;
  • (12) surface wind direction (in degrees magnetic) and speed, including significant variations and, if surface wind sensors related specifically to the sections of runway(s) in use are available and the information is required by aircraft operators, the indication of the runway and the section of the runway to which the information refers;
  • (13) visibility and, when applicable, RVR (5)  and, if visibility/RVR sensors related specifically to the sections of runway(s) in use are available and the information is required by operators, the indication of the runway and the section of the runway to which the information refers;
  • (14) present weather (5) ;
  • (15) 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 (5) ;
  • (16) air temperature;
  • (17) dew point temperature;
  • (18) altimeter setting(s);
  • (19) any available information on significant meteorological phenomena in the approach area including wind shear, and information on recent weather of operational significance;
  • (20) trend forecast, when available; and
  • (21) specific ATIS instructions.
(d) ATIS for departing aircraft

ATIS messages containing departure information only shall contain the following elements of information in the order listed:

  • (1) name of aerodrome;
  • (2) departure indicator;
  • (3) contract type, if communication is via D-ATIS;
  • (4) designator;
  • (5) time of observation, if appropriate;
  • (6) runway(s) to be used for take-off; status of arresting system constituting a potential hazard, if any;
  • (7) surface conditions of runway(s) to be used for take-off;
  • (8) departure delay, if appropriate;
  • (9) transition level, if applicable;
  • (10) other essential operational information;
  • (11) surface wind direction (in degrees magnetic) and speed, including significant variations and, if surface wind sensors related specifically to the sections of runway(s) in use are available and the information is required by aircraft operators, the indication of the runway and the section of the runway to which the information refers;
  • (12) visibility and, when applicable RVR (5)  and, if visibility/RVR sensors related specifically to the sections of runway(s) in use are available and the information is required by operators, the indication of the runway and the section of the runway to which the information refers;
  • (13) present weather (5) ;
  • (14) 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 (5) ;
  • (15) air temperature;
  • (16) dew point temperature;
  • (17) altimeter setting(s);
  • (18) any available information on significant meteorological phenomena in the climb-out area including wind shear;
  • (19) trend forecast, when available; and
  • (20) specific ATIS instructions.

SECTION 10

Alerting service

SERA.10001   Application
  • (a)Alerting service shall be provided by the air traffic services units:
  • (1) for all aircraft provided with air traffic control service;
  • (2) in so far as practicable, to all other aircraft having filed a flight plan or otherwise known to the air traffic services; and
  • (3) to any aircraft known or believed to be the subject of unlawful interference.
  • (b)Unless otherwise prescribed by the competent authority, aircraft equipped with suitable two-way radio-communications shall report during the period 20 to 40 minutes following the time of the last contact, whatever the purpose of such contact, merely to indicate that the flight is progressing according to plan, such report to comprise identification of the aircraft and the words ‘Operations normal’.
  • (c)The ‘Operations normal’ message shall be transmitted air-ground to an appropriate ATS unit.
SERA.10005   Information to aircraft operating in the vicinity of an aircraft in a state of emergency
  • (a)When it has been established by an air traffic services unit that an aircraft is in a state of emergency, other aircraft known to be in the vicinity of the aircraft involved shall, except as provided in (b), be informed of the nature of the emergency as soon as practicable.
  • (b)When an air traffic services unit knows or believes that an aircraft is being subjected to unlawful interference, no reference shall be made in 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.

SECTION 11

Interference, emergency contingencies and interception

SERA.11001   General
  • (c)In case of an aircraft known or believed to be in a state of emergency, including being subjected to unlawful interference, ATS units shall give the aircraft maximum consideration, assistance and priority over other aircraft, as may be necessitated by the circumstances.
  • (d)Subsequent ATC actions shall be based on the intentions of the pilot, the overall air traffic situation and the real-time dynamics of the contingency.
SERA.11005   Unlawful interference
  • (aa)An aircraft which is being subjected to unlawful interference shall endeavour to set the transponder to Code 7500 and notify the appropriate ATS unit of any significant circumstances associated therewith and any deviation from the current flight plan necessitated by the circumstances, in order to enable the ATS unit to give priority to the aircraft and to minimise conflict with other aircraft.
  • (ab)If an aircraft is subjected to unlawful interference, the pilot-in-command shall attempt to land as soon as practicable at the nearest suitable aerodrome or operating site or at a dedicated aerodrome or operating site assigned by the competent authority, unless considerations aboard the aircraft dictate otherwise.
  • (b)When an occurrence of unlawful interference with an aircraft takes place or is suspected, air traffic services units shall attend promptly to requests by the aircraft. Information pertinent to the safe conduct of the flight shall continue to be transmitted and necessary action shall be taken to expedite the conduct of all phases of the flight, especially the safe landing of the aircraft.
  • (c)When an occurrence of unlawful interference with an aircraft takes place or is suspected, ATS units shall, in accordance with locally agreed procedures, immediately inform the appropriate authority designated by the State and exchange necessary information with the aircraft operator or its designated representative.
SERA.11010   Strayed or unidentified aircraft
Strayed or unidentified aircraft
  • (a)As soon as an air traffic services unit becomes aware of a strayed aircraft it shall take all necessary steps as outlined in (1) and (3) to assist the aircraft and to safeguard its flight.
  • (1) If the aircraft’s position is not known, the air traffic services unit shall:
  • (i) attempt to establish two-way communication with the aircraft, unless such communication already exists;
  • (ii) use all available means to determine its position;
  • (iii) inform other air traffic services units into whose area the aircraft may have strayed or may stray, taking into account all the factors which may have affected the navigation of the aircraft in the circumstances;
  • (iv) inform, in accordance with locally agreed procedures, appropriate military units and provide them with pertinent flight plan and other data concerning strayed aircraft;
  • (v) request from the units referred to in (iii) and (iv) and from other aircraft in flight every assistance in establishing communication with the aircraft and determining its position.
  • (2) The requirements in (1)(iv) and (1)(v) shall apply also to air traffic services units informed in accordance with (1)(iii).
  • (3) When the aircraft’s position is established, the air traffic services unit shall:
  • (i) advise the aircraft of its position and the corrective action to be taken. This advice shall be immediately provided when the ATS unit is aware that there is a possibility of interception or other hazard to the safety of the aircraft; and
  • (ii) provide, as necessary, other air traffic services units and appropriate military units with relevant information concerning the strayed aircraft and any advice given to that aircraft.

Reading this document does not replace reading the official text published in the Official Journal of the European Union. We assume no responsibility for any inaccuracies arising from the conversion of the original to this format.

This text is published under EUR-Lex's own terms of reuse, not a Legalize or public-domain licence. EUR-Lex
Creative Commons Attribution 4.0 International (CC BY 4.0)
© European Union, https://eur-lex.europa.eu — Source: EUR-Lex (Publications Office of the European Union). Reused under the Creative Commons Attribution 4.0 International (CC BY 4.0) licence. Only EU legislation published in the printed Official Journal of the European Union is deemed authentic; consolidated texts are reproduced here for documentation purposes and have been reformatted to Markdown.