30Implementation program

30 Implementation program

30.1 RNP AR operations may only be conducted in accordance with the operator’s approved implementation program.

30.2 If an operator that has not previously conducted RNP AR operations, or RNP AR operations using a particular aircraft type, the implementation program must include limits on operating minima until the operator is able to demonstrate to CASA the capability to safely conduct RNP AR operations without such limits.

Note The initial operating period is determined after consideration of all relevant factors including operator RNAV and VNAV operating experience, the number and frequency of RNP AR operations conducted and the number of non-compliant incidents recorded.

30.3 The implementation program must have procedures to identify any negative trend in performance or operations, including procedures for monitoring RNP AR operations and collecting relevant data.

30.4 At intervals as specified in the operator’s implementation program, the operator must submit to CASA a report containing a review of operations including the following elements:

(a) the total number of RNP AR procedures conducted;

(b) the number of satisfactory approaches and departures by aircraft and system;

Note Satisfactory means the approach or departure was completed as planned without any navigation or guidance system anomalies.

(c) the reasons for unsatisfactory operations, for example:

(i) UNABLE REQ NAV PERF – RNP, GPS PRIMARY LOST, or other RNP related messages; and

(ii) excessive lateral or V/DEV; and

(iii) TAWS warning; and

(iv) autopilot system disconnect; and

(v) navigation data errors; and

(vi) pilot report of anomaly;

(d) comments, both oral and written, from the flight crew.