TELEPHONE: 1300-306-630 (local call - Aust wide, except from mobile phone) FAX: 02 6268 5111 1. INTRODUCTION 1.1 This AIP SUP amends AIP to remove navigation approvals that are no longer able to be used under CAO 20.91 from 13 July 2014. 2. BACKGROUND 2.1 CAO 20.91 was published and effective on the 13 July 2012. The Order provided for new performance based navigation approvals and the transition of some existing approvals. 2.2 Approvals previously issued under B-RNAV, P-RNAV, US-RNAV Type A or Type B, GPS Oceanic, Australian RNAV (AUSEP) and GPSRNAV, ceased to be issued from July 2012 and are no longer able to be used from 13 July 2014. 3. CHANGE DESCRIPTION AUSTRALIA AERONAUTICAL INFORMATION SERVICE AIRSERVICES AUSTRALIA GPO BOX 367 CANBERRA ACT 2601 E-mail: AIM.Editorial@airservicesaustralia.com AIP SUPPLEMENT (SUP) H43/14 DATE: 13 JUL 14 CESSATION OF NAVIGATION APPROVALS UNDER CAO 20.91 3.1 Effective from 13 July 2014, amend the following paragraphs of AIP: AIP GEN 1.5 para 8.5.5.1 remove CAO 20.91 transition information from note. AIP GEN 1.5 para 8.5.5.4 add C196 as an allowable airworthiness standard for IFR Area Navigation, remove CAO 20.91 transition information from RNAV (GNSS) Non- Precision Approach note.
() Page 2 of 2 AIP ENR 1.1 para 19.12 remove GPSRNAV and GPSOCEANIC from the list of tolerances used to avoid controlled airspace or restricted areas. AIP ENR 1.4 para 2.3.4 delete CAO 20.91 transitional arrangements. AIP ENR 1.10 section 3.3 update flight planning guidance to remove reference to AUSEP, GPSRNAV and GPSOCEANIC. Insert guidance for flight planning RNP1. AIP ENR 1.10 Appendix 2 Item 10 Note and Item 18 NAV/ remove guidance for GPSRNAV and GPSOCEANIC. 4. CANCELLATION 4.1 This AIP SUP will be cancelled when the amendments are incorporated into AIP Book, expected 21 August 2014. 5. DISTRIBUTION 5.1 By Airservices website only. Appendix: 1. AIP Changes
1. AIP Changes GEN 1.5 8.5.5 IFR Operations 8.5.5.1 GNSS may be used under the IFR in the following applications: a. DR Substitute. Pilots operating under the IFR may use GNSS in lieu of DR navigation techniques for that part of the flight that is outside the rated coverage of terrestrial navigation aids. Note: This is not an area navigation approval. b. IFR Area Navigation. Pilots operating in Australian domestic airspace under the IFR may use GNSS for position fixing and long range navigation in accordance with ENR1.1 Section 19., operations on designated area navigation routes, and application of area navigationbased LSALT. It may also be used for deriving distance information for en route navigation, traffic information and ATC separation. GNSS may also be used as a navigation aid to determine distance information for SID, STAR and instrument approach procedures where the use of GPS is specified on the IAL chart. Further, GNSS may be used to meet the IFR requirements for radio navigation systems specified in GEN 1.5 Section 2. Note: ATC may apply area navigation-based separation standards to aircraft meeting the requirements for IFR area navigation. c. RNAV(GNSS) Non-precision Approach (or RNP APCH). Pilots operating under the IFR may use GNSS as an approach navigation aid to determine distance and track information for RNAV (GNSS) Non-precision Approach procedures. Note: RNAV (GNSS) NPA and RNP APCH-LNAV are the same. d. Oceanic Area Navigation. CASA may issue an approval for an operator to use GNSS as an en route navigation aid in oceanic and remote continental areas outside the boundaries of Australian domestic airspace (see ENR 2.2 para 3.1). Standard conditions for these approvals may be found in CAO 20.91. e. GBAS Landing System (GLS). CASA may approve an operator to use GNSS GBAS as a precision approach navigation aid. Page 1 of 7
8.5.5.4 The following table summarises the airworthiness and operational requirements for IFR applications of GNSS: Application DR Substitute IFR Area Navigation GNSS APPLICATIONS IFR Operational Privileges/ Requirement 1. GNSS receiver operated in accordance with the manufacturer s operating instructions, and any additional instructions specified by the operator. 1.GNSS receiver operated in accordance with the manufacturer s operating instructions, and any additional instructions specified by the operator. 2. Flight crew meet appropriate GNSS qualification and recency requirements. 3. For SID, STAR and approach procedures, other than those titled RNAV (or RNP) procedures, primary track guidance must be provided by the navaid (NDB, VOR, LOC or ILS) nominated on the IAL chart. Page 2 of 7 Airworthiness Requirement 1. GPS receiver certified to TSO-C129, C129a, C145a, C146a or equivalent standard approved by CASA. 2. GNSS receiver fitted in accordance with AC21-36 or applicable equivalent standard at the time of fitment and automatic barometric aiding options functional. 3. Manufacturer s operating instructions, and any additional instructions specified by the operator carried on board the aircraft. 1.GPS receiver certified to TSO C129, C129a, C145a, C146a, C196 or equivalent standard approved by CASA. 2. GNSS receiver fitted in accordance with AC21-36 or applicable equivalent standard at the time of fitment and automatic barometric aiding options functional. 3. Manufacturer s operating instructions, and any additional instructions specified by the operator carried on board the aircraft.
RNAV (GNSS) Nonprecision Approach Note: RNAV (GNSS) NPA and RNP APCH- LNAV are the same. Oceanic Area Navigation GLS 1. GNSS receiver operated in accordance with the manufacturer s operating instructions, and any additional instructions specified by the operator. 2. Flight crew meet appropriate RNAV(GNSS)(or RNP APCH) qualification and recency requirements. 3. Unless using a TSO- C145a, C146a or C196 receiver and a valid prediction of approach FDE availability, at both the destination and alternate, if required, provision for an alternate aerodrome may not be based on RNAV (GNSS) (or RNP APCH) approach capability. 4. If a TSO-C129 or a C129a receiver is used, an alternate instrument approach utilising ground based navigation aids must be available. Requires an approval issued by CASA. Requires an approval issued by CASA. 1. GPS receiver certified to TSO-C129, C129a, C145a, C146a or equivalent standard approved by CASA. 2. GNSS receiver fitted in accordance with AC21-36 or applicable equivalent standard at the time of fitment and automatic barometric aiding options functional. 3. Manufacturer s operating instructions, and any additional instructions specified by the operator carried on board the aircraft. As detailed in an approval issued by CASA. As detailed in an approval issued by CASA. ENR 1.1 19.12 Avoiding Controlled Airspace The pilot in command of an aircraft operating in Class G airspace, or to the VFR in Class E airspace, must apply appropriate tolerances to the flight path to ensure that controlled airspace, or restricted areas, are not infringed. Note: aircraft within controlled airspace or a restricted area maybe operating up to the boundary. Page 3 of 7
In calculating whether an intended flight path may infringe controlled airspace, the following navigational tolerances must be applied to the intended flight path depending on method of navigation used. These tolerances may be rounded up to the nearest half degree for practical purposes: NDB ±6.9 VOR/TACAN ±5.2 DR ±12 Note: For DR tracking ±9 may be used where initial track guidance has been provided by NDB, VOR or TACAN and there is no subsequent change in track. RNAV5/RNAV10(RNP10)/RNP4 ±14NM RNP2 ±7NM VISUAL (POWERED AIRCRAFT) 0-2,000 AGL ±1NM ( ±2NM by night) 2,001-5,000 AGL ±2NM ( ±3NM by night) 5,001-10,000 AGL ±4NM ( ±5NM by night) VISUAL (GLIDERS) 0-10,000 ±5NM VISUAL (ALL AIRCRAFT) 10,001 - FL200 ±8NM FL205 - FL300 ±12NM FL305 - FL400 ±16NM ENR 1.4 Delete para 2.3.4 including table. ENR 1.10 3.3 GNSS Notification 3.3.1 No indication on the flight notification form is required for Visual Navigation or DR Substitute applications of GNSS. 3.3.2 Pilots able to use GNSS should flight plan for the following navigation applications: a. Night VFR Area Navigation or IFR Area Navigation should insert G and Z in Field 10 and NAV/RNP2 in Field 18 of the flight notification form. Page 4 of 7
b. RNAV(GNSS) Non--precision Approach (or RNP APCH- LNAV) should insert: G and R in Field 10 and PBN/S1 or PBN/S2 as appropriate in Field 18 of the flight notification form. c. Area Navigation to RNP1 for SID or STAR should insert G and R in Field 10 and PBN/O2 in Field 18 of the flight notification form. 3.3.3 Pilots of aircraft able to use GNSS for Oceanic Area Navigation applications should insert G and R in Field 10 and PBN/L1 in Field 18 of the flight notification form. 3.3.4 Pilots of aircraft that will use GNSS for GLS applications should insert G and Z in field 10 and NAV/GLS in field 18 of the flight notification form. 3.3.5 Pilots of aircraft able to conduct RNP AR approaches and departures should insert G and R in Field 10 and PBN/T1 and OPR/ in Field 18 of the flight notification form. 3.3.6 Pilots of aircraft able to use inertial systems for area navigation should insert I and R in Field 10 and PBN/B1 or PBN/B5 as appropriate in Field 18 of the flight notification form. APPENDIX 2 ATS FLIGHT NOTIFICATION - USER GUIDE Item 10 - Equipment and Capabilities Circle to indicate the presence of serviceable equipment that the pilot is qualified to use and where applicable, has authorisations from the State of Registry: N no COM/NAV/Approach Aid equipment for the route to be flown or the equipment is unserviceable. S standard COM/NAV/Approach Aid equipment of VHF/ILS/VOR. A GBAS Landing System B LPV (APV with SBAS) C LORANC D DME E1 FMC WPR ACARS E2 D--FIS ACARS E3 PDC ACARS Page 5 of 7
F ADF G GNSS H HFRTF I Inertial NAV J1 CPDLC ATN VDL Mode 2 J2 CPDLC FANS 1/A HFDL J3 CPDLC FANS 1/A VDL Mode A J4 CPDLC FANS 1/A VDL Mode 2 J5 CPDLC FANS 1/A SATCOM (INMARSAT) J6 CPDLC FANS 1/A SATCOM (MTSAT) J7 CPDLC FANS 1/A SATCOM (Iridium) K MLS L ILS M1 ATC RTF SATCOM (INMARSAT) M2 ATC RTF (MTSAT) M3 ATC RTF (Iridium) O VOR R PBN Approved T TACAN U UHF RTF V VHFRTF W RVSM Approved (except STATE formation flights) X MNPS Y VHF with 8.33 khz channel spacing capability Z other equipment or capabilities. Note 1: If the letter Z is used, specify the other equipment carried or other capabilities in Item 18, preceded by COM/, NAV/ and/or DAT/, as appropriate. Note 2: If the letter R is used, specify the performance based navigation levels that can be met in Item 18 following the indicator PBN/. Amend only the NAV/ entry under Item 18: Item 18 Enter Other information such as navaid training, block surveys and other plain language remarks of significance. Note: ACARS and TCAS or ACAS are not required to be included in the flight notification. Page 6 of 7
Enter information in the sequence shown below: NAV/ Followed by navigation equipment or capabilities other than those listed for Item 10a or under PBN/. Use when Z has also been entered in Item 10a: eg, NAV/RNP2. Page 7 of 7