
9 - AUX PAGES
175
190-00357-00 Rev H
Utility Page
5a. For a stored flight plan (“Flight Plan” data
option), the flight plan number field is high-
lighted. Turn the small right knob to select
the desired flight plan and press ENT.
OR
5b. For a specified user waypoint (“User Waypoint”
data option), the waypoint identifier field is
highlighted. Use the small and large right
knobs to enter the identifier of the desired user
waypoint. Press ENT when finished.
6. The flashing cursor moves to the “CROSS-SIDE”
field. Turn the small right knob to select “To”
or “From” and press ENT.
7. The flashing cursor moves to the “Initiate
Transfer?” confirmation field. Press ENT to
transfer the selected data.
To perform Manual GTN Crossfill
The Manual GTN Crossfill Function allows the GNS
400W/500W series unit to manually send all User
waypoints to the connected GTN unit or receive infor-
mation from a GTN unit.
The information received from the GTN unit includes
the following:
• ActiveWaypointLeg
•
Active Flight Plan
•
Direct-To Waypoint
•
Suspend/OBS Status
NOTE: The databases of the 400/500 series and the
400W/500W are incompatible, so you may not mix
systems.
NOTE: Manual GTN Crossfill requires the 400W/500W
series unit to have the same Jeppesen NavData®
database cycle number as the GTN unit.
NOTE: Crossfill and Manual GTN Crossfill can not be
configured to be present at the same time. The chosen
feature is configured by the installer for your installa-
tion.
NOTE: Ensure that the GTN unit has Auto GNS
Crossfill enabled.
Manual GTN Crossfill is a feature that will keep the
GNS system in sync with a flight plan that is being used
on the GTN system. The GTN will not automatically keep
its flight plan in sync with changes made on the GNS sys-
tem. Essentially, the crossfill feature is “one way” – from
the GTN to the GNS.
The GTN systems support a variety of procedure leg
types that the GNS systems do not support. As such, it is
normal and expected that the flight plan leg that is dis-
played on the GNS system will not always match the flight
plan leg on the GTN system. Departure, arrival and ap-
proach procedures often contain leg types that the GNS
does not support. The GNS typically “skips” over these
leg types and provides no guidance. Guidance may be