Civil Aviation Order 20.91 (Instructions and directions for performance-based navigation) 2012
15Certain other operators deemed to hold navigation authorisations for Appendices 1, 2, 3, 4 and 5
Start here
Get a plain-English read of 15
Turn the raw legal text into a practical explanation grounded in Civil Aviation Order 20.91 (Instructions and directions for performance-based navigation) 2012.
15 Certain other operators deemed to hold navigation authorisations for Appendices 1, 2, 3, 4 and 5
15.1 The operator of an Australian aircraft to whom paragraph 15.2 applies is deemed to hold a navigation authorisation for:
(d) RNP 1; and
(e) RNP APCH-LNAV; and
(f) RNP APCH-LP or RNP APCH-LPV.
15.2 This paragraph applies to the operator of an aircraft that is equipped, in accordance with paragraph 15.4, with equipment that was installed in accordance with paragraph 15.5.
15.3It is a condition of the navigation authorisation that the aircraft is flown by a pilot in accordance with paragraph 15.6.
15.4 The aircraft must be equipped with a GNSS stand-alone system with en route, terminal, NPA and APV capability having TSO-C146 ( ) or ETSO-C146 ( ) authorisation for Class Gamma and operational Class 1, 2 or 3.
15.5 The equipment must have been installed:
15.6 For paragraph 15.3, the aircraft is flown in a navigation specification by a pilot who complies with the requirements of paragraph 15.7 or 15.8 for the navigation specification.
15.7 For paragraph 15.6, for the navigation specification, the pilot must have:
(ii) containing an endorsement or entry under CAO 40.2.1, valid for navigation equivalent to the navigation specification in which the aircraft is to be flown by the pilot under the deemed authorisation.
15.8 For paragraph 15.6, for the navigation specification, the pilot must have:
(ii) containing an entry under CAO 40.2.3, valid for navigation equivalent to the navigation specification in which the aircraft is to be flown by the pilot under the deemed authorisation.
Appendix 1 — Requirements for use of RNAV 5
1 RNAV 5 navigation authorisation for I.F.R. flights
1.1RNAV 5 may only be used for PBN by an aircraft if:
(a) the operator has an RNAV 5 navigation authorisation in writing from CASA; and
(b) the aircraft is:
(i) equipped with a self-contained navigation system; or
(ii) flying on an approved or designated RNAV 5 route.
Note Air routes may be designed to support RNAV 5 depending on the supporting navaid infrastructure. In Australia, as the navaid infrastructure is limited, RNAV 5 operations are typically dependent on self-contained navigation systems.
1.2An RNAV 5 navigation authorisation may only be issued to an operator who:
(c) satisfies CASA that RNAV 5 operations can, and are likely to continue to, meet the requirements of this Appendix, including in relation to the following:
(ii) RNAV 5 equipment, system performance and system functionality;
Section 15 - Civil Aviation Order 20.91 (Instructions and directions for performance-based navigation) 2012 - Certain other operators deemed to hold navigation authorisations for Appendices 1, 2, 3, 4 and 5 | Zoe
(iv) approved flight crew training;
(vi) aircraft and RNAV system maintenance;
(vii) validity and continuing integrity of the airborne navigation database (if carried);
1.3An RNAV 5 navigation authorisation may not be issued unless the aircraft meets the requirements of this Appendix.
1.4 Despite subclauses 1.2 and 1.3, an RNAV 5 navigation authorisation may be issued to an operator who:
(a) holds an RNAV 1 and RNAV 2 navigation authorisation, or an RNP 2 or RNP 1 navigation authorisation; and
(i) an RNAV 1 and RNAV 2 navigation authorisation, or an RNP 2 or RNP 1 navigation authorisation; or
(ii) an RNAV 5 navigation authorisation; and
(c) applies in writing to CASA for an RNAV 5 navigation authorisation.
1.5 An RNAV 5 navigation authorisation may be issued subject to conditions if CASA considers this is necessary in the interests of safety.
1.6 It is a condition of the issue of a navigation authorisation that the applicable operational requirements of this Appendix are complied with after the issue of the authorisation.
1.7 It is a condition of the issue of a navigation authorisation that where an operational check, consideration, procedure or task (however described) is required under this Appendix, the operator must ensure that it is performed, given, followed or carried out, as the case may be.
Note The check, consideration, procedure or task may in practice be performed etc. by the pilot in command, other members of the flight crew, the despatch officer or other operational personnel. However, legal responsibility for compliance is placed on the operator who must ensure that the performance etc. occurs in accordance with his or her established procedures.
The application for a navigation authorisation must be made on the approved form and be accompanied by the following documents:
(a) aircraft airworthiness documents that satisfy CASA the aircraft is equipped for RNAV 5 operations, for example, the AFM, the AFM Supplement or OEM service letters;
(b) a detailed description of relevant aircraft equipment for RNAV 5 operations, including a configuration list of the components and equipment;
(c) a detailed description of the proposed flight crew training for RNAV 5 operations, including a copy of the training syllabus, for approval by CASA;
(d) a detailed description of the operating procedures to be used for RNAV 5 operations (including flight planning and flight procedures) supported by relevant copies of, or extracts from, the following:
(e) copies of the sections of the MEL applicable to RNAV 5 operations;
(f) a detailed description of the maintenance program used to ensure the continuing airworthiness of the aircraft for RNAV 5 operations;
(g) a detailed description of the method used to ensure the validity and continuing integrity of the airborne navigation database (if carried);
(h) if the aircraft is not equipped with GNSS — documentary evidence that satisfies CASA of the aircraft’s capability to meet RNAV 5 time limits for any relevant route on which it may be flown;
Note An acceptable means of evaluation of capability is contained in ICAO Doc 9613, Performance-based Navigation (PBN) Manual.
(i) if requested in writing by CASA — a copy of any relevant document referred to in any of the documents mentioned in paragraphs (a) to (h).
3.1 An aircraft is eligible for RNAV 5 operations if the aircraft’s AFM, AFM supplement, or OEM service letter states that the aircraft navigation system is approved for RNAV 5 or B-RNAV operations in accordance with:
(a) AMC 20-4 — Airworthiness Approval and Operational Criteria For the Use of Navigation Systems in European Airspace Designated For Basic RNAV Operations; or
(b) any of the following FAA documents:
(i) AC 90-96A — Approval of U.S. Operators and Aircraft to Operate under Instrument Flight Rules (IFR) in European Airspace Designated for Basic Area Navigation (B-RNAV) and Precision Area Navigation (P‑RNAV);
(ii) AC 90-45A — Approval of Area Navigation Systems for use in the U.S. National Airspace System;
(iii) AC 20-130 — Airworthiness Approval of Navigation or Flight Management Systems Integrating Multiple Navigation Sensors;
(iv) AC 20-138 — Airworthiness Approval of Global Positioning System (GPS) Navigation Equipment for use as a VFR and IFR Supplemental Navigation System;
(v) AC 25-15 — Approval of Flight Management Systems in Transport Category Airplanes.
3.2 An aircraft is eligible for RNAV 5 operations if the operator has demonstrated to CASA that the aircraft meets the requirements of ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part B, Chapter 2, Implementing RNAV 5.
4 RNAV 5 system performance
4.1An eligible aircraft’s navigation system (the system) must meet the performance, monitoring and alerting requirements for RNAV 5 operations as stated in ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part B, Chapter 2, Implementing RNAV 5.
4.2If GNSS is used for an RNAV 5 operation, positioning data from non-GNSS navigation sensors may be integrated with GNSS data if:
(b) if paragraph (a) cannot be complied with — there is a means to deselect the non‑GNSS inputs.
5 RNAV 5 system functionality
5.1 The system must meet the following minimum standards of functionality:
(a) the aircraft position relative to track must be continuously displayed on a navigation display situated in the primary field of view of the pilot flying the aircraft;
(b) where the minimum flight crew is 2 pilots, the aircraft position relative to track must also be continuously displayed on a navigation display situated in the primary field of view of the pilot not flying the aircraft;
(c) the system must display distance and bearing to the active (to) waypoint;
(d) the system must display ground-speed or time to the active (to) waypoint;
(e) the system must store at least 4 waypoints;
(f) the system must indicate failure of the system, including the sensors.
5.2 The following standards apply to navigation displays:
(a) navigation data must be available on:
(i) a display forming part of the RNAV equipment; or
(ii) an L/DEV display, for example, CDI, (E)HSI, or a navigation map display;
(b) the display must be suitable for use:
(i) as the primary flight instrument for navigation of the aircraft; and
(ii) for manoeuvre anticipation; and
(iii) for failure, status or integrity indication;
(c) the display must be visible to the pilot when looking forward along the flight path;
(d) where an L/DEV display is implemented, the L/DEV display must have:
(i) scaling compatible with any alerting and annunciation limits; and
(ii) scaling and full-scale deflection suitable for RNAV 5 operations.
6 RNAV 5 equipment
6.1 RNAV 5 navigation equipment must:
(a) enable the eligible aircraft to establish and follow a desired flight path; and
(b) automatically determine the aircraft’s position in the horizontal plane using inputs from 1 or more of the following types or combinations of position sensors:
(i) VOR/DME;
(ii) DME/DME;
(iii) INS or IRS;
(iv) GNSS.
6.2 If an aircraft is not equipped with GNSS, it must, nevertheless, have the capability to satisfy the RNAV 5 time limits for any relevant route on which it is flown.
7 Operating standards — flight planning – general
7.1 Before an RNAV 5 operation commences, proper 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 RNAV 5;
(b) whether the aircraft can be operated in accordance with the RNAV 5 requirements for:
(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, if a navigation database is used, it is current and appropriate for the region of operation and includes the navaids and waypoints required for the route;
7.2 If the aircraft’s essential RNAV 5 equipment is functioning properly, the PBN capability of the aircraft must be indicated in the flight plan.
8.1 This subclause only applies to an aircraft that:
(a) is equipped with a stand-alone GNSS or a GNSS/FMS; and
(b) derives its RNAV position data solely from GNSS signals without other navigation system inputs.
8.2If a continuous loss of the GNSS integrity function for more than 5 minutes is predicted for any part of the RNAV 5 operation, the flight plan must be revised, for example, by delaying the departure time or planning a different route.
8.3 For an RNAV 5 operation navigating with SBAS receivers, a check must be made for GNSS integrity availability in areas where SBAS is unavailable.
9 Operating standards — flight procedures
9.1 An RNAV 5 operation must comply with the following:
(a) the instructions and procedures of the OEM in relation to the performance requirements of RNAV 5;
(b) any AFM limitations or operating procedures required to maintain the navigation accuracy specified for RNAV 5.
9.2 The following checks and cross-checks must be made:
(a) a check that the navigation database is valid;
(b) a cross-check of the flight plan by comparing charts or other applicable resources with the navigation system flight plan and the aircraft map display (if applicable) and, if necessary, excluding specific navaids.
9.3 Flight progress must be monitored for navigational reasonableness by periodic cross‑checks with conventional navaids, where available.
9.4 Subject to subclause 9.5, the maximum permissible cross-track error/deviation is 2.5 NM.
Note 2.5 NM is half of the navigation accuracy.
9.5 Deviation from the standard mentioned in subclause 9.4 is acceptable during and immediately after turns, but only to the minimal extent that accurate cross‑track information may not be provided during the turn.
Note Flight crew procedures and training should emphasise observance of turn anticipation commands and management of rate of turn.
9.6 If ATC issues a heading assignment taking the aircraft off a route, the navigation system flight plan may only be modified when:
10 Contingency procedures for performance failure
10.1 If the system performance ceases to meet RNAV 5 requirements during an RNAV 5 operation in controlled airspace, ATC must be notified immediately.
10.2 Where stand-alone GNSS or GNSS/FMS equipment is used for an RNAV 5 operation and a loss of the integrity monitoring function occurs, the following checks and procedures must be followed:
(a) while continuing to navigate using GNSS — cross-check the aircraft position with other sources of position information, for example, VOR, DME and NDB information, to confirm an acceptable level of navigation performance;
(b) if unable to confirm navigation accuracy — revert to an alternative means of navigation and advise ATC accordingly.
10.3 If:
(a) stand-alone GNSS or GNSS/FMS equipment is used for an RNAV 5 operation; and
(b) a navigation display is flagged invalid due to an integrity alert;
the aircraft must:
(c) revert to an alternative means of navigation; and
(d) ATC must be advised accordingly.
11 Flight crew knowledge and training
11.1 An RNAV 5 operation may only be commenced if each member of the flight crew has knowledge of the following:
(a) the capabilities and limitations of the system installed in the aircraft;
(b) the operations and airspace for which the system is approved to operate;
(c) the limitations of the navaids to be used for the RNAV 5 operation;
(d) contingency procedures for RNAV 5 failures;
(e) the radio telephony phraseology for the relevant airspace in accordance with ICAO Doc 4444 and Doc 30;
(f) the flight planning requirements for the RNAV 5 operation;
(g) RNAV 5 procedure requirements as determined from chart depiction and textual description;
(iv) types of navigation sensors, for example, DME, IRU, GNSS, utilised by the system, and associated system prioritisation, weighting and logic; and
(v) turn anticipation with consideration of speed and altitude effects; and
(vi) interpretation of electronic displays and symbols.
11.2 An RNAV 5 operation may only be conducted if each member of the flight crew has received training in, or has equivalent experience of, RNAV 5 equipment and operating procedures, including training or experience in how to do the following:
(b) verify the successful completion of the system self-tests;
(c) initialise RNAV 5 system position;
(d) fly direct to waypoint;
(e) intercept a course or track;
(f) vector off and rejoin a procedure;
(g) determine cross-track error/deviation;
(h) remove and reselect navigation sensor input;
(i) confirm exclusion of a specific navaid or navaid type;
(j) perform gross navigation error checks using conventional aids.
12 MEL
The operator’s MEL must identify any unserviceability that affects the conduct of an RNAV 5 operation.
13 Navigation database — standards and discrepancies
13.1 If a navigation database is used for RNAV 5 operations, the navigation database:
(ii) European Organisation for Civil Aviation Equipment (EUROCAE) document ED-76, Standards for Processing Aeronautical Data; and
Note An LOA, issued by an appropriate regulatory authority to each of the participants in the data chain, demonstrates compliance with this requirement, for example, FAA LOA issued in accordance with FAA AC 20-153 or EASA LOA issued in accordance with EASA Implementing Rule (IR) 21, Subpart G.
13.2 An operator who has an RNAV 5 navigation authorisation from CASA, and who uses a navigation database for RNAV 5 operations, must periodically check the navigation database for database integrity.
Note While an LOA provides assurance of minimum standards for the supply of a navigation database, errors may still occur. All operators must conduct periodic checks to ensure database integrity.
13.3 Any discrepancy in data in the operator’s navigation database must be:
(b) resolved before further operational use by:
14 Navigation errors
14.1 The operator must take immediate action to remedy any condition that led to, or is likely to lead to, navigation error in the course of an RNAV 5 operation.
14.2 Without affecting the obligation in subclause 14.1, each of the following navigation errors must be reported to CASA and to AA within 72 hours of its occurrence:
(a) a lateral navigational error of at least 5 NM;
(b) a longitudinal navigational error of at least 5 NM;
(c) a longitudinal navigational error of at least 3 minutes variation between the aircraft’s estimated time of arrival at a reporting point and its actual time of arrival;
(d) a navigation system failure.
14.3 Each report mentioned in subclause 14.2 must:
Note The Navigation Error Investigation Form is the approved form for reporting a navigation error or an equipment failure.
14.4 Unless subclause 14.5 applies, the operator must take the remedial action mentioned in subclause 14.3 as soon as practicable.
14.5 Without affecting subclauses 14.1 to 14.3, for this clause CASA may:
(b) notify the operator of the cause and of the remedial action to be taken to prevent a recurrence of the error.
14.6 If subclause 14.5 applies, the operator must take the remedial action notified by CASA to prevent a recurrence of the error.
Appendix 2 — Requirements for use of RNAV 1 and RNAV 2
1 RNAV 1 and RNAV 2 navigation authorisation for I.F.R. flights
1.1 RNAV 1 and RNAV 2 may only be used for PBN by an aircraft if:
(a) the operator has an RNAV 1 and RNAV 2 navigation authorisation in writing from CASA; and
(b) the aircraft is either:
(i) equipped with a self-contained navigation system; or
(ii) flying on an approved or designated RNAV 1 and RNAV 2 route.
Note Air routes may be designed to support RNAV 1 or RNAV 2 depending on the supporting navaid infrastructure. In Australia, as the navaid infrastructure is limited, RNAV 1 and RNAV 2 operations are dependent on self-contained navigation systems.
1.2 RNAV 1 and RNAV 2 requirements are identical and a single navigation authorisation may be issued applying to both RNAV 1 and RNAV 2 operations. However, some operating procedures may be different.
Note In Australian airspace, RNAV 1 will be used only in terminal area operations and RNAV 2 routes or procedures will not be used.
1.3 An RNAV 1 and RNAV 2 navigation authorisation may only be issued to an operator who:
(c) satisfies CASA that RNAV 1 and RNAV 2 operations can, and are likely to continue to, meet the requirements of this Appendix, including in relation to:
(ii) RNAV 1 and RNAV 2 equipment, system performance and system functionality; and
(vi) aircraft and RNAV system maintenance; and
(vii) validity and continuing integrity of the airborne navigation database; and
1.4 An RNAV 1 and RNAV 2 navigation authorisation may not be issued unless the aircraft meets the requirements of this Appendix.
1.5 Despite subclauses 1.3 and 1.4, an RNAV 1 and RNAV 2 navigation authorisation may be issued to an operator who:
(a) holds an RNP 2 or RNP 1 navigation authorisation; and
(i) an RNP 2 or RNP 1 navigation authorisation; or
(ii) an RNAV 1 and RNAV 2 navigation authorisation; and
(c) applies in writing to CASA for an RNAV 1 and RNAV 2 navigation authorisation.
1.6 An RNAV 1 and RNAV 2 navigation authorisation may be issued subject to conditions if CASA considers this is necessary in the interests of safety.
1.7 It is a condition of the issue of a navigation authorisation that the applicable operational requirements of this Appendix are complied with after the issue of the authorisation.
1.8 It is a condition of the issue of a navigation authorisation that where an operational check, consideration, procedure or task (however described) is required under this Appendix, the operator must ensure that it is performed, given, followed or carried out, as the case may be.
Note The check, consideration, procedure or task may in practice be performed etc. by the pilot in command, other members of the flight crew, the despatch officer or other operational personnel. However, legal responsibility for compliance is placed on the operator who must ensure that the performance etc. occurs in accordance with his or her established procedures.
(a) aircraft airworthiness documents which satisfy CASA that the aircraft is equipped for RNAV 1 and RNAV 2 operations, for example, the AFM, the AFM Supplement or OEM service letters;
(b) a detailed description of relevant aircraft equipment for RNAV 1 and RNAV 2 operations, including a configuration list of the components and equipment;
(c) a detailed description of the proposed flight crew training for RNAV 1 and RNAV 2 operations, including a copy of the training syllabus, for approval by CASA;
(d) a detailed description of the operating procedures to be used for RNAV 1 and RNAV 2 operations (including flight planning and flight procedures) supported by relevant copies of, or extracts from, the following:
(e) copies of the sections of the MEL applicable to RNAV 1 and RNAV 2 operations;
(f) a detailed description of the maintenance program used to ensure the continuing airworthiness of the aircraft for RNAV 1 and RNAV 2 operations;
(g) a detailed description of the method used to ensure the validity and continuing integrity of the airborne navigation database;
(h) if requested in writing by CASA — a copy of any relevant document referred to in any of the documents mentioned in paragraphs (a) to (g).
3.1An aircraft is eligible for RNAV 1 and RNAV 2 operations if at least 1 of the following applies:
(a) the aircraft’s AFM, an AFM Supplement or an OEM service letter states that the aircraft navigation system is approved for RNAV 1 and RNAV 2 operations;
(b) the aircraft’s AFM, an AFM Supplement or an OEM service letter states that the aircraft navigation system is approved for P-RNAV in accordance with JAA TGL-10, and the additional requirements for RNAV 1 and RNAV 2 are met as set out in ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part B, Chapter 3, Implementing RNAV 1 and RNAV 2;
(c) the aircraft’s AFM, an AFM Supplement or an OEM service letter states that the aircraft navigation system is approved for US-RNAV in accordance with FAA AC 90-100A, and the additional requirements for RNAV 1 and RNAV 2 are met as set out in ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part B, Chapter 3, Implementing RNAV 1 and RNAV 2.
3.2An aircraft is eligible for RNAV 1 and RNAV 2 operations if the operator has demonstrated to CASA that the aircraft meets the requirements of ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part B, Chapter 3, Implementing RNAV 1 and RNAV 2.
4 RNAV 1 and RNAV 2 system performance
4.1The system must meet the system performance, monitoring and alerting requirements for RNAV 1 and RNAV 2 operations as stated in ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part B, Chapter 3, Implementing RNAV 1 and RNAV 2.
4.2If GNSS is used for an RNAV 1 and RNAV 2 operation, positioning data from non-GNSS navigation sensors may be integrated with GNSS data if:
(b) if paragraph (a) cannot be complied with — there is a means to deselect the non‑GNSS inputs.
5 RNAV 1 and RNAV 2 system functionality
5.1The system must as a minimum meet the functional requirements for navigation displays and standards stated in ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part B, Chapter 3, Implementing RNAV 1 and RNAV 2.
6.1 Before an RNAV 1 and RNAV 2 operation commences, consideration must be given to matters that may affect the safety of the RNAV 1 and RNAV 2 operation, including the following:
(a) whether the aircraft and the flight crew have relevant authorisations for RNAV 1 and RNAV 2;
(b) whether the aircraft can be operated in accordance with the RNAV 1 and RNAV 2 requirements for:
(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, if a navigation database is used, it is current and appropriate for the region of operation and includes the navaids and waypoints required for the route;
(e) for navigation relying on DME — whether operating procedures properly require the pilot in command:
(i) to check NOTAMs to verify the condition of critical DMEs; and
(ii) to consider his or her capability to navigate (including to an alternate destination) in the case of a failure of a critical DME while airborne;
(f) whether operating restrictions, including time limits, apply to the operation.
6.2 If the aircraft’s essential RNAV 1 and RNAV 2 equipment is functioning properly, the PBN capability of the aircraft must be indicated in the flight plan.
7.1This clause only applies to an aircraft that:
(a) is equipped with a stand-alone GNSS or a GNSS/FMS; and
(b) derives its RNAV position data solely from GNSS signals without other navigation system inputs.
7.2 If a continuous loss of the GNSS integrity function for more than 5 minutes is predicted for any part of the RNAV 1 and RNAV 2 operation, the flight plan must be revised, for example, by delaying the departure time or planning a different route.
7.3 For an RNAV 1 and RNAV 2 operation navigating with SBAS receivers, a check must be made of GNSS integrity availability in areas where SBAS is unavailable.
8.1 An RNAV 1 and RNAV 2 operation must comply with the instructions and procedures of the OEM in relation to the performance requirements of RNAV 1 and RNAV 2.
8.2 At system initialisation, the following must occur:
(b) verification that the aircraft position has been entered correctly;
(c) verification of proper entry of the ATC-assigned route immediately after initial clearance from ATC to conduct the relevant RNAV route;
(d) action to ensure the waypoints sequence, depicted by the navigation system, matches the route depicted on the appropriate charts and the assigned route.
8.3 The following steps must occur:
(a) selection of an RNAV 1 or RNAV 2 SID or STAR by route name from the on-board navigation database;
(b) confirmation that the selected route conforms to the charted route, or the route as modified through the insertion or deletion of specific waypoints in response to ATC clearances.
8.4 Except in response to ATC clearances, the following must not occur:
(a) creation of new waypoints by manual entry; or
(b) making manual entry of latitude, longitude or rho/theta values; or
(c) changing an RNAV SID or STAR database waypoint type from a fly-by to a flyover or vice versa.
Note Wherever possible, the pilot in command should extract RNAV 1 and RNAV 2 routes in the en route domain from the database in their entirety rather than load individual waypoints from the database into the navigation system flight plan. The pilot in command may, however, select and insert individual, named fixes and waypoints from the navigation database, provided all fixes along the published route to be flown are inserted.
8.5 The following checks and cross-checks must be made:
(a) a cross-check of the flight plan by comparing charts or other applicable resources with the navigation system flight plan and the aircraft map display (if applicable);
Note Small differences between charted navigation information and displayed navigation data may be noted. Differences of 3 degrees or less due to the equipment manufacturer’s application of magnetic variation or leg track averaging are operationally acceptable.
8.6 Flight progress must be monitored for navigational reasonableness by periodic cross‑checks with available data from ground-based aids.
8.7 For RNAV 1 routes, an L/DEV indicator, flight director or autopilot in LNAV mode must be used.
Note For RNAV 2 routes, an L/DEV indicator, flight director or autopilot in the LNAV mode is recommended. In lieu of an L/DEV indicator, a navigation map display with equivalent functionality to an L/DEV indicator is recommended.
8.8 Where an L/DEV indicator is used, scaling must be selected suitable for the navigation accuracy associated with the route or procedure, for example, full scale deflection ±1 NM for RNAV 1, ±2 NM for RNAV 2, or ±5 NM for TSO‑C129 ( ) equipment on RNAV 2 routes.
8.9 Route centrelines must be maintained, as depicted by L/DEV indicators or flight guidance, unless authorised to deviate by ATC or under emergency conditions.
8.10 Subject to subclause 8.11, the maximum permissible cross-track error/deviation is 0.5 NM for RNAV 1 and 1.0 NM for RNAV 2.
Note 0.5 NM and 1.0 NM are half of the navigation accuracy for RNAV 1 and RNAV 2, respectively.
8.11 Deviation from the standard mentioned in subclause 8.10 is acceptable during and immediately after turns, but only to the minimal extent that accurate cross‑track information may not be provided during the turn.
Note Flight crew procedures and training should emphasise observance of turn anticipation commands and management of rate of turn.
8.12 If ATC issues a heading assignment taking the aircraft off a route, the navigation system flight plan may only be modified when:
9.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 aircraft navigation system is operating correctly;
(c) that the correct runway and departure procedure (including any applicable en route transition) is entered in the navigation system flight plan and properly depicted;
(d) that, if an RNAV 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.
9.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.
Note The altitude at which RNAV guidance begins on a given route may be higher, for example, “climb to 304 m (or 1 000 ft), then direct to X….”.
9.3 For an RNAV 1 operation, an authorised method must be used to achieve an appropriate level of performance, for example, L/DEV indicator, flight director or autopilot.
9.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.
Note 1 This is usually achieved by the use of an automatic or manual runway update function. A navigation map may also be used to confirm aircraft position if procedures and the display resolution allow for compliance with the 304 m (1 000 ft) tolerance requirement.
Note 2 Based on evaluated IRU performance, the growth in position error after reverting to IRU can be expected to be less than 2 NM per 15 minutes.
9.5 When the aircraft is using GNSS, the signal must be acquired before the take-off roll commences.
10 Operating standards — flight procedures – RNAV STAR requirements
10.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.
10.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) that updating excludes a particular navaid, if so required by a route.
10.3 A route is not to be used if doubt exists as to its validity in the navigation database.
10.4 No member of the flight crew may create a new waypoint by manual entry into the RNAV system.
10.5 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.
10.6 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.7 All relevant published altitude and speed constraints must be observed.
11 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.
12 Flight crew knowledge and training
12.1 An RNAV 1 and RNAV 2 operation may only be commenced if each member of the flight crew has knowledge of the following:
(b) the capabilities and limitations of the RNAV 1 and RNAV 2 system installed in the aircraft;
(c) the operations and airspace for which the RNAV 1 and RNAV 2 system is approved to operate;
(d) the limitations of the navaids to be used for the RNAV 1 and RNAV 2 operation;
(e) the required navigation equipment for operation on RNAV routes with SIDs or STARs, for example, DME/DME, DME/DME/IRU and GNSS;
(f) depiction of waypoint types (flyover and fly-by), ARINC 424 Path Terminators, and associated aircraft flight paths;
(g) contingency procedures for RNAV 1 and RNAV 2 failures;
(h) the radio telephony phraseology for the relevant airspace in accordance with ICAO Doc 4444 and Doc 7030;
(i) the flight planning requirements for the RNAV 1 and RNAV 2 operation;
(j) RNAV 1 and RNAV 2 procedure requirements as determined from chart depiction and textual description;
(k) RNAV 1 and RNAV 2 system-specific information, including:
(iv) types of navigation sensors, for example, DME, IRU, GNSS, utilised by the RNAV 1 or RNAV 2 system, and associated system prioritisation, weighting and logic; and
(v) aircraft configuration and operational conditions required to support RNAV operations, including appropriate selection of CDI scaling (L/DEV display scaling); and
12.2 An RNAV 1 and RNAV 2 operation may only be conducted if each member of the flight crew has received training in, or has equivalent experience of, RNAV 1 and RNAV 2 equipment and operating procedures, including training or experience in how to do the following:
(b) verify the successful completion of RNAV 1 and RNAV 2 system self‑tests;
(c) initialise RNAV 1 and RNAV 2 system position;
(e) retrieve and fly a SID and a STAR with appropriate transition;
(f) verify waypoints and navigation system flight plan programming;
(g) resolve route discontinuities;
(h) adhere to speed and altitude constraints associated with a SID or a STAR;
(i) fly direct to waypoint;
(j) fly a course or track to waypoint;
(k) intercept a course or track;
(l) vector off and rejoin a procedure;
(m) fly radar vectors and rejoining an RNAV route from a heading mode;
(n) determine cross-track error/deviation;
(o) determine allowable deviation limits and maintain flight within those limits;
(p) remove and reselect navigation sensor input;
(q) confirm exclusion of a specific navaid or navaid type;
(r) perform gross navigation error checks using conventional aids;
(s) change arrival aerodrome and alternate aerodrome;
(t) perform parallel offset function if capability exists, and advise ATC if this functionality is not available;
(u) carry out contingency procedures for RNAV failures.
13 MEL
The operator’s MEL must identify any unserviceability that affects the conduct of an RNAV 1 and RNAV 2 operation.
14 Navigation database — standards and discrepancies
14.1A navigation database for RNAV 1 and RNAV 2 operations:
(ii) European Organisation for Civil Aviation Equipment (EUROCAE) document ED-76, Standards for Processing Aeronautical Data; and
Note An LOA, issued by an appropriate regulatory authority to each of the participants in the data chain, demonstrates compliance with this requirement, for example, FAA LOA issued in accordance with FAA AC 20-153 or EASA LOA issued in accordance with EASA Implementing Rule (IR) 21, Subpart G.
14.2An operator who has an RNAV 1 and RNAV 2 navigation authorisation from CASA must periodically check the RNAV 1 and RNAV 2 navigation database for database integrity.
Note While an LOA provides assurance of minimum standards for the supply of a navigation database, errors may still occur. All operators must conduct periodic checks to ensure database integrity.
14.3Any discrepancy in data in the operator’s navigation database must be:
(b) resolved before further operational use by:
15 Navigation errors
15.1 The operator must take immediate action to remedy any condition that led to, or is likely to lead to, navigation error in the course of an RNAV 1 and RNAV 2 operation.
15.2 Without affecting the obligation in subclause 15.1, each of the following navigation errors or events must be reported to CASA and to AA within 72 hours of its occurrence:
(a) a lateral navigational error of at least:
(i) 1 NM for RNAV 1; and
(ii) 2 NM for RNAV 2;
(b) a longitudinal navigational error of at least:
(i) 1 NM for RNAV 1; and
(ii) 2 NM for RNAV 2;
15.3 Each report mentioned in subclause 15.2 must:
(b) contain a preliminary analysis of the cause of the error, and
Note The Navigation Error Investigation Form is the approved form for reporting a navigation error or an equipment failure.
15.4 Unless subclause 15.5 applies, the operator must take the remedial action mentioned in subclause 15.3 as soon as practicable.
15.5 Without affecting subclauses 15.1 to 15.3, for this clause CASA may:
(b) notify the operator of the cause and of the remedial action to be taken to prevent a recurrence of the error.
15.6 If subclause 15.5 applies, the operator must take the remedial action notified by CASA to prevent a recurrence of the error.
Appendix 3 — Requirements for use of RNP 2
1 RNP 2 navigation authorisation for I.F.R. flights
1.1RNP 2 may only be used for PBN by an aircraft if the operator has an RNP 2 navigation authorisation in writing from CASA.
1.2An operator may fly on a route or in airspace designated as RNP 2 only if the operator holds an RNP 2 navigation authorisation.
1.3RNP 2 requires GNSS as the primary navigation sensor.
1.4An RNP 2 navigation authorisation may only be issued to an operator who:
(c) satisfies CASA that RNP 2 operations can, and are likely to continue to, meet the requirements of this Appendix, including in relation to:
(ii) RNP 2 equipment, system performance and system functionality; and
(vii) validity and continuing integrity of the airborne navigation database (if carried); and
1.5An RNP 2 navigation authorisation may not be issued unless the aircraft meets the requirements of this Appendix.
1.6Despite subclauses 1.4 and 1.5, an RNP 2 navigation authorisation may be issued to an operator who:
(a) holds a RNP 1, RNP APCH or RNP AR navigation authorisation; and
(i) a RNP 1, RNP APCH or RNP AR navigation authorisation; or
(ii) an RNP 2 navigation authorisation; and
(c) applies in writing to CASA for an RNP 2 navigation authorisation.
1.7An RNP 2 navigation authorisation may be issued subject to conditions if CASA considers this is necessary in the interests of safety.
1.8It is a condition of the issue of a navigation authorisation that the applicable operational requirements of this Appendix are complied with after the issue of the authorisation.
1.9It is a condition of the issue of a navigation authorisation that where an operational check, consideration, procedure or task (however described) is required under this Appendix, the operator must ensure that it is performed, given, followed or carried out, as the case may be.
Note The check, consideration, procedure or task may in practice be performed etc. by the pilot in command, other members of the flight crew, the despatch officer or other operational personnel. However, legal responsibility for compliance is placed on the operator who must ensure that the performance etc. occurs in accordance with his or her established procedures.
(a) aircraft airworthiness documents which satisfy CASA that the aircraft is equipped for RNP 2 operations, for example, the AFM, the AFM Supplement or OEM service letters;
(b) a detailed description of relevant aircraft equipment for RNP 2 operations, including a configuration list of the components and equipment;
(c) a detailed description of the proposed flight crew training for RNP 2 operations, including a copy of the training syllabus for approval by CASA;
(d) a detailed description of the operating procedures to be used for RNP 2 operations (including flight planning and flight procedures) supported by relevant copies of, or extracts from, the following:
(e) copies of the sections of the MEL applicable to RNP 2 operations;
(f) a detailed description of the maintenance program used to ensure the continuing airworthiness of the aircraft for RNP 2 operations;
(g) a detailed description of the method used to ensure the validity and continuing integrity of the airborne navigation database;
(h) if requested in writing by CASA — a copy of any relevant document referred to in any of the documents mentioned in paragraphs (a) to (g).
3.1An aircraft is eligible for RNP 2 operations if the aircraft’s AFM, AFM Supplement or OEM service letter states that the aircraft navigation system is approved for RNP 2 operations.
3.2An aircraft is eligible for RNP 2 operations if the aircraft is equipped with a stand-alone GNSS that is certified by the manufacturer for en route operations, installed in accordance with AC 21-36(0), and compliant with:
(a) TSO-C129 ( ) Class A1 or A2; or
(b) TSO-C146 ( ) Class Gamma and operational Class 1, 2 or 3; or
(c) ETSO-C146 ( ) Class Gamma and operational Class 1, 2 or 3; or
(d) standards that CASA considers are equivalent to the standards mentioned in paragraph (a), (b) or (c).
3.3An aircraft is eligible for RNP 2 operations if the aircraft is equipped with a multi-sensor system (for example, FMS) with GNSS equipment that is certified by the manufacturer for en route operations, installed in accordance with AC 21‑37 (0), and meets:
(a) the requirements of TSO-C115b FMS or ETSO-C115b FMS, and 1 of the following:
(i) TSO-C129(a) sensor Class B or C;
(ii) ETSO-C129(a) sensor Class B or C;
(iii) TSO-C145( ) Class 1, 2 or 3;
(iv) ETSO-C145( ) Class 1, 2 or 3;
(v) TSO-C196 ( ); or
(b) standards that CASA considers are equivalent to the standards mentioned in paragraph (a).
3.4 An aircraft is eligible for RNP 2 operations if the operator has demonstrated to CASA that the aircraft meets the requirements of ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part C, Chapter 2, Implementing RNP 2.
4 RNP 2 system performance
4.1The system must meet the performance, monitoring and alerting requirements for RNP 2 operations as stated in ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part C, Chapter 2, Implementing RNP 2.
5 RNP 2 system functionality
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 2, Implementing RNP 2.
5 RNP 2 equipment
5.1An aircraft conducting RNP 2 operations in oceanic or remote airspace must be equipped with appropriate dual, independent, serviceable long-range navigation systems.
5.2An aircraft conducting RNP 2 operations in continental en route airspace must be equipped with at least an appropriate single GNSS RNAV system, provided that an alternative means of navigation is available if required for the class of the operation.
6.1Before an RNP 2 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 RNP 2;
(b) whether the aircraft can be operated in accordance with the RNP 2 requirements for:
(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, if a navigation database is used, it is current and appropriate for the region of operation and includes the navaids and waypoints required for the route;
6.2If the aircraft’s essential RNP 2 equipment is functioning properly, the PBN capability of the aircraft must be indicated in the flight plan.
7.1As part of flight planning, a prediction for GNSS integrity availability must be obtained.
7.2For an RNP 2 operation navigating with SBAS receivers, a check must be made for GNSS integrity availability in areas where SBAS is unavailable.
7.3If a continuous loss of the GNSS integrity function for more than 5 minutes is predicted for any part of an RNP 2 operation, the flight plan must be revised, for example, by delaying the departure time or planning a different route.
7.4Subclauses 7.1, 7.2 and 7.3 do not apply to an aircraft whose RNP system can achieve LNAV accuracy equal to, or less than, 2 NM using requisite GNSS satellites.
8.1An RNP 2 operation must comply with the instructions and procedures of the OEM in relation to the performance requirements of RNP 2.
8.2At system initialisation, the following must occur:
(b) verification of proper entry of the ATC-assigned route immediately after initial clearance from ATC to conduct the relevant RNAV route;
(c) action to ensure the waypoints sequence, depicted by the navigation system, matches the route depicted on the appropriate charts and the assigned route.
8.3 The following checks and cross-checks must be made:
(a) a cross-check of the flight plan by comparing charts or other applicable resources with the navigation system flight plan and the aircraft map display (if applicable);
Note Small differences between charted navigation information and displayed navigation data may be noted. Differences of 3 degrees or less due to the equipment manufacturer’s application of magnetic variation or leg track averaging are operationally acceptable.
8.4During flight, as far as practicable, navigation reasonableness must be periodically confirmed by cross-reference to available data from ground-based aids.
8.5For RNP 2 routes, 1 or more of the following must be used:
(a) subject to subclause 8.6, an L/DEV indicator;
(b) a flight director; or
(c) an autopilot in the L/DEV mode.
8.6A navigation map display may be used instead of an L/DEV indicator, if the navigation map display has functionality equivalent to an L/DEV indicator as described in ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part C, Chapter 2, Implementing RNP 2.
8.7 Where an L/DEV indicator is used, scaling must be selected suitable for the navigation accuracy associated with the route or procedure, for example:
(a) full scale deflection ±2 NM; or
(b) on an RNP 2 route using an L/DEV indicator that complies with TSO‑C129 ( ) — full scale deflection ±5 NM.
8.8 Route centrelines must be maintained, as depicted by L/DEV indicators or flight guidance, unless authorised to deviate by ATC or under emergency conditions.
8.9 Subject to subclause 8.10, the maximum permissible cross-track error/deviation is half of the navigation accuracy, namely, 1.0 NM.
8.10 Deviation from the standard mentioned in subclause 8.9 is acceptable during and immediately after turns, but only to the minimal extent that accurate cross-track information may not be provided during the turn.
Note Flight crew procedures and training should emphasise observance of turn anticipation commands and management of rate of turn.
8.11 If ATC issues a heading assignment taking the aircraft off a route, the navigation system flight plan may only be modified when:
9 Contingency procedures for performance failure
ATC must be notified immediately if the system performance ceases to meet RNP 2 requirements during an RNP 2 operation in controlled airspace.
10 Flight crew knowledge and training
10.1 An RNP 2 operation may only be commenced if each member of the flight crew has knowledge of the following:
(b) the capabilities and limitations of the RNAV system installed in the aircraft;
(c) the operations and airspace for which the RNP 2 system is approved to operate;
(d) the limitations of the navaids to be used for the RNP 2 operation;
(e) depiction of waypoint types (flyover and fly-by), ARINC 424 Path Terminators, and associated aircraft flight paths;
(f) contingency procedures for RNP 2 failures;
(g) the radio telephony phraseology for the relevant airspace in accordance with ICAO Doc 4444 and Doc 7030;
(h) the flight planning requirements for RNP 2 operation;
(i) RNP 2 procedure requirements as determined from chart depiction and textual description;
(j) RNP 2 system-specific information, including:
(iv) types of navigation sensors, for example, DME, IRU, GNSS, utilised by the RNP 2 system, and associated system prioritisation, weighting and logic; and
(v) aircraft configuration and operational conditions required to support RNAV operations, including appropriate selection of CDI scaling (L/DEV display scaling); and
10.2 An RNP 2 operation may only be conducted if each member of the flight crew has received training in, or has equivalent experience of, RNP 2 equipment and operating procedures, including training or experience in how to do the following:
(b) verify the successful completion of RNP 2 system self-tests;
(c) initialise RNP 2 system position;
(e) verify waypoints and navigation system flight plan programming;
(f) resolve route discontinuities;
(g) fly direct to waypoint;
(h) fly a course or track to waypoint;
(i) intercept a course or track;
(j) fly radar vectors and rejoin an RNAV route from a heading mode;
(k) determine cross-track error/deviation;
(l) determine allowable deviation limits and maintain flight within those limits;
(m) remove and reselect navigation sensor input;
(n) confirm exclusion of a specific navaid or navaid type;
(o) perform gross navigation error checks using conventional aids;
(p) change arrival aerodrome and alternate aerodrome;
(q) perform parallel offset function if capability exists, and advise ATC if this functionality is not available;
(r) carry out contingency procedures for RNAV failures.
11 MEL
The operator’s MEL list must identify any unserviceability that affects the conduct of an RNP 2 operation.
12 Navigation database — standards and discrepancies
12.1 A navigation database for RNP 2 operations:
(ii) European Organisation for Civil Aviation Equipment (EUROCAE) document ED-76, Standards for Processing Aeronautical Data; and
Note An LOA, issued by an appropriate regulatory authority to each of the participants in the data chain, demonstrates compliance with this requirement, for example, FAA LOA issued in accordance with FAA AC 20-153 or EASA LOA issued in accordance with EASA Implementing Rule (IR) 21, Subpart G.
12.2 An operator who has an RNP 2 navigation authorisation from CASA must periodically check the RNP 2 navigation database for database integrity.
Note While an LOA provides assurance of minimum standards for the supply of a navigation database, errors may still occur. All operators must conduct periodic checks to ensure database integrity.
12.3 Any discrepancy in data in the operator’s navigation database must be:
13 Navigation errors
13.1 The operator must take immediate action to remedy any condition that led to, or is likely to lead to, navigation error in the course of an RNP 2 operation.
13.2 Without affecting the obligation in subclause 13.1, each of the following navigation errors or events must be reported to CASA and to AA within 72 hours of its occurrence:
(a) a lateral navigational error of at least 2 NM;
(b) a longitudinal navigational error of at least 2 NM;
13.3 Each report mentioned in subclause 13.2 must:
Note The Navigation Error Investigation Form is the approved form for reporting a navigation error or an equipment failure.
13.4 Unless subclause 13.5 applies, the operator must take the remedial action mentioned in subclause 13.3 as soon as practicable.
13.5 Without affecting subclauses 13.1 to 13.3, for this clause CASA may:
(b) notify the operator of the cause of the error and of the remedial action to be taken to prevent a recurrence of the error.
13.6 If subclause 13.5 applies, the operator must take the remedial action notified by CASA to prevent a recurrence of the error.
Appendix 4 — Requirements for use of RNP 1
1 RNP 1 navigation authorisation for I.F.R. flights
1.1 RNP 1 may only be used for PBN by an aircraft if the operator has an RNP 1 navigation authorisation in writing from CASA.
1.2 An operator may fly on a route or in airspace designated as RNP 1 only if the operator holds an RNP 1 navigation authorisation.
1.3 RNP 1 requires GNSS as the primary navigation sensor.
1.4 An RNP 1 navigation authorisation may only be issued to an operator who:
(c) satisfies CASA that RNP 1 operations can, and are likely to continue to, meet the requirements of this Appendix, including in relation to:
(ii) RNP 1 equipment, system performance and system functionality; and
(vii) validity and continuing integrity of the airborne navigation database (if carried); and
1.5 An RNP 1 navigation authorisation may not be issued unless the aircraft meets the requirements of this Appendix.
1.6 Despite subclauses 1.4 and 1.5, an RNP 1 navigation authorisation may be issued to an operator who:
(a) holds an RNP APCH or RNP AR navigation authorisation; and
(i) an RNP APCH or RNP AR navigation authorisation; or
(ii) an RNP 1 navigation authorisation; and
(c) applies in writing to CASA for an RNP 1 navigation authorisation.
1.7An RNP 1 navigation authorisation may be issued subject to conditions if CASA considers this is necessary in the interests of safety.
1.8It is a condition of the issue of a navigation authorisation that the applicable operational requirements of this Appendix are complied with after the issue of the authorisation.
1.9It is a condition of the issue of a navigation authorisation that where an operational check, consideration, procedure or task (however described) is required under this Appendix, the operator must ensure that it is performed, given, followed or carried out, as the case may be.
Note The check, consideration, procedure or task may in practice be performed etc. by the pilot in command, other members of the flight crew, the despatch officer or other operational personnel. However, legal responsibility for compliance is placed on the operator who must ensure that the performance etc. occurs in accordance with his or her established procedures.
(a) aircraft airworthiness documents which satisfy CASA that the aircraft is equipped for RNP 1 operations, for example, the AFM, the AFM Supplement or OEM service letters;
(b) a detailed description of relevant aircraft equipment for RNP 1 operations, including a configuration list of the components and equipment;
(c) a detailed description of the proposed flight crew training for RNP 1 operations, including a copy of the training syllabus for approval by CASA;
(d) a detailed description of the operating procedures to be used for RNP 1 operations (including flight planning and flight procedures) supported by relevant copies of, or extracts from, the following:
(e) copies of the sections of the MEL applicable to RNP 1 operations;
(f) a detailed description of the maintenance program used to ensure the continuing airworthiness of the aircraft for RNP 1 operations;
(g) a detailed description of the method used to ensure the validity and continuing integrity of the airborne navigation database;
(h) if requested in writing by CASA — a copy of any relevant document referred to in any of the documents mentioned in paragraphs (a) to (g).
3.1An aircraft is eligible for RNP 1 operations if the aircraft’s AFM, an AFM Supplement or an OEM service letter states that the aircraft navigation system is approved for RNP 1 operations.
3.2An aircraft is eligible for RNP 1 operations if the operator has demonstrated to CASA that the aircraft meets the requirements of ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part C, Chapter 3, Implementing RNP 1.
4 RNP 1 system performance
4.1The system must meet the performance, monitoring and alerting requirements for RNP 1 operations as stated in ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part C, Chapter 3, Implementing RNP 1.
5 RNP 1 system functionality
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 3, Implementing RNP 1.
6.1 Before an RNP 1 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 RNP 1;
(b) whether the aircraft can be operated in accordance with the RNP 1 requirements for:
(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, if a navigation database is used, it is current and appropriate for the region of operation and includes the navaids and waypoints required for the route;
6.2 If the aircraft’s essential RNP 1 equipment is functioning properly, the PBN capability of the aircraft must be indicated in the flight plan.
7.1 As part of flight planning, a prediction for GNSS integrity availability must be obtained.
7.2For an RNP 1 operation navigating with SBAS receivers, a check must be made for GNSS integrity availability in areas where SBAS is unavailable.
7.3 If a continuous loss of the GNSS integrity function for more than 5 minutes is predicted for any part of an RNP 1 operation, the flight plan must be revised, for example, by delaying the departure time or planning a different route.
7.4 Subclauses 7.1, 7.2 and 7.3 do not apply to an aircraft whose RNP system can achieve LNAV accuracy equal to or less than 1 NM using requisite GNSS satellites.
8.1 An RNP 1 operation must comply with the instructions and procedures of the OEM in relation to the performance requirements of RNP 1.
8.2 At system initialisation, the following must occur:
(b) verification of proper entry of the ATC-assigned route immediately after initial clearance from ATC to conduct the relevant RNAV route;
(c) action to ensure the waypoints sequence, depicted by the navigation system, matches the route depicted on the appropriate charts and the assigned route.
8.3 The following steps must occur:
(a) selection of an RNP 1 SID or STAR by route name from the on-board navigation database;
(b) confirmation that the selected route conforms to the charted route, or the route as modified through the insertion or deletion of specific waypoints in response to ATC clearances.
8.4 Except in response to ATC clearances, the following must not occur:
(a) creation of new waypoints by manual entry; or
(b) making manual entry of latitude, longitude or rho/theta values; or
(c) changing an RNAV SID or STAR database waypoint type from a fly-by to a flyover or visa versa.
8.5 The following checks and cross-checks must be made:
(a) a cross-check of the flight plan by comparing charts or other applicable resources with the navigation system flight plan and the aircraft map display (if applicable);
Note Small differences between charted navigation information and displayed navigation data may be noted. Differences of 3 degrees or less due to the equipment manufacturer’s application of magnetic variation or leg track averaging are operationally acceptable.
8.6 For RNP 1 routes, an L/DEV indicator, flight director or autopilot in LNAV mode must be used.
Note Examples of an L/DEV indicator include CDI and HSI.
8.7 Where an L/DEV indicator is used, scaling must be selected suitable for the navigation accuracy associated with the route or procedure, for example, full scale deflection ±1 NM.
8.8 Route centrelines must be maintained, as depicted by L/DEV indicators or flight guidance, unless authorised to deviate by ATC or under emergency conditions.
8.9 Subject to subclause 8.10, the maximum permissible cross-track error/deviation is half of the navigation accuracy, namely, 0.5 NM.
8.10 Deviation from the standard mentioned in subclause 8.9 is acceptable during and immediately after turns, but only to the minimal extent that accurate cross-track information may not be provided during the turn.
Note Flight crew procedures and training should emphasise observance of turn anticipation commands and management of rate of turn.
8.11 If ATC issues a heading assignment taking the aircraft off a route, the navigation system flight plan may only be modified when:
9.1 Before an eligible aircraft takes-off, the following RNAV SID requirements must be verified:
(a) that the 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 runway and departure procedure (including any applicable en route transition) is entered in the navigation system flight plan and properly depicted;
(d) that, if an RNAV 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.
9.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.
9.3 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.
Note The altitude at which RNAV guidance begins on a given route may be higher, for example, “climb to 304 m (or 1 000 ft), then direct to X….”.
9.4 For an RNP 1 operation, an authorised method must be used to achieve an appropriate level of performance for RNP 1, for example, L/DEV indicator, navigation map display, flight director or autopilot.
9.5 The GNSS signal must be acquired before the take-off roll commences.
9.6 If:
(a) an RNP 1 SID extends beyond 30 NM from the ARP; and
(b) CDI scaling automatically changes to en route mode;
then CDI scale to +/-1 NM must be selected until termination of the SID.
10 Operating standards — flight procedures – RNAV STAR requirements
10.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.
10.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;
10.3The operator must ensure that updating will exclude a particular navaid, if so required by a route.
10.4 A route is not to be used if doubt exists as to its validity in the navigation database.
10.5 No member of the flight crew may create a new waypoint by manual entry into the RNP system.
10.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 RNAV STAR.
10.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.
10.8 All relevant published altitude and speed constraints must be observed.
11 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.
12 Flight crew knowledge and training
12.1 An RNP 1 operation may only be commenced if each member of the flight crew has knowledge of the following:
(b) the capabilities and limitations of the RNP system installed in the aircraft;
(c) the operations and airspace for which the RNP 1 system is approved to operate;
(d) the limitations of the navaids to be used for the RNP 1 operation;
(e) the required navigation equipment for operation on RNAV routes with SIDs or STARs;
(f) depiction of waypoint types (flyover and fly-by), ARINC 424 Path Terminators, and associated aircraft flight paths;
(g) contingency procedures for RNP 1 failures;
(h) the radio telephony phraseology for the relevant airspace in accordance with ICAO Doc 4444 and Doc 7030;
(i) the flight planning requirements for RNP 1 operation;
(j) RNP 1 procedure requirements as determined from chart depiction and textual description;
(k) RNP 1 system-specific information, including:
(iv) types of navigation sensors, for example, DME, IRU, GNSS, utilised by the RNP 1 system, and associated system prioritisation, weighting and logic; and
(v) aircraft configuration and operational conditions required to support RNP operations, including appropriate selection of CDI scaling (L/DEV display scaling); and
12.2 An RNP 1 operation may only be conducted if each member of the flight crew has received training in, or has equivalent experience of, RNP 1 equipment and operating procedures, including training or experience in how to do the following:
(b) verify the successful completion of RNP 1 system self-tests;
(c) initialise RNP 1 system position;
(e) retrieve and fly a SID and STAR with appropriate transition;
(f) verify waypoints and navigation system flight plan programming;
(g) resolve route discontinuities;
(h) adhere to speed and altitude constraints associated with a SID or STAR;
(i) fly direct to waypoint;
(j) fly a course or track to waypoint;
(k) intercept a course or track;
(l) vector off and rejoin a procedure;
(m) fly radar vectors and rejoining an RNAV route from a heading mode;
(n) determine cross-track error/deviation;
(o) determine allowable deviation limits and maintain flight within those limits;
(p) remove and reselect navigation sensor input;
(q) confirm exclusion of a specific navaid or navaid type;
(r) perform gross navigation error checks using conventional aids;
(s) change arrival aerodrome and alternate aerodrome;
(t) perform parallel offset function if capability exists, and advise ATC if this functionality is not available;
(u) carry out contingency procedures for RNAV failures.
13 MEL
The operator’s MEL list must identify any unserviceability that affects the conduct of an RNP 1 operation.
14 Navigation database — standards and discrepancies
14.1A navigation database for RNP 1 operations:
(ii) European Organisation for Civil Aviation Equipment (EUROCAE) document ED-76, Standards for Processing Aeronautical Data; and
Note An LOA, issued by an appropriate regulatory authority to each of the participants in the data chain, demonstrates compliance with this requirement, for example, FAA LOA issued in accordance with FAA AC 20-153 or EASA LOA issued in accordance with EASA Implementing Rule (IR) 21, Subpart G.
14.2An operator who has an RNP 1 navigation authorisation from CASA must periodically check the RNP 1 navigation database for database integrity.
Note While an LOA provides assurance of minimum standards for the supply of a navigation database, errors may still occur. All operators must conduct periodic checks to ensure database integrity.
14.3Any discrepancy in data in the operator’s navigation database must be:
15 Navigation errors
15.1 The operator must take immediate action to remedy any condition that led to, or is likely to lead to, navigation error in the course of an RNP 1 operation.
15.2 Without affecting the obligation in subclause 15.1, each of the following navigation errors or events must be reported to CASA and to AA within 72 hours of its occurrence:
(a) a lateral navigational error of at least 1 NM;
(b) a longitudinal navigational error of at least 1 NM;
15.3 Each report mentioned in subclause 15.2 must:
Note The Navigation Error Investigation Form is the approved form for reporting a navigation error or an equipment failure.
15.4 Unless subclause 15.5 applies, the operator must take the remedial action mentioned in subclause 15.3 as soon as practicable.
15.5 Without affecting subclauses 15.1 to 15.3, for this clause CASA may:
(b) notify the operator of the cause of the error and of the remedial action to be taken to prevent a recurrence of the error.
15.6 If subclause 15.5 applies, the operator must take the remedial action notified by CASA to prevent a recurrence of the error.
Appendix 5 — Requirements for use of RNP 0.3
1 RNP 0.3 navigation authorisation for I.F.R. flights
As of the date of commencement of this Order, RNP 0.3 navigation authorisation for I.F.R. flights is not yet provided for or in effect.
Appendix 6 — Requirements for use of RNP APCH
1 RNP APCH navigation authorisation for I.F.R. flights
1.1RNP APCH may only be used for PBN by an aircraft if:
(a) the operator has an RNP APCH navigation authorisation in writing from CASA; and
(b) the aircraft is equipped with:
(i) a stand-alone GNSS system; or
(ii) an FMS with GNSS input.
1.2 RNP APCH means 1 of the following:
(a) the NPA known as RNP APCH-LNAV:
(i) where lateral and longitudinal guidance is provided by GNSS SIS; and
(ii) which is flown to a MDA charted as LNAV minima on the approach plate;
Note RNP APCH-LNAV was formerly known as RNAV (GNSS).
(b) the APV known as RNP APCH-LNAV/VNAV, where:
(i) lateral and longitudinal guidance is provided by GNSS SIS; and
(ii) vertical guidance is provided by Baro-VNAV; and
Note There is, therefore, some overlap of scope and meaning between RNP APCH‑LNAV/VNAV on the one hand, and APV Baro‑VNAV on the other. See Appendix 6 for APV Baro-VNAV.
(iii) the approach is flown to a DA charted as LNAV/VNAV minima on the approach plate;
(c) the NPA known as RNP APCH-LP:
(i) where lateral and longitudinal guidance equivalent to a localiser approach is provided by SBAS augmented GNSS SIS; and
(ii) which is flown to a MDA charted as LP minima on the approach plate;
Note The NPA known as RNP APCH-LP has not yet been deployed in Australia.
(d) the APV known as RNP APCH-LPV, where:
(i) lateral, longitudinal and vertical guidance is provided by SBAS augmented GNSS SIS; and
(ii) the approach is flown to a DA charted as LPV minima on the approach plate.
Note The APV known as RNP APCH-LPV has not yet been deployed in Australia.
1.3 An RNP APCH navigation authorisation may only be issued to an operator who:
(a) applies in writing to CASA, specifying which type of RNP APCH navigation authorisation is sought; and
(c) satisfies CASA that RNP APCH operations can, and are likely to continue to, meet the requirements of this Appendix, including in relation to:
(ii) RNP APCH equipment, system performance and system functionality; and
(vii) validity and continuing integrity of the airborne navigation database; and
1.4 An RNP APCH navigation authorisation may not be issued unless the aircraft meets the requirements of this Appendix.
1.5Despite subclauses 1.3 and 1.4, an RNP APCH-LNAV/VNAV navigation authorisation may be issued to an operator who:
(a) holds both of the following:
(i) an APV Baro-VNAV navigation authorisation;
(ii) an RNP APCH-LNAV navigation authorisation; and
(b) operates an aircraft which meets the aircraft eligibility requirements for both of the following:
(i) an APV Baro-VNAV navigation authorisation;
(ii) an RNP APCH-LNAV navigation authorisation; and
(c) applies in writing to CASA for an RNP APCH-LNAV/VNAV navigation authorisation.
1.6 Despite subclauses 1.3 and 1.4, an RNP APCH-LNAV navigation authorisation and an RNP APCH-LNAV/VNAV navigation authorisation (the respective authorisations) may be issued to an operator who:
(a) holds an RNP AR APCH navigation authorisation; and
(b) operates an aircraft which meets the aircraft eligibility requirements for an RNP AR APCH navigation authorisation; and.
(c) applies in writing to CASA for the respective authorisations.
1.7An RNP APCH navigation authorisation may be issued subject to conditions if CASA considers this is necessary in the interests of safety.
1.8 It is a condition of the issue of a navigation authorisation that the applicable operational requirements of this Appendix are complied with after the issue of the authorisation.
1.9 It is a condition of the issue of a navigation authorisation that where an operational check, consideration, procedure or task (however described) is required under this Appendix, the operator must ensure that it is performed, given, followed or carried out, as the case may be.
Note The check, consideration, procedure or task may in practice be performed etc. by the pilot in command, other members of the flight crew, the despatch officer or other operational personnel. However, legal responsibility for compliance is placed on the operator who must ensure that the performance etc. occurs in accordance with his or her established procedures.
(a) aircraft airworthiness documents which satisfy CASA that the aircraft is equipped for RNP APCH operations, for example, the AFM, the AFM Supplement or OEM service letters;
(b) a detailed description of relevant aircraft equipment for RNP APCH operations, including a configuration list of the components and equipment;
(c) a detailed description of the proposed flight crew training for RNP APCH operations, including a copy of the training syllabus, for approval by CASA;
(d) a detailed description of the operating procedures to be used for RNP APCH operations (including flight planning and flight procedures) supported by relevant copies of, or extracts from, the following:
(e) copies of the sections of the MEL applicable to RNP APCH operations;
(f) a detailed description of the maintenance program used to ensure the continuing airworthiness of the aircraft for RNP APCH operations;
(g) a detailed description of the method used to ensure the continuing integrity of the airborne navigation database;
(h) if requested in writing by CASA — a copy of any relevant document referred to in any of the documents mentioned in paragraphs (a) to (g).
An aircraft is eligible for RNP APCH operations if:
(a) the AFM, an AFM Supplement, or OEM service letter states that the aircraft navigation system is approved for RNP 0.3 approach operations with GNSS updating; or
(b) the aircraft is equipped with a navigation system which meets the requirements for PBN type RNP AR navigation authorisation; or
(c) the aircraft is equipped with a GNSS stand-alone system approved for NPA operations in accordance with AC 21-36 (TSO‑C129a/ETSO-C129a Class A1 or E/TSO-C146 Class Gamma and operational Class 1, 2 or 3); or
(d) the aircraft is equipped with a multi-sensor system (for example, FMS) with GNSS equipment that is:
(i) in accordance with TSO-C129/ETSO-C129 Class B1, C1, B3, C3 or E/TSO-C145 Class 1, 2 or 3 or TSO-C196 ( ); and
(ii) approved for approach operations by virtue of being in accordance with AC 21-36 and AC 21-37.
4 RNP APCH system performance
4.1The system must meet the performance, monitoring and alerting requirements for RNP APCH operations as stated in ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part C, Chapter 5, Implementing RNP APCH.
5 RNP APCH system functionality
5.1 Subject to subclause 5.2, 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 5, Implementing RNP APCH.
Note Guidance provided in AC 21-36, Global Navigation Satellite System (GNSS) Equipment: Airworthiness Guidelines, is also relevant.
5.2 An alternative means for the display of cross-track information is as follows:
(a) the aircraft’s position relative to the flight path must be displayed in the pilot’s primary field of view;
(b) there must be display of numeric cross-track deviation in 1/10th NM or less which may be outside the pilot’s primary field of view;
(c) the flight crew must consist of at least 2 pilots;
(d) the pilot not flying must be able to monitor the numeric cross-track deviation;
(e) crew procedures (including callouts) must be implemented to ensure that each member of the operating crew can perform all normal duties in addition to monitoring cross-track deviation;
(f) CASA must have conducted a satisfactory operational evaluation of the displays and crew procedures.
5.3 The requirement for the display of lateral position relative to the desired path is:
(a) a digital indication in 1/10th NM or less; or
(b) a relative indication which allows the pilot to determine deviation in proportion to a known indicator scale.
5.4 Where the minimum flight crew is 2 pilots, there must be a means for the pilot not flying to accurately verify the desired path and the aircraft position relative to that path.
5.5 Navigation system failure or alert must be displayed in the pilot’s primary field of view for the following:
(a) loss of GNSS integrity or integrity monitoring capability; or
(b) failure of a GNSS sensor.
5.6 The RNP APCH system must have the capability to determine:
(a) that GNSS positioning is active; or
(b) if the RNP system is one in which an alert is not immediately enunciated when GNSS updating is not available — that the current navigation performance of the system is adequate.
6 Operational standards — flight planning – general
6.1 Before an RNP APCH operation commences, consideration must be given to matters that may affect the safety of the operation, including the following:
(a) whether the aircraft, and each member of the flight crew, has relevant authorisations for RNP APCH;
(b) whether, if a navigation database is used, it is current and appropriate for the region of operation and includes the navaids and waypoints required for the route;
6.2 If the aircraft’s essential RNP APCH equipment is functioning properly, the PBN capability of the aircraft must be indicated in the flight plan.
7.1As part of flight planning, a prediction for GNSS integrity availability must be obtained.
7.2For an RNP APCH operation navigating with SBAS receivers, a check must be made for GNSS integrity availability in areas where SBAS is unavailable.
7.3If a continuous loss of the GNSS integrity function for more than 5 minutes is predicted for any part of an RNP APCH operation, the flight plan must be revised, for example, by delaying the departure time or planning a different route.
7.4Subclauses 7.1, 7.2 and 7.3 do not apply to an aircraft whose RNP system can achieve LNAV accuracy less than 0.3 NM using requisite GNSS satellites.
8 Operating standards — flight procedures
8.1 An operator must ensure that flight procedures described in this clause are complied with.
8.2 The following must be checked and confirmed:
(a) the waypoint sequence;
(b) the reasonableness of the tracks and distances;
(c) the VPA;
(d) that the GNSS sensor is used for position computation;
(e) if barometric aiding is used — that the current aerodrome barometric altimeter setting is entered.
8.3 The operator must ensure that the appropriate displays are selected to permit monitoring of the aircraft’s:
(a) approach path; and
(b) position relative to the approach path (cross-track and, where applicable, V/DEV).
8.4 The aircraft is to be established on the final approach course no later than the FAF.
8.5 Descent in the final segment is not to be commenced unless:
(a) the appropriate approach mode is annunciated, namely, LNAV, LNAV/VNAV, LP or LPV; and
(b) RNP 0.3 is selected and available.
8.6 The approach procedure is to be discontinued if:
(a) the navigation system display is flagged invalid; or
(b) there is a loss of integrity alert; or
(c) the integrity alerting function is not available; or
(d) FTE is excessive.
8.7 Subject to subclause 8.9, standard for limitation of cross-track error/deviation is:
(a) 0.5 NM for the initial segment, the intermediate segment and a missed approach; and
(b) 0.15 NM for the final approach segment.
8.8 A missed approach must be conducted if, in the final approach segment, the cross-track error/deviation equals or exceeds:
(a) 0.3 NM; or
(b) if RNP is equal to 0.3 NM — 1 x RNP; or
(c) if the aircraft is equipped with serviceable automated cross-track error alerting — when a cross-track error alert is received.
8.9 Deviation from the standard mentioned in subclause 8.7 is acceptable during and immediately after turns, but only to the minimal extent that accurate cross-track information may not be provided during the turn.
Note The use of a flight director or autopilot is recommended.
8.10Subject to subclause 8.11, the standard for V/DEV is:
(a) for RNP APCH-LNAV/VNAV after passing the VIP — + 75 feet, or a different value approved by CASA; or
(b) for RNP APCH-LPV — + ½ scale defection from the FAF.
8.11Transient deviation from the standard mentioned in subclause 8.10 is acceptable during aircraft configuration changes.
9 Contingency procedures for performance failure
The operator must ensure that the flight crew have and implement contingency procedures for a loss of RNP APCH capability during the approach.
10 Flight crew knowledge and training
10.1 An RNP APCH operation may only be commenced if each member of the flight crew has knowledge of the following:
(a) the requirements for RNP APCH authorisation;
(b) GNSS and RNP principles;
(c) navigation system operation;
(d) IAL procedure characteristics as determined from chart depiction and textural description;
(e) flight path construction, including waypoint types (flyover and fly-by), path terminators and other elements;
(f) for FMS/MMR systems, the method used to derive displayed position, including input from navigation sensors (for example, IRU, GNSS, DME) and system prioritisation/weighting/logic;
(g) functional integration with other aircraft systems;
(h) display symbology and interpretation;
(i) navigation equipment necessary to conduct RNP APCH operations;
Note Pilots need to be aware that the type of navigation equipment capable of RNP APCH procedures includes stand-alone and FMS installations and that the conduct of an RNP APCH varies accordingly.
(j) levels of automation, mode annunciations, changes, alerts, reversions and degradation;
(k) speed constraints;
(l) altitude limitations;
(m) operator policy on use of automation, including methods to minimise cross‑track error;
(n) radio telephony phraseology for RNP APCH applications.
10.2 An RNP APCH operation may only be conducted if each member of the flight crew has received training in RNP APCH equipment and operating procedures, including how to do the following:
(a) navigation equipment operation through the operating procedures, including:
(i) navigation database currency verification; and
(ii) system self-tests; and
(iii) position initialisation; and
(iv) retrieval, loading and execution of an RNP APCH;
(b) approach review, verification of waypoint sequence and navigation system flight plan;
(c) display and equipment set-up;
(d) management of route discontinuities;
(e) normal approach and landing;
(f) missed approach and holding;
(g) flying direct to a waypoint;
(h) intercepting an initial or intermediate segment of an approach;
(i) turn anticipation, including ground speed and altitude effects;
(l) monitoring procedures for each phase of flight;
(m) changing approach, destination or alternate;
(n) conducting contingency procedures following RNP system failure.
10.3 Without affecting the requirements of subclauses 10.1 and 10.2, before conducting an RNP APCH operation, each member of the flight crew must have sufficient ground training and flight training (whether in actual or simulated flight) in normal and abnormal operations to achieve operational competency.
11 MEL
The operator’s MEL must identify any unserviceability that affects the conduct of an RNP APCH operation.
12 Continuing airworthiness
12.1 The operator must have procedures in force to ensure the continuing airworthiness of the aircraft for RNP APCH operations.
12.2 The operator must ensure that the aircraft equipment and configuration control are consistent with:
(a) RNP APCH capability; and
12.3 The operator must ensure that engineering and maintenance personnel are trained in, and familiar with, RNP APCH airworthiness requirements.
13 Navigation database — standards and discrepancies
13.1A navigation database for RNP APCH operations:
(ii) European Organisation for Civil Aviation Equipment (EUROCAE) document ED-76, Standards for Processing Aeronautical Data; and
Note An LOA, issued by an appropriate regulatory authority to each of the participants in the data chain, demonstrates compliance with this requirement, for example, FAA LOA issued in accordance with FAA AC 20-153 or EASA LOA issued in accordance with EASA Implementing Rule (IR) 21, Subpart G.
13.2An operator who has an RNP APCH navigation authorisation from CASA must periodically check the RNP APCH navigation database for database integrity.
Note While an LOA provides assurance of minimum standards for the supply of a navigation database, errors may still occur. All operators must conduct periodic checks to ensure database integrity.
13.3Any discrepancy in data in the operator’s navigation database must be:
(b) before further operational use — resolved by:
(ii) prohibition of the route or procedure; or
Appendix 7 — Requirements for use of RNP AR
1 RNP AR navigation authorisation for I.F.R. flights
1.1 An RNP AR may only be used for PBN by an aircraft if the operator has an RNP AR navigation authorisation in writing from CASA.
1.2 An RNP AR may only be used for PBN by an aircraft for instrument approach and departure procedures that are supported by:
(a) a GNSS LNAV system; and
(b) an FMS supported by suitable flight control, cockpit control and display systems; and
(c) a Baro-VNAV system.
1.3 An RNP AR navigation authorisation is for 1 or more of the following RNP AR operations:
(a) RNP AR APCH (ICAO);
(b) RNP AR APCH (Proprietary);
(c) RNP AR DEP (ICAO);
(d) RNP AR DEP (Proprietary);
(e) RNP EOSID (Proprietary).
Note RNP AR APCH procedures and RNP AR DEP procedures operate to ICAO or proprietary design criteria. RNP AR EOSID procedures operate to proprietary design criteria only. Proprietary design criteria are more demanding than ICAO design criteria.
1.4An RNP AR navigation authorisation may only be issued to an operator who:
(a) applies in writing to CASA, specifying which type of RNP AR navigation authorisation is sought; and
(b) supplies the documents mentioned in clause 3; and
(c) satisfies CASA that RNP AR operations for the navigation authorisation sought can, and are likely to continue to, meet the requirements of this Appendix, including in relation to the following:
(ii) RNP AR equipment, system performance and system functionality;
(iv) approved flight crew training and recency;
(vi) aircraft and RNP system maintenance;
(vii) continued integrity of the airborne navigation database;
(viii) navigation error reporting procedures;
(ix) FOSA.
1.5 An RNP AR navigation authorisation may not be issued unless the aircraft meets the requirements of this Appendix.
1.6 Despite subclauses 1.4 and 1.5:
(a) an RNP AR APCH (ICAO) navigation authorisation may be issued to an operator who:
(i) holds an RNP AR APCH (proprietary) navigation authorisation; and
(ii) complies with subclause 1.8; and
(b) an RNP AR DEP (ICAO) navigation authorisation may be issued to an operator who:
(i) holds an RNP AR DEP (proprietary) navigation authorisation; and
(ii) complies with subclause 1.8; and
1.7Despite subclauses 1.4 and 1.5, an RNP AR DEP navigation authorisation, whether ICAO or proprietary, may be issued to an operator who:
(a) holds an RNP AR EOSID (Proprietary) navigation authorisation; and
(b) complies with subclause 1.8.
1.8For subclauses 1.6 and 1.7, the operator must:
(a) operate an aircraft which meets the aircraft eligibility requirements for the navigation authorisation sought; and
(b) apply in writing to CASA for the navigation authorisation sought.
2 Conditions for RNP AR operations
2.1An RNP AR navigation authorisation may be issued subject to conditions if CASA considers this is necessary in the interests of safety.
2.2It is a condition of the issue of a navigation authorisation that the applicable operational requirements of this Appendix are complied with after the issue of the authorisation.
2.3It is a condition of the issue of a navigation authorisation that where an operational check, consideration, procedure or task (however described) is required under this Appendix, the operator must ensure that it is performed, given, followed or carried out, as the case may be.
Note The check, consideration, procedure or task may in practice be performed etc. by the pilot in command, other members of the flight crew, the despatch officer or other operational personnel. However, legal responsibility for compliance is placed on the operator who must ensure that the performance etc. occurs in accordance with his or her established procedures.
3 Application — documents
(a) aircraft airworthiness documents which satisfy CASA that the aircraft is equipped for RNP AR operations, for example, the AFM, the AFM Supplement or OEM service letters;
(b) a detailed description of relevant aircraft equipment for RNP AR operations, including a configuration list of the components and equipment;
(c) a detailed description of the proposed flight crew training for RNP AR operations, including a copy of the training syllabus, for approval by CASA;
(d) a detailed description of the operating procedures to be used for RNP AR operations (including flight planning and flight procedures) supported by relevant copies of, or extracts from, the following:
(e) a FOSA as set out in clause 4;
(f) copies of the sections of the MEL applicable to RNP AR operations;
(g) a detailed description of the maintenance program used to ensure the continuing airworthiness of the aircraft for RNP AR operations;
(h) a detailed description of the method used to ensure the continued integrity of the airborne navigation database;
(i) if requested in writing by CASA — a copy of any relevant document referred to in any of the documents mentioned in paragraphs (a) to (h).
4 FOSA
4.1An operator must conduct a FOSA in each of the following circumstances:
(a) before applying to CASA for an RNP EOSID;
(b) before conducting an RNP AR operation that requires an RNP value of less than 0.3NM;
(c) before conducting an RNP AR operation in which it is planned to have at least 1 engine inoperative.
4.2For paragraph 4.1 (a), the operator’s application for an RNP EOSID must be accompanied by a copy of the FOSA.
Note The FOSA is to be consistent with ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part C, Chapter 6, Implementing RNP AR APCH. (See also the definition in paragraph 3.4 of this Order.).
4.3 The FOSA must set out details of the methods used by the operator to manage the risks associated with non-normal events arising from RNP AR operations.
4.4 The FOSA must include the mitigations implemented by the operator to reduce non-normal safety risks to the level of “As Low as Reasonably Practical”.
Note 1 Suitable methods to mitigate non-normal safety risks include flight crew procedures (including contingency procedures), flight crew training, engineering modifications, operating limitations, and procedure design.
Note 2 Additional guidance on provision for non-normal operations is contained in FAA AC 120-29A, Criteria for Approval of Category I and Category II Weather Minima for Approach.
5 Aircraft eligibility
An aircraft is eligible for RNP AR operations only if:
(a) the OEM has documented that the aircraft is capable of RNP AR approach operations, or RNP AR departure operations or both RNP AR approach and departure operations; and
(b) the aircraft meets the requirements for RNP AR operations in accordance with ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part C, Chapter 6, Implementing RNP AR APCH; and
(c) for an aircraft equipped with GNSS sensors which comply with TSO‑C129a or an equivalent standard, the following minimum equipment:
(i) 2 FMS;
(ii) 2 GNSS sensors (which may be included in an MMR);
(iii) 1 IRS;
(iv) 2 flight directors;
(v) 2 flight mode annunciators;
(vi) 2 RADALTs;
(vii) duplicated primary flight and navigation displays;
(viii) duplicated alternating current power source (for which an APU may be used);
(ix) 1 autopilot channel;
(x) 1 TAWS appropriate to the class of operation; and
(d) for an aircraft equipped with GNSS sensors or GNSS receivers which comply with TSO-C145a or TSO-C146a or an equivalent standard, the following minimum equipment:
(i) 2 FMS;
(ii) 2 GNSS sensors or receivers (and which may be included in an MMR);
(iii) 1 flight director;
(iv) 1 flight mode annunciator;
(v) 1 RADALT;
(vi) duplicated primary flight and navigation displays;
(vii) duplicated alternating current power source (for which an APU may be used);
(viii) 1 autopilot channel;
(ix) 1 TAWS appropriate to the class of operation; and
(e) all modifications, options or particular part numbers required by the manufacturer are installed in, or on, the aircraft.
6 RNP AR system performance
6.1 The system must meet the performance, monitoring and alerting requirements for RNP AR operations as stated in ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part C, Chapter 6, Implementing RNP AR APCH.
6.2 Positioning data from non-GNSS navigation sensors may be integrated with GNSS data if:
7 RNP AR system functionality
7.1Subject to this clause, an eligible aircraft’s RNP AR 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 6, Implementing RNP AR APCH.
7.2 The system must be capable of executing leg transitions and maintain tracks consistent with an RF leg.
Note ICAO Doc 9613 includes this requirement only where approaches are designed with RF legs. However, RNP AR procedures designed in accordance with proprietary design criteria for use by operators of Australian aircraft are dependent upon RF leg capability.
7.3 The following requirements must be complied with for the display of cross-track deviation, namely, within the pilot’s primary field of view there must be:
(a) a suitably scaled CDI; and
(b) a map display with a numeric indication of cross-track deviation in 1/100th NM or less.
7.4 Despite subclause 7.3, for an RNP AR approach or departure with an RNP of not less than 0.3, there must be within the pilot’s primary field of view:
(a) a map display; and
(b) a numeric display of cross-track deviation of 1/10th NM or less.
7.5 Despite subclause 7.3, for an RNP AR approach or departure with an RNP of 0.3 or less, the means by which the flight crew monitor and manage cross-track deviations must be:
(a) demonstrated by the operator to be adequate for all normal and non‑normal conditions within the FTE appropriate to the RNP to be used; and
(b) arrived at only after operator consideration of relevant factors, including the following:
(i) information displayed in the pilot’s primary field of view;
(ii) information displayed outside the pilot’s primary field of view;
(iii) the resolution, scaling, numeric and other cross-track indications available;
(iv) the predictive display of aircraft flight path;
(v) the crew procedures used to monitor and manage FTE;
(vi) operator procedures for initiation of a missed approach;
(vii) information provided by the aircraft manufacturer;
(viii) simulator demonstration of FTE management.
7.6 The navigation system is not required to provide an alert to the flight crew when GNSS updating is lost, provided there is an alert when the selected RNP no longer meets the criteria for continued navigation.
7.7 Subject to subclause 7.8, the system must provide LNAV guidance throughout a go-round conducted at any point in the approach.
Note This function is commonly referred to as TOGA to LNAV.
7.8 Where continuous LNAV guidance is not available, an alternative means is acceptable only if:
(a) each flight crew member receives specific training in accurate track‑keeping during a go-round; and
(b) the operator demonstrates to CASA that the lateral track can be accurately maintained under all normal and non-normal conditions.
8 Operational standards — flight planning – general
Operating procedures for RNP AR must be in accordance with clauses 9 to 23 of this Appendix.
Note The operating procedures contained in ICAO Doc 9613, Performance-based Navigation (PBN) Manual, Volume II, Part C, Chapter 6, Implementing RNP AR APCH do not apply and are replaced by the operating standards in clauses 9 to 23 of this Appendix.
9 RNP availability prediction
9.1Subject to subclause 9.2, before an RNP AR operation commences, availability of an RNP service must be predicted, taking into account relevant matters, including the following:
(a) aerodrome location;
(b) approach or departure operation;
(c) terrain masking;
(d) satellite serviceability (NOTAMs);
(e) installed avionics algorithms.
9.2Subclause 9.1 does not apply if the aircraft can achieve LNAV accuracy that is at least equal to that required for the RNP AR operation using requisite GNSS satellites.
10 Radio updating
If radio updating may degrade the GNSS position, radio updating must be inhibited before commencement of the RNP AR operation.
11 Procedure selection
An approach or departure procedure must be retrievable by procedure identifier from the aircraft navigation database.
12 Procedure verification
12.1 Before an RNP AR operation commences, the following must be verified:
(a) that the correct approach or departure procedure has been selected;
(b) that the cockpit electronic displays correctly replicate the route, the waypoint sequence and significant operational details shown on the published IAL procedure chart.
12.2 However, paragraph 12.1 (b) must not be carried out for an RNP AR operation that is an EOSID.
Note Verification that cockpit electronic displays correctly replicate the route, the waypoint sequence and significant operational details shown on the published IAL procedure chart is specifically prohibited for an EOSID in order to avoid inadvertent activation of the wrong route.
13 Procedure modification
The flight crew must not modify the loaded procedure.
14 Vectoring
When vectored by an air traffic service, a procedure may be intercepted at a position inside the IAF but not later than the VIP. However, descent on an approach procedure below the minimum vectoring altitude is not permitted until the aircraft is established within the vertical and lateral tolerances of the procedure, and the appropriate navigation mode is engaged.
15 Required equipment to be serviceable
Before an RNP AR operation commences, the required equipment must be serviceable and its serviceability confirmed.
Note A list of required equipment should be readily available to the flight crew on the flight deck.