You are on page 1of 28

FMS-5000 Version 4.

1 Highlights

Subject: Rockwell Collins FMS-5000 Version 4.1 — Change 5


NOTICE

The entire Supplement, AFMS W1610 - has been reprinted


incorporating Change 5.

The following summary describes the changes that are incorporated


with this change.

SECTION I - LIMITATIONS
Vertical Navigation Removed limitations regarding the temperature compensa-
tion.

SECTION II - NORMAL PROCEDURES


FMS Approach
Procedures

RNAV Approach Remove note from Step 6.


(With or without
Baro -VNAV)

Temperature Removed procedure.


Compensation

AFMS: W1610
Change 5 Highlights-1
Highlights FMS-5000 Version 4.1

THIS PAGE IS INTENTIONALLY LEFT BLANK

AFMS: W1610
Highlights-2 Change 5
FMS-5000 Version 4.1 AFM Supplement

Rockwell Collins FMS-5000 Version 4.1

AFMS: W1610 Model Affected: 60

When the Rockwell Collins FMS-5000 V4.1 Flight Management System is


installed in the affected model in accordance with the provisions of Mod-
Sum 060T002059, this supplement shall apply and must be inserted in the
SUPPLEMENTS section of the basic FAA Approved Airplane Flight Man-
ual.

The following Rockwell Collins Operator's Guide must also be carried on


the aircraft: FMS-5000 V4.0 Flight Management System for the Learjet
60XR; Publication Number 523-0818106, 1st Edition, dated 9Feb2010 with
addendum dated 17May10 or later applicable revision.

This Airplane Flight Manual Supplement (AFMS) covers limitations and


procedures for operation of the upgraded Rockwell Collins FMS-5000 sys-
tem installed in a Learjet 60XR airplane. The FMS-5000 upgrade provides
the additional capability to use the Satellite Based Augmentation System
(SBAS) to fly RNAV (GPS) instrument approach to LPV minimums.

The FAA approved material contained within this AFMS supplements or


supersedes the basic manual only in those areas listed herein. For limita-
tions, procedures, and performance information not contained in this sup-
plement, consult the Learjet 60XR FAA Approved Airplane Flight
Manual.

It is the responsibility of pilots who are qualified to operate the airplane


to be entirely familiar with the information contained in this publication
to ensure that the airplane is operated at all times within the flight and
system envelope.

FAA
Approved Date

for MARGARET KLINE, MANAGER


AIRCRAFT CERTIFICATION OFFICE
FEDERAL AVIATION ADMINISTRATION
WICHITA, KANSAS

Change 4 AFMS: W1610 Learjet Inc.


FAA Approved 8-16-2010 P.O. Box 7707
Change 4 Wichita, KS 67277
FMS-5000 Version 4.1 AFM Supplement

LIST OF EFFECTIVE PAGES


Use this page to determine the current status of this AFM Supplement. Pages affected by the current change are indicated
by an asterisk (*) immediately preceding the page number.

Dates of issue for original and changed pages are:

Original . . . . . . . . . . . . . O . . . . . . . . . 16-August-2010
Change. . . . . . . . . . . . . . 1 . . . . . . . . 24-February-2011
Change. . . . . . . . . . . . . . 2 . . . . . . . . 8-December-2011
Change. . . . . . . . . . . . . . 3 . . . . . . . . 29-February-2012
Change. . . . . . . . . . . . . . 4 . . . . . . . . . . . . 29-July-2013
Change. . . . . . . . . . . . . . 5 . . . . . . . . . . 8-January-2021

Page Status
Title. . . . . . . . . . . . . . . . . . . . . . . . . . . .4
* LOEP-1. . . . . . . . . . . . . . . . . . . . . . . . .5
* TOC-1 and TOC-2 . . . . . . . . . . . . . . .5
1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
* 3 thru 20 . . . . . . . . . . . . . . . . . . . . . . . .5

01/08/2021
FAA Approved ___________________________Date_________

KEITH JOHNSTON
ODA - administrator
ODA-501508-CE

Change 5 AFMS: W1610 LOEP-1


FAA Approved 8-16-2010
Change 5
FMS-5000 Version 4.1 AFM Supplement

TABLE OF CONTENTS
Section I — Limitations.......................................................................... 1
General .......................................................................................................... 1
Flight Management System (FMS).................................................. 1
Display Scaling................................................................................... 2
Approach ............................................................................................ 3
Vertical Navigation............................................................................ 3
Autopilot............................................................................................. 4
FMS Navigation Capabilities ................................................................... 4
Oceanic and Remote.......................................................................... 4
North Atlantic (NAT) Minimum Navigational Performance
Specifications (MNPS) Airspace...................................................... 5
High Latitude / Polar Region.......................................................... 5
RNP-10 Airspace................................................................................ 5
P-RNAV............................................................................................... 5
En route and Terminal, including B-RNAV ................................... 6
RNP-1 .................................................................................................. 7
RNAV 1 (STARS and SIDs)/RNAV 2 (Q-Routes and T-Routes). 8
FMS Instrument Approaches .................................................................... 9
SBAS / LPV ........................................................................................ 9
RNAV(GPS) or VOR/DME (GPS Overlay) .................................. 9
VOR/DME Approach (non-GPS) ................................................... 9
VOR or NDB (non-GPS) ................................................................. 10
Barometric VNAV............................................................................ 10

Section II — Normal Procedures .....................................................11


FMS Approach Procedures ...................................................................... 12
LPV Approach.................................................................................. 12
RNAV Approach (with or without Baro-VNAV) ........................ 14
Missed Approach............................................................................. 17
FMS NAV to NAV Operation......................................................... 17

Section III — Emergency Procedures (No Changes) .............. 18

Section IV — Abnormal Procedures ............................................ 18


VNAV Invalid Flag.................................................................................... 18
FMS Caution Messages ............................................................................ 18
APPR NOT AVAILABLE ................................................................ 18
CHK SBAS SVC PRVDR................................................................. 18
CRS TO FAF > 45 DEG.................................................................... 19
GNSS NOT AVAILABLE ................................................................ 19
HALF BANK SELECTED............................................................... 19
LOI TERM and LOSS OF INTEGRITY ......................................... 19

Change 5 AFMS: W1610 TOC-1


FAA Approved 8-16-2010
Change 5
AFM Supplement FMS-5000 Version 4.1

LPV NOT AVAILABLE....................................................................20


NO APPR...........................................................................................20
USE LNAV MINIMUM ...................................................................20

Section V — Performance Data (No Changes) ..........................20

TOC-2 AFMS: W1610


FAA Approved 8-16-2010
Change 5
FMS-5000 Version 4.1 AFM Supplement

SECTION I — LIMITATIONS
GENERAL
Flight Management System (FMS)
The system program number displayed on the FMS CDU STATUS Page
1/2 page must be SCID 832-4118-036.
The PERF DATA BASE number displayed on the FMS CDU STATUS Page
2/2 page must be 091-4982-001.
The VSPD DATA BASE number displayed on the STATUS page must be
815-9771-002 or 091-6512-001 (for Canadian registered A/C).
IFR en route, and terminal navigation is prohibited unless the pilot has
verified the currency of the database or verifies each selected waypoint for
accuracy by reference to current approved data.
If the Satellite Based Augmentation System is not available or disabled, the
aircraft must have additional navigation equipment appropriate to the in-
tended route, and it must be operational.
During periods of dead reckoning, indicated by the FMS DR annunciation,
the FMS shall not be utilized as the primary source of navigation.
Fuel display parameters are advisory only and do not replace the primary
fuel quantity or fuel flow gauges for loading or range/reserve planning.
The WGS-84 or NAD-83 coordinate reference datum in accordance with
the criteria of AC 20-130A, AC 91-49 Change 1, and AC 20-138A must be
used. Satellite navigation data is based upon use of only the Global Posi-
tioning System (GPS) operated by the United States.
The display of Geometric Altitude, GNSS HEIGHT or GNSS ALT on the
CDU and MFD STATUS 1/2 page shall not be referenced for compliance
with published or controller-issued altitudes.

NOTE A SBAS operational system (Service Provider) may not


be authorized for use within parts of the coverage area.
The flight crew is required to disable a non-authorized
SBAS operational system on the SBAS SERVICE PRO-
VIDERS CDU page (IDX/GNSS CTL/SELECT SBAS).

Change 2 AFMS: W1610 1


FAA Approved 8-16-2010
Change 2
AFM Supplement FMS-5000 Version 4.1

Flight Management System (FMS) (Cont)


The use of a RAIM prediction tool is required when the system is operated
outside an SBAS coverage area, including those areas where SBAS is pro-
vided, but has not been certified for civil aviation use. Predictions may be
performed using the following tools:
- Collins Pre-Departure GPS Coverage Predictor Program, CPN
832-3443-008, Rev -, or later version.
- EUROCONTROL AUGUR,
http://augur.ecacnav.com/augur/app/home
Display Scaling
When FMS is the selected NAV source, lateral and vertical full-scale devi-
ations are listed in the table below. Full scale deviation is 2 dots deviation
laterally or vertically from the center of the display.

SCALE
OPERATION
Lateral Vertical
OCEANIC
4 nm 500 ft
(OCEANIC Annunciated)
ENROUTE 2 nm 500 ft
TERMINAL
(TERM or LPV TERM Annunciated) 1 nm 500 ft

GPS SBAS Approach — LPV Angular Angular


(LPV APPR Annunciated) deviation deviation
GPS Approach
(GPS APPR Annunciated) 0.3 nm 250 ft

Conventional VOR/DME or
VOR/DME RNAV Approach 1 nm 250 ft
(APPR Annunciated)
Other Approaches
(NO APPR Annunciated) 1 nm 500 ft

Although most scale changes occur in a seamless manner, the pilot should
expect to occasionally observe a negligible jump of minimal magnitude in
the lateral and vertical scale presentations when transitioning from baro-
metric VNAV to SBAS VNAV that may become more pronounced when
the differential between outside air temperature and ISA increases.

2 AFMS: W1610 Change 1


FAA Approved 8-16-2010
Change 1
FMS-5000 Version 4.1 AFM Supplement

Approach
FMS instrument approaches must be accomplished in accordance with ap-
proved instrument approach procedures that are retrieved from the FMS
navigation database. The FMS J7 WORLD database must incorporate the
current update cycle.
The FMS, with inputs from the GPS, may only be used for approach guid-
ance if the reference coordinate data system for the instrument approach
is WGS-84 or NAD-83.
ILS, LOC, LOC-BC, LDA and SDF approaches using the FMS for approach
guidance are prohibited. The FMS may be utilized for an automatic NAV-
to-NAV transition to the localizer.
When the approach at the destination is based on GPS guidance and the
Satellite Based Augmentation System (SBAS) is not available or disabled,
an alternate airport required by operating rules must be served by an ap-
proach based on other than GPS navigation. The aircraft must have oper-
ational equipment capable of using that navigation aid, and the required
navigation aid must be operational.

FMS instrument approaches in FMS independent mode must be identi-


cal when conducting dual FMS approach operations.

NOTE If the flight plans are not identical in the two FMSs, the
flight director indications will conflict, which is not ac-
ceptable on final approach.
Inserting waypoints on a published approach is prohibited.
Approaches copied from the SEC FLPN must be re-entered if previously
flown.

Change 5 AFMS: W1610 3


FAA Approved 8-16-2010
Change 5
AFM Supplement FMS-5000 Version 4.1

Autopilot
The minimum altitude for autopilot coupled operations during an LPV
approach is 200 feet AGL or published Decision Altitude (DA), whichever
is higher.
For aircraft registered in EASA member states, the minimum altitude for
autopilot coupled operations during an LPV approach is 250 feet AGL or
published Decision Altitude (DA), whichever is higher. LPV approaches
are not authorized if TAWS is inoperative.

The minimum altitude for Autopilot coupled BARO VNAV approaches is


200 feet AGL or DA, whichever is higher.
The minimum altitude for use of the autopilot is 200 feet AGL, or MDA,
whichever is higher for approaches to MDA minimums.

FMS NAVIGATION CAPABILITIES


The dual Collins FMS-5000 (Flight Management System) with program
version 832-4118-036 is approved for use in the Learjet 60XR and meets the
requirements of Technical Standard Orders (TSO) TSO-C115b and TSO-
C146c Class Delta 4.
The following airworthiness approvals do not constitute operational
approval. Some types of operation require operational approval from the
regulatory authorities.
When the FMS is receiving appropriate navigation signals, it meets the ac-
curacy specifications for the following operations:

Oceanic and Remote


In accordance with AC 20-138A, the FMS-5000 and GPS-4000S have been
found to comply with the requirements for GPS primary means of naviga-
tion in oceanic and remote airspace. Two FMS-5000 units must be operat-
ing and receiving usable signals from two Rockwell Collins GPS-4000S
sensors and used in conjunction with the Rockwell Collins Pre-Departure
GPS Coverage Predictor Program, CPN 832-3443-008, Rev –, or later revi-
sion. For routes approved for single GPS navigation, a single FMS-5000
must be operating and receiving usable signals from a single GPS-4000S
sensor and used in conjunction with the Rockwell Collins GPS Coverage
Prediction Program listed above.

4 AFMS: W1610
FAA Approved 8-16-2010
Change 5
FMS-5000 Version 4.1 AFM Supplement

North Atlantic (NAT) Minimum Navigational Performance Specifica-


tions (MNPS) Airspace
In accordance with the criteria of AC 120-33, AC 91-49 and AC 20-138A,
the FMS and GPS has been found to comply with the requirements for
MNPS airspace. Two FMS units must be operating and receiving usable
signals from two operating GPS sensors. Operations with GPS require use
of the Collins Pre-Departure GPS Coverage Predictor Program, CPN 832-
3443-008, Rev –, or later revision.

High Latitude / Polar Region


The FMS-5000 considers the area greater than 80° north or 80° south as Po-
lar Regions. The FMS-5000 does not operate in the polar regions on the
Learjet 60XR due to the use of AHRS in lieu of an IRS. The message N/A
IN POLAR REGION will annunciate at latitudes greater than 80° north or
80° south and will not allow data to be entered into a flight plan.

Refer to Collins FMS-5000 Flight Management System for the Learjet 60XR
Operator's Guide, for additional information on operations in High Lati-
tudes.

RNP-10 Airspace
In accordance with the criteria of FAA Order 8400.12A without time lim-
itations. Two FMS systems must be operating and receiving usable signals
from two operating GPS sensors and used in conjunction with the Collins
predeparture GPS coverage predictor program (P/N 832-3443-008, Rev -,
or later revision).

P-RNAV
In accordance with the criteria of JAA TGL-10 and AC 90-96A. The FMS is
capable of P-RNAV operations provided the FMS is not in Dead Reckon-
ing (FMS DR not displayed on the PFD, MFD or CDU) and is receiving us-
able signals from one or more of the following:

− One GPS sensor


− Multiple DMEs
− A single DME if auto-tune is selected

Determine the requirements of the national, area, or local air traffic control
agency for determining the availability of GPS RAIM for the intended
route of flight prior to departure. Some terminal areas may require dual
operating FMS and GPS equipment.

AFMS: W1610 5
FAA Approved 8-16-2010
Change 5
AFM Supplement FMS-5000 Version 4.1

The operator/pilot must confirm that a Type 2 Letter of Authorization is


valid for the navigation database. This is available from Rockwell Collins,
Inc. by accessing the following website:
www.rockwellcollins.com/fms.

P-RNAV operations utilizing GPS as the only navigation sensor requires


the crew to confirm during pre-flight planning, the availability of Receiver
Autonomous Integrity Monitoring (RAIM) with the latest information
from the U.S. Coast Guard giving details of satellite non-availability (see
http://www.navcen.uscg.gov). The U.S. Notices to Airmen (NOTAM) of-
fice also provides satellite non-availability data planning for the intended
flight (route and time).

The confirmation of the availability of receiver autonomous integrity


monitoring (RAIM) for the intended flight (route and time) should be con-
firmed using all available information. Dispatch should not be made in
the event of predicted continuous loss of RAIM of more than 5 minutes for
any part of the intended flight. Predictions may be performed using the
following tools:
− Collins Pre-Departure GPS Coverage Predictor Program,
CPN 832-3443-008, Rev -, or later version.
− EUROCONTROL AUGUR,
http://augur.ecacnav.com/augur/app/home.
En route and Terminal, including B-RNAV
In accordance with AC 90-45A, AC 90-96A, AC 20-130A, AC 20-138A,
AMC 20-4, and AMC 20-5. The FMS must not be in Dead Reckoning (FMS
DR not displayed on the PFD, MFD or CDU). The FMS must be receiving
usable signals from one or more of the following:
− One GPS sensor
− VOR/DME or multiple DMEs
− A single DME if auto-tune is selected
The confirmation of the availability of RAIM for the intended flight (route
and time) should be confirmed using all available information. Dispatch
should not be made in the event of predicted continuous loss of RAIM of
more than 5 minutes for any part of the intended flight. Predictions may
be performed using the following tools:
− Collins Pre-Departure GPS Coverage Predictor Program,
CPN 832-3443-008, Rev -, or later version.
− EUROCONTROL AUGUR,
http://augur.ecacnav.com/augur/app/home.

6 AFMS: W1610
FAA Approved 8-16-2010
Change 5
FMS-5000 Version 4.1 AFM Supplement

RNP-1
The FMS is capable of operations on RNP-1 Departure Procedures and
STARS within the U.S. National Airspace in accordance with the criteria of
FAA AC 90-105, provided that:
1. The FMS is receiving usable signals from at least one of the follow-
ing:
a. One GPS sensor
b. Multiple DMEs
c. A single DME if auto-tune is selected
2. The following messages are not displayed:
a. FMS DR (PFD or CDU)
b. VOR/DME ONLY (CDU) or V/D ONLY (PFD)
c. VOR/DME DISTANCE > 40 nm (CDU)
3. Procedures that require GPS, or if GPS is the only sensor available,
the following messages are not displayed:
a. GNSS NOT AVAILABLE (CDU)
b. GNSS-FMS DISAGREE (CDU)
c. LOSS OF INTEGRITY (CDU or MFD)
d. LOI (PFD)
4. The crew has entered NOTAM’d NAVAIDs on the CDU
VOR/DME CONTROL page.
5. The operator/pilot has confirmed that a Type 2 Letter of Authori-
zation is valid for the navigation database. This is available from
Rockwell Collins, Inc. by accessing the following website:
www.rockwellcollins.com/fms.

NOTE The following condition only applies when SBAS is


NOTAM’d as not available or the aircraft is outside the
SBAS coverage area and the procedure requires GPS, or
if GPS is the only available sensor.
6. The confirmation of the availability of receiver autonomous integ-
rity monitoring (RAIM) for the intended flight (route and time)
should be confirmed using all available information. Dispatch
should not be made in the event of predicted continuous loss of
RAIM of more than 5 minutes for any part of the intended flight.
Predictions may be performed using the following tools:
− Collins Pre-Departure GPS Coverage Predictor Program,
CPN 832-3443-008, Rev -, or later version.
− The FAA website www.raimprediction.net

AFMS: W1610 7
FAA Approved 8-16-2010
Change 5
AFM Supplement FMS-5000 Version 4.1

RNAV 1 (STARS and SIDs)/RNAV 2 (Q-Routes and T-Routes)


The FMS is capable of RNAV 1 (STARs and SIDs) and RNAV 2 (Q-Routes
and T-Routes) operations in accordance with the criteria of FAA AC 90-
100A, provided that:
1. The FMS is receiving usable signals from at least one of the follow-
ing:
a. One GPS Sensor
b. Multiple DMEs
c. A single DME if auto-tune is selected
2. The following messages are not displayed:
a. FMS DR (PFD or CDU)
b. VOR/DME ONLY (CDU) or V/D ONLY (PFD)
c. VOR/DME DISTANCE > 40 nm (CDU)
3. Procedures that require GPS, or if GPS is the only sensor available,
the following messages are not displayed:
a. GNSS NOT AVAILABLE (CDU)
b. GNSS-FMS DISAGREE (CDU)
c. LOSS OF INTEGRITY (CDU or MFD)
d. LOI (PFD)
4. The crew has entered NOTAM’d navaids on the CDU VOR/DME
CONTROL page.
5. The operator/pilot has confirmed that a Type 2 Letter of Authori-
zation is valid for the navigation database. This is available from
Rockwell Collins, Inc. by accessing the following website:
www.rockwellcollins.com/fms.
6. The confirmation of the availability of receiver autonomous integ-
rity monitoring (RAIM) for the intended flight (route and time)
should be confirmed using all available information. Dispatch
should not be made in the event of predicted continuous loss of
RAIM of more than 5 minutes for any part of the intended flight.
Predictions may be performed using the following tools:
− Collins Pre-Departure GPS Coverage Predictor Program,
CPN 832-3443-008, Rev -, or later version.
− The FAA website www.raimprediction.net

8 AFMS: W1610
FAA Approved 8-16-2010
Change 5
FMS-5000 Version 4.1 AFM Supplement

RNAV 1 (STARS and SIDs)/RNAV 2 (Q-Routes and T-Routes) (Cont)


7. AC 90-100A applies to operation on U.S. Area Navigation (RNAV)
routes (Q-routes and T-routes), Departure Procedures (Obstacle
Departure Procedures and Standard Instrument Departures), and
Standard Terminal Arrivals (STARs). It does not apply to over
water RNAV routes (ref 14 CFR 91.511, including the Q-routes in
the Gulf of Mexico and the Atlantic routes) or Alaska VOR/DME
RNAV routes (“JxxxR”). It does not apply to off-route RNAV oper-
ations, Alaska GPS routes or Caribbean routes.

FMS INSTRUMENT APPROACHES


SBAS / LPV
In accordance with AC 20-130A, AC 20-138A and NPA 2009-04/AMC 20-
28 provided that:
1. The FMS is receiving usable signals from (at least) one GPS sensor.
2. A current altimeter setting for the landing airport is required.
3. The SBAS service provider required by the approach must be dis-
played on the CDU ARRIVAL page (right side, above ARR DATA)
at the Final Approach Fix (FAF).
4. LPV APPR annunciation must be displayed at the FAF on the PFD.
5. Where remote altimeter minima are shown, the VNAV function
may be used only to the published MDA.

RNAV(GPS) or VOR/DME (GPS Overlay)


In accordance with AC 20-130A, AC 20-138A and AMC 20-27 provided
that:
1. The FMS is receiving usable signals from (at least) one GPS sensor.
2. The autopilot or Flight Director is engaged (if approach is being
flown to DA minimums).
3. A current altimeter setting for the landing airport is required.
4. GPS APPR annunciation must be displayed at the FAF on the PFD.
5. Where remote altimeter minima are shown, the VNAV function
may be used only to the published MDA.

NOTE
This does not constitute approval to conduct Radius to
Fix (RF) leg or RNP APCH approach operations.

VOR/DME Approach (non-GPS)


In accordance with TSO C115B and AC 20-130A, the FMS must be receiv-
ing usable signals from the approach reference VOR/DME station, GNSS
sensors disabled, and the APPR annunciation must be displayed at the
FAF on the PFD.
AFMS: W1610 9
FAA Approved 8-16-2010
Change 5
AFM Supplement FMS-5000 Version 4.1

FMS INSTRUMENT APPROACHES (Cont)


VOR or NDB (non-GPS)
In accordance with TSO C115B and AC 20-130A, the FMS is not autho-
rized to provide guidance for an approach that does not have a GPS over-
lay. In the terminal area, NO APPR will be annunciated in white on the
PFD and APPR FOR REF ONLY in white on the CDU. The appropriate
ground station navigation source must be used as the primary guidance
for the approach.

NOTE
Some approach transitions are not included in the data-
base.

Barometric VNAV
In accordance with AC 20-129 the Barometric VNAV function is approved
for en route, terminal, and approach operations.

In accordance with AC 90-105 and AMC 20-27, the FMS must be receiving
usable signals from at least one GPS sensor, the GPS APPR annunciation
must be displayed at the FAF, and autopilot or flight director must be en-
gaged to descend to DA minimums. A current altimeter setting for the
landing airport is required. Where remote altimeter minima are shown,
the VNAV function may be used only to the published MDA.

10 AFMS: W1610
FAA Approved 8-16-2010
Change 5
FMS-5000 Version 4.1 AFM Supplement

SECTION II — NORMAL PROCEDURES


The Rockwell Collins version 4.1 FMS-5000 and GPS-4000S upgrade pro-
vides all previous functionality and improves the navigation accuracy, in-
tegrity, and availability of the system to provide additional RNAV, RNP
and approach Localizer Performance with Vertical guidance (LPV) capa-
bility from a Satellite Based Augmentation System (SBAS) Service Provid-
er.

SBAS uses a network of ground-based reference stations to measure small


variations in the GPS satellites signals throughout the world. Measure-
ments from the reference stations are routed to master stations, which send
the correction messages to geostationary satellites in a timely manner (at
least every 5 seconds or better). Those satellites broadcast the correction
messages, as well as the integrity status of individual satellites, where a
SBAS-enabled GPS receiver (GPS-4000S) can use the information while
computing its position to improve the availability, integrity and accuracy
of the GPS position.

For normal procedures, refer to Collins FMS-5000 Flight Management Sys-


tem for the Learjet 60XR Operator's Guide.

AFMS: W1610 11
FAA Approved 8-16-2010
Change 5
AFM Supplement FMS-5000 Version 4.1

FMS APPROACH PROCEDURES


LPV Approach

CAUTION - Use of the autopilot/flight director 1/2 BANK or


TURB modes may result in excessive deviation
during an approach transition or in a holding pat-
tern due to the limits these modes place on autopilot
command authority. During an FMS approach, ½
BANK mode is disabled when in APPR mode.
- No TAWS "GLIDESLOPE" alert will be sounded for
excessive deviation below glidepath when perform-
ing LPV approaches.
NOTE Approaches conducted utilizing SBAS-VNAV are not
subject to temperature limitations.

1. On the CDU, press the DEP ARR function key to show the
ARRIVAL page.
NOTE - Either an origin (ORIG) or a destination (DEST) air-
port must be specified in the flight plan for approach
selections to be available on the ARRIVAL page.
- When the DEP ARR key is pressed, one of three pag-
es is shown: the DEPART, ARRIVAL, or DEP/ARR
INDEX page. If the aircraft is on the ground, or air-
borne less than 50 nm from the origin airport, or less
than halfway to the destination airport, the DEPART
page for the ORIGIN airport shows. If the aircraft is
airborne and more than halfway to the destination
airport, the ARRIVAL page for the destination air-
port is shown.

2. Select an RNAV (GPS) approach that is SBAS LPV capable.

NOTE - RNAV (GPS) approaches with LPV minimums must


be loaded either as a SBAS LPV approach or a BARO
approach (if available).
- SBAS L/V (LNAV/VNAV) approaches are not cur-
rently in the data base and are not available for selec-
tion.

12 AFMS: W1610
FAA Approved 8-16-2010
Change 5
FMS-5000 Version 4.1 AFM Supplement

FMS APPROACH PROCEDURES (Cont)


LPV Approach (Cont)
3. Press the line select button adjacent to the desired transition.

NOTE If the desired approach or transition is not visible under


the APPROACHES or TRANS list, press the NEXT or
PREV function keys to scroll through additional selec-
tions.
4. Once the approach and approach transition have been selected,
press the EXEC function key to add the approach to the flight plan.
The FMS annunciates “LPV TERM” on the PFD when the aircraft is
within the terminal area (31 nm) of the selected runway threshold.

NOTE When an approach is added to a flight plan from the


ARRIVAL page, a discontinuity may be added immedi-
ately before the approach procedure in the flight plan.
5. With terminal annunciated select APPR mode on the flight direc-
tor. If intercepting the course via vectors, select APPR mode when
cleared to intercept the final course. APPR mode should be
engaged no later than 2 nm prior to the FAF.

6. When the flight plan leg after the Final Approach Course Fix
(FACF) becomes active and the aircraft meets the lateral capture
criteria, the PFD annunciates LPV APPR and displays angular lat-
eral and vertical deviation for the SBAS-VNAV approach.

7. RWY is annunciated on the PFD in the VNAV target altitude field


when within 500 ft (approximately 2 dots) of the LPV vertical path.
With APPR mode selected on the FGP, a white GP annunciation
will be displayed no later than 2 nm prior to the FAF. This indicates
the system is armed to capture and track a glidepath past the FAF.
After glidepath capture, the annunciation will change to VGP in
green. In VGP mode, the VNAV system will not level at the prese-
lected altitude. The preselector can be set to the missed approach
altitude. Operation in VGP mode is similar to GS mode for an ILS
approach and is appropriate for operations to a DA.

AFMS: W1610 13
FAA Approved 8-16-2010
Change 5
AFM Supplement FMS-5000 Version 4.1

FMS APPROACH PROCEDURES (Cont)


RNAV Approach (with or without Baro-VNAV)

CAUTION
Use of the autopilot/flight director 1/2 BANK or TURB
modes may result in excessive deviation during an ap-
proach transition or in a holding pattern due to the lim-
its these modes place on autopilot command authority.
During an FMS approach, ½ BANK mode is disabled
when in APPR mode.
NOTE If a non-GPS approach is selected (e.g. VOR/DME
RWY xx), the GNSS sensors must be deselected for the
approach
1. On the CDU, press the DEP ARR function key to show the
ARRIVAL page.

NOTE
- Either an origin (ORIG) or a destination (DEST) air-
port must be specified in the flight plan for approach
selections to be available on the ARRIVAL page.
- When the DEP ARR key is pressed, one of three pag-
es is shown: the DEPART, ARRIVAL, or DEP/ARR
INDEX page. If the aircraft is on the ground, or air-
borne less than 50 nm from the origin airport, or less
than halfway to the destination airport, the DEPART
page for the ORIGIN airport shows. If the aircraft is
airborne and more than halfway to the destination
airport, the ARRIVAL page for the destination air-
port is shown.
2. Press the line select button adjacent to the desired approach.
3. Press the line select key button adjacent to the desired transition.
NOTE If the desired approach or transition is not visible under
the APPROACHES or TRANS list, press the NEXT or
PREV function keys to scroll through additional selec-
tions.
4. Via the ARR DATA page, select BARO if LPV is the current
selection.

14 AFMS: W1610
FAA Approved 8-16-2010
Change 5
FMS-5000 Version 4.1 AFM Supplement

FMS APPROACH PROCEDURES (Cont)


RNAV Approach (with or without Baro-VNAV) (Cont)
5. Once the approach and approach transition, and BARO (if
required) have been selected, press the EXEC function key to add
the approach to the flight plan. The FMS annunciates GPS TERM
or TERM when the aircraft is within the terminal area (31 nm) of
the selected runway threshold.
When an approach is added to a flight plan from the
NOTE
ARRIVAL page, a discontinuity may be added immedi-
ately before the approach procedure in the flight plan.
6. With terminal annunciated select APPR mode (NAV if not using
VNAV guidance or descending on the VNAV path to the MDA) on
the flight director. If intercepting the course via vectors, select
APPR mode (or NAV) when cleared to intercept the final course.
APPR (or NAV, as applicable) mode should be engaged no later
than 2 nm prior to the FAF.
7. At 2 nm prior to the FAF, the pilot should verify white GPS APPR
or white APPR (depending upon the type of approach selected) is
annunciated on the PFD, and set the Altitude pre-selector as
required for the approach. To continue the approach to DA mini-
mums the AP or FD must be utilized.

AFMS: W1610 15
FAA Approved 8-16-2010
Change 5
AFM Supplement FMS-5000 Version 4.1

FMS APPROACH PROCEDURES (Cont)


RNAV Approach (with or without Baro-VNAV) (Cont)
8. If VNAV path guidance is desired for an FMS approach, VNAV
mode must be armed prior to the FAF. The FMS will provide a ver-
tical path for those approaches with a vertical angle displayed on
the CDU LEGS page to the altitude at the runway or missed
approach point. Approaches without a vertical angle will display
V-MDA above the missed approach point altitude on the CDU
LEGS page.

If APPR mode is selected on the FCP, a white GP (armed) annunci-


ation will be displayed 2 nm prior to the FAF. This indicates the
system is armed to capture and track a VNAV glidepath past the
FAF. After glidepath capture, the annunciation will change to VGP
in green. In VGP mode, the VNAV system will not level at the pre-
selected altitude. The preselector can be set to the missed approach
altitude. Operation in VGP mode is similar to GS mode for an ILS
approach and is appropriate when operating to a DA.

If NAV mode is selected on the FCP, a white PATH (armed) annun-


ciation will be displayed 2 nm prior to the FAF. This indicates the
system is armed to capture and track a VNAV path past the FAF.
After path capture, the annunciation will change to VPATH in
green.

In VPATH mode, the VNAV system will level at the preselected


altitude or VNAV reference altitude, whichever is higher. There
may be subsequent step-down fixes after the FAF that requires
pilot action to continue the descent to the MDA.

VNAV path guidance after the FAF is not available for those
approaches with V-MDA displayed above the missed approach
point altitude on the CDU. If flying level to the FAF, the aircraft
will remain in an altitude hold mode past the FAF unless another
flight director vertical mode is selected for descent to the desired
MDA. If descending to the FAF via a VNAV defined path, the
flight director will revert to PTCH mode at the FAF and the aircraft
will continue the descent at the aircraft pitch value present at the
transition to PTCH mode. There may be subsequent step-down
fixes after the FAF that requires pilot action to continue the descent
to the MDA.

16 AFMS: W1610
FAA Approved 8-16-2010
Change 5
FMS-5000 Version 4.1 AFM Supplement

FMS APPROACH PROCEDURES (Cont)


Missed Approach
Missed approach procedures are automatically added to the flight plan
with the selection of an approach. The missed approach procedure begins
on the LEGS page with the leg immediately following the MISSED APPR
label. It will also display on the ACT/MOD FPLN page as MISSED AP-
PROACH. A missed approach is activated by pressing the GA button.
If a missed approach is required from an FMS based approach:
1. Select the GA button to initiate the go-around and missed
approach procedure.
2. Set power, configure, and climb on course as required.
3. Set the appropriate lateral and vertical flight director modes.
4. Engage the autopilot (if desired).
If a missed approach is required from a localizer based approach:
1. Select the GA button to initiate the go-around and missed
approach procedure.
2. Set power, configure, and climb on course as required.
3. Select FMS as the active NAV source.
4. Set the appropriate lateral and vertical flight director modes.
5. Engage the autopilot (if desired).

FMS NAV to NAV Operation


The crew must select APPR (on the Flight Guidance Panel) after the FMS
completes the Nav-to-NAV set-up for the automatic transition from FMS
to LOC navigation to occur. The crew can confirm that the FMS has com-
pleted the Nav-to-Nav set-up for the selected approach by observing the
following on the PFD displays when the aircraft is in the terminal area:
− Localizer is tuned to the ILS frequency corresponding to the
selected approach and displayed on the PFD
− Localizer course is set
− LOC is the preselected navigation source

NOTE
The aircraft must be on an intercept to the localizer final
approach course, and APPR selected in order for the
transition to occur. After the transition the nav source
will be the captured localizer and the glideslope (GS)
will be armed. No further action required unless a
missed approach, then FMS nav source will need to be
reselected in order to fly the FMS missed approach pro-
cedure.

AFMS: W1610 17
FAA Approved 8-16-2010
Change 5
AFM Supplement FMS-5000 Version 4.1

SECTION III — EMERGENCY PROCEDURES


No change to FAA Approved Airplane Flight Manual.

SECTION IV — ABNORMAL PROCEDURES


VNAV Invalid Flag
The red VNAV flag indicates VNAV data is invalid.
Enroute:
- Select another vertical mode.
Approach:
- Select another vertical mode.

If accompanied by a yellow USE LNAV MINIMUM and LPV NOT AVAIL


message on the CDU;

- Outside the FAF, select BARO via the ARR DATA page and uti-
lize barometric VNAV for descent guidance to the DA or MDA,
as applicable. The selection of BARO must be executed prior to
the FAF. If the VNAV flag persists, use another vertical mode to
descend to MDA minimums.
- Inside the FAF, execute a missed approach.

FMS CAUTION MESSAGES


The following messages are annunciated in yellow on either the CDU or
PFD. Some CDU messages are repeated at the bottom of the MFD display.

APPR NOT AVAILABLE (CDU MFD)


This message is displayed when the FMS determines the system does not
meet the navigational requirements for approach operations and the air-
craft is inside the terminal area (within 31 nm of the selected runway
threshold). Do the following:
− Select an approach not based on GNSS or proceed to the alter-
nate airport if an approach cannot be completed in visual condi-
tions.
CHK SBAS SVC PRVDR (CDU)
This message is displayed when Satellite Based Augmentation System is
not available or is not enabled. Do the following:
− Verify the required SBAS provider is enabled.

18 AFMS: W1610
FAA Approved 8-16-2010
Change 5
FMS-5000 Version 4.1 AFM Supplement

FMS CAUTION MESSAGES (Cont)


CRS TO FAF > 45 DEG (CDU)
This message is displayed after executing a direct-to the FAF with an INTC
CRS greater than 45 degrees from the final approach course. The FMS will
not transition to the approach mode and SEQ INHB will be displayed on
the PFD in yellow. If the approach is flown with this message displayed,
the FMS will not provide guidance beyond the FAF to track the final ap-
proach course. Do the following:
− Perform a direct-to the FAF with an INTC CRS within 45
degrees of the final approach course.

GNSS NOT AVAILABLE (CDU)


MSG (PFD)
This message is displayed when the FMS cannot use any of the enabled
GNSS sensors or the crew has disabled all GNSS sensors via the GNSS CTL
page. Do one of the following:
− Continue FMS navigation with remaining valid sensors appro-
priate for the route of flight.
− If on LPV final approach, execute a missed approach.

HALF BANK SELECTED (CDU)


MSG (PFD)
This message is displayed when the autopilot/flight director 1/2 BANK
and NAV modes are active, an approach is in the flight plan and the air-
craft is within 31 nm of the approach airport. Message is also displayed
within 1 minute of entering a holding pattern. Do the following:
- Deselect 1/2 BANK mode prior to commencing the approach or
entering a holding pattern.
LOI TERM (PFD) and LOSS OF INTEGRITY (CDU MFD)
LOI is displayed on the PFD instead of LOI TERM if enroute. This message
is displayed when the FMS detects that the GNSS position does not meet
the requirements for navigational use in the current phase of flight. Do one
of the following:
- Select a navigation source other than FMS.
- Deselect the GNSS receivers and continue FMS navigation with
remaining valid sensors in accordance with airspace require-
ments.

AFMS: W1610 19
FAA Approved 8-16-2010
Change 5
AFM Supplement FMS-5000 Version 4.1

FMS CAUTION MESSAGES (Cont)


LPV NOT AVAILABLE (CDU)
MSG (PFD)
- If inside the FAF - execute a missed approach.
- If outside the FAF and time permitting - select a BARO
approach.

NO APPR (PFD)
NO APPR is yellow if on final approach, otherwise it is white on the PFD.
This message is displayed when the FMS is in approach mode and the
FMS determines the system does not meet the navigational requirements
for approach operations. Do the following:
− Execute a go-around if the approach cannot be completed in
visual conditions.

USE LNAV MINIMUM (CDU MFD)


This message is displayed when the GNSS vertical signal is inadequate for
operating to the LPV minimums. This message will be accompanied with
the “LPV NOT AVAILABLE” message. Do the following:
- Select BARO via the ARR DATA page and fly the approach uti-
lizing BARO VNAV to LNAV/VNAV DA minimums, or LNAV
MDA minimums, as applicable. The selection of BARO must be
executed prior to the FAF.
- If accompanied by an LPV NOT AVAIL message inside the FAF
execute a missed approach

SECTION V — PERFORMANCE DATA


No change to FAA Approved Airplane Flight Manual.

20 AFMS: W1610
FAA Approved 8-16-2010
Change 5

You might also like