0% found this document useful (0 votes)

6 views168 pages

ETOPS UsersGuide

The ETOPS II Startup Guide (Version 1.4) provides comprehensive instructions for utilizing the ETOPS II feature in JetPlan, including updates on error messages, Time-Limited Systems, and new APU options. It covers prerequisites, database setups, flight plan requests, and troubleshooting. The document also includes detailed chapters on Multi-Segment ETOPS and modifications for European business aviation operators.

Uploaded by

lensmir

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

6 views168 pages

ETOPS UsersGuide

Uploaded by

lensmir

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

ETOPS II Startup Guide

VERSION 1.4

Copyright © 2018 Jeppesen. All rights reserved.

DATD_Jepp_JPE_ETOPSIIStartupGuide
Document Revision History
Version Release Date Changes Include
1.4 April 11, 2018 • General revision of format and more details added to existing
topics.
• Updates to error and alert messages.
• Updated content on Time-Limited Systems.
• Addition of the Multi-Segment ETOPS feature.
• Addition of the APU Situation Flag Code (ST) option, which lets
you specify an APU Situation Code in your flight plan request. The
Situation Code you specify overrides the value of the Situation
Code parameter in the Customer Aircraft database.
• Addition of the APU Flag (AP) option, which lets you specify an
APU Flag code in your flight plan request. The APU Flag code you
specify overrides the value of the Auxiliary Power Unit Flag
parameter in the Customer Aircraft database.
• Revised information on the Point of Departure (POD) and Point of
Arrival (POA). JetPlan no longer automatically considers the POD
and POA as adequate ETOPS airports. The same rules that apply to
designating any airport as an adequate ETOPS airport now apply to
the POD and the POA.
Contents

Figures vii

Tables ix

Introduction 1
About the ETOPS II Startup Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Audience and Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1: Overview of ETOPS II 5

About ETOPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Current ETOPS Regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
About the ETOPS II Feature in JetPlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2: Getting Started 11

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Meeting Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
About User Preferences and ETOPS II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
ETOPS Carry-over Flag Preference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
ETOPCO in the Flight Plan Format or Flight Plan Request . . . . . . . . . . . . . . . . . . . . 15
Terminal Aerodrome Forecast (TAF) Check Preference . . . . . . . . . . . . . . . . . . . . . . . . 16
Setting Up Customer Databases for ETOPS II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
About the Customer Database Information in this Guide . . . . . . . . . . . . . . . . . . . . 17
Finding More Information on Customer Database Parameters . . . . . . . . . . . . . . . . . . 18
Setting Up the Customer Aircraft Database for ETOPS II . . . . . . . . . . . . . . . . . . . 19
Contents

Setting the Miscellaneous Section Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Setting the ETP Section Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Setting the ETOPS Section Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Setting Up the Aircraft Fleet Database for ETOPS II . . . . . . . . . . . . . . . . . . . . . . . 36
Setting up the City Pair Fleet Database for ETOPS II . . . . . . . . . . . . . . . . . . . . . . . 47
Setting Up the Customer Airport Database for ETOPS II . . . . . . . . . . . . . . . . . . . . 49
Setting Up the Airport Fleet Database for ETOPS II . . . . . . . . . . . . . . . . . . . . . . . . 51
Overriding Airport Fleet Database Records on a Flight Plan Request . . . . . . . . . . . . . 51
Setting Up the Flight Brief Database for ETOPS II . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 3: Running ETOPS II Flight Plans 63

Requesting an ETOPS Flight Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
About the ETOPS II Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
ETOPS II Flight Plan Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
ETOPS II Alternates Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
ETOPS II Flight Plan Input Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Chapter 4: Multi-Segment ETOPS 77

About Multi-Segment ETOPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
About the Multi-Segment ETOPS Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
About the Multi-Segment ETOPS Flight Plan Output . . . . . . . . . . . . . . . . . . . . . . . 85

Chapter 5: ETOPS II for EU-OPS Business Aviation Operators 87

About Modifying ETOPS II for European Business Aviation Rules . . . . . . . . . . . . 89
Modifying the Icing Penalty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Modifying the Wind Bias and Conservatism Calculation . . . . . . . . . . . . . . . . . . . . . 92
Adding Missed Approach Fuel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 6: APU Fuel Burn 95

About APU Situation Codes and APU Fuel Burn . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Chapter 7: Understanding ETOPS II Flight Plan Output 101

About the ETOPS II Flight Plan Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Customer Database Settings and Flight Plan Options for the Sample Output . . . . 104
ETOPS II Sample Flight Plan Output (Excerpts) . . . . . . . . . . . . . . . . . . . . . . . . . . 107
ETOPS Approval Time Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Fuel Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Suitable Airports Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Critical Fuel Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Equal Time Point Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Time Limited Systems Compliance Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
ETOPS Entry, Exit, and ETPs in the Nav Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

ETOPS II Startup Guide v. 1.4 April 11, 2018

Extended Critical Fuel Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Time Limited System Information for the ETP in the Extended Detail . . . . . . . . . . . . 114
ETP Segment Computation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Multi-ETOPS Segments Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Suitable Times Detailed Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Critical Point Detailed Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
TAF Weather Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Time Limited Systems Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Multi-ETOPS Segments Output in Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Chapter 8: Troubleshooting 125

Troubleshooting Error Messages and Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Troubleshooting Common Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Appendix A: Full Sample ETOPS II Flight Plan Output 137

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
ETOPS II Sample Flight Plan Request Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
ETOPS II Sample Flight Plan Output (Full) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Glossary 153

April 11, 2018 ETOPS II Startup Guide v. 1.4

Getting Started 11
Figure 2.1. ETOPS II Fuel Parameters in the Customer Aircraft Database . . . . . . . . 19
Figure 2.2. ETOPS II Miscellaneous Parameters in the Customer Aircraft Database 21
Figure 2.3. ETOPS II ETP Parameters in the Customer Aircraft Database . . . . . . . . 23
Figure 2.4. ETOPS II Parameters in the Customer Aircraft Database . . . . . . . . . . . . 26
Figure 2.5. ETOPS II Parameters in the Customer Aircraft Fleet Database . . . . . . . 37
Figure 2.6. ETOPS II Parameters in the City Pair Fleet Database . . . . . . . . . . . . . . . 47
Figure 2.7. ETOPS II Parameters in the Customer Airport Database . . . . . . . . . . . . 49
Figure 2.8. ETOPS II Parameters in the Customer Airport Fleet Database . . . . . . . . 52
Figure 2.9. ETOPS II Parameters in the Flight Brief Database . . . . . . . . . . . . . . . . . 56

Multi-Segment ETOPS 77
Figure 4.1. Sample route from FMMI to LFPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 4.2. Single-Segment ETOPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 4.3. Determining ETOPS Segments Using Flight Brief Database Settings . . 82
Figure 4.4. Associating EEPs and EXPs with Alternates . . . . . . . . . . . . . . . . . . . . . . 83
Figure 4.5. Determining Whether to Report an ETP . . . . . . . . . . . . . . . . . . . . . . . . . 84

Understanding ETOPS II Flight Plan Output 101

Figure 7.1. Customer Aircraft Database – Sample ETOPS Settings . . . . . . . . . . . . 104
Figure 7.2. Customer Aircraft Fleet Database – Sample SCM Dataset Settings . . . 105
Figure 7.3. Flight Brief Database - Sample ETOPS Settings . . . . . . . . . . . . . . . . . . 106
Figure 7.4. Sample Flight Plan Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Figure 7.5. ETOPS Approval Time Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Figures

Figure 7.6. Fuel Block ETOPS Additional Fuel Entry . . . . . . . . . . . . . . . . . . . . . . . 108

Figure 7.7. Suitable Airports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Figure 7.8. Critical Fuel Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 7.9. Entry, Exit, and Equal Time Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 7.10. Time Limited System Compliance Summary . . . . . . . . . . . . . . . . . . . . . 111
Figure 7.11. Entry, Exit, and Equal Time Points in Nav Log . . . . . . . . . . . . . . . . . . . 112
Figure 7.12. Extended Critical Fuel Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Figure 7.13. Time Limited System Detail for the ETP . . . . . . . . . . . . . . . . . . . . . . . . 114
Figure 7.14. Diagnostic Information – ETOPS Segment . . . . . . . . . . . . . . . . . . . . . . 115
Figure 7.15. Diagnostic Information – Multi-ETOPS Segments . . . . . . . . . . . . . . . . 116
Figure 7.16. Suitable Times Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Figure 7.17. Critical Points Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Figure 7.18. TAF Weather Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 7.19. Diagnostic Information -- Time Limited Systems . . . . . . . . . . . . . . . . . 121
Figure 7.20. Detailed Multi-ETOPS Segments Diagnostic Output . . . . . . . . . . . . . . 122

ETOPS II Startup Guide v. 1.4 April 11, 2018

Getting Started 11
Table 2-1: ETOPS Carry-over Flag Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 2-2: TAF Check Preference Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Table 2-3: Customer Aircraft Database – ETOPS II Fuels Parameters . . . . . . . . . . . 20
Table 2-4: Customer Aircraft Database – ETOPS II Miscellaneous Parameters . . . 22
Table 2-5: Customer Aircraft Database – ETOPS II ETP Parameters . . . . . . . . . . . 24
Table 2-6: Customer Aircraft Database – ETOPS II Parameters . . . . . . . . . . . . . . . 26
Table 2-7: Customer Aircraft Fleet Database – ETOPS II Parameters . . . . . . . . . . . 38
Table 2-8: Customer City Pair Fleet Database – ETOPS II Parameters . . . . . . . . . . 48
Table 2-9: Customer Airport Database – ETOPS II Parameters . . . . . . . . . . . . . . . . 50
Table 2-10: Customer Airport Fleet Database – ETOPS II Parameters . . . . . . . . . . . 53
Table 2-11: Customer Flight Brief Database – ETOPS II Parameters . . . . . . . . . . . . 57

Running ETOPS II Flight Plans 63

Table 3-1: Basic Flight Planner ETOPS II Flight Plan (01) Options . . . . . . . . . . . . 67
Table 3-2: Basic Flight Planner ETOPS II Alternates (ETOPS ALTS) Options . . . 68

APU Fuel Burn 95

Table 6-1: APU Situation Code Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Troubleshooting 125
Table 8-1: Error Messages and Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Table 8-2: Common Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Introduction

This chapter includes the following sections:

• About the ETOPS II Startup Guide

• Scope
• Assumptions
Introduction
About the ETOPS II Startup Guide

About the ETOPS II Startup Guide

The ETOPS II Startup Guide covers setting up the Extended Operations (ETOPS II) feature
for use in JetPlan or a flight planning product that interfaces with JetPlan, such as [Link]
or JetPlanner. The ETOPS II feature allows operators to perform flight planning tasks
associated with ETOPS operations while complying with Part 121 and Part 135 of the Federal
Aviation Administration (FAA) ETOPS regulations.

Audience and Purpose

The ETOPS II Startup Guide is intended for Jeppesen Implementation Specialists, support
personnel, account managers, and customers who want to understand how to configure and
use the ETOPS II feature.

Scope
The ETOPS II Startup Guide covers configuring JetPlan to support ETOPS II flight planning
and using [Link] to run ETOPS II flight plans. The ETOPS II flight plan options in
JetPlan support the 2007 FAA update to ETOPS Federal Aviation Regulations (FARs). The
2007 update revised and clarified the operational requirements for extended operations and
encoded the requirements into [Link] updated JetPlan to support the ETOPS
planning requirements and fuel calculations resulting from the 2007 regulatory changes. The
term ETOPS II differentiates the updated JetPlan ETOPS functionality from the pre-2007,
legacy ETOPS functionality. For a fuller discussion of the ETOPS II feature in JetPlan, see
Chapter 1, “Overview of ETOPS II.”

NOTE While customers can continue to use legacy, pre-2007 ETOPS in JetPlan,
legacy ETOPS is not covered in the ETOPS II Startup Guide. For documentation on
legacy ETOPS, see the User Manuals page on [Link].

The ETOPS II Startup Guide covers the following topics:

• ETOPS II overview
• ETOPS II functionality in JetPlan
• ETOPS II customer preference setup
• ETOPS II customer database setup
• ETOPS II flight planning in JetPlan

April 11, 2018 ETOPS II Startup Guide v. 1.4

• ETOPS II flight plan output

• ETOPS II troubleshooting
• ETOPS II terminology

Assumptions
This guide assumes familiarity with the following:

• General flight-planning principles, ETOPS fundamentals, and current

ETOPS regulations
• JetPlan or a flight planning product that interfaces with JetPlan, such as
JetPlanner
• Administration of JetPlan customer databases

NOTE For information on prerequisites, see Chapter 2, “Getting Started.”

ETOPS II Startup Guide v. 1.4 April 11, 2018

Overview of ETOPS II

This chapter includes the following sections:

• About ETOPS
• About the ETOPS II Feature in JetPlan
Overview of ETOPS II
About ETOPS

About ETOPS
NOTE The ETOPS II Startup Guide assumes familiarity with ETOPS as defined by
the Federal Aviation Administration (FAA) in AC 120-42B – Extended Operations
(ETOPS and Polar Operations). The following section provides a brief, high-level
summary of ETOPS only.

ETOPS pertains to flight operations in areas that are a defined distance from the closest
adequate diversion airport. The FAA defines an ETOPS area as being more than 60 minutes
from an adequate airport for two-engine airplanes and more than 180 minutes from an
adequate airport for three- or four-engine airplanes. The distance from the adequate airport is
based on a one-engine inoperative cruise speed in standard conditions in still air.

Airlines that operate aircraft in ETOPS areas must adhere to stringent procedures and
regulations. ETOPS regulations have evolved as aircraft capabilities have advanced. Since the
1950s, the FAA and the International Civil Aviation Organization (ICAO) have had rules
prohibiting two-engine airplanes from flying farther than 60 minutes from an acceptable
emergency airport (Federal Aviation Regulation 121.161). In 1985, the FAA published
guidelines that enabled operators to obtain approval to fly beyond the previous 60-minute
limitation, up to a maximum of 180 minutes deviation time from an adequate airport
(Advisory Circular 120-42). These guidelines were known in the aviation industry as Extended
Twin-Engine Operational Performance Standards (ETOPS).

In 2007, the FAA issued updated Federal Aviation Regulations (FARs) relating to the
operation of all aircraft on flights that have a potential for extended time diversions
(InFO 07004). As a result, the term ETOPS was redefined as Extended Operations. The
updated ETOPS FARs made significant changes to the planning and fuel calculations for
ETOPS flights. The updated FARs stipulate that operators planning with three- and four-
engine airplanes must perform ETOPS flight planning and operations when the route includes
a point farther than 180 minutes from an adequate airport. Part 135 operators are also required
to perform ETOPS flight planning and operations when the route includes a point farther than
180 minutes from an adequate airport.

Today, the majority of commercial airline flights over the North Atlantic operate under
ETOPS guidelines. In the Pacific, air carriers are often approved to fly two-engine airplanes as
far as 207 minutes from an adequate airport.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Current ETOPS Regulations

In 2008, the FAA issued “AC 120-42B – Extended Operations (ETOPS and Polar
Operations),” containing requirements for ETOPS that were later encoded into FAA
regulations such as FAR 121.161. In Europe, regulations governing ETOPS are documented in
“AMC-20 Amendment 7 - Annex II AMC 20-6 rev. 2,” issued by the European Aviation
Safety Agency (EASA).

About the ETOPS II Feature in JetPlan

NOTE In Jeppesen’s flight planning products, the term ETOPS II always refers to
Extended Operations.

To perform ETOPS operations, an operator must demonstrate that it can operate the aircraft in
compliance with ETOPS regulations. The operator must also implement special flight
planning and dispatch procedures that ensure safe operations in ETOPS areas. The JetPlan
ETOPS II feature enables an airline dispatcher to perform ETOPS flight planning tasks while
complying with ETOPS regulations. The following paragraphs describe some of the ETOPS II
capabilities that support compliance.

NOTE Output of ETOPS data on the flight plan is format-dependent. For more
information, see Chapter 7, “Understanding ETOPS II Flight Plan Output.”

Critical Point The flight plan must report the points along the route where the crew
Determination can expect to change to a different diversion airport in case of an
emergency. A critical point may be one of the following:

• Equal Time Points (ETPs) – An ETP is a point on the route that

is located at equal flying time from each of an associated pair of
backward and forward ETOPS alternates.
• ETOPS Entry Points (EEPs) – An EEP is the first point on the
route of an ETOPS flight, determined using a one-engine
inoperative cruise speed under standard conditions in still air,
that is — (1) More than 60 minutes from an adequate airport for
airplanes with two engines, or (2) More than 180 minutes from
an adequate airport for airplanes with more than two engines.
This is the point at which the aircraft enters an ETOPS area of
operation.

ETOPS II Startup Guide v. 1.4 April 11, 2018

• ETOPS Exit Points (EXPs) – An EXP is the point on the route

where the aircraft exits an ETOPS area of operation, meaning it
is no longer more than 60 minutes (or 180 minutes for airplanes
with more than two engines) from an adequate airport.

The Equal Time Point Summary on the flight plan includes data about
the critical point for the ETOPS segment. The EEPs, EXPs, and ETPs
are also reported in the navigation log on the flight plan.

Suitability Times The dispatcher must know and the flight plan must show the earliest
(Early/Late Time) and the latest time that the aircraft is expected to arrive at an ETOPS
Computation alternate airport. JetPlan calculates these early and late times based on
the location of the critical points, and the slowest and fastest speeds
that the aircraft is expected to fly a diversion leg to the alternate
airport. The suitable early and late arrival times for each alternate are
listed in the Suitable Times Detail summary on the flight plan.
Adjustments to suitability times can be set in the Flight Brief database
to comply with EU ETOPS regulations or those of other authorities.

Critical Fuel The point of ETOPS computations is to ensure that the aircraft has
Requirement sufficient fuel to fly the worst-case diversion leg in the worst-case
Calculation scenario. JetPlan can account for three standard ETOPS scenarios for
each diversion leg. All three scenarios use the same ETPs. ETPs are
calculated using forecast winds and single ETP True Airspeed (TAS).
The three scenarios analyzed are:

• Engine loss and aircraft depressurization, referred to in JetPlan

as Depressurized Engine-Out
• Aircraft cabin depressurization, referred to in JetPlan as
Depressurized All-Engine
• Engine loss, referred to in JetPlan as Pressurized Engine-Out

The fuel to meet the worst of the scenarios must be on board the
aircraft at the critical point. This information is reported on the flight
plan in the Critical Fuel Summary. In addition, when the extended
ETOPS option is requested (ETOPXN), the flight plan includes the
Extended Critical Fuel Detail output, which includes the Pressurized
Engine-Out scenario information.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Time-Limited JetPlan provides Time-Limited Systems (TLS) regulatory

System (TLS) information for ETOPS diversions that exceed 180 minutes. When
Summary the following conditions are true, the flight plan includes the ETOPS
TLS Compliance Summary, TLS Compliance Summaries for each
ETP and each scenario, and TLS diagnostic information:

• The flight plan format supports display of the TLS output.

• The Calculate TLS (TLSF) parameter in the Aircraft Fleet
Database is set to Yes.
• The Cargo Fire Suppression Time Limit (FS) parameter in the
Customer Aircraft Database is greater than 0.

Multi-Segment JetPlan enables you to configure the Flight Brief database to support
ETOPS multi-segment ETOPS flight planning. In multi-segment ETOPS
Computation flight plan calculations, JetPlan automatically determines all the
ETOPS segments that exist for user-specified ETOPS airports based
on settings in the Flight Brief database. When calculating multi-
segment flight plans, JetPlan does the following:

• Treats consecutive ETOPS segments that are beyond a

configurable distance from one another as two separate ETOPS
segments, as opposed to combining them
• Determines which ETPs the system can omit based on a
configurable distance between the abeam points of the forward
and backward alternates
• Excludes any alternate that has no critical points associated with
it from the set of ETOPS alternates and from critical fuel and
suitability calculations.

For more information on multi-segment flight planning, see “Setting

Up the Flight Brief Database for ETOPS II” on page 54 and
Chapter 4, “Multi-Segment ETOPS.”

ETOPS II Startup Guide v. 1.4 April 11, 2018

Getting Started

This chapter includes the following sections:

• Overview
• Meeting Prerequisites
• Setting Up Customer Databases for ETOPS II
Getting Started
Overview

Overview
This chapter describes prerequisites and provides information on the configuration of user
preferences and customer databases used in ETOPS II.

Meeting Prerequisites
You must meet the following prerequisites to set up and run ETOPS II flight plans using
JetPlan or a software product that interfaces with JetPlan, such as JetPlanner:

• Your aircraft records must include the necessary performance data

The Generic Aircraft database records on which your Customer Aircraft
records are based must include the appropriate performance data to support
the ETOPS scenarios. If the required performance data is not available for
the aircraft, contact Jeppesen Customer Support.
• You must have access to your customer databases
You or a designated authorized user must have access to [Link] to
make changes to the following customer databases:
– Customer Aircraft
– Aircraft Fleet
– Airport
– Airport Fleet
– Flight Brief

IMPORTANT Inaccurate or incomplete configuration of these databases puts the

accuracy of your ETOPS flight plan computations at risk. Jeppesen recommends
contacting your Jeppesen Implementation Specialist before using ETOPS II to
confirm your databases are set up correctly. After implementation of ETOPS II,
contact Jeppesen Customer Support if you have questions about your database
settings.

• Your flight plan format must support ETOPS II output

You can use your own format if it has been modified to support ETOPS II,
or you can use an existing format recommended by Jeppesen.
• The ETOPS Carry-over Flag customer preference must be set or your format
must include the ETOPCO keyword. See “About User Preferences and
ETOPS II” on page 14.

April 11, 2018 ETOPS II Startup Guide v. 1.4

About User Preferences and ETOPS II

NOTE Only Jeppesen Customer Support personnel can change customer

preference settings. If you have questions about your customer preference settings,
contact Jeppesen Customer Support.

Customer preferences define user-specific default functionality in JetPlan. The ETOPS Carry-
over Flag and the TAF Check customer preferences apply to ETOPS II. The following
paragraphs describe these preferences.

NOTE All other ETOPS-related customer preference database settings apply only
to legacy ETOPS and not to ETOPS II.

ETOPS Carry-over Flag Preference

The purpose of JetPlan ETOPS calculations is to ensure that the aircraft has enough fuel on
board to perform [Link] ETOPS Carry-over Flag customer preference determines the
default behavior in case the aircraft does not have enough fuel on board to perform ETOPS, a
condition called ETOPS Critical Fuel Shortfall (CFS). The preference settings control the
following:

• Whether or not to perform mitigation by adding fuel to cover the CFS.

• Where to account for the ETOPS added fuel value in the flight plan output.

NOTE Unless you have the ETOPS Carry-over (ETOPCO) format keyword set in
your flight plan format or can set the ETOPS Carry-over value in your flight plan
request, the ETOPS Carry-Over Flag preference must be set. (See “ETOPCO in the
Flight Plan Format or Flight Plan Request” on page 15.)

The ETOPS Carry-over Flag customer preference allows operators to specify whether ETOPS
critical fuel calculations are to assume that any extra planned fuel is present in the fuel on
board at the critical point. This feature is a response to the fact that some operator policies
might indicate that fuel categorized as EXTRA is not required in the fuel load on takeoff.

ETOPS II Startup Guide v. 1.4 April 11, 2018

The following table describes the settings for the ETOPS Carry-over Flag customer
preference used with ETOPS II. The recommended setting for the ETOPS Carry-over Flag
preference is 6. If you have additional questions about this preference, contact your Jeppesen
Implementation Specialist or Jeppesen Customer Support.

Table 2-1 ETOPS Carry-over Flag Settings

Setting Definition
3 CFS mitigation is performed. JetPlan assumes that all EXTRA fuel is loaded on the
aircraft. After being applied to other additional fuel needs, such as reserve fuel or hold fuel,
remaining EXTRA fuel is applied to any CFS found. If the remaining EXTRA fuel is
sufficient to cover the CFS, no fuel is added to ETOPS ADD in the flight plan output. If
remaining EXTRA fuel is insufficient to cover the ETOPS CFS, additional fuel required to
cover the CFS is added to ETOPS ADD. EXTRA and ETOPS ADD are output on separate
lines.

6 CFS mitigation is performed. JetPlan determines how much of the EXTRA fuel is required
(Recommended to cover any CFS found. JetPlan then allocates enough fuel from EXTRA to ETOPS ADD
setting) to cover the CFS. The balance left in EXTRA is the amount that is not required to cover the
ETOPS CFS and is output as EXTRA fuel. This approach ensures that the ETOPS critical
fuel requirement is still met in case the fuelers decide to leave EXTRA fuel off the aircraft.
EXTRA and ETOPS ADD amounts are output on separate lines.

ETOPCO in the Flight Plan Format or Flight Plan Request

The flight plan format can be modified with the ETOPCO flag, which has the same settings as
the ETOPS Carry-over Flag customer preference. The ETOPCO flag in the format overrides
or eliminates the need for the ETOPS Carry-over Flag setting in the customer preference
database. In addition, some flight planning products that interface with JetPlan let you
override the ETOPS Carry-over Flag customer preference setting in the flight plan request.
However, this option is not supported in the JetPlan Engine command line interface. For more
information about these options, contact your Jeppesen Implementation Specialist or Jeppesen
Customer Support.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Terminal Aerodrome Forecast (TAF) Check Preference

The TAF Check customer preference defines the source of the TAFs used during the ETOPS
weather evaluation process. The recommended setting for this preference is 4, which identifies
Jeppesen’s production weather service as the TAF source. If your system does not use the
Jeppesen production weather service, check with Jeppesen Customer Support for the
appropriate setting.

Table 2-2 TAF Check Preference Settings

Setting Definition
0 No Wx (TAF) check is performed.

1 Text file

2 No longer used

3 Wx_API (WnCli) server

4 (Default) WXD server

5 TAF xktran file

6 AOCi weather message WX009

NOTE TAFCHECK=6 requires additional configuration
settings. For more information, contact your Jeppesen
Implementation Specialist.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Setting Up Customer Databases for

ETOPS II
NOTE This document assumes that you use [Link] to perform database
maintenance. For step-by-step procedures on managing the JetPlan databases, see
the database Help files [Link].

This section contains information on customer database parameters used with ETOPS II.
These parameters are in the following databases:

– Customer Aircraft
– Aircraft Fleet
– City Pair Fleet
– Airport
– Airport Fleet
– Flight Brief

IMPORTANT Jeppesen recommends that you configure these databases in the

order listed above.

About the Customer Database Information in this

Guide
The following sections contain tables for each of the customer databases you need to
configure. The tables provide the following information:

• Customer database name – States the database name as it appears in

[Link].
• Parameter name – States each parameter name as it appears on the customer
database Edit page in [Link].
• Optional or required status – Indicates that the parameter is required if
JetPlan needs it to produce valid Critical Fuel Scenario calculations. If the
parameter is optional, your company policies govern whether or not it is
used.

April 11, 2018 ETOPS II Startup Guide v. 1.4

• Notes – Includes a high-level description and ETOPS II-specific setup

information for each parameter, including guidance on locating correct
values.

Finding More Information on Customer Database Parameters

The database tables in this chapter include summary information and special notes about the
ETOPS II database parameters only. This information supplements, but does not replace, the
more detailed database information in the JetPlan User Manual and the [Link] Help
files. To view a database-specific Help file, click the Help tab on that customer database page
in [Link]. You can download the JetPlan User Manual from the User Manuals page on
[Link].

ETOPS II Startup Guide v. 1.4 April 11, 2018

Setting Up the Customer Aircraft Database for

ETOPS II
The Customer Aircraft database contains performance factors that JetPlan uses in ETOPS II
calculations. The following sections describe the optional and required ETOPS II parameters
in the Customer Aircraft database.

IMPORTANT This guide provides supplementary information on ETOPS II

parameters only. For complete definitions, guidelines, and step-by-step procedures,
see the Help file for this database on [Link]. Setting the Fuels Section
Parameters

Figure 2.1 shows the Customer Aircraft database fuel parameters. Parameters outlined in blue
support ETOPS II but are optional. These parameters are used for primary mission burn
calculations. See Table 2-3 on page 20 for more information on these parameters.

Fuel Section Setup

The following parameters
are optional:
• (ST) Situation Code
• (BR) APU Burn Rate
(unloaded burn rate)
These two values are used
together in the Primary
Mission APU Burn
Calculation.

Figure 2.1. ETOPS II Fuel Parameters in the Customer Aircraft Database

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-3 describes the Customer Aircraft database fuel parameters that support ETOPS II.
Use this table in conjunction with the JetPlan User Manual or [Link] Help file, either of
which provides more detailed definitions of these parameters.

Table 2-3 Customer Aircraft Database – ETOPS II Fuels Parameters

Parameter Required/Optional Notes

(HF) Holding Fuel Flow This value is ignored in
ETOPS II flight plan
calculations.

(ST) Situation Code Optional Defines the time frame during which the auxiliary
power unit (APU) runs while in ETOPS airspace.
Set this value based on the aircraft manufacturer’s
recommendations and regulatory requirements for
running the APU during a primary mission.
Input values:
• E – APU fuel burn is calculated for the time
while in ETOPS airspace.
• W – APU fuel burn is calculated for the whole
flight.
• X – APU fuel burn is calculated from takeoff
to the ETOPS exit point.
• None – Set to None if you do not need to
calculate ETOPS APU burn while in ETOPS
airspace.
NOTE The APU Burn Rate (BR) parameter value is
applied only when the Situation Code parameter is
set to E, W, or X.

(BR) APU Burn Rate Optional The APU burn rate parameter applies to aircraft that
require the APU to be running while in ETOPS
airspace. This parameter refers to the unloaded
APU burn rate. Unloaded in this context means that
the APU is running idle. When the APU is running
idle, the fuel burn is lower than when there is a load
on the APU. The APU fuel burn is not included in
the Critical Fuel Scenario (CFS) calculation.
Input value: Pounds or kilos per hour
Example value: 185
NOTE The BR parameter value is applied only if
the Situation Code (ST) parameter is set to E, W, or
X.
NOTE Separate display of the APU fuel burn on
the flight plan is format-dependent. The APU fuel
burn is part of the trip fuel if not otherwise defined in
the format.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Setting the Miscellaneous Section Parameters

Figure 2.2 shows the Customer Aircraft database miscellaneous parameters that support
ETOPS II. The Print ETOPS parameter is required to access the ETOPS parameters. The Hold
Altitude parameter is optional. See Table 2-4 on page 22 for more information on these
parameters.

Misc Section Setup

• Setting (EP) Print
ETOPS to Yes is
required. This setting
makes ETOPS
parameters available
for use in the
Customer Aircraft
database.
• (HA) Hold Altitude is
optional. This value
affects the two-
engine decompressed
scenario, but not the
engine-out scenarios.

Figure 2.2. ETOPS II Miscellaneous Parameters in the Customer Aircraft Database

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-4 describes the Customer Aircraft database fuel parameters that support ETOPS II.
Use this table in conjunction with the JetPlan User Manual or [Link] Help file, either of
which provides more detailed definitions of these parameters.

Table 2-4 Customer Aircraft Database – ETOPS II Miscellaneous Parameters

Parameter Required/Optional Notes

(EP) Print ETOPS Required Makes the ETOPS parameters available for use in
the aircraft record in [Link].
Value: Yes or No
Required value: Yes

(HA) Hold Altitude Optional Defines the altitude at which hold fuel is calculated.
Set this value according to the company policy for
hold.
This value affects the two-engine decompressed
scenario, but not the engine-out scenarios.
This parameter overrides the hold altitude setting
loaded in the aircraft’s generic data.
Value: Altitude entry in feet
Example value: 1500

ETOPS II Startup Guide v. 1.4 April 11, 2018

Setting the ETP Section Parameters

Figure 2.3 shows the Customer Aircraft database ETP parameters. Parameters outlined in blue
support ETOPS II but are optional. These parameters apply to the application of Equal Time
Point (ETP) diversions. See Table 2-5 on page 24 for more information on these parameters.

Figure 2.3. ETOPS II ETP Parameters in the Customer Aircraft Database

ETP Section Setup

• EC, EF/EM, and EC1 are optional.
• These parameters enable you to define speed and
altitude for the divert portion of an ETOPS flight.
• EF is used to specify the ETP Depressurized
Flight Level value in feet. You can also enter this
value as millibars, using the EM parameter.
• In ETOPS flight plans, the value of EC1 is used as
the 1LE Depressurized Cruise Mode.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-5 describes the Customer Aircraft database ETP parameters that support ETOPS II.
Use this table in conjunction with the JetPlan User Manual or [Link] Help file, either of
which provides more detailed definitions of these parameters.

Table 2-5 Customer Aircraft Database – ETOPS II ETP Parameters

Parameter Required/Optional Notes

(EF or EM) ETP Optional Defines the flight level for the divert portion of a
Depressurized Flight depressurized all-engine, low-level ETOPS flight
Level plan. This parameter value acts as both the cruise
flight level and the wind data extract level for the
ETP calculation.
Set this value to reflect the depressurized critical
fuel scenario flight level, typically FL100.
Value: Flight level entered in one of the following
ways:
• As a three-character value representing
hundreds of feet (EF). Example:100 (10000
feet).
• As a three-character millibar value (EM).
Example: 700. See the [Link] Help file
or the JetPlan User Manual for allowed EM
values.
The EF and EM parameters are mutually exclusive.

(EC) ETP All Engine Optional but Defines the cruising speed of the aircraft for the
Depressurized Cruise recommended divert portion of a depressurized, all-engine ETOPS
Mode flight plan, based on cruise table data.
Set this value according to company policy. If the
EC parameter is not set, the system defaults to
Long-Range Cruise (LRC).
The input value must be consistent with table
performance data in the aircraft’s generic record.
For more information, see the “Aircraft Type
Commands” chapter in the JetPlan User Manual.
Value: A three-character cruise mode or true
airspeed entry.
Example value: LRC

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 2-5 Customer Aircraft Database – ETOPS II ETP Parameters (continued)

Parameter Required/Optional Notes

(EC1) ETP 1LE Optional but Defines the cruising speed for the divert portion of
Pressurized/Depressurized recommended the one-engine out depressurized flight plan, based
Cruise Mode on cruise table data. If the EC1 parameter is not set,
NOTE In ETOPS flight
the system defaults to 1LE.
plans, the value of EC1 is The value must be consistent with table
used as the 1LE performance data in the aircraft’s generic record.
Depressurized Cruise For more information, see the “Aircraft Type
Mode. Commands” chapter in the JetPlan User Manual.
Value: A three-character entry specifying an
auxiliary cruise mode. Examples: 330 or M76.

Setting the ETOPS Section Parameters

The ETOPS section in the Customer Aircraft database enables you to control the relevant
performance criteria used in the ETOPS flight plan calculation. Parameters in the ETOPS
section are required for the CFS calculation.

The parameters in the ETOPS section include flags and factors. Flags turn on features, such as
the Anti-Ice function. Factors are formulas used in ETOPS calculations – for example, the
Anti-Ice formula. A flag activates a particular factor and specifies the situation in which it is
applied. The value of a given flag or factor is coded information. Flag codes can be entered in
various combinations, depending on the type of performance factors you want to affect. For
detailed definitions of flags, factors, and coded values, see the “Customer Aircraft Database”
chapter in the JetPlan User Manual.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Figure 2.4 shows the Customer Aircraft database ETOPS section parameters. See Table 2-6 on
page 26 for more information on these parameters.

CADB – ETOPS
Section Setup
• Parameters in red are
required for the CFS
calculation.
• FS and OS are used
for TLS calculations.
• ES1 and ES2 are
used for Suitable
Times calculations.
• AP, AU, AZ, and AY
are used in the APU
burn calculation for
ETOPS diversions.
NOTE APU Burn may be
accounted for in the
engine-out performance
data.
• Other parameters are
recommended or
required for certain
calculations. See
Table 2-6.
• TV, IS, DV, and TR
are not used for
ETOPS II.

Figure 2.4. ETOPS II Parameters in the Customer Aircraft Database

Table 2-6 describes the Customer Aircraft database ETOPS parameters that support
ETOPS II. Use this table in conjunction with the JetPlan User Manual or [Link] Help
file, each of which provides more detailed definitions of these parameter.

Table 2-6 Customer Aircraft Database – ETOPS II Parameters

Parameter Required/Optional Notes

(ED) Use ETOPS Required When this parameter is set to Yes, JetPlan
calculates ETOPS performance based on settings in
the ETOPS section of the aircraft database.
Value: Yes or No (the default)
Required value: Yes

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 2-6 Customer Aircraft Database – ETOPS II Parameters (continued)

Parameter Required/Optional Notes

Icing-Temp Threshold Optional Defines the temperature threshold where anti-ice
(IT) performance calculations begin in an ETOPS flight
plan — for example, -3. Set this value based on the
aircraft manufacturer’s Flight Planning and
Performance Manual.
The IT parameter is used in conjunction with the
Anti-Ice Flag (AI) and the Ice Drag Flag (ID)
parameters in the Customer Aircraft [Link]
temperatures encountered in the flight plan are
above the IT value, anti-ice calculations are applied
(if defined). When temperatures are less than or
equal to the IT value, ice drag calculations are
applied (if defined).
To calculate both AI and ID, set AI=5CEI
(percentage) or 1CEI (whole number).
NOTE This value is used in the calculation of a
temperature-based icing penalty in ETOPS II flight
plans when the Temperature-Based Icing Penalty
parameter in the Flight Brief database is set to On.
This value is not used if the Temperature-Based
Icing Penalty parameter is set to Off (the default
setting).
Value: A temperature value in degrees. Default: 0.
Example value: -3

(ID) Ice Drag Flag Required Defines the application of the ice drag factor
defined by one of the following parameters: (IL) Ice
Drag LRC, (IE) Ice Drag 1LE Factor, and (IL) Ice
Drag LRC Factor.
The ID parameter is used in conjunction with the
Icing TEMP Threshold (IT) parameter.
Value: The predefined flag code followed by the
situation codes.
Recommended value: 1CED.
For additional information about this parameter and
situation codes, see Chapter 5, “ETOPS II for EU-
OPS Business Aviation Operators.”
NOTE The value of this parameter is used in the
calculation of a temperature-based icing penalty in
certain ETOPS II flight plans when the Temperature-
Based Icing Penalty parameter in the Flight Brief
database is set to On. This value is not used if the
Temperature-Based Icing Penalty parameter is set
to Off (the default setting).

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-6 Customer Aircraft Database – ETOPS II Parameters (continued)

Parameter Required/Optional Notes

(AI) Anti-Ice Flag Required Defines the application of the anti-ice factor—the
formula defined by the Anti-Ice LRC Factor (AL)
or Anti-Ice 1LE Factor (AE) parameter. The flag
input value depends on how you want to apply the
anti-ice factor:
• 1 = whole number
• 5 = percentage
The AI parameter is used in conjunction with the
Icing TEMP Threshold (IT) parameter.
Value: The predefined flag code (1 or 5) followed
by the situation codes, up to five alphanumeric
characters.
Recommended value: 5CED.
For additional information about this parameter, see
Chapter 5, “ETOPS II for EU-OPS Business
Aviation Operators.”
NOTE The value of this parameter is used in the
calculation of a temperature-based icing penalty in
certain ETOPS II flight plans when the Temperature-
Based Icing Penalty parameter in the Flight Brief
database is set to On. This value is not used if the
Temperature-Based Icing Penalty parameter is set
to Off (the default setting).

(IL) Ice Drag LRC Factor Required Defines the calculation used to determine the fuel
calculation for ice drag in a depressurized, all-
engine, low-level ETOPS plan.
See aircraft manufacturer’s Flight Planning and
Performance Manual.
Set the value to show the ice drag penalty at the
depressurized flight level with both engines
operating, excluding penalties for thermal anti-ice.
Value: An actual fuel burn value or percentage rate
followed by the factor application codes.
Example value: P1600CDHM

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 2-6 Customer Aircraft Database – ETOPS II Parameters (continued)

Parameter Required/Optional Notes

(IE) Ice Drag 1LE Factor Required Defines the calculation used to determine the fuel
calculation for ice drag in a depressurized, one
engine-out, low-level ETOPS plan.
See the aircraft manufacturer’s Flight Planning and
Performance Manual.
Set the value to show the ice drag penalty
(excluding the thermal anti-ice penalty) at the
depressurized flight level with one engine
operating.
Value: An actual fuel burn value or percentage rate
followed by the factor application codes.
Example value: P700CDHM

(IEP) Ice Drag 1LE Optional Defines the calculation used to determine the fuel
Pressurized (Factor) calculation for ice drag in a pressurized, one
engine-out, low-level ETOPS plan.
See the aircraft manufacturer’s Flight Planning and
Performance Manual.
Set the value to show the ice drag penalty
(excluding thermal anti-ice penalty) at the
pressurized, engine-out flight level.
Value: An actual fuel burn value or percentage rate
followed by the factor application codes.
Example value: P700CDHM

(AL) Anti-Ice LRC Factor Required Defines the calculation used to determine the fuel
calculation for anti-ice operations in a
depressurized, all-engine, low-level ETOPS plan.
See the aircraft manufacturer’s Flight Planning and
Performance Manual.
The value should be set to show the thermal anti-ice
penalty at the depressurized flight level with both
engines operating.
Value: An actual fuel burn value or percentage rate
followed by the factor application codes.
Example value: P400CDHM

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-6 Customer Aircraft Database – ETOPS II Parameters (continued)

Parameter Required/Optional Notes

(AE) Anti-Ice 1LE Factor Required Defines the calculation used to determine the fuel
calculation for anti-ice operations in a
depressurized, one engine-out, low-level ETOPS
plan.
See the aircraft manufacturer’s Flight Planning and
Performance Manual.
The value should be set to show the thermal anti-ice
penalty at the depressurized flight level with one
engine operating.
Value: An actual fuel burn value or percentage rate
followed by the factor application codes.
Example value: P1200CDHM

(AEP) Anti-Ice 1LE Optional Defines the calculation used to determine the fuel
Pressurized (Factor) calculation for anti-ice operations in a pressurized,
one engine-out, low-level ETOPS plan.
See the aircraft manufacturer’s Flight Planning and
Performance Manual.
The value should be set to show the thermal anti-ice
penalty at the pressurized, engine-out flight level.
Value: An actual fuel burn value or percentage rate
followed by the factor application codes.
Example value: P400CDHM

(CF) Conservatism Flag Optional Set to turn on the fuel conservatism calculation and
define the application of the conservatism factor
(the formula defined by the CV parameter).
May be required by regulation if an approved
aircraft performance monitoring program is not in
place.
Value: The predefined flag code followed by the
situation codes.
Example value: Blank 2CE

(CV) Conservatism Factor Optional If the Conservatism Flag (CF) parameter is set, this
parameter identifies the fuel conservatism applied
in the critical fuel scenarios.
The typical setting is 5% as stated in the regulations
for when approved aircraft performance monitoring
systems are not in place.
Value: An actual fuel burn value or percentage rate
followed by the factor application codes.
Example value: P500CD

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 2-6 Customer Aircraft Database – ETOPS II Parameters (continued)

Parameter Required/Optional Notes

(CZ) Cruise Distance Flag Optional Defines the application of the cruise distance factor
(the formula defined by the CD parameter).
Set to apply the cruise distance parameter value
when company policy indicates additional distance
should be planned for critical fuel calculations.
Additional distance may be required to account for
unexpected or expected maneuvering during
diversion.
Value: The predefined flag code followed by the
initial
descent distance.
Example value: 1D20
(CD) Cruise Distance Optional Enables the inclusion of additional mileage in the
Factor cruise distance calculations.
Based on company policy to account for additional
maneuvering distance in critical fuel calculations.
Does not affect the size of approval distance circles.
Value: An added distance in nautical miles,
followed by other inclusion codes.
Example value: 20CD

(ML) Missed Approach Optional Defines the application of the missed approach
Flag (MAP) fuel burn.
Value: Either On or Off. On activates the missed
approach burn factor (MB).
JetPlan converts On to 1 and Off to 2, which is what
[Link] displays on the aircraft record
summary page.
Example value: On (1)
NOTE For more information on using this
parameter value, see Chapter 5, “ETOPS II for EU-
OPS Business Aviation Operators.”

(MB) Missed Approach Optional Defines a missed approach fuel burn amount.
Burn See the aircraft manufacturer ‘s Flight Planning and
Performance Manual.
Value: An amount of fuel, in pounds or kilograms.
Example value: 2500
NOTE For more information on using this
parameter value, see Chapter 5, “ETOPS II for EU-
OPS Business Aviation Operators.”

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-6 Customer Aircraft Database – ETOPS II Parameters (continued)

Parameter Required/Optional Notes

(AP) Auxiliary Power Required Defines the application of the auxiliary power unit
Unit Flag (APU) fuel burn. The flag input value depends on
how you want to apply the APU burn factor (AU).
Expected to be set so that APU computations occur
in both engine-out scenarios. The manufacturer’s
Flight Planning and Performance Manual might
indicate that the APU must be running at all times
when in the ETOPS area with all engines running.
Do not set this flag if the APU burn is built into the
engine-out performance data to avoid double-
booking APU fuel in the critical fuel scenarios.
Value: The predefined flag code followed by the
situation codes.
Example value: 1CED

(AU) APU Loaded Required Defines the loaded APU burn rate at the
Depressurized depressurized flight level as indicated in the aircraft
manufacturer’s Flight Planning and Performance
Manual.
If the CADB Auxiliary Power Unit Flag (AP)
includes the letter E, the system uses the APU
Loaded factor when computing the APU fuel for
the ETOPS Depressurized Engine-Out scenario.
Value: The burn rate in percent or in lbs/kgs hour. A
percentage multiplier or an integer followed by the
divert special flag codes.
Example value: 320CDH

(AZ) APU Unloaded Optional Defines the unloaded APU burn rate at
Depressurized depressurized FL100.
If the CADB Auxiliary Power Unit Flag (AP)
includes the letter C, the system uses the APU
Unloaded factor when computing the APU fuel for
the ETOPS Depressurized All-Engine scenario.
Value: The burn rate in percent or in lbs/kgs hour. A
percentage multiplier or an integer followed by the
divert special flag codes.
Example value: 290CDH

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 2-6 Customer Aircraft Database – ETOPS II Parameters (continued)

Parameter Required/Optional Notes

(AY) APU Loaded Optional Defines the loaded burn rate of the APU at a
Driftdown (Pressurized) nominal driftdown flight level. Use the fuel burn
for the lowest expected flight level occurring in the
Pressurized Engine-Out scenario.
This value might be required if the manufacturer
specifies that the APU should be on at all times
within the ETOPS area. See aircraft manufacturer’s
Flight Planning and Performance Manual.
If the CADB Auxiliary Power Unit Flag (AP)
includes the D or E situation code, the system uses
the APU Loaded Driftdown factor when computing
the APU fuel for the ETOPS Pressurized Engine-
Out scenario.
Value: A percentage multiplier or an integer
followed by the divert special flag codes.
Example value: 420CDH

(HL) Hold Flag Required Defines the application of the hold fuel burn.
Expected to always be set so that Hold fuel is
included in critical fuel calculations.
Value: Time, Fuel, or Ignore
JetPlan converts Time to 1, Fuel to 2, and Ignore to
0, which is what [Link] displays on the
aircraft record summary page.
Example value: Time (1)

(HB) Hold Time Required Defines the time or fuel amount applied to the hold
fuel calculation.
Set according to company policy. The value is
normally 15 minutes to meet most ETOPS
regulations, but other values are supported.
Value: Either a time entry in minutes or a fuel
amount in pounds or kilograms.
Example value: 15

(ES1) Early Arrival TAS Optional Defines the airspeed used in the Earliest Arrival
Time calculation.
Set based on company policy for computation of
Early Arrival Times.
Recommended setting: The fastest TAS expected
for an all-engine, cruise, emergency diversion.
Value: Airspeed in knots
Example value: 420
If you leave this field blank, the system defaults to
465.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-6 Customer Aircraft Database – ETOPS II Parameters (continued)

Parameter Required/Optional Notes

(ES2) Late Arrival TAS Optional Defines the airspeed used in the Latest Arrival
Time calculation.
Set based on company policy for computation of
Late Arrival Times.
Recommend setting: The slowest TAS expected for
a diversion with the aircraft disabled and flying in
adverse conditions.
Value: Airspeed in knots
Example value: 368
If you leave this field blank, the system defaults to
465.

(ESA1) Early Arrival Optional Defines a fast speed altitude that corresponds to the
Flight Level Early Arrival TAS. Used for determining the
correct forecast wind component for a fast
diversion.
Set based on company policy and after consulting
aircraft manufacturer’s Flight Planning and
Performance Manual to determine the appropriate
early arrival flight level for an aircraft that is
disabled to some extent and flying in adverse
conditions.
Value: Flight level in hundreds of feet
Default value: 100 (10,000 feet)
Example value: 100

(ESA2) Late Arrival Optional Defines a slow speed altitude that corresponds to
Flight Level the Late Arrival TAS. Used for determining the
correct forecast wind component for a slow-speed
diversion.
Set based on company policy and after consulting
aircraft manufacturer’s Flight Planning and
Performance Manual to determine the appropriate
late-arrival flight level for an aircraft that is
disabled to some extent and flying in adverse
conditions.
Value: Flight level in hundreds of feet
Default value: 100
Example value: 100

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 2-6 Customer Aircraft Database – ETOPS II Parameters (continued)

Parameter Required/Optional Notes

(FS) Cargo Fire Optional Defines the amount of cargo fire suppression time
Suppression Time Limit used to compute Time Limited Systems compliance
time.
Set based on the aircraft manufacturer’s Flight
Planning and Performance Manual.
This value is used in calculations that confirm the
flying time to an ETOPS alternate beyond 180
minutes does not exceed the time specified for the
Time Limited Systems minus 15 minutes.
Value: Time in minutes
Example value: 298

(OS) Other Most Time- Optional Defines the amount of fire suppression time other
Limiting System Limit than cargo fire suppression that is used by JetPlan
to compute the Time Limited Systems compliance
times
Set based on the aircraft manufacturer’s Flight
Planning and Performance Manual.
This value is used in calculations that confirm the
flying time to an ETOPS alternate beyond 180
minutes does not exceed the time specified for the
Time Limited Systems minus 15 minutes.
Value: Time in minutes
Example value: 345

(PF) Performance Bias Optional Set to apply a performance bias when Hold and
Flag Missed Approach fuels are calculated.
Value: On or Off
JetPlan converts On to 1 and Off to 2, which is what
[Link] displays on the aircraft record
summary page.
Example value: On (1)

April 11, 2018 ETOPS II Startup Guide v. 1.4

Setting Up the Aircraft Fleet Database for ETOPS II

IMPORTANT This guide provides supplementary information on ETOPS II

parameters only. For complete definitions, guidelines, and step-by-step procedures,
see the Help file for this database on [Link].

You can use the Aircraft Fleet database to store and manage data related to a specific aircraft
fleet type. A fleet type is the Jeppesen generic aircraft ID for a specific airframe/engine
combination. For each flight plan request, JetPlan checks the Aircraft Fleet database for a
record that matches the aircraft fleet type in the request. If the record exists, JetPlan uses the
stored data when calculating the flight plan.

For ETOPS II, you can manage up to 12 Speed/Cruise Mode (SCM) datasets in the Aircraft
Fleet database. The SCM datasets include parameters that you can configure for use in
different ETOPS diversion mode and approval time combinations. You must define one SCM
dataset to use as your default. This data is then used in ETOPS II flight plan calculations for
the specified aircraft fleet type.

Each ETOPS SCM dataset is uniquely identified in the database by the combined values of the
ETOPS Diversion Mode Title parameter and the ETOPS Deviation Time parameter (the
approved ETOPS diversion time in minutes). In addition to the ETOPS Range Ring Radius,
each SCM dataset includes corresponding true airspeeds and cruise modes used for ETP and
Critical Fuel Scenario (CFS) calculations.

SCM Dataset Order of Precedence

JetPlan applies the appropriate SCM data to a flight plan using the following logic:

• User interfaces capable of doing so can identify an SCM dataset to use as an

override to any stored default dataset.
• If no user input is submitted as an override, JetPlan uses the default SCM
dataset as defined in the City Pair Fleet database record.
• If JetPlan cannot derive a default SCM dataset from the City Pair Fleet
database record, it uses the default ETOPS SCM dataset in the Customer
Aircraft Fleet database record.
• If the Customer Aircraft Fleet database record does not contain a default
SCM dataset, JetPlan fails the flight plan.

Figure 2.5 on page 37 shows the Customer Aircraft Fleet database ETOPS II Parameters. See
Table 2-7, “Customer Aircraft Fleet Database – ETOPS II Parameters,” on page 38 for more
information on these parameters.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Customer Aircraft Fleet Database -

ETOPS II Setup
• Required parameters are outlined in red.
• Default ETOPS Diversion Mode Title
(DMT) and Default ETOPS Deviation
Time (SD) are required. Together, they
define your default SCM dataset.
• Range Ring Radius (SR#) is required
and specifies the approved ETOPS area
of operation radius for ETOPS
alternates.
• Adequate Airport Radius (AR#)
specifies the small circle radius for the
ETOPS area of operations entry and exit
points calculation. If it is not set, the
entire route is considered ETOPS.
• JetPlan uses 1LE Depressurized ETP
TAS (SO#) to calculate the location of
1LE depressurized equal time points
(ETPs). If 1LE Depressurized ETP TAS
is not set, JetPlan uses the ETP
Depressurized TAS (EA) parameter in
the Customer Aircraft database. If
neither value is set, the GETARC 9
error occurs.
• Setting Initial Descent is recommended
for each scenario. If not set, JetPlan
assumes zero time, fuel, and distance
initial descent. (Descent modes must be
present in the aircraft data file.)
• Setting cruise mode is recommended for
each scenario. If not set, JetPlan uses
ETP All Engine Depressurized Cruise
Mode (EC) and ETP 1LE
Pressurized/Depressurized Cruise Mode
(EC1) in the Customer Aircraft
database. If no cruise mode is set,
JetPlan generates an alert.
• Time-Limited Systems (TLS) Fire
parameters are required for TLS
calculations. If not set, JetPlan cannot
provide compliance for approval times
greater than 180 minutes.

Figure 2.5. ETOPS II Parameters in the Customer Aircraft Fleet Database

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-7 table describes the Customer Aircraft Fleet database parameters that support
ETOPS II. Use this table in conjunction with the JetPlan User Manual or [Link] Help
file, each of which provides more detailed definitions of these parameter.

Table 2-7 Customer Aircraft Fleet Database – ETOPS II Parameters

Parameter Required / Optional Locating the appropriate value

(CFS) Critical Fuel Defines the default CFS fuel pad that is applied to
Scenario Fuel Pad the CFS calculation.
The CFS Pad increases the critical fuel required,
building a reserve to safeguard against overburns
enroute to the critical point or on the diversion leg.
Set based on company policy.
Value: 0–99999 lbs/kgs
Example value: 500

(DMT) Default ETOPS Required Identifies the ETOPS Diversion Mode Title of your
Diversion Mode Title default SCM set. (The ETOPS Diversion Mode
Title and the ETOPS Deviation Time together
constitute the title of your default SCM dataset.)
The value of this parameter must match exactly the
Diversion Mode Title of the SCM dataset you want
to use as the system default.
Value: The ETOPS Diversion Mode Title you are
using as the default.
Example value: 180/320
The default SCM dataset can be overridden. See
“SCM Dataset Order of Precedence” on page 36.

(SD) Default ETOPS Required The value of the ETOPS Deviation Time parameter
Deviation Time for your default SCM set. (The names of the default
ETOPS Diversion Mode Title and the default
ETOPS Deviation Time together constitute the title
of the default SCM dataset.)
The value of this parameter must exactly match the
Deviation Time of the SCM dataset you want to use
as the system default.
Value: The value of the Deviation Time parameter
you are using as the default.
Example value: 180
The default SCM dataset can be overridden. See
“SCM Dataset Order of Precedence” on page 36.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 2-7 Customer Aircraft Fleet Database – ETOPS II Parameters

Parameter Required / Optional Locating the appropriate value

ETOPS Speed Cruise Mode Datasets # (where # is a number from 1 to 12)

General

(DMT#) Diversion Mode Required Defines the title of the SCM dataset. This value and
Title the Deviation Time value together identify an SCM
dataset.
Set according to company policy.
Value: 1–10 alphanumeric characters.
NOTE Diversion Mode Titles can include the
approval time and the approval speed, as shown in
the example, but any value within the character limit
is acceptable.
Example value: 330/320

(SD#) Deviation Time Required Defines the approved ETOPS diversion time in
minutes. This value and the Diversion Mode Title
value together identify an SCM dataset.
Set according to company policy.
Example value: 330

(DS#) Descent Speed Optional Defines an ETOPS descent speed for inclusion in
the ETP summary section of the flight plan output.
This value is not used in computations.
Set according to company policy. The value can be
derived from the aircraft’s Flight Planning and
Performance Manual.
Value: Free text, 0–10 alphanumeric characters.
Example value: 320

(SR#) Range Ring Radius Required for CFS Enables you to specify the radius of the large
ETOPS circles (the ETOPS area of operation radius
for ETOPS alternates.)
The value is derived from the aircraft’s Flight
Planning and Performance Manual, Area of
Operation table.
Value: 0–9999 nm
Example value: 2310

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-7 Customer Aircraft Fleet Database – ETOPS II Parameters

Parameter Required / Optional Locating the appropriate value

(AR#) Adequate Airport Required Specifies the small circle radius for the ETOPS area
Radius of operations entry and exit points calculation. If
this parameter is not set, JetPlan considers the
entire route ETOPS.
The value is derived from the aircraft’s Flight
Planning and Performance Manual, Area of
Operation table.
Value: 0–9999 nm
Example value: 435

(SW#) Reference Weight Optional Enables you to specify the weight the airline uses to
determine aircraft performance for the ETOPS
range-ring radius. JetPlan does not use this weight
in any calculations.
You can derive this value from test flight plans at
various weights for the ETOPS routes.
Jeppesen recommends using this weight to derive
the Range Ring Radius and the Adequate Airport
Radius.
One way to determine this weight is by running a
maximum takeoff weight plan and finding the
aircraft gross weight at the ETOPS entry point.
Value: 0–9999999 lbs/kgs
Example value: 582000

(SO#) 1LE Depressurized Required Specifies the true airspeed (TAS) JetPlan uses to
ETP TAS NOTE If 1LE
calculate the location of 1LE depressurized Equal
Depressurized ETP TAS is Time Points (ETPs) between ETOPS Alternates.
not set, JetPlan uses the Calculated directly from the approval indicated air
ETP Depressurized TAS speed, at the depressurized flight level in standard
(EA) parameter in the conditions.
Customer Aircraft
database. If neither value The example value is the TAS derived from an
is set, the GETARC 9 error approval speed of 310IAS at FL100.
occurs. Value: 0–9999 knots
Example value: 357

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 2-7 Customer Aircraft Fleet Database – ETOPS II Parameters

Parameter Required / Optional Locating the appropriate value

Depressurized Engine-Out

(DO#) Initial Emergency Optional Enables you to store a reference to the performance
Descent data used for the initial descent (emergency
descent) for the depressurized, engine-out scenario.
Reference a descent (EDO) table loaded in JetPlan
Engine for the aircraft type. Consult with your
Jeppesen deployment specialist or customer support
representative to verify that the data exists for the
aircraft type and that your reference to the data is
accurate. The input value needs to match the code
in the aircraft data exactly.
Value: Three alphanumeric characters
Example value: EDO
NOTE If the Initial Emergency Descent parameter
is left blank, the descent is based on zero distance,
zero time, and zero fuel.

(CO#) Cruise Mode Required Specifies the cruise mode JetPlan uses as the basis
for the 1LE depressurized Critical Fuel Scenario
(CFS).
Typically set to the approved engine-out diversion
speed for the aircraft type. Must reference a
performance table for the aircraft type.
Setting cruise mode is recommended. If not set,
JetPlan uses ETP 1LE Depressurized Cruise Mode
(EC1) in the Customer Aircraft database.
Value: A valid cruise mode. The input value needs
to match the code in the aircraft data exactly.
Example value: 320

(FO#) Final Descent Optional Enables you to store a reference to the performance
data used for the final descent for the depressurized
engine-out scenario.
Set according to company policy, if a specific non-
standard descent table should be used for the
aircraft.
Typically unset.
NOTE If this parameter is not set, JetPlan uses the
system final descent value for the aircraft.
Input value: 3 alphanumeric characters. The input
value needs to match the code in the aircraft data
exactly.
Example value: AAA

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-7 Customer Aircraft Fleet Database – ETOPS II Parameters

Parameter Required / Optional Locating the appropriate value

(HO#) Hold Optional Enables you to store a reference to the performance
data used for the hold calculations for the
depressurized engine-out scenario.
Set according to company policy, if a specific non-
standard hold table should be used for the aircraft.
Typically unset.
NOTE If this parameter is not set, JetPlan uses
default Hold tables for the aircraft.
Input value: 3 alphanumeric characters. The input
value needs to match the code in the aircraft data
exactly.
Example value: BBB

Depressurized All-Engine

(DA#) Initial Emergency Optional Enables you to store a reference to the performance
Descent data to use for the initial descent (emergency
descent) for the depressurized all-engine scenario.
Reference a descent (EDA) table loaded in JetPlan
Engine for the aircraft type.
Consult with your Jeppesen deployment specialist
or customer support representative to verify that the
data exists and that your reference the data is
accurate.
Value: 3 alphanumeric characters. The input value
needs to match the code in the aircraft data exactly.
Example value: EDA
NOTE If the Initial Emergency Descent parameter
is left blank, the descent is based on zero distance,
zero time, and zero fuel.

(CA#) Cruise Mode Required This parameter specifies the cruise mode JetPlan
uses as the basis for the all-engine depressurized
Critical Fuel Scenario (CFS).
Set according to company policy.
NOTE Setting cruise mode is recommended. If not
set, JetPlan uses ETP All Engine Depressurized
Cruise Mode (EC) in the Customer Aircraft database.
Value: Valid cruise mode. The input value needs to
match the code in the aircraft data exactly.
Example value: M84

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 2-7 Customer Aircraft Fleet Database – ETOPS II Parameters

Parameter Required / Optional Locating the appropriate value

(FA#) Final Descent Optional Enables you to store a reference to the performance
data to use for the final descent for the
depressurized all-engine scenario.
Set according to company policy, if a specific non-
standard descent table is used for the aircraft.
This value is typically unset.
NOTE If this parameter is not set, JetPlan uses the
system final descent value for the aircraft.
Value: 3 alphanumeric characters. The input value
needs to match the code in the aircraft data exactly.
Example value: AAA

(HA#) Hold Optional Enables you to store a reference to the performance

data to use for the hold calculations for the
depressurized all-engine scenario.
Set according to company policy, if a specific non-
standard hold table is used for the aircraft.
Typically unset.
If this parameter is not set, JetPlan uses default
Hold tables for the aircraft.
Input value: 3 alphanumeric characters. The input
value needs to match the code in the aircraft data
exactly.
Example value: BBB

Pressurized Engine-Out

(DDO#) Initial Driftdown Optional Enables you to store a reference to the performance
Descent data to use for the initial descent (driftdown) for the
pressurized engine-out scenario.
This field is for initial driftdown, not emergency
descent.
Value: 3 alphanumeric characters. The input value
needs to match the code in the aircraft data exactly.
The typical value is DDF.
NOTE If the Initial Emergency Descent parameter
is left blank, the descent is based on zero distance,
zero time, and zero fuel.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-7 Customer Aircraft Fleet Database – ETOPS II Parameters

Parameter Required / Optional Locating the appropriate value

(DCO#) Cruise Mode Required Enables you to specify the cruise mode that JetPlan
uses to compute the cruise fuel for the engine-out,
pressurized Critical Fuel Scenario.
Set according to company policy.
NOTE Setting cruise mode is recommended. If it is
not set, JetPlan uses ETP 1LE Pressurized Cruise
Mode (EC1) in the Customer Aircraft database.
Value: Valid auxiliary cruise mode. The input value
needs to match the code in the aircraft data exactly.
Example value: 320

(DFO#) Final Descent Optional Enables you to store a reference to the performance
data to use for the final descent for the pressurized
engine-out scenario.
Set according to company policy, if a specific non-
standard descent table should be used for the
aircraft.
This parameter is typically unset.
If this parameter is not set, JetPlan uses the system
final descent value for the aircraft.
Input value: 3 alphanumeric characters. The value
must match the code in the aircraft data file exactly.
Example value: AAA

(DHO#) Hold Optional Enables you to store a reference to the performance

data to use for the hold calculations for the
pressurized engine-out scenario.
Set according to company policy, if a specific non-
standard hold table should be used for the aircraft.
This parameter is typically unset.
NOTE If this parameter is not set, JetPlan uses
default Hold tables for the aircraft.
Input value: 3 alphanumeric characters. The input
value needs to match the code in the aircraft data
exactly.
Example value: BBB

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 2-7 Customer Aircraft Fleet Database – ETOPS II Parameters

Parameter Required / Optional Locating the appropriate value

Time Limited Systems Fire

(TLSF#) Calculate TLS Optional but required for Enables you to include or exclude TLS calculations
Time-Limited Systems for the SCM dataset from the ETOPS calculations
(TLS) calculations and from the flight plan output.
Inclusion of TLS data on the flight plan is format-
dependent.
Values: Yes (Include)/No (Exclude)
• Yes–TLS calculations are included in the
ETOPS calculations, and TLS outputs are
included in the flight plan (format-dependent).
• No–TLS calculation are excluded from the
ETOPS calculations.
If the TLS calculations are excluded from the
ETOPS calculations, the TLS-related outputs
associated with a customer’s flight plan format are
as follows:
• Exclude the TLS Compliance Summary.
• Exclude TLS Fire Alerts.
• Exclude the TLS Compliance Summary for
each ETP.
• Include the TLS Diagnostics with all data
values blank.

(TFL#) Cruise FL Required for (TLS) Enables you to store a flight level to use in time
calculations computations for TLS fire suppression scenario
plans.
Indicates the nominal flight level for an all-engine
emergency diversion for the aircraft type.
Set according to company policy.
Value: A 3-digit value that identifies a flight level in
hundreds of feet.
Example value: 280

(TID#) Initial Descent Optional Enables you to store a reference to the performance
data to use for the initial descent (driftdown) for
TLS fire suppression scenario computations.
Indicates the descent profile to be used from
primary mission cruise altitude to the Cruise FL.
Typically left unset.
Value: 3 alphanumeric characters. The value must
match the code in the aircraft data file exactly.
Example value: HSP

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-7 Customer Aircraft Fleet Database – ETOPS II Parameters

Parameter Required / Optional Locating the appropriate value

(TCR#) Cruise Mode Required for (TLS) Enables you to store a reference to the performance
calculations data (the cruise mode) used to compute the level-
flight cruise portion of the TLS fire suppression
scenario computations. This cruise mode value is
used to model an emergency diversion.
Set according to company policy.
Value: A valid cruise mode (3 alphanumeric
characters). The value must match the code in the
aircraft data file exactly.
Example value: M87

(TFD#) Final Descent Optional Enables you to store a reference to the performance
data to use for the final descent for the TLS fire
suppression scenario computations.
Set according to company policy.
If the Final Descent parameter is blank for the SCM
dataset associated with a flight plan computation,
JetPlan computes the final descent using the generic
descent model.
NOTE The FAA does not require a final descent to
be computed. When this field is not set for TLS, the
system computes cruise to a point directly over the
airport.
Value: 3 alphanumeric characters. The value must
match the code in the aircraft data file exactly.
Example value: HSP

ETOPS II Startup Guide v. 1.4 April 11, 2018

Setting up the City Pair Fleet Database for ETOPS II

IMPORTANT This guide provides supplementary information on ETOPS II

parameters only. For complete definitions, guidelines, and step-by-step procedures,
see the Help file for this database on [Link].

You can use the City Pair Fleet database to store and manage data related to a specific
departure and arrival airport combination (a city pair) and a specific aircraft fleet type. A fleet
type is a specific airframe/engine combination. For each flight plan request, JetPlan checks the
City Pair Fleet database for a record that matches the city pair/fleet combination in the request.
If the record exists, JetPlan uses the stored data when calculating the flight plan.

For ETOPS II, you can define a default SCM dataset for a given city pair/fleet type
combination. In the City Pair Fleet database record for the city pair/fleet type combination,
you can create the default SCM database set by referencing a specific SCM set in the
Customer Aircraft Fleet database. Up to 12 SCM sets can be defined and stored in the
Customer Aircraft Fleet database. Each SCM set is uniquely identified by the values of the
ETOPS Diversion Mode Title parameter and the ETOPS Deviation Time parameter (the
approved ETOPS diversion time in minutes). You must ensure that the value of the ETOPS
Diversion Mode Title and the ETOPS Deviation Time parameters in the City Pair Fleet
database record exactly match the values of those parameters in the Customer Aircraft Fleet
database SCM dataset that you want to use as the default for the city pair/fleet.

If you set up a default SCM dataset in the City Pair Fleet database, JetPlan uses that data in
any flight plan request including a matching city pair/fleet combination. If the City Pair Fleet
database does not include a default SCM dataset, JetPlan follows the order of precedence
described in “Setting Up the Aircraft Fleet Database for ETOPS II” on page 36.

Figure 2.6 shows the City Pair Fleet database parameters that support ETOPS II. See
Table 2-8 on page 48 for more information on these parameters.

ETOPS SCM Dataset City Pair Fleet Database – ETOPS II Setup

ETOPS Diversion Mode Title 180/320
• Use the ETOPS Diversion Mode Title and the ETOPS
ETOPS Deviation Time 180 MIN
Deviation Time parameters to define a default ETOPS
SCM dataset for a specific city pair/fleet combination.
• Ensure that the value of the ETOPS Diversion Mode
Title and the ETOPS Deviation Time parameters in
the City Pair Fleet database record exactly match the
values of those parameters in the Aircraft Fleet
database SCM set that you want to use as the default
for the city pair/fleet.

Figure 2.6. ETOPS II Parameters in the City Pair Fleet Database

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-8 describes the City Pair Fleet database ETOPS parameters that support
ETOPS II. Use this table in conjunction with the JetPlan User Manual or [Link] Help
file, each of which provides more detailed definitions of these parameter.

Table 2-8 Customer City Pair Fleet Database – ETOPS II Parameters

Parameter Required / Optional Notes

(SN) ETOPS Diversion Optional This parameter is the customer-specified title of the
Mode Title SCM set used as the default for the designated city
pair and fleet type. This parameter and ETOPS
Deviation Time together constitute the SCM dataset
key in the City Pair Fleet database record. Both
parameters are required if the ETOPS SCM set is
used. This title/time combination must exactly
match those of the SCM set in the Aircraft Fleet
database that is being referenced as the default for
this city pair/fleet type combination.
This value is set based on company policy.
Value: The ETOPS Diversion Mode Title you are
using as the default.
Example value: 180/320

(SD) ETOPS Deviation Optional Indicates the number of minutes that defines the
Time approved ETOPS diversion time for the designated
city pair and fleet type. This parameter and
Diversion Mode Title together constitute the SCM
dataset key in the City Pair Fleet database record.
Both parameters are required if the ETOPS SCM
set is used. This title/time combination must match
exactly those of the SCM set in the Aircraft Fleet
database that is being referenced as the default for
this city pair/fleet type combination.
Value: The value of the Deviation Time parameter
you are using as the default.
Example value: 180

ETOPS II Startup Guide v. 1.4 April 11, 2018

Setting Up the Customer Airport Database for

ETOPS II

IMPORTANT This guide provides supplementary information on ETOPS II

parameters only. For complete definitions, guidelines, and step-by-step procedures,
see the Help file for this database on [Link].

The Customer Airport database enables you to create and maintain airports and custom values
associated with each airport. For each flight plan request, JetPlan checks the Customer Airport
database for a record that matches the airport in the request. If the record exists, JetPlan uses
the stored data when calculating the flight plan.

The ETOPS Approach parameters in the Customer Airport database let you define ceiling and
visibility minimum values used in the weather suitability checks of ETOPS II alternates.
Settings in the Airport database apply to any aircraft type. Any ETOPS Approach parameters
defined for the airport in the Customer Airport Fleet database record take priority over those
approach values in the Customer Airport record.

IMPORTANT A Customer Airport database record must exist for any airport
specified in an ETOPS request. This is true even if the ceiling and visibility for the
same airport are defined in the Customer Airport Fleet database.

Figure 2.7 shows the Customer Airport database parameters that support ETOPS II. See
Table 2-9 on page 50 for more information on these parameters.

Customer Airport Database – ETOPS II Setup

-- ETOPS APPROACH
• A Customer Airport record must exist for any airport used in an
ETOPS Ceiling MIN 800 FEET
ETOPS flight plan.
ETOPS Visibility MIN 9000 FEET
• The ETOPS Approach parameters define Ceiling Minimum
(ECM) and Visibility Minimum (EVM) used in suitability
checks.
• Ceiling and visibility minimum values defined in the Customer
Airport Fleet database override these settings in the Airport
database.
• If no minimum values are defined, JetPlan assumes that the
airport is suitable in any weather.

Figure 2.7. ETOPS II Parameters in the Customer Airport Database

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-9 describes the Customer Airport database parameters that support
ETOPS II. Use this table in conjunction with the JetPlan User Manual or [Link] Help
file, each of which provides more detailed definitions of these parameter.

Table 2-9 Customer Airport Database – ETOPS II Parameters

Parameter Required/Optional Notes

(ECM) ETOPS Ceiling Optional Defines the ceiling minimum for the airport in feet
Minimum or meters.
This parameter is used to determine if an ETOPS
alternate is suitable based on the TAF weather
between the early arrival time and later arrival time.
If the Customer Airport Fleet database does not
include a ceiling minimum value for this airport,
JetPlan checks for the minimum in the Customer
Airport database. If there is no minimum value in
the Customer Airport database, JetPlan uses zero
ceiling and assumes the airport is suitable in any
weather.
Value: 0–10000 feet or meters
Example value: 800

(EVM) ETOPS Visibility Optional Defines the visibility minimum for the airport in
Minimum feet or meters.
This parameter is used to determine if an ETOPS
alternate is suitable based on the TAF weather
between the early arrival time and later arrival time.
If the Customer Airport Fleet database does not
include a visibility minimum value for this airport,
JetPlan checks for the minimum in the Customer
Airport database. If there is no minimum value in
the Customer Airport database, JetPlan uses zero
visibility and assumes the airport is suitable in any
weather.
Value: 0–10000 feet or meters
Example value: 9000

ETOPS II Startup Guide v. 1.4 April 11, 2018

Setting Up the Airport Fleet Database for ETOPS II

IMPORTANT This guide provides supplementary information on ETOPS II

parameters only. For complete definitions, guidelines, and step-by-step procedures,
see the Help file for this database on [Link].

The Airport Fleet database enables you to define and manage data for combinations of specific
airports and specific aircraft fleet types. A fleet type is the Jeppesen generic aircraft ID that
defines a specific airframe/engine combination. For each flight plan request, JetPlan checks
the Airport Fleet database for a record that matches the combination of airport and aircraft
fleet type in the request. If the record exists, JetPlan uses the stored data when calculating the
flight plan.

Airport fleet records contain parameters that JetPlan uses to determine the ETOPS area of
operations in an ETOPS II flight plan. If you use the Airport Fleet database for ETOPS
planning, define a sufficient number of adequate ETOPS airports to ensure that the ETOPS
entry and exit points are accurately calculated. Also, create records for all approved ETOPS
alternates in your company’s operations specifications.

The ETOPS II parameters in the Airport Fleet database also include the weather minimum
values used in the weather suitability checks of ETOPS alternates. Weather minimums in the
Customer Airport Fleet take precedence over minimums for ETOPS alternates in the
Customer Airport database.

Overriding Airport Fleet Database Records on a Flight Plan

Request
Customers who operate under ETOPS rules typically create Airport Fleet records for adequate
airports supporting acceptable ETOPS entry and exit points for every potential flight.
However, you can also run ETOPS II flight plans without first having to set up or modify the
Airport Fleet database. In the [Link] Basic Flight Planner, you can use options on the
04 Line to add to, subtract from, or replace all the adequate airports in the Airport Fleet
database. For example, if an airport is currently unavailable due to a NOTAM, you can
exclude that airport from the flight plan request and submit an alternative adequate airport
directly in the flight plan request. For more information, see “Adequate Airports” in Table 3-2,
“Basic Flight Planner ETOPS II Alternates (ETOPS ALTS) Options,” on page 68.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Figure 2.8 shows the Customer Airport Fleet database parameters that support ETOPS II. See
Table 2-10 on page 53 for more information on these parameters.

Customer Airport Fleet

Database – ETOPS II Setup
• ETOPS Suitable Alternate
(ESU) airports – Acceptable
for use as alternates, typically
based on carrier's operations
specification.
• ETOPS Adequate Alternate
(EAD) airports –
Recommended for correct
ETOPS segment (entry/exit
point) calculation.
• ETOPS Approach values –
Define Ceiling Minimum
(ECM) and Visibility
Minimum (EVM) used in
suitability checks.
• ETOPS Approach values in
the Customer Airport Fleet
override ETOPS approach
values in the Airport database.
• If no ETOPS Approach
minimum values are defined,
JetPlan assumes that the
airport is suitable in any
weather.

Figure 2.8. ETOPS II Parameters in the Customer Airport Fleet Database

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 2-10 describes the Customer Airport Fleet database parameters that support
ETOPS II. Use this table in conjunction with the JetPlan User Manual or [Link] Help
file, each of which provides more detailed definitions of these parameters.

Table 2-10 Customer Airport Fleet Database – ETOPS II Parameters

Parameter Required/Optional Notes

Alternate Availability Parameters

(ESU) ETOPS Suitable Optional Defines the airport as acceptable for use in the
Alternate flight plan as an ETOPS alternate, typically based
on its inclusion in the carrier's operations
specification. Refer to the approved ETOPS
alternate airports included in the operations
specifications.
Value: Yes or No

(EAD) ETOPS Adequate Optional but Defines the airport as an ETOPS adequate alternate,
Alternate recommended for use in calculating the ETOPS area of operation.
Identify a sufficient number of airports to meet
regulatory requirements and to provide coverage of
the potential routes so that ETOPS entry and exit
points are accurately calculated.
Value: Yes or No

ETOPS Approach Parameters

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-10 Customer Airport Fleet Database – ETOPS II Parameters (continued)

Parameter Required/Optional Notes

Setting Up the Flight Brief Database for ETOPS II

The Flight Brief database enables you to automatically apply certain data or conditions to
certain flight plan requests. When you create a flight brief record, you select a flight brief type,
which defines the type of data or condition that you want to apply automatically. Then you use
the selection criteria options in the database to limit application of the data or condition to
certain flight plan requests. For each flight plan request, JetPlan checks the Flight Brief
database for a record that contains criteria that match elements in the request—for example,
the POD, fleet number, flight number, or date. If a matching record exists, JetPlan applies the
data or condition defined by the flight brief record to the flight plan calculation.

The (E) EU-ETOPS Early/Late Override flight brief type applies only to ETOPS II flight
plans. You can use the (E) EU-ETOPS Early/Late Override flight brief type to apply the
following conditions to ETOPS II flight plans:

• Specify whether or not JetPlan applies a 5% wind penalty to ETOPS II flight

plan calculations.
• Specify whether or not JetPlan applies a temperature-based icing penalty
logic to ETOPS II flight plan calculations.
• Specify which ETOPS critical fuel scenarios are computed and used in the
ETOPS uplift calculations and which critical fuel scenarios are displayed in
the extended output block on the flight plan.

ETOPS II Startup Guide v. 1.4 April 11, 2018

• Specify values that support multi-segment ETOPS flight planning

functionality, which enables you to do the following:
– Treat consecutive ETOPS segments that are beyond a configurable
distance from one another as two separate ETOPS segments, as
opposed to combining them
– Determine which ETPs the system can omit based on a configurable
distance between the abeam points of the forward and backward
alternates
• Specify buffer time parameters that extend the early and late arrival times at
ETOPS alternates. JetPlan includes the suitable times for an alternate in the
Airport Suitable Time block of the flight plan using the following
calculations:
– Suitable Early Arrival Time = Early Arrival Time - Early Buffer
Time.
– Suitable Late Arrival Time = Late Arrival Time + Late Buffer
For example, for EU ETOPS, the values would be set in the Flight Brief
database as follows:
– ETOPS Early Buffer = 0 minutes
– ETOPS Late Buffer = 60 minutes
For each ETOPS alternate computed for the plan, the JetPlan provides the
following information on the flight plan:
– The airport ID in ICAO format
– The ETOPS early arrival time, including early and late time buffers
– The ETOPS late arrival time, including early and late time buffers
For an example of the Airport Suitable Time block in a flight plan, see
Figure 7.15 on page 117.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Figure 2.9 shows the Flight Brief database parameters that support ETOPS II. See Table 2-11
on page 57 for more information on these parameters.

Flight Brief Database – ETOPS II

Setup
• Required to create a flight brief
record: Set Flight Brief Type to
E.
• ETOPS Early and Late Buffer
– Specify number of minutes to
extend early and late arrival
times.
• 5% Wind Bias – Set to On to
include the 5% wind penalty
• Temp-Based Icing Penalty –
Set to On to apply a
temperature-based icing
penalty to anti-ice and ice-drag
computations
• Scenario Options – Select
which critical fuel scenarios
are computed and used in the
ETOPS uplift calculations and
which are displayed in the
extended output block on the
flight plan.
• Multi-Segment ETOPS
Options – Specify the
maximum distance between
consecutive ETOPS segments
and include ETP in
computations for alternates

Figure 2.9. ETOPS II Parameters in the Flight Brief Database

Table 2-11 describes the Flight Brief database parameters that support
ETOPS II. Use this table in conjunction with the JetPlan User Manual or [Link] Help
file, each of which provides more detailed definitions of these parameters.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 2-11 Customer Flight Brief Database – ETOPS II Parameters

Parameter Required/Optional Notes

Flight Brief Record Name Required to create a flight
brief record.

Flight Brief Type Required to create a Type For ETOPS II flight plan options, this parameter
Parameter E flight brief record. must be set to (E) EU-ETOPS Early/Late Override.

ETOPS Early Buffer Optional The ETOPS Early Buffer and ETOPS Late Buffer
let you extend the early and late arrival times at
ETOPS alternates by setting the buffer times.
For example, according to NPA-OPS40A, “An
aerodrome may be nominated as an ETOPS Route
Alternate for flight planning and release purposes if
the available forecast weather conditions are
favorable and fall between the anticipated time of
landing until one hour after the latest possible time
of landing.” To satisfy this regulation, you could,
for example, set an arrival time early buffer to 0
minutes and a late buffer to 60 minutes. Note that
the buffer times might have to be different to satisfy
other aviation authorities.
Value: 000–999 (time in minutes). Example: 60
NOTE If no Type E flight brief record exists for a
flight, the default buffer times are zero. However, an
operator can apply buffer times to all its flights by
creating a single flight brief record for Flight Brief
Type E, and entering the buffer times. Similarly, to
have buffer times apply to all flights for a Fleet Type,
enter the Fleet Type and the buffer times.

ETOPS Late Buffer Optional The ETOPS Late Buffer option lets you extend the
late arrival time at an ETOPS alternate. See also the
description for the ETOPS Early Buffer parameter
above.
Value: 000–999 (time in minutes)
Example: 60

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-11 Customer Flight Brief Database – ETOPS II Parameters

Parameter Required/Optional Notes

(WIND) 5% Wind Bias Required When this option is set to On (the default), the
NOTE If no matching
system includes the 5% wind penalty in matching
Flight Brief Database ETOPS II flight plan requests. The wind adjustment
JetPlan Command-Line
record exists, the system is applied. The average wind component is
Codes:
automatically applies 5% computed using the forecast winds for the
WIND=Y/N, where: bias (5% higher following ETOPS II scenarios associated with each
Y=On headwinds, and 5% lower diversion:
tailwinds), as defined in
N=Off • Depressurized Engine Out
FAA regulations. See also
Chapter 5, “ETOPS II for • Depressurized All Engine
EU-OPS Business Aviation • Pressurized Engine Out
Operators.”
When this option is set to Off, no wind adjustment
is applied.
Values: On/Off. On is the default setting.
For additional information about this parameter, see
Chapter 5, “ETOPS II for EU-OPS Business Aviation
Operators.”

(ICE) Temp-Based Icing Optional When this option is set to On, the system applies a
Penalty NOTE When this option
temperature-based icing penalty logic to compute
is set to Off (the default), icing penalties in matching ETOPS II flight plan
the system applies non- requests.
JetPlan Command-Line
temperature-based icing Anti-ice and Ice-drag penalties are computed using
Codes:
penalty logic. the following Customer Aircraft database
ICE=Y/N, where:
parameter values:
Y=On
• Icing Temperature (IT)
N=Off
• Anti-Ice Flag (AI)
• Ice Drag Flag (ID)
For more information, see “Setting the ETOPS
Section Parameters” on page 25.
Values: On/Off. Off is default setting.
For additional information about this parameter, see
Chapter 5, “ETOPS II for EU-OPS Business
Aviation Operators.”

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 2-11 Customer Flight Brief Database – ETOPS II Parameters

Parameter Required/Optional Notes

(ETOPS II) Scenario Optional NOTE These parameters replace the Cruise Mode
Options Begin Flag (CS) and Cruise Mode End Flag (CE)
IMPORTANT If a flight
parameters in the Customer Aircraft database in
has a matching Flight Brief
ETOPS II flight plans only. Any values set for those
JetPlan Command-Line record, but one or more of
parameters are not used in ETOPS II flight plan
these scenarios is not set
Codes: calculations. However, CS and CE are still used in
in the record, the system
legacy ETOPS flight plans.
D1LEF - Engine-Out defaults to “Output in Plan,
Depressurized scenario Use in Uplift” for the These options enable you to control:
DLRCF - All-Engine scenarios that are not set. • Which ETOPS critical fuel scenarios are
Depressurized scenario computed and used in the ETOPS uplift
If no matching FBDB
P1LEF - Engine-Out record exists for the flight,
calculations. (Uplift is a fuel which is added to
Pressurized scenario the system automatically takeoff fuel to compensate for ETOPS fuel
uses all three scenarios in shortfall.)
Options for each scenario:
the critical fuel calculation • Which ETOPS critical fuel scenarios are
1 - Output in plan, Use in and outputs all three displayed in the extended output block on the
uplift (default value) scenarios in the extended flight plan.
2 - Output in plan, output block on the flight
plan. You can choose one or all of the following
Exclude in uplift
scenarios:
3 - Do not output, Exclude If all three scenarios are • Engine-Out Depressurized
in uplift set to “Do not output,
Exclude in uplift,” the • All-Engine Depressurized
Examples: D1LEF=1
DLRCF=2 P1LEF=1 system computes the flight • Engine-Out Pressurized
plan without ETOPS, and
outputs an alert that all
three scenarios have been
excluded and that a fuel
deficit may exist. The
system does not output
any ETOPS data on the
flight plan.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 2-11 Customer Flight Brief Database – ETOPS II Parameters

Parameter Required/Optional Notes

(ETOPS II) Scenario For each of the scenarios above, you can choose
Options (continued) one of the following options:
• Output in plan, Use in uplift – (Default) The
TOTAL fuel for the selected scenario is used
in the calculation of the total fuel required for
the Equal Time Point (ETP). The data column
for the scenario is output in the EQUAL TIME
POINT DATA section of the flight plan if it
was included in the flight plan request.
• Output in plan, Exclude in uplift – The
TOTAL fuel for the selected scenario is not
used in the calculation of the total fuel
required for the ETP. The data column for the
scenario is output in the EQUAL TIME
POINT DATA section of the flight plan if it
was included in the flight plan request.
• Do not output, Exclude in uplift – The TOTAL
fuel for the selected scenario is not used in the
calculation of the total fuel required for the
ETP. The data column for the scenario is not
output in the EQUAL TIME POINT DATA
section of the flight plan if it was included in
the flight plan request. See also the following
IMPORTANT note.
NOTE If all three scenarios are set to “Do not
output, Exclude in uplift,” the system computes the
flight plan without ETOPS, and outputs an alert that
all three scenarios have been excluded and that a
fuel deficit may exist. The system does not output
any ETOPS data on the flight plan.

(ETOPS II) Multi-Segment ETOPS Options

Combine ETOPS Optional but required for This option lets you specify a maximum distance in
segments less than <n> Multi-Segment ETOPS nautical miles between consecutive ETOPS
nm apart calculations segments. If the distance between any two ETOPS
segments is less than or equal to the value of this
parameter, the system considers the two ETOPS
segments and the route in between them as one
ETOPS segment.
NOTE If you do not enter a value for this
parameter, the system uses 9999 nm as the default
value. In this case, the system considers the two
ETOPS segments and the entire route between
them as one ETOPS segment.
Values: 1–9999 nautical miles. The default value is
9999.
Example: 0100

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 2-11 Customer Flight Brief Database – ETOPS II Parameters

Parameter Required/Optional Notes

Include ETP in Optional but required for This option lets you specify a factor that the system
computation for alternates Multi-Segment ETOPS multiplies by the range ring radius used in the flight
closer than <n> times the calculations plan to define a maximum distance between two
range-ring radius sequential ETOPS alternates. The system uses the
distance value to determine whether to include the
ETP between the alternates in the flight plan.
The system computes the ETP, associated critical
fuel, and early and late arrival time (EAT/LAT)
values for each ETOPS alternate pair that is closer
together than the maximum distance. The system
also includes these ETPs in the ETP summary
output on the flight plan and as waypoints in the
navigation log. ETPs for alternate pairs that are
farther apart than the maximum distance are
omitted from the flight plan results unless they
occur during an ETOPS segment.
NOTE The applicable range ring radius is stored in
the Speed Cruise Mode (SCM) dataset that is used
to compute ETOPS for the flight plan. The SCM sets
are stored in the City Pair Fleet and Aircraft Fleet
databases.
NOTE If you do not enter a value for this
parameter, the system applies no limit to the
distance between two sequential ETOPS alternates.
In this case, the system computes ETPs and the
associated critical fuel and EAT/LAT values between
each alternate.
NOTE If you enter 0.000 for this parameter, the
system treats each sequential ETOPS alternate as a
standalone alternate and does not compute the ETP
between them.
Values: 0.000–99.999
Example: 1.800

April 11, 2018 ETOPS II Startup Guide v. 1.4

Running ETOPS II Flight

Plans

This chapter includes the following sections:

• Requesting an ETOPS Flight Plan

• About the ETOPS II Options
Running ETOPS II Flight Plans
Requesting an ETOPS Flight Plan

Requesting an ETOPS Flight Plan

You can run ETOPS II flight plans with several of Jeppesen’s flight planning products,
including [Link]’s Basic Flight Planner and JetPlanner. Each application has its own
graphical user interface (GUI) and its own method of selecting flight plan options. However,
the same ETOPS II flight plan options are used in all the interfaces.

This guide focuses on using ETOPS II with the Basic Flight Planner in [Link]. For
information on using ETOPS II with another Jeppesen flight planning product, refer to the
product’s user documentation.

The Basic Flight Planner in [Link] enables you to submit the necessary information for a
flight plan request, such as the POD, POA, aircraft, operating weight, and so on. This guide
focuses only on ETOPS II-specific options. For information on non-ETOPS II options, see the
JetPlan User Manual or your flight planning product’s user documentation.

To generate an ETOPS II flight plan, you need to specify an ETOPS II flight plan option in the
01 OPTIONS box in the Basic Flight Planner Form in [Link]. For the list of ETOPS II
flight plan options, see Table 3-1 on page 67. If you use the ETOPN, ETOPXN, or ETOPXNL
01 option, you can also specify additional options in the 04 ETOPS ALTS box. For a list of
the 04 ETOPS ALTS options, see Table 3-2 on page 68.

April 11, 2018 ETOPS II Startup Guide v. 1.4

To request an ETOPS II flight plan in the Basic Flight Planner

1. Go to [Link].
2. Click the Basic Flight Planner tab.
The Basic Flight Planning Form dialog box opens.

3. In the 01 OPTIONS box, type the desired ETOPS II flight plan option. See
Table 3-1 on page 67 for possible 01 options.
If you type ETOPN, ETOPXN, or ETOPXNL in the 01 OPTIONS box, the
04 ETOP ALTS box becomes available.
4. If you specify the ETOPN, ETOPXN, or ETOPXNL 01 Option, you can
also specify an 04 ETOP ALTS option in the corresponding box. For a list
of possible 04 ETOP ALTS options, see Table 3-2 on page 68.

NOTE ETOPS II supports manual selection of alternates only.

5. Click Generate Flight Plan.

ETOPS II Startup Guide v. 1.4 April 11, 2018

About the ETOPS II Options

In the [Link] Basic Flight Planner Form dialog box, you can enter ETOPS II flight plan
options in the 01 OPTIONS box and ETOPS alternates options in the 04 ETOP ALTS box.
The following tables describe these options in detail. For information on how to use these
options in the Basic Flight Planner, see “ETOPS II Flight Plan Input Examples” on page 74.

NOTE The ETOPS II 01 OPTIONS listed in Table 3-1 can be used with any of the
other standard 01 OPTIONS options (except for the legacy ETOPS options). The
04 ETOP ALTS options listed in Table 3-2 are available only when certain ETOPS II
01 OPTIONS are used.

ETOPS II Flight Plan Options

Table 3-1 lists ETOPS II flight plan options that you can specify in the 01 OPTIONS box in
the Basic Flight Planner Form dialog box. The ETOPS II flight plan options invoke
ETOPS II functionality and instruct the application to generate an ETOPS II flight plan using
the other information you provide in the Basic Flight Planner. With some ETOPS II 0 Options,
you can specify additional ETOPS II options in the 04 ETOP ALTS box.

More details are provided in Table 3-1 and in Table 3-2.

Table 3-1 Basic Flight Planner ETOPS II Flight Plan (01) Options

01 Option Explanation
FP, ETOPN Basic ETOPS II Option. This option invokes JetPlan’s ETOPS II feature. The
ETOPS critical fuel reserve computation includes three scenarios: Depressurized
Engine-Out, Depressurized All-Engine, and Pressurized Engine-Out.
NOTE When using the ETOPN, ETOPXN, and ETOPXNL 01 OPTIONS, you can
also specify certain 04 ETOP ALTS options. See Table 3-2 on page 68 for a list of
supported ETOP ALTS options.

FP, ETOPNL Basic ETOPS II Option with Diagnostics. This option invokes JetPlan’s ETOPS II
feature and produces the same plan as ETOPN. However, the flight plan output also
includes ETOPS diagnostic information.

FP, ETOPXN Extended ETOPS II Option. This option invokes JetPlan’s ETOPS II feature.
However, the flight plan output also includes an extended report for the Critical Fuel
Scenarios computation.
NOTE When using the ETOPN, ETOPXN, and ETOPXNL 01 OPTIONS, you can
also specify certain 04 ETOP ALTS options. See Table 3-2 on page 68 for a list of
supported ETOP ALTS options.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 3-1 Basic Flight Planner ETOPS II Flight Plan (01) Options (continued)

01 Option Explanation
FP, ETOPXNL Extended ETOPS II Option with Diagnostics. This option invokes JetPlan’s
ETOPS II feature and produces the same output as ETOPXN. However, the flight
plan output also includes ETOPS diagnostic information.
NOTE When using the ETOPN, ETOPXN, and ETOPXNL 01 OPTIONS, you can
also specify certain 04 ETOP ALTS options. See Table 3-2 on page 68 for a list of
supported ETOP ALTS options.

FP, RC Reclear Option. When the RC or RCC option is used with the ETOPS II options,
or the ETOPS exit point for the reclear leg is factored into the computation of the Early
Arrival Time (EAT) and Late Arrival Time (LAT) for the ETOPS alternate that is
FP, RCC
closest to the reclear leg exit point. In the plan to the reclear destination, the EAT or
LAT for the closest alternate might differ from the values computed in the plan to the
intended destination.

ETOPS II Alternates Options

Table 3-2 lists the ETOPS alternates options. In the Basic Flight Planner, specify ETOPS
alternate information in the 04 ETOP ALTS box. The 04 ETOP ALTS box is available only
when the specified 01 Option is one of the following: ETOPN, ETOPXN, and ETOPXNL. For
more information on the ETOPS II 01 Options, see “ETOPS II Flight Plan Options” on
page 67.

Table 3-2 Basic Flight Planner ETOPS II Alternates (ETOPS ALTS) Options

Option Explanation
<airport code>/<airport code>/<airport code> ETOPS II Alternates. For ETOPS II, the ICAO or
where <airport code> is the code for an ETOPS II IATA codes for the alternates are entered in the
alternate, up to 12 alternates, each separated by a slash 04 ETOP ALTS box with each alternate separated by
a slash (/). If the POD or POA is desired as an
alternate, you must explicitly include it. You can enter
up to 12 alternates.
Example: KSFO/PHOG

<airport code> ETOPS II Single Alternate. For ETOPS II, you can
where <airport code> is the code for a single enter a single alternate for the ETOPS segment. In this
ETOPS II alternate situation, there is no Equal Time Point. Therefore,
JetPlan bases the Critical Fuel Scenario on the
diversions to the alternate from the ETOPS Entry and
Exit Points.
Example: UHPP

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 3-2 Basic Flight Planner ETOPS II Alternates (ETOPS ALTS) Options (continued)

Option Explanation
<airport code>[,Ice%1][,Ice%2] ETOPS II Icing Percentages. For ETOPS II, you can
optionally specify icing percentages (ICE%) for
diversion legs to determine what part of the route has
an icing condition. When you enter an icing
percentage, JetPlan computes the icing fuel in the
Critical Fuel Scenario as Ice% of the icing fuel
calculated for the entire diversion leg. The rules for
Ice% are as follows:
• <airport code> with no ice percentages – Critical
Fuel Scenarios are based on 100% icing.
• <airport code> with Ice%1 icing percentage –
Icing percentage is applied to the forward
diversion leg to the alternate.
• <airport code> with Ice%2 icing percentage –
Icing percentage is applied to the backward
diversion leg to the alternate. A comma (,) must
be used for the forward diversion leg—for
example, CYQX,,45.
• <airport code> with both Ice%1 and Ice%2 –
Ice%1 is applied to the forward diversion leg to
the alternate, and Ice%2 is applied to the
backward diversion leg to the alternate.
NOTE Computation of Critical Fuel Scenarios from
ETOPS entry and exit points to an ETOPS alternate
occurs only when there is a single alternate associated
with the ETOPS segment.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 3-2 Basic Flight Planner ETOPS II Alternates (ETOPS ALTS) Options (continued)

Option Explanation
AP=1<xxx> AP (APU Flag). For ETOPS II, you can specify a
where <xxx> are codes for the APU Flag value for the APU Flag in the 04 ETOP ALTS box.
The code you specify overrides the value of the (AP)
Auxiliary Power Unit Flag parameter in the Customer
Aircraft database. This option enables you to account
for special situations without having to change the
Customer Aircraft database record. For example,
because of a MEL, you might need to operate the
APU from takeoff to landing for a given flight.
The value of AP begins with 1 and is followed by a
combination of upper or lower case C, E, and D,
where:
• C – Calculates the APU fuel burn for the all-
engines depressurized scenario.
• E – Calculates the APU fuel burn for the one-less
engine depressurized scenario.
• D – Calculates the APU fuel burn for the one-
less engine pressurized scenario.
For example: AP=1CED, AP=1CE, AP=1ED, and
AP=1DC
For more information, see “Setting Up the Customer
Aircraft Database for ETOPS II” on page 19 and
Chapter 6, “APU Fuel Burn.”
NOTE Do not set this flag if the APU fuel burn is built
into the engine-out performance data to avoid double-
booking APU fuel in the critical fuel scenarios. If you
are not sure if the performance data includes the APU
fuel burn value, consult with your Jeppesen
Implementation Specialist or customer support
representative.

scmt=<SCM Set Deviation Time>,scmn= ETOPS II SCM Set. For ETOPS II, you can specify
<SCM Set Deviation Mode Title> an SCM dataset for use in the flight plan computation.
If none is specified, JetPlan uses the default SCM
dataset in the Customer Aircraft Fleet database
record. To specify a different SCM dataset, include
the SCM Set Deviation Time (scmt=), followed by the
SCM Set Deviation Mode Title (scmn=). Add the
parameters after the last alternate (and icing
percentage if applicable), separated from the last
alternate by a comma. For example:
CYQX/BIKF,40,scmt=180,scmn=180/320
In this example, the SCM Set corresponds to SCM
dataset #2 in the Customer Aircraft Fleet database
record.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 3-2 Basic Flight Planner ETOPS II Alternates (ETOPS ALTS) Options (continued)

Option Explanation
ST= APU Situation Code input. For ETOPS II, you can
or specify an APU Situation Code in the 04 ETOP ALTS
box. The Situation Code you specify overrides the
ST=<APU Situation Code>
value of the Situation Code parameter in the Customer
Aircraft database. This option enables you to account
for special situations without having to change the
Customer Aircraft database record. For example, you
might need to operate the APU during specific
intervals, such as from takeoff to landing, from
takeoff to exiting the ETOPS Area of Operations
(AOO), or from entering the ETOPS AOO to exiting
the AOO. You can also choose to exclude the APU
burn calculation completely.
The options for setting the Situation Code in the flight
plan request are as follows:
• ST=X – Calculate the APU fuel burn from the
POD to the last ETOPS exit point.
• ST=W – Calculate the APU fuel burn from the
POD to the POA.
• ST=E – Calculate the APU fuel burn for ETOPS
segments only.
• ST= (blank) – Do not calculate the APU fuel
burn.
The following example illustrates the use of the
Situation Code in an 04 ETOPS ALTS entry:
CYQX/BIKF,40,scmt=180,scmn=180/320,ST=X/CY
QX,,50/BIKF,20,
20/EINN,10,
The following example illustrates the use of the
Situation Code set to blank (no APU fuel burn
calculated):
EINN,,/CYJT,ST=,AP=1CDE
For more information on APU Situation Codes see
“Setting Up the Customer Aircraft Database for
ETOPS II” on page 19 and Chapter 6, “APU Fuel
Burn.”

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 3-2 Basic Flight Planner ETOPS II Alternates (ETOPS ALTS) Options (continued)

Option Explanation
Adequate Airports

AA=<airport code> Enables you to submit a list of up to five airports as

additions to those designated as adequate in the
Customer Airport Fleet database.
NOTE You can also subtract an airport. When you
submit an airport as both an addition and a subtraction,
the subtraction takes precedence, and JetPlan
excludes the airport from the ETOPS entry and exit
point computations.
NOTE JetPlan does not automatically consider the
POD and POA as adequate ETOPS airports. The
same rules that apply to designating any airport as an
ETOPS adequate airport apply to the POD and the
POA.

AS=<airport code> Enables you to submit a list of up to five airports as

subtractions from those designated as adequate in the
Customer Airport Fleet database.
NOTE You can also add an airport. When you submit
an airport as both an addition and a subtraction, the
subtraction takes precedence, and JetPlan excludes
the airport from the ETOPS entry and exit point
computations.

AR=<airport code> NOTE Additions to or subtractions from adequate

airports in the Customer Airport Fleet database can
result in a set of airports that does not overlap the
route, creating no ETOPS entry or exit points. In this
case, the ETOPS entry point is located at the POD,
and the ETOPS exit point is located at the POA.
This option enables you to submit a list of up to ten
airports as replacements for those designated as
adequate in the Customer Airport Fleet database.
When you specify the replacement list, JetPlan
computes the ETOPS entry and exit points based
solely on this list. Airports in the Customer Airport
Fleet database or specified with the AS or AA option
are ignored.
When you do not specify an adequate list, JetPlan
computes the ETOPS entry and exit points based on
the set of adequate airports by doing the following:
• Including airports marked adequate in the
Customer Airport Fleet database
• Including airports submitted as additions (with
the AA option)
• Excluding airports submitted as substitutions
(with the AS options)

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 3-2 Basic Flight Planner ETOPS II Alternates (ETOPS ALTS) Options (continued)

Option Explanation
Reclear

<airport code>/<airport code>*/<airport code> Enables you to exclude an ETOPS alternate from
ETOPS operations for the plan to the reclear POA. In
the 04 ETOPS ALTS entry, type an asterisk (*) to the
right of the code for the ETOPS alternate you want to
exclude. For example:
kden/ksfo*/ksjc

April 11, 2018 ETOPS II Startup Guide v. 1.4

ETOPS II Flight Plan Input Examples

The following examples illustrate some uses of the ETOPS II options.

Basic ETOPS II Option

01 OPTIONS FP,FLE, ETOPN,AW
02 POD KDEN
03 POA PHNL
04 ETOPS ALTS KSFO/PHOG

Basic ETOPS II Option with Diagnostics

01 OPTIONS FP,FLE, ETOPNL,AW
02 POD KDEN
03 POA PHNL
04 ETOPS ALTS KSFO/PHOG

Extended ETOPS II Option

01 OPTIONS FP,FLE, ETOPXN,AW
02 POD KDEN
03 POA PHNL
04 ETOPS ALTS KSFO/PHOG

Extended ETOPS II Option with Diagnostics

01 OPTIONS FP,FLE, ETOPXNL,AW
02 POD KDEN
03 POA PHNL
04 ETOPS ALTS KSFO/PHOG

Extended ETOPS II Option with Reclear

01 OPTIONS FP,FLE, ETOPXN,RC,AW
02 POD KDEN
03 POA PHNL
04 ETOPS ALTS KSFO/PHOG

Extended ETOPS II Option, One ETOPS Alternate

01 OPTIONS FP,FLE, ETOPXN,AW
02 POD PANC
03 POA RJAA
04 ETOPS ALTS UHPP

ETOPS II Startup Guide v. 1.4 April 11, 2018

ETOPS II Option, Two ETOPS Alternates with Icing % Input

01 OPTIONS FP,FLE, ETOPN,AW
02 POD EWR
03 POA EGLL
04 ETOPS ALTS CYQX,,70/EINN,40
In this example:
• 70 -icing percentage for the diversion from the ETP
to CYQX
• 40-icing percentage for the diversion from ETP to
EINN

ETOPS II Option, Three ETOPS Alternates with Icing % Input

01 OPTIONS FP,FLE, ETOPN,AW
02 POD EWR
03 POA EGLL
04 ETOPS ALTS CYQX,,70/BIKF,40,30/EINN,60
In this example:
• 70 -icing percentage for the diversion from the ETP1 to
CYQX
• 40-icing percentage for the diversion from ETP1 to BIKF
• 30-icing percentage for the diversion from ETP2 to BIKF
• 60-icing percentage for the diversion from ETP2 to EINN

ETOPS II Option, Single Alternate with Icing % Input

01 OPTIONS FP,FLE, ETOPXN,AW
02 POD PANC
03 POA RJAA
04 ETOPS ALTS UHPP,,70
In this example:
• 100 default icing percentage for the diversion from
the ETOPS entry point to UHPP
• 70-icing percentage for the diversion from ETOPS
exit point to UHPP

April 11, 2018 ETOPS II Startup Guide v. 1.4

Multi-Segment ETOPS

This chapter includes the following sections:

• About Multi-Segment ETOPS

• About the Multi-Segment ETOPS Calculation
• About the Multi-Segment ETOPS Flight Plan Output
Multi-Segment ETOPS
About Multi-Segment ETOPS

About Multi-Segment ETOPS

Two types of ETOPS segments are possible: single-segment and multi-segment. In a single-
segment ETOPS flight plan, JetPlan uses only the first EEP and the last EXP and considers the
route between these points as one, single ETOPS segment. The EEP is closest to the POD, and
the EXP is closest to the POA. For example, on a flight over the North Pacific from South Asia
to Memphis, JetPlan locates the entry and exit points of the ETOPS segment near Japan and
near Alaska. JetPlan ignores adequate airports in between these points. The missing
intermediate non-ETOPS segment or segments forces operators to plan additional suitable
ETOPS alternates that are not needed in all circumstances, such as for cargo flights.

In Multi-Segment ETOPS flight plan calculations, JetPlan automatically determines all the
ETOPS segments that exist for user-specified ETOPS airports. To activate Multi-Segment
ETOPS, define the Minimum Distance Between ETOPS Segments parameter and the ETOPS
alternates maximum distance factor in the Flight Brief database (see “Setting Up the Flight
Brief Database for ETOPS II” on page 54).

JetPlan treats consecutive ETOPS segments that are beyond a configurable distance from one
another as two separate ETOPS segments, as opposed to combining them. If the distance
between any two ETOPS segments is greater than the value of the Minimum Distance
Between ETOPS Segments parameter, the system considers the segments as separate. If the
distance between the ETOPS segments in equal to or less than Minimum Distance Between
ETOPS Segments parameter, JetPlan the considers the two ETOPS segments and the route
between them as one ETOPS segment. When the Minimum Distance Between ETOPS
Segments value is set to 9999 (the default), then all ETOPS segments are combined into one.

JetPlan determines which ETPs and alternates to include and which to omit based on a
configurable distance between the abeam points of the forward and backward alternates. For
each pair of ETOPS alternates, JetPlan determines their relative nearness to one another using
the value of the ETOPS Alternates Maximum Distance Factor. JetPlan calculates the distance
between the backward and forward alternates as the great circle (not route) distance between
the route point abeam of the backward alternate and the route point abeam of the forward
alternate. For each ETOPS alternate pair that is closer together than the ETOPS Alternates
Maximum Distance Factor, JetPlan computes the ETP associated critical fuel, and early and
late arrival times The system also includes these ETPs in the ETP summary output on the
flight plan and as waypoints in the navigation log.

JetPlan omits any ETP if its associated alternates are farther apart than the ETOPS alternates
maximum distance factor unless they occur in an ETOPS segment. The omitted ETPs are not
considered as a critical points but are reported in the ETOPS diagnostic part of the flight plan.
JetPlan also excludes any alternate that has no critical points associated with it. JetPlan
excludes these alternates from the set of ETOPS alternates and, subsequently, from critical
fuel and suitability calculations. For each excluded alternate, JetPlan produces an alert.

April 11, 2018 ETOPS II Startup Guide v. 1.4

About the Multi-Segment ETOPS

Calculation
The following paragraphs describe how JetPlan calculates a plan with multiple ETOPS
segments based on Flight Brief database settings. Figure 4.1 shows a sample route from FMMI
to LFPO with ETOPS alternates FMMI and HECA and several adequate airports.

Figure 4.1. Sample route from FMMI to LFPO

ETOPS II Startup Guide v. 1.4 April 11, 2018

Figure 4.2 illustrates the single-segment ETOPS approach to this calculation. The flight
planner must select another suitable alternate to provide coverage over the entire orange
segment because a portion of the route is outside the selected ETOPS alternate range radius
rings (big circles).

Figure 4.2. Single-Segment ETOPS

April 11, 2018 ETOPS II Startup Guide v. 1.4

Figure 4.3 illustrates ETOPS segment determination using the Multi-Segment ETOPS settings
in the Flight Brief database. If the matching Flight Brief record is set to combine ETOPS
Segments less than 2075 NM apart, then JetPlan treats the two segments separately.
Otherwise they are considered one segment (including all the route in between).

Figure 4.3. Determining ETOPS Segments Using Flight Brief Database Settings

ETOPS II Startup Guide v. 1.4 April 11, 2018

Figure 4.4 illustrates how JetPlan associates EEPs and EXPs with alternates. If the Flight Brief
database record is set to combine ETOPS segments less than 2075 NM apart, then the EEP and
EXP occurring prior to the ETP are associated with the backward alternate for Suitability
Time Evaluation. Those occurring after the ETP are associated with the forward alternate. If
the ETP is omitted from the report, then Critical Fuel calculations are also based on the EEPs
and EXPs.

Figure 4.4. Associating EEPs and EXPs with Alternates

April 11, 2018 ETOPS II Startup Guide v. 1.4

Figure 4.5 illustrates how JetPlan determines whether or not to exclude an ETP. If the ETP
falls within an ETOPS segment, and/or the distance between the points abeam of the alternates
is less than the Max Distance Between Alternates in the Flight Brief database, then the ETP is
used for Critical Fuel and Suitability Times calculations. Otherwise, the ETP is excluded for
those purposes. In this example the ETP is not within an ETOPS segment and the airports are
far apart, so the ETP is not reported on the flight plan, used for suitability calculations, or used
for critical fuel calculation.

Figure 4.5. Determining Whether to Report an ETP

The final result of the calculation is as follows:

• For alternate FMMI, critical fuel and suitability calculations are made from
EEP1 and EXP1.
• For alternate HECA, critical fuel and suitability calculations are made from
EEP2 and EXP2.
• The ETP is omitted from reporting on the flight plan.
• Both ETOPS segments are within the approved coverage circle of the
alternates, so no coverage alert is issued.

ETOPS II Startup Guide v. 1.4 April 11, 2018

About the Multi-Segment ETOPS Flight

Plan Output
When the Flight Brief database is configured to support Multi-Segment ETOPS, JetPlan
includes the Multi-Segment Diagnostic section in the flight plan output. For a detailed
example, see “Multi-ETOPS Segments Output in Detail” on page 122.

April 11, 2018 ETOPS II Startup Guide v. 1.4

ETOPS II for EU-OPS

Business Aviation
Operators

This chapter includes the following sections:

• About Modifying ETOPS II for European Business Aviation Rules

• Modifying the Icing Penalty
• Modifying the Wind Bias and Conservatism Calculation
• Adding Missed Approach Fuel
ETOPS II for EU-OPS Business Aviation Operators
About Modifying ETOPS II for European Business Aviation Rules

About Modifying ETOPS II for European

Business Aviation Rules
The default behavior of ETOPS II meets the needs of airlines certified under FAA 121.646
ETOPS rules. JetPlan also provides the option to change the default behavior to comply with
JAR-OPS 1.245 rules specific to European Business Aviation customers with aircraft having
19 or fewer seats, operating weight below 45360kg, and certified to operate above FL450.
Using customer database settings, you can change the JetPlan default calculation of the
following quantities to comply with JAR-OPS 1.245:

• Icing penalties
• Wind bias and conservatism
• Missed approach fuel

The following sections describe how to use customer database settings to comply with JAR-
OPS 1.245.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Copyright © 2018 Jeppesen. All rights reserved.
89
ETOPS II for EU-OPS Business Aviation Operators
Modifying the Icing Penalty

Modifying the Icing Penalty

The default ETOPS II icing penalty calculation uses the 10 percent comparison of ice-
accumulation to anti-ice as specified in FAA 121.646. You can use a setting in the Flight Brief
database to change the icing penalty calculation to a Temperature-Based icing penalty
calculation. Create an E (EU-ETOPS) type Flight Brief record and set the Temp-Based Icing
Penalty parameter to On. For more information on ETOPS parameters in the Flight Brief
database, see “Setting Up the Flight Brief Database for ETOPS II” on page 54. For specific
procedures on creating or modifying a Flight Brief record, see the Help file for the Flight Brief
database on [Link].

When the Temp-Based Icing Penalty in the Flight Brief database is set to On, the icing
penalties are calculated using the following parameters in the Customer Aircraft database:

• Icing Temperature (IT)

• Anti-Ice Flag (AI)
• Anti-Ice Factor—You can separately set three factors for each of the ETOPS
scenarios: Depressurized Engine Out, Depressurized All Engine, and
Pressurized Engine Out. The anti-ice factors are AI LRC FAC (AL), AI
LRC FAC (AE), and AI P1LE FAC (AEP), respectively.
• Ice Drag Flag (ID)
• Ice Drag Factor—You can separately set three factors for each of the
ETOPS scenarios. The ice drag factors are IDRAG LRC FAC (IL), IDRAG
1LE FAC (IE), and IDRAG P1LE FAC (IEP) respectively.

The icing penalty calculation for each scenario is controlled by the following letters that can
be included in the Anti-Ice Flag (AI) or Ice Drag Flag (ID):

• Letter C in AI or ID causes the penalty to be calculated for the

Depressurized All-Engine scenario.
• Letter E in AI or ID causes the penalty to be calculated for the
Depressurized Engine-Out scenario.
• Letter D in AI or ID causes the penalty to be calculated for the Pressurized
Engine-Out (Driftdown) scenario
• Letter I in AI or ID causes the penalty to be calculated for each scenario (if
ID or AI has CED) when the temperature along the diversion is less than or
equal to the value of IT.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Copyright © 2018 Jeppesen. All rights reserved.
90
ETOPS II for EU-OPS Business Aviation Operators
Modifying the Icing Penalty

• Letter N in AI or ID causes the penalty to be calculated for each scenario (if

ID or AI has CED) when the temperature along the diversion is greater than
the value of IT.
• If letter N and letter I are not used, the penalty is calculated for each scenario
(if ID or AI has CED), regardless of the temperature.

For more information on ETOPS parameters in the Customer Aircraft database, see “Setting
Up the Customer Aircraft Database for ETOPS II” on page 19. For specific procedures on
creating or modifying a Customer Aircraft record, see the Help file for the Customer Aircraft
database on [Link].

April 11, 2018 ETOPS II Startup Guide v. 1.4

Copyright © 2018 Jeppesen. All rights reserved.
91
ETOPS II for EU-OPS Business Aviation Operators
Modifying the Wind Bias and Conservatism Calculation

Modifying the Wind Bias and

Conservatism Calculation
The default ETOPS II wind bias calculation applies a 5% wind bias as specified in
FAA 121.646. You can turn off the wind bias calculation using a setting in the Flight Brief
database.

Without an active Flight Brief database record, the 5% wind bias defaults to On. To exclude
the 5% wind bias in the ETOPS II calculations, create an E (EU-ETOPS) type Flight Brief
record and set the 5% Wind Bias parameter to Off to turn off the wind bias calculation. For
more information on ETOPS parameters in the Flight Brief database, see “Setting Up the
Flight Brief Database for ETOPS II” on page 54. For specific procedures on creating or
modifying a Flight Brief record, see the Help file for the Flight Brief database on [Link].

ETOPS II Startup Guide v. 1.4 April 11, 2018

Copyright © 2018 Jeppesen. All rights reserved.
92
ETOPS II for EU-OPS Business Aviation Operators
Adding Missed Approach Fuel

Adding Missed Approach Fuel

You can optionally include missed approach fuel in the uplift for each diversion by setting the
Missed Approach Flag (ML) and the Missed Approach Burn (MB) parameters in the
Customer Aircraft database as follows:

• Set the ML parameter to On (1) to include missed approach fuel.

• Set the MB parameter to the amount of missed approach fuel you want
JetPlan to include

NOTE In the FLE format, ETOPS II extended output includes the missed approach
fuel in the MAP row of the extended output.

April 11, 2018 ETOPS II Startup Guide v. 1.4

APU Fuel Burn

This chapter includes the following section:

• About APU Situation Codes and APU Fuel Burn

APU Fuel Burn
About APU Situation Codes and APU Fuel Burn

About APU Situation Codes and APU Fuel

Burn
ETOPS rules require at least three independent sources of AC power for an airplane to be
ETOPS Type Design Approved. This can be accomplished by a variety of configurations,
including Auxiliary Power Units (APUs), more than one generator per engine, Hydraulic
Motor Generators, and Ram Air Turbines (A320), to name a few.

The JetPlan APU parameters in the Customer Aircraft database provide control over planning
APU fuel for ETOPS flights, both for the primary mission and for each diversion. ETOPS
regulations require the operator to comply with manufacturer instructions for APU use. The
aircraft manufacturer details the APU fuel burn scenario in which the APU must run. This
information is included in the Flight Manuals provided to the operator.

You can set the fuel burn scenario for an aircraft by setting the Situation Code (ST) in the
Customer Aircraft database. See Table 6-1 for the Situation Code settings and the calculation
performed for each setting. In addition, the following APU-related parameters can be set in the
Customer Aircraft database:

• (BR) APU Burn Rate

• (AP) Auxiliary Power Unit Flag
• (AU) Auxiliary Power Unit Burn
• (AZ) Unloaded Depressurized APU Burn
• (AY) Loaded Driftdown APU Burn

See “Setting Up the Customer Aircraft Database for ETOPS II” on page 19 for more
information about these parameters.

April 11, 2018 ETOPS II Startup Guide v. 1.4

You can set the fuel burn scenario for an aircraft by setting the Situation Code (ST) in the
Customer Aircraft database. Table 6-1 includes revised logic for ETOPS II regarding the
calculations associated with the Situation Codes.

Table 6-1 APU Situation Code Calculations

Situation Code Calculation

Situation Code = W APU Fuel Amount for ST=W APU fuel is equal to the flight time from takeoff to
landing at the POA, multiplied by the APU Burn
rate (BR).
Example: If flight duration is 5hrs 53min, and BR =
100 lbs/hr, then APU Fuel is 588lbs.

APU Burn for ST=W APU fuel is planned to be burned at the APU Burn
rate (BR) starting at takeoff and so that the last of the
APU fuel is burned on the segment arriving at the
POA.
Note: The segment burn for every segment
effectively has an additional lbs/time fuel flow bias
equal to the BR parameter.

Situation Code = E APU Fuel Amount for ST=E APU fuel is equal to the flight time from ETOPS
Entry to ETOPS Exit multiplied by the APU Burn
rate (BR).
Example: If the EEP occurs at 0128 into flight, and
the EXP occurs at 0421 into flight, then flight time
between the two is 0253. If BR = 100, then APU
Fuel is 288lbs.

APU Burn for ST=E APU fuel is planned to be carried unburned to the
ETOPS Entry Point, and then burned at the APU
Burn rate (BR), starting at the ETOPS Entry Point
and so that the last of the APU Fuel is burned on the
segment arriving at the ETOPS Exit Point.
Note: The segment burn for every segment, starting
at the EEP and ending at the EXP, effectively has an
additional lbs/hr fuel flow bias equal to the BR
parameter.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 6-1 APU Situation Code Calculations

Situation Code Calculation

Situation Code = X APU Fuel Amount for ST=X APU Fuel is equal to the flight time from takeoff to
the ETOPS Exit Point, multiplied by the APU Burn
rate (BR).
Example: If the time from takeoff to the EXP is
03+53, and BR = 100 lbs./hr., then APU Fuel is 388
lbs.

APU Burn for ST=X APU Fuel is planned to be burned at the APU Burn
rate (BR), starting at takeoff and so that the last of
the APU Fuel is burned on the segment arriving at
the ETOPS Exit Point.
Note: The segment burn for every segment, starting
at takeoff and ending at EXP, will effectively have
an additional lbs/hr fuel flow bias equal to the BR
parameter.

Situation Code = N APU Fuel Amount for ST=N Using the Situation Code N directs the system to
(None) ignore the Situation Code parameter and compute
the flight as if the Situation Code parameter is set to
None.

NOTES:
• The weight of APU Fuel is included in takeoff weight.
• Additional trip fuel is included to account for the “cost to carry” the APU fuel.
• APU Fuel is not offset by ETOPS ADD.
• When ST is set to a value other than “off” (such as not 0 [zero]), and BR is greater than zero, then APU
Fuel is never zero.
• APU Fuel is accounted for separately from EXTRA in the fuel block.
• APU Fuel remaining at the critical points is part of the Fuel on Board and is considered burnable in the
ETOPS critical fuel calculations.
• APU Fuel is excluded from the planned landing weight. Note that the landing weight derived from the sum
of the aircraft operating weight + payload + fuel remaining as shown in the flight plan body is equal to the
landing weight listed in the flight plan summary. Fuel remaining at the POA includes reserves,
contingencies, ETOPS ADD, and EXTRA, but not APU Fuel.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Understanding ETOPS II
Flight Plan Output

This chapter includes the following sections:

• About the ETOPS II Flight Plan Output

• Customer Database Settings and Flight Plan Options for the Sample Output
• ETOPS II Sample Flight Plan Output (Excerpts)
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

About the ETOPS II Flight Plan Output

This chapter includes excerpts from sample ETOPS II flight plan output in the FLE flight plan
format. Your flight plan output might differ somewhat, depending on your specific
configuration and customizations.

The following sections include the following information:

• The customer database settings and flight plan options for the sample flight
plan
• Excerpts from the resulting sample flight plan, including ETOPS output
• Guidelines for interpreting the ETOPS output

NOTE To view the full sample ETOPS II flight plan excerpted below, see
Appendix A, “Full Sample ETOPS II Flight Plan Output.”

April 11, 2018 ETOPS II Startup Guide v. 1.4

Copyright © 2018 Jeppesen. All rights reserved.
103
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

Customer Database Settings and Flight Plan Options

for the Sample Output
All ETOPS parameter settings have the potential to affect flight plan output. Settings from the
Customer Aircraft, Aircraft Fleet, and Flight Brief databases are included here as aids to
understanding the sample output in this section.

Figure 7.1 shows the Customer Aircraft database ETOPS parameter settings in effect on the
system used to run the sample flight.

-- ETOPS Sample Customer

ED USE ETOPS Y Aircraft database
CS CRZ MODE BEG 1 CE CRZ MODE END 3 ETOPS Settings
ET ETOP APPR TIME 180 MIN IT ICING TEMP -6
ID ICE DRAG FLAG 1CED AI ANTI-ICE FLAG 5CED • When JetPlan computes
IL IDRAG LRC FAC P400CDH AL AI LRC FAC P500CDH Time Limited Systems
IE IDRAG 1LE FAC P700CDH AE AI 1LE FAC P100CDH (TLS), it includes the
IEP IDRAG P1LE FAC P700CDH AEP AI P1LE FAC P100CDH FS and OS values in the
CF CONSERV. FLAG 2CE TV CONSERV. TIME 000 calculation. The result
CV CONSERV. FAC P500CDH TR TIME [Link] is output in the flight
CZ CRUISE FLAG 1D20 ML MAP FLAG 1 plan.
CD CRUISE DIST MB MAP BURN 1200 LBS
AP APU FLAG 1CED HL HOLD FLAG 1 • The (ET) ETOPS
AU APU BURN 320CDH HB HOLD TIME 0015 MIN Approval Time
AZ APU UNLOAD DEP 270CDH IS ISA FLAG parameter is used with
AY APU LOADED DD 290CDH IB ISA BURN legacy ETOPS only.
ES1 EARLY ARV TAS 420 KTS ES2 LATE ARV TAS 340 KTS This value is inert in
ESA1 EARLY ARV FLV 100 ESA2 LATE ARV FLV 100 ETOPS II flight plan
FS FIRE SUPP LIM 240 MIN OS OTHER SSTM LIM 240 MIN calculations.
DV DIVERT FLAG 1CDH PF PF BIASES FLAG 1

Figure 7.1. Customer Aircraft Database – Sample ETOPS Settings

ETOPS II Startup Guide v. 1.4 April 11, 2018

Copyright © 2018 Jeppesen. All rights reserved.
104
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

Figure 7.2 shows the SCM dataset settings in the Customer Aircraft Fleet database in effect on
the system producing the sample output.

Figure 7.2. Customer Aircraft Fleet Database – Sample SCM Dataset Settings

April 11, 2018 ETOPS II Startup Guide v. 1.4

Copyright © 2018 Jeppesen. All rights reserved.
105
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

Figure 7.3 shows sample ETOPS II settings in the Flight Brief database in effect on the system
producing the sample output.

EARLY-BUFFER TIME: 0 Sample Flight Brief Fleet Database

LATE-BUFFER TIME: 60 Settings
PBN FLAG:
PBN TEXT:
• The Early and Late Buffer times are
STS TEXT: used in the Suitable Times calculations
OTHER STS TEXT: in plans for the ER77 fleet.
ORGN TEXT: • The Scenario Options determine which
WIND BIAS: Y critical fuel scenarios are computed and
TEMPERATURE-BASED ICING PENALTIES: N used in the ETOPS uplift calculations
ETOPS UPLIFT AND OUTPUT FLAG FOR D1LE: 1
and which are displayed in the extended
ETOPS UPLIFT AND OUTPUT FLAG FOR DLRC: 1
ETOPS UPLIFT AND OUTPUT FLAG FOR P1LE: 1
output block on the flight plan.
OUTPUT FLIGHT NUMBER FLAG: N • The Temperature-Based Icing Penalties
AEFP FLAG: N parameter controls application of
POLITICAL BOUNDARY REPORT FLAG: N temperature-based icing.
FIR/UIR BOUNDARY REPORT FLAG: N
MINIMUM DISTANCE BETWN ETOPS SEGMENTS:
• The Minimum Distance Between
ETOPS ALTERNATES MAXIMUM DISTANCE FACTOR: ETOPS Segments and ETOPS
FLIGHT BRIEF TEXT: Alternates Maximum Distance Factor
LATE BUFFER TIME SET TO 60 are used in the Multi-Segment ETOPS
calculations.

Figure 7.3. Flight Brief Database - Sample ETOPS Settings

Figure 7.4 shows the flight plan options for the sample ETOPS II flight plan output illustrated
in this chapter. For information on the ETOPS options in this sample, see Chapter 3, “Running
ETOPS II Flight Plans.”

01 OPTIONS fp,fle,etopxnl,wh07,aw,-e,cs/jdtest,cpt/w david,dsp/j hanna

02 POD kjfk
03 POA egll
04 ETOPS cyqx,,100/einn,100
06 ROUTE j
07 HOLD,ALTERNATE/DIST 30,eham
08 ETD 2200
09 PROFILE i
10 A/C TYPE/REGN $er77test
11 CRZ MODE m84
14 PAYLOAD 85000
16 POD OR POA FUEL a0,i
20 COMPUTING 2665

Figure 7.4. Sample Flight Plan Options

ETOPS II Startup Guide v. 1.4 April 11, 2018

Copyright © 2018 Jeppesen. All rights reserved.
106
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

ETOPS II Sample Flight Plan Output (Excerpts)

This section explains ETOPS II-related excerpts from sample EOTPS II flight plan output. All
examples refer to the FLE format.

NOTE ETOPS II output is supported in many formats. The example below is typical
but may not match your specific format. For more information, contact your Jeppesen
Implementation Specialist or Customer Service Representative.

NOTE To view the full sample ETOPS II flight plan excerpted below, see
Appendix A, “Full Sample ETOPS II Flight Plan Output.”

ETOPS Approval Time Line

Figure 7.5 shows the ETOPS Approval Time lines. JetPlan uses the ETOPS
SPEED/[Link] SET DEV TIME (SD#) from the SCM set to compute the ETOPS flight
plan. The inclusion of the approval time line output is format-dependent.

///// THIS FLIGHT PLAN COMPLIES WITH THE 180 MIN ETOPS RULE /////

PLAN 2665 11292216Z FOR ETD 2200Z

FLT REL IFR JDTEST /30 KJFK/JFK TO EGLL/LHR MACH: M84 REGN NTEST
PROGS JUL ELEV 0013FT 0083FT AVG W/C P042 ISA DEV P08
COMP 2216Z FOR ETD 2200Z/30NOV17 REGN NTEST TRENT892 LBS

SUBJECT TO THE FOLLOWING CONDITIONS

ETOPS FLIGHT/MAX DIVERSION TIME IN STILL AIR LIMITED TO 180 MINUTES
FROM THE FOLLOWING ETOPS ALTERNATE AIRPORTS - CYQX/YQX
EINN/SNN

Figure 7.5. ETOPS Approval Time Line

April 11, 2018 ETOPS II Startup Guide v. 1.4

Copyright © 2018 Jeppesen. All rights reserved.
107
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

Fuel Block
Figure 7.6 illustrates the Fuel Block area of the flight plan. JetPlan includes an ETOPS ADD
line that shows excess or deficit fuel and time for the ETOPS flight plan.

FUEL TIME CORR OWE 325100 PYLD 85000 APLD .. .. ..

DEST EGLL 90006 05+57 . . . . EZFW 410100 MZFW 430000 AZFW .. .. ..
RESV 8200 00+36 . . . . ETOW 524281 MTOW 648000 ATOW .. .. ..
DEST-MNVR 0 00+00 . . . . ELDW 434275 MLDW 460000 ALDW .. .. ..
ALTERNATE 10199 00+41 . . . . EHAM FL290 0222 NM M.72 W/C P028
HOLD-ALT 5776 00+30 . . . .
ETOPS ADD 0 00+00
REQD 114181 07+44 . . . . NOTE - LDGWT INCLUDES RESERVE FUEL
EXTRA 000000 00+00 . . . . NOTE - APM 0000 PCN
TAXI 2000 SCHEDULE TIMES ETD 2200/.. .. .. ..
TOTAL 116181 07+44 . . . . RTE ETA 0357/.. .. .. ..

INCREMENTAL BURN PER 1000 LBS INCREASE/DECREASE IN TOW: 163

ATC CLRNC:.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..

-N0489F370 DCT MERIT DCT HFD J42 BOS J575 YQY DCT JOOPY/M084F370
DCT 49N050W/M084F370 51N040W 52N030W 52N020W/M084F370 DCT
LIMRI/N0491F370 DCT XETBO DCT VAPAL DCT EVRIN UL607 NUMPO UP2
BEDEK

FL 370

Figure 7.6. Fuel Block ETOPS Additional Fuel Entry

Suitable Airports Times

Figure 7.7 illustrates the Suitable Airport Times area of the flight plan. Because rules differ
between authorities, being able to modify parameters used to determine early and late arrival
time is important. You can store early and late buffer times in the Flight Brief database.
JetPlan then uses these defined buffer times in the calculations that determine suitable early
and late arrival times. By setting the values appropriately, you can meet EU ETOPS
requirements and those of other authorities if they differ. See “Setting Up the Flight Brief
Database for ETOPS II” on page 54 for more information on setting the early and late buffer
times and how JetPlan uses those times in the calculations.

ENROUTE ALTN:
CYQX/YQX VALIDITY PERIOD FROM 0158 UTC / TO 0500 UTC
EINN/SNN VALIDITY PERIOD FROM 0320 UTC / TO 0458 UTC

Figure 7.7. Suitable Airports

ETOPS II Startup Guide v. 1.4 April 11, 2018

Copyright © 2018 Jeppesen. All rights reserved.
108
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

Critical Fuel Summary

Figure 7.8 illustrates the Most Critical Fuel Scenario line in the output. The most critical fuel
scenario is that for which the difference between the fuel on board and the critical fuel
required is lowest. To summarize the ETOPS critical fuel calculation results, the system
provides the following information:

• The Equal Time Point (ETP), Critical Point, entry point (EEP), or exit point
(EXP) at which the most critical fuel scenario occurs
• Excess fuel, if any
The fuel quantities are reported in the units used in the flight plan computation— kilograms or
pounds.

MOST CRITICAL FUEL SCENARIO AT : ETP01 FUEL EXCESS OF 11100

Figure 7.8. Critical Fuel Summary

Equal Time Point Summary

Figure 7.9 is an illustration of the Equal Time Point Summary in the flight plan output.

1 2/3 4/5 6/7 8 9 10 11 / 12

TIME TO
DIST W/C CFR FOB EXC ETP / ALT
ETP1 CYQX/EINN 0819/0910 M023/P017 044423 055523 11100 03+25/02+22
N5145.0 W03339.0

Figure 7.9. Entry, Exit, and Equal Time Points

April 11, 2018 ETOPS II Startup Guide v. 1.4

Copyright © 2018 Jeppesen. All rights reserved.
109
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

Key to the Equal Time Point Summary columns:

1 – Identifies the critical point identifier (ETP1).

2 – Identifies the backward alternate (CYQX). If no backward alternate
exists, this item is blank.
3 – Identifies the forward alternate (EINN). If no forward alternate exists,
this item is blank.
4 – Displays the great circle distance (DIST) from the ETP (or EEP if there
is a single alternate) to the backward alternate. Note that the cruise distance
value is excluded.
5 – Displays the great circle distance (DIST) from the ETP (or EXP if there
is a single alternate) to the forward alternate. Note that the cruise distance
value is excluded.
6 – Displays the wind component (W/C) to the backward alternate, with 5%
bias applied.
7 – Displays the wind component (W/C) to the forward alternate, with 5%
bias applied.
8 Displays the Critical Fuel Required (CFR)–—for example, the highest
CFR from among the three backward and three forward scenarios.
9 – Displays the Fuel on Board (FOB) at the critical point.
10 – Displays the excess fuel (EXC) at the critical point.
11 – Displays the time enroute from POD to the critical point (TIME TO
ETP). This value is the amount of time it takes to get to the ETP, not the
time of arrival at the ETP. For example, if a flight departs at 1200, and it
takes 3 hrs 0 min to arrive at the ETP, this time will be 3+00, not 1500.
12 – Displays the time of flight from the critical point—including the ETP
labeled as the critical ETP—to the alternate (TIME TO ALT). This value
equals the cruise time plus the descent time.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Copyright © 2018 Jeppesen. All rights reserved.
110
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

Time Limited Systems Compliance Summary

Figure 7.10 shows the Time Limited System (TLS) Compliance Summary, which is output
when the Calculate TLS parameter in the Customer Aircraft Fleet database is set to Yes. The
TLS calculations use the following parameters:

• TLS Fire parameters in the SCM Dataset section of the Customer Aircraft
Fleet database
• The Cargo Fire Suppression Time Limit (FS) and Other Most Time-
Limiting System Limit (OS) parameters in the Customer Aircraft database

TIME LIMITED SYSTEM COMPLIANCE SUMMARY

LONGEST ALL-ENGINE DIVERSION TIME IS 121 MINUTES FROM ETP1

CARGO FIRE SUPPRESSION CAPACITY MINUS 15 MIN IS 225 MINUTES
LONGEST ONE-ENGINE-OUT DRIFTDOWN DIVERSION TIME IS 0135 MINUTES FROM ETP1
OTHER MOST TIME LIMITING SYSTEM TIME CAPACITY MINUS 15 MIN IS 225 MINUTES

Figure 7.10. Time Limited System Compliance Summary

Key to the Time Limited System Compliance Summary output:

• Line 1 states the longest diversion time in minutes in the Pressurized All-
Engine scenario. The time is rounded to the nearest minute.
• Line 2 states the Cargo Fire Suppression Time Limit (FS) value in the
Customer Aircraft database minus 15 minutes.
• Line 3 states the longest time in minutes from ETP1 to the alternate for the
Most Critical Fuel Scenario Pressurized, One-Engine Out scenario. The time
is rounded to the nearest minute.
• Line 4 states the Other Most Time-Limiting System Limit (OS) value in the
Customer Aircraft database minus 15 minutes.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Copyright © 2018 Jeppesen. All rights reserved.
111
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

ETOPS Entry, Exit, and ETPs in the Nav Log

Figure 7.11 shows an excerpt from the Nav Log with the ETOPS Entry, Exit, and Equal Time
Points. JetPlan can include the ETOPS Entry and Exit Points in the Nav Log portion of the
flight plan as fully-specified, detailed route waypoints.

EEP1 N5034.0 W04239.9 DCT 086 068 489 P045 P07 0300 00+33 ... 49088 ....
370 260046 010 087 069 840 534 00 1594 02+46 ... 65093 ....

5140N N5100.0 W04000.0 DCT 086 068 489 P045 P07 0105 00+12 ... 52004 ....
370 260046 010 087 069 840 534 00 1489 02+58 ... 62177 ....

ETP1 N5145.0 W03339.0 DCT 093 077 489 P040 P07 0242 00+27 ... 58658 ....
370 260040 010 093 077 840 529 00 1247 03+25 ... 55523 ....

5230N N5200.0 W03000.0 DCT 093 077 489 P040 P07 0137 00+16 ... 62425 ....
370 260040 010 093 077 840 529 00 1110 03+41 ... 51756 ....

EXP1 N5201.7 W02042.6 DCT 099 086 490 P038 P08 0344 00+39 ... 71755 ....
370 270038 010 099 086 840 528 00 0766 04+20 ... 42426 ....

Figure 7.11. Entry, Exit, and Equal Time Points in Nav Log

JetPlan can also provide the output options listed below. Ask your Jeppesen Implementation
Specialist or Jeppesen Customer Support about including any of this information in your flight
plans:

• Entry points can be included as waypoints or as non-waypoints, or they can

be excluded.
• Exit points can be included as waypoints or as non-waypoints, or they can
be excluded.
• Equal Time Points points can be included as waypoints or as non-waypoints,
or they can be excluded.
• Airport IDs can be displayed in either ICAO or IATA format.
• The effects that entry, exit, and Equal Time Points have on the segment fuel
and time and distance for the next waypoint.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Copyright © 2018 Jeppesen. All rights reserved.
112
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

Extended Critical Fuel Detail

Figure 7.12 shows the standard extended critical fuel detail that is output when the extended
ETOPS option (ETOPXNL) is requested. The detail includes the third scenario added with
ETOPS II: Pressurized, One-Engine Out (displayed in the PRESS 1 ENG column in the
output).

------- EQUAL TIME POINT DATA - ETP01 CYQX/YQX - EINN/SNN --------

DIVERSION SUMMARY
ETP LOCATION N5145.0 W03339.0
ETE FROM ORIGIN 03+25
GWT AT DIVERSION 465623
FOB 055523
DIVERSION AIRPORTS CYQX/YQX | EINN/SNN
G/C DIST 0819 | 0910

CRITICAL FUEL REQUIRED CALCULATION

FLIGHT CONDITION DECOMP DECOMP PRESS | DECOMP DECOMP PRESS
CONFIG 2 ENG 1 ENG 1 ENG | 2 ENG 1 ENG 1 ENG
SPEED LRC 320 320 | LRC 320 320
FL 100 100 220 | 100 100 220
AVG W/C M023 M023 M030 | P017 P017 P024
ENROUTE TEMP ISA P006 P006 P007 | P005 P005 P006
FORECAST ICING PCT 000100 000100 000100 | 000100 000100 000100
TIME TO ALT NO HOLD 02+28 02+22 02+10 | 02+29 02+22 02+15
CRUISE 034181 036461 030546 | 034357 036501 031944
DESCENT 000627 000663 000774 | 000627 000663 000774
HOLD 002938 002821 002857 | 002937 002821 002849
MAP 001200 001200 001200 | 001200 001200 001200
APU 000732 000836 000701 | 000736 000839 000726
ICING 001887 000399 000342 | 001896 000400 000356
CONSERVATISM 001887 001997 001709 | 001896 001999 001778
TOTAL 043452 044377 038129 | 043649 044423 039627

CRITICAL FUEL REQUIRED AT ETP01 - DECOMP 1 ENG TO EINN/SNN

AMOUNT TIME
CFR 044423 02+22
FOB 055523
QTY DIFF 011100

Figure 7.12. Extended Critical Fuel Detail

The speed modes displayed in the Equal Time Point Data for each ETP derive from the cruise
modes in the Aircraft Fleet database record. JetPlan looks for an SCM dataset in the Aircraft
Fleet database record. If it cannot find an SCM dataset, JetPlan generates an alert. Only the
cruise mode is included in the output for DECOMP 2 ENG, DECOMP 1 ENG, and PRESS 1
ENG. However, the final descent and hold calculations are also based on the Aircraft Fleet
database record. If the data is present for the aircraft, JetPlan also uses the initial emergency
descent modes, but they are not required for a valid ETOPS II plan.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Copyright © 2018 Jeppesen. All rights reserved.
113
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

Time Limited System Information for the ETP in the Extended

Detail
Figure 7.13 shows the Time Limited System (TLS) detail for the ETP (ETP1 in this example).
This information is output for each ETP when the extended ETOPS option is requested and
when the Calculate TLS parameter in the specified SCM dataset in the Customer Aircraft Fleet
database is set to Yes. Calculations use the TLS Fire parameters in the SCM Dataset section
of the Customer Aircraft Fleet database record and the Cargo Fire Suppression Time Limit
(FS) and Other Most Time-Limiting System Limit (OS) parameters in the Customer Aircraft
[Link] are rounded to the nearest minute.

TIME LIMITED SYSTEM COMPLIANCE AT ETP 01

Figure 7.13. Time Limited System Detail for the ETP

The output includes each diversion airport associated with the ETP. For each diversion airport,
the output includes two scenarios: the All Engine Pressurized (ALL E) and the One-Engine
out Pressurized (1 ENG). The scenarios are listed in the CONFIG row.

For each of the scenarios, the following information is listed:

• Flight Level (F.L.).

• Cruise Speed (SPEED).
• Average Wind Component (AVG W/C).
• Average Enroute Temperate (ENROUTE TEMP).
• Limiting Capacity Minus 15 Minutes (SYSTEM CAPACITY MINUS 15
MIN):
– For the All Engine Pressurized Scenario, the limiting capacity value
is the Fire Suppression Limit (FS) value in the Customer Aircraft
database minus 15 minutes.
– For the One-Engine Out Pressurized Scenario, the limiting capacity
value is the Other Most Time-Limiting System Limit (OS) value in
the Customer Aircraft database minus 15 minutes.
• Time to Alternate (TIME TO ALTERNATE).

ETOPS II Startup Guide v. 1.4 April 11, 2018

Copyright © 2018 Jeppesen. All rights reserved.
114
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

ETP Segment Computation Information

The flight plan output includes the standard diagnostic information when the flight plan
request includes the ETOPXNL option. Figure 7.14 shows the diagnostic information for
ETOPS segments.

ETOPS Segment Computation

User airports not used:

User airports added:

User airports removed:

Adequate airport radius: 0435

Area # Name Source Point Point

------- ---- ------ ------ ----
Area 0: CYYB CAPFDB 0 166
Area 1: KJFK CAPFDB 0 442
Area 2: CYUL CAPFDB 0 526
Area 3: KBOS CAPFDB 0 603
Area 4: CYQB CAPFDB 0 646
Area 5: KBGR CAPFDB 0 749
Area 6: CYBG CAPFDB 44 645
Area 7: CYHZ CAPFDB 90 961
Area 8: CYQY CAPFDB 255 1126
Area 9: CYJT CAPFDB 385 1232
Area 10: CYQX CAPFDB 532 1395
Area 11: CYYT CAPFDB 569 1433
Area 12: CYYR CAPFDB 681 1058
Area 13: EINN CAPFDB 2261 3027
Area 14: EGPF CAPFDB 2480 3027
Area 15: LFRB CAPFDB 2500 3027
Area 16: EGPO CAPFDB 2554 2960
Area 17: EGLL CAPFDB 2580 3027

Coverage created by adequate airports

From To From To
Airport Airport Point Point
------- ------- ----- ------
CYYB CYYT 0 1433
EINN EINN 2261 3027

ETOPS Segment Entry/Exit points

Mileage
Entry/Exit # Airport Marker
-------------- ------- ------
Entry point 0: CYYT 1433
Exit point 0: EINN 2261

Figure 7.14. Diagnostic Information – ETOPS Segment

April 11, 2018 ETOPS II Startup Guide v. 1.4

Copyright © 2018 Jeppesen. All rights reserved.
115
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

The adequate airport radius value derives from the default SCM dataset in the Aircraft Fleet
database record. The adequate airports listed in the output are identified as adequate in the
Customer Airport Fleet database record (the ETOPS Adequate Alternate parameter is set to
Yes). You can also add or subtract adequate airports through the flight plan request. The
ETOPS Segment Computation output indicates the source of the listed airports.

Neither the ETOPS Adequate Alternate parameter nor the ETOPS Suitable Alternate
parameter in the Airport Fleet database record needs to be set for JetPlan to generate an
ETOPS II plan. However, if the ETOPS Adequate Alternate parameter is not set, JetPlan does
not output the list of adequate airports. If the ETOPS Suitable Alternate parameter is not set,
JetPlan generates the following alert message, where XXXX is the ICAO identifier the divert
airport that does not have the parameter set:

ALERT TAG EAPTCHK

ALERT MESSAGE XXXX IS FLAGGED AS NOT SUITABLE IN APFDB.

JetPlan can also generate an alert if the suitable airport is below the minimum values as set in
the Customer Airport Fleet database.

Multi-ETOPS Segments Diagnostic Information

Figure 7.15 shows the diagnostic information section for Multi-Segment ETOPS. This flight
plan includes only one segment. In a multi-segment ETOPS flight plan, this section contains
information on each segment. For a detailed example of Multi-Segment output, see “Multi-
ETOPS Segments Output in Detail” on page 122.

Multi-ETOPS Segments Diagnostic

RRR: 1325, DISTF: MINSD:

ALTS ALTS ETP IN INCLUDE

PT LABEL MM ALTS DIST CF CLOSE? ETOPS SEG? ETP?
==== ===== ==== ========= ==== == ====== ========== =======
EEP01 EEP01 1433 CYQX
ETP01 ETP01 1780 CYQX/EINN 1689 Y Y Y
EXP01 EXP01 2261 EINN

ALT SEQ ABEAM LAT/LON START MM END MM EXCLUDED?

======== === ================ ======== ====== =========
CYQX/YQX 01 N4830.0 W05200.0 000053 002658 N
EINN/SNN 02 N5152.7 W00749.3 001769 003027 N

Figure 7.15. Diagnostic Information – Multi-ETOPS Segments

ETOPS II Startup Guide v. 1.4 April 11, 2018

Copyright © 2018 Jeppesen. All rights reserved.
116
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

Suitable Times Detailed Information

Figure 7.16 shows the suitable times detailed information and includes references to any
Flight Brief database record that contains Early and Late Arrival Buffer parameter information
used in the early and late suitable airport calculations. For more information on the suitable
times calculation, see “Setting Up the Flight Brief Database for ETOPS II” on page 54.

Suitable Times Detail

FLIGHT ETD: 2200

SLOW TAS = 340
SLOW SPEED ALTITUDE = FL100
FAST TAS = 420
FAST SPEED ALTITUDE = FL100

THE FOLLOWING FLIGHT BRIEF RECORD(S) MATCH THIS FLIGHT--

SELECTION CRITERIA:

FLIGHT BRIEF NAME: ER77BUFFER FLIGHT BRIEF TYPE: E

EFECTIVE DATE: UFN FLEET TYPE: ER77
EXPIRATION DATE: UFN TAIL NUMBER:
FLIGHT NUMBER: ENROUTE FIR:
POD: KJFK DEPARTURE FIR:
POA: EGLL ARRIVAL FIR:
APT: FIR:
EARLY/LATE ARRIVAL ETOPS BUFFER TIMES:
ETOPS EARLY BUFFER: 0
ETOPS LATE BUFFER: 60

SELECTION CRITERIA:

FLIGHT BRIEF NAME: ETOP-JFKLHR FLIGHT BRIEF TYPE: E

Figure 7.16. Suitable Times Detail

April 11, 2018 ETOPS II Startup Guide v. 1.4

Copyright © 2018 Jeppesen. All rights reserved.
117
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

FBDB RECORD USED FOR EARLY SUITABLE TIME: ETOP-JFKLHR

FBDB RECORD USED FOR LATE SUITABLE TIME: ER77BUFFER
ALTERNATE:CYQX N4856.4W05434.2
SUITABLE EARLY ARRIVAL TIME IS 0158 (0158 - 0 MIN)
SUITABLE LATE ARRIVAL TIME IS 0500 (0500 + 0 MIN)

EAT: 0158 LAT: 0400

CRITICAL POINT EEP1 (N5034.0W04239.9) ETP1 (N5145.0W03339.0)

ETA AT CRITICAL POINT: 0046 FROM POD 0125 FROM POD

G/C DIST 0473 NM 0819 NM
SLOW WC M022 M022
SLOW ARRIVAL TIME 0215 0400
FAST WC M022 M022
FAST ARRIVAL TIME 0158 0329

ALTERNATE:EINN N5242.0W00855.2
SUITABLE EARLY ARRIVAL TIME IS 0320 (0320 - 0 MIN)
SUITABLE LATE ARRIVAL TIME IS 0458 (0458 + 0 MIN)

EAT: 0320 LAT: 0358

CRITICAL POINT ETP1 (N5145.0W03339.0) EXP1 (N5201.7W02042.6)
ETA AT CRITICAL POINT: 0125 FROM POD 0220 FROM POD
G/C DIST 0910 NM 0435 NM
SLOW WC P018 P017
SLOW ARRIVAL TIME 0358 0333
FAST WC P018 P017
FAST ARRIVAL TIME 0330 0320

Figure 7.16. Suitable Times Detail (continued)

ETOPS II Startup Guide v. 1.4 April 11, 2018

Copyright © 2018 Jeppesen. All rights reserved.
118
Understanding ETOPS II Flight Plan Output
About the ETOPS II Flight Plan Output

Critical Point Detailed Information

Figure 7.17 shows the detailed information for the critical point, ETP1, including information
about the backward and forward alternates. Information from the default Customer Aircraft
Fleet SCM dataset is listed, including the Range Ring Radius and Suitable Airport Radius.

Critical Points Detail

TAS: 385
-------BACKWARD------ -------FORWARD-------
COORDINATES MILE ETE ALT DIST TIME WC ALT DIST TIME WC
-------------- ----- ------ ---- ---- ----- ---- ---- ---- ----- -----
ETP1 N51450 W033390 1780 03:25 CYQX 819 02:15 P000 EINN 910 02:15 P000

Diversion Mode: 180/320

Range Ring Radius: 1325
Adequate Airport Radius: 0435

Adequate Airports:
CYYB
KJFK
CYUL
KBOS
CYQB
KBGR
CYBG
CYHZ
CYQY
CYJT
CYQX
CYYT
CYYR
EINN
EGPF
LFRB
EGPO
EGLL

Figure 7.17. Critical Points Detail

April 11, 2018 ETOPS II Startup Guide v. 1.4

TAF Weather Detail

Figure 7.18 shows the detailed weather source, ceiling, and visibility information for the
backward and forward alternates. Information is derived from the Customer Airport Fleet
database ETOPS Ceiling and Visibility parameters and the TAFCHECK preference value.

- TAF SOURCE: TAF_WXD (TAFCHECK PREFERENCE = 4)

TAF SETTINGS FOR CYQX
- CAPFDB ETOPS VISIBILITY MIN = 0 FT.
- CAPFDB ETOPS CEILING MIN = 0 FT.
- CAPDB ETOPS VISIBILITY MIN = 4800 FT.
- CAPDB ETOPS CEILING MIN = 2400 FT.

TAF CYQX 291738Z 2918/3018 17015G25KT P6SM BKN025 OVC070 TEMPO

2918/2921 5SM -SHSNRA BR BKN020
FM292100 19015G25KT P6SM BKN025 OVC070 TEMPO 2921/2924 5SM -SHRA
BR BKN020
FM300000 19015G25KT 6SM -RA BR OVC015 TEMPO 3000/3006 3SM -RA BR
BKN006 OVC015
FM300600 30012G22KT P6SM BKN015 OVC080 TEMPO 3006/3008 5SM
-SHSNRA BR
BECMG 3010/3012 33015G25KT
FM301700 32017G27KT P6SM BKN025
RMK NXT FCST BY 300000Z

TAF SETTINGS FOR EINN

- CAPFDB ETOPS VISIBILITY MIN = 0 FT.
- CAPFDB ETOPS CEILING MIN = 0 FT.
- CAPDB ETOPS VISIBILITY MIN = 2800 M.
- CAPDB ETOPS CEILING MIN = 2800 FT.

TAF EINN 291700Z 2918/3018 33007KT 9999 FEW018 SCT030 TEMPO 3012/3018
34013KT -SHRA FEW018CB BKN020

Figure 7.18. TAF Weather Detail

ETOPS II Startup Guide v. 1.4 April 11, 2018

Time Limited Systems Diagnostics

Figure 7.19 shows the diagnostic output for the Time-Limited Systems scenario, which is
defined in the Customer Aircraft Fleet database. The calculation uses the value of the Cargo
Fire Suppression Time Limit (FS) parameter in the Customer Aircraft database.

TIME LIMITED SYSTEMS DIAGNOSTICS

AIRCRAFT: ER77TEST
FIRE SUPPRESSION LIMIT - 15MIN = 0225

-------

Figure 7.19. Diagnostic Information -- Time Limited Systems

April 11, 2018 ETOPS II Startup Guide v. 1.4

Multi-ETOPS Segments Output in Detail

When the Flight Brief database is configured to support Multi-Segment ETOPS, JetPlan
includes the Multi-Segment Diagnostic section in the flight plan output, similar to the example
in Figure 7.20. For more detailed information on Multi-Segment ETOPS, see Chapter 4,
“Multi-Segment ETOPS.”

Multi-ETOPS Segments Diagnostic

RRR: 1260, DISTF: 50.000 (1260 X 50.000 = 6300MAX), MINSD: 500

ALTS ALTS ETP IN INCLUDE

PT LABEL MM ALTS DIST CF CLOSE? ETOPS SEG? ETP?
==== ===== ==== ========= ==== == ====== ========== =======
EEP01 EEP01 0455 EINN
ETP01 ETP01 0862 EINN/BIKF 1021 Y Y Y Y
EXP01 EXP01 1126 BIKF
EEP02 EEP02 1735 BIKF
ETP02 ETP02 2713 BIKF/CYQX 0629 Y Y Y Y
EXP02 EXP02 4849 CYQX

ALT SEQ ABEAM LAT/LON START MM END MM EXCLUDED?

======== === ================ ======== ====== =========
EINN/SNN 01 N5700.0 E00713.6 000003 002003 N
BIKF/KEF 02 N6900.0 W02000.0 000144 002905 N

Figure 7.20. Detailed Multi-ETOPS Segments Diagnostic Output

Key to the columns in the Multi-ETOPS Segments Diagnostic output:

• PT – The critical point name and number: EEP (ETOPS Entry Point), ETP
(Equal Time Point), and EXP (ETOPS Exit Point).
• Label – The same as PT, but the number can be different because JetPlan
can omit some ETPs.
• MM – The mileage marker of the critical point. This value is the route
distance from the POD to the critical point.
• ALTS – The ETOPS alternates associated with a critical point.
• ALTS DIST – The distance between associated ETOPS alternates.
• CF – Indicates whether or not the critical fuel was calculated for this point
• ALTS CLOSE? – Indicates whether or not the ETOPS alternates are closed.
• ETP IN ETOPS SEG? – Indicates whether or not the ETP is in the ETOPS
segment.
• INCLUDE ETP? – Indicates whether or not the ETP is included in the list of
ETPs.

ETOPS II Startup Guide v. 1.4 April 11, 2018

• ALT – The ETOPS alternate.

• SEQ – The sequential number.
• ABEAM LAT/LON – The coordinates of the point on the route that is
abeam from the alternate.
• START MM – The route path mileage marker where the route enters the big
circle for the alternate.
• END MM – The route path mileage marker where the route exits the big
circle for the alternate.
• EXCLUDED – Indicates whether or not the alternate has been excluded.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Troubleshooting

This chapter includes the following sections:

• Troubleshooting Error Messages and Alerts

• Troubleshooting Common Issues
Troubleshooting
Troubleshooting Error Messages and Alerts

Troubleshooting Error Messages and

Alerts
Table 8-1 provides troubleshooting guidance for possible ETOPS II system errors and alert
messages.

Table 8-1 Error Messages and Alerts

Sample Error/Alert Cause What to do

04 ETOPS DUPLICATE ETOPS Occurs after entering Line 04 Correct the alternate input.
ALTERNATE RECEIVED: input, and indicates that a
<airport code> duplicate alternate was entered.
ALERT TAG ETOPEXA In multi-segment ETOPS plans, Evaluate the alternates and verify
ALERT MSG ETOPS ALT any ETOPS alternate that has no that the remaining combination of
<AIRPORT ID> EXCLUDED: critical points associated with it is airports is acceptable. If it is not,
HAS NO ETPS OR CRITICAL excluded from the set of ETOPS try one of the following solutions:
FUEL CALCULATIONS
alternates and thus from critical • Select an alternate that is
fuel and suitability calculations. closer to the ETOPS segment
JetPlan generates the ETOPS ALT
• Select an alternate that is
alert for each ETOPS alternate that
closer to the other alternates
is automatically excluded.
• Adjust the Flight Brief
In these plans, JetPlan
database Multi-Segment
automatically excludes any
ETOPS parameters so that the
alternate for which all of the
airport will not be excluded
following are true:
• The alternate is not near
another alternate.
• The alternate’s ETPs do not
fall within an ETOPS
segment.
• The alternate has no
associated entry or exit
points.
ETPCOORD In a multi-segment plan, the line of Consider replacing one or the other
NO ETP FOR ALTERNATES ETPs for the airport pair does not alternate or dropping one.
<airport code> AND cross the route because one
<airport code> ALONG THE alternate is too far from the end of
ROUTE OF FLIGHT.
the route or because of the way
alternates are oriented
perpendicular to the route.
VCOSTI01 An invalid cruise mode was used Enter a valid cruise mode from the
in the Aircraft Fleet database for performance modes associated
an emergency scenario. with the aircraft.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 8-1 Error Messages and Alerts

Sample Error/Alert Cause What to do

ALERT TAG NOFMCCI Related to the TC setting. See the Set the LC parameter on your
ALERT MSG FMC CI method JPDC Help for details. aircraft to Raw Sample or
requested but not Traditional JetPlan as is
available for aircraft appropriate for the aircraft.
type.

ALERT TAG ETP1LEP This alert does not indicate a Enter a valid DD01 value.
ALERT MSG PRESS 1 ENG failure in the calculations, only If an initial driftdown descent
INITIAL DESCENT SCM VALUE that the calculations are less calculation is desired, then choose
DDF DOES NOT EXIST. accurate and more conservative
IMMEDIATE DESCENT TO a valid DD01 value from those
than they would be if the system available for the aircraft type. If no
OPTIMIZED FLIGHT LEVEL IS
USED.
were accounting for the initial appropriate descent schedules are
driftdown descent profile in the available, contact your Jeppesen
scenario. Implementation Specialist.
There can be two causes:
• No value is entered for Initial
Driftdown Descent (DD01)
for the Pressurized Engine out
Scenario in the Aircraft Fleet
DB.
• DD01 is set to DDF, and
DDF does not exist in the
aircraft’s cruise mode
schedule.
JetPlan looks for the driftdown
schedule (for example, DDF) in
the auxiliary driftdown section
first. If JetPlan cannot find it in the
auxiliary driftdown section, for
example because it does not exist,
then it looks for it in the auxiliary
descent section. If it is located in
the auxiliary descent section,
JetPlan uses it to calculate the
initial descent to the optimized
flight level. If it is not located in
the auxiliary descent section,
JetPlan drops down to the
optimized flight level, omitting the
initial descent calculations.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 8-1 Error Messages and Alerts

Sample Error/Alert Cause What to do

ALERT TAG ETP1LEP The ACFDB file has DDO1=1LE. Establish the descent schedule.
ALERT MSG PRESS 1 ENG JetPlan looks for the 1LE descent
INITIAL DESCENT NOT schedule in the auxiliary driftdown
COMPUTED FOR ETP1 - section first. If JetPlan cannot find
<AIRPORT ID>: IMMEDIATE
it in the auxiliary driftdown
DESCENT TO FL180 USED.
section, possibly because it doesn’t
exist, then it looks for it in the
auxiliary descent section.
If it is located in the auxiliary
descent section, JetPlan uses it to
calculate the initial descent to the
optimized flight level.
If it is not located in the auxiliary
descent section, JetPlan drops
down to the optimized flight level.
ETOPSCN2 The performance data for the Specify an all-engine schedule that
CRUISE SCHEDULE=393 FOR decompressed all-engine scenario exists in the flight schedules:
DECOMP 2 ENG IS NOT IN A does not exist in the aircraft 1. Select to view the aircraft in
PERFORMANCE DB. performance data flight schedules. the aircraft database.
2. Click the A/C TYPE value in
– or – the upper right of the record.
3. Choose an appropriate all-
ETOPSCN2 engine schedule from among
INITIAL DESCENT those listed.
SCHEDULE=EDO FOR DECOMP 2
ENG IS NOT IN A Consult with your Implementation
PERFORMANCE DB. Specialist for help understanding
the schedules or for another
schedule that is appropriate for
your operation.
TBLDSC99 The descent schedule is not found Specify an all-engine descent
in the performance database. schedule that exists in the flight
schedules:
1. Select to view the aircraft in
the aircraft database.
2. Click the A/C TYPE value in
the upper right of the record.
3. Choose an appropriate all-
engine descent schedule from
among those listed.
4. Check the SCM sets and
make sure that you have
entered the correct value for
the descent schedule.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 8-1 Error Messages and Alerts

Sample Error/Alert Cause What to do

ALERT TAG ETOPCVG A partial or entire ETOPS segment Run another plan with ETOPS
THE ETOPS <segment number> in the route is not within approval alternates that provide ETOPS
IS NOT ETOPS COMPLIANT range of user-submitted ETOPS coverage for the area.
FROM <latitude and alternates.
longitude coordinates>
TO <latitude and
longitude coordinates>

ALERT TAG ETP1LEP Occurs when a problem ID is The alert can be ignored if the
ALERT MSG PRESS 1 ENG encountered in flight level profile is acceptable. Or enter a
INITIAL DESCENT NOT optimization. descent schedule in the Initial
COMPUTED FOR Driftdown Descent parameter in
ETP1 -CYQX: IMMEDIATE
the SCM Dataset of the Aircraft
DESCENT TO FL270 USED.
Fleet DB.
ALERT TAG ETOPCVG Based on the airports in the If the route is an ETOPS route,
ALERT MSG Route has no CAPFDB and the Adequate revisit those airports marked as
ETOPS segments. Non- Airport Range in the SCM Dataset adequate in the CAPFDB. If
ETOPS flight plan is in the Aircraft Fleet DB, the satisfied with those airports as they
calculated.
system could not find entry and are, and if ETP analysis is desired,
exit points because the entire route revert to Overwater Driftdown.
falls within 60 minutes of adequate
airports. In other words, the route
is non-ETOPS. Certain
calculations cannot be performed
without entry and exit points.
ALERT TAG EAPTCHK The ETOPS alternate is unsuitable Use another ETOPS alternate that
ALERT MSG <airport ID> IS between the Early Arrival Time has suitable weather.
NOT SUITABLE DUE TO BAD and Late Arrival Time because the
WEATHER. ceiling or visibility is below the
threshold values set in the
Approach data section of the
Airport Fleet DB or Airport DB.
JetPlan uses the Airport Fleet DB
ceiling and visibility parameters if
they exist. Otherwise it uses the
Airport DB parameters.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 8-1 Error Messages and Alerts

Sample Error/Alert Cause What to do

ETOPBM1 ETOPS was not calculated for the Recompute the plan using different
NON-ETOPS FLIGHT PLAN IS plan because the cruise mode ETOPS alternates.
CALCULATED DUE TO could not be calculated due to a
PERFORMANCE FAILURE FROM performance consideration, such
ETP1 TO KJF <airport
as the aircraft being too heavy at
code> :
ETP1 MILEAGE MARKER:
the critical point.
<nnnn>
AIRCRAFT: <aircraft id>
ACTUAL GWT: <nnnnnnn>
CRUISE MODE: <mode>
TEMP: <temp deviation>
FLIGHT LEVEL: <flight
level>

ETOPBM1 The flight’s distance was

DUE TO NEGATIVE CRUISE computed to be zero or a negative
DISTANCE SCENARIO DECOMP number. Therefore, an immediate
2 ENG FROM ETP1 TO KJFK descent profile was used to the
COMPUTED WITHOUT INITIAL
cruise altitude.
DESCENT.

NOTE DECOMP 2 ENG can also

be DECOMP 1 ENG and PRESS 1
ENG. DESCENT can be DRIFT-
DOWN.

ETOPCRZ The Cruise Mode parameter for the Examine your SCM Dataset values
SCM CRUISE MODES SCM Dataset in the Aircraft Fleet in the Aircraft Fleet DB. Ensure
UNSPECIFIED FOR DECOMP 1 DB is not set for the scenario. that they are set to meet your
ENG. CACDB CRUISE MODE operational objectives.
APPLIED. The ETP CRZ (EC) parameter in
the Customer Aircraft database
- or - was used.

ETOPCRZ
SCM AND CACDB CRUISE MODES
UNSPECIFIED FOR DECOMP 1
ENG. DEFAULT LRC USED.

NOTE DECOMP 2 ENG is a

scenario name. The scenario can
also be DECOMP 1 ENG or
PRESS 1ENG.
NOTE For the one-engine
scenarios, the default performance
mode is 1LE.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 8-1 Error Messages and Alerts

Sample Error/Alert Cause What to do

ALERT TAG ETOPTLS Occurs when the Calculate TLS Set the FIRE SUPP LIM (FS)
ALERT MSG FIRE SUPRESSION flag in the Aircraft Fleet database parameter in the Customer Aircraft
TIME LIMIT IS NOT SET IN record is set to Y, and the FS FIRE DB. For example, 180.
CADB. SUPP LIM in the Aircraft database
THE PLAN MAY NOT COMPLY
is blank or zero.
WITH ETOPS REGULATIONS.

ETOPTLS A Time Limited Systems plan was Enter a value for Cruise Mode in
CRUISE MODE FOR TLS IS NOT computed and the Cruise Mode in the Time-Limited Systems Fire
SET. TLS CALCULATION IS the Time-Limited Systems Fire section of the SCM Dataset in the
SUPPRESSED. section of the SCM Dataset in the Aircraft Fleet DB.
Aircraft Fleet DB is not set.
EAPTCHK An ETOPS plan was requested Add a record in the Airport Fleet
NO CAPFDB RECORD FOR ETOPS with <airport id> as an ETOPS DB for the airport.
ALTERNATE <airport ID> alternate. The airport is not in the
Airport Fleet DB.
EAPTCHK The ETOPS alternate requested is Change the flag setting for the
<airport ID> IS FLAGGED AS flagged ETOPS Suitable airport in the Airport Fleet DB to
NOT SUITABLE IN APFDB. Airport=No in the Alternate ETOPS Suitable Airport=Yes.
Availability section of the Airport
Fleet DB.
EAPTCHK The airport was used as an ETOPS Use a different ETOPS alternate.
<airport ID> IS NOT alternate and the ceiling or
SUITABLE DUE TO BAD visibility at the airport is below the
WEATHER. thresholds set in the Aircraft Fleet
DB or Airport DB during the Early
Arrival Time to late Arrival Time
window.
JetPlan uses the Airport Fleet DB
ceiling and visibility parameters if
they exist. Otherwise, it uses the
Airport DB parameters.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Table 8-1 Error Messages and Alerts

Sample Error/Alert Cause What to do

ETOPCVG There are no ETOPS segments If the need is to force an ETOPS
Route has no ETOPS associated with the route. segment for the flight, change then
segments. Non-ETOPS specify different adequate airports
flight plan is along the route. This can be done
calculated.
by either making changes to the
ETOPS Adequate Alternate setting
in the Alternate Availability
section of the Airport Fleet DB, or
by changing the adequate airports
on a flight-by-flight basis.
If you are using the Basic Flight
planner, see the reference
information in “Running ETOPS II
Flight Plans” on page 63. If you
are using JetPlanner or another
flight planning product, see the
application’s user guide.
ETOPRCL A reclear plan was run and the Review the route and the ETOPS
RECLEAR LEG IS NOT SUBJECT reclear leg is not subject to ETOPS alternates, and select different
TO ETOPS BECAUSE THE rules. ETOPS alternates if necessary.
RECLEAR EXIT POINT IS
LOCATED BEFORE THE
RECLEAR POINT.

ETOPADQ Adequate airports that were Because they are not in the Airport
ADEQUATE AIRPORTS submitted as subtractions from Fleet DB, there is no need to
SUBMITTED BY USER DO NOT those in the Airport Fleet DB are request that they be subtracted
EXIST: <airport ID list> not in the Airport Fleet DB. from the adequate airport set.
ALERT TAG TLSFIRE Occurs when the ETOPS approval Revise the plan as needed to stay
FOR ETP2 TO PHOG THE ALL time is greater than 180 minutes within the FIRE SUPRESSION
ENGINE DIVERSION TIME OF and the FIRE SUPRESSION LIM LIM (FS) in the Customer Aircraft
161 MIN > 35 MIN FIRE (FS) in the Customer Aircraft DB DB minus 15 minutes.
SUPRESSION LIMIT.
minus 15 minutes is less than the
longest divert time for the
pressurized one engine scenario.
FIRE SUPRESSION TIME LIMIT If the FIRE SUPRESSION LIM Enter the FIRE SUPRESSION
IS NOT SET IN CADB. THE (FS) parameter in the Customer LIM (FS) parameter in the
PLAN MAY NOT COMPLY WITH Aircraft DB is not set, the Time Customer Aircraft DB.
ETOPS REGULATIONS. Limited Systems compliance
information is not included in the
flight plan.

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 8-1 Error Messages and Alerts

Sample Error/Alert Cause What to do

CRUISE MODE FOR TLS IS NOT If the Cruise Mode parameter is Enter the Cruise Mode parameter n
SET. TLS CALCULATION IS not set in the Time-Limited the Time-Limited System Fire
SUPPRESSED. System Fire section of the SCM section of the SCM Dataset in the
Dataset in the Aircraft Fleet DB, Aircraft Fleet DB.
the Time Limited Systems
compliance information is not
included in the flight plan.
ETOPDFU NEED MORE FUEL FOR The ETOPS fuel short fall is Examine departure fuel, ETOPS
ETOPS OPERATIONS greater than zero (0) for departure airports, load, and other factors to
fuel cases with a known payload. determine where adjustments can
Departure fuel is insufficient to be made to ensure sufficient fuel
meet ETOPS requirements. exists to meet ETOPS
requirements.
ETOPCFR In the Flight Brief database, all Set at least one of the scenarios in
FUEL DEFICIT OF <#### LBS scenario parameters (D1LEF, the Flight Brief database to Output
or KGS>. FOR <critical DLRCF, and P1LEF) are set to Do in plan, Use in uplift or Output in
point name> TO BIKF FOR not output, Exclude in uplift. plan, Exclude in uplift.
<scenario name>
If all three scenarios are set to Do
Where: not output, Exclude in uplift, the
• #### = The fuel short fall system computes the flight plan
value reported in LBS or without ETOPS and outputs an
KGS alert that all three scenarios have
been excluded and that a fuel
• Critical point name = EEP, deficit may exist. The system does
EXP, or ETP and number not output any ETOPS data on the
• Scenario name = DECOMP 1 flight plan.
ENG, DECOMP 2 ENG, or
PRESS 1 ENG
Example:
FUEL DEFICIT OF 1000 LBS.
FOR ETP1 TO BIKF FOR
DECOMP 1 ENG

AT LEAST ONE ALTERNATE JetPlan has excluded all ETOPS Plan enough alternates sufficient to
REQUIRED alternates from the plans to the meet the requirements for the
reclear POA, so the list of ETOPS reclear route.
alternates for the route to the
reclear POA is empty. The list of
ETOPS alternates for the route to
the reclear POA should not be
empty for ETOPS flight plans. If it
is this, message displays.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Troubleshooting Common Issues

Table 8-2 provides troubleshooting guidance for common issues.

Table 8-2 Common Issues

Problem Cause What to do

The POD and POA are not To use the POD and POA as Specify the POD and POA as
showing up as Alternates alternates, those airports must be alternates.
specified along with the other
ETOPS alternates.

The plan includes one alternate The wrong syntax was used for Alternates should be input with /
even though two were input entering alternates. as the separator, such as in
CYQX/BIKF.
The following inputs are not
correct:
• CYQX,BIKF or
• CYQX BIKF

Line 04 does not allow data entry. ETOPS II option was not specified Use one of the following options:
in LINE 01. • ETOPN
• ETOPXN
• ETOPXNL

April 11, 2018 ETOPS II Startup Guide v. 1.4

Table 8-2 Common Issues

Problem Cause What to do

Some critical fuel scenarios in the The Flight Brief database record is Set the ETOPS scenarios in the
extended output are not computed configured to compute only Flight Brief database
and show all zeros, similar to what certain scenarios. appropriately.
is shown below:

FLIGHT CONDITION DECOMP

DECOMP PRESS
CONFIG 2 ENG. 1
ENG. 1 ENG.
SPEED LRC
320
F.L. 100
100 000
AVG W/C P026
P026 P000
ENROUTE TEMP ISA P000
P000 P000
FORECAST ICING PCT 00100
000100 000100
TIME TO ALT NO HOLD 02.54
02.40 00.00
CRUISE 038079
037443 000000
DESCENT 000627
000663 000000
HOLD 002720
002603 000000
APU 001005
000931 000000
ICING 001657
000407 000000
CONSERVATISM 001935
001905 000000
TOTAL 046023
043952 000000

No Time Limited Systems Fire The Calculate TLS flag might be Set the Calculate TLS flag to Y in
Suppression Output. set to N in the Time-Limited the Time-Limited System Fire
System Fire section of the SCM section of the SCM Dataset in the
Dataset in the Aircraft Fleet DB. Aircraft Fleet DB.

ETOPS II Startup Guide v. 1.4 April 11, 2018

Full Sample ETOPS II

Flight Plan Output

This appendix includes the following sections:

• Overview
• ETOPS II Sample Flight Plan Request Options
• ETOPS II Sample Flight Plan Output (Full)
Full Sample ETOPS II Flight Plan Output
Overview

Overview
This appendix includes sample flight plan inputs and the resulting flight plan output. The
sample ETOPS II flight plan in this appendix is in the FLE format. The content of the flight
plan output is typical for the ETOPXNL flight plan option. However, your specific format
may vary somewhat from this example.

For detailed descriptions of the ETOPS II-related sections in the sample flight plan output, see
Chapter 7, “Understanding ETOPS II Flight Plan Output.” For descriptions of the ETOPS II
flight plan options, see Chapter 3, “Running ETOPS II Flight Plans.” For more information on
fight plans and flight plan options, see the JetPlan User Manual.

ETOPS II Sample Flight Plan Request

Options
The following flight plan request inputs resulted in the sample flight plan output in the
following section.

01 OPTIONS fp,fle,etopxnl,wh07,aw,-e,cs/jdtest,cpt/w david,dsp/j

hanna
02 POD kjfk
03 POA egll
04 ETOPS cyqx,,100/einn,100
06 ROUTE j
07 HOLD,ALTERNATE/DIST 30,eham
08 ETD 2200
09 PROFILE i
10 A/C TYPE/REGN $er77test
11 CRZ MODE m84
14 PAYLOAD 85000
16 POD OR POA FUEL a0,i
20 COMPUTING 2665

April 11, 2018 ETOPS II Startup Guide v. 1.4

ETOPS II Sample Flight Plan Output (Full)

NUMBER OF ALERTS 2

ALERT TAG EAPTCHK

ALERT MSG CYQX IS NOT SUITABLE DUE TO BAD WEATHER

ALERT TAG EAPTCHK

ALERT MSG EINN IS NOT SUITABLE DUE TO BAD WEATHER

BLOCK TIMES FLIGHT TIMES FUEL

IN . . . . ON . . . . TAKEOFF . . .
OUT . . . . OFF . . . . LANDING . . .
TOTAL . . . . TOTAL . . . . BURN . . .
CAPT W DAVID
F/O
DISP J HANNA

* JEPPESEN HISTORICAL AVERAGE WINDS HAVE BEEN USED. *

///// THIS FLIGHT PLAN COMPLIES WITH THE 180 MIN ETOPS RULE /////

PLAN 2665 11292216Z FOR ETD 2200Z

FLT REL IFR JDTEST /30 KJFK/JFK TO EGLL/LHR MACH: M84 REGN NTEST
PROGS JUL ELEV 0013FT 0083FT AVG W/C P042 ISA DEV P08
COMP 2216Z FOR ETD 2200Z/30NOV17 REGN NTEST TRENT892 LBS

SUBJECT TO THE FOLLOWING CONDITIONS

ETOPS FLIGHT/MAX DIVERSION TIME IN STILL AIR LIMITED TO 180 MINUTES
FROM THE FOLLOWING ETOPS ALTERNATE AIRPORTS - CYQX/YQX
EINN/SNN
NOTE See “ETOPS Approval Time Line” on page 107.

FUEL TIME CORR OWE 325100 PYLD 85000 APLD .. .. ..

INCREMENTAL BURN PER 1000 LBS INCREASE/DECREASE IN TOW: 163

ATC CLRNC:.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..

ETOPS II Startup Guide v. 1.4 April 11, 2018

-N0489F370 DCT MERIT DCT HFD J42 BOS J575 YQY DCT JOOPY/M084F370
DCT 49N050W/M084F370 51N040W 52N030W 52N020W/M084F370 DCT
LIMRI/N0491F370 DCT XETBO DCT VAPAL DCT EVRIN UL607 NUMPO UP2
BEDEK

FL 370
NOTE See “Fuel Block” on page 108.

ENROUTE ALTN:
CYQX/YQX VALIDITY PERIOD FROM 0158 UTC / TO 0500 UTC
EINN/SNN VALIDITY PERIOD FROM 0320 UTC / TO 0458 UTC
NOTE See “Suitable Airports Times” on page 108.

MOST CRITICAL FUEL SCENARIO AT : ETP01 FUEL EXCESS OF 11100

TIME TO
DIST W/C CFR FOB EXC ETP / ALT
ETP1 CYQX/EINN 0819/0910 M023/P017 044423 055523 11100 03+25/02+22
N5145.0 W03339.0

EEP1: N5034.0 W04239.9

EXP1: N5201.7 W02042.6
NOTE See “Critical Fuel Summary” on page 109 and “Equal Time Point Summary” on page 109.

TIME LIMITED SYSTEM COMPLIANCE SUMMARY

LONGEST ALL-ENGINE DIVERSION TIME IS 121 MINUTES FROM ETP1

KJFK ELEV 00013FT

POSN LAT LONG AWY M/H T/H TAS COMP TMP ZND ZNT ETA ACBO / ABO
FREQY FL WIND GMORA M/C T/C MAC GS SR DTGO ACTM ATA FOB / AFOB

KJFK N4038.4 W07346.7 DEPARTURE MANEUVERING 00+00 ... 0000 ....

3027 00+00 ...114181 ....

FIR N4051.5 W07335.5 DCT 043 030 ... P015 P11 0015 00+03 ... 2014 ....
CLB ...... 047 047 033 ... 443 01 3012 00+03 ...112167 ....

MERIT N4122.9 W07308.2 DCT 043 030 ... P015 P11 0038 00+08 ... 7118 ....
CLB ...... 047 047 033 ... 443 01 2974 00+11 ...107063 ....

HFD N4138.5 W07232.8 DCT 071 057 ... P033 P09 0031 00+04 ... 9150 ....
114.9 CLB ...... 047 073 059 ... 507 02 2943 00+15 ...105031 ....

PUT N4157.3 W07150.6 J42 070 056 ... P039 P08 0037 00+05 ... 11576 ....
117.4 CLB ...... 042 072 059 ... 537 01 2906 00+20 ...102605 ....

TOC J42 068 054 489 P040 P07 0028 00+02... 12212 ....
370 270048 049 071 057 529 00 2878 00+22 ...101969 ....

April 11, 2018 ETOPS II Startup Guide v. 1.4

BOS N4221.4 W07059.4 J42 068 054 489 P040 P07 0017 00+02 ... 12743 ....
112.7 370 270048 049 071 057 840 529 00 2861 00+24 ...101438 ....

SCUPP N4236.2 W07013.8 J575 079 064 489 P043 P07 0037 00+04 ... 13853 ....
370 270048 021 082 066 840 532 00 2824 00+28 ...100328 ....

CANAL N4240.1 W07001.4 J575 080 065 489 P045 P07 0010 00+01 ... 14150 ....
370 270049 021 082 067 840 534 00 2814 00+29 ...100031 ....

TUSKY N4333.9 W06700.0 J575 080 065 489 P045 P07 0143 00+16 ... 18400 ....
370 270049 021 082 067 840 534 01 2671 00+45 ... 95781 ....

YQI N4349.5 W06604.9 J575 082 066 489 P046 P07 0043 00+05 ... 19666 ....
113.3 370 269050 018 085 068 840 535 00 2628 00+50 ... 94515 ....

HIDIG N4440.8 W06401.0 J575 073 056 489 P044 P07 0103 00+12 ... 22701 ....
370 267051 024 076 059 840 533 02 2525 01+02 ... 91480 ....

YHZ N4455.4 W06324.1 J575 076 059 489 P047 P07 0030 00+03 ... 23573 ....
115.1 370 265052 024 078 061 840 536 02 2495 01+05 ... 90608 ....

IGTAS N4505.0 W06259.4 J575 077 059 489 P047 P07 0020 00+02 ... 24154 ....
370 264052 027 079 061 840 536 02 2475 01+07 ... 90027 ....

YQY N4609.2 W06003.3 J575 078 060 489 P048 P07 0139 00+16 ... 28171 ....
114.9 370 261051 032 079 062 840 537 00 2336 01+23 ... 86010 ....

FIR N4641.7 W05825.0 DCT 080 062 490 P046 P08 0075 00+08 ... 30312 ....
370 260048 035 083 064 840 536 00 2261 01+31 ... 83869 ....

JOOPY N4830.0 W05200.0 DCT 080 062 490 P046 P08 0282 00+32 ... 38364 ....
370 260048 035 083 064 840 536 00 1979 02+03 ... 75817 ....

FIR N4846.3 W05056.3 DCT 086 068 489 P045 P07 0045 00+05 ... 39631 ....
370 260046 021 087 069 840 534 00 1934 02+08 ... 74550 ....

4950N N4900.0 W05000.0 DCT 086 068 489 P045 P07 0040 00+05 ... 40758 ....
370 260046 021 087 069 840 534 00 1894 02+13 ... 73423 ....

EEP1 N5034.0 W04239.9 DCT 086 068 489 P045 P07 0300 00+33 ... 49088 ....
370 260046 010 087 069 840 534 00 1594 02+46 ... 65093 ....

5140N N5100.0 W04000.0 DCT 086 068 489 P045 P07 0105 00+12 ... 52004 ....
370 260046 010 087 069 840 534 00 1489 02+58 ... 62177 ....

ETP1 N5145.0 W03339.0 DCT 093 077 489 P040 P07 0242 00+27 ... 58658 ....
370 260040 010 093 077 840 529 00 1247 03+25 ... 55523 ....

5230N N5200.0 W03000.0 DCT 093 077 489 P040 P07 0137 00+16 ... 62425 ....
370 260040 010 093 077 840 529 00 1110 03+41 ... 51756 ....

EXP1 N5201.7 W02042.6 DCT 099 086 490 P038 P08 0344 00+39 ... 71755 ....
370 270038 010 099 086 840 528 00 0766 04+20 ... 42426 ....
NOTE See “ETOPS Entry, Exit, and ETPs in the Nav Log” on page 112.
5220N N5200.0 W02000.0 DCT 099 086 490 P038 P08 0027 00+03 ... 72487 ....
370 270038 010 099 086 840 528 00 0739 04+23 ... 41694 ....

ETOPS II Startup Guide v. 1.4 April 11, 2018

LIMRI N5200.0 W01500.0 DCT 096 088 490 P036 P08 0185 00+21 ... 77448 ....
370 273036 010 096 088 840 526 02 0554 04+44 ... 36733 ....

XETBO N5200.0 W01400.0 DCT 096 090 491 P035 P09 0037 00+04 ... 78437 ....
370 275035 010 096 090 840 526 02 0517 04+48 ... 35744 ....

VAPAL N5152.7 W00749.3 DCT 095 089 491 P033 P09 0229 00+27 ... 84546 ....
370 273033 048 095 089 840 524 00 0288 05+15 ... 29635 ....

EVRIN N5146.9 W00633.8 DCT 100 097 490 P033 P08 0047 00+05 ... 85792 ....
370 271033 019 100 097 840 523 01 0241 05+20 ... 28389 ....

NEKAP N5143.6 W00517.4 UL607 096 093 490 P033 P08 0048 00+06 ... 87058 ....
370 271033 019 096 093 840 523 01 0193 05+26 ... 27123 ....

TOD UL607 097 095 490 P032 P08 0055 00+06 ... 88510 ....
370 270032 043 097 095 840 522 01 0138 05+32 ... 25671 ....

ABDUK N5138.6 W00348.0 UL607 097 095 ... P032 P08 0001 00+00 ... 88521 ....
DSC ...... 043 097 095 ... 499 01 0137 05+32 ... 25660 ....

NUMPO N5136.6 W00317.0 UL607 098 096 ... P033 P05 0019 00+02 ... 88590 ....
DSC ...... 043 098 096 ... 500 00 0118 05+34 ... 25591 ....

OKESI N5126.6 W00203.7 UP2 105 103 ... P021 P08 0047 00+06 ... 88842 ....
DSC ...... 043 104 102 ... 411 01 0071 05+40 ... 25339 ....

BEDEK N5122.3 W00133.5 UP2 105 104 ... P018 P07 0019 00+03 ... 88976 ....
DSC ...... 031 104 103 ... 379 01 0052 05+43 ... 25205 ....

NIGIT N5118.8 W00110.3 OCK2F 105 104 ... P015 P06 0015 00+03 ... 89092 ....
DSC ...... 024 104 103 ... 359 01 0037 05+46 ... 25089 ....

D272L N5118.5 W00045.9 OCK2F 092 091 ... P013 P04 0015 00+02 ... 89226 ....
DSC ...... 024 092 091 ... 294 01 0022 05+48 ... 24955 ....

OCK N5118.3 W00026.8 OCK2F 092 091 ... P009 00 0012 00+03 ... 89347 ....
115.3 DSC ...... 023 091 091 ... 275 00 0010 05+51 ... 24834 ....

EGLL N5128.7 W00027.7 OCK2F 359 358 ... P001 M06 0010 00+06 ... 90006 ....
DSC ...... 023 358 357 ... 095 00 0000 05+57 ... 24175 ....
ELEV 00083FT

ATC ARRIV:.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..

GREAT CIRCLE DISTANCE 2999 NM AIR DISTANCE 2801 KJFK TO EGLL

FLT PLAN BASED ON WP042 ISA P08

DESTINATION ALTERNATE DATA

POSN LAT LONG AWY M/H TAS COMP ZND ZNT ETA LBS
FREQY FL WIND GMORA M/C MAC RS SR ACTM ATA ABO ACBO

MISAP N5128.7 W00027.7

April 11, 2018 ETOPS II Startup Guide v. 1.4

BPK N5145.0 W00006.4 .. 038 326 P012 031 006 ... ...
117.5 265018 023 040 ... 338 01 0006 ... ... 3483

TOTRI N5146.5 E00011.8 Q295 081 325 P021 011 002 ... ...
270021 024 083 ... 346 01 0008 ... ... 4719

MATCH N5146.8 E00015.0 Q295 083 327 P023 002 000 ... ...
270023 024 000 ... 350 01 0008 ... ... 4945

BRAIN N5148.7 E00039.1 Q295 082 325 P030 015 003 ... ...
269030 024 083 ... 355 01 0011 ... ... 6631

DAGGA N5149.3 E00047.7 Q295 083 437 P032 005 001 ... ...
269032 024 083 ... 469 01 0012 ... ... 7194

CLN N5150.9 E00108.9 Q295 083 437 P032 013 002 ... ...
114.55 290 268032 024 083 733 469 01 0014 ... ... 7571

ARTOV N5154.3 E00125.6 UL620 071 437 P030 011 001 ... ...
290 268031 023 072 733 467 01 0015 ... ... 7890

TOD N5204.2 E00216.5 UL620 071 275 P030 033 004 ... ...
290 266029 023 072 ... 305 01 0019 ... ... 8808

REDFA N5206.9 E00229.3 UL620 071 280 P028 008 002 ... ...
266029 023 072 ... 308 01 0021 ... ... 8918

SULUT N5226.9 E00325.3 REDF1A 058 274 P016 040 009 ... ...
262018 014 059 ... 290 01 0030 ... ... 9469

SUGOL N5231.5 E00358.0 REDF1A 075 274 P014 021 005 ... ...
259014 014 076 ... 288 01 0035 ... ... 9758

EHAM N5218.5 E00445.9 REDF1A 116 P025 032 007 ... ...
261030 017 113 ... 01 0042 ... ... 10199
ELEV -0011FT
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
START OF ICAO FLIGHT PLAN

(FPL-JDTEST-IS
-B772/H-SDE1E2E3GHIJ3J5M1RWXY/LB1D1
-KJFK2200
-N0489F370 DCT MERIT DCT HFD J42 BOS J575 YQY DCT JOOPY/M084F370
DCT 49N050W/M084F370 51N040W 52N030W 52N020W/M084F370 DCT
LIMRI/N0491F370 DCT XETBO DCT VAPAL DCT EVRIN UL607 NUMPO UP2
BEDEK
-EGLL0557 EHAM
-PBN/A1B1D1L1 DOF/171130 REG/NTEST
EET/KZBW0003 CZQM0045 CZQX0131 JOOPY0203 CZQX0208 50W0213 40W0258
EGGX0341 20W0423 EISN0444 XETBO0448 EGTT0520
SEL/TEST PER/D RALT/KJFK CYQX EINN EGLL RMK/TCAS EQUIPPED)

END OF ICAO FLIGHT PLAN

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

ETOPS II Startup Guide v. 1.4 April 11, 2018

------- EQUAL TIME POINT DATA - ETP01 CYQX/YQX - EINN/SNN --------

DIVERSION SUMMARY
ETP LOCATION N5145.0 W03339.0
ETE FROM ORIGIN 03+25
GWT AT DIVERSION 465623
FOB 055523
DIVERSION AIRPORTS CYQX/YQX | EINN/SNN
G/C DIST 0819 | 0910

CRITICAL FUEL REQUIRED CALCULATION

CRITICAL FUEL REQUIRED AT ETP01 - DECOMP 1 ENG TO EINN/SNN

AMOUNT TIME
CFR 044423 02+22
FOB 055523
QTY DIFF 011100
NOTE See “Extended Critical Fuel Detail” on page 113.

TIME LIMITED SYSTEM COMPLIANCE AT ETP 01

DIVERSION AIRPORTS CYQX EINN
CONFIG ALL E 1 ENG ALL E 1 ENG
F.L. 300 220 300 220
SPEED LRC 320 LRC 320
AVG W/C M040 M030 P032 P024
ENROUTE TEMP M039 M022 M040 M023
SYSTEM CAPACITY MINUS 15 MIN 225 225 225 225
TIME TO ALTERNATE 121 130 117 135
NOTE See “Time Limited System Information for the ETP in the Extended Detail” on page 114.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

START OF WIND AND TEMPERATURE SUMMARY KJFK TO EGLL

------------------------------------------------------------------

FL ISA WIND CMP TMP WIND CMP TMP WIND CMP TMP WIND CMP TMP

410 -56 27043+036-54 27044+040-54 27044+040-54 27044+040-53

390 -56 27047+039-53 27048+043-53 27048+044-53 27048+044-53
370 -56 27048+040-50 27048+043-50 27049+045-50 27049+045-50

April 11, 2018 ETOPS II Startup Guide v. 1.4

350 -54 27048+040-46 27049+044-46 27049+045-46 27050+046-46

330 -50 27047+039-42 27047+043-42 27048+044-42 27048+044-42
310 -46 27044+036-38 27044+040-38 27045+041-38 27045+042-38
BOS SCUPP CANAL TUSKY

410 -56 27045+041-53 27045+038-53 27046+041-53 27046+041-53

390 -56 27049+045-53 27050+042-52 27051+045-52 27051+046-52
370 -56 27050+046-50 27051+044-50 27052+047-50 26052+047-50
350 -54 27050+047-46 26051+046-46 26052+048-46 26052+049-46
330 -50 27049+046-43 26050+046-43 26050+047-43 26050+047-43
310 -46 26046+044-38 26047+043-39 26047+044-39 26047+044-39
YQI HIDIG YHZ IGTAS

410 -56 26045+042-53 26043+041-52 26042+041-52 26042+041-52

390 -56 26050+047-52 26047+045-52 26046+045-52 26045+044-52
370 -56 26051+048-50 26048+046-49 26046+045-50 26046+045-50
350 -54 26051+048-46 26048+046-46 26047+046-47 26046+045-47
330 -50 26049+046-43 26046+044-43 26045+044-44 26044+043-44
310 -46 26046+044-39 26044+042-40 26042+041-41 26041+040-41
YQY JOOPY 4950N 5140N

410 -56 26037+037-52 27034+034-51 27032+032-51 27031+031-51

390 -56 26040+040-52 27037+037-51 27035+035-51 27034+034-50
370 -56 26040+040-50 27038+038-49 27036+036-49 28035+035-48
350 -54 26040+040-47 27038+038-46 28036+036-46 28035+035-46
330 -50 26039+039-44 27038+038-44 28036+036-44 28035+035-44
310 -46 27037+036-41 27036+036-41 28034+034-41 28034+033-41
5230N 5220N LIMRI XETBO

410 -56 27030+030-51 27029+029-51 27029+029-51

390 -56 27033+033-50 27032+032-51 27032+032-51
370 -56 27033+033-48 27033+033-49 27033+033-49
350 -54 27034+034-46 27034+034-47 27034+034-47
330 -50 28034+034-44 27034+034-44 27034+034-44
310 -46 28033+032-42 27033+033-42 27033+033-42
VAPAL EVRIN NEKAP

END OF WIND AND TEMPERATURE SUMMARY KJFK TO EGLL

------------------------------------------------------------------
ROUTE ARRAY KJFK TO EGLL

KJFK N40384W073467 FIR N40515W073355 MERIT N41229W073082

HFD N41385W072328 PUT N41573W071506 BOS N42214W070594
SCUPP N42362W070138 CANAL N42401W070014 TUSKY N43339W067000
YQI N43495W066049 HIDIG N44408W064010 YHZ N44554W063241
IGTAS N45050W062594 YQY N46092W060033 FIR N46417W058250
JOOPY N48300W052000 FIR N48463W050563 4950N N49000W050000
EEP1 N50340W042399 5140N N51000W040000 ETP1 N51450W033390
5230N N52000W030000 EXP1 N52017W020426 5220N N52000W020000
LIMRI N52000W015000 XETBO N52000W014000 VAPAL N51527W007493
EVRIN N51469W006338 NEKAP N51436W005174 ABDUK N51386W003480
NUMPO N51366W003170 OKESI N51266W002037 BEDEK N51223W001335
NIGIT N51188W001103 D272L N51185W000459 OCK N51183W000268
EGLL N51287W000277

------------------------------------------------------------------

ETOPS II Startup Guide v. 1.4 April 11, 2018

DISPATCH REL IFR JDTEST /30 KJFK/JFK TO EGLL/LHR MACH:M84 REG NTEST

SUBJECT TO THE FOLLOWING CONDITIONS

ETOPS FLIGHT/MAX DIVERSION TIME IN STILL AIR LIMITED TO 180 MINUTES
FROM THE FOLLOWING ETOPS ALTERNATE AIRPORTS - CYQX/YQX
EINN/SNN

-N0489F370 DCT MERIT DCT HFD J42 BOS J575 YQY DCT JOOPY/M084F370
DCT 49N050W/M084F370 51N040W 52N030W 52N020W/M084F370 DCT
LIMRI/N0491F370 DCT XETBO DCT VAPAL DCT EVRIN UL607 NUMPO UP2
BEDEK

REQUIRED FUEL - 116181 LBS

I CERTIFY THAT THIS FLIGHT IS DISPATCHED/RELEASED IN ACCORDANCE

WITH ALL APPLICABLE FAR REGULATIONS.

DISPATCHER: J HANNA

PIC: W DAVID F/O: R/O:

DISPATCHER SIGN .. .. .. .. ..

PIC SIGN: .. .. .. .. .. .. .. SOBS:.. .. . MEL/CDL: .. .. .. .. ..

( ) SPECIAL AIRPORT AND/OR ROUTE PER FAR 121.445 (CHECK BOX AND
PIC SIGN ONLY IF APPLICABLE).
( ) THIS ROUTE MAY REQUIRE SPECIAL TERRAIN AVOIDANCE PROCEDURES PER
FAR 121.191 (CHECK BOX AND PIC SIGN ONLY IF APPLICABLE).

I CERTIFY THAT I AM QUALIFIED TO SERVE AS PIC TO THE APPLICABLE

SPECIAL AIRPORT AND/OR ROUTE IN ACCORDANCE WITH THE REQUIREMENT
OF FAR 121.445.

PIC SIGN: .. .. .. .. .. .. .. .. .. ..

ETOPS Segment Computation

User airports not used:

User airports added:

User airports removed:

Adequate airport radius: 0435

Area # Name Source Point Point

April 11, 2018 ETOPS II Startup Guide v. 1.4

Area 8: CYQY CAPFDB 255 1126

Area 9: CYJT CAPFDB 385 1232
Area 10: CYQX CAPFDB 532 1395
Area 11: CYYT CAPFDB 569 1433
Area 12: CYYR CAPFDB 681 1058
Area 13: EINN CAPFDB 2261 3027
Area 14: EGPF CAPFDB 2480 3027
Area 15: LFRB CAPFDB 2500 3027
Area 16: EGPO CAPFDB 2554 2960
Area 17: EGLL CAPFDB 2580 3027

Coverage created by adequate airports

From To From To
Airport Airport Point Point
------- ------- ----- ------
CYYB CYYT 0 1433
EINN EINN 2261 3027

ETOPS Segment Entry/Exit points

Mileage
Entry/Exit # Airport Marker
-------------- ------- ------
Entry point 0: CYYT 1433
Exit point 0: EINN 2261
NOTE See “ETP Segment Computation Information” on page 115.

Multi-ETOPS Segments Diagnostic

RRR: 1325, DISTF: MINSD:

ALTS ALTS ETP IN INCLUDE

PT LABEL MM ALTS DIST CF CLOSE? ETOPS SEG? ETP?
==== ===== ==== ========= ==== == ====== ========== =======
EEP01 EEP01 1433 CYQX
ETP01 ETP01 1780 CYQX/EINN 1689 Y Y Y
EXP01 EXP01 2261 EINN

ALT SEQ ABEAM LAT/LON START MM END MM EXCLUDED?

======== === ================ ======== ====== =========
CYQX/YQX 01 N4830.0 W05200.0 000053 002658 N
EINN/SNN 02 N5152.7 W00749.3 001769 003027 N
NOTE See “Multi-ETOPS Segments Diagnostic Information” on page 116 and “Multi-ETOPS Segments Output in
Detail” on page 122.

Suitable Times Detail

FLIGHT ETD: 2200

SLOW TAS = 340
SLOW SPEED ALTITUDE = FL100
FAST TAS = 420
FAST SPEED ALTITUDE = FL100

THE FOLLOWING FLIGHT BRIEF RECORD(S) MATCH THIS FLIGHT--

ETOPS II Startup Guide v. 1.4 April 11, 2018

SELECTION CRITERIA:
FLIGHT BRIEF NAME: ER77BUFFER FLIGHT BRIEF TYPE: E
EFECTIVE DATE: UFN FLEET TYPE: ER77
EXPIRATION DATE: UFN TAIL NUMBER:
FLIGHT NUMBER: ENROUTE FIR:
POD: KJFK DEPARTURE FIR:
POA: EGLL ARRIVAL FIR:
APT: FIR:
EARLY/LATE ARRIVAL ETOPS BUFFER TIMES:
ETOPS EARLY BUFFER: 0
ETOPS LATE BUFFER: 60

SELECTION CRITERIA:

FLIGHT BRIEF NAME: ETOP-JFKLHR FLIGHT BRIEF TYPE: E

FBDB RECORD USED FOR EARLY SUITABLE TIME: ETOP-JFKLHR

FBDB RECORD USED FOR LATE SUITABLE TIME: ER77BUFFER

ALTERNATE:CYQX N4856.4W05434.2
SUITABLE EARLY ARRIVAL TIME IS 0158 (0158 - 0 MIN)
SUITABLE LATE ARRIVAL TIME IS 0500 (0500 + 0 MIN)

EAT: 0158 LAT: 0400

CRITICAL POINT EEP1 (N5034.0W04239.9) ETP1 (N5145.0W03339.0)
ETA AT CRITICAL POINT: 0046 FROM POD 0125 FROM POD
G/C DIST 0473 NM 0819 NM
SLOW WC M022 M022
SLOW ARRIVAL TIME 0215 0400
FAST WC M022 M022
FAST ARRIVAL TIME 0158 0329

ALTERNATE:EINN N5242.0W00855.2
SUITABLE EARLY ARRIVAL TIME IS 0320 (0320 - 0 MIN)
SUITABLE LATE ARRIVAL TIME IS 0458 (0458 + 0 MIN)

EAT: 0320 LAT: 0358

April 11, 2018 ETOPS II Startup Guide v. 1.4

Critical Points Detail

Diversion Mode: 180/320

Range Ring Radius: 1325
Adequate Airport Radius: 0435

Adequate Airports:
CYYB
KJFK
CYUL
KBOS
CYQB
KBGR
CYBG
CYHZ
CYQY
CYJT
CYQX
CYYT
CYYR
EINN
EGPF
LFRB
EGPO
EGLL
NOTE See “Critical Point Detailed Information” on page 119.

- TAF SOURCE: TAF_WXD (TAFCHECK PREFERENCE = 4)

TAF SETTINGS FOR CYQX
- CAPFDB ETOPS VISIBILITY MIN = 0 FT.
- CAPFDB ETOPS CEILING MIN = 0 FT.
- CAPDB ETOPS VISIBILITY MIN = 4800 FT.
- CAPDB ETOPS CEILING MIN = 2400 FT.

TAF CYQX 291738Z 2918/3018 17015G25KT P6SM BKN025 OVC070 TEMPO

TAF SETTINGS FOR EINN

- CAPFDB ETOPS VISIBILITY MIN = 0 FT.
- CAPFDB ETOPS CEILING MIN = 0 FT.

ETOPS II Startup Guide v. 1.4 April 11, 2018

- CAPDB ETOPS VISIBILITY MIN = 2800 M.

- CAPDB ETOPS CEILING MIN = 2800 FT.

TAF EINN 291700Z 2918/3018 33007KT 9999 FEW018 SCT030 TEMPO 3012/3018
34013KT -SHRA FEW018CB BKN020
NOTE See “TAF Weather Detail” on page 120.

============

TIME LIMITED SYSTEMS DIAGNOSTICS

AIRCRAFT: ER77TEST
FIRE SUPPRESSION LIMIT - 15MIN = 0225

-------

END OF JEPPESEN DATAPLAN

REQUEST NO. 2665

01 OPTIONS

April 11, 2018 ETOPS II Startup Guide v. 1.4

NOTE The Glossary includes definitions of special ETOPS terms used in this guide.
You can also refer to the JetPlan User Manual or ask your Jeppesen Customer
Support representative for assistance.

AOO — Area of Operation—For turbine engine-powered airplanes with two engines, an

area beyond 60 minutes from an adequate airport—or with more than two engines, an
area beyond 180 minutes from an adequate airport—and within the authorized ETOPS
Maximum Diversion Time approved for the operation being conducted. An ETOPS
Area of Operation is calculated at the Approved One-Engine Inoperative Cruise Speed
under standard conditions in still air.

APU — Auxiliary Power Unit

APU BR — APU Burn Rate

CADB — Customer Aircraft Database

Critical Fuel Requirement — The end result of the ETOPS computations used to ensure
that the aircraft has sufficient fuel to fly the worst case diversion leg in the worst case
scenario. The three standard scenarios are accounted for on each diversion leg and fuel
to meet the worst scenario must be on board according to the flight plan at the critical
point.
Glossary

CFS — Critical Fuel Scenario

Critical Point (Equal Time Point) — The ETP at which the ETOPS Critical Fuel Required
is the closest to, or exceeds, the Planned Fuel On Board.

EAT — Early Arrival Time

EB — Early Buffer Time

EEP — ETOPS Entry Point

ETOPS Alternate — Suitable airports that provide coverage of the entire AOO.

ETP — Equal Time Points. Points along the route at which the crew can expect to change
which airport to divert to in case of an emergency.

ETE — Estimated Time Enroute

EXP — ETOPS Exit Point

FAR — Federal Aviation Regulation

LAT — Late Arrival Time

LB — Late Buffer Time

POD — Point of Departure

POA — Point of Arrival

ETOPS II Startup Guide v. 1.4 April 11, 2018

ST — Situation Code

Suitability Times — The earliest and the latest time the aircraft can be expected to arrive at
the ETOPS alternate airport, depending on the critical points, and the slowest and
fastest expected speeds the aircraft can be expected to fly on a diversion to that airport.

April 11, 2018 ETOPS II Startup Guide v. 1.4

ETOPS User's Guide: 2 Engine Aircraft: Ersion
No ratings yet
ETOPS User's Guide: 2 Engine Aircraft: Ersion
64 pages
ETOPS Maintenance Program Overview
No ratings yet
ETOPS Maintenance Program Overview
89 pages
ETOPS Operational Guidelines Guide
100% (9)
ETOPS Operational Guidelines Guide
388 pages
Understanding ETOPS Certification
No ratings yet
Understanding ETOPS Certification
2 pages
ETOPS Operations Overview for B738
No ratings yet
ETOPS Operations Overview for B738
50 pages
JetPlanUserManual PDF
0% (1)
JetPlanUserManual PDF
1,224 pages
ETOPS Training for 737-700W Dispatchers
100% (1)
ETOPS Training for 737-700W Dispatchers
59 pages
ETOPS Operations Policy Manual
No ratings yet
ETOPS Operations Policy Manual
44 pages
ETOPS Certification and Approval Guide
100% (6)
ETOPS Certification and Approval Guide
53 pages
ETOPS Certification and Approval Guide
100% (6)
ETOPS Certification and Approval Guide
99 pages
Understanding ETOPS Certification
100% (3)
Understanding ETOPS Certification
53 pages
Takeoff Safety Training Aid
100% (1)
Takeoff Safety Training Aid
201 pages
Getting To Grips With ETOPS
100% (6)
Getting To Grips With ETOPS
201 pages
ETOPS Training Course Overview
90% (10)
ETOPS Training Course Overview
67 pages
Comprehensive ETOPS Policy Overview
No ratings yet
Comprehensive ETOPS Policy Overview
36 pages
ETOPS Overview and Procedures for A320
100% (1)
ETOPS Overview and Procedures for A320
66 pages
ETOPS Maintenance Program Overview
No ratings yet
ETOPS Maintenance Program Overview
47 pages
GTG Etops Vol II Issue01
100% (7)
GTG Etops Vol II Issue01
46 pages
ETOPS Manual for Flight Crew
100% (2)
ETOPS Manual for Flight Crew
96 pages
B737 FMC Manual
No ratings yet
B737 FMC Manual
578 pages
ETOPS Flight Crew Guide Template
No ratings yet
ETOPS Flight Crew Guide Template
68 pages
Etops Manual A320-232, A321-232 v3 Dated 20 Apr 10
100% (2)
Etops Manual A320-232, A321-232 v3 Dated 20 Apr 10
44 pages
ETOPS: Extended Range Twin Engine Ops
No ratings yet
ETOPS: Extended Range Twin Engine Ops
45 pages
ETOPS Flight Planning Guidelines
No ratings yet
ETOPS Flight Planning Guidelines
31 pages
ETOPS Supplementary Training Guide
50% (2)
ETOPS Supplementary Training Guide
31 pages
ETOPS Manual for Saudi Arabian Airlines
100% (2)
ETOPS Manual for Saudi Arabian Airlines
74 pages
ForeFlight Dispatch Guide v17.8
No ratings yet
ForeFlight Dispatch Guide v17.8
505 pages
Etops 1
No ratings yet
Etops 1
9 pages
Understanding ETOPS Regulations in Aviation
No ratings yet
Understanding ETOPS Regulations in Aviation
231 pages
FMS Task Book
100% (1)
FMS Task Book
106 pages
Flight Planning and Monitoring PDF
No ratings yet
Flight Planning and Monitoring PDF
340 pages
CAE Oxford Aviation Academy - 030 Flight Performance & Planning 2 - Flight Planning and Monitoring (ATPL Ground Training Series) - 2014 PDF
100% (2)
CAE Oxford Aviation Academy - 030 Flight Performance & Planning 2 - Flight Planning and Monitoring (ATPL Ground Training Series) - 2014 PDF
340 pages
FMC System Update Manual 12.0
No ratings yet
FMC System Update Manual 12.0
560 pages
Flight Briefing for LFBP to EHBK
No ratings yet
Flight Briefing for LFBP to EHBK
72 pages
ForeFlight Dispatch Guide Overview
No ratings yet
ForeFlight Dispatch Guide Overview
394 pages
Extended Range Twin Engine Operations (ETOPS)
100% (1)
Extended Range Twin Engine Operations (ETOPS)
2 pages
EDTO Summary 2
No ratings yet
EDTO Summary 2
6 pages
Flight Management Computer System FMC Update 13.0 Reference Guide
100% (1)
Flight Management Computer System FMC Update 13.0 Reference Guide
558 pages
Understanding ETOPS and EDTO Concepts
No ratings yet
Understanding ETOPS and EDTO Concepts
49 pages
EDTO vs ETOPS: Flight Operations Guide
No ratings yet
EDTO vs ETOPS: Flight Operations Guide
31 pages
158 Aircraft Browser
No ratings yet
158 Aircraft Browser
13 pages
A320/A321 Advanced Systems Guide
No ratings yet
A320/A321 Advanced Systems Guide
67 pages
FlyBus A320 Operating Manual
100% (1)
FlyBus A320 Operating Manual
52 pages
684eaad8aa8b7
No ratings yet
684eaad8aa8b7
38 pages
Overview of Saudia's ETOPS Operations
50% (2)
Overview of Saudia's ETOPS Operations
112 pages
StartupBoeing ETOPS
No ratings yet
StartupBoeing ETOPS
7 pages
Understanding ETOPS Regulations
No ratings yet
Understanding ETOPS Regulations
1 page
ETOPS Flight Crew Training Guide
100% (1)
ETOPS Flight Crew Training Guide
32 pages
Japan Airlines ETOPS Training Manual
100% (2)
Japan Airlines ETOPS Training Manual
40 pages
Atp Sec Etops
100% (1)
Atp Sec Etops
6 pages
Understanding ETOPS Operations
67% (3)
Understanding ETOPS Operations
73 pages
Etops (R-2)
No ratings yet
Etops (R-2)
75 pages
ETOPS Certification and Procedures Guide
100% (3)
ETOPS Certification and Procedures Guide
69 pages
ETOPS in Long-Haul Aviation Explained
No ratings yet
ETOPS in Long-Haul Aviation Explained
1 page
MR TBO Demonstration Flight Overview
No ratings yet
MR TBO Demonstration Flight Overview
25 pages
New ETOPS Rule
No ratings yet
New ETOPS Rule
9 pages
Pilot's Guide 150-045240.N
100% (1)
Pilot's Guide 150-045240.N
510 pages
Airbus A318/A319 Systems Guide Vol 4
No ratings yet
Airbus A318/A319 Systems Guide Vol 4
67 pages