Document ID: chunk:federal_register_of_legislation:F2018C00889:reg:22:p7
Version: federal_register_of_legislation:F2018C00889
Segment Type: reg
Provision Reference: reg 22 (pt 7/26)
Character Range: 185316–188328

II, Part C, Chapter 4, Implementing Advanced RNP.
       4.2Positioning data from non-GNSS navigation sensors may be integrated with GNSS data if:
(a) the non-GNSS data does not cause position errors exceeding the TSE budget; or
(b) if paragraph (a) does not apply — there is a means to deselect the non‑GNSS inputs.

5 Advanced RNP system functionality
       5.1To meet the requirements of clause 3 of this Appendix, the system must, as a minimum, meet the standards of functionality stated in ICAO Doc. 9613, Performance-based Navigation (PBN) Manual, Volume II, Part C, Chapter 4, Implementing Advanced RNP.
       5.2Additional functional and performance requirements for A-RNP are:
(a) the required inclusion of:
 (i) Radius to fix path terminator; and
 (ii) parallel offsets; and
 (iii) RNAV holding; and
(b) the optional inclusion of:
 (i) scalability; and
 (ii) higher continuity; and
 (iii) fixed radius transitions (FRT); and
 (iv) time of arrival control.
       5.3Baro-VNAV authorised in accordance with Appendix 8 may be used in conjunction with A-RNP under this Appendix.
       5.4FRT authorised in accordance with Appendix 11 may be used in conjunction with A-RNP under this Appendix.
Note   A map display depicting the aircraft computed flight path must be installed for operations using RF Legs and/or FRT so is required for an A-RNP airworthiness approval.

6 Operating standards – flight planning – general
       6.1Before an A-RNP operation commences, consideration must be given to matters that may affect the safety of the operation, including the following:
(a) whether the aircraft and the flight crew have relevant authorisations for A-RNP;
(b) whether the aircraft can be operated in accordance with the A-RNP requirements for:
           (i) the planned route, including the route to any alternate aerodromes; and
 (ii) minimum equipment requirements for the flight;
(c) whether the navaids required for the planned route are available and adequate for the period of the operation, including any non-RNAV contingencies;
(d) whether the navigation database is current and appropriate for the region of operation and includes the navaids and waypoints required for the route;
(e) whether operating restrictions, including time limits, apply to the operation.
       6.2If the aircraft's essential A-RNP equipment is functioning properly, the PBN capability of the aircraft must be indicated in the flight plan.

7 Operating standards — flight procedures – general
       7.1 An A-RNP operation must comply with the instructions and procedures of the OEM in relation to the performance requirements of A-RNP.
       7.2 At system initialisation, the following must occur:
(a) confirmation that the navigation database is current;
(b) verification of proper entry of the ATC-assigned route immediately after initial clearance from ATC to conduct the relevant A-RNP route;
(c) action to ensure the waypoints sequence, depicted by the navigation system, matches the route depicted on the