Document ID: chunk:federal_register_of_legislation:F2018C00889:reg:5:p16
Version: federal_register_of_legislation:F2018C00889
Segment Type: reg
Provision Reference: reg 5 (pt 16/51)
Character Range: 67694–70537

plan may only be modified when:
(a) ATC clearance is received to rejoin the route; or
(b) ATC confirms a new clearance.

8 Operating standards – flight procedures – RNAV SID requirements
       8.1 Before an eligible aircraft takes-off, the following RNAV SID requirements must be verified:
(a) that the aircraft's RNAV system is available, is operating correctly and the correct aerodrome and runway data is loaded;
 (b) that the correct runway and departure procedure (including any applicable en route transition) is entered in the navigation system flight plan and properly depicted;
       8.2 RNAV guidance must be selected and available to provide flight guidance for lateral RNAV at no later than 153 m (or 500 ft) above the aerodrome field elevation.
       8.3 For an RNAV 1 operation, an authorised method must be used to achieve an appropriate level of performance, for example, lateral deviation indicator, flight director or autopilot.
       8.4 For operations without GNSS using DME/DME/IRU, the aircraft navigation system position must be confirmed within 304 m (or 1 000 ft) of a known position, at the starting point of the take-off roll.
       8.5 When the aircraft is using GNSS, the signal must be acquired before the take-off roll commences.

9 Operating standards – flight procedures – RNAV STAR requirements
       9.1 The following must be checked and confirmed for RNAV STAR:
(a) that the aircraft navigation system is operating correctly;
(b) that the correct arrival procedure and runway (including any applicable transition) are entered in the navigation system flight plan and properly depicted.
       9.2 A route is not to be used if doubt exists as to its validity in the navigation database.
       9.3 No member of the flight crew may create a new waypoint by manual entry into the RNAV system.
       9.4 If the operator's contingency procedures require reversion to a conventional arrival route, provision for that arrival route must be made before commencement of the RNAV STAR.
       9.5 Route modifications in the terminal area may take the form of radar headings or "direct to" clearances and may require the insertion of tactical waypoints from the navigation database. However, no member of the flight crew may make a manual entry or modification of the loaded route using temporary waypoints or fixes not contained in the database.
       9.6 All relevant published altitude and speed constraints must be observed.

10 Contingency procedures for performance failure
       ATC must be notified immediately if the system performance ceases to meet RNAV 1 and RNAV 2 requirements (as applicable) during an RNAV 1 and RNAV 2 operation in controlled airspace.
Appendix 3 — Requirements for use of RNP 2

1 Eligibility for RNP 2 I.F.R. flights
       1.1RNP 2 navigation may only be used for PBN by an