Fms. Sy0302 Fms Trainer Part 2

T-6C FMS TRAINER 2
Lesson #302
© 2016 Beechcraft Corporation. ALL RIGHTS RESERVED. BEECHCRAFT PROPRIETARY - This document contains proprietary data or information pertaining to
items, or components, or processes, or other matter developed or acquired at the private expense of Beechcraft and is restricted to use only by persons authorized
by Beechcraft in writing to use it. Disclosure to unauthorized persons would likely cause substantial competitive harm to Beechcraft’s business position. Neither said
document nor said technical data or information shall be furnished or disclosed to or copied or used by persons outside Beechcraft without the express written
approval of Beechcraft.
1
OBJECTIVES
• Review basic FMS/GPS functions and
operations required during the
INSTRUMENT phase of training.
2
Textron Aviation Defense - Title Page Rights Apply
LESSON TOPICS
• Building an active flight plan
• Building a standby flight plan
• Manual RAIM check
• Selecting and deselecting satellites
• Radar departure to the first waypoint
• Turning at Fly-By waypoints
• Manually inserting a holding fix
• Exiting holding
• Deleting a holding fix
• Enroute, Terminal and approach modes
• Missed approach procedures
• Activating standby flight plan
• Radar Vectors to Final Approach Course
• DME HOLD function
3
Building an active flight plan
•The T-6C FMS provides the capability to preload a RTE-

1 (route 1 flight plan) with all waypoints required to takeoff
from Airport “A”, fly a published DP, navigate via waypoints
and or airways to a primary destination, execute a
published STAR, shoot an RNAV (GPS) approach to
airport “B”, execute the published missed approach
procedure, activate a RTE-2 (route 2 flight plan) and fly to
airport “C” with the same preloaded capabilities.
4
Building an
active flight plan
•For our example we will load
RTE-1 with a flight plan from
KNSE (Whiting Field NAS -North)
to KHBG (Hattiesburg Bobby L.
Chain MUNI).
•ORIGN – KNSE
•DEST – KHBG
•Route of flight:
PENSI MVC V222 LBY
•Approach:
KHBG RNAV (GPS) Z RWY 13
(DIYET transition)
5
6
7
Building an
active flight plan
•From the MFD menu
page 1/2, select the
ROUTE page by pressing
LSK R2.
8
Building an
active flight plan
•RTE-1 is currently active.
NOTE
If RTE-2 is active it can be used
to load the first route and RTE-1
can be used for the
alternate/standby route.
9
Building an active
flight plan
•To clear an existing flight

plan, put the airport where
your flight will originate
from in the scratch pad
(KNSE)
•Upload it to the ORIGIN
at LSK L1
10
Building an active
flight plan
•All previously existing

waypoints will be removed
from RTE-1.
Note
Putting the word delete in the
scratch pad and uploading it to
the ORIGIN (LSK L1) will Delete
the ORIGN, DEST and all
waypoints.
11
Building an active
flight plan
•Next put your destination airport

in the scratchpad and upload it to
DEST using LSK R1.
12
Building an active
flight plan
•In order for the FMS to accept

a flight plan there must be at
least one waypoint between the
ORGIN and DEST.
•To enter individual waypoints in
the route of flight move to RTE
1 page 2/2 using LSK LR.
13
Building an active
flight plan
•Route of flight never begins

with an airway.
•WAYPOINTS are entered in
the “TO” positions (on the right
side).
•AIRWAYS are entered in the
“VIA” positions (on the left side).
•Enter the first waypoint into the
scratch pad (PENSI)
•Upload it from the scratchpad
to the “TO” position at LSK R1
14
Building an active
flight plan
•Note that the word DIRECT

auto fills in the VIA position.
• The system will only accept an
AIRWAY for entry to the via
positions after line 1.
•If nothing is entered in the “VIA”
position (left side), it defaults to
“DIRECT”.
15
Building an active
flight plan
•Our next waypoint, MVC

is also a direct leg.
• Enter MVC into the
scratch pad and upload it
to LSK R2.
16
Building an active
flight plan
•Once again the VIA line is

auto filled with DIRECT.
17
Building an active
flight plan
•At this point our route will

be continued on the
airway V222.
•Place V222 in the
scratchpad and upload it
to the VIA line at LSK L3
18
Building an active
flight plan
•We have now designated

MVC as the point where
the V222 airway will be
joined.
•Next we need to identify
the waypoint at which we
intend to exit V222.
19
Building an active
flight plan
•In the SCRATCHPAD,

enter the last WAYPOINT
on V222 we intend to use
(LBY for our example).
•Upload LBY from the
SCRATCHPAD to the “TO”
position at LSK R3.
20
Building an active
flight plan
•All waypoints that exist in

the database on V222
airway between our airway
entry point of MVC and
our exit point at LBY will
be automatically loaded
into the route (this will be
seen when we review the LEGS
pages).
•Next we can move to the
DEP/ARR page to load an
approach at our
destination
•LSK UL will take us to the
MFD MENU page 1/2.
21
Building an active
flight plan
•From the MFD MENU

page 1/2, select DEP/ARR
at LSK R3.
22
Building an active
flight plan
•On the DEP/ARR INDEX

page you can access any
available departures using the
left LSK’s labeled “DEP”.
•Standard Terminal Arrivals
(STARS) and Instrument
Approach procedures are
accessed via the associated
right LSK’s labeled “ARR” .
•Select LSK L1 “DEP” to view
any Departure Procedures
from KNSE.
23
Building an active
flight plan
•Note that there are no

Departures available for this
airport.
•Select LSK UL to return to the
NAV page.
24
Building an active
flight plan
•From the NAV page use LSK

R5 to return to the DEP/ARR
pages to address our intended
arrival.
25
Building an active
flight plan
•Arrival options for our

destination KHBG are available
via LSK R2.
26
Building an active
flight plan
•Note there are no STARS for

this airport.
•Based on preflight planning we
would select an approach for
our destination.
• For our example we will use
the RNAV (GPS) Z RWY 13.
•Use LSK R2 to select this
approach.
27
Building an active
flight plan
•There are three transitions

listed for this approach.
•If no transition is selected, the
system will not load associated
waypoints for specific IAFs,
HILO patterns, Arcing or any PT
tracks.
• Because it is easier to bypass
potentially unneeded waypoints
upon arrival, than to reload the
approach to obtain additional
required waypoints. It is
recommended to select a
transition.
•For our example we expect the
DIYET transition. Select this
using LSK R3.
28
Building an active
flight plan
• appears beside
the approach and transition
you have selected.
•Use LSK R6 to move to the
LEGS pages to verify the
flight plan waypoint data
and sequence.
Note
if you wish to change your
selected approach, reselecting
LSK R1 will restore the list of
available approaches.
If you wish to change the

selected transition, reselecting
LSK R2 will restore the list of
available transitions.
29
Building an active
flight plan
Note
In our example we are viewing
LEGS page 1/3.
•Use current charts and

approach publications
(updated with NOTAMS and
TCNs) to review the flight
plan sequence insuring
there are no discrepancies
between what is current and
what has been retrieved
from the NAV database.
•Notice that the V222
waypoints (YARBO and
PICAN) between our V222
airway entry/exit points have
been automatically included.
•Use LSK LR to move
through the remaining pages
2/2 and 3/3.
30
Building an active
flight plan
•If the last point entered in

the route of flight differs
from the first waypoint on
the selected approach, a
ROUTE DISCONTINUITY
will be inserted following
the last waypoint point in
the Route of flight.
•The FMS will not
automatically sequence
past a discontinuity.
•To remove a discontinuity,
copy the first point
following the discontinuity
into the SCRATCHPAD
using the adjacent LSK
(DIYET at LSK L2 in our
example).
31
Building an active
flight plan
•Upload the waypoint to the

position of the discontinuity
(DIYET to LSK L1 in our example).
32
Building an active
flight plan
•Use LSK LR to continue

reviewing the remaining
pages for all waypoints
including missed approach
procedures, for sequence
and accuracy.
33
Building an active
flight plan
•There will be a flashing

light located near LSK UR
.
• This indicates that the
(modifications) have not
been saved/executed.
34
Building an active
flight plan
•Once the LEGS have

been reviewed for
accuracy, the UFCP EXEC
key is used to
save/execute the flight
plan.
35
Building an active
flight plan
•An additional method to aid

checking for route accuracy
(sanity check), is to use the
ROSE PLAN view on the NAV
page.
•From the NAV page select LSK
LL until the ROSE PLAN view is
displayed.
36
Building an active
flight plan
•Select a range scale that will

provide an uncluttered view of
the selected waypoint (the 5 nm
scale works well).
•Use the NEXT button at LSK

R6 to cycle through the
waypoints. Each time it is
pressed the display will cycle to
the next point in the planned
sequence.
•In this frame we are at KNSE

and the next point is to our
WNW.
37
Building an active
flight plan
•Now PENSI is centered

with the next point to the
North.
•The magenta line from
KNSE to PENSI indicates
the active leg of our flight
•The white lines from
PENSI onward indicate
inactive legs of the flight
plan.
•Press LSK R6 again to
move to the next waypoint.
38
Building an active
flight plan
•Now MVC is centered

with the next point to the
West (this is where we
joined V222).
•Press LSK R6 to move to
the next point
39
Building an active
flight plan
•YARBO with the next

point to the West.
the next point.
40
Building an active
flight plan
•PICAN with the next point

to the West.
the next point.
41
Building an active
flight plan
•LBY with the next point to

the North.
42
Building an active
flight plan
•Now that we are close to

the airport changing the
range scale will allow you
to view most of the
waypoints for the
approach.
•The (IAF) DIYET, (IF)
HILGA, (FAF) CUPPA and
part of the the (MAP)
RWY13/O.
•Press LSK R6 to cycle
through each point.
Note
NETTI on the approach plate is
not in the FMS database. It is
identified in relation to RWY13/O.
43
Building an active
flight plan
•IAF DIYET
44
Building an active
flight plan
•(IF) HILGA
45
Building an active
flight plan
•(FAF) CUPPA
46
Building an active
flight plan
•(MAP) RWY13/O
•The /O at RWY13 indicates a
“FLY OVER” waypoint (all GPS
missed approach waypoints are FLY
OVER points).
•After the MAP, selecting NEXT
(LSK R6) brings you back to the
beginning of the flight plan.
NOTE
On the NAV page, missed approach
waypoints are not shown until MISS APR
is selected. All waypoints can be viewed
on the TSD display once within range.
47
Building an active
flight plan
•At this point you can

return to the ROSE MAP
view by using LSK LL.
48
Building a standby
flight plan
•ROUTE 2 (RTE-2), the non-

active route, can be loaded for an
alternate or second destination.
•For our example we will assume
landing at KHBG (Hattiesburg)
and then departing RWY 13 to
KMSY (New Orleans INTL).
ORIGN – KHBG
DEST – KMSY
ROUTE – LBY1.LBY (SID)
LBY.RYTHM3 (STAR)
APPROACH – (Radar Vectors)
KMSY RNAV (GPS) Y RWY 10
49
50
51
52
53
54
Building a standby
flight plan
•From the ROSE MAP view of

the NAV page, use LSK L5 to
access the ROUTE page (also
accessible from the MFD MENU page
1/ 2).
55
Building a standby
flight plan
•From the ACT RTE 1 page

select RTE 2 (the inactive route) at
LSK L6.
56
Building a standby
flight plan
•All the characters are

cyan indicating that you
are working with an
inactive route.
•Now load the airport that
our second leg will begin
from as the RTE-2
ORIGIN.
57
Building a standby
flight plan
•Enter the second leg

ORIG, KHBG into the
scratchpad.
•Upload it to the ORIGN at
LSK L1.
58
Building a standby
flight plan
•Enter the second leg

DEST, KMSY into the
scratchpad.
•Upload it to DEST at LSK
R1.
59
Building a standby
flight plan
•We could use LSK LR

(NEXT) to move to page 2
(the VIA-TO page) to load a
route as before but for this
route there is a DP (SID),
that terminates at a
transition point for a STAR
to our destination.
•As long as there is at least
one waypoint between the
ORIGN and DEST the FMS
will accept the plan.
•In this case, we will move
to the DEP/ARR page to
retrieve the SID and STAR
waypoints.
•Press LSK UL to return to
the NAV page.
60
Building a standby
flight plan
•From the NAV PAGE

select LSK R5 to access
the DEP/ARR page.
NOTE
DEP/ARR pages are also
available from the MFD MENU
page 1/2.
61
Building a standby
flight plan
•Select DEP (departure

procedures) for KHBG
using LSK L3.
62
Building a standby
flight plan
•There is a SID (standard

instrument departure)
available for both runway
13 and 31. It is the LBY1.
(The graphic depiction for
this departure is located in
the Low Altitude Approach
Plates.
•Based on preflight
weather we will plan on
runway 13 for the
departure.
•Select the LBY1 SID
using LSK L1.
63
Building a standby
flight plan
• appears next to
LBY1 indicating it has
been selected.
•A note in the scratchpad
directs you to select a
departure runway.
•Use LSK R1 to select
runway 13.
64
Building a standby
flight plan
• appears next to
LBY1 and runway 13
indicating they are both
now selected for use.
•Return to the NAV page
using LSK UL.
NOTE
To change the SID, reselecting
LSK L1 will bring up the list of
available SIDs.
To change the RWY, reselecting

LSK R1 will bring up the list of
available RWYs.
65
Building a standby
flight plan
•From the NAV page

select LSK R5 to return to
the DEP/ARR page 1/1.
66
Building a standby
flight plan
•On the DEP/ARR page

1/1, select LSK R4 to
access available Arrival
options for KMSY (all
available STARs and or approach
procedures).
67
Building a standby
flight plan
•On the ARRIVALS page,

STARS will be listed on
the left, approaches on the
right.
•In the STAR publication,
we find that our
destination has 4 STAR
options. The RHYTHM
THREE ARRIVAL, (EATON
TRANSITION), begins at LBY
(the point at which our selected
SID terminated).
•Select the RHYTHM
THREE ARRIVAL
“RYTHM3” using LSK L3.
68
Building a standby
flight plan
•Note that the RYTHM3

ARRIVAL has been
selected.
•There are 4 published
transitions for this arrival.
•In our example, select the
LBY (EATON TRANSITION)
using LSK L3.
69
Building a standby
flight plan
•Note that the RYTHM3 STAR

and LBY TRANS indicate
selected.
•The associated waypoints
will provide navigational
guidance to our destination
terminal area.
•Next from the right side, we
can load an approach based
on preflight weather, NOTAMS
or information from the AP/1
and IFR Enroute Supplement.
•Note, there are 4 pages of
available approach procedures
in this example.
•Use the LR and LL LSKs to
find the page with the desired
approach procedure.
70
Building a standby
flight plan
•In our case, the RNAV

(GPS) Y RWY 10 (RNAV10
Y) appears on page 2/4.
•To load this approach with
all it’s associated waypoints,
press LSK R3.
71
Building a standby
flight plan
•Based on the expected

arrival, select an
appropriate transition.
•For our example load the
RQR transition (remember, it
is easier to delete any unneeded
waypoints than to reload the
entire approach).
•Select LSK R2 to load the
RQR transition.
72
Building a standby
flight plan
• now appears beside

our choices.
•Under STARS we have
selected:
-RYTHM3 (RYTHM THREE)
arrival
-LBY (EATON) TRANSITION
•Under APPROACHES we
have selected:
-RNAV10 Y APPROACH
-RQR TRANSITION
•Selecting LSK R6 CONFIRM,
will save the fight plan.
73
Building a standby
flight plan
•From the ARRIVALS

PAGE LSK R6 LEGS can
be use to access the RTE-
2 legs pages to review the
plan for accuracy and
address route
discontinuities as required.
NOTE
The LEGS page is also available
from the MFD MENU page 1/2.
74
DP
Building a standby waypoints
flight plan
•In this example there are three

pages of legs information
(viewing 1/3 at this time).
•Use the Hattiesburg SID from
the Low Altitude Approach Plate
to verify the departure
waypoints.
•Use the STAR publication to
verify ARRIVAL waypoints.
•Use LSK LR to move to the
next page.
1st two STAR

waypoints
75
Final
Building a standby STAR
flight plan waypoint
•On page 2/3, Use the

STAR publication to verify
the final ARRIVAL
waypoint.
•Note the discontinuity
between the STAR and
the approach.
•Use the Approach Plate
for KMSY to verify the
approach waypoints.
•Use LSK LR to move to
the next page
Approach
waypoints
76
Approach
Building a standby waypoints
flight plan
•Use the Approach Plate

for KMSY to verify the
remaining approach
waypoints including the
missed approach .
•To address the previously
noted route discontinuity,
use LSK LL to move back
to page 2/3.

Building a standby
flight plan
•The discontinuity can be

removed (close up the flight
plan) by pressing LSK L3 to
copy the first waypoint in
the approach (RQR) to the
scratchpad.
•With RQR in the
scratchpad it can be
uploaded to the point of
discontinuity by selecting
LSK L2.
NOTE
Where the discontinuity
represents a clearance limit,
leaving it in place may serve as a
reminder to obtain further
clearance prior to proceeding
past the clearance limit.
78
Building a standby
flight plan
•With the discontinuity

removed the FMS will
continue sequencing to
RQR after reaching
WAVEZ.
•LSK R6 CONFIRM must
be selected to save this
modification to the route.
79
Building a standby
flight plan
•With both flight plans

loaded return to the NAV
PAGE to begin the flight.
80
Manual RAIM check
•A RAIM (Receiver Autonomous

Integrity Monitoring) Check, can
be manually performed to predict
signal availability for your
destination.
•From the MFD MENU page 1/2,
select LSK R6 to access the
INITREF page.
Note
It is not recommended to perform
manual predictive RAIM request when
the aircraft is about to enter the
APPROACH phase of flight as the
FMS automatically sends request as
well. No manual request should be
performed when the aircraft is within 6
nm of the FAF waypoint. 81
Manual RAIM check
•On INIT/REF INDEX

page 1/2 select LSK R5
for NAV STATUS.
82
Manual RAIM check
•On the NAV STAUS

INDEX page 1/1 select
PREDICT RAIM using
LSK L1.
83
Manual RAIM check
•The destination airport is shown at

LSK L1.
•The ETA is shown at LSK L2
•Arrival times listed on the right
hand side of the display are for the
destination ETA (at LSK R2) and
intervals of 5 minutes before or
after the ETA up to a maximum of
15 minutes.
•The predicted Horizontal Integrity
Limits (HIL) codes/accuracy are
displayed next to the arrival times.
• Possible HIL codes/accuracy are:

-APPR </= .3 nm
-TERM >.3 but </= 1.0 nm
-ENRT > 1.0 nm but </= 2.0 nm
-NONE > 2.0 nm
-**** No HIL due to GPS sensor failure or
lack of current almanac information.
84
Selecting and
deselecting
satellites
•GPS satellites can be
excluded from the
Predictive RAIM
calculations.
•If a satellite is reported
unreliable via NOTAM’s,
use LSK R6 to access the
SAT DESEL page.
NOTE
The FMS automatically
disregards any satellite
not in its expected
location; therefore this
procedure is not normally
required.
85
Selecting and
deselecting
satellites
•On the GPS SAT
DESELECT page 1/1, key
the undesirable satellite’s
Pseudo Range Number
(PRN) into the scratchpad.
For our example we will deselect
PRN 07.
•Once in the scratchpad
upload the undesirable
PRN to the LSK L1
position.
86
Selecting and
deselecting
satellites
•The deselected PRN will
appear in reverse video
white color.
87
Selecting and
deselecting
satellites
•To Reselect a previously
deselected satellite the
process is very similar.
•Type the PRN you wish to
RESELECT into the
scratch pad (07 in our
example).
•Upload the desired PRN
to LSK L2.
88
Selecting and
deselecting
satellites
•The absence of any
highlighted PRN’s in the
list indicates all satellites
available for selection.
89
Radar departure to
the first waypoint
•During a Radar departure

it is not uncommon to be
vectored around traffic
prior to being cleared to
proceed to the first
waypoint.
•This can result in an “off
course” (CDI no longer
centered) situation.
•Once cleared to proceed
direct to the active
waypoint turn to the head
of FMS needle (BP 2).
90
Radar departure to
the first waypoint
•Once headed towards the

active waypoint we need
to get the FMS CDI to
reflect a new course from
our current position direct
to the active waypoint.
(Get the CDI to center)
•This can be
accomplished from the
LEGS pages.
91
Radar departure to
the first waypoint
•To set a direct course

from your present position,
to any waypoint in the
flight plan (PENSI in our case),
copy it to the scratchpad
by pressing it’s associated
LSK (LSK L1 for PENSI).
92
Radar departure to
the first waypoint
•Once the desired

waypoint is in the
scratchpad, upload it to
the active waypoint
position (LSK L1 on the
ACT RTE page 1).
93
Radar departure to
the first waypoint
•The EXEC light

will illuminate. To make
the modification
active press the EXEC
button on the UFCP.
94
Radar departure to
the first waypoint
•With the change Active

the new course will
provide tracking from the
aircrafts present position
to the active waypoint.
95
Turning at a
waypoint
•The FMS CDI provides

tracking information
between each waypoint in
the flight plan.
96
Turning at a
waypoint
•As you approach an

active FLYBY waypoint,
the waypoint name will
become highlighted in
magenta with white letters.
•The FMS will compute a
lead turn point that will
provide an on course
solution to the next
waypoint.
97
Turning at a
waypoint
•When it is time to begin

the turn to intercept the
next course, the head of
the FMS CDI will point to
the next course to be
flown on the HSI.
•The deflected CDI will
begin flashing. If a smooth
standard rate of turn is
used at this time, it will
result in an on course
indication at the end of the
turn.
Flashing New
CDI bar cours
e 98
Turning at a
waypoint
•The new active waypoint

and it’s distance will be
displayed on the PFD
(LSK R6 and L5) and also
on the NAV page.
New waypoint
and distance
New
waypoint
and 99
Manually inserting
a holding fix
•During the flight it may be

necessary to hold at any
of the waypoints along
your route.
•This can be
accomplished by
accessing the HOLD page
from the MFD MENU page
1/2.
NOTE
If there are no holding points in
the current route of flight, a /H
will be loaded into the
SCRATCHPAD and the LEGS
page 1 will be displayed.
100
Manually inserting
a holding fix
•If there is a holding point

already in the flight plan,
the first one in sequence
will be displayed. (in our
example it is HILGA, our missed
approach holding fix)
•On the RTE HOLD page
1/1, select NEW HOLD at
LSK L6.
NOTES
Selecting New Hold, will place a /H
in the SCRATCHPAD and bring up
the LEGS pages.
The /H can also be put into the

SCRATCHPAD manually using the
UFCP and manually switching to
the LEGS page.
101
Manually inserting
a holding fix
•Upload the /H to the LSK

adjacent to the desired
holding waypoint (we will
use MVC for our
example).
•This will return you to the
HOLD page with the
waypoint already loaded
with a default pattern
102
Manually inserting
a holding fix
•LSK L1 shows the

proposed holding FIX.
•LSK L2 can be used to
toggle between a RIGHT
(standard) or LEFT (non-
standard) pattern.
•LSK L3 shows the flight
plan course leading to the
FIX.
•LSK L4 is leg time
(defaulted to 1.0 minutes).
•LSK L5 provides leg
length in distance if
required.
•LSK R5 displays the EXIT
TYPE (This will always be
MANUAL for user created
holding fixes). 103
Manually inserting
a holding fix
•For our example we will

use the holding clearance;
“Hold south of the MVC

VOR on the 180 radial
make left turns with 5 mile
legs, expect further
clearance five minutes
after never.”
•Using LSK L2 we have

toggled TURN DIR to
LEFT for Non-Standard
holding.
104
Manually inserting
a holding fix
•The Holding course will be

360.
•Enter 360 into the
scratchpad and uploaded it
to LSK L3.
105
Manually inserting
a holding fix
•To set the leg length,

enter 5 into the scratch
pad and upload it to LSK
L5.
106
Manually inserting
a holding fix
•Review Holding data

LSK L1 FIX MVC
LSK L2 TURN DIR LEFT
LSK L3 INBD CRS 360°
LSK L5 LEG DIS 5.0 NM
•Once all data is reviewed
and correct the
(modification) will need to
be executed using the
EXEC button on the
UFCP.
•The green light will
be flashing at the top of
the display as a reminder.
107
Manually inserting
a holding fix
•Once the new holding

has been activated a
green /H will appear next
to the holding waypoint on
the LEGS page.
108
Manually inserting
a holding fix
•The holding pattern will Type

of
be depicted on the NAV holdin
page once it is within g
range. entry
•As you approach the fix a
message will be displayed
prompting the type of
holding entry to be used.
•Crossing the fix, the FMS
will not sequence beyond
a manually entered
holding waypoint until the
exit is armed or another
waypoint is maually
selected as the active Holding
waypoint. depiction
109
Exiting Holding
•Once established in
holding (anytime after first
passage of the holding
waypoint) and cleared to
proceed on course, the
EXIT HOLD should be
armed to allow the FMS to
resume normal
sequencing.
•To ARM the EXIT, select
the HOLD page from the
MFD MENU page 1/2.
110
Exiting Holding
•Use LSK R6 to select

EXIT HOLD.
111
Exiting Holding
•The green light is a

reminder that this
has not been
saved/activated.
•Pressing the EXEC button
on the UFCP will
save/activate the change.
112
Exiting Holding
•Once executed on the

UFCP, EXIT ARMED will
appear at LSK R6.
•With the EXIT ARMED,
the FMS will sequence to
the next waypoint at the
next passage of the
holding waypoint.
113
Deleting
a holding fix
•To cancel or remove an
existing holding waypoint
prior to entering holding,
simply enter / in the
scratchpad and upload it to
the existing holding
waypoint on the LEGS
page.
114
Deleting
a holding fix
•The modification will
require that the EXEC
button be selected on the
UFCP for the change to
take effect.
•This process will remove
Manually entered holding
fixes.
•It can also be used to
delete holding patterns
that are part of a loaded
approach procedure.
115
Enroute , Terminal
and Approach modes
•When PFD SOURCE is
FMS, the phase of flight is
displayed on the PFD. There
are three phases consisting
of:
-Enroute
-Terminal
-Approach
•During FMS operations, the
HSI lateral deviation scale
changes with the current
phase of flight.
•On departure the system will
be in the Terminal mode.
•HSI lateral deviation scale
will be: FMS
Phase of HSI lateral
- 1 NM full scale (.5 nm per deviation
dot). flight
scale 116
Enroute , Terminal
and Approach modes
•During departure, Terminal
mode remains active until
either of the following
conditions are met:
-The radial distance from the

departure airport becomes
greater than 33 nm.
OR
-The aircraft reaches 16,000
feet above the departure
airports elevation.
117
Enroute , Terminal
and Approach modes
•Transition from the Terminal
mode to the Enroute mode
will trigger the following
changes:
-HSI lateral deviation scale

changes over a 10 second
period from 1 nm to:
5 nm full scale (2.5 nm per
dot).
-The phase of flight indication

adjacent to the HSI will
change from TERM to
and flash for 15 seconds.
118
Enroute , Terminal
and Approach modes
•Upon reaching the
transition point from
Enroute to the destination
Terminal area, the NAV
page will display the
advisory message:
119
Enroute , Terminal
and Approach modes
•Transition from Enroute to
the destination Terminal
area requires:
-Radial distance from the

destination airport is less
than 30 nm.
AND
-The aircraft descends

below
15,000 feet above the
destination airports
elevation.
120
Enroute , Terminal
and Approach modes
•Arrival in the destination
terminal area triggers the
following changes:

changes over a 10 second
period from 5 nm to:
1 nm full scale (.5 nm per dot).
-The phase of flight

indication adjacent to the
HSI will change from ENR
to and flash for 15
seconds.
121
Enroute , Terminal
and Approach modes
•Approaching the destination
airport, with a valid GPS
approach selected and
loaded into the active flight
plan from the navigation
database, the following
indications will be noted:
• 3 nm prior to the FAF

- the NAV page will display
the advisory message;
122
Enroute , Terminal
and Approach modes
• At 2 nm inbound to the FAF, with
GPS approach integrity (RAIM)
predicted to exist at the FAF,
missed approach point (MAP),
and the current aircraft position,
the FMS transitions automatically
to the approach mode, with the
following indications:
ON THE NAV PAGE
-Non-precision approach
advisory illuminates at top of
MFD.
-The prompt is displayed at

the bottom right LSK on the NAV
page.
123
Enroute , Terminal
and Approach modes
ON THE PFD
-Non-precision approach
advisory illuminates at top of
MFD.
- replaces TERM adjacent to

the HSI and flashes for 15
seconds.

changes over a 10 second period
from 1 nm to:
.3 nm full scale (.15 nm per dot).
124
Missed approach
procedures
•Upon reaching the MAP

(missed approach point),
the FMS will not
automatically sequence to,
or display any follow-on
missed approach
waypoints.
125
Missed approach
procedures
•After the MAP, course

guidance along the FAC
will continue to be provided
by the FMS.
•Once initial missed
approach actions are taken
(two positive rates gear, above
110 flaps) the additional
(follow-on) waypoints can
be activated by selecting
LSK LR (MIS APR) on the
NAV PAGE.
126
Missed approach
procedures
•Once MISS APR is

activated, the FMS will
display and sequence
through any follow on
waypoints normally.
•Here the display shows

the need for a right turn to
proceed direct to HILGA/H
our missed approach
holding point which is 15.1
nm behind us.
127
Activating
RTE-2
•The inactive route (in our

example RTE-2) can be
activated to fly to your next
destination.
•This may be done on the
deck prior to taking off for
the second leg of your
flight or during a missed
approach.
•To activate an inactive
route, from the NAV page
select LSK L5 to access
the ROUTE page.
128
Activating
RTE-2
•On the ACT RTE page 1,

select LSK L6 to bring up
the inactive route (RTE 2
in our example).
129
Activating
RTE-2
•INACTIVE route
information will be
displayed in CYAN.
•Select LSK R6
(ACTIVATE) to change
this route from inactive to
active.
130
Activating
RTE-2
•This will bring up the RTE

2 LEGS page.
•The modification
will have to be accepted
by pressing the EXEC
button on the UFCP.
131
Activating
RTE-2
•Once executed, RTE 2

will be displayed as ACT
RTE 2 LEGS on the top
line.
•At this time you could
return to the NAV page
and continue your flight to
the next destination.
132
Radar Vectors to
Final Approach
Course (RVFAC)
•The last waypoint in the
flight plan to KMSY (prior to
the approach) is WAVEZ (part
of the RYTHM3 STAR).
133
Radar Vectors to
Final Approach
Course (RVFAC)
•From the RHYTHM
THREE ARRIVAL
DESCRIPTION, aircraft
receiving clearance for
approaches and landings to
anything other than RWY
19 at KMSY should expect
vectors to the final
approach course.
134
Radar Vectors to
Final Approach
Course (RVFAC)
•The following example will
outline procedures required
to set the FMS up to assist
with Radar vectors to the
FAF (KUSTE) for:
New Orleans/Louis
Armstrong INTL (KMSY)
RNAV (GPS) Y RWY 10.
•After WAVEZ The FMS was

programmed to RQR (the IAF
for this approach).
•Instead, we are receiving

vector to KUSTE (the FAF for
this approach).
135
Radar Vectors to
Final Approach
Course (RVFAC)
•During RVFAC we will
most likely receive vectors
that will not maintain the
FMS programmed track of;
WAVEZ, RQR, FIGUR,
KUSTE.
•To aid in orientation

during vectors to the FAF,
It would be helpful to
display an extended final
approach course leading
to the FAF KUSTE and set
KUSTE as the active
waypoint.
136
Radar Vectors to
Final Approach
Course (RVFAC)
•This can be
accomplished using the
LEGS pages.
•To access the LEGS
pages from the NAV page,
select LSK L2.
137
Radar Vectors to
Final Approach
Course (RVFAC)
•Use LSK LR (if required)
to access the LEGS page
with the FAF.
•In this example, KUSTE,
the FAF is located on
LEGS page 1/2.
•Copy the FAF KUSTE to
the scratch PAD by
selecting the adjacent LSK
(L3 in this example).
•Once the FAF waypoint is
in the scratchpad, upload
it to the active waypoint
position (LSK L1 on LEGS
page 1).
138
Radar Vectors to
Final Approach
Course (RVFAC)
•Note that the current
course to KUSTE is 179°
(this represents a direct course
from present position).
•If the modification is
executed (EXEC on the
UFCP) at this point, the
direct course of 179°
will be used.
•We are being vectored to
intercept the FAC of 106°
(the course between KUSTE and
RWY10).
•Note that the FMS has
placed 106° at LSK R6 as a
suggested FAC.
Note
Any desired course can be put
into the SCRATCHPAD and
uploaded as the INTC CRS. 139
Radar Vectors to
Final Approach
Course (RVFAC)
•The published FAC on the
approach plate is 103°, yet the
FMS FAC is 106°?
•Magnetic courses defined by
conventional NAVAIDS are
determined by the application
of the NAVAIDS magnetic
variation. In contrast, RNAV
GPS systems may use an
algorithm which applies the
magnetic variation and may
result in small differences in
the displayed course.
However both methods will
produce an acceptable solution
when using an approved IFR
navigation system.
•In this case the GPS database
acquired course of 106° will be
used.
140
Radar Vectors to
Final Approach
Course (RVFAC)
•To use the recommended
course of 106°, select LSK
R6
Note
It is important to note that when
you select LSK R6 (INTC CRS)
that the font used to display
106° will change from medium to
large and the green triangle next
to the INTC CRS ( ) will
disappear.
(This is really a small change,

ensure your attention is on the
course as you select LSK R6)
141
Radar Vectors to
Final Approach
Course (RVFAC)
•Note the following
changes on LEGS page 1:
-The font of the
listed at LSK R6 has
changed from medium to
large and the green
triangle had been
removed).
-The course leading to the
FAF KUSTE has changed
to 106°.
•To accept the

(modification) select
EXEC on the UFCP.
142
Radar Vectors to
Final Approach
Course (RVFAC)
•Note that
(MODIFICATION) has
changed to
(ACTIVE) and the FAF
is highlighted in magenta
as the new active
waypoint.
•Return to the NAV display

using LSK UL.
143
Radar Vectors to
Final Approach
Course (RVFAC)
•The NAV display now
shows the intercept
course extending outward
from the FAF.
•This will aid in general

orientation of our aircrafts
position and heading with
relation to the FAC during
radar vectors.
144
DME HOLD
Function
•Normally when a VHF
NAVAID frequency is tuned,
the FMS also auto tunes
the aircraft’s DME
transceiver to that
NAVAID’s paired UHF
frequency.
•In situations were DME
information is needed from
a source other than the
NAVAID being used for VHF
navigation, the DME HOLD
function can be employed.
•For example, the (KNPA)
ILS Z or LOC/DME 7L uses
DME from NPA (UHF
channel 119x) and Localizer
course information from I-
NPA (VHF 109.3). 145
DME HOLD
Function
•To use DME HOLD, the Enroute Chart Legend for
first action is to find the NAVAID and Communication
paired VHF frequency for Boxes
the our desired DME
channel (119x in our example).
NOTE
TACAN channels may be
assumed “X” unless noted as “Y”
Enroute Chart
•The paired frequency NAVAID Box for NPA TACAN
may be found on the
Enroute Chart (paired
frequencies are listed in
parenthesis).
146
DME HOLD
Function
•Paired frequencies may
also be found in the Flight
Information Handbook
(FIH).
147
DME HOLD
Function
•The FMS database also
has the frequency pairing
tables.
•To find the paired
frequency for NPA, select
the NAV TUNE priority
function Button (PRB) on
the UFCP to access the
NAV TUNE- VOR/LOC
page.
•Enter the NAVAID
identifier (NPA) into
window 2 and press ENT.
•The paired frequency will
be displayed in window 3.
148
DME HOLD
Function
•If the DME paired
frequency is known it can
be loaded into window 3
on the UFCP persistent
display.
149
DME HOLD
Function
•Next use the PFB NAV
TUNE to access the NAV-
DME page.
150
DME HOLD
Function
•The W2 key is used to
toggle between DME
HOLD ON/OFF.
NOTE
Presence of the letter H following
the frequency in window 2
indicates that DME HOLD is ON.
•Press W2 until the “H”

appears after the
frequency.
151
DME HOLD
Function
•Now on the persistent
display, enter the VHF
frequency required for
course guidance (I-NPA
109.3 for our example).
152
DME HOLD
Function
•The PFD will display the
VHF navigation frequency
just below the PFD
SOURCE and with BP 1
selected to VOR/LOC it
will also be displayed
adjacent to LSK L6.
153
DME HOLD
Function
•The Paired frequency and
it’s associated DME will be
displayed in AMBER color.
•Note the letter H
preceding the paired
frequency. This indicated
that DME frequency is
being held.
•Until the H is removed,
subsequent changes in
the VHF NAV frequency
will no longer auto tune
the DME transceiver.
154

Fms. Sy0302 Fms Trainer Part 2

Uploaded by

Copyright:

Available Formats

Fms. Sy0302 Fms Trainer Part 2

Uploaded by

Document Information

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

Fms. Sy0302 Fms Trainer Part 2

Uploaded by

Copyright:

Available Formats

T-6C FMS TRAINER 2

•The T-6C FMS provides the capability to preload a RTE-

•To clear an existing flight

•All previously existing

•Next put your destination airport

•In order for the FMS to accept

•Route of flight never begins

•Note that the word DIRECT

•Our next waypoint, MVC

•Once again the VIA line is

•At this point our route will

•We have now designated

•In the SCRATCHPAD,

•All waypoints that exist in

•From the MFD MENU

•On the DEP/ARR INDEX

•Note that there are no

•From the NAV page use LSK

•Arrival options for our

•Note there are no STARS for

•There are three transitions

If you wish to change the

•Use current charts and

•If the last point entered in

•Upload the waypoint to the

•Use LSK LR to continue

•There will be a flashing

•Once the LEGS have

•An additional method to aid

•Select a range scale that will

•Use the NEXT button at LSK

•In this frame we are at KNSE

•Now PENSI is centered

•Now MVC is centered

•YARBO with the next

•PICAN with the next point

•LBY with the next point to

•Now that we are close to

•At this point you can

•ROUTE 2 (RTE-2), the non-

•From the ROSE MAP view of

•From the ACT RTE 1 page

•All the characters are

•Enter the second leg

•Enter the second leg

•We could use LSK LR

•From the NAV PAGE

•Select DEP (departure

•There is a SID (standard

To change the RWY, reselecting

•From the NAV page

•On the DEP/ARR page

•On the ARRIVALS page,

•Note that the RYTHM3

•Note that the RYTHM3 STAR

•In our case, the RNAV

•Based on the expected

• now appears beside

•From the ARRIVALS

•In this example there are three