Document ID: chunk:federal_register_of_legislation:F2018C00889:reg:5:p30
Version: federal_register_of_legislation:F2018C00889
Segment Type: reg
Provision Reference: reg 5 (pt 30/51)
Character Range: 104736–107702

aircraft's RNP system is available, is operating correctly and the correct aerodrome and runway data is loaded;
(b) that the aircraft navigation system is operating correctly;
(c) that the correct aerodrome/heliport and departure procedure (including any applicable en route transition) is entered in the navigation system flight plan and properly depicted;
(d) that, if an RNP departure procedure is assigned and the runway, procedure or transition is subsequently changed, the appropriate changes are entered in the navigation system flight plan, properly depicted and available for navigation.
Note   It is recommended that, within the constraints of normal operations, there be a final check of proper runway entry and correct route depiction, shortly before take-off.
       8.2 The operator must ensure that each member of the flight crew is aware of the functional limitations of relevant RNP systems and the correct application of manual tracking procedures.
       8.3 The flight guidance system must be selected and available to provide flight guidance for lateral navigation no later than the first waypoint defining a procedure requiring RNP 0.3 in accordance with this Appendix.
       8.4 For an RNP 0.3 operation, an authorised method must be used to achieve an appropriate level of performance for RNP 0.3, for example, lateral deviation indicator, navigation map display, flight director or autopilot.
       8.5 The GNSS signal must be acquired before take-off.

9 Operating standards – flight procedures – RNP STAR requirements
       9.1 The following must be checked and confirmed for RNP STAR:
(a) that the aircraft navigation system is operating correctly;
(b) that the correct arrival procedure and aerodrome/heliport (including any applicable transition) are entered in the system and properly depicted.
       9.2 The following must be checked and confirmed:
(a) the active navigation system flight plan, by comparing the charts with the navigation displays;
(b) the sequence of waypoints;
(c) the reasonableness of track angles;
(d) distances, altitude or speed constraints;
(e) as far as practicable, which waypoints are fly-by and which are flyover;
(f) which waypoints represent the beginning or end of a radius-to-fix leg segment.
       9.3 The operator must ensure that updating will exclude a particular navaid, if so required by a route.
       9.4 A route is not to be used if doubt exists as to its validity in the navigation database.
       9.5 No member of the flight crew may create a new waypoint by manual entry into the RNP system.
       9.6 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 RNP STAR.
       9.7 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,