ORO.GEN.160 Occurrence reporting

GENERAL

(a)The operator should report all occurrences defined in AMC 20-8, and as required by the applicable national rules implementing Regulation (EU) No 376/2014 on occurrence reporting in civil aviation.

(b)In addition to the reports required by AMC 20-8 and Regulation (EU) No 376/2014, the operator should report volcanic ash clouds encountered during flight.

REPORTABLE EVENTS OF PBN OPERATIONS

(a)A reportable event should be an event that adversely affects the safety of the operation and may be caused by actions or events external to the functioning of the aircraft navigation system.

(b)Technical defects and the exceedance of technical limitations, including:

(1)significant navigation errors attributed to incorrect data or a database coding error;

(2)unexpected deviations in lateral/vertical flight path not caused by flight crew input or erroneous operation of equipment;

(3)significant misleading information without a failure warning;

(4)total loss or multiple navigation equipment failure; and

(5)loss of integrity, e.g. RAIM function, whereas integrity was predicted to be available during preflight planning, should be considered a reportable event.

(c)The operator should have in place a system for investigating a reportable event to determine if it is due to an improperly coded procedure or a navigation database error. The operator should initiate corrective actions for such an event.

REPORTABLE EVENTS OF LVOs

(a)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;

(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.

(b)The reports should be submitted to the aerodrome involved when relevant and in addition to the recipients prescribed in ORO.GEN.160(b).

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 systemic 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.