AMC1 SPA.PBN.105(f) PBN operational approval

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

AMC1 SPA.PBN.105(f) PBN operational approval ED Decision 2016/020/R RNP MONITORING PROGRAMME (a) The operator approved to conduct RNP AR APCH operations, should have an RNP monitoring programme to ensure continued compliance with applicable rules and to identify any negative trends in performance. (b) During an interim approval period, which should be at least 90 days, the operator should at least submit the following information every 30 days to the competent authority. (1) Total number of RNP AR APCH operations conducted; (2) Number of approach operations by aircraft/system which were completed as planned without any navigation or guidance system anomalies; (3) Reasons for unsatisfactory approaches, such as: (i) UNABLE REQ NAV PERF, NAV ACCUR DOWNGRAD, or other RNP messages during approaches; (ii) excessive lateral or vertical deviation; (iii) TAWS warning; (iv) autopilot system disconnect; (v) navigation data errors; or (vi) flight crew reports of any anomaly; (4) Flight crew comments. (c) Thereafter, the operator should continue to collect and periodically review this data to identify potential safety concerns, and maintain summaries of this data. AMC1 SPA.PBN.105(f) PBN operational approval ED Decision 2016/020/R RNP MONITORING PROGRAMME (a) The operator approved to conduct RNP AR APCH operations, should have an RNP monitoring programme to ensure continued compliance with applicable rules and to identify any negative trends in performance. (b) During an interim approval period, which should be at least 90 days, the operator should at least submit the following information every 30 days to the competent authority. (1) Total number of RNP AR APCH operations conducted; (2) Number of approach operations by aircraft/system which were completed as planned without any navigation or guidance system anomalies; (3) Reasons for unsatisfactory approaches, such as: (i) UNABLE REQ NAV PERF, NAV ACCUR DOWNGRAD, or other RNP messages during approaches; (ii) excessive lateral or vertical deviation; (iii) TAWS warning; (iv) autopilot system disconnect; (v) navigation data errors; or (vi) flight crew reports of any anomaly; (4) Flight crew comments. (c) Thereafter, the operator should continue to collect and periodically review this data to identify potential safety concerns, and maintain summaries of this data. ##### AMC1 SPA.PBN.105(f) PBN operational approval *ED Decision 2016/020/R* **RNP MONITORING PROGRAMME** (a) The operator approved to conduct RNP AR APCH operations, should have an RNP monitoring programme to ensure continued compliance with applicable rules and to identify any negative trends in performance. (b) During an interim approval period, which should be at least 90 days, the operator should at least submit the following information every 30 days to the competent authority. (1) Total number of RNP AR APCH operations conducted; (2) Number of approach operations by aircraft/system which were completed as planned without any navigation or guidance system anomalies; (3) Reasons for unsatisfactory approaches, such as: (i) UNABLE REQ NAV PERF, NAV ACCUR DOWNGRAD, or other RNP messages during approaches; (ii) excessive lateral or vertical deviation; (iii) TAWS warning; (iv) autopilot system disconnect; (v) navigation data errors; or (vi) flight crew reports of any anomaly; (4) Flight crew comments. (c) Thereafter, the operator should continue to collect and periodically review this data to identify potential safety concerns, and maintain summaries of this data.