Professional Documents
Culture Documents
Common Tasks
JetPlanner Common Tasks
Jeppesen
55 Inverness Drive East
Englewood, Colorado 80112-5498
Revision 1.0
Copyright © 2015 Jeppesen. All rights reserved.
Except as otherwise provided and authorized in a written agreement between both Jeppesen and your company,
Jeppesen's copyrighted information and materials may not be processed, reformatted, reproduced, stored in a
retrieval system, or transmitted in whole or in part, in any form or by any means, whether electrical, mechanical,
photocopying, recording or otherwise, without prior written permission of Jeppesen.
Microsoft, Windows XP, Windows Vista, Windows 7, and Internet Explorer are either registered trademarks or
trademarks of Microsoft Corporation in the United States and/or other countries.
Product or brand names may be trademarks or registered trademarks of their respective owners.
Contents
Chapter 1: Introduction 1
Who Should Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Chapter 2: Overview 5
About JetPlanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Creating a New User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Updating Your Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chart View User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Selecting Data to Appear in Chart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Changing Themes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Displaying Groups of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Focusing on Desired Areas of the Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Displaying Details about an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Changing Attributes of Groups of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Displaying Raster Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Creating a Flight Plan in Flight Plan Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Converting Units of Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Finding Details in the Help File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Getting Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Key Terms and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
NOTES Contents
Chapter 4: Routing 39
Introduction to Routing with JetPlanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Jet Airways Optimization (J) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Why Use Jet Airways Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Indicating Jet Airways Optimization in the Route String . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Navigation Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Why Use Navigation Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Indicating Navigation Optimization in the Route String . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Direct Optimization (D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Why Use Direct Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Indicating Direct Optimization in the Route String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
User-Specified Optimized Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Rules for User-specified Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Route String Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
J,NAV1,NAV2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
NAV1,NAV2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
J,NAV1,D,NAV2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
J,D,NAV1,NAV2,D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
User-Specified Routing with SRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Why Use User-Specified Routing with SRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Route String Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Route String Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
-NAV1 NAV2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
-SID1 NAV1 NAV2 STAR1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
-SID1 NAV1 J10 NAV2 STAR1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
-SID1 NAV1 J10 NAV2 N45W045 N45W030 NAV2 STAR1 . . . . . . . . . . . . . . . . . . . . . . 51
Index 171
Introduction
This guide is for flight planners and pilots who access a JetPlan flight-planning engine through
JetPlanner.
For more information about the JetPlan engine and the engine’s traditional “Question and
Answer” command-line inputs, see the JetPlan User Manual.
Product Support
Australia: 61-73105-9450
Email: opssupport@jeppesen.com
Overview
About JetPlanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Creating a New User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Updating Your Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chart View User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Selecting Data to Appear in Chart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Changing Themes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Displaying Groups of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Focusing on Desired Areas of the Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Displaying Details about an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Changing Attributes of Groups of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Displaying Raster Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Creating a Flight Plan in Flight Plan Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Converting Units of Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Finding Details in the Help File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Getting Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Key Terms and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
NOTES Overview
About JetPlanner
About JetPlanner
JetPlanner is a Windows-based user interface that provides access to the Jeppesen JetPlan
flight-planning engine. This user interface enables flight planners to create full-featured flight
plans.
Use JetPlanner to access the JetPlan flight-planning engine to create, run, and review flight
plans at any time and from any location. JetPlanner uses an internet connection to submit flight
plan requests to the online JetPlan engine. The flight-planning engine calculates the flight plan
and returns alerts and error messages if necessary.
You can access more tabs and features to complete the following tasks and refine flight plans:
• Retrieve text weather reports.
• Retrieve graphical weather reports.
• Choose alternates.
• Work with flight plans (including filing flight plans with ATC authorities and
sending messages).
• Manipulate flight levels.
• Calculate payload and fuel.
If your organization updates data with an internet connection, use the following procedure.
3. On the Update Databases dialog, select the check box Check/Uncheck All and
click Submit.
4. When the update completes, on the Account Databases dialog click Close.
JetPlanner displays weather images on the Chart View regardless of NavData. Wind data is
available down to 3,000 feet MSL. For information about accessing weather data through
JetPlanner, see Chapter 8, “Retrieving Weather Reports.”
Changing Themes
A theme displays objects in Chart View, such as High Altitude Enroute features. You can
change the theme to meet your needs for particular flight -planning tasks.
Examples of data that you can display with buttons on the Preferences toolbar are as follows:
VORs
JetPlanner displays a dialog box that is named for the airport. [Figure 2.8]
Example You can change the thickness and color of oceanic tracks.
Example
To create a flight plan request with the Flight Plan wizard, do one of the
following
• Do one of the following:
• From the File menu, click New Request
• From the View menu, click Flight Plan Manager Bar and in the Flight Plan
Manager click Create Flight Plan.
• From the View menu, click Personal Folder Bar, and in Personal Folders
right-click and select New and then select Request.
JetPlanner displays the Flight Plan wizard. [Figure 2.11]
Once the flight plan request exists, you can hide and display the Flight Plan wizard by
pressing F4. To close the Flight Plan wizard, click Close.
To convert units of measure, from the Tools menu, click Conversions. You can copy the
result of the conversion to the Windows clipboard with the To Clipboard button.
AC Aircraft.
Altitude range An altitude profile that specifies lower and upper limits within which
the aircraft climbs or descends as flight rules or performance dictates.
Call sign An identifier for filing purposes. The call sign is an optional
JetPlanner input.
CFMU Central flow management unit, a means of validating a flight plan for
European airspace.
Constrained IFR A flight rule that applies instrument flight rules (IFR) but avoids step
climbs and descents while the aircraft is transiting specific organized
track structures (OTS), such as the North Atlantic Tracks (NAT).
FIR Flight information region, a defined airspace within which pilots can
obtain flight information and alerting services.
GRID MORA Minimum Off Route Altitude. GRID MORA is a Jeppesen method
for depicting the minimum flight altitude within a charted grid
formed by the lines of latitude and longitude.
Hard altitude An altitude profile input that maintains one flight level for an enroute
segment or the entire flight.
ID Identifier.
MEA Minimum enroute altitude. The minimum altitude at which pilots can
receive reliable VOR signals along a specific segment of an airway.
MEAs also ensure 1,000-foot clearance (2,000 feet in mountainous
terrain) of any obstacle within five nautical miles of the airway
centerline.
NRP National Route Program. The NRP allows flights that operate at or
above 29,000 feet within the conterminous U.S. (regardless of city
pairs) to participate in minimum time/cost routes without being
subject to route-limiting restrictions.
OTS Organized track structures. Sets of routes for flight over water.
UIR Upper flight information region. An airspace that covers the same
geographic area as a FIR but extends vertically upward from 24,500
feet.
VFR Visual flight rules. Procedures and rules associated with minimum
cloud clearance and visibility requirements.
WX Weather.
Standard Tab
The Standard tab contains most of the features to create flight plans. It is the default tab of the
Flight Plan wizard. Figure 3.5
NOTE If you enter the hold time value without entering an alternate airport, the
JetPlan engine applies this time to POA. If you enter an alternate, the JetPlan
engine applies this time to the alternate. If a default hold time is in the
database, entering a Hold Time overrides that default setting.
5. For ETD, enter a four-digit UTC (Zulu) value to define the estimated time of
departure. You can specify a time up to 23 hours and 59 minutes from the current
time.
6. In the Aircraft Name box, select an aircraft from the downloaded aircraft
database.
NOTE If the aircraft database defines a default cruise mode for the aircraft that you
select, the JetPlan engine uses that value in the Cruise Speed box on the
Standard tab.
7. On the Rte list, select the route type (example: Optimized jet airways).
8. In the Cruise Speed box, select the primary cruise mode if the box is blank.
When current NavData is available in Chart View, you can drag the great circle line with the
PC mouse to edit the flight plan request (“rubber-banding”). JetPlanner plots the line as solid
while you drag it, then changes the line to dashed when you finish. When you submit the flight
plan request, it contains the data implied by the modified great circle line—for example, by
including a must-fly point.
With or without rubber-banding, the flight path is subject to optimization and other routing
features. For more information about these features, see Chapter 4, “Routing.”
2. In the Fuel box to the right of the weight and time option buttons, enter the
amount of fuel for the unit of measure that you chose.
3. To instruct the JetPlan engine how to calculate the fuel amount, click Arrival or
Departure:
• Departure calculates the fuel amount that you have on takeoff.
• Arrival calculates the fuel amount that you have on arrival.
4. For Reserves, select the type of fuel reserves to use for this flight.
For example, the International Reserves option uses default international reserves
in the flight plan calculation.
For more information about autoweight, see “Completing Payload Information” on page 33.
To choose the output format and submit the request for processing
1. (Optional) To override the default plan layout, select the Output Format
check box and then enter the appropriate three-character code in the Output
Format box.
2. Click Submit to send the request for processing.
If the flight plan request processes without error, JetPlanner plots a solid route line in
Chart View. This solid line is the calculated route of flight, and generally follows the dashed
great circle line. Figure 3.12
Figure 3.5 A route line and great circle line in Chart View
Routing
The JetPlan engine supports two routing methods, which you can use separately or in
combination: Route Optimizer and Specific Route Selector (SRS) [Figure 4.1]. A combination
route uses one or more SRS segments with one or more optimized segments in the same plan.
Combination routes provide benefits of both types of routing.
The Route Optimizer dynamically calculates the most efficient flight path with wind direction
and speed. Depending on the general course of flight, the Route Optimizer maximizes a
tailwind or minimizes a headwind.
The Specific Route Selector enables you to enter a route as you would file it with ATC. The
results are predictable because no optimization occurs.
1. The JetPlan flight-planning engine chooses a SID or STAR if the SID or STAR transition point is in
the optimized route and the SID or STAR is in the navigational database.
Optimization
Your database administrator sets the optimization goal—to minimize fuel, time, or expense—
for each aircraft in the aircraft database. JetPlanner uses the selected source of wind data to
accomplish the optimization goal. If your route includes must-fly waypoints, the Route
Optimizer optimizes to and from each must-fly waypoint.
The Route Optimizer processes the identifier of standard instrument departure (SID) or
standard terminal arrival (STAR) as the name of an airway.
The optimizer chooses waypoints, SIDs, and STARs, based on the following conditions:
When the J option is active, the Route Optimizer respects any time and directional restrictions
of airways.
J as the first input in the route string specifies optimized jet airways as the default routing
method for the plan.
Navigation Optimization
Navigation optimization uses direct segments between navaids as the primary routing method.
Airways may be part of the route, but navigation optimization does not actively search for
airways.
The optimizer chooses waypoints, SIDs, and STARs, based on the following conditions:
If wind is zero between points, the direct route is approximately the great circle route. The
variance depends on the location of the nearest 5-degree or 10-degree lat/long point.
• For routes that are mostly east/west, direct optimization calculates checkpoints at
every one degree of latitude and ten degrees of longitude.
• For routes that are mostly north/south, direct optimization calculates checkpoints
at every five degrees of latitude and one degree of longitude.
You can also use direct optimization to specify direct segments within a navigation-optimized
or jet airways optimized route. Verify that the latitude and longitude precision meets your
requirements.
NOTE If the POD and POA are the same airport, you can use direct optimization to
reverse the direction of the flight. You can apply direct routing to almost any
segment of the route.
You cannot specify Optimize Jet Airways and Navigation Optimized in the same segment of a
route string.
After specifying the primary optimizer, you can specify a direct segment anywhere else in the
route by using the Direct Optimize command (“D”). Identifiers for SIDs, STARs and airway
segments are not valid inputs for Direct optimization.
NOTE While using User-specified optimized routing, separate inputs with a comma.
J,NAV1,NAV2
In this example, Jet airways is the default mode of optimization. The route optimizer uses “J”
rules to NAV1.
Because the example does not specify a direct segment between NAV1 and NAV2, the JetPlan
engine uses the default “J” to find airway routing between the two points. The default "J" also
applies from NAV2 to the POA.
NAV1,NAV2
In this example, no command appears for the route optimizer, so Navigation is the default
mode of optimization. The route optimizer uses Navigation-optimized rules to NAV1.
The example does not specify a direct segment between NAV1 and NAV2, so the JetPlan
engine uses the default Navigation Optimizer to find the most efficient route between the two
points. The default Navigation Optimizer also applies from NAV2 to the POA.
J,NAV1,D,NAV2
In this example, Optimize Jet Airways is the default mode of optimization.
The example specifies direct optimization between NAV1 and NAV2 with the “D” command.
This command overrides the “J” and plans a Direct optimized route for this particular segment.
From NAV2 to the POA, the default “J” applies.
J,D,NAV1,NAV2,D
In this example, Optimize Jet Airways is the default mode of optimization.
Immediately following the default “J”, the “D” specifies a Direct optimized segment from the
POA to NAV1. The Route Optimizer overrides the “J” command for the first segment, so the
segment from the POD to NAV1 is a Direct optimized.
No command appears between NAV1 and NAV2, so the Route Optimizer uses the default “J”
between these two points.
The “D” command after NAV2 specifies a Direct Optimized segment from NAV2 to the POA.
IMPORTANT With SRS, the JetPlan engine calculates every route entry that you
specify, regardless of compliance (or lack of compliance), within the
airspace of the flight.
SRS routing is more efficient for expressing particular flight plan requirements. SRS enables
you to:
When you use SRS, separate all inputs with spaces rather than with commas or other
separators.
Because the Route Optimizer is off, all route segments are great circle direct unless you
specify a SID, a STAR, or airway segments.
To specify a transition point for a SID or STAR, specify the SID/STAR identifier and its
published transition point. Use a space or period to separate the SID/STAR identifier and point
identifier.
To specify a runway with a SID/STAR, append the runway identifier to the name of the SID or
STAR. Use the syntax sidstar$#$, where sidstar identifies the SID or STAR, and #
specifies the runway. The runway number must be two digits. Use L for a left runway, R for a
right runway, and B for a procedure that is common to parallel runways.
-NAV1 NAV2
In this example, a direct route from the POD to NAV1 is planned, direct from NAV1 to NAV2
and direct from NAV2 to the POA.
Upon reaching the transition point NAV1, a direct route is planned from NAV1 to NAV2.
NAV2 serves as the published transition point to finish the flight plan on the STAR1 arrival.
The plan follows airway J10 to NAV2, which serves as the published transition point onto the
STAR1 arrival.
The plan follows airway J10 to NAV2. From NAV2 the aircraft flies a direct route to two
lat/long points.
Following the second lat/long point, a direct segment to NAV2 is planned. NAV2 is the
published transition point for the STAR1 arrival.
Specifying Direction
To indicate direction, a coordinate requires a single-character prefix or suffix (one or the other
but not both): N or S or E or W.
Specifying Coordinates
Table 4.2 specifies the rules for specifying latitude and longitude coordinates.
Features and
Examples Latitude Longitude
Direction Single-letter prefix or suffix—one or the other but not both:
N or S or E or W.
Numerals • One or two digits indicate degrees • One to three digits indicate degrees
• If three or four digits, the last two • If four or five digits, the last two indicate
indicate minutes minutes
Examples Each of the following indicates 37 degrees Each of the following indicates 98 degrees
12 minutes and 4 tenths of a minute North 23 minutes and 6 tenths of a minute West
latitude and receives the same output from longitude and receives the same output
the flight-planning engine: from the flight-planning engine:
• N3712.4 • W09823.6
• N3712 • W09823
• 3712.4N • 09823.6W
• 3712N • 09823W
Specifying a Point
To specify a lat/long point, type the latitude coordinate followed by the longitude coordinate.
Optionally separate the coordinates with a slash, space, or comma.
Examples To specify the point from the previous examples, use any of the following inputs
to produce the same output from the flight-planning engine:
N3712.4/W09823.6
N3712/W09823
N3712.4/09823.6W
N3712/09823W
N3712.4W09823.6
N3712W09823
3712.4N09823.6W
3712N09823W
Naming a Point
By default, the JetPlanner flight-planning engine names a lat/long point internally by
combining the first two digits of the latitude with the second and third digits of the longitude.
This internal name is visible in the flight plan output from the engine.
You might decide that you want to specify your own names for ad-hoc lat/long points so they
are easier to interpret in the flight plan.
To name an ad-hoc lat/long point, precede the lat/long coordinates with the text name in
parentheses:
(name)latlong
where:
(name) is an optional, ad-hoc name that appears in the flight plan output. The
name can be 1 – 6 characters in length. The characters can be alphanumeric or
special. If you use a name, put it in parentheses. Otherwise, omit the parentheses.
latlong specifies the latitude and longitude of the point using the coordinate
rules.
In the following example, the name CP1 appears in the flight plan output for the coordinates
N3712W09823:
(CP1)N3712W09823
You can use multiple switch commands within the same route string.
The transition from the last entry before the “--” to the first input after the “--” must be valid.
-SID1 NAV1--J
In this example, routing begins in SRS mode.
The “--” command switches the route mode from SRS to the new route segment, which is
Optimized.
Within the optimized segment, the “J” command activates Optimized Jet Airways from NAV1
to the POA.
For a valid transition between the last entry before the “--” and first entry after the “--”,
NAV1 must be on an airway.
NAV1--STAR1
In this example, Navigation Optimized is applied from the POD to NAV1.
-SID1 NAV1--J,NAV2--STAR1
In this example, routing begins in SRS mode.
The SID1 departure is planned to NAV2. Because NAV2 is also a point on an airway, the Jet
Airway optimizer can optimize from NAV1 to NAV2. NAV2 is the published transition point
for the arrival STAR1.
Then you select a database route for the plan in either of two methods.
One method is to select The most optimal database route from the Rte list on the Standard
tab on the Flight Plan wizard. [Figure 4.6] This method optimizes from all routes in your
organization’s route database between the POD and POA. The POD/POA on the flight plan
request must match the airport pair of the database record.
The other method is to select a specific database route that you know exists between the POD
and POA. The names of the stored database routes appear just above the The most optimal
database route option in the Rte list.
When you select a specific route name, the JetPlan engine generates a flight plan using only
data from that specific route database record.
These stored database routes are available for selection from the Rte list only if you have
downloaded your route database with Tools > Account Databases > Update.
Examples Search only the database route groups that you specify (Inclusive of Route
Group)
Exclude groups from the search (Exclusive of Route Group).
You can specify a route by name. If the database record exists and its airport pair matches the
POD/POA on the flight plan request, the JetPlan engine uses that record. [Figure 4.9]
If the route request is too long, the JetPlan online flight-planning engine returns a message that
is similar to the following:
To request a complex route more efficiently, use waypoints from your organization’s database
instead of ad-hoc points.
Planning an ETOPS
Route
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Completing a Basic Flight Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Analyzing Airport Coverage with the Equal Time Points Tool . . . . . . . . . . . . . . . . 64
Analyzing Coverage of Extended Range Airports . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Displaying Detailed Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Adjusting Segment Icing Percentages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
NOTES Planning an ETOPS Route
Introduction
Introduction
JetPlanner enables you to analyze and plan routes that require equal time points (ETP) and
extended operations (ETOPS).
The JetPlan flight-planning engine does not interpret lists of ETOPS alternate airports
(“suitable”) or ETP airports as a routing constraint or requirement. You ensure that the route
meets your requirements by visually inspecting the route that the flight-planning engine
returns. If all of the route is within the range rings of ETOPS alternate airports, then the route
meets ETOPS routing requirements. If all of the route is within the range rings of ETP
airports, then the route meets your organization’s requirements.
The following information introduces these features and suggests a method to complete a
flight plan with coverage by extended range and adequate range airports:
1. “Completing a Basic Flight Plan” on page 63
2. “Analyzing Airport Coverage with the Equal Time Points Tool” on page 64
3. “Analyzing Coverage of Extended Range Airports” on page 68
4. “Displaying Detailed Calculations” on page 70
5. “Adjusting Segment Icing Percentages” on page 71
Figure 5.1 shows the great circle line from ENGM to MMUN and an optimal route line that is
south of the great circle line.
After you have a route line, analyze the route for coverage by ETP and ETOPS alternate
airports. The Equal Time Points tool and the Flight Plan wizard help you identify ETP and
ETOPS alternate airports that are appropriate to the route.
To analyze a route for ETOPS coverage, use the Equal Time Points tool. To display airports,
range rings, and arrows for equal time points on the chart, click the Route range rings button
( ). For general Chart View tools and techniques, refer to “Chart View User Interface” on
page 10.
When the chart shows all of the airports that you want for analysis, use the ETP tool to specify
and draw range rings around potential airports. The route line either is, or is not, completely
within those range rings.
Analyze both sets of airports, ETP and ETOPS alternates. Choose the set of airports to analyze
first with respect to your organization’s operational specification and your own work
preferences. In the method that follows, coverage of ETP airports is analyzed first. In this
example, the distance to an ETP airport is the binding constraint because that distance is
always smaller than the distance for an ETOPS alternate airport. If the route is sufficient with
ETP, then it is sufficient with ETOPS alternate airports.
The Equal Time Points tool is a visual analysis tool only. It receives a list of SCM data sets
from your organization’s database, but it does not affect the inputs, nor does it affect the
outputs, of flight plan calculations. You separately manage data between the tool and the flight
plan.
To display range rings for a list of airports with the Equal Time Points tool
1. Click Tools, and then click Equal Time Points (or press Ctrl + E).
JetPlanner displays the Equal Time Points dialog box.
If a flight plan route is on the chart, then JetPlanner fills the SCM Data Set list
with the data sets that are available for the flight plan aircraft.
2. If the SCM Data Set list is active, select the correct data set for the analysis.
3. In the Name box, type a name for the analysis that you want to perform.
In Figure 5.2, the name is for a potential route.
4. In the Distance box, type the distance of the range rings in nautical miles.
5. To instruct JetPlanner to display range rings for the airports, in the Range group of
the dialog box, click Display.
6. For each airport that you want to analyze, click in an empty Airport cell and type
an airport identifier.
JetPlanner fills the Description box with the name of the airport and displays the
range ring. The list of airports does not need to be in alphabetical or flight-plan
sequence.
7. To control other display features, use the controls in the Coverage Display group.
After you analyze the route for coverage by the airports, you might need to adjust the route
with a must-fly waypoint or other criteria, and then adjust the list of airports. The route line in
Figure 5.3 shows several hundred miles of exposure outside of ETP.
Figure 5.3 ENGM MMUN southern route with range rings. The chart projection makes the range
rings seem different in size.
Figure 5.4 shows a northern route for the flight that includes a point near CYYR as a must-fly
waypoint. The range rings completely enclose the route line, so you consider the coverage of
this route as adequate. You can confidently proceed with the ETOPS analysis.
Figure 5.5 ETOPS tab ***don’t have enough shots here. Need to
address 4.6***
Figure 5.6 Equal time point arrows for ETOPS alternate airports on the ETOPS tab
Restricted Areas
NOTE If you try to avoid a restricted area that is part of a stored route, the flight-
planning engine returns an error. You cannot include and exclude the same
airspace for the same flight plan. If the restricted area is part of an SRS route,
the flight-planning engine ignores the restriction.
For users with the same JetPlanner ID and password to share information, you can download a
copy of your organization’s database of restricted areas to your PC.
Figure 6.1 Country Avoid list on the Route & Time tab
3. Click the name of the region to avoid, and then click OK.
JetPlanner closes the Select an Item list and shades the selected region in
Chart view.
4. Right-click the boundary of the shaded region, and then click Avoid. [Figure 6.3]
JetPlanner includes the region identifier on the Route & Time tab of the Flight
Plan wizard. [Figure 6.4]
User-Defined Data
Example You can add user-defined waypoints and other features to plans.
You can locally define the following types of data and add them to a flight plan:
• Waypoints
• Navigational Aids
• Ground Reference Points
6. To add a waypoint to the route, select the waypoint and click OK.
Retrieving Weather
Reports
4. Select a weather report in the Text Weather dialog box, and then click OK.
The Text Weather dialog box appears with the entry for the weather report.
[Figure 8.2]
5. Click Submit.
6. After the weather report downloads, in the Text Weather dialog box, click Close.
7. To review the report, click the Text Weather tab and select the report from the
Text Weather Manager. [Figure 8.3]
To append text weather to the flight plan when you submit the request
1. In the Flight Plan wizard, click the Weather tab. [Figure 8.5]
2. Select one or more check boxes for the types of weather data that you want
(example: METAR).
3. Select one or more check boxes for types of weather stations to report (example:
POA).
4. If you want to receive enroute weather, select the Append enroute weather to
flight plan check box.
2. If the Raster Images and Vector Images tabs are empty, select the Update
weather inventory check box and click Submit.
JetPlanner updates the inventory of graphical weather.
3. Select the region that you want.
4. Select Raster Images or Vector Images.
5. Click the plus sign (+) to expand an image type; then select the option boxes for
the weather images that you want.
6. Click Submit to download the weather images.
7. (Optional) In the Description list, enter a name for the template.
8. Click Save, and then click OK. [Figure 8.7]
11. In Graphic Weather manager, select the name of the weather images that you
want to view.
Satellite weather
Infrared satellite Measure the temperature of the reflecting surface. Maps update at
images different intervals depending on the imagery type.
Base reflectivity Measure the intensity of radar echo returns from precipitation
(NEXRAD radar particles. Maps update every six minutes and contain the most recent
base reflectivity) NEXRAD mosaic.
maps
Echo tops Depict the height, in hundreds of feet, of the highest echo returns.
Maps update every six minutes and contain the most recent
NEXRAD mosaic.
One-hour Represent the cumulative inferred precipitation over the past hour.
precipitation maps Maps update every six minutes and contain the most recent
NEXRAD mosaic.
Radar composites Combine reflectivity values and echo tops as reported by NEXRAD
Radar Coded Messages (RCM). Maps update every 30 minutes on the
hour and at the half-hour.
Single-site radars Depict the actual base reflectivity from the individual NEXRAD
radar sites.
Surface weather Contains the most recent observations from the stations on the map.
depictions Maps update once per hour (usually close to the hour).
Surface analyses Depict the latest METAR observations for various regions with radar
and satellite imagery. Maps are available for various regions.
Surface weather Depict conditions from the surface to FL240. Maps are available in
forecasts 24-hour forecast periods for various regions.
Low-level Depict conditions from the earth’s surface to FL240 in 12- and 24-
significant hour forecast periods. Maps update four times each day, and the valid
weather forecasts time appears on the lower margin of each panel.
Low-level Available for the United Kingdom and Northwest Europe. To access
significant these maps, click the U.K. Met Office T4 Charts button in Graphic
weather maps World Weather Regions window.
(surface-FL100)
Low-level spot Available in nine-hour forecast periods for the United Kingdom and
wind maps European Union. To access these maps, click the U.K. Met Office T4
(FL010-FL240) Charts button in the Graphic World Weather Regions window.
Mid-level Available for Europe, the Middle East, and India. To access these
significant maps, click the U.K. Met Office T4 Charts button in the Graphic
weather maps World Weather Regions window.
(FL100-FL450)
North Atlantic Graphically depict the twice-daily ABC and XYZ North Atlantic
tracks tracks. The ABC westbound tracks maps are online from 2300
through 0100 UTC and are valid from 1130 to 1900 UTC. The XYZ
eastbound tracks are online from 1200 through 1400 UTC and are
valid from 0100 to 0800 UTC.
Upper-level wind Issued every three hours for the regional United States at six-hour and
and temperature twelve-hour forecast periods; maps for all other areas update every
maps six hours at 12- and 24-hour forecast periods.
Icing maps Available for the U.S. at the following forecast periods: 00, 03, 06,
12, 18 and 24 hours
Turbulence maps Available for the U.S. at the following forecast periods: 00, 03, 06,
12, 18 and 24 hours.
IFR AIRMETS Updated every hour and are available 30 - 45 minutes after the hour.
SIGMETS and Updated every hour and contain the most recent information. Maps
convective are available 20 - 30 minutes after the hour.
SIGMETS
Lifted index maps Updated four times a day and are valid at 0000, 0600, 1200 and 1800
UTC. Maps remain available one-and-a-half hours after the valid
time.
Hurricane/ Depict the name of the storm at the current position for each system.
typhoon tracks Also depicted is the day of the month and time of the current position
or forecast. Below the day and time is the central pressure of the
storm in mb, and below that is the wind speed in knots.
Lightning maps Available every 10 minutes and include all lightning detected during
that 10-minute period.
Choosing Alternates
By default, the JetPlan engine uses great circle routing to determine the distance, optimum
altitude, and required fuel to the alternate. To ensure that the JetPlan engine adds fuel to the
calculations, you can specify a greater distance to the alternate.
Example The actual distance from KDEN to KCOS might be 60 nautical miles, but you
specify 100 nautical miles of distance. JetPlanner adds fuel for 100 nautical miles
to the alternate fuel block rather than the actual 60 nautical miles.
Your organization’s database might contain alternate routes. You can manipulate the altitude
only if you are using an alternate route that is stored in the database.
Table 9.1 Settings that affect alternate fuel and distance calculations
Setting Comments
Alt Type Type of alternate, either Primary, Secondary, Departure, or Enroute. Each type is
associated with generic values in the JetPlan database. Usage of Departure and Enroute
alternates depends on the flight plan format.
By default, JetPlanner adds fuel to the flight plan for the Primary alternate. You can
include secondary alternates, but JetPlanner only considers fuel for the secondary
alternates when you use the JAR-OPS uplift philosophy.
Hold time The JetPlan engine uses hold time (in minutes) to calculate a holding fuel amount.
By default, JetPlan calculates hold time over the point of arrival. JetPlan calculates hold
time over the alternate that you specify an alternate,
Your organization’s aircraft database includes parameters to control the:
• holding fuel flow
• hold altitude,
• minimum amount of hold fuel, and
• whether JetPlan uses landing weight or max zero fuel weight to calculate hold fuel.
Uplift requirement The JAR-OPS uplift philosophy tells the JetPlan engine to determine which alternate
(JAR-OPS) requires the most fuel and then applies this fuel amount to the fuel totals. If you identify
only a primary alternate, no uplift philosophy is necessary.
To use the Airport Filter to search for an alternate airport after you have
specified an arrival (destination) airport
1. In the Flight Plan wizard, click the Alternates tab.
2. In Arrival Alternates by the box for Primary, click the ellipses ( ) button.
The Airport Filter dialog displays.
5. Click Find.
Search automatically uses the criteria that you set to display a list of alternates.
6. After you select the alternate from the list, click OK to enter that alternate in the
Alternate box.
Default Calculation
By default, the JetPlan engine calculates a direct route to the alternate. If an Alternate database
route is available in your organization’s alternate database, you can make it the default setting.
If you click the Miles from POA button and enter a value, the distance that you enter
overrides the distance between the POA and Alternate in the database.
Example The actual distance from KDEN to KCOS might be 60 nautical miles, but you
specify 100 nautical miles of distance. JetPlanner adds fuel for 100 nautical miles
to the alternate fuel block rather than the actual 60 nautical miles.
To modify the route calculation by using a specified distance (Miles from POA)
1. In the Primary or Secondary alternate field, enter a four-character ICAO or three-
character IATA code for the alternate airport if one is not already present.
2. In the Route Type area, click the Miles from POA option button and then enter
the distance in nautical miles.
3. Click Save or Save As.
To modify the route calculation by using the customer Route alternative option
1. In the Primary or Secondary alternate field, enter a four-character ICAO or three-
character IATA code for the alternate airport if one is not already present.
2. In the Route Type area on the Primary or Secondary alternate in the Alternate tab,
click Route.
3. In the list to the right, select the route name from your organization’s database.
NOTE If a route exists in the database but does not appear in the list, you might
need to update the Alternates database on the machine (Tools >
Account Databases > Update).
NOTE Enter values in each box. If you do not, the JetPlan engine returns an error.
You can use Flight Levels with any Route Type choice. If you use Flight Levels, their values
override any flight level in an Alternate database route.
4. If the criteria match at least one airport, a list appears. Select the desired airport,
and then click OK. [Figure 9.10]
5. After you select the desired alternate from the list, click OK to enter that alternate
on the Alternates tab.
2. Click the Airport tab and then set the search criteria.
3. Click Find.
Search uses the criteria that you set to find alternates. [Figure 9.12]
4. If the criteria match at least one airport, a list appears. Select the desired airport
and then click OK.
5. After you select the desired alternate from the list, click OK to enter that alternate
on the Alternates tab.
After you complete the flight plan inputs and click Submit, the JetPlan engine generates the
flight plan and displays it in the Chart View and View Plans tabs. [Figure 10.1]
In the Flight Plan Manager, choose a flight plan by selecting its check box. [Figure 10.2]
To reformat a flight plan into one of the selectable formats (and, optionally,
print in that format)
1. Select the flight plan from one of the following:
• Dispatch View
• Flight Plan Manager
• Personal Folder
2. Click the View Plans tab. [Figure 10.3]
3. To select a format, click its button at the bottom of the View Plans tab.
4. (Optional) To print, right-click the plan and select Print.
NOTE The Text button displays the flight plan either in your organization’s default
flight plan format or in the format that you select in the Output Format section
on the Standard tab.
NOTE If the original flight plan used an optimizer for routing, the JetPlan engine
reoptimizes the routing in the new request when you submit it.
To create a flight plan request with the original inputs from a flight plan
1. Select the flight plan from one of the following:
• Dispatch View
• Flight Plan Manager
• Personal Folder
2. Right-click the flight plan, and then click Create Request from.
The Flight Plan wizard opens with inputs that you used to create the flight plan.
3. Edit the request and click Save or Submit.
Editing a Request
2. In the Data Directory Settings list, select Saved PDF files location.
3. Change the directory to what you want. To browse for a folder, click the ellipses
( ) button.
4. Click OK to save the changes.
Examples By using the Trip Kit feature through Personal Folders, you can print strip charts
(enroute plates) for a flight plan.
You can save strip charts of a flight plan as a .pdf file with the same procedure.
NOTE The Trip Kit feature works only if you have an up-to-date Jeppesen charting
product installed on the same machine after JetPlanner was installed.
JetPlanner prints strip charts sequentially. A range of chart scales is available. You can use any
scale with any chart theme.
To print strip charts for a flight plan that is in Flight Plan Manager
1. Right-click in Personal Folders and select New Folder.
2. Name the new folder.
3. Drag and drop the flight plan from Flight Plan Manager to the new folder in
Personal Folders.
4. In the new folder, click + on the flight plan to display its terminal charts.
[Figure 10.5]
5. Right-click on the flight plan (not airport detail), then point to Print, and then
click Trip Kit.
A Printing_TK dialog appears with the flight plan identifier after the TK_.
[Figure 10.6]
6. On the Printing_TK dialog, select the Strip Charts (Enroute Plates) option box.
7. Select other options on the dialog as you want, such as chart scale and profile
sections.
8. Click Print Preview to verify the charts look the way you want. Change options
and settings as necessary.
9. When all options on the dialog are as you require, click Print or Save as PDF.
As an alternative to its regular electronic flight plan filing, some versions of JetPlanner can be
configured to file a flight plan through the Aeronautical Fixed Telecommunications Network
(AFTN).
AFTN filing enables you to change any part of a flight plan before you file it, but does not
check for your errors and does not enable you to track the plan through JetPlanner. Because
JetPlanner does not track the plan, canceling or delaying the plan requires a separate AFTN
message.
• If you do not know how JetPlanner is configured, begin with the procedure for
regular filing on page 132.
• If JetPlanner is configured for regular filing, continue with the procedure “To file
the flight plan electronically with ATC (without AFTN)” on page 132.
• If JetPlanner is configured for AFTN filing, continue with the procedure “To file
the flight plan electronically with ATC using AFTN” on page 134.
3. Complete the required boxes (*) in the File Flight Plan dialog.
4. Complete one of the following options to set time to file the plan:
• File immediately
• File [_] hours [_] minutes before ETD (lead time)
• File at [_] on [_] to submit at a specific time on a specific date
5. Click Submit.
ATC filing status appears in the Dispatch View (View > Dispatch View Bar).
3. In the Priority list, select the appropriate priority for the flight plan filing.
NOTE JetPlanner does not check for errors that you might type. When you click
Send, JetPlanner sends the flight plan to the recipients.
5. Click Send.
ATC filing status appears in the Dispatch View (View > Dispatch View Bar).
Status Description
Cancelled Flight plan filed with ATC and then canceled. This status appears
when you cancel a plan, even if you did not send the plan to Crew
Brief or delay the plan.
Computed Flight plan calculated but not yet filed with ATC.
Delayed Flight plan filed, then a request to delay sent to ATC. If a plan has
been both delayed and sent to Crew Brief, it appears as
“Delayed/CB”. For ICAO flight plans only.
Filed Flight plan computed and filed with ATC.
Released Primary plan “Released” by the Release choice from the right-click
menu.
3. (Option) Set a new departure time. In the next step, you can select a different date
with the same time.
4. (Option) To select a new departure date, click the ellipses button ( ) to open a
Select Date dialog.
5. Click Submit.
Status shows Delaying while processing, then Delayed when processing is
complete.
3. Click Submit.
Status shows Delaying while processing, then Delayed when processing is
complete.
To validate a flight plan prior to filing for the Eurocontrol area with CFMU
1. From the View menu, click Dispatch View Bar.
JetPlanner displays the Dispatch View dialog box.
2. Right-click a flight plan and click Validate Filing.
JetPlanner displays the CFMU Validation Result.
The CMFU Validation Results window (Figure 10.12) shows any validation errors. Use this
window to have JetPlanner suggest routes similar to the one you created that meet CFMU
validation requirements.
To uplink a flight plan, your organization’s database must contain the Type code for a flight
management system (FMS).
This section explains how to uplink a flight plan with ARINC Direct Uplink and Satcom
Direct, and how to check ARINC acknowledgments.
Acknowledgement Comments
Flight Plan Delivered Flight plan uplinked to the aircraft and received by the flight management
system (FMS).
Flight Plan Stored ARINC Direct’s host system received and stored the Uplink request. The
plan is ready for a downlink request from the aircraft.
Unable to Deliver Flight Plan An aircraft requested the stored flight plan, but the plan failed to load
(ARINC Direct received a NAK message from the FMS). A possible cause
is that the FMS was loading another flight plan.
To submit a crew briefing request and activate the flight plan in EasyBrief
1. From the View menu, click Dispatch View Bar.
JetPlanner displays the Dispatch View dialog box.
2. Right-click a plan and select Crew Brief > Notify.
3. To add a message for the crew, select Send message. Type the message, and then
click Submit.
4. When done, click Close ( ) to dismiss the Summary.
You can create messaging templates to simplify sending future messages of a similar type.
The Cruise section on the Speed and Level tab in the Flight Plan wizard enables you to use
multiple cruise modes in a flight plan. [Figure 11.2]
Figure 11.2 Cruise mode section of the Speed and Level tab
The Initial Primary list determines the first cruise mode of the flight. The Initial Primary cruise
mode appears as the first cruise mode in the Multiple Cruise column of lists on the
Speed and Level tab.
To the right of the Multiple Cruise column is a Checkpoint column. The JetPlan engine plans
the cruise mode from Multiple Cruise until the flight reaches the specified checkpoint. All
must-fly waypoints that you type into the route string appear in each Checkpoint list.
To use fewer cruise mode changes than the total allowed, select the POA as the last “Until”
checkpoint.
Figure 11.3 Altitude Profile in the Speed & Level tab of the Flight Plan wizard
Each list in the Altitude Profile includes sets of selections, one of each set ending in “…until
TOD” that serve the without-checkpoints alternative. You can use as many as 10 of these
Altitude Profile options per flight plan.
Example You can instruct JetPlanner to calculate a flight plan in which the aircraft must be
at a specific altitude by a specific checkpoint somewhere along the route of flight.
Because the altitude specification was to a checkpoint rather than for the entire
route, JetPlanner prompts you for a profile for the remainder of the flight.
Table 11.1 helps you select the correct profile function for each situation.
Use the most efficient level in a segment Optimize Until Checkpoint 156
Use the most efficient level for the remainder of the flight Optimize until TOD 157
Fly one level for the remainder of the flight At Flight Level Until TOD 159
Achieve (reach) a level before a point and fly at that level for a Attain Flight Level by Checkpoint 160
segment Until Checkpoint
Achieve (reach) a level before a point and fly at that level for Attain Flight Level By Checkpoint 161
the remainder of the flight Until TOD
Constrain optimization of level for the remainder of the flight Between Flight Levels Until TOD 163
Attain
At
Between
To direct the JetPlan engine to determine the optimum altitude from TOC to
TOD
• In the Altitude Profile section on the Speed & Level tab, click
Optimize until TOD from the list. [Figure 11.7]
At Flight Level
The At functions enable you to specify a single flight level for the designated segment of the
flight plan. JetPlanner starts the change of altitude at checkpoint. Due to the fixed-altitude
constraint, no optimization occurs.
To ensure that the aircraft maintains a particular flight level until it reaches a
checkpoint
1. On the Speed & Level tab in the Altitude Profile section, click At from the list.
[Figure 11.8]
2. In the next box type the flight level (###) to use to the checkpoint.
3. From the Until list, select the checkpoint at which that altitude is no longer
required.
To ensure that the aircraft attains a particular flight level before specific
checkpoint and maintains that flight level until another checkpoint:
1. On the Speed & Level tab in the Altitude Profile section, click Attain from the
list. [Figure 11.10]
To ensure that the aircraft attains a particular flight level before a specific
checkpoint and maintains that flight level until TOD
1. On the Speed & Level tab in the Altitude Profile section, click Attain until TOD
from the list. [Figure 11.11]
2. In the next box, type the flight level (###) that the aircraft must attain.
3. From the By list, select the checkpoint by which the aircraft attains that fixed
altitude.
NOTE Specify both a minimum and a maximum flight level. The JetPlan engine
returns an error from a flight plan request that contains one flight level but not
the other.
2. In the next two boxes, type the minimum then maximum flight levels for the range
(###) (###).
3. From the Until list, select the checkpoint identifier.
2. In the next two boxes, type the minimum then maximum flight levels for the range
(###) (###) between TOC and TOD.
Adjusting Payload
The fuel and payload features in the Flight Plan wizard enable you to create different fuel and
payload scenarios that you can apply to the flight plan. You access payload and fuel
information from the Payload tab on the Flight Plan wizard.
The payload scenarios in JetPlanner enable you to use different input methods to calculate fuel
scenarios that fit different needs. The JetPlan engine uses the parameters that you set to adjust
the fuel and payload of the flight plan.
Maximizing Payload
To maximize payload and control departure or arrival fuel, use the option Maximize ZFW,
known fuel.
The option “Maximize ZFW, known fuel” maximizes aircraft zero-fuel weight by adding the
maximum payload defined in the weights section of the aircraft database.
Jeppesen recommends that you use the Auto Weight feature. The Auto Weight feature limits
payload to ensure that the flight plan exceeds no weight limit.
Figure 12.1 Maximize ZFW with known fuel and Auto Weight
Adjusting Fuel
Use the fuel reserves features in the Standard tab on the Flight Plan wizard to plan for fuel
reserves with the reserve policy that you select. The JetPlan engine uses the parameters that
you set to adjust the calculations.
To maximize the amount of fuel that the aircraft departs with, use the option
Known Payload, tanker fuel.
Maximizing Fuel
To specify the payload and weight upon departure or arrival, use the option
Known Payload, tanker fuel. Because you specify payload, the only way to increase aircraft
weight is to add fuel.
Jeppesen recommends using the Auto Weight function. The Auto Weight function limits
payload to ensure that the flight plan does not exceed any weight limit.
Index
A 109
Alternate ATC
Changes between TOC and TOD 154 flight plan format similar 40
applying 153 B
drop-down list 153 Base Reflectivity
fixed 158 Infrared/radar composite 98
in Speed & Level tab of Flight Plan NEXRAD 98
wizard 152
Single-site radar 99
Route
Winter radar mosaic 99
database manipulation 104
SRS C
combining low and high in single call sign 30
flight plan 49
CCAA 76
Wind data floor for online 10
CFMU
Altitude Profile
Acronym defined 139
Applying 153
Validation
Speed & level tab of flight plan wizard
failure 140
152
requirements 139
ARINC
results example 139
Acknowledgment
S Chart View 87
User-Defined Waypoint 87
V
Visible Satellite Images 98
W
Waypoint
Dropping to Chart View 85
Must-fly 66
User-Defined 87
User-defined
actions to manage 83