Document ID: chunk:federal_register_of_legislation:F2018C00889:reg:22:p10
Version: federal_register_of_legislation:F2018C00889
Segment Type: reg
Provision Reference: reg 22 (pt 10/26)
Character Range: 193411–196328

map display, flight director or autopilot.
       8.5 The GNSS signal must be acquired before the take-off roll commences.
       8.6 For aircraft using (E)TSO-C129a stand-alone equipment, the departure aerodrome must be loaded into the flight plan in order to achieve the appropriate navigation system monitoring and sensitivity.
       8.7 For aircraft using (E)TSO-C146a stand-alone equipment, if the departure begins at a runway waypoint, then the departure aerodrome does not need to be in the flight plan to obtain appropriate monitoring and sensitivity.

9 Operating standards – flight procedures – RNP STAR requirements
       9.1 The following must be checked and confirmed for an RNP 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 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.
       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, 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.8 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 RNP requirements during an RNP operation in controlled airspace.

11 Flight crew knowledge and training
       11.1 An A-RNP operation may only be commenced if each member of the flight crew has knowledge of the following:
(a) the meaning and proper use of aircraft equipment and navigation suffixes;
(b) the capabilities and limitations of the RNP system installed in the aircraft;
(c) the operations and airspace for which the RNP system is approved to operate;
(d) the limitations of the navaids to be used for the RNP operation;
(e) the required navigation equipment for operation on RNP