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

Instrument number CASA 371/09

I, CLIVE ROY ADAMS, Manager, CASA Operations, Air Transport Eastern Region, a delegate of CASA, make this instrument under regulation 179A of the Civil Aviation Regulations 1988 (CAR 1988).

[Signed Clive Adams]

Clive Adams
Manager, CASA Operations
Air Transport Eastern Region

1^st November 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 July 2011.

2           Definitions

                In this instrument:

AFM means the aircraft flight manual.

ANP means actual navigation performance.

FAF means final approach fix.

FCOM means flight crew operations manual.

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.

IAF means initial approach fix.

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.

RNAV (GNSS) approach means an area navigation instrument approach procedure published in the Australian AIP.

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.

3           Application

                This instrument applies to the conduct of RNAV (GNSS) approaches by Virgin Blue International Airlines Pty Ltd, trading as V Australia, Aviation Reference Number 768593 (V Australia) using Boeing 777 aircraft with an RNP-capable RNAV system (the aircraft).

4           Instructions

                I issue the instructions in Schedule 1.

Schedule 1             Instructions

1           Use of RNP capability for RNAV (GNSS) approaches

Instead of complying with the instructions in instrument CASA 608/08 issued under regulation 179A of CAR 1988, 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)      V Australia must maintain and validate the FMS navigation database in accordance with the manufacturer’s procedures.

     (3)      V Australia must:

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

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

     (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 in other V Australia Boeing 777 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 procedure as published inRNAV (GNSS) approach charts.

     (7)      RNAV (GNSS) approach charts must be verified by V Australia before use.

3           Procedures

     (1)      The pilot in command must ensure that RNAV (GNSS) approaches are flown in accordance with authorised V Australia instrument approach procedures.

     (2)      The pilot in command must ensure that RNAV (GNSS) approaches are flown in selectable mode using the navigation database without modification.

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

     (4)      The pilot in command must discontinue an RNAV (GNSS) approach once past the IAF:

(a)     if ANP exceeds 0.3 RNP; or

(b)     in I.M.C., if any of the following alerts are displayed:

                  (i)   FMC;

                 (ii)   NAV ADIRU INERTIAL;

                (iii)   GPS;

                (iv)   NAV UNABLE RNP.

     (5)      The approach may be continued at the discretion of the pilot in command once passed the FAF, if there should be a GPS alert with ANP remaining within 0.3 RNP.