Training Guide

Updating Flight Progress, Forecast, &

Cancellation
Native Sabre
Software Version 2.0

Document Edition 1.2 (10 2015)

This documentation is the confidential and proprietary intellectual

property of the Sabre Airline Solutions business. Any
unauthorized use, reproduction, preparation of derivative works,
performance or display of this document or software represented
by this document, without the express written permission of Sabre
Airline Solutions is strictly prohibited.

Sabre , the Sabre logo, Sabre Airline Solutions, the Sabre Airline
Solutions logo, Sabre Travel Network , the Sabre Travel Network
logo, AirCentre , AirVision , SabreSonic CSS are trademarks
and/or service marks of an affiliate of Sabre Inc. All other
trademarks, service marks and trade names are the property of
their respective owners.

2015 Sabre Inc. All rights reserved.

Table of Contents

1 Flight Information Overview

1.1 Reading a Flight's Scheduled Operations 1
1.1.1 Performing a Flifo Review 1
1.1.2 Additional Flifo Example 1
1.2 Reading a Flight's Updates 2
1.3 Listing Important Terms and Definitions 3

2 Flight Updates
2.1 Updating Flight Progress 5
2.1.1 Applying Notification Codes 6
2.2 Applying Cancellation or Decisions to Cancel 7
2.3 Updating Flight Progress 8
2.3.1 Additional Application Notes 9
2.4 Deleting a Flight Progress 9
2.5 Concerning Flight Dispatch 9
2.5.1 Inputting a Flight No-Op / Cancellation 10
2.5.2 Updating a Landing Cancellation 11
2.5.3 Updating a Departure Cancellation 12
2.6 Updating a Flight Forecast 13
2.7 Viewing Flight Information History 13

3 Quick Reference of Entries

3.1 Notification Codes 15
3.2 Dispatch Entries 15
3.3 Flifo Acronyms / Codes 15

Table of Contents
Training Guide iii Confidential and Proprietary Sabre Airline Solutions
Document Revisions

Date Section Description

20 Oct 2015 Flight Information Overview Expanded section

20 Oct 2015 Flight Updates Added data concerning Notification Code 9

15 Apr 2015 Throughout Documentation brought to latest template

Table of Contents
Training Guide iv Confidential and Proprietary Sabre Airline Solutions
Objectives

Item Objective
Objectives By the end of the module, participants will be able to:
l Demonstrate the ability to input flight progress
l Demonstrate the formats to modify / delete flight progress
l Discuss the rationale for inputting a leg / flight / departure cancellation
l Demonstrate the format to input flight forecast
l Explain the flight information history response
EPR Duty Code: 5, 7, or 8

Keyword: No specific EPRkeyword required

UAT Keyword: DSPTCH (for Flight Dispatch entries)

Preparation To prepare for teaching this module:

l You must select and assign specific host flights so each student can apply flight progress entries.
l Students must first complete the Flight Information module
Reference For more information, refer to Focus

Table of Contents
Training Guide v Confidential and Proprietary Sabre Airline Solutions
 Table of Contents
Training Guide vi Confidential and Proprietary Sabre Airline Solutions
Flight Information Overview

Flight Information, also called Flifo, is information regarding a flights departure and arrival times and other
pertinent information such as the gate and terminal. The Flifo response is composed of two sections: the
flight's normal scheduled operation times, and updates on what the flight actually does.

1.1 Reading a Flight's Scheduled Operations

The normal schedule for a given flight includes:

l Scheduled departure and arrival times
l Terminal and/or gate information (if available via your airline's SSCI Terminal Table)
l Baggage claim area information

1.1.1 Performing a Flifo Review

Prior to updating a flight progress, you should access Flifo to view that flights normal operating schedule.
Use this format to view a Flifo for a flight. Example entry:
231

Item Description
2 Primary Fllifo action code

31 Example flight number

Example system response:

U00031/12APR
SGN 1255P C01
BKK 233P

Item Description
U00031/12APR Airline code, flight number, date

SGN 1255P C01 Departure city, scheduled departure time, departure gate

BKK 233P Arrival city in line of flight, scheduled arrival time

Note If you do not specify a date in your entry, the system will default to the current date. You may request
to view Flifo for yesterday, today, or any date in the future. To specify a date, append the initial entry
with /<date>.

1.1.2 Additional Flifo Example

Entry Description
231/19APR Flifo request for a future date

1 Flight Information Overview

Training Guide 1 Confidential and Proprietary Sabre Airline Solutions
Notes

l When you request Flifo for a flight that has not yet departed or for a flight on a future date, usually, only the
flight's scheduled operational information displays.
l If the gate, terminal, and baggage claim information is available, the gate information is located in the
response closest to the arrival / departure times, the baggage claim area information is located before the
gate information and arrival time.
l If the flight forecast contains a date change, an Cross-of-Lorraine () appears next to the city where the
date change occurs.

1.2 Reading a Flight's Updates

The Flight's updates contains information on the flight as it occurs, which includes:
l Actual departure time
l Actual arrival time
l Estimated time of arrival
l Out of the gate and off times
When you request FLIFO for a flight that has departed, the system displays both the flight forecast and the
flight progress details. All the times in the flight progress are actual or estimated times.
A flight progress response is similar to the following:

U09531/15OCT
YVR 835A S11
HNL 31 1155A
3YVR/ETD 1000 15OCT - LINE MTC *1149*HDQH2Z
4YVR/OUT 1012 15OCT OFF 1024 15OCT *1224*HDQH2Z
2HNL/ETA 1323 15OCT *1224*HDQH2Z

Note The flight forecast is at the top part of the response. The flight progress is the data located at the
bottom. Each line of the flight progress starts with a number code (explained below).
Examine the first line of the flight update response:

3YVR/ETD 1000 15OCT - LINE MTC *1149*HDQH2Z

Item Description
3 This is a notification code used in flight progress entries. (The codes are their uses are explained in the
next section of this Training Guide.)

YVR The city impacted by the update

ETD Shorthand code for Estimated Time of Departure

1000 The local estimated time of departure, and the date

15OCT

LINE This area is free text remarks - the reason for this delay is "line maintenance."
MTC

1 Flight Information Overview

Training Guide 2 Confidential and Proprietary Sabre Airline Solutions
 Item Description
1149 The time the flight progress was updated (in Sabre Central time)

HDQH2Z The home station and sine of the person who updated the Flifo

Any diversion cities would display in the flight updates area.

1.3 Listing Important Terms and Definitions

In the flight update data, there is a standard set of flight information codes. The following are a few terms and
definitions used when working with Flight Information and Progress:
Item Description
PRE Preliminary estimated arrival time

ETA Estimated time of arrival

ETD Estimated time of departure

DCSN Decision

OUT Gate departure time the time an aircraft pushes out of a gate

OFF Take off time the time an aircraft has wheels off the ground

ON Landing time the time the aircraft touches onto the ground at landing

IN Gate arrival the time an aircraft pulls into a gate

LX Landing cancel / Leg cancel

DX Departure cancel

FX Flight cancel

ATC Air Traffic Control

OP Operations

Note For a listing of additional codes, see the Appendix to this Training Guide, or refer to the Focus
reference manual F*FMH.

1 Flight Information Overview

Training Guide 3 Confidential and Proprietary Sabre Airline Solutions
 1 Flight Information Overview
Training Guide 4 Confidential and Proprietary Sabre Airline Solutions
Flight Updates

Entering Flight updates into the system means adding accurate and complete flight information, thus providing
a high level of customer service. This is done either automatically immediately upon a flights arrival to or a
flight departure from a specific airport, or you may update flight information manually.
Flight information is divided into three main categories:

Action
Item code Description
Flight Forecast 2F Advises of irregular flight information such as delays, equipment changes, etc.

Flight 2P Advises of actual flight times such as preliminary arrival time (PRE), estimated time of
Progress arrival (ETA), actual time of arrival (IN), etc.

Flight or 2N Makes either a flight, or one or more airports pertaining to a flight not operational
Airport NOOP

2.1 Updating Flight Progress

Use this format to enter the actual operating time / delay / reason into the stored flight information record for a
specific flight. The free text field allows a maximum of 225 characters.
Note Flight Progress entries will update flights in the SabreSonic Check-in database.
Example entry:
2P127/ORIG23AUG4DUS/OUT 913A OFF 920A ATC

Item Description
2P Action code for Flight Progress

127 Example flight number

/ORIG23AUG Slash separator, indicator for Origin point, and date of origination

4 Notification code

DUS End Item character (as a separator) and board point

/OUT 913A OFF 920A Mandatory / slash separator andFlight Progress information (free text, up to 225
ATC characters)

Example response:

DONE. 1234P/23AUG

Note The time and date indicated in the response is in Sabre time (U.S. Central time).
Example of the Flifo entry and response after a Flight Progress update:
2127/23AUG

2 Flight Updates
Training Guide 5 Confidential and Proprietary Sabre Airline Solutions
 U00127/23AUG
DUS 910A
CDG1003A1058A
4DUS/OUT 913A OFF 920A ATC*1234*HDQHLF

The last line of the flight information shows the flight progress you have added:

Item Description

4DUS/ Notification code and city code

OUT 913A OFF 920A ATC Flight Progress (free text)

*1234* Time the flight progress was entered (in Sabre Central time)

HDQHLF Updater's EPR home city and sign

2.1.1 Applying Notification Codes

The notification code that you use in the entry should correspond with the type of flight progress you are
updating. For example, you use the notification code 4 when the flight progress being input is for OUT / OFF
flight information. When you make a Flight Progress entry to update Flifo, the system sends notification
messages to advise that Flifo exists on the flight. The routing of the notification messages is controlled by the
notification code used in the 2P entry.
Notes

l You may include only one notification code in a single Flifo message entry.
l You can also have the message print at two other points (such as at your Operations Centre and/or a
Reservations / Call Centre), as determined your settings on your Flifo routing table.
The notification codes and their definitions follow:
Notification
Code Description
1 Use for cancellations or flight diversions

2 Use for PRE, ETA, IN

3 Use for DCSN, ETD

4 Use for OUT, OFF

5 Use for flight forecast, STUB information

6 Use for departure cancellation

9 Use for aircraft and tail number information

Note By default, code 9 updates appear in Flifo responses only to those using a duty code (the
Programmer's duty code). If your airline wants to have code 9 updates visible to other users,
Sabre must configure this setting for you. If your airline is interested in this option, contact
Global Customer Care.
The routing of the notification messages is as follows:

2 Flight Updates
Training Guide 6 Confidential and Proprietary Sabre Airline Solutions
 Notification
Code Description
1 All airports in the line of flight will receive the Flifo message

2 Only the airport identified in the entry will receive the Flifo message

3 The Input airport and all upline airports will receive the Flifo message

4 The Input airport and all downline airports receive the Flifo message

5 Input airport and all airports in between in-line of flight will receive the message

6 Message may be sent to a queue, to a printer, or nowhere (as determined by settings decided on
by your carrier)

9 No routing is done for this code type; code 9 does not generate any outbound message

2.2 Applying Cancellation or Decisions to Cancel

Generally, only teams such as Dispatch or System Operations use the flight notification codes 1, 3, and 6.
These teams use these codes when canceling flights or making a decision to cancel the flight. The teletype
messages would still be generated as indicated above.
In intermediate cities, two flight progress entries are required: one entry for IN/OUT, and one entry for
OUT/OFF.
You should do this by using separate entries, as shown in the following examples:
First, view the existing Flight information. Example entry and response:
249

U00049/20APR
PVD 510P
RDU 655P 730P C24
ATL N1 D7 850P

Next, update the Flight Progress for each leg:

2P49/ORIG20APR4PVD/OUT510P OFF515P

DONE.1240P/20APR

2P49/ORIG20APR2RDU/ON650P IN655P

DONE.1240P/20APR

2P49/ORIG20APR4RDU/OUT730P OFF735P

DONE.1241P/20APR

2 Flight Updates
Training Guide 7 Confidential and Proprietary Sabre Airline Solutions
2P49/ORIG20APR2ATL/ON845P IN850P

DONE.1242P/20APR

Finally, review the updated Flifo:

249

U00049/20APR
PVD 510P
RDU 655P 730P C24
ATL N1 D7 850P
4PVD/OUT510P OFF515P*1240*HDQBCF
2RDU/ON650P IN655P*1240*HDQBCF
4RDU/OUT730P OFF735P*1241*HDQBCF
2ATL/ON845P IN850P*1242*HDQBCF

2.3 Updating Flight Progress

Use this format to make modifications to existing Flight Progress information in Flifo. Example entry:
2P127/ORIG23AUG4DUS/OUT920A OFF945A ATC

Item Description
2P Action code for Flight Progress

127 Example flight number

/ORIG23AUG Slash separator, indicator for Origin point, and date of origination

4 Notification code

DUS End Item character (as a separator) and board point

/OUT 920A OFF 945A Mandatory / slash separator andupdated Flight Progress information (free text, up to 225
ATC characters)

Example system response:

DONE.0244P/23AUG
RPLCD. FLWG MSG
4DUS/OUT913A OFF920A ATC*1417*HDQDQS

The response indicates that the new information has replaced the original information. The original information
now appears on the last line of the above response.
Notes

l Although the system allows free text after the flight progress, be careful not to enter a space between the
flight progress keyword and the time.
For example, a space between OUT and 920AM will cause spacing to be off in a VDS Daily Schedule

2 Flight Updates
Training Guide 8 Confidential and Proprietary Sabre Airline Solutions
 inventory display, because the system draws the data for the VDS response from the 2P entry. When the
spacing is off, part of the information is eliminated from the response.
l The Sabre system edits the entry for the notification code and the airport / city code. If there is more than
one line of flight progress, your entry must contain the exact notification and city / airport code of the line to
be changed.

2.3.1 Additional Application Notes

Item Description
Double For double date flights, always use the origination date for flight progress input.
Date
Flights

Round When applicable, you should input an asterisk (* ) after the city/airport code, to indicate that the
Robin information applies to the second occurrence of that city. For example: 2P127/ORIG23AUG2ORD*/IN
Flights 730A

Date You may update flight progress for yesterdays, todays, and tomorrow's flights.
Range

Reinstate When reinstating, the airport code you use to reinstate a flight leg must be the same airport code that was
Flights used to cancel the leg. When you reinstate a flight leg, the system updates both inventory and Flifo
records.

2.4 Deleting a Flight Progress

Use this format to delete a line of flight progress completely from Flifo.
Caution There should seldom be any need to delete flight progress completely from Flifo.
Example entry:
2X127/ORIG23AUG4DUS

Item Description
2X Action code for Flifo Deletion

127 Example flight number

/ORIG23AUG Slash separator, indicator for Origin point, and date of origination

4 Notification code

DUS End Item character (as a separator) and board point

2.5 Concerning Flight Dispatch

This section of this Training Guide is designed for Flight Dispatch or Operations agents / offices, whose
responsibility is to cancel legs / flights or place a decision to cancel into Flight Progress.

2 Flight Updates
Training Guide 9 Confidential and Proprietary Sabre Airline Solutions
2.5.1 Inputting a Flight No-Op / Cancellation

Use this format to input information about the cancellation of a flight. The entry updates both Flifo and
inventory records of the flight.
Note The entry is only permitted for duty codes 5, 7, and 8. In addition, your workstation must include the
UAT keyword DSPTCH (Dispatch).
Example entry:
2N31/ORIG18APR1SGN/FX EQUIP OUT OF SERVICE

Item Description
2N Action code for Flifo Cancel

31 Example flight number

/ORIG18APR Slash separator, indicator for Origin point, and date of origination

1 Notification code

SGN End Item character (as a separator) and board point

/FX EQUIP OUT OF SERVICE Required slash separator, cancellation code, and free text.

The valid cancellation codes are:

l LX - Landing Cancel
l FX - Complete flight Cancel
l DX - Departure Cancel

Example response

DONE.0413P/18APR

The following is an example of a Flifo entry and response containing a cancellation flight progress notice:
231

U00031/18APR
SGN 1255P C01
BKK 233P
1FX EQUIP OUT OF SERVICE*1612*HDQBCF

Example of the city pair availability response, after the flight cancel progress has been entered:
Note in the City Pair Availability response, the flight is now preceded by an X and the inventory count
shows blank (or 0).
1SGNBKK/6A

X 31 Y B H Q V K M SGNBKK 1255P 233P CRJ S 0 /E

2 Flight Updates
Training Guide 10 Confidential and Proprietary Sabre Airline Solutions
2.5.2 Updating a Landing Cancellation

Use this format to input information about the landing cancellation of a flight in the flight progress and
inventory records.
The Landing Canceled entry inhibits sales into and out of the airport city code specified, but allows sales
through that airport. For example,
l a flight operates from ADD to KLA to NBO.
l The landing at KLA is canceled, but the flight still operates ADD to NBO.
l If you input a Landing Canceled for KLA, no one can sell seats for the KLA to NBO leg, but they could
sell ADD to NBO.
l An X will appear in City Pair Availability to the left of the affected flight number.
Notes

l The city you specify in your entry is the city where the landing is being canceled.
l Use the Landing Canceled format for overfly situations, diversions and cancellations of origin / termination
airports.
Example entry:
2N63/ORIG18APR1KLA/LX DUE KLA WEATHER

Item Description
2N Action code for Flifo Cancel

63 Example flight number

/ORIG18APR Slash separator, indicator for Origin point, and date of origination

1 Notification code

KLA End Item character (as a separator) and board point

/LX DUE KLA WEATHER Required slash separator, cancellation code, and free text.

The valid cancellation codes are:

l LX - Landing Cancel
l FX - Complete flight Cancel
l DX - Departure Cancel

Example response

DONE.0423P/18APR

The following is an example of a Flifo entry and response containing a landing cancellation notice:
263

U00063/18APR
KLA 551P C06

2 Flight Updates
Training Guide 11 Confidential and Proprietary Sabre Airline Solutions
 NGO N1 D5 730P
1KLA/LX DUE KLA WEATHER*1623*HDQBCF

2.5.3 Updating a Departure Cancellation

Use a DX or Departure Cancellation entry when an intermediate flight leg is canceled on a multi-stop flight
and a downline non-connecting stub will originate. For example, a cancelled flight was traveling from SCL-
BUE-GRU-REC where BUE provides the STUB flight.
The DX entry inhibits sales out of and through the airport city code specified in the entry, but will allow sales
into that airport. An X will appear to the left of the flight number in City Pair Availability.
Notes

l Using the DX entry for this purpose will also require that a STUB input entry be made for departure from
the downline city.
l Notification code 6 is the only code valid for this entry.
To use the DX entry:
1. Add a departure cancellation text.
2. Add a flight STUB.
Example entry for adding Departure Cancellation text:
2N418/ORIG11SEP6SCL/DX DUE WEATHER

Item Description
2N Action code for Flifo Cancel

418 Example flight number

/ORIG11SEP Slash separator, indicator for Origin point, and date of origination

6 Notification code (code 6 is mandatory for DX)

SCL End Item character (as a separator) and board point

/DX DUE KLA WEATHER Required slash separator, cancellation code, and free text.

The valid cancellation codes are:

l LX - Landing Cancel
l FX - Complete flight Cancel
l DX - Departure Cancel

Example system response (the same as the LX and FX entries):

DONE. 1142A/11SEP

Example entry for adding a flight STUB:

2P418/ORIG11SEP5BUE/STUB ORIG DUE TO DX CANCEL WEATHER

2 Flight Updates
Training Guide 12 Confidential and Proprietary Sabre Airline Solutions
 Item Description
2N Action code for Flifo Cancel

418 Example flight number

/ORIG11SEP Slash separator, indicator for Origin point, and date of origination

5 Notification code

BUE End Item character (as a separator) and board point

/STUB ORIG DUE TO DX CANCEL WEATHER STUB code and free text

2.6 Updating a Flight Forecast

Use this format to advise of irregular flight operations such as delays, equipment changes, etc. This entry is
allowed for flights yesterday, today, and tomorrow. Example entry:
2F404/ORIG17APR5BNE/OP WITH DC10

Item Description
2F Action code for Flight Forecast

F0F Example flight number

/ORIG17APR Slash separator, indicator for Origin point, and date of origination

5 Notification code

BNE End Item character (as a separator) and board point

/OP WITH DC10 Mandatory / slash separator andFlight Forecast information (free text, up to 225 characters)

Example response:

DONE.1231P/17APR
RPLCD FLWG MSG
5BNE/OP WITH DC10*1223*HDQBCF

2.7 Viewing Flight Information History

Use this format to view a Flifo history that will provide all canceled items for a Flifo record. Example entry:
2H181/ORIG20OCTMEX

Item Description
2H Action code for Flifo History

181 Example flight number

/ORIG20OCT Slash separator, indicator for Origin point, and date of origination

MEX Board point

2 Flight Updates
Training Guide 13 Confidential and Proprietary Sabre Airline Solutions
Example system response:

4HAV/OUT0747*0646
2MEX/PRE0825*0648
2MEX/ETA0820*0701
2MEX/ETA0820*0737
2MEX/ETA0820*0745
3MEX/ETD0910 INOP LDR *0904
2LAX/PRE111

Notes

l For double dated flights, use date of flight origination.

l If no canceled items for Flifo exist, the response will be NONE.
l Date is optional: may use yesterday, today or tomorrow. The default date is today.

2 Flight Updates
Training Guide 14 Confidential and Proprietary Sabre Airline Solutions
Quick Reference of Entries

Example Entry Description

2127 Request Flifo for Date Departure

2P127/ORIG23AUG4DUS/OUT 913A OFF 920A Input Flight Progress

2P127/ORIG23AUG4DUS*/OUT1005A OFF 1020A ATC Input Flight Progress for Round Robin Flight

2X127/ORIG23AUG4DUS Delete Line of Flight Progress

2X127/ORIG23AUG-25AUG3DUS Reinstate Flight for Range of Dates

2H127 Flight Information History

3.1 Notification Codes

Code Office Function

1 Cancellation or Diversion

2 PRE, ETA, IN

3 DCSN, ETD

4 OUT, OFF

5 Flight forecast, STUB info

6 Departure Cancellation

9 Aircraft and tail number

3.2 Dispatch Entries

Example Entry Description

2N419/ORIG11SEP1SCL/FX EQ OTS Input Flight Cancellation into Flight Progress

2N419/ORIG11SEP1DFW/LX WEATHER Input Leg Cancellation into Flight Progress

2P419/ORIG11SEP1SCL/STUB ORIG DUE BUE XLC Input Departure Cancellation and Downline Stub into
CANCEL WEATHER Flight Progress

2F404/ORIG17APR5BNE/OP WITH 737 Input Flight Forecast

3.3 Flifo Acronyms / Codes

Note This is not a comprehensive or an official list, these are just some of the Flifo codes and shortcuts
which may be used in the industry.

Code Description

ACCOM Accommodate

3 Quick Reference of Entries

Training Guide 15 Confidential and Proprietary Sabre Airline Solutions
 Code Description

ACCT On account of, or because of

A/E, AWTEQ Awaiting Equipment

ALT Alternate city

ARNTP Air Interruption

ARR, ARVL Arrival

ASAP As Soon As Possible

BDNG Boarding
CGOHD Cargo Loading

CHG Change

CHG GAUGE, CHGEQ Changing Equipment (Change of Gauge)

CNCL, CXCL Canceled

CNDS Conditions

CNSLD Consolidated

CNTCS, CONNEX Connections

CNX Late Baggage

CREW Awaiting Crew

CX Cargo

DFRD Deferred

DLY Delay

DPTR Departure

EDM Equipment Distribution - Mechanical

EDWX Equipment Distribution - Weather

ENG Engine

EQOTS Equipment Out of Service

EQPTD Equipment Distribution Inbound

FDCND Field Conditions

FLCND Flight Conditions

FLOW Air Traffic

GATES Awaiting Gate Space

GDNTP Ground Delay

HDWND Headwinds

HLDG Holding

3 Quick Reference of Entries

Training Guide 16 Confidential and Proprietary Sabre Airline Solutions
 Code Description

HVYLOAD Heavy Load - landing to add fuel

IN Gate arrival time the time an aircraft pulls into a gate

INTMD Intermediate

IMPVMT Improvement

LDNG Landing

LDNG LMTS, LDLMT Landing Limits

LT Late

MECH, MX Mechanical

MNTC Maintenance

OPNL Operational

OPTG Operating

OSO Off-Schedule Operations

OTS Out-of-Service

OVR Overfly

PLN Plan

PLT Inbound teletype

PSVC Passenger Service

PVSLY Previously

R, RTN Routine

RNWY Runway (Tarmac)

RON Remain Overnight

RTRN Return

RVSD Revised

SCTD Scattered

SHWR Rain Showers

SKED Scheduled

STUB Substitution of Equipment

SVCG Servicing

TFC Traffic

TOLMT Take-Off Limits

TOP OFF Adding fuel

3 Quick Reference of Entries

Training Guide 17 Confidential and Proprietary Sabre Airline Solutions
 Code Description

TRM Terminate

TRDO Change Equipment

TURBC Turbulence

TSTM Thunderstorm

VSBY Visibility

WEA, WX Weather

WBM Weather Minimums

WL OPT Will Operate

3 Quick Reference of Entries

Training Guide 18 Confidential and Proprietary Sabre Airline Solutions