Document ID: chunk:federal_register_of_legislation:F2018C00889:reg:5:p25
Version: federal_register_of_legislation:F2018C00889
Segment Type: reg
Provision Reference: reg 5 (pt 25/51)
Character Range: 91342–94342

to be in the flight plan to obtain appropriate monitoring and sensitivity.

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 system and properly depicted.
       9.2 The operator must ensure that updating will exclude a particular navaid, if so required by a route.
       9.3 A route is not to be used if doubt exists as to its validity in the navigation database.
       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.

10 Contingency procedures for performance failure
       ATC must be notified immediately if the system performance ceases to meet RNP 1 requirements during an RNP 1 operation in controlled airspace.
Appendix 5 – Requirements for use of RNP 0.3

1 RNP 0.3 navigation authorisation for I.F.R. flights
       1.1The RNP 0.3 navigation specification was developed specifically for helicopter operations in metropolitan areas and for offshore support, including Point-in-Space (PINS) arrival and departure operations. This navigation specification addresses en route, terminal and approach operations using RNP 0.3 for all phases of flight. Fixed-wing aircraft that operate at speeds similar to helicopters are eligible for an RNP 0.3 navigation authorisation provided they meet all the requirements specified in this Appendix.
       1.2RNP 0.3 may only be used for PBN by an aircraft if the operator has an RNP 0.3 navigation authorisation in writing from CASA.
       1.3An operator may fly on a route, or in airspace designated as RNP 0.3, only if the operator holds an RNP 0.3 navigation authorisation.
       1.4RNP 0.3 requires GNSS approved to (E)TSO-C145, (E)TSO-C146 or (E)TSO-C196 as the primary navigation sensor.
       1.5An RNP 0.3 navigation authorisation may only be issued to an operator who:
(a) applies in writing to CASA for it; and
(b) supplies the documents mentioned in clause 2 of this Appendix; and
(c) satisfies CASA that RNP 0.3 operations can, and are likely to continue to, meet the requirements of this Appendix, including in relation to:
           (i) aircraft eligibility; and
           (ii) RNP 0.3 equipment, system performance and system functionality; and
           (iii) operating standards, including flight planning and flight procedures; and
           (iv) approved flight crew training