Routepack structure – Jeppesen JeppView 3 User Manual
Page 173
JeppView User's Guide
176
•
— Provides an overview of how a RoutePack displays
airports, terminal charts, alternates, and other airports not associated to the
route.
•
— Guides you through creating a RoutePack using the
RoutePack Wizard. This topic also provides methods to create just the
RoutePack, and add a route later by either using the RoutePack Wizard or by
using the point-and-click method.
•
— Describes how to create a route in an
existing RoutePack using the RoutePack Wizard, and how to use the Enroute
Charts view to create a route by using the point-and-click method.
TIP
RoutePacks created in a Jeppesen program, such as FliteStar version v9,
FliteDeck v3 and JetPlanner v2.1 and later, can be saved and opened in
any other RoutePack-capable program.
RoutePack Structure
It is important to understand the hierarchy of the RoutePack so that you can
manipulate and use the RoutePack List to your benefit.
A RoutePack is structured to contain multiple routes and alternate routes, as well as
an Other Charts folder, which holds airports not necessarily linked to a specific route.
Terminal charts for the airports contained in the route are organized under their
associated airport in the RoutePack.
As shown in the image below, RoutePacks are organized by the following levels:
Level 1 contains RoutePacks.
Level 2 contains routes and the Other Charts folder. Each RoutePack
can have multiple routes and its own Other Charts folder.
Level 3 contains route waypoints (airports, navaids, and
waypoints) and the airports in the Other Charts folder.
Level 4 contains terminal charts (attached by a dotted
line to their airport) and alternate routes. The first
airport in the alternate route is the airport to which it is
attached.
Levels 5 contains alternate route airports and
waypoints.
Level 6 contains terminal charts for
airports in the alternate route.