User Ifpl Basic Opt 570 v1 0

Lido/Flight
Version 5.7.0
Interactive Flight Planning Basic Procedures
User Manual, Version 1.0
February 10, 2012
Customer Documentation
Interactive Flight Planning - Basic Procedures
Copyright 2012 by Lufthansa Systems AG

Postal address:
Lufthansa Systems AG
Am Prime Parc 2
65479 Raunheim
Germany
Changes are periodically made to the information herein; these changes will be incorporated in
new editions of the publication. Lufthansa Systems AG hereinafter referred to as Lufthansa
Systems may make improvements and/or changes in the product(s) described in this publication
at any time.
Trademarks: Words that we have reason to believe constitute registered trademarks are
designated as such. However, neither the presence nor the absence of such designation should be
regarded as affecting the legal status of any trademark.
The documents are confidential and shall only be used for internal purposes by customers. The
respective confidentiality provisions agreed upon by each customer and Lufthansa Systems apply.
The documents shall not be disclosed to third parties. Anyone using these documents must take
appropriate security precautions to ensure their confidentiality at all times.
Readers' comments, suggestions and inquiries regarding our publications are explicitly welcome.
Our documentation team may be contacted at:

Email: documentation@lhsystems.com
The Lido Helpdesk may be contacted at:

Email: nav.services@lhsystems.com
Tel.: +49 (0) 69 696 4999
February 10, 2012 Page 2 of 218

Revision History
Version No. Date Reason for Change
V. 1.0 Feb 10, 2012 Initial issue of document for Lido/Flight version 5.7.0
Updates:
New layout for window 'Flight List' including improved
possibility to hide and unhide log messages
Consideration of minimum reserve fuel may be
activated/deactivated for inflight calculation
Changes are marked in blue.

Table of Contents
1 Introduction ............................................................................................................................... 7
2 Basic Procedures of Interactive Flight Planning ................................................................... 9
2.1 Overview........................................................................................................................... 9
2.2 Selecting Flight Records................................................................................................... 9
2.2.1 Selecting a Flight Record .......................................................................... 10
2.2.2 Searching for Flights in the Flight List ....................................................... 12
2.3 Setting up a Planning Parameter Scenario .................................................................... 13
2.3.1 Setting up a Planning Parameter Scenario ............................................... 13
2.3.2 Triggering Alternate Selection and Airport Suitability Check ..................... 17
2.4 Calculating a Flight ......................................................................................................... 19

2.4.1 Defining Route Options ............................................................................. 19
2.4.2 Calculating a Flight .................................................................................... 21
2.4.3 Defining Route Details............................................................................... 28
2.4.4 Reviewing and Modifying Route Details .................................................... 32

2.4.5 Route Validation Check ............................................................................. 33
2.4.6 Defining or Modifying Restrictions ............................................................. 34
2.4.7 Considering Natural Hazards (optional) .................................................... 37

2.5 Reviewing Flight Related Information............................................................................. 39
2.5.1 Reviewing Weather and NOTAM Information for DEP, DEST and ALTNs 40
2.5.2 Reviewing Weather and NOTAM Information for Additional Airports ........ 42
2.5.3 Reviewing Cost Information....................................................................... 45
2.6 Calculating a Reclearance Flight.................................................................................... 46

2.6.1 Overview.................................................................................................... 46
2.6.2 Calculating a Flight Using the Standard Reclearance Procedure or the

Decision Point Procedure .......................................................................... 48
2.6.3 Calculating a Flight Using the Reduced Contingency Fuel Procedure ...... 50
2.6.4 Optional: Performing an Automatic Reclearance Calculation.................... 53
2.6.5 Reviewing Results of Reclearance Calculation ......................................... 55

2.7 Flight Planning over AIRAC Change Dates.................................................................... 56

2.7.1 Recalculating a Flight with Modified ETD/ETA .......................................... 57
2.7.2 Recalculating a Flight Using Via Waypoints .............................................. 59
2.7.3 Recalculating a Flight Using a Via Waypoint Valid at 00:00 UTC.............. 61
3 Performing FPL/OFP Transmission ...................................................................................... 62
3.1 Workflow and Overview of Procedures .......................................................................... 62

3.2 Filing an OFP and Generating a Briefing Package......................................................... 64
3.3 Maintaining Additional Briefing Information .................................................................... 67
3.4 Transmitting a Briefing Package via Window 'Flight List' ............................................... 70
3.5 Sending Flight Plan Update Messages .......................................................................... 72
3.6 Removing a Briefing Package from the Server .............................................................. 75
3.7 Monitoring the Publishing Process ................................................................................. 76
4 Performing an Inflight Calculation ........................................................................................ 77
4.1 Calculation Parameters .................................................................................................. 77

4.2 Performing an Inflight Calculation................................................................................... 77
4.3 Reviewing Results of Inflight Calculation........................................................................ 80
5 Field and Button Description................................................................................................. 81
5.1 Overview......................................................................................................................... 81
5.2 Window 'Flight List' ......................................................................................................... 82
5.3 Window 'Planning Parameter'......................................................................................... 93
5.4 Window 'Alternate Information' ..................................................................................... 106
5.5 Window 'Analysis' ......................................................................................................... 108
5.6 Window 'Weather/NOTAM'........................................................................................... 125

5.7 Window 'Route Options' ............................................................................................... 133

5.7.1 Area 'Specific Selection Criteria'.............................................................. 134
5.7.2 Area 'Route Types' .................................................................................. 135
5.7.2.1 AUSOTS Tracks ................................................................ 137
5.7.2.2 NAT and NOR Tracks (OTS) ............................................. 138

5.7.2.3 South Atlantic Tracks (SAT) .............................................. 139
5.7.2.4 Polar Tracks (POL)/Arctic Tracks ...................................... 140
5.7.2.5 ATC Reroute Proposal (ATC RRP) ................................... 142
5.7.2.6 PACOTS Tracks ................................................................ 143

5.7.2.7 Predefined Routes/Playbook Routes/Coded Departure
Routes ............................................................................... 144
5.7.3 Area 'Optimization Criteria' ...................................................................... 152
5.8 Window 'Route Definition'............................................................................................. 153

5.9 Window 'Restrictions'.................................................................................................... 164
5.10 Window 'Reclearance' .................................................................................................. 174
5.11 Window 'Cost Viewer' ................................................................................................... 185
5.12 Window 'FPL/OFP Transmission' ................................................................................. 188
5.12.1 Window 'Briefing additional Info' .............................................................. 199
5.12.2 Window 'Detailed Package' ..................................................................... 205
5.13 Window 'Inflight Assistance' ......................................................................................... 208

1 Introduction
Abstract Interactive Flight Planning (IFPL) with Lido/Flight starts with the selection of
a flight from the flight list, which is followed by the creation of a planning
parameter scenario. Then the user can determine further parameters for
the flight plan calculation and choose from a number of optimization criteria
as well as routes to be considered. Lido/Flight calculates one or more
OFPs, which are ready to be filed and used for the generation of the
briefing package. The function 'FPL/OFP Transmission' supports users to:
Review OFP calculation results

Generate and file the ATS flight plan
Prepare and send a briefing package
Send update messages in case of changes, cancellation and delay
The briefing package may include additional briefing information which can
be transmitted via different media. Optionally an email function can be used
for attaching additionally relevant satellite images and significant weather
charts.
Disclaimer The documentation of Lido/Flight modules and features covers all features
currently available. Please note that this documentation shall only apply to
those modules or features which Lufthansa Systems provides to the
respective customer under an agreement between the parties. Nothing in
this documentation shall imply any rights to any modules or features
described herein. Please contact your Lufthansa Systems representative if
you have any questions.
Functional Options Some of the screenshots used in this handbook are composites of all
on Screenshots currently available options. Your airline may be subscribing to some and
not all of the options described herein. Some step-by-step instructions may
therefore not apply to you.
Before You Start Before you start with interactive flight planning, verify that these
prerequisites are fulfilled:
All flight data for the respective flight are available (received
automatically via SSIM load or OPS interface, or entered manually).
Flights have been assigned to an office / team by the shift manager.
For more details about shift management within Lido/Flight see the
documentation 'Shift Management Feature Description'.

Purpose of This manual provides a general view of the interactive flight planning
Document process with Lido/Flight. This process starts with the selection of a flight
from the flight list and ends with the calculated OFP ready to be sent to
respective authorities and to be used for the generation of the briefing
package.
As far as a deeper knowledge is required to use special functionalities to
their full extent this document refers to the customer documentation of the
respective feature.
Structure of This document consists of two main parts:

Document
The first part gives step-by-step instructions for calculating a flight
with Lido/Flight.
The second part is a detailed field and button description of the
graphical user interface used for these interactive flight planning
procedures.
Both parts are again divided into corresponding sections. Following graphic
illustrates the structure of this document.
Structure of Document

2 Basic Procedures of Interactive Flight Planning
2.1 Overview
Planning a Flight Interactive Flight Planning within Lido/Flight covers the following main
with Lido/Flight steps, which are described more precisely within subsequent chapters:
1. Select a flight record from the flight list.

See chapter 'Selecting Flight Records'.
2. Set up a planning parameter scenario.
See chapter 'Setting up a Planning Parameter Scenario'.
3. Calculate and select the flight route.
See chapter 'Calculating a Flight'.
4. Review flight related weather and NOTAM information.
See chapter 'Reviewing Flight Related Information.
5. Calculating a reclearance flight.
See chapter 'Calculating a Reclearance Flight.'
6. Perform FPL/OFP Transmission: Finally a flight is planned and ready to
be transmitted to ATC and used for the generation of a briefing
package.
See chapter 'Performing FPL/OFP Transmission'.
7. Perform an inflight calculation: See chapter 'Performing an Inflight
Calculation.'
2.2 Selecting Flight Records
Overview Usually you start your flight planning activities by consulting the list of flights
provided in window 'Flight List'. This list gives you an overview of flights to
be calculated as well as up-to-date flight operation information. Here, you
select your flight for flight planning calculations.
If the flight you are going to calculate is not available in the flight list, you
must create a new flight record and insert it into the flight list. For this
purpose window 'Flight Data' is provided (Path: 'Flight Planning' > 'Flight
Data' or 'Shift Mgmt' > 'Flight Data'). It is mandatory to connect a flight to
the flight list if you want to file the flight plan and / or generate briefing
documents.

2.2.1 Selecting a Flight Record
Selecting a 1. Open window 'Flight List'.

Flight Record
Path: 'Flight Planning' > 'Flight List'
or 'Shift Mgmt' > 'Flight List'
The layout of the window may differ according to your settings.
2. Optionally, adjust any of the filters in area 'Filter Definition' to specify

the flights displayed in table 'Flight List'.
Criterion Action
Office Select the appropriate office from the drop-down list.
Team Select the appropriate team from the drop-down list.
Status Select the appropriate flight status from the drop-down
list.
DEP Insert the IATA or ICAO airport code of the departure
airport.
DEST Insert the IATA or ICAO airport code of the destination
airport.
Period Select the appropriate period from drop-down list 'Period'.
If you select 'fix period', the fields 'From' and 'Till' become
editable. Adjust them to your needs.
Continued on next page

Selecting a Flight Record - Continued
3. Select a flight in table 'Flight List' with a click on the respective row.
To find the appropriate flight you can make use of any of the following
options:
Scan the flight list step-by-step.
Sort the flight list according to one criterion with a click in the
respective column header. To sort by multiple criteria, hold 'Ctrl' on
your keyboard while clicking in the respective column headers.
Use the color-coding of the flight list for orientation concerning the
processing status of each flight. You may use field 'Status' in area
'Filter Definition' to display only flights of one specific flight status.
For details about the color-coding see the field and button
description of window 'Flight List' within this document.
Search for specific flights using the search options in area
'Search Definition'. To do so, follow procedure 'Searching for Flights
in the Flight List'.
Select a flight, for which a log message is available. Click on the
respective message in table 'Log'. The corresponding flight will be
marked in table 'Flight List' automatically.
Note: Table 'Log' displays operational changes of flights currently displayed in
table 'Flight List'. The table is updated automatically.
A flight record is selected and can be used for further flight planning
calculations.

2.2.2 Searching for Flights in the Flight List
Introduction A special search function allows you to search flights within the flight list by
specifying certain search criteria.
Before You Start Before you start, verify that window 'Flight List' is open.
Searching for 1. Enter one or more search criteria in the respective field of area
Flights in the 'Search Definition'.
Flight List
You may use any of the following search criteria:

Airline (IATA or ICAO airline code)
Flight (flight number)
ATC C/S (ATC Callsign; optional feature)
DEP (IATA or ICAO code of departure airport)
DEST (IATA or ICAO code of destination airport)
STD (scheduled time of departure; format: DDhhmm, e.g. 241345)
2. Click on button 'Search'

to start the search.
The first flight in table 'Flight List' matching all entered search criteria is
marked. The status line shows how many flights are found altogether.
3. Navigate through your search results.

Click on button 'Next' to jump to the next flight in table 'Flight List'
matching the entered search criteria.
4. Optionally, click on button 'Clear Search' to clear all entry fields in area
'Search Definition'. You can now enter new criteria.
Flights have been searched for in the flight list.

2.3 Setting up a Planning Parameter Scenario
2.3.1 Setting up a Planning Parameter Scenario
Before You Start Before you start, verify that:

Window 'Flight List' is open.
The flight you are going to plan is selected in the flight list.
Setting up a 1. Open window 'Planning Parameter':

Planning Parameter
In the flight list right-click on the required flight to open the flight-related
Scenario
context menu. Select 'Edit Planning Parameters...' to load all available
details of this flight in window 'Planning Parameter'.
When accessing window 'Planning Parameter' from window 'Flight List',

a check process is automatically started that determines whether the
flight leg is a possible tankering flight. In this case an info box opens
and tells you which flight to plan first if you want the tankering additional
fuel to be based on the second leg.
For details about tankering
flights see document
'Tankering Feature
Description'.

Setting up a Planning Parameter Scenario - Continued
2. Select alternates and run an airport suitability check for all airports
affected by this flight. For details see procedure 'Triggering Alternate
Selection and Airport Suitability Check' in this chapter.
You may change the defined alternate cruise procedure (optional).
3. For calculating an ETOPS flight click on button 'PET / ETOPS' and the
following actions will be performed:
Window 'PET / ETOPS Parameter' opens.
The en-route alternates are selected automatically according to
predefined criteria.
The Airport Suitability Check is performed for en-route alternates.
The results of selection and check of en-route alternates are
displayed in window 'PET/ETOPS Parameter'. The lists of en-route
alternates can be adjusted here if necessary.
For more details about ETOPS calculations see document
'ETOPS Operations Feature Description'.
4. If necessary insert or change any of these planning parameters:

Runway at departure and / or destination airport
Taxi Time and/or Taxi Fuel: You can change the values individually
or synchronize them via the toggle 'Sync.'.
Note: Taxi Time is directly related with taxi out fuel via the stored fuel flows
inside the database, and even if field 'Taxi Fuel' is not visible, a change of
taxi time will result in a recalculation of taxi fuel (except toggle 'Sync.' is
visible, but deactivated).
The limit of 1 minute taxi out time must not be under-run; in that case a
message is given.
Priority regarding load or fuel in case of weight limitations
PIC Qualifier
Weight and Balance Data,
including Dry Operating Weight, Load, Estimated Zero Fuel Weight,
Maximum Allowable Takeoff Weight
Note: You may adjust the unit for TCAP, FOB, DOW, Load, ESTZFW, MALTOW,
MALLAW by selecting the respective value from the drop-down list 'Unit'.
Aircraft-related items: Aircraft registration and Performance
Correction Factor
En-route weight penalty (optional)
Fuel policy items. For details see documents 'Fuel Policy Feature
Description', and 'Leg Policy Feature Description.
Variable Fuel Reserve (entry field 'VFR').
Caution: Do not change any of the following data:
'AL', 'Flt.-No.', 'OS', 'ATC C/S', 'Date', 'DEP', 'STD', 'STA', 'DEST'.
Otherwise the flight will no longer be connected to the flight list
and thus it is not possible to file this flight and / or generate
briefing documents.

5. You may check weather and NOTAM information: Click on button

'WX/NOTAM' to open window 'Weather / NOTAM'. For details see
procedures in chapter 'Reviewing Flight Related Weather and NOTAM
Information'.
6. If the font color of the command button 'REMARK' is red, there is a

remark available for this flight. Click on button 'REMARK' to open
window 'Remarks'.
Upon request, the button 'REMARK' can be configured to indicate if the
remarks for this flight have been checked in window 'Remarks'. The
font color of the button will turn yellow if available remarks have been
checked. If already checked remarks are updated, the button will turn
red again.
If this option is configured, and if you continue creating the scenario
without checking available remarks, a message box will open when the
scenario is inserted.
7. After changing planning parameters, check the airports / runways once

more by clicking on button 'Recheck'.
The recheck compares the inserted aircraft equipment and PIC
qualification with the weather and NOTAM situation at departure,
destination and alternate airports. The checked time window is the
same as the one of the last Airport Suitability Check triggered by
clicking on button 'Initialize'.
The result of the recheck is displayed in the table 'List of Airports'.
Caution: If you click 'Initialize' instead of 'Recheck', the following of your

changes will be lost:
Policy for alternate selection (unless you have selected 'Sequence
by User'), best available time, aircraft registration, PIC
qualification, weight and balance data (DOW, Load, ESTZFW,
MALTOW, CGZFW).

8. Store the planning parameter scenario for this flight in the database by
clicking on button 'INSERT'.
The system checks if the EZFW exceeds the MZFW. If configured for
the customer respective manual intervention may be necessary.
All data currently displayed in window 'Planning Parameter' and if
applicable all data defined in window 'PET/ETOPS Parameter' are
stored in the database. If necessary, you may enter or edit remarks for
this scenario.
If Lido/Flight is configured to track
the checking of the remarks, and if
you insert the created scenario
without checking available
remarks, a message box will open:
Click on button 'CONTINUE' to insert the planning parameter

scenario without reviewing the remarks. The font color of button
'REMARK' turns yellow.
Click on button 'CANCEL' to go back to window 'Planning
Parameter' without inserting the scenario. The font color of button
'REMARK' is red.
Click on button 'REMARK' to open the window 'Dispatch Bulletin' to
view the remarks. When closing this window, you return to window
'Planning Parameter'. The font color of the button 'REMARK' turns
yellow.
A planning parameter scenario has been set up for this flight. Now you can
use this scenario for further flight planning calculations.

2.3.2 Triggering Alternate Selection and Airport Suitability Check
Before you Start Before you start, verify that the window 'Planning Parameter' is open and
basic flight data is loaded.
For more details about the Airport Suitability Check, see document 'Airport
Suitability Check Feature Description'.
Triggering 1. Verify the fuel policy that determines the alternate sequence (default
Alternate Selection setting: Minimum ALTN Fuel).
and Airport If you select option 'Sequence by User', enter one or more destination
Suitability Check alternates (fields 'Alternates: 1-4').
2. Click the button 'Initialize' to trigger the airport suitability check for
departure, destination, takeoff alternate(s), and destination alternates.
The result of the check is shown in the 'List of Airports'.
If configured, the system checks if operating without destination
alternate airports is possible. If so, the alternate sequence changes to
'No ALTN'. Please check always the NOTAM information for the
destination airport, also if airport is found suitable.
3. You may perform a Weather/NOTAM check for test purposes and to

survey results: Click the button 'WX NTM CHK' to open the window
'Airport Suitability Weather NOTAM TEST'.

Triggering Alternate Selection and Airport Suitability Check - Continued
4. You may enter or change alternates manually or adjust the takeoff

alternate airport in the field 'TKOF'.
5. The system optimizes the alternate route as minimum fuel track (MFT).
You may define the alternate route for one or more alternates. To do so
click the right mouse button in the entry field of the respective alternate
airport. The window 'Alternate Information' opens; define the alternate
route, specify the flight level to the alternate and modify the runway of
the alternate airport. You may open the window 'List of Routes
Selection' with the button 'List of Routes ' and select all available
routes. Click 'Append' to transfer selected route to the window
'Alternate Information'.
6. If you use the optional function 'Fix Alternate Route' the system
automatically checks for a maintained alternate route, if the toggle
'Alternate route auto select ON' is set.
You may de-activate the automatic selection of a fix predefined
alternate route by setting the toggle 'Alternate route auto select OFF'.
It is required to deleted the content of the window using the button
'Remove +++'.
If the function of calculating a VIA alternate scenario is active: You may
enter an airport to be checked as via alternate. To do so use the drop-
down list below the 'Sequence' to change to 'VIA Alternate' and insert
the 4-letter code of desired airport in the field for alternate. The ASC
checks this airport with quality 'VIA_ALTN'.
7. Trigger an Airport Suitability Recheck with the button 'Recheck' to

include all manual changes in a check regarding weather and NOTAM
situation. The result of the recheck will be shown in the 'List of Airports'.
Note: If you click 'INITIALIZE', the manual entries for the alternates may be overruled
by the automatic selection (except for option 'Sequence by User').
Alternates are selected and an airport suitability check has been triggered.
Now you are ready to go on with setting up the planning parameter
scenario.

2.4 Calculating a Flight
Introduction Based on the planning parameter scenario the dispatcher can determine
further parameters, routes and optimization criteria for a specific flight and
finally calculate the flight plan.
The calculation of a flight may include the following procedures:
Defining Route Options

Calculating a Flight
Defining Route Details
Reviewing or Modifying Route Details
Defining of Modifying Restrictions
2.4.1 Defining Route Options
Introduction For the optimization of the route between departure airport and destination
airport, Lido/Flight offers a variety of options for the calculation of routes. In
window 'Route Options' the dispatcher can define the required route types
and optimization criteria. Depending on the number of the selected routes
and optimization criteria one or several routes are created and set up for
calculation.

Window 'Planning Parameter' is open.
A planning parameter scenario has been inserted for the flight you
are going to plan.

Defining Route 1. Click on button 'ANALYSIS'.

Options Window 'Analysis' opens containing all details for your flight, which are
available up to now. Upon the first opening additionally window 'Route
Options' opens.
2. Define one or more route types to be used for flight plan calculations:
Route Type Button

Predefined routes PRED
North Atlantic Tracks (NAT) OTS
Northern Organized Tracks (NOR) OTS
South Atlantic Tracks SAT
Polar Tracks POL
ATC Re Routing Proposal ATC RRP
Note: This option is only available for flights, which have been
calculated and filed before, and for which ATC has sent
a rerouting proposal.
Pacific Tracks PACOTS

Australian Tracks AUSOTS

Defining Route Options - Continued
3. Define one or more optimization criteria to be used for flight plan

calculations. The following optimization criteria can be selected:
Consideration of Restrictions
No Yes No Yes
Non-ETOPS ETOPS
Minimum Cost Track MCT MCT/R E/MCT E/MCT/R
Minimum Fuel Track MFT MFT/R E/MFT E/MFT/R
Minimum Time Track MTT MTT/R E/MTT E/MTT/R
Minimum Distance Track MDT MDT/R E/MDT E/MDT/R
For more details about optimization criteria, see document

'Optimization' Feature Description'.
4. Click on button 'OK' to close window 'Route Options' and return to

window 'Analysis'.
Route options have been defined. For every route and/or optimization
criterion selected a route is created and displayed in the table of window
'Analysis'. To continue with flight planning and calculate the created routes
follow procedure 'Calculating a Flight'.
2.4.2 Calculating a Flight

A planning parameter scenario has been inserted for the flight you
are going to plan.
Route options have been defined and one or more routes have been
created.
Window 'Analysis' is open displaying all details for your flight, which
are available up to now.

Calculating a Flight 1. For every route and/or optimization criterion defined in window
'Route Option' a route has been created and is displayed in the table of
window 'Analysis'.
For each route the following details are displayed:
ROUTE, REG, EST ZFW, MALTOW, MALLAW.
You may specify or adjust any of these values manually:
EST ZFW, ADDFU, MALLAW, MAX FL.
2. If required define/adjust additional parameters for the calculation:

Parameters How to Define/Adjust:
1. Operational Select respective value from drop-down list 'Operational
case Case'. You may use button 'Set to Def.' to retrieve the
default settings for operational case, climb, cruise, and
descent procedures.
2. Procedure / Select respective value from drop-down list 'Procedure'.
Speed for
Specify a thrust rating by selecting the respective value
climb and/or
from drop-down list 'Thrust Rating'.
cruise and/or
Options depend on the values provided within performance
descent
tables for respective aircraft performance type by
phase
Lufthansa Systems, e.g.: F (full thrust), R1 (derate 1),
R2 (derate 2).
For the cruise phase additionally determine the speed
within fixed MACH airspace / airways by selecting
respective option from drop-down list 'Fixed MN
Airspace/Airway.
Enable/disable the VSOPS functionality by selecting 'ON'
or 'OFF' from drop-down list 'VSOPS'.
For details about speed procedures see document 'Speed
Procedures Feature Description'.

Calculating a Flight Continued
Parameters How to Define/Adjust:

3. Values for Enter the respective value into field 'REM Fuel' or 'Fuel
remaining fuel Gravity'.
and fuel gravity
4. Weather Select the respective value from drop-down list
prognosis 'Prognosis'. For available options see field and button
description of window 'Analysis'.
5. Restrictions to Click on button 'Restriction' to open window
be considered 'Restrictions', where you can define restrictions to be
considered.
Note: These restrictions are considered by all calculation
methods; for the route optimization criteria the
following options must be selected: MCT/R, MFT/R,
MTT/R, and MDT/R.
6. Optimization Click on button 'Opt
Parameters Param.' to open
window 'Optimization
Parameter'. You may
deactivate or alter the
defined minimum
cruise times.
If you use the option for calculating the CO2 emission

costs, you may alter the predefined emission index and
the price for CO2 allowances for the current flight.
7. Routing Click on button 'RTE DEF' to open window 'Route
Definition', where you can define several details for the
route. For details see procedure 'Defining Route
Details'.
8. Maximum Flight Enter a value for the maximum flight level into the
Level respective row of the OFP overview.
Note: The system checks that the value does not exceed
the limit for the aircraft as maintained in window
'Aircraft Operator Maintenance'.

3. Optionally you may select the toggle 'In background', which enables the
calculation in background and allows you to proceed working with
Lido/Flight while calculations are being performed.
Click on button 'Analysis' to start the calculation of the flight plan.
Flight plans are calculated for all specified routes.
If a calculation results in a reduction of PLNZFW compared to EZFW,

the limited weights and the weight causing the limitation are displayed
in red color.
4. If you have calculated two or more routes, you can sort them by any
criterion displayed in the table.
To do so, select the appropriate check box of the respective table row.
That way you can easily find the route with the lowest value of the
selected criterion.

5. Review detailed results of each OFP calculation. Always mark the

required OFP in the table of window 'Analysis', which is then
highlighted with blue background color.
The table describes the functions for reviewing OFP details.
OFP Information How to Review Information

OFP Detail Description Click on button 'OFP' to open window 'OFP'.
Routing of OFP Click on button 'Route Survey' to open window
'Route Survey' showing a short route description of
the selected OFP.
Note: You can choose between two options for
displaying the routing: ATS flight plan route or
waypoint sequence. To specify the type set the
toggle 'Route Display' in window 'Analysis'
respectively.
Alternates including Click on button 'ALTN Survey' to open window
Alternate Routing 'Alternate Survey'.
Graphical Click on button 'Graphic' to open window 'Flight
representation of Planning Graphic Window'.
horizontal routing
Optionally click on button 'Zoom' to use the zoom
function and/or click on button 'Menu' to use the
menu. For details see field and button description of
window 'Analysis'.
Graphical Select the respective value ('Height', 'Temp', 'Fuel')
representation of from the drop-down list next to button 'Menu'. 'Map'
vertical routing, is set as default.
temperature, and/or fuel
Note: Open graphic display must be closed with button
consumption 'OFF' to continue with planning.
Restrictions considered Click on button 'Restriction view.' to open window
by and having an effect 'Restriction Viewer' displaying restrictions for
on calculations individual segments of the route.
Caution: Red font color of button 'Restriction
view' indicates unspecified
restrictions and prevents filing an
OFP. Open window
'Restriction View' to check for
unspecified restrictions.

Calculating a Flight - Continued
OFP Information How to Review Information
'More Info' Click on button 'More Info' to open an info box

displaying:
Initials of the user, who calculated this route,
Tankering information (for tankering flights
only)
Costs Click on button 'COSTS' to open window
'Cost Viewer' displaying a detailed list of ATC
charges.
Optimization Click on button 'Opt Param.' to open window
parameters 'Optimization Parameter'. You may deactivate
or alter the defined minimum cruise times.
Results of ETOPS Click on button 'ETOPS' to open window
calculations 'PET/ETOPS Output'.
6. Optionally adjust the routing of one or more OFPs.

To do so, click on button 'RTE DEF' to open window 'Route Definition',
and follow procedure 'Reviewing or Modifying Route Details'.
When you have completed your adjustments, click on button
'ANALYSIS' to return to window 'Analysis'.
7. Optionally review additional information:

Click on button 'WX/NOTAM' to open window 'Weather/NOTAM',
where you can retrieve weather and NOTAM information about
airports and airspace.
Click on button 'A/C DEV' if the font color is yellow, indicating that
there is a MEL/CDL deviation for this aircraft. Window 'List of
Aircraft Deviations' opens in read-only mode, displaying all
MEL/CDL deviation(s) for the aircraft.
For details see document 'MEL/CDL Automation Feature
Description'.
Click on button 'REMARK' if the font color is red, indicating that a
remark is available for this flight.
Window 'Remarks' opens displaying information available for this
flight. You may enter and edit remarks.

Calculating a Flight - Continued
8. Optionally edit the overview of OFPs in the table:

To remove an OFP:
Mark the respective row and click on button 'Remove OFP'.
To copy an OFP for further processing:
Mark the respective row and right-click on that row.
Window 'Copy Control Panel' opens, where you can specify which
item(s) of that OFP shall be transferred (options: flight level, cruise
speed, SID/STAR, ADDFU, MAX FL).
Click on button 'OK' in window 'Copy Control Panel'.
A new row is generated in the table of window 'Analysis'. The
purple color of the route name indicates that this OFP is a copy.
Optionally modify any attributes of the route. Then click on button
'Analysis' to trigger a flight planning calculation.
9. Optionally perform a tankering calculation if applicable.

To do so, click on button 'Tankering'. Window 'Tankering' opens,
where you can initiate the tankering calculation based on suggested
values for tankering fuel. For details see document 'Tankering
Feature Description'.
10. Finally click on button 'Recheck' to trigger an Airport Suitability Recheck

for the airports concerned.
Window 'Recheck' opens displaying the results of the check.
For details see document 'Airport Suitability Check Feature
Description'.
Depending on the result of the recheck you should revise the OFP.
One or more OFP(s) have been calculated, which are ready to be filed
and/or sent.
Continue with the transmission of the flight plan and briefing package.

2.4.3 Defining Route Details
Introduction Window 'Route Definition' allows the user to initially define route details for
a planned scenario prior to calculating the flight in window 'Analysis'. For
example it is possible to define waypoints, flight levels, cruise procedures,
etc., to be used for the calculation of a route.
Before You Start Before you start defining route details, verify that a planning scenario for
the flight has been inserted in window 'Planning Parameter', i.e. the status
of the flight is at least 'FP: 1'.
Defining Route 1. Open window 'Route Definition'.

Details
Path: 'Flight Planning' > 'Flight List' > flight-related context menu
'Review Route Definition...'
or 'Flight Planning' > 'Flight List' > flight-related context menu
'Edit Planning Parameters...' > button 'RTE DEF'
2. If you come from window 'Planning Parameter' and if you just inserted
the planning parameter scenario, it will be displayed upon opening of
window 'Route Definition'.
If you come from window 'Flight List', retrieve the planning scenario for
the flight from the database by clicking on button 'SELECT'.

Defining Route Details - Continued
3. Define routing details in the table according to your requirements.

These details may include waypoints, flight levels, cruise procedures,
etc.
If the routing includes free flight segments, it might be necessary to
adjust the flight level to the flight levels of the connecting route
segments.
Caution: When you manually adjust a single flight level in this table, be
aware that the following lines will be filled automatically with the
same value. You will have to reset the flight level of the
following lines to the original values. The automatic filling
process will stop only if there is a change in flight level unit.
In the following, examples for possible route definitions are given:
What is defined? Example
PRED:
The name of the predefined
route to be used is entered.
During calculation of the route,
all waypoints of the PRED are
automatically retrieved by the
system.
OTS Track:
The OTS track 'G' is to be used
between waypoints MALOT and
STEAM.
Before Calculation:
Definition of OTS Track to be Used
After Calculation:
Waypoints are Automatically Retrieved

4. You may use available predefined route portions from the database
(e.g. company routes or officially published tracks). To do so, click on
button 'List of Routes' to open window 'List of Routes'. Click on drop-
down list menu 'Type', select e.g. 'Company Route' and click on button
'SELECT' to display all available routes.
Click on button 'APPEND' to return to and transfer the selected route to

window 'Route Definition'.
5. If applicable, define any of the following calculation parameters:
Prognosis of Upper Air Data

Operational Case
Fixed MN Airspace/Airway Information
VSOPS
Optimization Mode (MCT, MTT, MDT, MTT)
ETOPS conditions (ETOPS On/Off)
6. You may define the following data:
Maximum flight level in field 'MAX FL'

Optimization parameters (default minimum cruise times) in window
'Optimization Parameter' by clicking button 'Opt Param'
Restrictions in window 'Restrictions' to be considered during
calculation by clicking button 'Restriction'

7. Start the calculation of your defined route with a click on button

'Calculate'. The details of the calculated route are displayed in the table
as follows:
If optional feature Route Validation Check is configured, the defined

route is automatically checked for invalid waypoints. For details and
handling options see chapter 'Route Validation Check' in this
document.
8. If you want to insert the defined route into the database, click on button
'INSERT RTE'. The defined route can then be selected temporarily as
predefined route (PRED) via window 'Analysis' >
button 'Route Options'.
9. You may review the OFP: Click on button 'ANALYSIS' to open window
'Analysis'. The OFP of the defined route is marked with the designator
'DEFRTE'. You may now continue flight planning.
Route details have been defined and the route has been calculated.

2.4.4 Reviewing and Modifying Route Details
Introduction After having calculated a flight it is possible to review and modify the route
details for this flight, e.g. to review waypoints, flight levels, and optimization
criteria.
Before You Start Before you start, verify that window 'Analysis' is open and one or more
OFPs have been calculated.
Reviewing and 1. Select the OFP for which you want to review and modify route details.
Modifying Route
Details 2. Open window 'Route Definition' with a click on button 'RTE DEF'.
Window 'Route Definition' opens in 'Entry Mode' displaying detailed
information on the routing for the selected OFP.
3. You may review the route details. To do so, click on toggle 'Entry Mode'
to switch to the 'Display Mode'.
4. You may modify the route details in the table according to your
requirements (including waypoints, flight levels etc.). See that 'Entry
Mode' is activated.
Caution: When you manually adjust a single flight level in this table, be
aware that the following lines will be filled automatically with
the same value. You will have to reset the flight level of the
following lines to the original values. The automatic filling
process will stop only if there is a change in flight level unit
(e.g. to meters).
To select available predefined route portions from the database (e.g.

company routes or officially published tracks), open window 'List of
Routes and follow procedure 'Defining Route Details' given above.

Reviewing and Modifying Route Details - Continued
5. You may modify calculation parameters as e.g. Operational Case,

VSOPS or ETOPS conditions, and data as e.g. Maximum flight level or
restrictions. For a complete list of all parameters or data that can be
modified, please see procedure 'Defining Route Details'.
6. You may now click on button 'Calculate' to calculate your flight plan
according to the new settings. Go to window 'Analysis' to view the OFP
of the defined route with designator 'DEFRTE', and continue flight
planning.
Route details have been reviewed and modified. An OFP has been
recalculated.
2.4.5 Route Validation Check
Route Validation Prior to the calculation of a manually defined or modified route, the
Check application can be configured to perform a validation check of the defined
route. Thus errors due to incorrectly entered waypoints can be avoided.
This feature is optional and has to be configured by Lufthansa Systems on
customer request.
If configured, Lido/Flight will check the manually defined route on:
Duplicate waypoint(s), and
Inadequate Track Deviation (compared to a configurable track
deviation value)
The route validation check is performed in all user interfaces, in which the
user can manually enter waypoints and define a route (e.g. 'Route
Definition', 'Reclearance'). The check is triggered automatically before the
calculation (or recalculation) of the defined route and runs in the
background.
For more details on this subject see document 'Interactive Flight Planning -
Basic Procedures Functional Description'.

Display of Invalid If any invalid waypoints are found on a planned route, the waypoint codes
Waypoints are highlighted in red color in the respective flight planning window.
Additionally, the list 'Invalid Waypoints' opens and displays all invalid
waypoints and the reason why they are found invalid:
The user has the following options:

Ignore the list and continue the flight planning in the initial window:
Click on button 'CONTINUE' to close the list and start the flight
planning calculation.
Print the list for later reference.
Correct the listed waypoints in the initial flight planning window:
Keep the list open for your reference, or click on 'CANCEL' to close it.
Correct the waypoints in the initial flight planning window and restart
the calculation of the route.
A new calculation of the defined route will trigger another route validation
check.
2.4.6 Defining or Modifying Restrictions
Introduction Window 'Restrictions' allows the user to define restrictions before OFP
calculation and to review restriction settings of already calculated OFPs.
Various rules can be activated/ deactivated to consider/not consider
aspects of flight route calculation.
Restriction settings are applied to route types PRED, OTS as well as to all
optimization criteria considering restrictions, e.g. MCT/R, MFT/R, MDT/R,
MTT/R. All other optimization criteria ignore settings in window
'Restrictions'.
The following procedure describes step-by-step instructions provided that
all available functions are enabled. Your airline may be subscribing to some
and not all of the functions described herein. Some steps may therefore not
apply to you.
Default restrictions are NOTAM, Traffic Rights, AIP and special time
restrictions for the segments.

Before You Start Before you start verify the following:

A flight planning scenario is inserted in window 'Planning Parameter'.
Window 'Analysis' is open and flight data is loaded.
One or more optimization criteria considering restrictions (MCT/R, MFT/R,
MDT/R, MTT/R, etc.), PREDs or OTS routes are selected.
Defining or 1. Open window 'Restrictions'.

Modifying
Path: 'Flight Planning' > 'Analysis' > button 'Restriction '
Restrictions
2. For defining routing elements which are to be excluded from flight

calculation, define data in one or more of the following fields:
Segment Route Waypoint
Country Airspace FIR/UIR
For example, if you want to exclude a certain route segment from the
calculation, do the following:
Enter the 'From' and 'To waypoint' of the segment to be excluded in
table 'Segment' and click button 'OK'. Window 'Restrictions' closes and
you return to window 'Analysis'. During flight calculation, the entered
segment is not considered.

Defining or Modifying Restrictions - Continued
3. For defining Terminal Procedure rules, set the rules according to your
needs in area 'Terminal Procedure Rules'. Disabled rules are not
considered during flight calculation.
For more information, see document 'Terminal Procedure Feature
Description'.
4. For defining AIP rules, set the rules according to your needs in area
'AIP Rules'. Disabled rules are not considered during flight calculation.
5. For defining special time rules, make corresponding selections in area

'Special Time Rules'. Per default, 'Use Weekend Rules' is selected in
fields 'General Rule' and 'Country Specific'.
6. NOTAM and Traffic Right restrictions are considered during flight

calculation per default. Deselect the corresponding check boxes if you
do not want to consider NOTAM and/or Traffic Right restrictions.
In table 'Except' you can define exceptions from the general setting. For
NOTAMs, indicate NOTAM publisher and NOTAM code; for Traffic
Rights indicate the country.
Example: If NOTAM restrictions are to be considered (toggle is set to 'Yes'),
you can indicate NOTAMs which are not to be considered during
flight planning.
7. Define if the terrain clearance check should be done for the main routing
during flight calculation. By default the check is activated. For more
information, see document 'En-route Terrain Analysis User Manual'.
8. Define if traffic flow restrictions should be considered during flight
calculation.
You can either deactivate all restrictions currently available in Lido/Flight
collectively or you can deactivate certain restrictions individually. For
more information, see document 'Traffic Flow Restriction (TFR) User
Manual'.
9. You can exclude Free Flight areas of airspace from flight calculation by
entering the name of the airspace in table 'except Free Flight Airspace'.
Optionally use wildcard '%' and press the 'Enter' key. A list window
opens displaying all matching areas of airspace.
For more information, see document 'Free Flight Feature Description'.
10. If configured, define the way in which natural hazards of types Volcanic
Ash Clouds, Tropical Cyclones and Extremely Cold Temperatures are to
be considered during flight planning. For detailed information, refer to
chapter 'Considering Natural Hazards'.
11. Click on button 'OK'. Window 'Restrictions' closes.
Restrictions have been defined and are considered during OFP calculation.

2.4.7 Considering Natural Hazards (optional)
Introduction Lido/Flight provides the possibility to consider following types of natural

hazards during flight planning:
Official volcanic ash clouds (VAA)
Company defined volcanic ash clouds (company VAA)
Tropical cyclones (TC)
Extremely low temperatures (Cold)
This feature is optional and needs to be configured by Lufthansa Systems
on customer request.
Settings Following default settings are available on how to use natural hazard data
during flight planning:
Setting Description
Disabled Data on natural hazard is not considered at all.
No rerouting Hazard Tracking mode is activated, i.e. segments affected by

the natural hazard under consideration are internally tracked
by Lido/Flight and can be visualized in MAPS.
Rerouting Hazard Avoidance mode is activated, i.e. segments affected

by the natural hazard under consideration are closed at the
affected flight levels and a rerouting is triggered. During
optimization, Lido/Flight ignores closed segments and plans a
flight track around such areas.
Affected areas can be visualized in MAPS.
The default setting as requested by the customer is reflected in window

'Restrictions'. However, the dispatcher is able to overrule the defined setting
during flight planning.
Exceptions are company VAA with aviation code 'HIGH' and 'LOW'. Here,
the setting is fixed and cannot be changed:
Company VAA with Setting

code
HIGH 'Rerouting', i.e. Hazard Avoidance mode is activated.
LOW 'No rerouting'; i.e. Hazard Tracking mode is

activated.

Considering 1. Open the window 'Restrictions'.

Natural Hazards
2. To change the default setting for hazard type 'Official VAA', select the
corresponding option in drop-down list 'VA'.
If enabled, Lido/Flight considers VAA with ICAO aviation color code
'ORANGE', 'RED', and with code 'N/G', i.e. no color code is given. For
further information on the aviation color codes, see document
'Interactive Flight Planning - Functional Description'.
The selected option of how to consider VAA applies equally to all three
color codes.
3. To change the default setting for 'Company VAA' with aviation code
'MEDIUM', select the corresponding option in drop-down list 'C-VA'
The setting for 'Company VAA' with aviation codes 'HIGH' and 'LOW' is
fixed and cannot be changed here.
However, the setting for these types of hazard only applies if an option
other than 'Disabled' is selected from drop-down list 'C-VA'. If option
'Disabled' is selected, company VAA are not considered at all
independent of the aviation code.
4. To change the default setting for hazard type 'Tropical Cyclone', select
the corresponding option in drop-down list 'TC'.
5. To change the default setting for hazard type 'Extremely Low
Temperatures', select the corresponding option in drop-down list 'Cold'.
6. Click button 'OK' to close window 'Restrictions'.
Natural hazards are considered during flight planning according to the

defined settings.

2.5 Reviewing Flight Related Information
Flight Related Following procedures describe how to review the following flight related
Information information, which was considered in flight calculation:
Weather and NOTAM information for departure, destination and
alternate airports, and for additional airports
Cost information

2.5.1 Reviewing Weather and NOTAM Information

for DEP, DEST and ALTNs
Before You Start Following procedure describes how to review weather and NOTAM
information for departure, destination and alternates.
Before you start, verify that flight data are loaded within one of the windows
'Planning Parameter' or 'Analysis'.
Reviewing 1. Open window 'Weather/NOTAM'.

Information for
Path: 'Flight Planning' > 'Planning Parameter' > button 'WX/NOTAM'
DEP, DEST and
ALTNs or 'Flight Planning' > 'Analysis' > 'button 'WX/NOTAM'
The index card 'Weather/NOTAM' is selected and following airports are
listed within the list box 'Airports':
Departure
Destination
All alternates displayed in window 'Planning Parameter', panel
'Alternates' (1 4)
2. Select one of the listed airports.

Relevant weather messages and NOTAMs for this airport are
displayed within the display field.
Airport Information is displayed in the airport information line
above the display field.

Reviewing Information for DEP, DEST and ALTNs - Continued
3. If you want to see additional information for the airport currently

selected, click on button 'MORE'.
The display field is split into two parts. The upper part displays additional
airport information, namely landing and takeoff minima and additional
remarks. It can be defined which weather minima are displayed for
which type of operation as well as the sequence in which they are
displayed. However, company minima and state-published minima of
the same type of operation are always displayed in pairs if available.
Possible minima are ETOPS, ALTN, LDG and TKOF minima. If an OFP
has not yet been calculated, only minima for the operation types TKOF,
LDG and ALT are displayed.
The lower part displays relevant weather and NOTAM information.
4. If you want to see information for additional Alternates, click on button

'SELECT ALTN'.
All alternate airports available for the given combination of aircraft
registration and destination are now listed within the list box 'Airports'.
Select the airport you want to see information for.
Relevant weather messages and NOTAMs for this airport are displayed.
5. If you want to see information for any other airport, click into the first free
field of list box 'Airports', enter the respective airport code and press the
'TAB' key. Relevant weather messages and NOTAMs for this airport are
displayed.
6. Click on button 'CLOSE' to close window 'Weather/NOTAM'.
Weather and NOTAM information for DEP, DEST, ALTNs has been
reviewed.

2.5.2 Reviewing Weather and NOTAM Information

for Additional Airports
Before You Start Following procedure describes how to review information for additional
airports somehow related to a certain flight.
Before you start, verify that:
Flight data are loaded in window 'Analysis'
One or more OFPs have been calculated.
Note: Information for additional airports are only available via window 'Analysis' and after at
least one OFP has been calculated, because most of the additional airports depend
on the particular routing of an OFP.

Reviewing 1. Open window 'Weather/NOTAM'.

Information for
Path: 'Flight Planning' > 'Analysis' > 'button 'WX/NOTAM'
Additional Airports
2. Select index card 'Weather/NOTAM add. Airports'.
Select a value from the drop-down list 'OFP No', because most of the
additional airports depend on the particular routing of an OFP. The
numbers offered within this list correspond to the numbers of the OFPs
displayed in window 'Analysis'.
Check boxes for all types of additional airports that are available for the
current flight are activated.
3. Select one or more check box(es) to display additional airports of

respective types.
Depending on the currently calculated flight, the following airport types
may be available:
Takeoff Alternate
Via Alternate
Reclearance Airport
Reclearance Alternate
Reclearance Fuel En-route Airport
Note: If the RAP-ERA has been inserted by the user, this airport is displayed.
If the airport has been selected automatically by the system, the airport
used in calculation is displayed.
ETOPS Adequate Airport

ETOPS Suitable Airport
ETOPS Available Airport
Fuel En-route Alternate (ERA)
Note: If the ERA has been inserted by the user, this airport is displayed. If the
airport has been selected automatically by the system, the airport used
in calculation is displayed.
Inflight Destination
Inflight Alternate
Inflight via-Alternate
For a detailed description of the conditions under which certain airport
types are available see chapter 'Functional Description' earlier in this
document.
All airports of selected type(s) are displayed within the list box
'Airports'. They are arranged in groups according to their type.

Reviewing Information for Additional Airports - Continued
4. Select one of the listed airports.

Relevant weather messages and NOTAMs for this airport are
displayed within the display field.
Airport Information is displayed above the display field.
5. If you want to see additional information for the airport currently

selected, click on button 'MORE'.
The display field is split into two parts. The upper part displays additional
airport information, namely landing and takeoff minima and additional
remarks. It can be defined which weather minima are displayed as well
as the sequence in which they are displayed. Possible minima are
ETOPS, ALTN, LDG and TKOF minima.
The lower part displays relevant weather and NOTAM information.
6. Click on button 'CLOSE'.

Window 'Weather/NOTAM' is closed.
Weather and NOTAM information for additional airports has been reviewed.

2.5.3 Reviewing Cost Information
Before you Start Before you start verify that:

Flight data are loaded in window 'Analysis'
One or more OFPs have been calculated.
Reviewing Cost 1. Open window 'Cost Viewer' by the button 'COSTS'.

Information after
Flight Calculation
2. Review the costs as shown for ATC charges.
3. If the function for calculating the emission trading costs for CO2 has
been subscribed you may review the following data:
Fuel consumption
Emission of CO2
Costs for CO2 emission
4. You may print the shown data.
Cost information of calculated flight has been reviewed.

2.6 Calculating a Reclearance Flight
2.6.1 Overview
Workflow of Originating from a regular calculated OFP, for a reclearance calculation the
Reclearance dispatcher has to proceed as follows:
Calculation
1. Select a reclearance waypoint
2. Define a reclearance airport; optionally, for the standard reclearance
procedure define a reclearance alternate airport
3. Trigger an Airport Suitability Check for the RAP and optionally for the
RAP alternate. The system selects an RAP automatically.
The calculation results are displayed for review as:
Basic OFP
Recleared OFP to destination, labeled as 'RCL DEST'
OFP to the reclearance airport, labeled as 'RAP'
The Airport Suitability Check is performed according to the policy defined for
the airline. Lido/Flight offers different types of airport suitability checks: The
policies 'Standard', and according to the requirements of JAA, FAA and
CASA. For detailed information please refer to the respective feature
description 'Airport Suitability Check'.
If optional feature 'Route Validation Check' is configured, the defined route
from decision point to reclearance airport will be checked in the
background on invalid waypoints prior to the calculation. For details and
handling options see chapter 'Route Validation Check' in this document.
Warning in Case of Under specific conditions, it may occur that for reclearance flights Lido/Flight
Exceeding the calculates extra fuel/additional fuel that exceed aircraft limits like TCAP,
Weight Limits MLW and MTOW.
This message is displayed after
the calculation of a reclearance
flight in the following cases:
Planned Landing Weight

exceeds MLW
Block fuel exceeds the
TCAP
Planned TOW exceeds
the MTOW
In case of a message click on button 'OK' to close the message window.
Change the calculation parameter and re-calculate the flight until the weight
limits are kept.

Overview of The figure compares the main steps of a manual and automatic reclearance
Procedures calculation. The following procedures are described in detail:
1. Reclearance: Calculating a reclearance flight
Automatic Reclearance (optional function):
Performing an automatic reclearance calculation
Reviewing Results of Reclearance Calculation in the
'Analysis' Window
Workflow of Reclearance and Automatic Reclearance Calculation

2.6.2 Calculating a Flight Using the Standard Reclearance Procedure or

the Decision Point Procedure

Window 'Analysis' is open.
One or more OFP(s) have been calculated.
The OFP for calculating a reclearance flight is selected.
Calculating a 1. Open window 'Reclearance' using the button 'RECLEARANCE'.

Reclearance Flight
The copy control panel opens showing
parameter of the vertical profile.
Not selected parameter will be
optimized in reclearance calculation.
Selected parameter is copied from
the basic OFP as fix value.
Example:
If you select flight level, the cruise flight level in
reclearance calculation remains as optimized in
calculation of basic OFP.
Make your selection.

Quit your selection with 'OK'; the 'Reclearance' window opens.
The basic OFP as a sequence of waypoints is displayed in the column
'Route (basic OFP)'.
2. Select the desired reclearance waypoint; it is transferred into the table

(entry mode). This waypoint defines the intersection of the basic route to
the reclearance point.
Insert the desired reclearance airport (RAP) in the field 'RAP' and
optionally a reclearance alternate in the field 'RAP-ALTN'.
In case of an ETOPS calculation, check the ETOPS parameter whether
the inserted suitable or adequate airports cover the route to the RAP
using the graphical functions.
3. Perform an Airport Suitability Check for the RAP and the RAP alternate:
Click 'Initialize' for starting the check. The check applies the estimated
arrival time at the RAP and the RAP alternate.

Calculating a Flight Using the Standard Reclearance Procedure or the Decision Point Procedure - Continued
4. If required, change the calculation conditions regarding optimization,

contingency fuel policy or restrictions.
5. Start the reclearance calculation by the button 'RECLEARANCE'.

If optional feature 'Route Validation Check' is configured, the defined
route is checked for invalid waypoints prior to the calculation. For details
and handling options see chapter 'Route Validation Check' in this
document.
The calculation performs the following steps:
1. Calculation from DEP to RAP via the decision point
2. Calculation to destination with reduced contingency fuel amount
3. Recalculation of RAP or DEST route with new weight
6. The reclearance OFP is displayed in the column 'RCL DEST'.
The table of route information switches into the display modus.
Review the calculation results.

Calculating a Flight Using the Standard Reclearance Procedure or the Decision Point Procedure - Continued
7. Use the button 'OK' to quit the 'Reclearance' window.

You return to window 'Analysis' or window 'Route Definition'.
A reclearance flight has been calculated.

The reclearance OFP is shown in the 'Analysis' window. The reclearance
OFP number includes the basic OFP number and the reclearance OFP
number, e.g. 2/1.
Proceed with the flight planning process.
2.6.3 Calculating a Flight Using the Reduced Contingency Fuel Procedure

Calculating a 1. Open window 'Reclearance' using the button 'RECLEARANCE'.

Reclearance Flight
The copy control panel opens showing
parameter of the vertical profile.
Example:

'Route (basic OFP)'. The contingency fuel policy of the RAP is shown as
defined for the aircraft registration.

Calculating a Reclearance Flight- Continued
2. Select the desired reclearance waypoint; it is transferred into the table

(entry mode). This waypoint defines the intersection of the basic route to
the reclearance point.
Insert the desired reclearance airport (RAP) in the field 'RAP' and
optionally a reclearance alternate in the field 'RAP-ALTN'.
If for the calculation of the OFP to the reclearance airport the selected
option for contingency fuel calculation requires the input of an en-route
alternate, insert the ERA in the respective field.
In case of an ETOPS calculation, check the ETOPS parameter whether
the inserted suitable or adequate airports cover the route to the RAP
using the graphical functions.
3. Perform an Airport Suitability Check for the RAP and the RAP alternate
and if applicable the ERA: Click 'Initialize' for starting the check. The
check applies the estimated arrival time at the RAP, the RAP alternate
and the ERA.
4. If required, change the calculation conditions regarding optimization,

contingency fuel policy or restrictions.
5. Start the reclearance calculation by the button 'RECLEARANCE'.

route is checked for invalid waypoints prior to the calculation. For details
and handling options see chapter 'Route Validation Check' in this
document.
The calculation performs the following steps:
1. Calculation from DEP to RAP via the decision point
2. Calculation to destination with reduced contingency fuel amount
3. Recalculation of RAP or DEST route with new weight

Calculating a Reclearance Flight- Continued
6. The reclearance OFP is displayed in the column 'RCL DEST'.

The table of route information switches into the display modus.
7. Use the button 'OK' to quit the 'Reclearance' window.

You return to window 'Analysis' or window 'Route Definition'.
A reclearance flight has been calculated.

number, e.g. 2/1.

2.6.4 Optional: Performing an Automatic Reclearance Calculation
Automatic Using 'Automatic Reclearance' function is optional.

Reclearance
Prerequisite for using 'Automatic Reclearance' is the authorization of at least
Calculation
one airport for the use as reclearance airport. For more details about
authorizing a specific airport in window 'Airport Authorization' see
documentation 'Data Maintenance User Manual'.
The function 'Auto Reclearance' automatically calculates the reclearance
point and selects the reclearance airport according to predefined rules that
have been set in the system control parameters. The focus is on an
approximate 90 % section of the total track.

You have authorized airports for the use as reclearance airports.
Performing an 1. Open window 'Reclearance' using the button 'RECLEARANCE'.

Automatic
Reclearance The copy control panel opens showing
Calculation parameter of the vertical profile.
Example:


'Route (basic OFP)'.
2. You may alter automatic settings for calculation manually: Reclearance

waypoint, reclearance airport, reclearance airport alternate, optimization
criterion, contingency fuel policy or restrictions.

Performing an Automatic Reclearance Calculation - Continued
3. Start the automatic reclearance calculation with the button

'AUTO RECLEARANCE'. The application automatically performs an
Airport Suitability Check and selects the best reclearance points and
suitable reclearance airports.
The itemized fuel amounts the three OFPs as required in a reclearance
calculation are displayed on the right.
4. You may accept the reclearance airport as suggested by the system, or

alter it as follows: Click on button 'Alternative RAPs' and open the
window showing authorized reclearance airports. Select one and click
either:
'CALCULATE' for starting a new reclearance calculation, or

'INSERT' to transfer the airport into window 'Reclearance' window
and start the new calculation with 'RECLEARANCE' button.
5. Click on button 'OK' to confirm the reclearance calculation. Reclearance

results are shifted in form of a separate reclearance OFP into window
'Analysis'.
An automatic reclearance calculation has been performed.

number, e.g. 2/1.

2.6.5 Reviewing Results of Reclearance Calculation
Transfer of OFP After a reclearance calculation, performed either by dispatcher or

Data automatically, the reclearance OFP as displayed in the column 'RCL DEST'
is transferred to the 'Analysis' window.
In the 'Analysis' window the reclearance OFP is shown next to the basic
OFP. The reclearance OFP number includes the basic OFP number and the
reclearance OFP number, e.g. 2/2.
Reviewing Results The transferred calculation results of the reclearance OFP in window
of Reclearance 'Analysis' are referring to the flight to the destination airport. In the case, that
Calculation the flight to the reclearance airport (RAP) requires a higher takeoff fuel, the
system merges the calculation results of the columns 'RCL DEST' and
'RAP'. This refers to the data for Planned Takeoff Fuel 'PLNTOF', Planned
Zero Fuel Weight 'PLNZFW', and Planned Takeoff Weight 'PLNTOW'. The
figure shows an example for the transfer of OFP data for the reclearance
OFP number 2/2.
'Reclearance' Window 'Analysis' Window
Transfer of Calculation Results from 'Reclearance' Window to 'Analysis' Window

2.7 Flight Planning over AIRAC Change Dates
AIRAC Aeronautical Information Publications (AIPs) are issued by or with the

authority of a state and contain aeronautical information essential to air
navigation. The AIPs are kept up-to-date by regular revision on a fixed
cycle known as the AIRAC (Aeronautical Information Regulation And
Control) cycle: revisions are produced every 28 days, always on a
Thursday. The changes are published well in advance to their effective date
so that users of the aeronautical data can update their flight planning
systems in time.
AIRAC Changes in Data Maintenance staff of Lufthansa Systems updates aeronautical

Lido/Flight information in Lido/Flight following the AIRAC cycle as Lido/Flight can
handle data with future validity dates.
Nevertheless in Lido/Flight issues may occur when planning a route over
midnight at an AIRAC effective date, if a segment of the route is updated
at 00:00 UTC with the new AIRAC cycle. In this case Lido/Flight stops the
calculation of the OFP and displays an error message.
The following example is used to illustrate a possible AIRAC issue for a
flight planned over midnight at an AIRAC effective date. The waypoint
sequence of an airway to be used is realigned at 00:00 UTC.
Example:
Flight 2A123 from FRA to HER, ETD: October 20, 23:00 UTC.
Planned route segment valid on October 20:
Airway UN503 via waypoints LIZUM LIKDA BAKOR VEZAL LAMPO ()
After realignment of waypoint sequence on October 21 the valid route is:
Airway UN503 via waypoints LIZUM GOGEM OGEPI OZE SUMIR LAMPO
()
How Lido/Flight processes the data:

The system selects the predefined route according to the day of departure:
Airway UN503 using the waypoints as of October 20.
While calculating the system detects that the waypoint sequence of the
selected route is not valid on October 21. The calculation stops with an
error message stating that the selected routing is not available (e.g. 'No
continuous route found ').

Approaches to The following table lists possible approaches to avoid AIRAC issues when
AIRAC Issues planning a route that is updated at the AIRAC effective date. The choice
depends on the information on the AIRAC issue that is available for the
user, when the calculation of the flight is interrupted:
Available Information Proposed Approach

for Recalculation
The time when the AIRAC issue occurs along the Modifying ETD/ETA
planned route can be identified.
The AIRAC issue can be located exactly along Using Via Waypoints
the planned route (e.g. the error message states:
No continuous route found between waypoint
'LIZUM' and 'LAMPO').
There are one or more AIRAC issues along the Using a Via Waypoint
route to be planned. valid at 00:00 UTC
2.7.1 Recalculating a Flight with Modified ETD/ETA
Introduction This approach solves AIRAC issues by creating a new planning parameter
scenario with an ETD/ETA modified to that day where updated segments of
the routing are valid, and recalculation of the OFP.
The approach can be used if the following conditions apply:
The calculation of a flight has been stopped in window 'Analysis'.
The time when the AIRAC issue occurs can be located on the route.

Recalculating a 1. Open window 'Planning Parameter' with a click on button

Flight Using 'PLAN PARAM'.
Modified ETD/ETA
2. Modify the 'ETD' to the AIRAC effective date (in the current example
October 21) using the yellow fields and adapt 'ETA' accordingly. Click
on button 'INSERT' to insert the new planning parameter scenario.
3. Open window 'Analysis' using button 'ANALYSIS'.

Window 'Route Options' opens additionally. Click on button 'PRED' to
show all available predefined routes. As the 'ETD' has been changed to
the new AIRAC effective date, the application will show all routes valid
on October 21. Select the desired route and confirm the selection with
a click on button 'OK'. You return to window 'Analysis'.
Trigger a calculation of the scenario with a click on button 'ANALYSIS'.
Note: The WX prognosis and NOTAM checks used for this calculation relate to the
modified ETD/ETA.
4. Open window 'Planning Parameter' with a click on button

'PLAN PARAM'. Change the fields 'ETD' and 'ETA' of the current
scenario back to the original date, and insert the scenario.
Caution: Do not click on button 'Initialize', as this will delete the
modifications.
5. Reopen window 'Analysis'.

Right-click on the OFP, which has been calculated successfully with
the modified ETD/ETA to copy it. Window 'Copy Control Panel' opens.
Select all available items of the OFP to copy them and click on button
'OK'. A new OFP column is generated in window 'Analysis'. The purple
color of the route name indicates that this OFP is a copy.
Note: The copying will keep the segment sequence exactly as it was in the flight
plan with modified ETD/ETA that was copied.
6. Trigger the calculation of a new flight plan with a click on button

'ANALYSIS'.
The flight has been recalculated using a modified ETD/ETA.

The new flight plan considers the correct weather prognosis and NOTAM
situation, but is based on the updated route after the AIRAC date.

2.7.2 Recalculating a Flight Using Via Waypoints
Introduction This approach solves AIRAC issues by specifying via waypoints and using
free optimization of the route between the via waypoints.
The AIRAC issue can be located exactly along the planned route,
e.g. if the error message states: 'No continuous route found between
waypoints 'LIZUM' and 'LAMPO'.
Recalculating a 1. Open window 'Route Definition' with button 'RTE DEF'. The window
Flight Using opens in 'Entry Mode' and displays the waypoint codes of departure
Via Waypoints and destination airport.
2. Specify the two waypoints mentioned in the error message as via

waypoints: In column 'WPT Code' click into the next empty field below
the departure airport and enter the code of the first via waypoint e.g.
'LIZUM'. Press the 'TAB' key or click in the next empty field below and
enter the second via waypoint e.g. 'LAMPO'.
Mark the first via waypoint with a click in the respective line. The whole
row is highlighted:

Recalculating a Flight Using Via Waypoints - Continued
3. Open window 'List of Routes' with a click on button 'List of Routes'.

Open drop-down list 'Type' and select a route segment, e.g.
'Company Route'. Set the date of validity to the first day of the new
AIRAC cycle (default: operations day).
Click on button 'SELECT' to display all routes between the two via
waypoints valid in the new AIRAC cycle. Mark the desired route with a
click in the respective row.
Transfer the selected route to window 'Route Definition' with a click on

button 'APPEND'. You return to window 'Route Definition'.
4. Trigger a calculation of the defined route with a click on button

'Calculate'.
Note: Check if the optimized route between the set via waypoints matches your
requirements, especially if there is a large area between the selected
waypoints.
5. Click on button 'ANALYSIS' to go back to window 'Analysis' and

continue your flight planning.
A flight has been recalculated using via waypoints.

2.7.3 Recalculating a Flight Using a Via Waypoint Valid at 00:00 UTC
Introduction This approach solves AIRAC issues by using a waypoint as via waypoint
that is valid in the previous as well as in the new AIRAC cycle, and that is
part of the desired route. The approach consists of the following two steps:
1. Calculating the first part of the route from (departure to via waypoint)
operated with company routes valid in the previous AIRAC cycle.
2. Calculating the second part of the route (from via waypoint to
destination airport) operated with routes valid in the new AIRAC
cycle.
There is more than one AIRAC issue along the planned route.
Recalculating a 1. Open window 'Route Definition' with a click on button 'Rte Def'.
Flight Using a Via
Waypoint Valid at 2. Enter a waypoint where the aircraft will be at around 00:00 UTC as a
00:00 UTC via waypoint'. This via waypoint must be:
Valid both in the previous and in the new AIRAC cycle
Part of the desired company route in any case
3. Open window 'List of Routes' with button 'List of Routes'.

Set field 'Date of Validity' to the day before the AIRAC effective date to
plan the first part of the flight with routes valid in the old AIRAC cycle:
Select a company route from the departure airport to the selected
via waypoint, and transfer the route to window 'Route Definition' with a
click on button 'APPEND'.
4. Repeat step 3 to plan the second part of the route from the set via
waypoint to the destination airport. The field 'Date of Validity' has to be
set to the AIRAC effective date, as the second part of the route will be
operated with routes valid in the new AIRAC cycle.
5. Return to window 'Route Definition' and trigger a calculation of the

defined route with a click on button 'Calculate'.
A flight has been recalculated using a via waypoint valid at 00:00 UTC.

3 Performing FPL/OFP Transmission
3.1 Workflow and Overview of Procedures
Workflow The following picture shows a workflow by means of user interfaces of

transmitting OFP information to ATS and transmitting briefing package to
servers and users via different transmission media.
Airport Suitability Recheck in window 'FPL/OFP Transmission' is a
complete airport suitability check, which verifies an existing flight planning
scenario. The recheck uses calculated flight times for a more precise time
window: the estimations of the selected scenario are validated against the
precise calculated flight times.
Workflow FPL/OFP Transmission and Message Transmission Function

Transmission You can transmit the OFP/ATS flight plan and the briefing package within
Options one step or perform each step separately. The table below summarizes the
possible options dependent on the used button.
Action Button Description

Transfers the ATS flight plan (Filing)
File 'File ATS'
In the 'Flight List' the flight gets the status '2'.
Initializes the generation of the briefing package
Send 'Send OFP' In the 'Flight List' the status of the flight changes
from '2' to '3'.
Transfers the ATS flight plan (Filing).
File Initializes the generation of the briefing package.
'File ATS/
and
Send OFP' Transfers the briefing package to the server.
Send
In the 'Flight List' the flight gets the status '3'.
Note: The filing and/or sending of the briefing package with the above buttons may
generate an automatic e-mail with OFP/ATS flight plan in ARINC-633XML format
to a customer-defined receiver address, if Lido/Flight has been configured
accordingly. For more information, see 'Data Maintenance User Manual',
Chapter 'Address'.
Overview of The following procedures describe how to file a flight plan and how to
Procedures transmit briefing packages:
1. Filing an OFP and generating a briefing package
2. Maintaining additional briefing information
3. Transmitting a briefing package via window 'Flight List'
Note: This procedure is available for customers using the Lido/Flight module
'Airline Operations Support AOS', Three-Click-Version.
4. Sending update messages
5. Removing a briefing package from the server
Monitoring the publishing process
Before You Start Before you start, verify that you have maintained the following data:
A set of target addresses for receiving briefing package
Lido/Flight users and their relevant data.
For a description of these tasks, please consult the documentation for basic
data maintenance and the function 'Shift Management'.
For using the optional function for transmitting messages via E-mail the
user has to secure additionally the following prerequisites:
Decide, which work station is to receive all E-mail replies

Determine the addresses of all user as reply addresses

3.2 Filing an OFP and Generating a Briefing Package
Before You Start For filing an OFP and generating a briefing package an OFP has to be
selected. For filing and sending of OFPs use the OFPs with the
numbers 1-99 only.
The selection of an OFP is possible during the flight planning process in
window 'Analysis'. For a flight, which has the status '3' in the flight list an
OFP can be selected directly via window 'Flight List'.
1. Window 'Analysis' is open.
2. The respective OFP has been selected.
Filing an OFP and 1. Open window 'FPL/OFP Transmission'.

Generating a
Path: Window 'Analysis' > button 'OFP TRANS'
Briefing Package
or: For a flight with a status '3' in the flight list:
Window 'Flight List' > flight-related context menu
'Review OFP Transmission...' > button 'SELECT'
The OFP data is transferred into the window.

Review the ATC flight plan. You may alter data if necessary. Upon
opening the window, Lido/Flight checks if the departure airport is
located within the IFPS region. If so, the toggle 'ECAC' is selected and
the addresses for the departure airport are loaded. You may add or
delete ATC addresses. For inserting additional addresses please select
the respective address row by the toggle in front of the respective row;
otherwise for filing an ATS flight plan these addresses are ignored.

Filing an OFP and Generating a Briefing Package - Continued
2. You may add additional information to the briefing package:

Use button 'Additional Info' to open a separate window containing
briefing information. Make your settings as described in procedure
'Appending Additional Briefing Information'.
3. You may write remarks related to the selected OFP:

Open window 'Remarks for Briefing OFP' using button 'OFP Remarks'.
Write your remarks (default: max. 1000 characters). Save the data and
quit the window with button 'OK'.
Depending on the customer setting the remarks are available either:
Permanent for latest sent OFP, or
As long as the dispatcher is preparing the OFP transmission
4. Transmit the information using one of the following buttons:

Button Actions
'File ATS' Transfers the ATS flight plan (Filing).
'Send OFP' Initializes the generation of the briefing package.
'File ATS/ Transfers the ATS flight plan (Filing).
Send OFP'
Initializes the generation of the briefing package.
Transfers the briefing package to the server.
Note: If multiple flight plans are used, the ATS flight plan will be filed in the format as
defined for the flight plan of the currently displayed index card.
According to the customer settings the button may automatically trigger

one or all of the following actions:
The generation of an automatic e-mail with OFP/ATS flight plan in
ARINC-633XML format. If there is no e-mail receiver defined, there
is a warning pop-up for your information. Confirm the pop-up with
'OK' and the filing/sending of the briefing package will continue.
An Airport Suitability Recheck. For further information please
consult the feature description 'Airport Suitability Check' of your
applied policy.
The further procedure depends on the result of the check:
If Then
Window 'Recheck' The Briefing Package is sent automatically.
does not open
Window 'Recheck' Window 'Recheck' displays the check results.
opens
Either to go back to 'Planning Parameter'/'Analysis' or
continue the OFP filing and/or sending with button
'CONTINUE'.

Filing an OFP and Generating a Briefing Package - Continued
5. Window 'Detailed Package' opens automatically. Here you can see the
complete briefing package that you may print: Use button 'PRINT' to
open window 'Print Options' and select the desired items.
6. You may transmit the briefing information. To do so, click on button

'Message Transmission': Window 'Transmission Options' opens
showing the options and default settings, which may vary according to
customer functions and preferences.
Select the items to be transmitted.

If you have subscribed the function for using the transmission medium
email, you may additionally attach satellite images and significant
weather charts. Click on button 'ATTACH' for browsing for images and
charts to be attached. Select one or more of the files offered by region
and time for either category in window 'Attachment Selection Box'. Click
on button 'ATTACH' to upload your selection.
Click on button 'TRANSMIT': Window 'Message Transmission' opens
showing the content of the briefing documentation according to your
settings.
Set your message transmission options according to your needs. Send
the selected items via button 'SEND'.
The flight plan has been filed and/or the briefing package is generated and
distributed.
Transmission and action has been tracked in the transmission history table.
In window 'Flight List' the respective line of the flight is highlighted green,
and in column 'Status' the flight plan status changed depending on the
transmission action. In window 'Analysis' the respective OFP is highlighted
red.

3.3 Maintaining Additional Briefing Information
Additional Briefing The user may add additional briefing information to the briefing package of
Information an OFP, which is triggered with the buttons 'File ATS/Send OFP and 'Send
OFP'.
Another option is replacing additional briefing information of an existing
briefing package. This function supports the requirement of distributing data
without filing an ATS flight plan or without creation of briefing documents.
The following procedures explain how to maintain additional briefing
information for a briefing package:
1. Appending additional information to an initial briefing package
2. Replacing additional information of an existing briefing package

An OFP has been filed.
Window 'FPL/OFP Transmission' is open and an OFP is selected.

Appending 1. Open window 'BRIEFING additional Info'

Additional Briefing
Path: 'FPL/OFP Transmission' > button 'Additional Info'
Information to an
Initial Briefing
Package
Upon opening the OFP information is transferred. The selected OFP is

labeled as 'MAIN' OFP.
2. You may select available OFPs and append them to the briefing
package as 'INFO' (Information) OFP, or 'SUMMARY' OFP. You may
write remarks in the respective input field.
3. To provide an actual organized track information as part of the briefing

package click the drop-down list 'TRACKS' for the required track
system. The adopted field shows the time of validity.
4. If you have subscribed the functions 'Overflight Permissions', 'Waypoint

Information' and 'Secondary Mini Flight Plan' you may switch on/off the
functions by the respective toggle.
5. If you have subscribed the feature 'Supplemental Weather and NOTAM

Information': Specify up to six additional airports for which weather and
NOTAM information is added.
6. Click on button 'APPEND' for appending the selected data. The window
closes; the data is transferred to window 'FPL/OFP Transmission'.
Additional briefing information has been appended to the OFP. If included

in the briefing package, OTS tracks will be displayed in the briefing
package section 'DISPATCH BRIEFING INFO'.

Replacing 1. Open window 'BRIEFING additional Info'

Additional
Path: 'FPL/OFP Transmission' > button 'Additional Info'
Information of an
Existing Briefing 2. The selected OFP is labeled as 'MAIN' OFP.
Package
Change the additional briefing information according to your needs;
possible is to:
Enable 'RWC', if available
Enable 'TAIL TANK', if available
Select 'TRACKS'
Write remarks in the respective input field
Select the available OFPs and append them to the briefing package
as 'INFO'rmation OFP, or 'SUMMARY' OFP.
3. Click on button 'APPEND' for appending the selected data and

transferring the data to window 'FPL/OFP Transmission'.
4. Click on button 'Dispatch Info', which generates the defined data and
initializes the replacement of the defined dispatch briefing information
within the actual briefing package.
Note: If none of the additional briefing information as described in step 2 were
selected, the system gives the information 'No Additional Info defined'.
The execution of this functionality is independent on the current OFP

status.
Additional briefing information has been replaced.

Each new 'Dispatch Info' or 'Send OFP' overwrites existing data in the
briefing documentation.
Transmission and action has been tracked in the transmission history table.
The OFP status remains unchanged.

3.4 Transmitting a Briefing Package via Window 'Flight List'
Before You Start For flights which have the status '3' in the flight list (OFP has been
generated), briefing packages may be transmitted directly via window
'Flight List'.
The flight in the flight list has been selected.
Transmitting a 1. Open window 'Detailed Package':

Briefing Package
via window
context menu. Select 'Review Briefing Package...' to load the
'Flight List'
corresponding data in window 'Detailed Package'.
2. You may review aircraft deviations: Click on button 'A/C DEV' to open
window 'List of Aircraft Deviations (MEL/CDL)'. Quit the window with
button 'OK'.
3. You may calculate a new flight planning scenario: Use the buttons
'PLAN PARAM' or 'ANALYSIS' for continuing.

Transmitting a Briefing Package via window 'Flight List' - Continued
4. You may write remarks: Use button 'REMARK' to open window

'Remarks' and write your remarks for the dispatch bulletin.
5. You may print the briefing package: Click on button 'PRINT'. Window
'Print Options' opens. Make your selection and click on button 'PRINT'
for starting the print process.
6. You may file an OFP or send the briefing package via window
'FPL/OFP Transmission': Use button 'OFP TRANS' and continue as
described in procedure 'Filing an OFP and Generating a Briefing
Package'.
7. For
transmission
click on button
'Message
Transmission':
Window
'Transmission
Options'
opens.
Change the items to be transmitted.
If you have subscribed the function using the transmission medium
email, you may attach satellite images and significant weather charts:
Click on button 'ATTACH' for browsing for images and charts to be
attached. Select one or more of the files offered in the 'Attachment
Selection Box' window by region and time for either category.
Click on button 'ATTACH' to upload your selection.
Click on button 'TRANSMIT': Window 'Message Transmission' opens.
Set your transmission options.
Transmit your briefing package with button 'SEND'.
The briefing documentation according to your selection has been

transmitted.
Transmission action has been tracked in the transmission history table.

3.5 Sending Flight Plan Update Messages
Which Update For filed OFPs associated update messages can be sent in case of
Messages can be cancellation, delay and modification.
Sent?
The following table shows the different functions.
Message Button
Application
Type Label
Message in case a flight has been cancelled.
Flight Plan Cancellation
If a flight has been cancelled, you have to withdraw

the briefing documentation manually. See procedure
'Removing a Briefing Package from the Server'.
In window 'Flight List' for the respective flight the
CNL
status number is reset to '1'.
Function disables the possibility to send an OFP
separately before filing a new ATS FPL.
Any cancellation of a flight plan requires a previously
filed ATS-FPL.
Message in case a flight is delayed related to the time
of departure.
Delay
Function maintains the possibility to send any OFP

DLA
separately.
status number remains as it is.
Message in case of modification of the filed flight plan.
Modification
Function maintains the possibility to send any OFP

CHG separately.
status number remains as it is.
The content of the messages follows the format:

(MESSAGE TYPE - flight number - departure airport and EOBT
destination airport/ flight plan).
On customer request cancellation messages and modification messages
can be sent without the EOBT (Estimated off-block time).


An OFP has been filed.
Window 'FPL/OFP Transmission' is open.
A click on any of the history columns loads the FPL/OFP content applicable
to filed history entry.
For customers using the FAA format:
For filed ICAO messages index card 'ICAO' is the active one; update
messages cannot be sent in FAA format. For proceeding click on index
card 'ICAO' to activate buttons 'CNL', 'DLA', and 'CHG' and send them from
there.
All further message transmission processes initiated in this window are
based on the data of active index card.
Sending Flight Plan 1. Select the respective OFP in the column of the transmission history
Update Messages table.
2. Insert the required data related to the update:

For a delay message change the departure time. For a modification
message insert the changes to be transmitted. If for the update
message the address needs to be altered, click into the respective
address field and alter the address.

Sending Flight Plan Update Messages - Continued
3. Click on the respective button for the update message. The following
table shows possible actions and results of different update messages.
Button Action/Result
Transmission window opens showing the cancellation
message. You may either:
CNL Edit transmission options: Open window 'Message
Transmission' with the respective button.
Click on button 'SEND' for sending cancellation message.
Transmission window opens showing the delay message.
The information is compared with the actual visible display. In
case of different departure times the message will be created
DLA with the new time. You may either:
Edit transmission options: Open window 'Message
Click on button 'SEND' for sending delay message.
Transmission window opens showing the modification
message.
The information is compared with the actual visible display. In
case of changes of the ATS flight plan the complete ATS flight
plan is shown.
CHG
You may either:
Edit transmission options: Open window 'Message
Click on button 'SEND' for sending modified flight plan.
The respective flight plan update message has been sent. If for the ATS
flight plan a modification message is detected, the complete ATS flight plan
is sent.
In case of a cancellation message the status of the flight in window
'Flight List' is reset to '1'.
The status of the flight in the transmission history table changes in
accordance to the update message.

3.6 Removing a Briefing Package from the Server
Introduction Removal of a briefing package is necessary in case of cancellation of a

flight. This action cancels only the route of the flight, not the flight itself.
For removal of a briefing package the function of withdrawing of all briefing
documents from the server is provided.
Before you Start Before you start, verify that:

An OFP has been filed and sent.
Select the flight for which the information is to be removed.
Removing a 1. Open window 'FPL/OFP Transmission':

Briefing Package
from the Server
context menu. Select 'Review OFP Transmission...' to load the
corresponding data in window 'FPL/OFP Transmission'.
2. Click on button 'SELECT', which opens a list of scenarios. Select the

scenario for which the information is to be withdrawn from the server.
3. Select the respective OFP in the column of the transmission history

table.
4. Remove the transferred briefing package from the server using button
'Withdraw Documents'.
The selected briefing package is removed from the server.

In window 'Flight List' the respective flight gets the status number '4'.
Removal has been tracked in the transmission history table by the status
'Withdrawn'.

3.7 Monitoring the Publishing Process
Transmission Every transmission of flight information and an update message is

Monitoring monitored by an OFP status in a transmission history shown in window
'FPL/OFP Transmission'.
Actions performed in the user interfaces for FPL/OFP transmission are
additionally connected with flight information in window 'Flight List'.
Both the transmission history and the flight list are reflecting the status of
the flight planning process and briefing as shown in the following table.
The different status is supported by a color-coding.
Flight List
Lido/Flight
Column Description
Module
'Status'
Flight information is available in window
0 'Flight List' by SSIM load, OPS Interface, or
inserted manually. IFPL
A planning parameter scenario has been inserted
in window 'Planning Parameter'.
1
A flight has been calculated automatically, but no
AOS
briefing package was generated and sent.
An ATS flight plan has been filed (transmitted to
2 ATC), but no briefing package was generated and
sent. IFPL
AOS
An ATS flight plan was filed and a briefing
3
package was generated and sent.
The briefing package has been withdrawn.
4 Only the route is canceled, not the flight itself. IFPL
Withdraw documents means that the action after
pressing button 'Sent' is canceled.
An OFP has been generated; the briefing
package is prepared, but not yet sent.
The sending needs to be made manually.
This status is shown in the following cases:
5 The customer uses the AOS 3-click version. AOS

The Airport Suitability Recheck has detected
discrepancies.
For more details about the AOS, please see
documentation 'Airline Operations Support (AOS)
Functional Description and User Manual'.

4 Performing an Inflight Calculation
4.1 Calculation Parameters
Calculation The function 'Inflight Assistance' allows the calculation of an OFP from an
Parameters en-route waypoint (inflight waypoint) to the destination airport while the
aircraft is already airborne.
Customers using the optional function 'Precision Path Procedure' may
additionally consider all waypoints of a selected route, which are located on
micro segments of the used terminal procedure. For more details about
'Precision Path Procedure (3P)' see documentation 'Terminal Procedure
All flight planning parameters such as fuel variables, operational mode and
cruise procedure can be reset for a recalculation.
For an inflight calculation parameters for segments and/or route portions
may be maintained. The sequence of waypoints and/or airways will be
considered as 'via direction'. Route portions which are not specified will be
optimized according to the selected optimization mode. Unspecified flight
levels will be optimized according to the gross weight.
If optional feature 'Route Validation Check' is configured, the defined route
from inflight waypoint to destination is checked for invalid waypoints
prior to the inflight calculation.
4.2 Performing an Inflight Calculation

An OFP has been filed and sent.
The aircraft is airborne.
The OFP for an inflight calculation has been selected.

Performing an 1. Open window 'Inflight Assistance'.

Inflight Calculation
'Edit Planning Parameters...' > button 'Analysis' > button
'Inflight'
The basic OFP is displayed in the column 'Routing' as a sequence of

waypoints.
If you use the optional function 'Precision Path Procedure' you may
additionally display all waypoints of a selected route, which are located
on micro segments of the used terminal procedure. To do so select the
toggle 'Show TP waypoints'. All waypoints are considered in
calculation.
Optimization mode, restrictions and ETOPS rules are shown as
selected in the main OFP.
2. Click on the desired inflight waypoint in the routing table. The selected
waypoint and all following waypoints of the planned route to the
destination airport of the basic OFP are shown in the waypoint table
(entry mode).
You may change a single waypoint or the complete routing after a
certain inflight waypoint. Click on button 'Append Row' to insert a new
line. Enter a new waypoint, define flight level and cruise procedure.
Optionally you may also define a free flight waypoint.
For each waypoint you may change values for vert. unit, flight level and
cruise procedure; the respective data for IAS, MN and cost index are
filled in automatically.

Performing an Inflight Calculation - Continued
3. Depending on the configuration insert the gross weight into the field
with name 'GW' or the remaining fuel 'Rem Fuel' to define the
remaining fuel or vice versa. If required, change the calculation
conditions, for example regarding optimization or restrictions. You may
change the load, the DOW, the optimization mode, the inflight
destination airport or the route to the destination airport.
4. If you defined a new destination airport for an ETOPS flight, check the
ETOPS parameters.
Activate which 'Inflight Components' for fuel calculation you wish to
include in the new calculation.
5. Trigger an Airport Suitability Check for the destination airport and the
destination alternate: Click 'Initialize' to start the check. The check
applies the estimated arrival time at the airports.
You may check the weather and NOTAM situation manually: Open
window 'WX/NOTAM' with button 'WX/NOTAM'.
6. Start the inflight calculation with a click on the button 'INFLIGHT'. The
results of the inflight calculation are displayed on the right. The table of
route information switches into the display modus.
route from inflight waypoint to destination is automatically checked
for invalid waypoints prior to the inflight calculation. For details and
handling options see chapter 'Route Validation Check' in this
document.
If the remaining fuel is less than the fuel required for the inflight OFP
that means if the value for 'D Fuel' (delta fuel) is negative and
highlighted in red an information window opens.
7. You may add remarks to the calculation.

Close the window using the button 'OK'. You return to window 'Analysis'
or window 'Route Definition'.
An inflight calculation for an airborne flight has been completed. Weather

information and restrictions are considered for the shown initialization time.
An inflight reclearance calculation is possible if the value of the calculated
inflight fuel exceeds the value of the remaining fuel.

4.3 Reviewing Results of Inflight Calculation
Reviewing Results After an inflight calculation the inflight OFP with the route identifier 'INFLT'
of an Inflight is transferred from window 'Inflight Assistance' to window 'Analysis'.
Calculation
The calculation results of the inflight OFP refer to the flight from an en-
route waypoint to the destination airport. Delta Fuel is calculated, which is
the difference between remaining fuel (REM Fuel) and the fuel planned for
the inflight OFP (PLNFUEL).
In window 'Inflight Assistance' this value is displayed in the line 'D FUEL'
[kg]. If this value is negative, it is highlighted in red and information is
given. In window 'Analysis' the planned fuel is displayed in the line
'ADDFU'. On customer request the delta fuel value can be displayed in the
line 'ADDFU' [min] or [kg]. The figure shows an example for the display of
delta fuel [min].
The conversion follows the formula:
Additional fuel [min] =
Delta fuel [kg] / Fuel Flow at flight level 150 [kg/s] * 60 [s/min)
If the delta fuel is negative, this field is empty.
'Inflight Assistance' Window 'Analysis' Window
Display of Delta Fuel Value in Windows 'Inflight Assistance' and 'Analysis'

5 Field and Button Description
5.1 Overview
Windows Affected Following windows provide the graphical user interface for basic flight
planning procedures:
Window Purpose
Flight List Gives an overview of all flights.

Planning Parameter Allows the user to set up a flight planning scenario.
Analysis Gives the user the possibility to define further
calculation parameters, trigger a flight plan
calculation and review calculation results in detail.
Route Options Allows the user to define routes and/or optimization
criteria to be used for calculations.
Additionally window 'Route Options' allows the user
to enable/disable Free Flight calculations (for details
see the optional document 'Free Flight Feature
Description').
Note: Window 'Route Options' opens automatically when the
user opens window 'Analysis' and no OFP has been
calculated for respective planning parameter scenario
before.
Route Definition Serves to define new routes including parameters

such as waypoints, flight level limitations, weights,
and additional fuel and optimization criteria.
Additionally, it serves to modify existing routes, i.e.
to change parameters of a route already calculated.
Restrictions Serves to define restrictions before OFP calculation
and to review restriction settings of already
calculated OFPs.
Reclearance Lets users of Lido/Flight set the parameters for
performing reclearance calculations.
FPL/OFP Lets users of Lido/Flight add information for

Transmission preparing a briefing package and transmit
information for an individual flight. Prerequisite for
using this window is the calculation of a flight.
Inflight Assistance Provides the function to calculate an OFP
(Operational Flight Plan) from a selectable inflight
waypoint to the planned or a new destination airport.
This chapter gives a detailed field and button description for each of these
windows.

5.2 Window 'Flight List'
Purpose and Window 'Flight List' provides the user with an overview of flights and up-to-
Structure of date flight operation information. Displaying the entire workload for dispatch
Window personnel, window 'Flight List' is the main access point to the interactive
'Flight List' flight planning process.

The following screenshot is a composite of all currently available options.
The user interface layout differs depending on the customers settings.
Therefore some fields may not apply to you.
The window is divided into different areas, which are described in detail:
Window Links Log
Filter Definition Flight List
Search Definition Command Buttons

Window Links
Title/Button Description
New Flight Opens window 'Flight Data' in mode 'Create a flight'.

IFM Opens window 'IFM Message/Alert'.
Message/Alert
Optional window link only available if Lido/Flight module
'Inflight Monitoring' has been subscribed to.
Worksheet Opens window 'Worksheet' displaying all flights for which
a briefing package is available.
Optional window link only available if option 'Worksheet'
has been configured.
Filter Definition Area 'Filter Definition' offers the possibility to specify certain criteria for the
flights to be displayed in the flight list.
Office Office for which flights are displayed in table 'Flight List'.
Option Description
All Office: All flights, which were assigned to any office.
Note: Option 'All Office' covers all other office
options except 'NOOFFICE' and 'NORULE'.
<Office Name> All flights, which were assigned to the respective
office.
RPL: All flights, which were assigned to the office 'RPL'
(Repetitive Flight Plan) for the use within the
Lido/Flight module AOS.
RPLPLATO: All flights, which were assigned to the office 'RPL' for
the use within the Lido/Flight module
'Route Analysis (PlaTo)'.
NOOFFICE: All flights, which were assigned to the office
'NOOFFICE'.
NORULE: All flights, which were not explicitly assigned to any
office.
Default: Office to which the workstation is connected.

Team Team for which flights are displayed in flight list.
Availability of teams depends on selected office.
Default: Team to which the user is assigned.
Status Status for which flights are displayed in flight list.
By default: (all statuses)
DEP IATA or ICAO code of departure airport for which flights
are displayed in flight list.

Filter Definition - Continued
DEST IATA or ICAO code of destination airport for which flights

are displayed in flight list.
Period Time period for which flights are displayed in flight list
Possible values:
48 hours (default)
All flights
Fix period
Selection influences content and alterability of the fields
'From' and 'Till'.
From Begin of time period for which flights are displayed in flight
list [DD-MMM-YYYY hhmm]
The actual value and the possibility to edit this field
depend on the selection from drop-down list 'Period':
Value in field 'Period' Field 'From'
Displayed Value Alterability
48 hours (default) Current time minus 24 hours No
All flights Empty No
Fix period Current time minus 24 hours Yes
Till End of time period for which flights are displayed in flight
list [DD-MMM-YYYY hhmm]
The actual value and the possibility to edit this field
depend on the selection from drop-down list 'Period':
Value in field 'Period' Field 'Till'
Displayed Value Alterability
48 hours (default) Current time plus 24 hours No
All flights Empty No
Fix period Current time plus 24 hours Yes
Default Selects default for 'Office' for management users or

'Team' for dispatch users, and initializes new data
selection.

Search Definition Area 'Search Definition' offers the possibility to search for certain flights
within the flight list.
Airline IATA code of airline

Flight Flight number
ATC C/S ATC Callsign [Alphanumerical Value]
Optional field only available if feature 'ATC Callsign' is
subscribed to.
DEP IATA or ICAO code of departure airport
DEST IATA or ICAO code of destination airport
STD Scheduled time of departure [DDhhmm]
Search Searches according to entered criteria and marks first
matching flight in table 'Flight List'.
Next Marks next flight of search result in table 'Flight List'.
Clear Search Clears search definition.
Log Table 'Log' displays operational changes of those flights currently displayed
in table 'Flight List'. The table is updated automatically.
AL IATA code of airline of affected flight

FLT Flight number of affected flight
DEP IATA code of departure airport of affected flight
DEST IATA code of destination airport of affected flight
Status Processed relevant operational change
Status Information Description of Incoming Data
ACFT (DAIQT -> DAIPS) Aircraft change
user initials User initial change
team change Team change
Ofp office Responsible office
Briefing office Responsible office
PIC Qualifier C -> E Change of Pilot Qualification
STD 1000 > 1100 Change of scheduled time of departure
next info Next information from OPS control about a
pending flight

Log Continued
Status Continued
ETD 1110 (1100STD) Publication of estimated time of departure
STA Scheduled time of arrival
ETA Estimated time of arrival
Airborne 1125 (1125 STD) Airborne time
0415 EDCT GDP for [ ] Certain number of flights affected by an
flights EDCT time issued by FAA.
A click on this entry opens a window listing
all affected flights with further information.
WAB data ZFW change larger than a limit specified
for each aircraft type
flight cancellation Flight cancellation
slot status Slot change
deviation MEL/CDL status change for a flight, for
which a briefing package has already
been sent
recalc AOS recalculation results (e.g. OFP
calculation error, OFP calculation warning)
IFPS messages: Incoming messages from CFMU in
Brussels
(e.g. ACK, REJ, MAN)
Currently only IFPL and IRQP messages
are considered.
ATC callsign change Change of ATC Callsign
DEST check failed Airport suitability check for DEST failed
(only in AOS with a special setting)
Auto office change ok Messages according to actions as defined
in window 'Office Action' of the shift
manager.
Auto office change error Messages according to actions as defined
in window 'Office Action' of the shift
manager.

Log Continued
Status Continued For customers using the optional module 'Air/Ground
Communications/Datalink':
DLK-TEXTRQ message Text downlink message from the crew
(TEXTRQ = text request); message may
be supported by a pop-up
DLK-FLOGRQ message Text downlink message from the crew
(FLOGRQ = flight list log)
DLK-FAILRP message Failure uplink message from the datalink
ground module
(FAILRP = failure report)
DLK-UDLVRJ message Failure uplink message from the customer
service provider (e.g. SITA) after passing
the datalink ground module
(UDLVFJ = undeliverable reject)
For customers using the optional module 'Traffic Flow

Restriction':
TFR problem TFR problems occured during an AOS
calculation. The flight is highlighted in
yellow color.
For customers using the optional module 'AOS':

AOS warning Messages according to AOS actions as
defined in window 'AOS Actions'.
AOS error Messages according to AOS actions as
Warning: Check for MEL Messages according to AOS actions as
items defined in window 'AOS Actions'.
Abort: Active MEL item Messages according to AOS actions as
<Context A right-click on a table row opens a log-message-related

Menu> context menu.
Context Menu Option Description
Hide Entry Hides the currently marked log message.
Note: Button 'Clear Log' might be used to
hide all log messages at once.
Unhide all Unhides all hidden log messages.
Clear Log Hides all currently displayed log messages from table
'Log'.
Note: Log-message-related context menu 'Unhide all' might be used
to unhide those log messages.

Flight List The flight list displays all flights matching the criteria selected in the area
'Filter Definition'.
A special color-coding of the background is used to reflect the processing
status of each flight. The currently selected flight has the background color
'Blue Dark'.
Color Processing Status of Flight IFPL AOS
White Flight not yet processed. X X

Earlier than filing time (3 hours prior to STD/ETD) minus 30 min.
Orange Flight not yet processed. Up to 30 minutes before filing time X X
(3 hours prior to STD/ETD). Serves as reminder that flight
calculation should be initiated.
Time limit can be changed in window 'Airport Pair'. For details
see document 'Shift Management Feature Description'.
Red Flight not yet processed. Less than 3 hours until STD/ETD. X X
Serves as reminder that flight calculation should be initiated.
Time limit can be changed in window 'Airport Pair'. For details
see document 'Shift Management Feature Description'.
Light Pink Flight calculated by AOS. - X
Calculation warning: Review recommended.
Optional warning available if calculation of predefined routes
failed (AOS option available if configured on customer request)
Purple Flight calculation aborted due to error. X X
IFPL: One of the following processes failed: optimization,
background transmission, file writing, waypoint selection
AOS: Calculation error: Manual intervention necessary.
Yellow Flight calculation aborted due to problem caused by TFR. - X

Option only available for users of Lido/Flight module 'Traffic
Flow Restrictions (TFR)'.
Green Flight Planning Scenario is inserted. (FP status at least 1); X X
Flight is not yet airborne.
Pale AOS calculation completed. Briefing package can be sent. - X
Green
Pale Blue Flight Planning Scenario is inserted. (FP status at least 1); X X
Flight is airborne or has been canceled.
The following terms refer to the column headers of table 'Flight List'. The
display of columns and labels may differ according to customer settings.
Some columns are optional and only available if configured on customer
request.
1ST ALTN Optional column: ICAO code of first alternate airport

Content only available if OFP has been filed and table
'Flight List' has been refreshed automatically.

Flight List Continued
2nd ALTN Optional column: ICAO code of second alternate airport

ACFT Aircraft registration
AIR Airborne time
AL IATA code of airline
ALTN Optional column: ICAO code of alternate airport
ATC C/S Optional column: ATC Callsign
Only available if feature 'ATC Callsign' has been
subscribed to.
CTOT Calculated Takeoff Time
Day Calendar day of flight
DLY Optional column: Delay of flight [minutes]
Content depends on the receipt of ATD and ETA.
Condition Display in field 'DLY'
ETD > STD Plus sign ('+') and difference between
Prior to receipt of
ETD and STD, displayed in red color

ATD and ETA
ETD < STD Minus sign ('-') and difference between

ETD and STD, displayed in black color
ETD = STD '0', displayed in black color
no ETD available blank
ETA > STA Plus sign ('+') and difference between
After to receipt
of ATD and
ETA and STA, displayed in red color

ETA
ETA < STA Minus sign ('-') and difference between

ETA and STA, displayed in black color
ETA = STA '0', displayed in black color
DEP IATA code of departure airport

DEST IATA code of destination airport
EDCT Expected Departure Clearance Time (for FAA slots)
ETA Optional column: Estimated time of arrival
[DDhhmm + suffix E] (e.g. 132059E)
ETD Estimated time of departure [DDhhmm]
FIN Optional column: FIN number as maintained in window
'Aircraft'

FLT Flight number

Fuel Order Optional column: Fuel on board [kg] according to final
load sheet, received via Lido/Flight interface 'Weight and
Balance Data'.
HLD Optional column: Special holding time [minutes]
SPEC FUEL Optional column: Special fuel
STA Optional column: Scheduled time of arrival [DDhhmm]
STA/ETA Optional column: Scheduled time of arrival [DDhhmm] /
estimated time of arrival [DDhhmm + suffix E]
(e.g. 132059E)
Status Status of OFP preparation and briefing
Status Description
0 No scenario has been inserted in window 'Planning
Parameter' yet.
FP (Flight Planning) Status
1 Scenario has been inserted in window

'Planning Parameter'.
2 ATS flight plan has been filed, but no briefing package
has been generated yet.
3 ATS flight plan has been filed and briefing package has
been generated.
4 Briefing package has been withdrawn.
CNL The flight has been canceled.
0 No action has been taken by crew or station personnel
yet; SB/B Status is also '0' if dispatch user clicks on
B (Briefing) Status
SB (Self Briefing)/
button 'Withdraw Documents' or 'Send OFP' in window

'FPL/OFP Transmission'.
1 Flight plan has been retrieved by the crew or station
personnel.
2 Briefing package has been printed or fuel has been
ordered by the crew or station personnel.
If flight is assigned to specific briefing office, it is labeled

as briefing flight (B); if briefing office is set to 'NOOFFICE'
or 'NORULE', flight is labeled as self briefing flight (SB).
For details see document 'Shift Management Feature
Description'.

STD Scheduled time of departure [DDhhmm]

STD/ETD Optional column: Scheduled time of departure [DDhhmm]
/ estimated time of departure [DDhhmm + suffix E]
(e.g. 132059E)
Team Team to which the user is assigned
Time Time when flight plan has to be or has been filed [hhmm]
User Initials of the user processing the flight
VIA ALTN Optional column: ICAO code of via alternate airport
<Context Flight-related context menu opens via right-click on a
Menu> table row.
Context Menu Option Description
Edit Planning Opens window 'Planning Parameter' with data
Parameters... of the related flight.
Edit Flight Data... Opens window 'Flight Data' with data of the
related flight.
Review Analysis... Opens window 'Analysis' with data of the
related flight.
Review Route Opens window 'Route Definition' with data of
Definition... the related flight.
Review OFP Opens window 'FPL/OFP Transmission' with
Transmission... data of the related flight.
Review AOS Info... Opens window 'AOS Info' with AOS calculation
results of the related flight.
Option only available for flights calculated by
the AOS.
Review IFM Flight Opens window 'IFM Flight Event' with all
Event... applicable 'Inflight Monitor' messages for the
related flight.
Option only available if the related flight is
registered for IFM monitoring.
Review DLK History... Opens window 'Detailed Message History' with
data of the related flight.
Option only available if module 'Air/Ground
Communications / Datalink' has been
subscribed to.
Review Briefing Opens window 'Detailed Package' with briefing
Package... package of the related flight.
Option only available if OFP has been sent for
the related flight.

<Context Menu>
Continued Context Menu Option Description
Start AOS Starts an AOS recalculation of the related
(Re)calculation flight.
Option only available for flights calculated by
the AOS.
Uplink... Opens window 'Message Transmission' or
'Flight Data Uplink' depending on the
configuration of Lido/Flight.
Option only available if module 'Air/Ground
Communications / Datalink' has been
subscribed to.
Edit Flight Opens window 'Flight Assignment' for
Assignment... assigning flights to another office/team in the
course of shift management activities. For
details see document 'Shift Management
Unlock Flight Unlocks the related flight in the course of shift
management activities.
Option only available to user role
'shiftmanager'.
Command Buttons
Stop Update / Button to stop and start the continuous update of tables
Start Update 'Flight List' and 'Log'.
Label Description
Stop Update Deactivates continuous update
Button label changes to 'Start Update' and warning
message is displayed within 'Information Area' of
window 'Flight List'.
Start Update Reactivates continuous update
Button only available if continuous update has been
deactivated via button 'Stop Update'.
Print Prints displayed data.

Close Closes window.

5.3 Window 'Planning Parameter'
Purpose and In window 'Planning Parameter' the user can define and/or adjust a number
Structure of of parameters used for the calculation of the flight plan for a certain flight.
Window 'Planning This set of planning parameters is referred to as a 'planning parameter
Parameter' scenario'.
Path: 'Flight Planning'>'Flight List' > flight-related context menu
'Edit Planning Parameters...'
The following screenshot is a composite of all currently available options.
Your airline may be subscribing to some and not all of the options described
herein. Therefore the window you see on your site may differ from this
screenshot and some step-by-step instructions may not apply to you.
1: Basic Flight Data 5: PET / ETOPS Calculations
2: Alternate Selection 6: Weight and Balance Data
3: General Planning Data 7: Command Buttons
4: Airport Suitability Check

1: Basic Flight
Data
The area 'Basic Flight Data' contains general information about the flight to
be calculated. If you open window 'Planning Parameter' via window
'Flight List' with a certain flight selected, these data are loaded automatically.
AL Entry field for IATA Airline Code.

Flt-No. Entry field for Flight Number.
OS Entry field for Operational Suffix.
Format: alphabetic character
Usage and meaning of the operational suffix is subject to
customer's conventions.
Date Entry field for Date of flight.
Format: DDMMMYY, e.g. 09JUL08
DEP Entry Field for ICAO code of departure airport.
RWY Drop-down list to specify the runway of the departure
airport used for flight plan calculations.
Default value: preferential runway if available;
otherwise: main statistical runway.
STD Entry field for scheduled time of departure.
Entry field below Entry field for flight-plan departure day and time
'STD' (estimated time of departure (ETD) either entered
manually or received via interface).
If no ETD is published, the STD is displayed.
STA Entry field for scheduled time of arrival.
Entry field below Entry field for flight-plan arrival day and time (estimated
'STA' time of arrival (ETA) either entered manually or received
via interface).
If no ETA is published, the STA is displayed.
DEST Entry field for ICAO code of destination airport.
RWY Drop-down list to specify the runway of the destination
Default value: preferential runway, if available;

2: Alternate
Selection
In the area 'Alternate Selection' the policy for the selection of alternates can
be determined, which will be considered in flight planning calculations for
this planning parameter scenario. Furthermore the default cruise procedure
for alternate fuel calculation can be reviewed and changed (optional
feature, to be configured on customer request).
Altn Cruise Cruise procedure for alternate fuel calculation as defined

Procedure in window 'Aircraft Operator Maintenance'.
Possible options are:
LRC Long Range Cruise Default
ECON Economic Cruise (cost

index) Optional
SPEED Constant IAS/MACH
Cost Index Cost index for alternate fuel calculation as defined in

window 'Aircraft Operator Maintenance'. Only visible if
cruise procedure ECON is selected.
The cost index can be changed for current flight scenario;
however, value has to comply with ECON performance
table.
Alternates: Entry field for airport considered as take-off alternate
TKOF (ICAO airport code).

2: Alternate Selection - Continued
Alternates: 1-4 Entry fields for airports considered as alternate airports

(ICAO airport code).
The user may enter manually the alternates to be used for
flight planning. If 'Sequence by User' is selected from the
drop-down list 'Sequence', the sequence 1-4 represents
the ranking of the airports, which will be considered for
further flight planning calculations. If other options are
selected from the drop down list 'Sequence', this will
influence the alternate sequence (see description of field
'Sequence' below).
A click with the right mouse button in one of these fields
will open window 'Alternate Information', in which the user
can define the alternate route, specify the flight level to
the alternate and / or modify the runway of the alternate
airport.
Sequence Drop-down list to define the fuel policy that determines the
alternate sequence. Possible options are for example:
Minimum ALTN Fuel
DEST below Minimum
Sequence by User
For details on alternate selection please see document
'Airport Suitability Check Feature Description' for the
respective policy.
No Via Drop-down list to specify a Via Alternate airport for the

Alternate first alternate.
No Via Alternate (default setting)
Via Alternate
The Via Alternate must fulfill the requirements of
destination minima. A longer routing via Via Alternate
to the destination alternate will be taken into account.
Terrain A/I Drop-down list to enable/disable the consideration of icing
Penalty for terrain clearance calculations (for details see the
document 'Terrain Clearance Feature Description').
Possible options:
No Icing (default)
Icing
Flag Domestic
Flag (default)
FAR Flights performed according to Federal Aviation
Regulations no. 121 or no. 91.

3: General Planning
Data
Tankering Display field showing the reason for tankering.

Possible reasons:
Price MAXV (volume)
MAXH (handling) MAXB (business)
The field is only available if the flight is a possible
tankering flight. For details about tankering see the
document 'Tankering - Feature Description'.
Taxi Time Taxi out time [minutes]
Taxi Fuel Taxi out fuel [kg/lbs]

3: General Planning Data - Continued
Sync. Toggle key: Synchronized

If activated, the values 'Taxi Time' and 'Taxi Fuel' will be
synchronized. This means if the user changes one value,
the other value will be automatically recalculated on the
basis of the formulas for fuel flow and fuel amounts
(maintained in window 'Aircraft Operator Maintenance').
The calculated values will be rounded: taxi fuel rounded
up to whole kg/lbs, taxi time rounded down to whole
minutes.
If deactivated, the values can be changed individually,
without a recalculation of the other value.
The customer can choose from various options for the

display and editing function of the fields Taxi Time/Taxi
Fuel/Sync. as follows:
Option for Field/s Visible only Visible and Editable
<none> ---
Taxi Time
Taxi Fuel
Taxi Time and

Taxi Fuel with toggle 'Sync'
For 'Taxi Time' and 'Taxi Fuel' the system selects the
values as maintained. The following table shows the
checks and the sequence of use:
Value for Checked Window and Maintained by
Sequence of Use
Taxi Time Window 'Taxi Time' Customer
Window 'Aircraft Operator Customer
Maintenance'
Window 'Airport' Lufthansa Systems
Taxi Fuel Window 'Aircraft Operator Customer
Maintenance' (if not maintained,
(Taxi Fuel Flow [kg/h]) then taxi fuel = 0)
Priority Drop-down list to specify the priority regarding load or fuel
in case of weight limitations during the flight planning
process.
Possible values:
Load (in case of weight limitations fuel is reduced)
Fuel (in case of weight limitations load is reduced)

3: General Planning Data - Continued
Fin No FIN number as maintained in window 'Aircraft'.

Operator Display field showing the IATA code of operating airline.
Registration Entry field for registration of the aircraft used for flight plan
calculations.
PERFCORR Entry field for the performance correction factor of the
aircraft displayed in the field 'Registration'.
The performance correction factor is assigned to an
aircraft within window 'Aircraft'.
CONT Contingency Fuel
Field/Button Description
<Drop-down list> Contingency fuel policy as defined in
window 'Aircraft Operator Maintenance'.
<Radio buttons> Manual change of contingency fuel
calculation mode as maintained in window
'Leg Policy' or 'Aircraft Operator
Maintenance'.
Buttons are only available if option 'Manual
Cont Fuel Calculation Mode' is configured
by Lufthansa Systems on customer
request.
<Display field> % Percentage of trip fuel to be carried as
additional contingency fuel as maintained
in window 'Aircraft Operator Maintenance'.
For more details see document 'Fuel Policy Feature
Description'.
TCAP Tank Capacity
En-Route WT Entry field for maintaining en-route weight penalty [kg/lbs],
Penalty unit of measurement depends on setting for the aircraft.
This artificial weight limits the altitude of an aircraft, but
does not influence weight calculation.
FOB Fuel on Board
Remaining fuel from the previous flight leg.
You may define a value for minimum departure fuel for a
flight leg or an aircraft; if both values are maintained the
highest value is displayed.
Customers using the Lido/Flight module 'Air/Ground
Communications' may receive this information via fuel
report.
During the flight planning process the dispatcher can alter
the value manually.
PIC Entry field for authorization qualifier of pilot in command.

4: Airport
Suitability Check
The area 'Airport Suitability Check' provides the possibility to trigger the
airport suitability check for departure, destination and alternate airports and
shows the results of this check. All values displayed are for information only
and cannot be modified by the user.
List of Table showing results of the airport suitability check

Airports triggered by clicking on button 'Initialize' or 'Recheck'.
ICAO Displays ICAO code of checked airports.
Quality Displays type of operation the airport is used for and
checked.
Status Displays results of the airport suitability check.
The results include the check period and details such as
suitability designator of checked runway, approach
procedure considered and others.
For details see document 'Airport Suitability Check Feature
Description' for the respective policy.
PA Indicator if an alternate is used as planning alternate
Y = Yes
N = No

4: Airport Suitability Check - Continued
Initialize Button to trigger the following actions:

Update of operational data like best available time,
aircraft registration, PIC qualification, and weight and
balance data (DOW, Load, ESTZFW, MALTOW,
CGZFW)
Selection of alternate airports
Airport Suitability Check
The result of the airport suitability check is displayed in the
table 'List of Airports'.
Recheck Button to trigger a recheck.
The recheck compares the inserted aircraft equipment and
PIC qualification with the weather and NOTAM situation at
departure, destination and alternate airports.
The result of the recheck is displayed in the table 'List of
Airports'. The recheck does not cause any modification of
inserted or displayed data.
Init. Time Display field showing the time, when the button 'Initialize'
was clicked.
Display Format: ddhhmm, e.g. 240946.
5: PET/ETOPS
Calculations
Button to open window 'PET/ETOPS Parameter' for triggering PET/ETOPS

calculations.
For details see document 'ETOPS Operations Feature Description'.

6: Weight and The area 'Weight and Balance Data' displays

Balance Data information as received via the 'Weight and
Balance' interface of Lido/Flight.
DOW Dry Operating Weight.

Load Weight of payload.
ESTZFW Estimated Zero Fuel Weight (sum of 'DOW' and 'Load').
MALTOW Maximum Allowable Take-Off Weight (minimum of structural
weight, MEL weight and All Up Weight).
In case the Lido/Flight module 'Lido Integrated Takeoff
Performance - LinTop' is implemented, a takeoff
performance calculation can be performed. Respective
limiting weights are considered when determining the
MALTOW. See corresponding customer documentation.
MALLAW Maximum Allowable Landing Weight (minimum of structural
weight, MEL weight and All Up Weight).
In case the Lido/Flight module 'Lido Integrated Landing
Performance - LinLap' is implemented, a landing
performance calculation can be performed. Respective
limiting weights are considered when determining the
MALLAW. See corresponding customer documentation.
CG ZFW Center of Gravity of 'ESTZFW' (received via interface
'Weight and Balance' or inserted manually within window
'Flight Data').
Note: If this value is not provided via the interface or by manual input,
flight plan calculations use a default value for the center of gravity,
which is not displayed in this field.
Unit Drop-down list to specify the unit of measurement for the

fields 'DOW', 'Load', ESTZFW', MALLAW, and 'MALTOW'.
Possible values: KG (kilograms), LB (pounds), T (tons)
By default the weight unit will be set according to the
respective aircraft type and weight unit defined for the flight.
On customer request the possibility for manual change of the
weight unit may be switched off.

6: Weight and Balance Data - Continued
Quality Display of planning status of weight and balance data (WAB)

for the flight. It indicates the source and accuracy of the
Estimated Zero Fuel Weight data. Possible options are:
No Info No information available
Booking <variable time> Option to display the status and
Example: Booking (5HRS) the current time difference
between the message creation
time and the STD of the flight
(variable time).
OPS EZFW
OPS EZFW (weighted) Action driven mode
Load sheet ZFW
First and Final Station UNISYS transaction
7a: Command
Buttons Title/Button Description
SELECT Selects data of a flight record from the database according to

specified selection criteria.
Note: If there is more than one scenario stored in the database for the
respective flight, window 'List of Scenarios' opens showing all
scenarios available. The user can choose one of the scenarios
from the list.
INSERT Inserts the planning parameter scenario for the respective

flight into the database.
This covers all data currently displayed in window 'Planning
Parameter' and if applicable all data defined in window
'PET/ETOPS Parameter'.
The planning parameter scenario is an essential basis for all
further flight planning calculations.
FLT LIST Opens window 'Flight List'.
RTE DEF Opens window 'Route Definition', loads the data of the flight
currently being processed, and closes window 'Planning
Parameter'.
ANALYSIS Opens window 'Analysis', loads the data of the flight currently
being processed, and closes window 'Planning Parameter'.
If window 'Analysis' is opened for the first time for a certain
flight, window 'Route Options' opens additionally. Here the
user can determine the optimization criteria for flight planning
calculation.

7a: Command Buttons - Continued
OFP Opens window 'FPL / OFP Transmission', loads the data of

TRANS the flight currently being processed, and closes window
'Planning Parameter'.
Button is only applicable if flight data is currently loaded and
the flight is available in the flight list.
WX/NOTAM Opens window 'Weather / NOTAM', where the user can
retrieve weather and NOTAM information about airports and
areas of airspace.
A/C DEV Opens window 'List of Aircraft Deviations'.
REMARK Opens window 'Remarks' displaying dispatch bulletins and
remarks relevant for the flight. In this window remarks can be
changed and/or added.
Note: Dispatch bulletins are are for information only, and are maintained
in window 'Dispatch Bulletin'.
Upon request, the button 'REMARK' can be configured to

indicate if the remarks related to a current flight event have
been checked in window 'Remarks':
Remarks are Font Color of Button 'REMARK' Indicator is
not available black
standard
available red
checked yellow
optional
updated red
WX NTM Opens window 'Airport Suitability Weather NOTAM TEST',

CHK where the user can perform a Weather/NOTAM check for
test purposes and survey results in detail.
CLEAR Clears the data currently displayed.
HELP Function not established.
PRINT Prints the data currently displayed in window 'Planning
Parameter'.
CLOSE Closes window 'Planning Parameter'.

7b: Command The following command buttons are available if either the optional
Buttons for Lido/Flight module 'Lido Integrated Takeoff Performance LinTop' or the
LinTop or optional Lido/Flight module 'Lido Integrated Landing Performance LinLap'
LinLap is implemented.
MALTOW Runs an automatic takeoff performance calculation

(applicable for 'LinTop').
T/O REQ Opens window 'Takeoff Performance Request', in which the
user can launch an interactive takeoff performance
calculation (applicable for 'LinTop').
T/O RES Opens window 'Takeoff Performance Result', in which the
results of the takeoff performance calculation are displayed
(applicable for 'LinTop'). Button is only available if a takeoff
performance calculation has been run.
If more than one takeoff performance calculation has been
run, a list box opens, from which the user can choose a
calculation record.
MALLAW Runs an automatic landing performance calculation
(applicable for 'LinLap').
LDG PERF Opens window 'Landing Performance' to run a semi-
interactive landing performance calculation (applicable for
'LinLap').

5.4 Window 'Alternate Information'
Window 'Alternate Window 'Alternate Information' allows maintaining and reviewing alternate
Information' route information, specifying flight level to the alternate airport and
modifying the runway of an alternate airport. All data displayed in this
window is considered for alternate planning.
Path: 'Flight Planning'>'Flight List' > flight-related context menu
'Edit Planning Parameters...' > right-click in an alternate entry field
Alternate/RWY ICAO code of alternate airport and used runway

MAX Flight Maximum flight level to the alternate airport, which will be
Level considered in the flight calculation [FF] flight level feet
Free Flight Toggle for defining a waypoint as free flight waypoint.
Available for optional function 'Free Flight'. For more
details see document 'Free Flight Feature Description'.
Waypoint Code Waypoint code or coordinates of the waypoint
Symbol Symbol dependent on waypoint type as defined in window
'Waypoint'
Ctry Country code of the waypoint
AWY/ Airway or route code as defined in the windows
Route Code 'Airway/Directs' or 'Terminal Procedure.

Window 'Alternate Information' - Continued
Route Type Route type as defined in the windows 'Airway' or 'Terminal

Procedure
Example: AWY, DCR, Terminal Procedure
Vert Unit Unit of vertical data [FF] flight level feet, [FT] feet, [FM]
flight level meter, or [m] meter
Forced Toggle for enabling/disabling a forced flight level
calculation for a segment where the flight level is not
defined
Alternate route Toggle activates/de-activates the optional function of
auto select automatically selecting pre-defined fix alternate routes.
ON/OFF
Independent on the setting of this toggle Lido/Flight
considers the content of the table of 'Alternate
Information' for selecting alternate route information.
List of Routes Button to open window 'List of Routes' which supports the
user in selecting available route portions.
For more information on this window, see document 'Data
Maintenance User Manual', chapter 'Window List of
Routes'.
Detailed Route Button to open window 'Detailed Route' which displays
further details of the selected route portion, e.g. waypoints
and AWY/RC.

5.5 Window 'Analysis'
Purpose and Window 'Analysis' allows the user to

Structure of
Define additional parameters for flight planning calculations
Window 'Analysis'
Trigger the calculation
Review calculation results in detail
Perform a reclearance calculation
Perform an inflight assistance calculation
Path: 'Flight Planning' > 'Analysis'

or: 'Flight Planning' > 'Flight List' > flight-related context menu
'Review Analysis...'
1: Basic Flight Data 6: Graphic
2: Scenario Information 7: OFP Functions
3: Parameters for Calculation 8: Command Buttons
4: OFP Calculation and Details 9: Traffic Flow Restriction - TFR
5: OFP Overview

1: Basic Flight Data
AL IATA airline code.

Flight-No. Flight number.
OS Operational suffix.
Date Date of flight.
Format: DDMMMYY, e.g. 30DEC05
DEP ICAO code of departure airport.
Drop-down list Drop-down list to specify the runway of the departure
below 'DEP' airport used for flight plan calculations.
Default value: preferential runway, if available,
STD Scheduled time of departure.
Entry field Entry field for flight-plan departure day and time (estimated
below 'STD' time either entered manually or received via interface).
STA Scheduled time of arrival.
Entry field Entry field for flight-plan arrival day and time (estimated
below 'STA' time either entered manually or received via interface).
DEST ICAO code of destination airport.
Drop-down list Drop-down list to specify the runway of the destination
below 'DEST' airport used for flight plan calculations.
Default value: preferential runway, if available,

2: Scenario
Information
Init. Time Display field showing the time, when the last Airport
Suitability Check has been performed for this planning
parameter scenario, triggered by clicking on button
'Initialize'.
Non ETOPS Drop-down list showing if the planning parameter scenario
includes ETOPS parameters or not.
Possible values:
ETOPS Scenario includes ETOPS parameters.
Non ETOPS Scenario does not include ETOPS parameters.
3: Parameters for
Calculation

3: Parameters for Calculation - Continued
Operational Drop-down list to select an operational case for which the

Case calculation shall be performed. Possible values:
Standard ST
One engine out 1X
Gear down GD
Spare engine SE
The selected value determines the performance table
used for the calculation.
Set to Def. Button to retrieve the default settings for operational case,
climb, cruise, and descent procedures.
Climb Set of fields for specifying the climb procedure:
The drop-down list 'Procedure' allows the specification of
the procedure type for the climb phase.
Possible values:
Option Description
Speed Triggers drop-down lists 'MN' and 'IAS', where
the user can select appropriate mach number
and indicated airspeed; default values are
maintained in the windows 'Aircraft Operator
Maintenance' and optionally 'Leg Policy'.
ECON Economic climb procedure;
Only available if 'ECON' has been selected for
the cruise procedure; triggers the entry field
'Cost Index', which is automatically filled with
the value displayed in corresponding field of
cruise procedure.
Additionally the user can optionally specify a thrust rating
by selecting respective value from the drop-down list
'Thrust Rating'.
Options depend on the values provided within
performance tables for respective aircraft performance
type by Lufthansa Systems and can be:
F : Full thrust
R1 : Derate 1
R2 : Derate 2
R3 : Derate 3

Cruise Set of fields for specifying the cruise procedure:

the procedure type for the cruise phase.
Possible values:
Option Description
LRC Long Range Cruise
ECON Economic cruise procedure; triggers the entry
field 'Cost Index', where the user can enter an
appropriate cost index; default values are
If optional feature dynamic cost index is
configured, the toggle 'Dyn.' is available. If
activated the cost index for the current flight is
calculated dynamically and the result is
displayed in field 'Cost Index'. A manual change
of this value deactivates the function for the
selected scenario.
MEC Maximum Endurance Cruise

Fixed MN Drop-down list to determine the speed within fixed MACH

Airspace / airspace / airways. For details see document 'Speed
Airway Procedures Feature Description'.
Possible values:
Option Description
Optimum MN Average of speed at entry and exit point
of fixed MACH airspace.
Default MN Fix speed as maintained in window
'Aircraft Operator Maintenance' as
default cruise speed.
Fixed MN OFF Disables consideration of fixed MACH
airspace.
VSOPS Drop-down list to enable/disable the VSOPS (Variable
Speed Operations) functionality.
For details see document 'Speed Procedures Feature
Description'.
Descent Set of fields for specifying the descent procedure:
the procedure type for the descent phase.
Possible values:
Option Description
ECON Economic descent procedure; only available, if
'ECON' has been selected for the cruise
procedure previously;
triggers the entry field 'Cost Index', which is
automatically filled with the value displayed in
corresponding field of cruise procedure.
REM Fuel Entry field for remaining fuel (to be entered manually).
Fuel Gravity Fuel gravity [kg/l] to be assumed for the calculation of the
tank capacity.
By default a fuel gravity value of 0.8 kg/l is displayed;
Lufthansa Systems maintains this value in window 'Airline'.

Prognosis Drop-down list to define the prognosis of Upper Air Data to

be used for flight planning calculations.
Possible values:
Option Description
Actual Upper Air Data is interpolated in order to
(Default) match the conditions of the actual time as
close as possible for each calculated
segment.
ISA-WX Calculations are based on ISA without wind.
Prognoses for current date + 36 hours
JAN DEC Statistics for a certain month of year: Triggers
drop-down list for specifying deviation,
including these options: Avg (default), 68%,
85%.
SUMMER/ Statistics for SUMMER / WINTER.
WINTER
YEAR Statistics for the whole YEAR.
JAN-MAR, Statistics for a quarter of the year.
APR-JUN,
JUL-SEP,
OCT-DEC
Statistical values trigger an
additional drop-down list for
specifying the deviation.
Possible values: Avg (default),
68%, 85%.
Route Button to open window 'Route Options', where the user can
Options define routes and/or optimization criteria to be used for
calculations.
Additionally window 'Route Options' allows the user to
enable/disable Free Flight calculations (for details see the
optional document 'Free Flight Feature Description').
Note: Window 'Route Options' opens automatically, when the user
opens window 'Analysis' and no OFP has been calculated for
respective planning parameter scenario before.
Restriction Button to open window 'Restrictions', where the user can

define restrictions to be considered for flight planning
calculations.

Opt Param Button to open window

'Optimization Parameter' in
which the defined minimum
cruise times can be altered
or deactivated for the current
flight event.
Customers using the optional function for calculation of

CO2 emissions and trading costs may alter pre-set data for
emission index and price allowances for CO2 emissions for
the respective flight.
Data Description
Emission Index Index, which translates the fuel burn into
an equivalent CO2 emission.
It is dependent on the used fuel type.
Default value is 3.15 [kg CO2/kg fuel]
Price Allowances Price for CO2 emission allowances
within the Emissions Trading System
(ETS) [US$/t CO2] or [/t CO2]

4: OFP Calculation
and Details
Restriction Button to open window 'Restriction Viewer' displaying

view. restrictions for a calculated route.
It displays the waypoints and connected airways of the

marked route. The following indicators are possible in the
column 'Restriction'. Red font color of the button label
indicates that there is an unspecified restriction, which is
relevant for the calculated route. Unspecified restrictions
can be identified by the prefix 'U'.
A AIP Restriction
C Company NOTAM
N NOTAM
S Supplementary Restriction

4: OFP Calculation and Details - Continued
Route Button to open window 'Route Survey' displaying a

Survey description of the calculated route.
Note: There are two options for the display of the route: ATS flight plan
route (default) and waypoint sequence. The user determines the
display option by selecting/deselecting the toggle 'Route Display:
ATS/Waypoint' in window 'Analysis'.
Route Display: Toggle to specify the type of display in window 'Route

ATS / WPT Survey'.
Possible options:
ATS (ATS flight plan route; default)
WPT (waypoint sequence).
Inflight Button to open window 'Inflight Assistance' with a
calculated OFP loaded. Here the user can recalculate the
OFP from an en-route waypoint to destination.
ALTN Button to open window 'Alternate Survey' displaying the
Survey alternate calculations of the marked OFP.
Tankering Button to start a tankering calculation of an OFP.
For details see document 'Tankering Feature
Description'.
ETOPS Button to open window 'PET/ETOPS Output' displaying the
results of the ETOPS calculation of the marked OFP.
Reclearance Button to open window 'Reclearance' for performing a
reclearance calculation.
Analysis Button to trigger the flight planning calculations, which are
based on the planning parameter scenario currently loaded,
the selected route options and the restrictions defined to be
considered.
In background Optional function. Toggle for switching on/off if the OFP
calculation is to be performed in background. If selected,
Lido/Flight calculates in background and the user is able to
continue working with Lido/Flight.

5: OFP Overview
The table 'OFP Overview' displays key data of all calculated OFPs. Every
OFP is displayed in a separate column. Every row displays certain
information for the OFP.
The display and label of key data differs according to the settings of
customer; the screenshots represent the possible settings.
A color-coding for the labels of the rows is used to classify data as follows:
Red font color Important data

Blue font color Editable data
Check boxes in front of every row can be used to sort OFPs by respective
criterion.

5: OFP Overview - Continued
A special copy function is triggered

by a right mouse click/double left
mouse click on a marked OFP. A
'Copy Control Panel' opens showing
parameter for further optimization.
optimized in calculation.
Selected parameter from the
OFP is copied as fix value.
Example:
If you select flight level, the cruise flight level
in reclearance calculation remains as
optimized in calculation of basic OFP.
Scenario No. Display field showing the number of the currently marked
OFP as displayed in field 'OFP NO'.
ROUTE Designator for For OFPs based on free optimization.
optimization type
Route designator For OFPs based on certain routes like
predefined routes, North Atlantic
Tracks, Polar Tracks, South Atlantic
Tracks, Pacific Tracks, PACOTS or
routes defined in window
'Route Definition'.
Possible values for optimization types:
No Yes No Yes
Non-ETOPS ETOPS
Min. Cost Track MCT MCT/R E/MCT E/MCT/R
Min. Fuel Track MFT MFT/R E/MFT E/MFT/R
Min. Time Track MTT MTT/R E/MTT E/MTT/R
Min. Distance Track MDT MDT/R E/MDT E/MDT/R
Color-coding:
Default font color is black;
Font color of copied OFPs is purple.

OFP NO OFP number according to calculation sequence

OFP-No. 1
OFP-No. with ETOPS-No. 1/0/1 (indicator for ETOPS
calculation)
Color-coding:
Background color of the OFP last sent is red.
REG Registration of the aircraft or type of aircraft
FIN NO Unique number as an additional ID of registration
CRUISE Cruise procedure,
e.g. MN/IAS, LRC, CI, MEC, VRBL (variable)
TRIP Trip fuel [kg or pounds]
TTIME/ Trip time/flight time [minutes]
FLT TIME
ETA Estimated time of arrival as calculated excluding
taxi-in time
If the ETA is later than STA, the resulted value is
indicated in red color.
Format: hhmm, e.g. 1720
COSTS Costs, considering:

Assumed fuel costs: (Trip Fuel + Taxi Fuel) x Fuel Price
ATC en-route charges
Time costs (aircraft value x trip time)
Optionally the costs for CO2 emissions
Note: This value does not reflect the exact costs of the entire
operation, but the relation between cost values of different
OFPs is considered appropriate for finding the route with the
lowest cost structure.
BURN OFF Trip fuel [kg or pounds]

CONT Contingency fuel [kg or pounds]
CONT POL Contingency fuel policy of the airline
ADD FUEL Additional fuel [minutes]
T/O FUEL Take-off fuel [kg or pounds]
RESRVE Reserve fuel [minutes]
ALTN ICAO airport code of alternate airport
Note: The determination of the alternate airport is based on the
alternate selection of the planning parameter scenario.

AFUEL/ Alternate Fuel [kg or pounds]

ALTNFUEL
HOLDING Holding Fuel [kg or pounds]
PLNTOF Planned Takeoff Weight [kg or pounds]
EXTRA Extra fuel [kg or pounds]
TTL FUEL Total fuel [kg or pounds]
P EXTRA Possible extra fuel [kg or pounds]
TAXI Taxi fuel [kg or pounds]
BLOCK Block fuel [kg or pounds]
DIST Total distance of flight route [NM]
AVG WC Average wind component,
including climb and descent phase.
Prefix indicates wind direction:
P = plus = tailwind
M = minus = headwind.
MAXZFW Maximum Zero Fuel Weight [kg or pounds]
ESTZFW Estimated Zero Fuel Weight [kg or pounds]]
PLNZFW Planned Zero Fuel Weight [kg or pounds]
MALTOW Maximum Allowed Takeoff Weight [kg or pounds]
PLNTOW Planned Takeoff Weight [kg or pounds]
MALLW Maximum Allowed Landing Weight [kg or pounds]
PLNLW Planned Landing Weight [kg or pounds]
ADDFU Additional fuel [minutes]
For an inflight calculation on customer request this field
can display the delta fuel as shown in window 'Inflight
Assistance', line 'D FUEL'. If the delta fuel is negative, this
field in empty.
TCAP Tank Capacity [kg or pounds]
SAVINGS Possible savings in US dollars if tankering scenario is
accepted; applicable for tankering flights only.
MAX FL Maximum flight level
Optimization may be limited to a maximum level.

6: Graphic
The graphic tool provides a graphical display of various kinds of data like
flight routes or aeronautical objects in order to illustrate geographical
correlations of these objects. The user can access this tool within several
contexts and modules of Lido/Flight. For more details about graphic
handling see document 'Graphic Tool Feature Description'.
Graphic Button to open the graphical display window of the

graphic tool (only available, if data to be displayed are
loaded in the main window).
As soon as the display window is open, the label of this
button changes to 'Update'.
Update Button to update graphical display window.
Off Button to close the graphical display window. If not closed
with this button, the graphic is still open in the
background.
Zoom Button to enable the zoom mode of the display window.
Menu Button to enable the menu in the display window.
With the menu enabled, certain objects can be displayed
additionally. All available options are described in feature
description 'Graphic Tool'.
Map Drop-down list to specify the details to be displayed in
window 'Flight Planning Graphic Window'. Options are:
Map: (default) Horizontal routing of the OFP
including following objects: departure and
destination airports, en route and destination
alternates, waypoints of the routing,
ETOPS circles (if applicable).
Height: Height (FL) for vertical routing (NM) of the
OFP.
Temp: Temperature (C) along the covered distance
(NM).
Fuel: Fuel consumption (kg) along the covered
distance (NM).
Note: For the options 'Height', 'Temp', and 'Fuel' window 'Flight
Planning Graphic Window' opens as soon as the user selects
the option. To open the window in 'Map' mode, the user has to
click on button 'Graphic'.
ALTN Drop-down list to specify the number of alternates to be

displayed on the map. Possible options:
None, 1 (default), 2, 3, or ALL.

7: OFP Functions
The area 'OFP Functions' allows the user to run a number of operations for
a selected OFP.
Remove OFP Button to remove the OFP currently marked from the
table.
OFP Button to open window 'OFP' with a detailed description of
the OFP currently marked.
More Info Button to open window 'More Info' showing the initials of
the dispatcher who calculated the currently marked OFP.
Tankering information (only applicable for tankering
OFPs):
Addfu Option, number of OFP used as basis for tankering
calculation, minimum saving, reason for tankering.
Recheck Button to trigger a recheck for the OFP currently marked.
Window 'Recheck' opens displaying the 'List of Airports'
with the results of the recheck.
8: Command
SELECT Selects a planning parameter scenario according to the

specified selection criteria.
If there is more than one planning parameter scenario
stored in the database that matches the specified selection
criteria, window 'List of Scenarios' opens displaying all
matching planning parameter scenarios, from which the
user can choose one.
PLAN PARAM Opens window 'Planning Parameter' and loads the planning
parameter scenario of the flight currently being calculated.
RTE DEF Opens window 'Route Definition', where the user can define
a route before flight plan calculations or modify the route
afterwards.
If an OFP has been marked in window 'Analysis', the
routing of this OFP is displayed in window 'Route
Definition'.

8: Command Buttons - Continued
OFP TRANS Triggers a recheck for the OFP currently marked and
Opens window 'FPL/ OFP Transmission' if the recheck
does not detect any problems; OFP data are loaded in
window 'FPL/OFP Transmission', or
Opens window 'Recheck' if the recheck detects a
situation, which requires dispatcher's awareness.
WX/NOTAM Opens window 'Weather / NOTAM', where the user can
retrieve weather and NOTAM information about airports
and areas of airspace.
COSTS Opens window 'Cost Viewer' displaying a detailed list of
ATC Charges for the OFP currently marked.
REMARK Opens window 'Remarks' displaying dispatch bulletins and
remarks relevant for the flight.
Remarks can be changed and/or added; dispatch bulletins
are for information only.
Note: Dispatch bulletins are maintained in window 'Dispatch Bulletin'.
Red font color on the button indicates that a remark is
available for this flight.
CLEAR Clears the data currently displayed.
REFRESH Triggers a screen reset.
PRINT Prints the data currently displayed in window 'Analysis'.
CLOSE Closes window 'Analysis'.
9: Traffic Flow Toggle and buttons are available for

Restriction - TFR customers using the Lido/Flight
module 'Traffic Flow Restriction
(TFR)'.
For more details about TFR see the documents 'Traffic Flow Restriction
Functional Description, User Manual and Field & Button Description'.
Check box Check box for selecting to calculate flight in the debug
'TFR Debug' mode.
TFR debug Button opens window 'TFR Debug Info'.
TFR Legality Button triggers a legality check and opens window 'TFR
Legality Check' displaying a list of all broken traffic flow
restrictions.

5.6 Window 'Weather/NOTAM'
Purpose and Window 'Weather / NOTAM' allows the user to view flight-related weather
Structure of and NOTAM information. The window consists of several index cards each
Window of which provides different kinds of flight-related information. At the moment
'Weather/NOTAM' only index cards 'Weather/NOTAM' and 'Weather/NOTAM add. Airports' are
enabled.
Path: 'Flight Planning' > 'Planning Parameter' > button 'WX/NOTAM'
or 'Flight Planning' > 'Analysis' > button 'WX/NOTAM'
1: Flight Data
2: Index Card 'Weather / NOTAM'
3: Index Card 'Weather NOTAM add. Airports'
4: Command Buttons

1: Flight Data Flight data are automatically loaded into window 'Weather / NOTAM' from
the flight currently being calculated and loaded in window 'Planning
Parameter' or 'Analysis'.
AIRLINE IATA airline code

REG Aircraft registration
DEP ICAO airport code for departure airport
DEST ICAO airport code for destination airport
ETD Estimated time of departure
ETA Estimated time of arrival
from/till Time period in which the displayed weather and NOTAM
information is valid; it refers to the flight currently being
calculated.
From value = ETD
Till value = ETA + 3 hours
OFP No Drop-down list to select an OFP for the display of
additional airports.
This drop-down list has an effect on index card
'Weather/NOTAM add. Airports' only.

2: Index Card This area displays flight-related weather/NOTAM information for

'Weather/NOTAM' departure, destination and alternate airports.
The index card is divided into different areas, which are described in
detail:
2a: Airports 2c: Airport Information Line
2b: Airport Status Information (optional) 2d: Display of Information
2a: List box for the display of ICAO airport codes.

Following airports are listed:
Airports
Departure
Destination
Alternates displayed in window 'Planning Parameter',
panel 'Alternates' (1 4)
Additionally all alternate airports available for the
given combination of aircraft registration and
destination
(only displayed if button 'SELECT ALTN' has been
clicked)
The airports displayed refer to the flight currently being
calculated.

2: Index Card 'Weather/NOTAM' Continued
2b: Displays status information on the selected airport as well

as the period of time during which the displayed airport
Airport Status
status is valid.
Information
(optional) Airport status information is available only if an Airport
Suitability Check has been performed in the window from
which window 'Weather/NOTAM' has been opened, i.e.
the airport status is displayed in the original window.
This feature is optional and has to be subscribed by the
customer.
2c: As soon as one airport is selected for the display of
weather and NOTAM information, the airport information
Airport
line displays following details of the airport:
Information
Line IATA Airport Code
Airport Name
Elevation
Variation
The airport information line refers to the airport currently
selected.
2d: In this area following weather and NOTAM information
referring to the airport currently selected are displayed:
Display of
Information 1. SA: actual weather
2. FC: latest available forecast covering the time
period between ETD and ETA + 3 hours
(forecast valid for 12 hours)
3. FT: latest available long-term forecast covering the
time period between ETD and ETA + 3 hours
4. NOTAMs, valid between ETD and ETA + 3 hours
Note: If the time period between ETD and ETA + 3 hours cannot be
covered with valid FC/FT messages, the latest FC/FT
messages valid within the last 48 hours are displayed.
If the button 'MORE' has been clicked, the display area is

divided into two parts: the upper one displays additional
airport information, the lower one displays weather and
NOTAM information as described above.

3: Index Card This area displays flight-related weather/NOTAM information for additional
'Weather/NOTAM airports somehow related to a certain flight.
add. Airports'
The index card is divided into different areas, which are described in detail:
3a: Airports 3d: Display of Information
3b: Period of Validity 3e: Additional Airports
3c: Airport Information Line
3a: Airports List box for the display of ICAO airport codes. Those
airports are displayed that have been activated via the
check boxes in area 3e 'Additional Airports'; for further
details see description of area 3e.
The airports displayed refer to the flight currently being
calculated.
3b: Period of Line 'Weather and NOTAM from until '
Validity indicates the time period displayed weather and NOTAM
information are valid for. The time period refers to the
flight currently being calculated.
From value = ETD
Till value = ETA + 3 hours
3c: Airport As soon as one airport is selected for the display of
Information weather and NOTAM information, the airport information
Line line displays following details of the airport:
IATA Airport Code and Airport Name
Elevation
Variation
The airport information line refers to the airport currently
selected.

3: Index Card 'Weather/NOTAM add. Airports' Continued
3d: Display of In this area following weather and NOTAM information

Information referring to the airport currently selected are displayed:
1. SA: actual weather
2. FC: latest available forecast covering the time
period between ETD and ETA + 3 hours (forecast
valid for 12 hours)
3. FT: latest available long-term forecast covering
the time period between ETD and ETA + 3 hours
4. NOTAMs, valid between ETD and ETA + 3 hours
Note: If the time period between ETD and ETA + 3 hours cannot be
covered with valid FC/FT messages, the latest FC/FT
messages valid within the last 48 hours are displayed.
3e: Additional Check boxes to select the types of airports to be

Airports displayed in list box 'Airports'
Depending on the flight currently being calculated
following airport types may be available:
Takeoff Alternate
Via Alternate
Reclearance Airport/Alternate
Reclearance Fuel En-route Airport
ETOPS Adequate/Suitable/Available Airport
Fuel En-route Alternate
Inflight Destination/Alternate/via-Alternate
Multiple selections are possible. If more than one check
box is selected, all airports of selected types are
displayed within the list box 'Airports'. They are arranged
in groups according to their type.
Note: Every airport is displayed only once, even if it belongs to more
than one group of additional airports and all of them are
selected for display.
This applies particularly to ETOPS airports: Every 'ETOPS
suitable airport' is automatically an 'ETOPS adequate airport'
and a 'ETOPS available airport'. And every 'ETOPS adequate
airport' is automatically an 'ETOPS available airport'.

4: Command
SELECT ALTN Button to load following airports into the list box 'Airport'.
Departure airport
Destination airport
All Alternate airports available for the given
combination of aircraft registration and destination.
The button is effective on index card 'Weather/NOTAM'
only.
MORE Button to load additional airport information such as
minima or additional remarks into the display area.
Following information is displayed (if available):
Landing Minima (Company Landing Minima)
Landing Minima for ALL airlines
Alternate Minima
Takeoff Minima
Airport Authorization Check
Additional Remarks
Note: It can be defined, which weather minima are displayed as
well as the sequence in which they are displayed.
For Minima following details are displayed (if applicable):

RWY: Runways of the airport currently selected,
for which minima are available in the
database
Airl: Indicates minimum type:
If value is Then type is
ALL State Minimum (AIP)
IATA airline code Company Minimum
Acft CAT: Aircraft category
Length: Length of runway (meters)
APCH: Approach procedure
DH: Decision Height (feet)
RVR/VIS: Runway Visual Range/Visibility (meters)

4: Command Buttons Continued
MORE - An Airport Authorization Check is run. If no authorization

continued is available in the database, following remark is displayed:
NOT ALLOWED FOR LANDING.
Additional Remarks are displayed as maintained in
window 'CurFew / ATC Closing Times'.
Remarks are divided into following sections:
OPS
ATC
RST (restrictions)
RMK (other remarks)

5.7 Window 'Route Options'
Purpose and To start an analysis at least one (pre- or self-defined) route or type of route
Structure of the optimization must be selected. Window 'Route Options' offers a menu of
Window available options.
'Route Options'
In window 'Analysis', the button 'Route Options' opens the respective
window if a flight planning scenario was inserted. The dispatcher can select
required route options. The window is opened automatically upon opening
window 'Analysis' if no OFP has been calculated previously.
'Route Options'
1: Area 'Specific Selection Criteria'
2: Area 'Route Types':
Australian Organized Track Structure (AUSOTS)
NAT and NOR Tracks (OTS)
South Atlantic Tracks (SAT)
Polar Tracks (POL)
ATC Rerouting Proposal (ATC RRP)
Pacific Organized Track System (PACOTS)
Predefined Routes/Playbook Routes/Coded Departure Routes
3: Area 'Optimization Criteria'

5.7.1 Area 'Specific Selection Criteria'
Area 'Specific
Selection Criteria'
No Weekend Check box for including/excluding weekend routes.

Weekend: All available routes including weekend
only routes are selected. (Default)
No Weekend: All routes but excluding weekend only
routes are selected
use non-publ. Check box for selection if either published direct
DCT segments only, or additionally non-published direct
segments are to be considered during flight planning.
Published direct segments are published officially in AIS
documentation.
Per default, the check box is selected, which means all
available published and non-published directs are
considered. The default setting can be configured on
customer request.
Settings of Toggle Key Usage of Directs
'Use non-publ. DCT'
Selected Published and
non-published directs
Deselected Published directs
Note: The separation of the direct segments in the aeronautical
database is not performed yet. It is recommended to have the
check box selected.

5.7.2 Area 'Route Types'
Area 'Route Types'
The route type buttons enable the user to open a list with routes of the
respective type, offered for the corresponding city pair of the flight. For the
calculation of the chosen route the selected restrictions in window
'Restriction', selected either by default or selected manually, are considered
during the calculation of that route.
The following sub-chapters describe the single windows, which can be
opened with the buttons described as following:
AUSOTS Opens window 'AUSOTS Composition' for the composition

of routes using tracks of the Australian Organized Track
Structure (AUSOTS).
For a detailed description of this window and the function
see document 'Organized Track Handling Feature
Description'.
OTS Opens window 'Manual OTS Composition' for the
composition of NAT and NOR routes using tracks of the
Organized Track System (OTS).
Description'.
SAT Enlarges the window and displays index card 'SAT ' for
the selection of South Atlantic Tracks.
POL Enlarges the window and displays the index card 'POL' for
the selection of the Polar Tracks.
ATC RRP Enlarges the window and displays the ATC Rerouting
Proposal.

Area 'Route Types' - Continued
PACOTS Opens window 'PACOTS Composition' for the composition

of routes using tracks of the Pacific Organized Track
System (PACOTS).
Description'.
PRED/ Enlarges the window and displays multiple index cards for
Playbook/ the selection of:
Coded Dep
Predefined routes (company / predefined routes)
Route
Playbook Routes
Coded Departure Routes
The route types Playbook and Coded Departure are
optional and have to be configured by Lufthansa Systems
on customer request. If these two route types are not
configured, the button is displayed as 'PRED' button. The
opened window displays the index card 'PRED' only.

5.7.2.1 AUSOTS Tracks
AUSOTS
Window 'AUSOTS Composition' is designed to let the user manually

compose routes using flexible tracks of the Australian Organized Track
Structure (AUSOTS).
AUSOTS routes consist of Route to Track, Route from Track and
Flex Route which is the actual AUSOTS flexible track. Depending on the
city pair of flight, the offered routes are inbound or outbound routes.
For a detailed description of this window and the function see document
'Organized Track Handling Feature Description'.

5.7.2.2 NAT and NOR Tracks (OTS)
NAT and NOR

Tracks
Window 'Manual OTS Composition' is designed to let the user manually

compose NAT routes and NOR routes.
NAT routes consist of Route to/from Track, NAT track, Common Portion
and Non-Common Portion. These NAT routes are subsequently used for
flight planning calculations. Depending on the city pair of flight, the offered
routes are eastbound routes or westbound routes.
NOR routes consist of Route to Track, NAT track, NOR track and Non-
Common Portion. NOR tracks are available in westbound flight direction
only.

5.7.2.3 South Atlantic Tracks (SAT)
South Atlantic
Tracks (SAT)
To see available South Atlantic Tracks the user can click on button 'SAT'.
Window 'Route Options' enlarges and displays an index card with available
South Atlantic Tracks. Each route is shown with type, name, route waypoint
description and distance. The dispatcher can chose the required route by
selecting the respective row.
Per default the method for the optimization of the tracks from the departure
airport to the start point of the SAT and from the end point of the SAT to the
destination airport is Minimum Distance Track with Restrictions (MDT/R).
South Atlantic Tracks are maintained by Lufthansa Systems in window
'Predefined Route Maintenance'.
Type ST: South Atlantic Track.

Name Airway/Route Code identifying name of the route.
Routes maintained by Lufthansa Systems are inserted
with the short cut: 'NB' for north bound / 'SB' for south
bound plus main airway.
Route Description of route by listing all waypoints.
Distance Distance of complete route in [NM].
Purp. Not applicable for SAT Tracks.
For Predefined/Company Routes, Playbook Routes and
Coded Departure Routes only. See chapter 'Predefined
Routes/ Playbook Routes/Coded Departure Routes'.

South Atlantic Tracks (SAT) - Continued
Rmk Not applicable for South Atlantic Tracks. For

Predefined/Company Routes, Playbook Routes and
Coded Departure Routes only.
FMS Not applicable for South Atlantic Tracks. For
Predefined/Company Routes only.
Notes Display of available notes as inserted in window
FMS only Not applicable for South Atlantic Tracks. For
Predefined/Company Routes only.
5.7.2.4 Polar Tracks (POL)/Arctic Tracks
Polar Tracks (POL)/

Arctic Tracks
To see available Polar Tracks and Arctic Tracks the user can click on
button 'POL'. Window 'Route Options' enlarges and displays an index card
with Polar Tracks. Each route is shown with type, name, route waypoint
description and distance. The dispatcher can choose the required route by
selecting the respective row.
Per default the method for the optimization of the tracks from the departure
airport to the start point of the Polar Track and from the end point of the
Polar Track to the destination airport is Minimum Distance Track with
Restrictions (MDT/R).
Polar Tracks are maintained by Lufthansa Systems in window 'Predefined
Route Maintenance'.

Polar Tracks (POL)/Arctic Tracks Continued
Type PT: Polar Track.

with the shortcut: 'WB' for westbound plus 'ARCTIC' plus
Track Identifier (e.g. 'O', 'R', 'S'), e.g. WB_ARCTICR.
Purp. Not applicable for Polar Tracks.
Coded Departure Routes only. See chapter 'Predefined
Routes/ Playbook Routes/Coded Departure Routes'.
Rmk Not applicable for Polar Tracks.
Coded Departure Routes only.
FMS Not applicable for Polar Tracks.
For Predefined/Company Routes only.
FMS only Not applicable for Polar Tracks.
For Predefined/Company Routes only.

5.7.2.5 ATC Reroute Proposal (ATC RRP)
ATC Reroute
Proposal
(ATC RRP)
To see incoming rerouting proposals from ATC the user can click on button
'ARC RRP'. Window 'Route Options' enlarges and displays a table with
available ATC rerouting proposals.
The button 'ATC RRP' and corresponding window is only available for
flights, which have been calculated and filed and for which ATC has sent a
rerouting proposal.
This feature is only available if the Lido/Flight module 'Slot Manager' is
subscribed. For a detailed description of the feature see documents
'Slot Manager Functional Description and User Manual'.

5.7.2.6 PACOTS Tracks
PACOTS
Window 'PACOTS Composition' is designed to let the user manually

compose routes using flexible tracks of the Pacific Organized Track System
(PACOTS).
PACOTS routes consist of Departure Route, Routes to/from Track, Flex
Route which is the actual PACOTS track, and Arrival Route. Depending on
the city pair of flight, the offered routes are eastbound routes or westbound
routes.

5.7.2.7 Predefined Routes/Playbook Routes/Coded Departure Routes
Predefined Routes/ To see available pre-defined routes for the selected city pair (waypoint
Playbook Routes/ pair), the user can click on button 'PRED' or 'PRED/Playbook/Coded Dep
Coded Departure Route', depending on the configuration. Window 'Route Options' enlarges
Routes and index cards are displayed for the selection of:
Predefined Routes ('PRED')
Playbook Routes ('Playbook')
Coded Departure Routes ('Coded Dep Route')
Per default, the index card 'PRED' is selected. The listed route types are
maintained by Lufthansa Systems in window 'Predefined Route
Maintenance', except for Company Routes.
Each route is shown with type, name, route waypoint description, distance
and remark for weekend and night routings. The dispatcher can choose the
required route by selecting the respective row.
Index Card:
'PRED'
For predefined routes a pre-check of existing segment closures (NOTAM)

is performed for any time during entire flight event. If one or more segments
are closed the comment 'CLOSED' is displayed in the first line of the 'Route'
field.
Note: The preplanning status of this check needs to be considered. It is possible that after
actual time calculation a route, which was closed can be used and a route, which
was open, cannot be used for flight planning.

Index Card: 'PRED' - Continued
Type Display of 3-letter airline code of the airline for which the
company route is maintained.
with the shortcut: Point to point plus serial number or city
pairs (IATA code) plus serial number of the route, e.g.
FRALHR1.
Purp. Column indicates if the route is a company route of one of
the following types:
A: Active dispatch routes
P: Strategic and/or tactical planning routes
C: Contingency routes
'N' means no 'Purpose' maintained in window 'Predefined
Route Maintenance'.
The column is only displayed if the optional feature to
categorize and filter Company Routes, Playbook Routes
and Coded Departure Routes is subscribed. Category is
defined with drop-down list 'Purpose' in window
'Predefined Route Maintenance'. For predefined
Company Routes, CDR and Playbook Routes only.
See also description of the check boxes 'Active Dispatch'
'Planning' and 'Contingency'. For further details, see
document 'Data Maintenance User Manual', chapter
'Predefined Route'.
Rmk Display if route is a:
Week route 'W'
Weekend route 'WE'
Night route 'N'

Index Card: 'PRED' - Continued
FMS Column indicates if the route is a FMS route and if the

route exists in the onboard FMS database of the
respective aircraft or not.
'Y'(es): FMS route exists in the onboard FMS database
of the respective aircraft.
'N'(o): FMS route does not exist in the onboard FMS
database of the aircraft.
The column is only displayed if the optional feature 'FMS
Route Extraction' is subscribed. For further details, see
document 'FMS Route Extraction Feature Description'.
Active Dispatch Check box to filter routes according to the three types
during the interactive flight planning:
Planning
Contingency P: Strategic and/or tactical planning routes
If none of the three route types is selected, the routes
which have not been assigned to any of the three route
types will be displayed, and these will be marked with an
'N' in the 'Purp' column. The customer can define which
type is selected by default, when opening the window.
Routes are displayed according to maintenance in
window 'Predefined Route Maintenance', field 'Purpose'.
FMS only Check box to select all routes that are available in the
onboard FMS database of the selected aircraft. If the
feature 'FMS Route Extraction' is in use, a column 'FMS'
is displayed, indicating if the route is stored in the onboard
FMS database of the selected aircraft. In this case, the
corresponding check box to filter for FMS routes is
available.

Index Card:
'Playbook'
The National Playbook is designed to mitigate the potential adverse impact

to the FAA. In addition, they are designed for customers planning flight
events during periods of severe weather or other events that affect
coordination of routes. These events include, but are not limited to,
convective weather, military operations, communications, and other
situations. The routes start at an airport or waypoint and end at the
destination airport.
This route type is optional and can be configured by Lufthansa Systems on
customer request. The FAA published Playbook Routes are maintained in
window 'Predefined Route Maintenance' by Lufthansa Systems.
Type PB: Playbook Route

with the shortcut: Point to point or city pairs (IATA code)
plus 'PB' for playbook route plus serial number, e.g.
JFKLAXPB1.
Play Name Displays the Play Name of a Playbook Route, e.g. CAN 4
WEST, DEN ONL. Names are displayed as published
officially. They are maintained by Lufthansa Systems in
window 'Playbook Group and Playname'.

Index Card: 'Playbook' - Continued
Playbook Display of the category, which groups Play Names.

Group Possible categories are:
Airports
Airway Closures
East to West Transcon Routes
Regional Routes
West to East Transcon Routes
Groups are available if maintained by Lufthansa Systems
in window 'Playbook Group and Playname'. Categories
can be adapted according to the requirements published
officially.
Rmk. Display if route is a:
Week route 'W'
Weekend route 'WE'
Night route 'N'
Optimize using: Option fields to select a method for the optimization of the
tracks from the departure airport to the start point of the
route. The user can select the following optimization
criteria with or without consideration of restrictions as
maintained in window 'Restrictions'.
Option Option/R
Minimum Cost Track Minimum Cost Track considering

(MCT) maintained restrictions (MCT/R).
Minimum Time Track Minimum Time Track considering
(MTT) maintained restrictions (MTT/R).
Minimum Distance Minimum Distance Track
Track (MDT) considering maintained restrictions
(MDT/R).
Minimum Fuel Track Minimum Fuel Track considering
(MFT) maintained restrictions (MFT/R).
Per default the optimization criterion 'MFT/R' is selected.

Index Card: 'Playbook' - Continued
All PB for this Check box to display all maintained Playbook Routes for
DEST APT the destination airport. If check box is deselected, only
relevant Playbook Routes starting within the optimization
area are displayed. For the definition of optimization area
see document 'Optimization Feature Description'.
Active Dispatch Check box to filter routes according to following three
types during the interactive flight planning:
Planning
Contingency
type is selected by default when opening the window.

Index Card:
'Coded Dep Route'
Coded Departure Routes (CDR) linking city pairs were created to reduce
workload between control towers and the FAA Command Center. CDR
reduces key entry inputs for controllers and minimizes read-back time
between tower staff and pilots thus creating an abbreviated clearance.
More specifically, the CDRs provide more flexibility of selecting an alternate
departure for a specific airport when a weather or traffic constraint exists.
This route type is optional and can be configured by Lufthansa Systems on
customer request. The FAA published CDRs are maintained in window
'Predefined Route Maintenance' by Lufthansa Systems.
Type CD: Coded Departure Route.

with the shortcut: City pairs (IATA code) plus route
identifier and optionally serial number as published by the
FAA, e.g. FRALHR1.
Rmk. Display if route is a:
Week route 'W'
Weekend route 'WE'
Night route 'N'

Index Card: 'Coded Dep Route'- Continued
Active Dispatch Check box to filter routes according to following three

types during the interactive flight planning:
Planning
Contingency
type is selected by default when opening the window.

5.7.3 Area 'Optimization Criteria'
Area 'Optimization
Criteria'
The optimization criteria enable the user to select the required track
optimization with specific priorities such as costs, fuel, time and distance.
The user can select track optimization with or without defined restrictions.
For each selected optimization criterion a calculation is performed in
window 'Analysis'. E. g., in case a predefined route from any of the route
types is selected and options 'MCT' and 'MFT' are selected, three
calculations are performed: two free optimized tracks and one predefined
route.
No Yes No Yes
Non-ETOPS ETOPS
Minimum Cost Track MCT MCT/R E/MCT E/MCT/R

Minimum Fuel Track MFT MFT/R E/MFT E/MFT/R
Minimum Time Track MTT MTT/R E/MTT E/MTT/R
Minimum Distance Track MDT MDT/R E/MDT E/MDT/R

5.8 Window 'Route Definition'
Purpose and Window 'Route Definition' serves to define new routes including parameters
Structure of such as waypoints, flight level limitations, weights, additional fuel, and
Window optimization criteria.
'Route Definition' Additionally, it serves to modify existing routes, i.e. to change parameters of
a route already calculated.
The window is available in two modes:
In the entry mode, new routes can be defined or existing routes can
be modified.
In the display mode, all information is displayed on a route already
calculated and selected in window 'Analysis'.
Path: 'Flight Planning' > 'Route Definition'
'Review Route Definition...'
'Edit Planning Parameters...' > button 'RTE DEF'
'Edit Planning Parameters...' > button 'Analysis' > button 'RTE DEF'
1: Basic Flight Data 5: Graphic Tool

2: Route Definition Number 6: (Re) Calculation Buttons
3: Calculation Parameters 7: ETOPS Information
4: Route Details 8: Command Buttons

AL Airline code (IATA)

Flt-No. Flight number
OS Operational suffix; an alpha character which follows the
flight number. The meaning and use of the character is
defined by the customer.
Date Date of flight
Initialization Time when the last airport suitability check has been
Time performed for this planning parameter scenario, triggered
by clicking on button 'Initialize' in window 'Planning
Parameter'.
DEP ICAO code of departure airport
Field below Drop-down list displaying the runway of the departure
'DEP' airport used for flight plan calculations.
STD Scheduled time of departure
Format: DDHHMM, e.g. 041220
Field below Flight-plan departure day and time (estimated time of

'STD' departure [ETD] either entered manually or received via
interface).
Field below Entry field for flight-plan arrival day and time (estimated
'STA' time of arrival [ETA] either entered manually or received
via interface).
DEST ICAO code of destination airport
Field below Drop-down list displaying the runway of the destination
'DEST' airport used for flight plan calculations.
Registration Registration of aircraft which is used for flight plan
calculations.

2: Route Definition
Number
Rte Def No Route code number of the inserted route.

As long as no changes to the initially calculated route have
been made, the route code number is zero. If changes have
been made and the newly calculated route has been inserted
into the database, a different number is assigned.
3a: Calculation
Parameters
Non ETOPS Drop-down list showing if the planning parameter scenario

includes ETOPS parameters or not.
Possible values:
ETOPS Scenario includes ETOPS parameters.
Non ETOPS Scenario does not include ETOPS parameters.
Prognosis Drop-down list to define the prognosis of Upper Air Data to
be used for flight planning calculations.
Possible values:
Option Description
Actual Upper Air Data is interpolated in order to match the
(Default) conditions of the actual time as close as possible for
each calculated segment.
ISA-WX Calculations are based on ISA without wind.
date Prognoses for current date + 36 hours.
JAN DEC Statistics for a certain month of year: Triggers drop-
down list for specifying deviation, including these
options: Avg (default), 68%, 85%.
SUMMER/ Statistics for SUMMER / WINTER. Triggers drop-
WINTER down list for specifying deviation, including these
options: Avg (default), 68%, 85%.
YEAR Statistics for the whole YEAR. Triggers drop-down
list for specifying deviation, including these options:
Avg (default), 68%, 85%.
JAN-MAR, Statistics for a quarter of the year. Triggers drop-
APR-JUN, down list for specifying deviation, including these
JUL-SEP, options: Avg (default), 68%, 85%.
OCT-DEC

3b: Calculation
Parameters
Operational Drop-down list to select an operational case for which

Case the calculation shall be performed. Possible values:
Standard ST
One engine out 1X
Gear down GD
Spare engine SE
Fixed MN Drop-down list to determine the speed within fixed
Airspace/Airway MACH airspace / airways. For details see document
'Speed Procedures Feature Description'.
Possible values:
Option Description
Optimum MN Average of speed at entry and exit
point of fixed MACH airspace.
Fixed MN OFF Disables consideration of fixed MACH
airspace.
VSOPS Drop-down list to enable/disable the VSOPS (Variable
Speed Operations) functionality.
For details see document 'Speed Procedures Feature
Description'.

3c: Calculation
Title/ Description
Parameters
Button
OFP No Number of selected or calculated OFP.

MCT Optimization modes 'Minimum Cost
Track', 'Minimum Time Track', 'Minimum
MTT Distance Track' or 'Minimum Fuel Track'
MDT for route portion.
If no 'Airway' or 'Route Code' name or
MFT
type is defined, the default mode is 'MTT'.
Restricted/ Indicates whether restrictions are
Not considered in the OFP calculation.
Restricted
Default option is 'Restricted'.
Non-publ. Indicates whether direct segments which
DCT are not officially published are considered
during flight planning.
ETOPS Indicates whether ETOPS conditions are
considered in the OFP calculation.
Possible options are 'OFF' and 'ON'.
The default option depends on the used
scenario.
ESTZFW Estimated zero fuel weight considered in
the OFP calculation.
MALTOW Maximum allowable takeoff weight
MALLW Maximum allowable landing weight
ADDFU Additional fuel considered in the OFP
calculation.
MAX FL Maximum flight level (hundreds of feet)
DIST Route distance (nautical miles [NM]) of
the selected or calculated OFP.
Opt Button to open window 'Optimization
Param Parameter' in which the defined minimum
cruise times can be altered or deactivated
for the current flight.
Restriction Button to open window 'Restrictions' in
which the user can define restrictions to
be considered.

4: Route Details This area displays details on the route.

The table can be used either in 'Entry Mode' for editing purposes or in
'Display Mode' for review purposes. You can activate the desired mode by
clicking the corresponding toggle (marked with a red rectangle).
Route Details Area Entry Mode
Route Details Area Display Mode

4: Route Details - Continued
Free Flight Check box to define the waypoint as free-flight waypoint

WPT Code Waypoint code (e.g. EDDF), waypoint coordinates (e.g.
570000N0100000W) or waypoint ARINC code (e.g.
5710N)
Symbol Detailed description of the waypoint type, e.g. 'NI' or
'RNAV' for a waypoint of type 'ENROUTE WPT'
Ctry Country code of corresponding waypoint
AWY/RC Airway name (e.g. UB1, W19) or route code name
(e.g. FRATFS1).
Type Detailed description of airway type or route code type
MSA [FT] Minimum safe altitude in feet; available in 'Display Mode'
Vert Unit Vertical unit. The following units are available:
FT: Feet
FF: Flight Level Feet
FM: Flight Level Meter
M: Meter
Flight Level / Flight level value (displayed in the corresponding unit)
FL WPT
Forced Forced flight level calculation for a segment where the
flight level is not defined; available in 'Entry Mode'.
Cruise The following cruise procedures are available:
Procedure
SPEED: Indicated Airspeed and Mach Number
LRC: Long Range Cruise
ECON: ECON Speed Procedure
MEC: Maximum Endurance Cruise
IAS Indicated airspeed. Data entry is possible only for cruise
procedure type 'SPEED'.
MN Mach number. Data entry is possible only for cruise
Cost Index Cost index for cruise procedure 'ECON'.
Wind Dir Wind direction. Data entry in degrees, e.g. 330
Wind Speed Wind velocity. Data entry in knots, e.g. 060
Trip Time Accumulated time to each waypoint; available in 'Display
Mode'

4: Route Details - Continued
Restriction Restriction considered at waypoint and/or following

segment; available in 'Display Mode'
U : Unspecified restriction indicator
N : NOTAM
A : AIP Restriction
S : Slot Restriction
C : Company NOTAM
Field below Waypoint code of destination (e.g. UUDD); available in
column 'WPT 'Entry Mode'
Code'
Remove Row Button to delete the selected row; available in
'Entry Mode'
Remove +++ Button to delete the selected row and all following rows;
available in 'Entry Mode'
Append Row Button to add an empty row after the selected row;
Table End Button to select the last row available; available in
'Entry Mode'
Clear Awy/RC Button to delete all data in columns 'AWY/RC' and 'Type';
Fill Segments Button to insert following data of the OFP calculated or
selected: WPT Code, Symbol, Country, AWY/RC, Type
and Vertical Unit; available in 'Entry Mode'
Weather and Displays detailed restrictions and weather information of
NOTAM per the inserted waypoint; available in 'Display Mode'
Segment
List of Routes Button to open window 'List of Routes' which supports the
user in selecting available route portions.
For more information on this window, see document 'Data
Maintenance User Manual', chapter 'Window List of
Routes'.
Detailed Route Button to open window 'Detailed Route' which displays
further details of the selected route portion, e.g. waypoints
and AWY/RC.
Entry Mode / Check box to select in which mode the table is to be
Display Mode displayed

5: Graphic Tool
The graphic tool provides a graphical display of various kinds of data like
flight routes or aeronautical objects in order to illustrate geographical
correlations of these objects. The user can access this tool within several
contexts and modules of Lido/Flight. For more details about graphic
handling see document 'Graphic Tool Feature Description'.
Graphic Button to open the graphical display window of the

graphic tool (only available if data to be displayed are
loaded in the main window).
As soon as the display window is open, the label of this
button changes to 'Update'.
Update Button to update the graphical display window.
OFF Button to close the graphical display window. If not closed
with this button, the graphic is still open in the
background.
Zoom Button to enable the zoom mode of the display window.
Menu Button to enable the menu in the display window.
With the menu enabled, certain objects can be displayed
additionally. All available options are described in
document 'Graphic Tool Feature Description'.
Map Drop-down list to specify the details to be displayed in
window 'Flight Planning Graphic Window'.
Possible options:
Map (default): Horizontal routing of the OFP including
following objects:
departure and destination airports,
enroute and destination alternates,
waypoints of the routing,
ETOPS circles (if applicable).
Height: Height (FL) for vertical routing (NM) of
the OFP.
Temp: Temperature (C) along the covered
distance (NM).
Fuel: Fuel consumption (kg) along the
covered distance (NM).
Note: For the options 'Height', 'Temp' and 'Fuel' window 'Flight
Planning Graphic Window' opens as soon as the user selects
the option. To open the window in 'Map' mode, the user has to
click on button 'Graphic'.
ALTN Drop-down list to specify the number of alternates to be

displayed on the map.
Possible options: None, 1 (default), 2, 3, or ALL.

6: (Re) Calculation
Buttons
Calculate Initializes the calculation of an operational flight plan

(OFP) based on the selected planning parameter scenario
and data, modes and options defined in this window.
The result of the OFP calculation is available in
window 'Analysis'.
Reclearance Opens window 'Reclearance' in which the user can
perform a reclearance calculation.
Recheck Initializes a check function which compares the inserted
registration and PIC all-weather qualification to the
weather and NOTAM situation at destination and alternate
airports.
The check applies to the JAR-OPS regulations and
considers the calculated time of arrival at destination and
alternate airports.
The check does not modify data inserted or displayed.
The result of the check is displayed in window 'Recheck'
in the 'List of Airports'.
7: ETOPS
Information
ETOPS Output Opens window 'PET/ETOPS Output' which displays the

result of the ETOPS calculation if available.

8: Command
Buttons
SELECT Selects the flight planning scenario from the
database and displays data in corresponding
fields.
INSERT Enabled if an OFP was calculated in window
RTE 'Route Definition' and the window is displayed
in the display mode.
Clicking the button inserts the calculated route
in the database.
PLAN Opens window 'Planning Parameter' and
PARAM transfers the planning parameter scenario
data.
ANALYSIS Opens window 'Analysis' and transfers the
planning parameter scenario data.
OFP TRANS Opens window 'FPL/OFP Transmission' and
transfers the selected OFP (see field 'OFP
No') and the corresponding scenario data into
this window.
COSTS Opens window 'Cost Viewer' which displays a
detailed list of ATC charges of the selected
OFP.
This function is available only in the display
mode.
REMARKS Opens window 'Remarks' displaying dispatch
bulletins and remarks relevant for the flight.
Remarks can be changed and/or added;
dispatch bulletins are for information only.
Note: Dispatch bulletins are maintained within
window 'Dispatch Bulletin'.
A red font color of the button indicates that a

remark is available for this flight.
CLEAR Clears the data currently displayed
HELP Function not established
PRINT Prints the data currently displayed in the
window
CLOSE Closes the window

5.9 Window 'Restrictions'
Purpose and Window 'Restrictions' allows the user to define restrictions before OFP
Structure of calculation and to review restriction settings of already calculated OFPs.
Window Various rules can be activated/ deactivated to consider/not consider
'Restrictions' aspects of flight route calculation.
The following screenshot displays window 'Restrictions' with all available
functions. Your airline may be subscribing to some and not all of the
functions described herein. Some fields may therefore not apply to you.
1: Routing Elements Rules 7: Terrain Clearance Check Rules
2: Terminal Procedure Rules 8: Traffic Flow Restrictions Rules
3: AIP Rules 9: Free Flight Rules
4: Special Time Rules 10: Meteorological Restrictions
5: NOTAM Rules 11: Command Buttons
6: Traffic Right Rules

Menu Button This menu button is available for the tables in window 'Restrictions'. It
offers the following functions:
Insert Before Inserts a new row before the currently selected row (the
Current Row selected row must contain data).
Delete Current Deletes the currently selected row.
Row
Delete All Rows Deletes all rows in the table.
1a: Segment
From/To Start/end waypoint of segment to be excluded from OFP

Waypoint calculation.
Possible formats:
ICAO Waypoint Code (e.g. RUGAS)
Coordinates (e.g. 570000N0100000W)
ARINC code (e.g. 5710N)
1b: Country
Country ICAO country code of country to be excluded from OFP

calculation.

1c: Route
First/Last First/last waypoint of route to be excluded from OFP

Waypoint calculation.
Possible formats:
Awy Airway or route code of route to be excluded from OFP
calculation.
Possible formats:
Airway (e.g. UB1)
Route Code (e.g. FRATFS1)
SID/STAR (e.g. NKR2L)
1d: Airspace
Airspace Name Name of airspace to be excluded from OFP calculation.

Country ICAO country code of corresponding airspace.

1e: Waypoint
Waypoint Waypoint to be excluded from OFP calculation.

Possible formats:
Symbol Detailed specification of waypoint type.
Country ICAO country code of corresponding waypoint.
1f: FIR/UIR
Airspace Name Name of airspace to be excluded from OFP calculation.

Code Airspace code (e.g. LFMM).
Type Airspace type definition (FIR or UIR).
2: Terminal Terminal procedure rules can be

Procedure assigned to certain conditions of an
Rules aircraft. Following toggles allow to
consider ('Yes') or ignore '(No') these
conditions during flight calculation.
TP Altitude Toggle to define consideration of terminal procedure

Restriction altitude restrictions for the micro segment approach.

2: Terminal Procedure Rules - Continued
ICAO Aircraft The shortest terminal procedure available matching the

Type ICAO aircraft type of the used aircraft is applied for route
calculation.
Toggle to define consideration of ICAO aircraft type.
Engine Type The shortest available terminal procedure matching the
engine type of the used aircraft is applied for route
calculation.
Toggle to define consideration of engine type.
Wake The shortest available terminal procedure matching the
Turbulence wake turbulence category (WTC) of the used aircraft is
Category applied for route calculation.
Toggle to define consideration of WTC.
Flight The optimizer checks if the used aircraft is equipped with
Management an FMS and selects terminal procedure F-SID or F-STR.
System
If toggle is set to 'No', there will be no check for matching
FMS equipment and terminal procedures.
TP Flight Toggle to define consideration of flight properties as
Properties maintained for terminal procedure in window 'Terminal
Procedure Flight Properties'.
If considered, the system checks if a matching flight-
properties record exists. If there is none, or the aircraft
fulfills all requirements, the terminal procedure is free to
use. If the aircraft does not meet all requirements, the
terminal procedure is handled as closed.
Note: Toggle is only available for new ICAO flight plans.
AWY/DCT Toggle to define consideration of flight properties as

Flight maintained for airways or directs in window
Properties 'AWY Segment Flight Properties'.
If considered, the system checks for a matching flight
properties record. If there is none, or the aircraft fulfills all
requirements, the segment is free to use. If the aircraft
does not meet all requirements, the segment is handled
as closed.

3: AIP Rules The following toggles allow to

consider ('Yes') or ignore '(No') AIP
rules during flight calculation.
NAT OTS Rules

NOR OTS Rules Toggles to define consideration of corresponding OTS
PAC OTS Rules rules.
AUS OTS Rules
RVSM Rules Toggle to define consideration of RVSM rules.
Domest./Intern. Airway segments can be marked as 'Domestic',
Segments 'International' or 'All'. Segments marked as 'Domestic'
cannot be used for international flights and vice versa.
Flights are considered as domestic flights if departure
airport and destination airport are located in the same
country.
If toggle is set to 'Yes', Lido/Flight differentiates between
segment types 'Domestic' and 'International'.
If toggle is set to 'No', Lido/Flight does not differentiate
between segment types.
Optimization Airway segments can be marked as 'Optimization
Segments Segments', i.e. they can be used during route
optimization (MFT/R, MTT/R, MCT/R or MDT/R).
If toggle is set to 'Yes', only segments marked as
'Optimization Segments' are considered.
If toggle is set to 'No', Lido/Flight does not differentiate
between 'Optimization Segments' and other segments.
NAR Rules Toggle to define if Lido/Flight has to use a routing
complying with the NAR rules.
Airspace Flight Toggle to define consideration of flight properties as
Properties maintained for airspace in window 'Airspace'.
If considered, the system checks for a matching flight
properties record. If there is none, or the aircraft fulfills all
requirements, the area of airspace is free to use. If the
aircraft does not meet all requirements, the area of
airspace is handled as closed.

4: Special Time Routes can be marked as

Rules 'weekday route' and 'weekend
routes'. Routes marked in
such a way can only be used
at defined weekdays and
weekends.
General Rule Drop-down list to select a time rule which applies to all
countries.
Possible options:
Ignore Weekend Rules:
During route optimization weekend rules are not
applied, i.e. both route types 'weekend route' and
'weekday route' are considered.
Use Weekend Rules:
During route optimization weekend rules are applied,
i.e. 'weekend routes' are considered at defined
weekends and 'weekday routes' are considered at
defined weekdays.
Only Non Weekend Routing:
During route optimization only 'weekday routes' are
considered.
Only Weekend Routing:
During route optimization only 'weekend routes' are
considered.
Country Drop-down list to select a rule which applies only to those
specific countries listed in table 'Valid for'.
Valid for Table to specify one or more countries to which the
selected country-specific rule applies.

5: NOTAM Rules
NOTAM Toggle to define if NOTAM restrictions are to be

considered ('Yes') or ignored ('No') during flight
calculation.
Except Table to define exceptions from the general toggle setting
by indicating NOTAM publisher and NOTAM code. The
NOTAM code is composed as follows:
<ClassSeriesNumber/YY>
Example: If NOTAM restrictions are to be considered
(toggle is set to 'Yes'), you can indicate NOTAMs
which are not to be considered during flight
planning.
6: Traffic Right
Rules
Traffic Right Toggle to define if traffic right restrictions are to be

considered ('Yes') or ignored ('No') during flight
calculation.
Except Table to define exceptions from the general toggle setting
by indicating ICAO country code.
Example: If traffic right restrictions are to be considered
(toggle is set to 'Yes'), you can indicate countries
which are not to be considered during flight
planning.

7: Terrain
Clearance
Check Rules
Terrain Toggle to define if the terrain clearance check should be

Clearance done for the main routing during flight calculation.
Check
8: Traffic Flow
Restrictions
Rules
Traffic Flow Toggle to activate or deactivate the consideration of all

Restriction traffic flow restrictions currently available in Lido/Flight
during flight calculation.
ASC Threshold Fields to enter a minimum flight level during ascend and
descend procedures. This threshold defines a tolerance
range within which flights are accepted. The minimum
DSC Threshold range can also be entered in feet or meters by selecting
the corresponding unit from the drop-down list.
<table> Table to define individual restrictions to be excluded
from flight calculation.
Restrictions can be excluded by their ID and/or by their
maintaining/affected airline.
For more information, see document 'Traffic Flow
Restriction (TFR) User Manual'.

9: Free Flight
Rules
except Free Table to enter the names of free flight areas of airspace
Flight Airspace to be excluded from flight calculation.
10: Meteorological
Restrictions
(optional)
VA Volcanic ash clouds as officially published by Volcanic

Ash Advisory centers
C-VA Company defined volcanic ash clouds with
contamination level 'MEDIUM'.
Note: If option 'Disabled' is selected, company defined VAA
are not considered at all independent of the
contamination level.
TC Tropical cyclones as officially published by Tropical

Cyclone Advisory centers
Cold Extremely cold temperatures below configured threshold
value
11: Command
OK Saves restriction settings and closes the window.

DEFAULT Clears all table entries and sets all toggles to default.
PRINT Prints the data currently displayed in the window.
CANCEL Closes the window without saving any settings made.

5.10 Window 'Reclearance'
Purpose and Window 'Reclearance' lets users of Lido/Flight set the parameters for
Structure of performing reclearance calculations.
Window
'Reclearance'
'RECLEARANCE'
'Edit Planning Parameters...' > button 'Analysis' > button 'Inflight'
> button 'Reclearance'
'Edit Planning Parameters...' > button 'RTE DEF' > button
'Reclearance'
1: Flight Information
2: Route of Basic OFP
3: Route from Reclearance Waypoint/Decision Point to RAP
In this area, the layout of the graphical user interface varies dependent
on the used option for the reclearance procedure.
3.1: Menu for MAPS and Graphic Handling
3.2: Menu for Defining a Route and Table Handling
4: Menu and Result of Airport Suitability Check for the RAP
5: OFP Information
6: Command Buttons

Copy Control Panel Upon opening window 'Reclearance' a copy control panel opens showing
parameter of the basic OFP for further optimization.
optimized in reclearance
calculation.
Selected parameter from the basic
OFP is copied as fix value.
Example:
Quit your selection with the button 'OK' to open the 'Reclearance' window.
By default no item is selected, on customer request the setting may be
adapted.
1: Flight
Information
AL IATA airline code of the affected flight.

Flt-No Flight number
OS Operational suffix
Format: alphabetic character.
Date Date of the flight
RWY Runway of the departure airport used for flight plan
calculations.
Default value: Preferential runway, if available;
Field below Flight-plan departure day and time (estimated time
'STD' either entered manually or received via interface).

1: Flight Information - Continued
Field below Flight-plan arrival day and time (estimated time either
'STA' entered manually or received via interface).
RWY Drop-down list to specify the runway of the destination
Default value: preferential runway, if available;
Initialization Time, when the button 'Initialize' was used lastly.
Time
Registration Registration of assigned aircraft
2: Route of Basic The Route of Basic OFP shows all waypoints of the flight-
OFP plan.

3: Route from The waypoint table can be used either in 'Display' mode for review or in
Reclearance 'Entry' mode for editing. You can activate the desired mode by clicking the
Waypoint/ corresponding checkbox (see button marked with a red rectangle).
Decision Point
to RAP The layout of the window varies dependent on the used option for the
reclearance procedure.
The following screenshot shows the possible layout for customers using the
standard reclearance procedure or the decision point procedure.
This screenshot shows the layout for customers using the reduced
contingency fuel procedure.
Additional fields are provided for the following options determining the
contingency fuel:
'Contingency Fuel Percentage + ERA': For insertion of an RAP ERA
'Fix Contingency Fuel Value': For insertion of a fix fuel value

3: Route from Reclearance Waypoint/Decision Point to RAP - Continued
WPT Code ICAO waypoint code or coordinates

Example:
Waypoint code: FFM, RUGAS, TAFFY
Coordinates: 570000N0100000W
or ARINC Code 5710N
Symbol Detailed 'Waypoint Type' specification of the

(Entry mode) corresponding waypoint
AWY/RC Airway or route code type
Example:
Airway: UB1, W19, UA9
Route Code: YVRYYC1, FRATFS1, FRA5315N12
Type Airway or route code type

(Entry mode)
Vert Unit Vertical Unit:
FT Feet FM Flight Level Meter
FF Flight Level Feet M - Meter
Flight Level Value for flight level
MSA [FT] Display of Minimum Safe Altitude [feet].
(Display mode) Display depends on the respective setting of customer.
Possible options are: MSA, MEA (Minimum safe en-route
altitude) or MORA (Minimum off route altitude). For further
information consult the feature description 'Minimum Safe
Altitude'.
(Entry mode) calculation for a segment where the flight level is not
defined
Trip Accumulated time for each waypoint
(Display mode)
MCT, MTT, Optimization mode of route portions, when no 'AWY/RC'
MDT, MFT or /and 'Type' is defined as one of the following:
MCT Minimum Cost Track
MTT Minimum Time Track
MDT Minimum Distance Track
MFT Minimum Fuel Track
Default mode is used as set in Main OFP.

Restricted / Toggle field according to the basic OFP, which defines

Not Restricted whether restrictions will be considered (Restricted) or not
considered (Not Restricted) in the calculation.
Non-publ. DCT Check box for selection, if either published direct
segments only, or additionally non-published direct
segments to be considered during flight planning.
Per default the check box is selected, which means all
available published and non-published directs are
considered.
Note: The separation of direct segments in the aeronautical database
is not yet performed. Therefore it is recommended to have the
check box selected.
ETOPS / Indicator according to the basic OFP, which displays

ETOPS OFF whether the reclearance calculation will consider ETOPS
rules (ETOPS) or not (ETOPS OFF).
<XX> Field for selection/display of runway at the RAP.
RAP Reclearance Airport
RAP-ALTN Reclearance Airport Alternate; field is displayed when the
option 'With ALTN' has been selected.
RCL CONT Contingency fuel policy applied in reclearance calculation
Policy 'RCL DEST'.
RAP CONT Contingency fuel policy applied in reclearance calculation
Policy for the 'RAP' OFP.
RRSV PERC Route Reserve Percentage: The route reserve
percentage can be set with a default value according to
the contingency fuel policy of the airline. The default value
can also be modified in each reclearance procedure and
activated by the toggle.
With ALTN/ Drop-down list for selecting if reclearance calculation is to
No ALTN be performed with/without alternate.
RAP ERA En-route alternate for reclearance airport for the route
from departure decision point reclearance airport. The
field is displayed only when the selected RAP
contingency option requires a manual input of a RAP
ERA.

RAP CONT Drop-down list for display and selection of options for
contingency fuel policy applied in reclearance calculation
using the reduced contingency fuel procedure for the
'RAP' OFP.
Possible options:
Contingency Fuel Percentage
Contingency Fuel Time
Contingency Fuel Percentage + ERA
Automatic Decision for Contingency Fuel Percentage
Contingency Fuel Optimization 1/2
Fix Contingency Fuel Value
FIXCONT Field for inserting a fix value for contingency fuel; field is
displayed only when the RAP contingency option 'Fix
Contingency Fuel Value' has been selected.
3.1: Menu for For the description of MAPS and Graphics handling please see the feature
MAPS and descriptions for 'MAPS' and 'Graphic Tool'.
Graphic
Handling

3.2: Menu for

Defining a
Route and
Table Handling
Altn Info ... Button opens the 'Alternate Info' window, which displays
detailed information about the alternate and the alternate
route.
List Rtes Button opens the 'List of Routes Selection' window with a
list of routes in which the user can select valid route
portions.
Detail Rte Button opens the 'Detailed Route' window, which displays
the waypoints and AWY/RC of the marked route portion.
Remove Row Deletes the marked row.
Remove +++ Deletes the marked row and all following rows.
Append Row Button to add an empty row after the selected row.
Table End Button marks the last row available or inserts an empty
row before the destination if all rows are marked.
Clear Awy/RC Removes all entries in the column Awy/RC.
Entry/Display Toggle for display/selection of the mode of table, which
may be either the 'Entry' or the 'Display' mode.

4: Menu and Result The table 'Airport' shows the result of the Airport Suitability Check, triggered
of Airport by using the buttons 'Initialize' or 'Recheck'.
Suitability Check
for the RAP
ICAO Code ICAO code of the checked airports

Quality Operational case as considered in the Airport Suitability
Check (ASC).
Status The results of the weather and NOTAM check are shown.
Airports are checked according to the appropriate
minimum (take-off, landing, alternate). The checked
RWYs, the considered approach procedure, and the
check period is displayed.
PA Indication of the alternate status as planning or regular
alternate airport
Y Planning Alternate
N Alternate
RCL The 'RCL WX/NOTAM' button opens the
WX/NOTAM 'Weather/NOTAM' window for reviewing airport weather
and NOTAM conditions.
Initialize Button, which starts the Airport Suitability Check of RAP
and if applicable the reclearance airport alternates
according to the respective policy. The result will be
displayed in the 'List of Airports' table.
Recheck Button starts an Airport Suitability Recheck of RAP and if
applicable the reclearance airport alternates according to
the respective policy. The result will be displayed in the
'List of Airports' table.
Initialization Display of the day and time, when the Airport Suitability
Time (RCL) Check or Recheck for a reclearance airport was
performed.

5: OFP Information This part shows the results of the OFP calculation according to the items of
the 'Analysis' window.
ROUTE Field shows the type of optimization considered in

calculation.
Example: MTT (Minimum Time Track).
OFP/RCL Number of the OFP/Reclearance OFP. The reclearance

OFP number includes the basic OFP number and the
reclearance OFP number, e.g. 3/1.
DEST OFP information of the basic OFP from the departure to
the destination airport
RCL DEST OFP information about the recleared OFP from the
departure to the destination airport. In calculation the
partial route from the reclearance point (decision point) to
the destination is calculated anew according to the fuel
policy procedure of the airline.
RAP OFP information about the OFP where the route from the
departure to the reclearance airport via the reclearance
point (decision point) is calculated.

6: Command
Buttons
RECLEARANCE Button starts reclearance calculation according to the

optimization settings made.
AUTO Button starts an automatic reclearance calculation
RECLEARANCE according to the settings made in advance.
The button is available for customers, who subscribed
the optional function 'Automatic Reclearance'.
Alternative RAPs Button opens a list showing alternative reclearance
airports and is available in connection with optional
function 'Automatic Reclearance'. The user may
override the reclearance airport (RAP) selected
automatically by Lido/Flight.
Note: Button is active after automatic reclearance calculation.
RCL Point Reclearance waypoint
GC Dist Great Circle Distance from reclearance waypoint

to RAP [nm]
RAP Reclearance airport
ALTN Great Circle Distance from reclearance waypoint

to RAP alternate [nm]
REMARKS Button opens window 'Remarks' for writing/reviewing
remarks for the 'Dispatch Bulletin'.
CLEAR Clears the current window.
PRINT Sends the content of the current window to the
configured printer.
HELP Functionality not yet established.
OK The 'OK' button closes the 'Reclearance' window and
transfers the data of the calculated reclearance OFP to
window 'Analysis'.

5.11 Window 'Cost Viewer'
Purpose and The window 'Cost Viewer' lets users of Lido/Flight review the costs of a
Structure of the calculated flight.
Window 'Cost
Viewer'
'Edit Planning Parameters...' > button 'ANALYSIS' > button 'COSTS'
1: Flight and Route Information
2.1: Overview of Costs
2.2: ATC Charges Overview per Region
3: Emission Trading Costs

1: Flight and
Route
Information AL Airline Code
Flight-No./OS Flight Number/Operational Suffix
DEP/DEST Departure/Destination Airport
STD/STA Scheduled Time of Departure/Arrival
REG Aircraft Registration
MTOW Maximum Takeoff Weight as planned
OFP Number of calculated OFP
Route Optimization Criterion for the flight
Example: MDT (Minimum Distance Track)
Route Detailed description of the route
2.1: Overview of This area shows an overview of costs.

Costs
The default currency is US$; it can be changed on customer request.
Time Costs Time costs as maintained in the window

'Aircraft Operator Maintenance'
Total ATC Total ATC charges as shown in detail for airspace
Charge

2.2: ATC Charges This table is related to the total ATC charges and shows the ATC charges
Overview per for the selected flight per ATC charges region in detail.
Region
ATC Charges ATC charges region to be flown

Region
If one region is crossed multiply, the ATC charges for this
region are cumulated in the first line; the other lines show
a '0'.
From/To Entry and exit waypoint of the crossed airspace
Charge Type Display of charge type; possible options are:
ERC: En-route charge
TNC: Terminal navigation charge
COM: Communication charge
MET: Meteorology charge
Dev Charge: Development charge
Safety Charge
Local Charge/ Value of ATC charges shown in local currency
Local Currency
USD Charge Value of ATC charges shown in US$
3: Emission In this area the emission trading costs of the flight is displayed.
Trading Costs
Fuel [kg] Calculated fuel consumption of the flight, differentiated for

trip fuel, taxi fuel, and reserve fuel
CO2 [t] Amount of emitted CO2 of the flight
CO2 Costs Costs for the emission of CO2 [US$ or EUR]
[USD]

5.12 Window 'FPL/OFP Transmission'
Purpose and Window 'FPL/OFP Transmission' lets users of Lido/Flight add information
Structure of for preparing a briefing package and transmit information for an individual
Window 'FPL/OFP flight. Prerequisite for using this window is the calculation of a flight.
Transmission'
Path: 'Flight Planning' > 'Planning Parameter' > button 'OFP TRANS'
'Review OFP Transmission...'
'Review Briefing Package...' > button 'OFP TRANS'
'Review Analysis...' > button 'OFP TRANS'
'Review Analysis...' > button 'Rte DEF' > button 'OFP TRANS'
1: Basic Flight Data 8: Transmission Buttons
2: OFP Select Function 9: Additional Information for
Briefing Package
3: History Information of OFP
10: Transmission History
4: Addresses
11: Command Buttons
5: ICAO/FAA Flight Plan
6: Briefing Status
7: Processing Modus (relevant for
the buttons 'File ATS/Send OFP'
and 'Send OFP')


Flt-No. Flight number.
Drop-down list Field showing the runway of the departure airport used for
below 'DEP' flight plan calculations.
Entry field Flight-plan departure day and time (estimated time
below 'STD' either entered manually or received via interface).
Entry field Flight-plan arrival day and time (estimated time either
below 'STA' entered manually or received via interface).
Drop-down list Field showing the runway of the destination airport used
below 'DEST' for flight plan calculations.
Initialization Display field showing the time, when the last Airport
Time Suitability Check has been performed for this planning
parameter scenario.

2: OFP Select This function supports the user in

Function selecting separate OFPs to be filed
or transmitted.
OFP No. Selection criteria entry fields to load a certain OFP into
RCL No. the window.
ETOPS No. Example: OFP No. with RCL No and ETOPS No.: 1/2/1
Load OFP The button 'Load OFP' initializes the selection of the OFP
as described in the entry fields.
3: History
Information
of OFP
REG Entry field for registration of the aircraft used for flight plan
calculations.
Status Display of status of the OFP as tracked in the message
history, possible information is:
Status Description
Filed + Sent ATS flight plan was sent and briefing
package was generated.
Sent Only Briefing package was generated.
Filed Only ATS flight plan was sent.
Cancelled ATS flight plan was cancelled but no briefing
package erased.
Delayed Flight is delayed.
Changed Flight is changed.
Disp. Info Dispatch briefing info was changed.
AR Amend Release (optional).
Withdrawn A removal message is sent to briefing
application informing that previous sent
briefing package is not valid any more.
Status Time Time when an action has been performed.
OFP No. Fields show the number of the loaded OFP.
RCL No.
Example: OFP No. with RCL No. and ETOPS No.: 1/0/1
ETOPS No.

4: Addresses Upon opening window 'FPL/OFP Transmission' Lido/Flight checks if the

departure airport is located within the IFPS region, which is the airspace, in
which flight plan distribution is coordinated by the Integrated Flight Plan
Processing System of Eurocontrol. If yes: the toggle 'ECAC' (European
Civil Aviation Conference) is selected, otherwise not. The number of lines
depends on the status of the toggle 'ECAC'.
If the departure airport is located outside the IFPS region, the dispatcher
may decide to de-activate the 'ECAC' toggle manually.
The color of the background shows if a flight plan has been changed after
sending:
Lavender: Current flight plan has not been changed.
Blue: Flight plan has been changed.
<Line 1> Entry field for AFTN addresses required for the departure
airport.
<Line 2> Entry field for AFTN addresses required for the en-route
part of the OFP.
<Line 3> Entry field for AFTN addresses required for the
destination airport.
<Line 4, left> Entry field for filing time of the ATS flight plan.
<Line 4, right> Entry field for AFTN address of the ATS flight plan
originator.
ECAC Toggle for selecting either the IFPS or standard
(European Civil (non - IFPS) addressing mode.
Aviation
Conference)
<Line 3> Entry only appears if 'ECAC' button is selected.

Additional ATC/ACC addresses will be displayed in order
that ATS plan will be sent to addresses shown.

5: ICAO/FAA Lido/Flight checks the criteria that determine whether a flight calls for an
Flight Plan ICAO (old or new) or an FAA flight plan. The outcome is offered as default
setting. Layout and content conform to the respective flight plan format
requirements.
If multiple flight plans are used:
The following information is displayed directly in the window or on
specific index cards:
Information is displayed for flight plan:
ICAO old ICAO new FAA
Old Directly or on - If configured: On
index card 'ICAO' index card 'FAA'
Flight Plans:
Used ICAO
Both On index card On index card If configured: On

'ICAO old' 'ICAO new' index card 'FAA'
New - Directly or on If configured: On
index card 'ICAO' index card 'FAA'
The ATS flight plan will be sent in the format as defined for the flight
plan of the currently displayed index card. The used index card will be
displayed by default for the next flight.
5.1: ICAO
Flight Plan
Field Description
07 ATS call sign

08 Type of flight and flight rules
09 ICAO type of aircraft
09/X Wake turbulence category of the aircraft
Example: A332/J
10 Radio and transponder equipment of the aircraft
(new: G for GPS-equipped ACFT)
13 ICAO code of departure airport
Proposed departure time
15 ATS route-description

5.1: ICAO Flight Plan - Continued
Field Description
16 ICAO code of destination airport

Estimated elapsed time
ICAO code of alternate airport
ICAO code of alternate airport if 2nd alternate airport was required
18 ICAO field 18
19 ICAO field 19
Supplementary information (optional) may be entered in this field:
Survival equipment information
(e.g. number of life jackets, number of dinghies and any other
information about survival equipment)
Information about endurance
Aircraft color
5.2: FAA Flight

Plan
The part of the ATS flight plan that represents FAA formatted information
contains for example:
ATC call sign Proposed departure time
Aircraft type and navigation Routing and estimated elapsed
equipment time
Initial TAS/Initial flight altitude Remarks
Departure airport
All flight and aircraft information is issued according to FAA format
requirements.

6: Briefing Status Traffic light for showing the briefing

status.
Options are:
Green Briefing package has not yet been retrieved.

Briefing package has been retrieved, but fuel is not yet
Yellow
ordered.
Red Briefing package has been printed or fuel has been ordered.
7: Processing Optional function for selecting the processing modus

Modus for when the buttons 'File ATS/Send OFP' and
Sending the 'Send OFP' are used. Possible options are:
Briefing Package
(File ATS/ YES: Data is transmitted in background.
Send OFP) NO: Data is transmitted in foreground.

8: Transmission The transmission buttons allow the following actions:

Buttons
Filing and sending of OFPs
Note: Filing and sending is limited to the OFPs with the
numbers from 1-99.
Adding information for preparing a briefing

package
Sending flight plan update messages
Transmitting information for an individual flight
File ATS Initializes the release of the ATS flight plan and the
Send OFP generation of the briefing package to the addresses
displayed in the window. Dependent on settings the
button may automatically trigger an Airport Suitability
Recheck.
Send OFP Initializes the generation and sending of the briefing
package. Dependent on settings the button may
automatically trigger an Airport Suitability Recheck.
CNL Opens a transmission window for cancellation of a flight.
Action cancels only the route of the flight, not the flight
itself. If a flight has been cancelled, the dispatcher has to
withdraw the briefing documentation manually.
DLA If departure time has changed, use the button to open a
transmission window to release a delay message.
CHG In case of a change use the button to open a
transmission window to release a modification message.
File ATS Initializes the release of the ATS flight plan. Dependent
on settings the button may automatically trigger an Airport
Suitability Recheck.
Withdraw A remove message is sent to briefing application
Documents informing that previous sent briefing package is not valid
any more. Withdrawing documents means that the action
after using the button 'Send OFP' is cancelled.
Note: Button is only enabled, if a briefing package has been sent.
After withdrawing documents, the buttons 'Dispatch Info' and
'Show Detailed Package' are dimmed.

8: Transmission Buttons - Continued
Dispatch Info Initializes the replacement of the defined dispatch briefing

information within the current briefing package. In the
transmission history table the OFP receives the status
'Disp. Info'.
After withdrawing documents, the button 'Dispatch Info' is
dimmed.
Show Detailed Opens window 'Detailed Package' that displays the

Package generated briefing package information.
After withdrawing documents, the button 'Show Detailed
Package' is dimmed.
Message Opens window 'Message Transmission' to send the ATS

Transmission flight plan.
Transmission Button is available for customers only, who have
via DLK subscribed the Lido/Flight module 'Air/Ground
Communications/Datalink'. For details see documentation
for 'Air/Ground Communications/Datalink'.
Amend Release Button is available for customers only, who have
subscribed the optional function ARTR (Amend Release
To Read). It provides means to amend flight releases as
Amend Release/s (AR) and/or Flight Movement
Forecast/s (FMF). For details see documentation 'ARTR
(Amend Release To Read) Feature Description'.
9: Additional
Information for
Briefing Package
Additional Info Opens the 'BRIEFING additional info' window for the
definition and appending of briefing information.
OFP Remarks Opens window 'Remarks for Briefing OFP' for writing
remarks related to the 'Main OFP'.
Default setting: field size is limited to a maximum of
1000 characters (can be extended upon customer
request).
The customer may decide if the remarks are available
either
Permanently for latest sent OFP, or
As long as the dispatcher is preparing the OFP
transmission.

10: Transmission The table for transmission history tracks actions performed in the window
History referring to the OFP number, a status and the time of action. The
information is tracked from right to the left. Clicking on a column loads the
OFP information as tracked.
If an action failed, the user receives a respective status information in the

status field
OFP/RCL/ Fields show the number of the current OFP.

ETOPS-No
Examples:
OFP number: 1
OFP number with reclearance number: 1/1
OFP number with ETOPS number: 1/0/1
OFP number with RCL number and ETOPS number: 1/2/1
Status Field shows the status of the OFP; following status is

possible:
Status Description
Filed Only ATS flight plan has been filed.
Sent Only Briefing package has been sent.
Filed + Sent ATS flight plan has been filed and briefing
package has been sent.
Filed + SentErr Error in connection with sending.
Disp. Info Additional dispatch information has been

added and sent.
Cancelled Flight has been cancelled.
Delayed Flight delay message has been sent.
Changed Flight plan has been changed and change

message has been sent.
Withdrawn Briefing package has been withdrawn.
Status Time Time of respective action. Format is: <ddhhmm>

11: Command
Buttons
SELECT Selection of the current flight plan.

PLAN PARAM Opens window 'Planning Parameter' and transfers the
Planning Parameter Scenario data.
ANALYSIS Opens window 'Analysis', transfers the planning
parameter scenario data and marks the last generated
OFP.
RTE DEF Opens window 'Route Definition' and transfers the data of
the last generated OFP and the Planning Parameter
Scenario data.
WX/NOTAM Opens window 'Weather/NOTAM' showing airport
weather and NOTAM conditions.
REMARK ... Opens the dispatch remark window.
CLEAR Clears the data in 'Flight Information'.
PRINT Prints the content of the window.
HELP Function not implemented.
CLOSE Closes the window.

5.12.1 Window 'Briefing additional Info'
Purpose and Window 'Briefing additional info' allows appending additional information for
Structure of briefing purposes to the briefing package as follows:
Window 'BRIEFING
additional Info' OFPs for summary and information purposes
Optional: Overflight permissions of the ATS flight plan
Optional: Waypoint information
Optional: Mini OFPs
Optional: Weather and NOTAM information for up to 6 airports.
Remarks, related to separate OFPs and the additional information.
Path: 'Analysis' > 'FPL/OFP Transmission' > button 'Additional Info'
1: Flight Information 5: Remark
2: Additional Information 6: Optional: Supplemental Weather
and NOTAM Information
3: Briefing Status
7: Command Buttons
4: OFP Information

1: Flight
Information

Flt-No. Flight number.
Entry field Flight-plan departure day and time (estimated time
below 'STD' either entered manually or received via interface). If no
ETD is published, the STD is displayed.
Entry field Flight-plan arrival day and time (estimated time either
below 'STA' entered manually or received via interface). If no ETA is
published, the STA is displayed.
Initialization Time, when the last Airport Suitability Check has been
Time performed for this planning parameter scenario.

2: Additional In this area by

Information enabling/disabling a toggle
the following information may
be added to the briefing
package:
RWC Runway Weight Charts information.

TAIL TANK Information about tail tank; information content may
be defined by customer.
OVERFLIGHT Country and permission code of overflight
PERMISSIONS permissions.
Note: This addition requires the following prerequisites:
In window 'Traffic Rights' the toggle 'Output' is
selected to 'YES'.
The OFP layout has to be adapted accordingly.
WAYPOINT INFO Waypoint information of all waypoints of the route

from departure airport to destination airport (for
example latitude, longitude, flight level).
MINI OFP Mini flight plans.
Possible values are:
'Yes' Mini-OFPs are added to the briefing
(default) package.
'No' Mini-OFPs are not added to the briefing
package.
The toggle is only enabled, if a Mini-OFP has been
calculated for that flight. Otherwise it is dimmed.
3: Briefing Status Traffic light for showing the briefing status.

Options are:
Green Briefing package has not yet been retrieved.

Yellow Briefing package has been retrieved, but fuel is not yet
ordered.
Red Briefing package has been retrieved. Fuel order is
completed.
The above signs are valid in connection with any briefing application
supporting the needed information.

4: OFP Information
TRACKS Drop-Down list for selecting tracks of the Organized Track

System (OTS). Adopted display field shows the time of
validity.
For details see documentation 'Organized Track Handling
OFP NO Fields show the number of the current OFP.
RCL NO Examples:
ETOPS NO OFP number: 1
OFP number with reclearance number: 1/1
OFP number with ETOPS number: 1/0/1
OFP No. with RCL No. and ETOPS No.: 1/2/1
REMARK Field for inserting a remark to the selected OFP.

ROUTE Optimization criterion as selected for the OFP.
Order No Order number according to the selection sequence for the
option. Counting is separate for summary OFPs and
information OFPs. User may alter the numbering.
OPTION Option of the OFP Information as to be appended to the
briefing package. Possible options are:
MAIN OFP as selected from the
'FPL/ OFP Transmission' window
SUMMARY A short OFP is appended.
INFO A complete OFP is appended for information.
COSTS - TOW Calculation results from window 'Analysis'.

5: Remark
Entry field for writing a remark related to the additional briefing information
package. If the user has entered remarks in window 'FPL/OFP
Transmission', the font of the button 'REMARK' turns to red.
Note: This remark will appear only within the BRIEFING additional info environment.
6: Optional: With the feature 'Supplemental Weather and

Supplemental NOTAM Information' the user has the
Weather and possibility to add weather and NOTAM
NOTAM information for additional en-route airports to
Information the weather package, which is part of the
briefing package.
Note: These additional en-route airports are not
considered during the airport suitability
check.
NO Number of additional airport.

ICAO Code Entry field for ICAO codes of airports for supplemental
weather and NOTAM information.
If required, use
the menu
button on top of
the scroll bar to
delete one or
more rows.

7: Command
Buttons
Set to Clears all entries and selections made manually by the

DEFAULT user.
Show detailed Opens the 'Detailed Package' window that displays the
Package generated briefing package information.
APPEND Appends the additional information to the briefing
package and closes the window.
CANCEL Closes window 'BRIEFING additional info' and returns to
window 'FPL/OFP - Transmission'.
PRINT Sends the content of the current window to the configured
printer.

5.12.2 Window 'Detailed Package'
Purpose and This window shows the detailed briefing package for a flight, for which an
Structure of OFP has been calculated, and allows reviewing, transmitting and printing
Window the displayed information. The briefing package consists of the following
'Detailed Package' parts: OFP, ATS flight plan, NOTAM identification of all NOTAMS relevant
for the current briefing package, and additional information, if defined by
dispatcher.
Note: Actual weather information is not part of this information package.
The window can be accessed from different windows as shown in the

overview. The display of command buttons differs dependent of the access.
The review of the detailed briefing package is shown exemplary for the
access via window 'Flight List'.
Window Access by
Sending of an OFP by 'File ATS/Send OFP', or
'FPL/OFP 'Send OFP': the window opens automatically.
Transmission'
Button 'Show Detailed Package'
Button 'BRF PKG' for flights, which have already been
'Flight List'
calculated.
'Briefing
Button 'Show detailed Package'
additional Info'

Command Buttons The display of buttons depends on the used

functions and the stage of flight planning process.
The buttons 'File', 'File and Send', and 'Send' are
visible for customers only, which use the Three-
Click-Version of the Airline Operations Support
(AOS) module of Lido/Flight.
The buttons 'PLAN PARAM', 'ANALYSIS',
'OFP TRANS', 'A/C DEV', and 'REMARK' are
visible if the window is opened via window 'Flight
List' directly.
File Initializes the release of the ATS flight plan.

File and Send Initializes the release of the ATS flight plan and the
generation of the briefing package.
Send Initializes the generation of the briefing package.
PLAN PARAM Opens window 'Planning Parameter' and transfers the
planning parameter scenario data.
ANALYSIS Opens window 'Analysis', transfers the planning
parameter scenario data and marks the last generated
OFP.
OFP TRANS Opens window 'FPL/OFP Transmission' and transfers
the data of the last generated OFP and the Planning
Parameter Scenario data.
A/C DEV Opens window 'List of Aircraft Deviations'.
REMARK Opens the dispatch remark window. If a remark is
available, the font is shown in red.

Command Buttons - Continued
Message Button opens window 'Transmission Options' showing
Transmission basic flight information and allows selecting/deselecting
the parts to be transmitted.
OFP Main OFP

ATC ATC flight plan
INFO All information, which were added via
window 'Briefing Additional Info'
WX Weather information
ABD Optional function for appending 'Additional
Briefing Data'
NOTAM Flight related NOTAM package
SAT IMAGES Optional function for attaching satellite
SAT WX images and weather charts. This function is
CHARTS available for the transmission medium
'Email' only.
ATTACH Opens a window for browsing for image
and chart files to be attached.
SELECT Selects missing flight data.
CLEAR Clears the content of the window and
inserts the current date.
TRANSMIT Closes window 'Transmission Options'.
Window 'Message Transmission' opens
showing the transmitted content of the
briefing documentation.
PRINT Button opens window 'Print Options' showing basic flight
information and allows selecting/deselecting the parts of
briefing package. Lido/Flight offers different print options.

5.13 Window 'Inflight Assistance'
Purpose and Window 'Inflight Assistance' provides the function to calculate an OFP
Structure of (Operational Flight Plan) from a selectable inflight waypoint to the planned
Window or a new destination airport.
'Inflight Assistance'
'Edit Planning Parameters...' > button 'ANALYSIS' > button 'Inflight'
2: Routing of Basic OFP
3: Route from selected inflight waypoint to Destination Airport
In this area, the layout of the graphical user interface varies depending
on the used mode for the inflight calculation (display or entry mode).
3.1: Waypoint Table of the Route from Inflight Waypoint to Destination
Airport
3.2 Menu for MAPS and Graphic Handling
3.3: Menu for Defining a Route and Table Handling
4: Menu and Result of Airport Suitability Check for the new Routing.
5: Inflight Fuel Components
6: OFP Information for Inflight Calculation
7: Command Buttons

AL Airline code (IATA)

Flt-No Flight number
OS Operational suffix; an alphabetical character which follows
the flight number. The meaning and use of the character
is defined by the customer.
Date Date of flight
Initialization Time when the last airport suitability check has been
Time performed for this planning parameter scenario, triggered
by clicking on button 'Initialize' in window 'Planning
Parameter'.
DEP ICAO code of departure airport
Field below Drop-down list displaying the runway of the departure
'DEP' airport used for flight plan calculations.
Field below Flight-plan departure day and time (estimated time of

'STD' departure [ETD] either entered manually or received via
interface).
Field below Entry field for flight-plan arrival day and time (estimated
'STA' time of arrival [ETA] either entered manually or received
via interface).
DEST ICAO code of destination airport
Field below Drop-down list displaying the runway of the destination
'DEST' airport used for flight plan calculations.
Registration Registration of aircraft which is used for flight plan
calculations.

2: Routing of Basic The Routing of Basic OFP shows all waypoints of the
OFP calculated flight plan.
3: Route from In this area the user may set the calculation parameters for the inflight
Inflight Waypoint calculation. By default the settings used in the calculation of the basic OFP
to Destination are shown, which can be changed for the inflight calculation.
Airport
Operational Drop-down list to select an operational case for which

Case the calculation shall be performed. Possible values:
Standard ST
One engine out 1X
Gear down GD
Spare engine SE
Show TP Toggle to enable/disable the display of all waypoints of a
waypoints selected route, which are located on micro segments of
the used terminal procedures.
The toggle is connected to the optional function
'Precision Path Procedure' for terminal procedures. The
display of toggle is optional.

3: Route from Inflight Waypoint to Destination Airport - Continued
Fixed MN Drop-down list to determine the speed within fixed

Airspace/Airway MACH airspace / airways.
Possible values are:
Option Description
Optimum MN Average of speed at entry and exit point
of fixed MACH airspace.
Fixed MN Disables consideration of fixed MACH
OFF airspace.
MCT, MTT, Toggle field to define optimization mode of route
MDT, MFT portions if no 'AWY/RC' or /and 'Type' is defined as one
of the following:
MCT Minimum Cost Track
MTT Minimum Time Track
MDT Minimum Distance Track
MFT Minimum Fuel Track
Restricted Toggle field to define whether restrictions will be
considered (toggle activated) or not considered (toggle
inactivated) in flight plan calculation.
Non-publ. DCT Check box to select if either published direct segments
only or also non-published direct segments are to be
considered in flight planning.
Note: The separation of direct segments in the aeronautical
database is not yet performed. Therefore it is recommended to
have the check box selected.
No ETOPS / Toggle field to define whether ETOPS rules are

ETOPS considered in OFP calculation (selection: 'ETOPS') or
not ('No ETOPS').
GW Field to enter the gross weight (GW) at a certain inflight
waypoint.
Time Current time
Load Weight of payload.
DOW Dry Operating Weight.
ZFW Planned Zero Fuel Weight (sum of 'DOW' and 'Load').
Rem Fuel Entry field for remaining fuel (to be entered manually).
Weight Quality Indicates origin of weight data

3.1: Waypoint Table The waypoint table can be used either in 'Display' mode for review or in
of the Route 'Entry' mode for editing. The layout of the table varies according to the used
from Inflight mode. You can activate the desired mode by clicking the corresponding
Waypoint to checkbox (see button marked with a red rectangle).
Destination
Airport Entry Mode:
Display Mode:
Free Flight Column is used for Free Flight calculations (optional

feature, to be configured by Lufthansa Systems on
customer request). It is possible to define an existing
waypoint as free flight waypoint or create a new free flight
waypoint. For more details about Free Flight, see
document 'Free Flight Feature Description'.
Possible options depending on active mode:
Entry Mode Toggle 'Set'
Display Toggle 'View'
WPT Code ICAO waypoint code or coordinates
Example:
Waypoint code: FFM, RUGAS, TAFFY
Coordinates: 570000N0100000W
or ARINC Code 5710N
Symbol Detailed 'Waypoint Type' specification of the

(Entry mode) corresponding waypoint

3.1: Waypoint Table - Continued
AWY/RC Airway or route code type

Example:
Airway: UB1, W19, UA9
Route Code: YVRYYC1, FRATFS1, FRA5315N12
Type Airway or route code type

(Entry mode)
Vert Unit Vertical unit. The following units are available:
FT: Feet
FF: Flight Level Feet
FM: Flight Level Meter
M: Meter
Flight Level Value for flight level

(Entry mode) calculation for a segment where the flight level is not
defined.
MSA [FT] Display of Minimum Safe Altitude [feet].
(Display mode) Display depends on the respective setting of customer.
Possible options are: MSA, MEA (Minimum safe en-route
altitude) or MORA (Minimum off route altitude). For further
information see the feature description 'Minimum Safe
Altitude'.
Cruise The column 'Cruise Procedure' allows the specification of
Procedure the cruise procedure type.
Possible values:
Option Description
Speed Triggers drop-down lists 'MN' and 'IAS',
where the user can select appropriate
mach number and indicated airspeed;
default values are maintained in the
windows 'Aircraft Operator Maintenance'
and optionally 'Leg Policy'.
LRC Long Range Cruise
ECON Economic cruise procedure; triggers the
entry field 'Cost Index', where the user
can enter an appropriate cost index;
default values are maintained in the
windows 'Aircraft Operator Maintenance'
and optionally 'Leg Policy'.
MEC Maximum Endurance Cruise

3.1: Waypoint Table - Continued
IAS Indicated Airspeed Applicable for cruise

procedure 'SPEED' only.
MN Mach Number
Cost Index Cost index for cruise procedure 'ECON'. A value between
0 and 100 is possible.
Trip Time Accumulated time to each waypoint.
(Display Mode)
IAS Indicated airspeed. Data entry is possible only for cruise
MN Mach number. Data entry is possible only for cruise
<XX> Field for selection/display of runway at the destination
airport. If the airport has been inserted manually, the
preferential runway is displayed; if the airport has been
inserted automatically, the runway of the basic OFP is set.
DEST Inflight destination airport
ALTN Alternate airport
<drop-down Menu for alternate sequence options, which may be
menu> 'With ALTN' (using the default policy),
(optional) 'Isolated AD Operation', or 'No ALTN Requ.'
3.2: Menu for For the description of MAPS and Graphics handlings please see the feature
MAPS and descriptions for 'MAPS' and 'Graphic Tool'.
Graphic
Handling

3.3: Menu for

Defining a
Route and
Table Handling
Altn Info ... Button opens window 'Alternate Information', which

displays detailed information about the alternate and the
alternate route.
List Rtes Button opens window 'List of Routes Selection' with a list
of routes in which the user can select valid route portions.
Detail Rte Button opens window 'Detailed Route', which displays the
waypoints and AWY/RC of the marked route portion.
Remove Row Deletes the marked row.
Remove +++ Deletes the marked row and all following rows.
Append Row Inserts an empty row after the marked row.
Table End The 'TABLE END' button marks the last row available or
inserts an empty row before the destination if all rows are
marked.
Clear Awy/RC Removes all entries in the column Awy/RC (Airway name,
e.g. UB1, W19, or Route Code name (e.g. FRATFS1).
Entry/Display Toggle for display/selection of the mode of table, which
may be either the 'Entry' or the 'Display' mode.

4: Menu and Result The table 'List of Airports' shows the result of the Airport Suitability Check,
of Airport triggered by using the buttons 'Initialize' or 'Recheck'.
Suitability Check
for the
New Routing
ICAO Code Displays ICAO code of the checked airports.

Quality Displays type of operation the airport is used for and
checked. In case of inflight calculation the quality can be
for example:
INF_DEST (Inflight Destination)
INF_ALTN (Inflight Alternate)
Status Displays results of the airport suitability check.
The results include the check period and details such as
suitability designator of checked runway, approach
procedure considered and others.
For details see document 'Airport Suitability Check
Feature Description' for the respective policy.
PA Indicator if an alternate is used as planning alternate:
Y = Yes
N = No
Initialization Display of day and time when the Airport Suitability Check
Time or Recheck for inflight airports was performed.
Initialize Button that starts the Airport Suitability Check of
destination airport and airport alternates according to the
respective policy. The result will be displayed in the 'List
of Airports' table.
Recheck Button that starts the Airport Suitability Recheck of the
destination airport and the airport alternates according to
the respective policy. The result will be displayed in the
'List of Airports' table.
WX/NOTAM The 'WX/NOTAM' button opens the 'Weather/NOTAM'
window for reviewing airport weather and NOTAM
conditions.

5: Inflight Fuel Toggles for including/excluding the

Components consideration of fuel components in
an inflight calculation.
CONT Contingency fuel

HOLDING Holding fuel
ALTN Alternate fuel
Note: If option 'Excluding ALTN' is selected, the option 'Excluding
HOLDING' will be activated automatically.
RESERVE Reserve fuel (FAA)

MIN RES Minimum reserve fuel (FAA)
Note: Activation of this toggle requires the toggle 'Including
RESERVE' to be activated to consider reserve fuel.
6: OFP Information This area shows the results of the

for Inflight inflight OFP calculation according to
Calculation the parameters set in window
'Inflight Assistance'. The results are
shown analogous to the results in
window 'Analysis', important results
or negative results are marked in
red.
ROUTE Route type of the calculated inflight route is INFLT.

INF-OFP Number of OFP for the inflight calculation

6: OFP Information for Inflight Calculation - Continued
() Results according to window 'Analysis'

D FUEL Delta Fuel [kg or pounds], which is the difference between
remaining fuel (REM Fuel) and the fuel planned for the
inflight calculation (PLNFUEL).
Note: In the above example the Delta Fuel is marked in red, as the
remaining fuel is less than the planned fuel needed for the
inflight OFP.
7: Command
Buttons
ETOPS Param Opens window 'PET/ETOPS Parameter' with index

card 'ETOPS' open.
ETOPS Output Opens window 'PET/ETOPS Output' which displays the
result of the ETOPS calculation if available.
Reclearance Opens window 'Reclearance' for performing a
reclearance calculation
Note: Button is accessible only in case the calculated inflight fuel
exceeds the value of the remaining fuel.
INFLIGHT Starts the inflight calculation according to the displayed

parameters.
REMARK Button opens window 'Remarks' for writing/reviewing
remarks for the 'Dispatch Bulletin'.
CLEAR Clears the current window.
PRINT Sends the content of the current window to the
configured printer.
HELP Functionality not yet established.
OK Closes the 'Inflight Assistance' window and transfers
the data of the calculated inflight OFP to window
'Analysis'.

User Ifpl Basic Opt 570 v1 0

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

User Ifpl Basic Opt 570 v1 0

Transféré par

Droits d'auteur :

Formats disponibles

Lido/Flight

Copyright 2012 by Lufthansa Systems AG

Our documentation team may be contacted at:

The Lido Helpdesk may be contacted at:

February 10, 2012 Page 2 of 218

February 10, 2012 Page 3 of 218

2 Basic Procedures of Interactive Flight Planning ................................................................... 9

2.3.2 Triggering Alternate Selection and Airport Suitability Check ..................... 17

2.4 Calculating a Flight ......................................................................................................... 19

2.4.3 Defining Route Details............................................................................... 28

2.4.4 Reviewing and Modifying Route Details .................................................... 32

2.4.7 Considering Natural Hazards (optional) .................................................... 37

2.6 Calculating a Reclearance Flight.................................................................................... 46

2.6.2 Calculating a Flight Using the Standard Reclearance Procedure or the

2.6.4 Optional: Performing an Automatic Reclearance Calculation.................... 53

2.6.5 Reviewing Results of Reclearance Calculation ......................................... 55

February 10, 2012 Page 4 of 218

2.7 Flight Planning over AIRAC Change Dates.................................................................... 56

2.7.3 Recalculating a Flight Using a Via Waypoint Valid at 00:00 UTC.............. 61

3 Performing FPL/OFP Transmission ...................................................................................... 62

3.1 Workflow and Overview of Procedures .......................................................................... 62

4 Performing an Inflight Calculation ........................................................................................ 77

4.1 Calculation Parameters .................................................................................................. 77

5 Field and Button Description................................................................................................. 81

February 10, 2012 Page 5 of 218

5.7 Window 'Route Options' ............................................................................................... 133

5.7.2.1 AUSOTS Tracks ................................................................ 137

5.7.2.2 NAT and NOR Tracks (OTS) ............................................. 138

5.7.2.4 Polar Tracks (POL)/Arctic Tracks ...................................... 140

5.7.2.5 ATC Reroute Proposal (ATC RRP) ................................... 142

5.7.2.6 PACOTS Tracks ................................................................ 143

5.7.3 Area 'Optimization Criteria' ...................................................................... 152

5.8 Window 'Route Definition'............................................................................................. 153

5.13 Window 'Inflight Assistance' ......................................................................................... 208

February 10, 2012 Page 6 of 218

Review OFP calculation results

February 10, 2012 Page 7 of 218

Structure of This document consists of two main parts:

February 10, 2012 Page 8 of 218

2 Basic Procedures of Interactive Flight Planning

1. Select a flight record from the flight list.

2.2 Selecting Flight Records

February 10, 2012 Page 9 of 218

2.2.1 Selecting a Flight Record

Selecting a 1. Open window 'Flight List'.

The layout of the window may differ according to your settings.

2. Optionally, adjust any of the filters in area 'Filter Definition' to specify

Continued on next page

February 10, 2012 Page 10 of 218

Selecting a Flight Record - Continued

February 10, 2012 Page 11 of 218

2.2.2 Searching for Flights in the Flight List

You may use any of the following search criteria:

2. Click on button 'Search'

3. Navigate through your search results.

Flights have been searched for in the flight list.

February 10, 2012 Page 12 of 218

2.3 Setting up a Planning Parameter Scenario

2.3.1 Setting up a Planning Parameter Scenario

Before You Start Before you start, verify that:

Setting up a 1. Open window 'Planning Parameter':

When accessing window 'Planning Parameter' from window 'Flight List',

Continued on next page

February 10, 2012 Page 13 of 218