CASA 05/09 Instructions use of RNAV (GNSS) approaches by RNP-capable aircraft (Cth)

Instrument number CASA 05/09

I, MICHAEL DAVID QUINN, Deputy Chief Executive Officer, Operations, a delegate of CASA, make this instrument under regulation 179A of the Civil Aviation Regulations 1988.

[Signed M. D. Quinn]

Mick Quinn
Deputy Chief Executive Officer
Operations

12 January 2009

Instructions — use of RNAV (GNSS) approaches by RNP-capable aircraft

1          Duration

            This instrument:

(a)   commences on the day after it is registered; and

(b)   stops having effect at the end of January 2011.

2          Application

            This instrument applies to the conduct of RNAV (GNSS) approaches by

            Qantas Airways Limited, Aviation Reference Number 216147

            using Airbus A380 aircraft with an RNP-capable RNAV system.

3          Instructions

            I issue the instructions in Schedule 1.

4          Definitions

            In this instrument:

AFM means the aircraft flight manual.

approved navigation database means a navigation database on a medium approved by the manufacturer of the aircraft as suitable for use with the aircraft.

FAF means final approach fix.

FCOM means the flight crew operations manual.

FLS means the FMS landing system, a function that provides the flight crew with cockpit guidance to fly a non-precision approach in an ILS look-alike way.

FMA means flight mode annunciator.

FMS means the aircraft’s flight management system.

GNSS means the Global Navigation Satellite System, a satellite navigation system used by a pilot on board an aircraft to determine position from satellite data.

GPS means theUnited States Government satellite navigation system known as the Global Positioning System.

LSALT means lowest safe altitude.

MSA means minimum safe altitude.

navigation database means electronic data such as waypoints, altitudes, constraints and similar details as coded and entered into the FMS from time to time.

operator means Qantas Airways Limited (Qantas), Aviation Reference Number 216147.

RNAV (GNSS) approach means an area navigation instrument approach procedure.

RNP means the required navigation performance as displayed to the pilot in command by the FMS.

RNP-capable RNAV system means an area navigation system, fitted to an aircraft, which the AFM states is capable of meeting RNP 0.3 requirements.

Schedule 1          Instructions

1          Use of RNP capability for RNAV (GNSS) approaches

            The pilot in command of an aircraft operating under the I.F.R. may use an RNP‑capable RNAV system in accordance with these instructions as a non‑precision approach I.F.R. navigation aid for a published RNAV (GNSS) approach procedure, including a related missed approach procedure.

2          Requirements

   (1)     The AFM must contain a statement that the aircraft is capable of meeting the RNP 0.3 requirements.

   (2)     The operator must maintain and validate the FMS navigation database in accordance with the manufacturer’s procedures.

   (3)     The operator must:

(a)   have a means of predicting the availability and integrity of GPS satellites; and

(b)   make the relevant information available to flight crews before flight.

   (4)     Subject to these instructions, the pilot in command must ensure that RNAV (GNSS) approaches are flown in accordance with the procedures published in the FCOM and other Qantas A380 operations manuals and instructions.

   (5)     RNAV (GNSS) must not be used to satisfy any of the requirements for alternate aerodrome planning.

   (6)     RNAV (GNSS) must not be used as a navigation reference for flight below the LSALT or MSA, except in accordance with an RNAV (GNSS) approach.

   (7)     RNAV (GNSS) approach charts must be verified by the operator before use.

3          Procedures

   (1)     The pilot in command must ensure that RNAV (GNSS) approaches are flown in accordance with authorised instrument approach procedures validated by the operator.

   (2)     The pilot in command must use, wherever practicable, a managed approach instead of a selected approach. The pilot in command must ensure that all approach chart altitude requirements are complied with.

   (3)     If the pilot in command elects to fly the aircraft using the FLS function, he or she must check that:

(a)   the slope of the FLS beam is no less than the slope depicted on the RNAV (GNSS) approach chart; and

(b)   the course of the FLS beam is the same as the course depicted on the RNAV (GNSS) approach chart; and

(c)   the anchor point of the FLS beam is at the runway threshold, if continued use of the FLS deviation scales for advisory purposes is to be used below the MDA; and

(d)   F-APP is displayed on the FMA.

   (4)     The pilot in command must ensure that a vertical approach path remains above the vertical limitations published in the approach chart.

   (5)     The pilot in command must discontinue an RNAV (GNSS) approach if an RNP of 0.3 or less cannot be maintained from the FAF, or if the vertical flight path cannot be maintained above the vertical limitations published in the approach chart.