AMC2 ORO.GEN.160 Occurrence reporting

• ED Decision 2016/019/R found in: Air Operations (965/2012) Part-ARO Part-ORO Part-CAT Part-SPA Part-NCC Part-NCO Part-SPO (Feb 2025)

AMC2 ORO.GEN.160 Occurrence reporting ED Decision 2016/019/R 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. AMC2 ORO.GEN.160 Occurrence reporting ED Decision 2016/019/R 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. ##### AMC2 ORO.GEN.160 Occurrence reporting *ED Decision 2016/019/R* **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.