AMC and GM to Part-ORO — Issue 2, Amendment 20

AMC & GM to Part-ORO

Issue 2, Amendment 20

Annex III to ED Decision 2022/012/R ‘AMC & GM to Annex III (Part-ORO) to Commission Regulation (EU) No 965/2012 — Issue 2, Amendment 20’

The text of the amendment is arranged to show deleted, new or amended text as shown below: (a) deleted text is struck through; (b) new or amended text is highlighted in blue; (c) an ellipsis ‘[…]’ indicates that the rest of the text is unchanged. Note to the reader In amended, and in particular in existing (that is, unchanged) text, ‘Agency’ is used interchangeably with ‘EASA’. The interchangeable use of these two terms is more apparent in the consolidated versions. Therefore, please note that both terms refer to the ‘European Union Aviation Safety Agency (EASA)’.

Annex III to ED Decision 2022/012/R Page 1 of 4

AMC & GM to Part-ORO

Issue 2, Amendment 20

The Annex to Decision 2014/017/R of 24 April 2014 of the Executive Director of the Agency is amended as follows:

GM2 ORO.GEN.110(f) Operator responsibilities

ELEMENTS OF THE BRIEFING GIVEN TO FLIGHT OPERATIONS OFFICERS/FLIGHT DISPATCHERS BEFORE ASSUMING DUTIES Before commencing their shift, the FOO/FD should be briefed on relevant safety information such as: (a) weather charts; (b) weather reports; (c) NOTAMs; (d) operational restrictions in force; (e) flights in the air and flights for which operational flight plans have been issued but which have not yet started and for which the FOO/FD will be responsible; (f) the forecast flight schedule; and (f)(g) other relevant safety information as listed in GM 28 Annex I ‘Definitions for terms used in Annexes II to VIII’.

GM1 ORO.GEN.130(b) Changes related to an AOC holder

CHANGES REQUIRING PRIOR APPROVAL

The following GM is a non-exhaustive checklist of items that require prior approval from the competent authority as specified in the applicable implementing rules: (…) (p) method used to establish aerodrome operating minima; (pq) (…) (qr) (…) (rs) (…) (st) (…)

AMC3 ORO.GEN.160 Occurrence reporting

REPORTABLE EVENTS OF LVOs

A reportable event should include: (1) significant deviations from the flight path not caused by flight crew input; (2) misleading information without flight deck alerts; (3) loss of airborne navigation equipment functions necessary for the operation;

Annex III to ED Decision 2022/012/R Page 2 of 4

AMC & GM to Part-ORO

Issue 2, Amendment 20

(4) loss of functions or facilities at the aerodrome necessary for the operation, including aerodrome operating procedures, ATC operation, navigation facilities, visual aids and electrical power supply; (5) loss of other functions related to external infrastructure necessary for the operation; and (6) any other event causing the approach or landing to be abandoned if occurring repeatedly. The reports should be submitted to the aerodrome involved when relevant and in addition to the recipients prescribed in ORO.GEN.160(b).

GM1 ORO.GEN.160 Occurrence reporting

REPORTABLE EVENTS OF LVOs — OTHER EVENTS OCCURRING REPEATEDLY

(a) The purpose of point (a)(6) of AMC3 ORO.GEN.160 is to share the information with aviation stakeholders other than the operator of the aircraft to identify yet unknown systemetic safetyrelated issues. The main focus is thus on a series of similar events rather that an isolated single event. (b) Other events causing the approach or landing to be abandoned may include but are not limited to: (1) erroneous or inadequate flight crew action or aircraft handling; or (2) meteorological phenomena or human-made disturbances (e.g. road crossing final approach in an EFVS approach, laser strikes, etc.) or emissions from infrastructures (e.g. 5G) which require flight crews to take corrective action to an extent to which the LVO cannot be terminated successfully or completed as planned, leading to a go-around, a balked landing or an unplanned manual intervention by the pilot during the landing manoeuvre. (c) Possible causes may be human-factor-related issues when employing newly introduced LVO equipment technologies or procedures or when changes take place in the runway environment or aerodrome vicinity.

AMC1 ORO.DEC.100(a);(d) Declaration

RELEVANT INFORMATION PRIOR TO COMMENCING OPERATION, AND NOTIFICATION OF ANY CHANGES TO DECLARATION — EFVS 200 OPERATIONS

Declarations involving EFVS 200 operations (under NCC.OP.235 or SPO.OP.235) should be submitted at least 60 days before the new declaration or any change becomes effective, and indicate the date as of which they would apply.

GM1 ORO.DEC.100(a);(d) Declaration

RELEVANT INFORMATION PRIOR TO COMMENCING OPERATION, AND NOTIFICATION OF ANY CHANGES TO DECLARATION — EFVS 200 OPERATIONS

(a) When a declaration involves EFVS 200 operations in accordance with NCC.OP.235 or SPO.OP.235, the competent authority should be enabled to fulfil its responsibilities in

Annex III to ED Decision 2022/012/R Page 3 of 4

AMC & GM to Part-ORO

Issue 2, Amendment 20

accordance with ARO.GEN.345 prior to starting these operations or implementing changes to such EFVS 200 operations. (b) In accordance with ORO.DEC.100 points (a) and (d), the operator shall provide all relevant information and notify any changes. In relation to EFVS 200, this may be but is not limited to: (1) AFM or additional data from the TC/STC holder; (2) established relevant aerodrome operating minima; (3) documented operating procedures; (4) training and checking programmes; (5) minimum equipment list (MEL) for the operations to be undertaken; and (6) processes to ensure that only runways and instrument procedures suitable for the intended operations are used.

Annex III to ED Decision 2022/012/R Page 4 of 4