80 - RNP Operations

AW139 - RFM - 4D Supplement 80
Document N° RNP Operations

139G0290X002 (EPIC Phase 7)
The information contained in this document supplements

the information of the Basic Flight Manual.
For limitations, procedures and performance data not
contained in this Supplement, consult the basic
Rotorcraft Flight Manual
SUPPLEMENT 80
RNP OPERATIONS
(EPIC PHASE 7)
E.A.S.A. Approved Page S80-i

Rev. 25
Supplement 80 AW139 - RFM - 4D
RNP Operations Document N°
(EPIC Phase 7) 139G0290X002
This Page Intentionally Left Blank
Page S80-ii E.A.S.A. Approved

Rev. 25
SUPPLEMENT 80
RNP OPERATIONS (EPIC PHASE 7)
TABLE OF CONTENTS
Page
ABBREVIATIONS AND DEFINITIONS S80-1
GENERAL INFORMATION S80-3
SECTION 1 - LIMITATIONS S80-5
REQUIRED EQUIPMENT S80-5
TYPE OF OPERATION S80-5
GLIDE SLOPE LIMITATIONS S80-5
AIRSPEED AND ALTITUDE LIMITATIONS FOR
APPROACHES S80-5
AUTOMATIC FLIGHT CONTROL SYSTEM LIMITATIONS S80-6
FLIGHT MANAGEMENT SYSTEM LIMITATIONS S80-6
SECTION 2 - NORMAL PROCEDURES S80-7
PRE START CHECKS S80-7
RNP 1, RNP 2, RNP 0.3 PROCEDURE
(FOR DEPARTURE, EN-ROUTE, ARRIVAL) S80-7
LPV APPROACH PROCEDURE S80-8
RNP AR APCH AND RNP APCH (LNAV AND
LNAV/VNAV MINIMA) APPROACH PROCEDURE S80-10
SECTION 3 - EMERGENCY AND MALFUNCTION
PROCEDURES S80-14
GENERAL S80-14
CAS MESSAGES S80-15
GPS FAIL (SINGLE GPS INSTALLATION) S80-15
SINGLE GPS FAIL (DUAL GPS INSTALLATION) S80-16
DOUBLE GPS FAIL (DUAL GPS INSTALLATION) S80-17
SINGLE LPV UNAVAILABLE CAUTION S80-18
DOUBLE LPV UNAVAILABLE CAUTION S80-19
FD FAIL DURING RNP APCH APPROACH S80-20
SECTION 4 - PERFORMANCE S80-21
PART II - MANUFACTURER’S DATA S80-23
SECTION 6 - WEIGHT AND BALANCE S80-23
E.A.S.A. Approved Page S80-iii

Rev. 25
Table of contents (Contd.)

Page
SECTION 7 - SYSTEM DESCRIPTION S80-23
GENERAL INFORMATION S80-23
LPV ANNUNCIATION S80-25
RNP AR APCH ANNUNCIATION S80-29
LIST OF ILLUSTRATIONS
Page
Figure 1 MCDU ARRIVAL page S80-25
Figure 2 MCDU APPROACH minima type page S80-26
Figure 3 LPV vertical deviation display on PFD S80-27
Figure 4 LPV Identifier and APP Green Advisory on
PFD S80-28
Figure 5 LPV MCDU ARRIVAL page S80-29
Figure 6 Expanded Lateral Deviation Scale with pointer
and EPU winglets S80-30
Page S80-iv E.A.S.A. Approved

Rev. 25
ABBREVIATIONS AND DEFINITIONS

Abbreviations and Acronyms used throughout this Supplement are
defined as follows
— APV :APproach with Vertical guidance
— APCH :APproaCH
— AR :Authorization Required
— BOD :Bottom Of Descent
— DA(H) :Decision Altitude (Height)
— FAS :Final Approach Segment
— FPAP :Flight Path Alignment Point
— FTP :Fictitious Threshold Point
— GNSS :Global Navigation Satellite System
— GPA :Glide Path Angle
— GPS :Global Positioning System
— LPV :Localizer Performance with Vertical guidance
— LNAV :Lateral NAVigation
— LTP :Landing Threshold Point
— MAP :Missed Approach Point
— MSA :Minimum Safe Altitude
— NLOC :Navigation LOCalizer
— NGS :Navigation Glide Slope
— PINS :Point IN Space
— RF :Radius to Fix
— RNAV :aRea NAVigation
— RNP :Required Navigation Performance
— ROD : Rate Of Descent
— SBAS :Satellite Based Augmentation System
— TOD :Top Of Descent
— VNAV :Vertical NAVigation
— VGP :Vertical Glide Path
E.A.S.A. Approved Page S80-1

Rev. 25
1. Go Around — Is the automatic procedure following

the activation of GA pushbutton
2. Published Missed — Is the missed approach procedure

Approach Procedures presented in the approach plate
chart and loaded into the FMS
navigation database
Page S80-2 E.A.S.A. Approved

Rev. 25
GENERAL INFORMATION
This supplement details the certified capabilities of the AW139, when
equipped with Primus Epic Phase 7, to operate RNP Navigation
Specifications listed in following Table 1, in accordance with ICAO
9613 PBN manual Ed. 4th, AMC 20-26, AMC 20-27, AMC 20-28, AC
90-105A, AC 20-138D change 2 and AC 90-101A:
ICAO 9613 Flight Phase

Ed. 4th
PBN manual APPROACH
- En-
Arrival Dep
Navigation route Initial Intermediate Final Missed
Specification
RNP 2 2 - - - - - -
RNP 1 1 1 1 1 - 1 1
RNP APCH - - 1 1 0.3 1 -
LNAV &
LNAV/VNAV
minima
RNP APH - - 1 1 Angular 1 -
LPV minima
RNP AR - - 0.3 0.3 0.3 1 -
APCH
RNP 0.3 NM
minima (*)
RNP 0.3 -0.3 0.3 0.3 0.3 - 0.3 0.3
Table 1 Navigation Specification
(*) Procedures with RNP lower than 0.3 NM in the approach segment
or 1.0 NM in the missed approach are not authorized.
The AW139 complies with requirements of AC 20-138D change 2 for
RNP operations with RF (Radius to Fix) legs when used in association
with RNP 1, RNP0.3, RNP APCH and RNP (AR) APCH Navigation
Specifications. The RF capability can be used during terminal
procedures, including approaches.
Note
RNP AR APCH 0.3/MA 1.0 certification approval does
NOT constitute operational approval.

Rev. 25

Rev. 25
SECTION 1 - LIMITATIONS
For Limitations not presented in this Supplement see Basic RFM or
appropriate Supplement.
RNP APCH approaches with LP minima are not supported.
REQUIRED EQUIPMENT
— PRIMUS EPIC Phase 7 with software EB7030191 - 00110/00111/

00112/00114/00115.
— For LPV Approaches, RNP AR APCH Approaches and RNP 0.3

only:
• SBAS GPS kits P/N 3G3450F00113 or P/N 3G3450F00413
• 2nd SBAS GPS kits P/N 4G3450F00613
TYPE OF OPERATION
RNP operations are approved under Day/Night VFR and Day/Night
IFR operation.
GLIDE SLOPE LIMITATIONS

Maximum Glideslope angle for LPV approaches...............................9°
Maximum Glideslope angle for RNP AR APCH,
LNAV/VNAV and LNAV approaches ...............................................8.3°
AIRSPEED AND ALTITUDE LIMITATIONS FOR APPROACHES

Minimum APP mode engagement airspeed for
RNP APCH approach procedures .......................................... 50 KIAS
Maximum ROD while approaching the MAP.......................... 1000 fpm
Minimum DA(H) for RNP AR APCH,
LNAV/VNAV and LNAV approaches ............................................ 250 ft
Minimum DA(H) for LPV approaches........................................... 200 ft

Rev. 25
Note
The airspeed at the FAF and MAP, as indicated on the
the Approach Plate being used, must not be exceeded.
Note
Use of IAS mode is recommended with RNP APCH and
RNP AR APCH approaches below 60 KIAS.
AUTOMATIC FLIGHT CONTROL SYSTEM LIMITATIONS

RNP operations must be flown using the default Flight Director
coupled mode or by following raw data. Use of Flight Director in
uncoupled mode for RNP operations is not approved.
For RNP APCH approaches with a glide slope angle greater than 7.5
degrees the final approach segment (from FAF to MAP) must be flown
with AFCS approach modes coupled. In case a failure occurs after the
FAF, causing the FD to decouple, the pilot must discontinue the
current approach.
RNP procedures including RF legs must be flown with LNAV Flight
Director mode coupled. In case a failure occurs, causing the FD to
decouple, the pilot must discontinue the current procedure.
FLIGHT MANAGEMENT SYSTEM LIMITATIONS

Use of FMS offset function during RNP 0.3 operations is forbidden.

Rev. 25
SECTION 2 - NORMAL PROCEDURES
PRE START CHECKS
1. MFD — Set SYSTEM page, select

SYS CONFIG and verify Top
Level System Part Number
(EPIC software release)
installed: EB 7030191-00110/
00111/00112/00114/00115.
RNP 1, RNP 2, RNP 0.3 PROCEDURE

(for departure, en-route, arrival)
For normal procedures associated with RNP 1, RNP 2 and RNP 0.3 in
the departure, en-route and arrival phases of flight refer to the basic
RFM.
CAUTION
The Honeywell FMS cannot automatically retrieve the

0.3 NM RNP value from Navigation Database for
airways. Before the start of a RNP 0.3 airway, the crew
shall manually enter 0.3 as RNP value by accessing the
PROGRESS 2/3 RNP MCDU page. Following the
manual entry, current RNP value shall be checked on
PFD or PROGRESS 1/3 MCDU page.

Rev. 25
LPV APPROACH PROCEDURE

Prior to reach the FAF (Final Approach Fix)
1. PFD/MCDU — Once the approach has been

activated verify:
• Advisory message "LPV" (White/
Green) displayed on PFD
• LPV Approach Reference Path
Identifier (lower left on PFD)
corresponds to Approach Plate
information
• DA(H) set accordingly Approach
chart
• PERF INIT executed.
Note
If the pilot decides to fly the lateral and vertical deviations
displayed manually (glideslope lower than 7.5°), then
neither LNAV nor VGP should be engaged. A mix of
LNAV engagement and hands-on flying the vertical
deviation, with no VGP engagement, should not be used
for LPV approaches.
2. MCDU — If deceleration profile is required

verify/set the INITIAL and FINAL
speeds and relative distances with
respect to the MAP waypoint.
3. Guidance controller — If Flight Director coupled guidance

is required, press APP or DCL
pushbutton to arm LNAV & VGP
Confirm DCL armed or engaged if
DCL mode selected.
4. Altimeters — Verify QNH at destination.

Rev. 25
5. Landing path — Adjust speed to comply with the

Approach Plate.
Perform APPROACH AND
LANDING PROCEDURE as per
basic Rotorcraft Flight Manual.
6. Pre Landing check — Complete.
During FAS
1. PFD — Once APP displayed in green,

verify the "LPV" annunciation turns
green. If coupled Flight Director is
used, verify the automatic
transition on lateral axis from LNAV
mode to NLOC mode.
2. AFCS — If coupled Flight Director is used,

confirm:
• NGS mode engaged as required
• IAS or DCL mode engaged, if
required. For airspeed below
60 KIAS engage IAS mode.
3. Airspeed — Adjust as required to maintain

ROD less than 1000 fpm, while
approaching the MAP.
Note
The approach airspeed should account for head or tail
winds to ensure a ROD of 1000 fpm is not exceeded
while approaching the MAP.

Rev. 25
Before or at the DA(H)
1. Cyclic — If the required visual references

are acquired, press STBY
pushbutton to disengage AFCS
Flight Director modes (if engaged)
and fly manually to landing point.
If at DA(H) the required Visual References to continue the approach
have not been attained perform the Missed Approach procedure (MA).
Missed Approach Procedure
1. Collective — Press GA pushbutton.

Confirm LNAV engages and
remains engaged.
CAUTION
GA mode does not target altitude constraints, therefore

the pilot must manage altitude according to the published
missed approach procedure.
2. Once a positive Rate of Climb— Continue Go Around checks,

is established, as required.
RNP AR APCH AND RNP APCH (LNAV AND LNAV/VNAV MINIMA)

APPROACH PROCEDURE
Within Terminal Area
1. MCDU — If deceleration profile is required

verify/set the INITIAL and FINAL
speeds and relative distances with
respect to the MAP waypoint.

Rev. 25
2. Guidance controller — If Flight Director coupled guidance

is required, press APP or DCL
pushbutton to arm LNAV & VGP
modes.
Confirm DCL armed or engaged if
DCL mode selected.
At IAF (Initial Approach Fix)
1. PFD — After sequencing the IAF point

check the Lateral Deviation
indicator on the HSI.
2. Altimeters — Verify QNH/QFE, crosscheck pilot

and copilot (or STBY) altimeters
agree within ±100 ft.
Note
If the altimeter crosscheck fails then the
procedure must not be continued.
3. Landing path — Adjust the speed to comply with

the Approach Plate.
Perform APPROACH AND
LANDING PROCEDURE as per
basic Rotorcraft Flight Manual.
Prior to the FAF
1. PFD — Check APP green advisory

message displayed (lower left on
PFD) and “P” displayed in vertical
deviation bug.
2. Lateral Deviation — Confirm lateral deviation on HSI is

within RNP limit and “DGR”
message is not displayed,
otherwise discontinue the current
procedure.

Rev. 25
Note
During RNP AR APCH approach, if the aural message
“RNP RNP” is activated (the expanded lateral deviation
indicator on ADI turns amber), then a missed approach
must be initiated.
During FAS
1. AFCS — If coupled Flight Director is used,

confirm:
• VGP mode engaged as required
• IAS or DCL mode engaged, if
required. For airspeed below
60 KIAS engage IAS mode.
2. Airspeed — Adjust as required to maintain

ROD less than 1000 fpm, while
approaching the MAP.
Note
The approach airspeed should account for head or tail
winds to ensure a ROD of 1000 fpm is not exceeded
while approaching the MAP.
Before or at the DA(H)
1. Cyclic — If the required visual references

are attained press STBY
pushbutton to disengage AFCS
Flight Director modes (if engaged)
and fly manually to landing point.
If at DA(H) the required Visual References to continue the approach
have not been attained perform the Missed Approach procedure (MA).

Rev. 25
Missed Approach Procedure
1. Collective — Press GA pushbutton.
CAUTION
GA mode does not target altitude constraints, therefore

the pilot must manage altitude according to the published
missed approach procedure.
1. Once a positive Rate of — Continue Go Around checks

Climb is established, as required.

Rev. 25
SECTION 3 - EMERGENCY AND MALFUNCTION

PROCEDURES
GENERAL
The following malfunction procedures are intended to integrate those
of the basic RFM and, if a Flight Director is used, those of the
applicable Supplement installed 67, 69 or 70.
The following malfunction procedures are to be used only during RNP
Operations.
In the specific case of loss of GNSS Navigation information the FMS
system reverts to the remaining navigation sensors, which are not
allowed for use during RNP Operations.
Even when using non-GNSS sensors or in degraded mode (EPU
higher than RNP), the FMS continues to provide navigational position,
groundspeed, and ground track information. The procedure waypoints
still remain displayed in the PFD.

Rev. 25
CAS MESSAGES
GPS FAIL (SINGLE GPS INSTALLATION)
GPS FAIL + FMS/GPS MSCP UNAVL
+ possible DGR message on PFD
GPS system failure

FMS reverts to alternative
navigation sensors
Loss of RNP capability
- Discontinue the current RNP

procedure and notify ATC of
the loss of RNP capability

Rev. 25
SINGLE GPS FAIL (DUAL GPS INSTALLATION)
1(2) GPS FAIL
Single GPS system failure
Loss of GPS redundancy
- Continue flight

Rev. 25
DOUBLE GPS FAIL (DUAL GPS INSTALLATION)
1-2 GPS FAIL + FMS/GPS MSCP UNAVL
+ possible DGR message on PFD
+ possible 1-2 LPV UNAVAIL

for LPV approaches only
GPS system failure

FMS reverts to alternative
navigation sensors
Loss of RNP and LPV capability
- Discontinue the current RNP

procedure and notify ATC of
the loss of RNP capability

Rev. 25
SINGLE LPV UNAVAILABLE CAUTION
1(2) LPV UNAVAIL
LPV capability not available

or loss of redundancy
If LPV or LPV If LPV NLOC NGS

on on-side PFD (or LNAV VGP if
before FAF)
disengages with chime
on on-side PFD’s
LPV loss of redundancy
- Continue If before FAF If after FAF

Approach
- Select alternative
LNAV source on PFD - Discontinue
- Re- Engage APP or Approach
DCL
- Continue approach

Rev. 25
DOUBLE LPV UNAVAILABLE CAUTION
1-2 LPV UNAVAIL + LPV on both PFD’s
LPV approach unavailable
If before FAF If after FAF
- Continue approach
using LNAV/VNAV minima or - Discontinue
alternative approved means Approach
If LNAV/VNAV minima not available
- Discontinue
Approach

Rev. 25
FD FAIL DURING RNP APCH APPROACH
replaces FD arrow above altitude

FD FAIL indicator on both PFD’s
+
Loss of flight director cue information
Both Flight Directors invalid nad NOT available
If FD engagement If FD engagement
mandatory not mandatory
(i.e. LPV with Glide Path Angle
greater than 7.5°, or RNP
procedure with RF, or approaches - Continue Approach
with IAS lower than 60 KIAS
- Discontinue the current

procedure

Rev. 25
SECTION 4 - PERFORMANCE
No Change.

Rev. 25

Rev. 25
PART II - MANUFACTURER’S DATA
SECTION 6 - WEIGHT AND BALANCE

No Change.
SECTION 7 - SYSTEM DESCRIPTION

For full details of the EPIC FMS operation and use see EPIC and FMS
Pilots guide latest issue.
GENERAL INFORMATION
RNP AR APCH Operational approval must be requested by Aircraft
Operator (AO) and granted by the local Competent Authority. A Flight
Operational Safety Assessment (FOSA) methodology is used.
The FOSA must account for the fact that a loss of GNSS reception (in
case of loss of GNSS satellites view or dual GNSS receiver failure)
has, as a consequence, the loss of RNAV and RNP capabilities.
In case of loss of RNP capability during RNP AR operations, the flight
crew must discontinue the approach, unless the pilot has runway
visual references in sight.
In this case, the relevant and specific contingency procedures
(assessed in the FOSA) must be applied to terminate the RNP
navigation and revert to conventional navigation or apply specific ATC
instructions.
For all navigation specification listed in Table 1, except for LPV
approaches, the FMS (selected as Navigation Source) computes
lateral path deviation/guidance by using available sensors for position
computation. The lateral deviation computed by FMS is used as input
for LNAV Flight Director Mode.
For approaches with LNAV, LNAV/VNAV and RNP 0.3 minima/MA 1.0,
FMS uses baro VNAV to compute vertical path deviation/guidance.
The vertical deviation computed by FMS is used as input for VGP
flight director mode.
Page S80-23
Rev. 25
For the specific case of LPV approaches, lateral and vertical deviation/
guidance are directly computed by GPS, based upon the FAS data
block defining the approach path. These deviations are used as input
of NLOC / NGS flight director modes, respectively.
Intercept of the final approach segment may be performed either flying
an approach transition or through vectoring.
The following table provides, as reference, the ROD (Rate Of
Descent) for varying Ground Speed (GS) and Glide Path Angle (GPA):
GPA (deg) GROUNDSPEED (kts) ROD (fpm)

4 141 1000
4.5 125 1000
5 113 1000
5.5 103 1000
6 94 1000
6.5 87 1000
7 80 1000
7.5 75 1000
7.5 68 900
7.5 60 800
7.5 53 700
8 70 1000
8 60 850
8 50 710
9 62 1000
9 50 800
Table 1 ROD/GS/GPA
Page S80-24
Rev. 25
For information the AW139 has been demonstrated to be capable of

performing any procedure that meets the following design criteria
when flying with AFCS coupled at sea level:
— Minimum turn radius:.............................................................0.2 NM
— Minimum initial, intermediate and final approach
segments length: ...................................................................0.5 NM
— Maximum intercept angle for the turn to final: ................45 Degrees
— Maximum descent gradient during initial and
intermediate segment:.....................................................1000 ft/NM
LPV ANNUNCIATION
When an approach contains LPV line of minima, this is indicated in the
MCDU ARRIVAL page under the RNAV MIN prompt.
ARRIVAL 1/1
AIRPORT
1L SURFACE KDVT 1R
RW25L
2L APPROACH RNAV MIN 2R
VECTOR.RNAV LPV
3L STAR 90117/W25A 3R
4L 4R
5L 5R
6L REVIEW ACTIVATE 6R
ICN-39-A-150080-G-A0126-01001-A-01-1
Figure 1 MCDU ARRIVAL page
Page S80-25
Rev. 25
Selecting RNAV min prompt permits the pilot to choose different

approach minima types, when available. When defined, LPV is the
default.
APPROACH MINIMA TYPE 1/1
1L LPV(SEL) RETURN 1R
90117/W25A
2L 2R
3L LNAV/VNAV 3R
4L 4R
5L 5R
6L 6R
ICN-39-A-150080-G-A0126-01002-A-01-1
Figure 2 MCDU APPROACH minima type page
Note
The flight crew shall avoid selecting an approach
minimum that is not clearly stated on the approach chart,
despite the FMS allowing selection multiple minima
types. Refer to Honeywell publication D201710000025.
Page S80-26
Rev. 25
When a LPV approach is selected, a LPV annunciator is displayed on

the top right of the attitude display.
This annunciator is:
• WHITE when the LPV is armed, meaning that it has been

loaded without any failure and the aircraft is in the Terminal Area
• GREEN when LPV is active, meaning that pseudo-NLOC mode

angular deviation is active
• AMBER when LPV is not available or a loss of redundancy for

LPV function has occurred.
The LPV annunciator complements the lateral and vertical deviations
display. The vertical deviation bug has a ‘L’ to indicate it refers to a
LPV approach.
LPV annunciator (active)
Deviation bug with ‘L’

to indicate LPV path
ICN-39-A-155080-G-00001-30039-A-001-01
Figure 3 LPV vertical deviation display on PFD
Page S80-27
Rev. 25
The LPV approach identifier is displayed close to the ADI when a LPV
approach is loaded and the aircraft is in the terminal area.
APP Green Advisory Message
LPV Approach Reference Path Identifier

ICN-39-A-155080-G-00001-30040-A-001-01
Figure 4 LPV Identifier and APP Green Advisory on PFD
Page S80-28
Rev. 25
RNP AR APCH ANNUNCIATION

For RNP AR APCH approaches the MCDU ARRIVAL indicate the
RNP value under the RNAV MIN prompt.
ARRIVAL 1/1
AIRPORT
1L SURFACE KDVT 1RS
RW25L
2L APPROACH RNAV MIN 2RS
VECTOR.RNAV RNP 0.30
3L STAR 3RS
4L 4RS
5L 5RS
6L REVIEW 6RS
ICN-39-A-150080-G-A0126-01003-A-01-1
Figure 5 LPV MCDU ARRIVAL page

As an aid to the pilot for RNP AR APCH approaches, an expanded
lateral deviation scale is added on PFD below the ADI.
The scale is displayed in the approach and missed approach (except
for holdings) phases of RNP AR APCH approaches. The lateral
deviation pointer is scaled as a function of FMS RNP, such that the
full scale deflection is equal to the active RNP value. The winglets
starting at the center of the triangle pointer are sized according to the
current EPU.
When within RNP limit, the lateral deviation pointer with winglet is
displayed in cyan for non-coupled side and in magenta for coupled
side.
When the lateral deviation pointer with winglet exceeds the RNP
value, it will be displayed in amber and flash initially. Correspondingly
a “RNP RNP” aural alert will be played.
Page S80-29
Rev. 25
Expanded Lateral Deviation scale position
FD coupled and inside RNP limit Outside RNP limit
RNP indication with low EPU

(typical with SBAS)
ICN-39-A-155080-G-00001-30041-A-001-01
Figure 6 Expanded Lateral Deviation Scale with pointer

and EPU winglets
Loss of valid FMS data result in the lateral deviation pointer and scale
being replaced by an amber X.
Page S80-30
Rev. 25

80 - RNP Operations

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

80 - RNP Operations

Uploaded by

Copyright:

Available Formats

AW139 - RFM - 4D Supplement 80

Document N° RNP Operations

The information contained in this document supplements

E.A.S.A. Approved Page S80-i

This Page Intentionally Left Blank

Page S80-ii E.A.S.A. Approved

E.A.S.A. Approved Page S80-iii

Table of contents (Contd.)

Page S80-iv E.A.S.A. Approved

ABBREVIATIONS AND DEFINITIONS

E.A.S.A. Approved Page S80-1

1. Go Around — Is the automatic procedure following

2. Published Missed — Is the missed approach procedure

Page S80-2 E.A.S.A. Approved

ICAO 9613 Flight Phase

Table 1 Navigation Specification

E.A.S.A. Approved Page S80-3

This Page Intentionally Left Blank

Page S80-4 E.A.S.A. Approved

— PRIMUS EPIC Phase 7 with software EB7030191 - 00110/00111/

— For LPV Approaches, RNP AR APCH Approaches and RNP 0.3

• SBAS GPS kits P/N 3G3450F00113 or P/N 3G3450F00413

• 2nd SBAS GPS kits P/N 4G3450F00613

GLIDE SLOPE LIMITATIONS

AIRSPEED AND ALTITUDE LIMITATIONS FOR APPROACHES

E.A.S.A. Approved Page S80-5

AUTOMATIC FLIGHT CONTROL SYSTEM LIMITATIONS

FLIGHT MANAGEMENT SYSTEM LIMITATIONS

Page S80-6 E.A.S.A. Approved

SECTION 2 - NORMAL PROCEDURES

PRE START CHECKS

1. MFD — Set SYSTEM page, select

RNP 1, RNP 2, RNP 0.3 PROCEDURE

The Honeywell FMS cannot automatically retrieve the

E.A.S.A. Approved Page S80-7

LPV APPROACH PROCEDURE

1. PFD/MCDU — Once the approach has been

2. MCDU — If deceleration profile is required

3. Guidance controller — If Flight Director coupled guidance

4. Altimeters — Verify QNH at destination.

Page S80-8 E.A.S.A. Approved

5. Landing path — Adjust speed to comply with the

6. Pre Landing check — Complete.

1. PFD — Once APP displayed in green,

2. AFCS — If coupled Flight Director is used,

3. Airspeed — Adjust as required to maintain

E.A.S.A. Approved Page S80-9

Before or at the DA(H)

1. Cyclic — If the required visual references

Missed Approach Procedure

1. Collective — Press GA pushbutton.

GA mode does not target altitude constraints, therefore

2. Once a positive Rate of Climb— Continue Go Around checks,

RNP AR APCH AND RNP APCH (LNAV AND LNAV/VNAV MINIMA)

Within Terminal Area

1. MCDU — If deceleration profile is required

Page S80-10 E.A.S.A. Approved

2. Guidance controller — If Flight Director coupled guidance

At IAF (Initial Approach Fix)

1. PFD — After sequencing the IAF point

2. Altimeters — Verify QNH/QFE, crosscheck pilot

3. Landing path — Adjust the speed to comply with