Professional Documents
Culture Documents
SITA Keyword Manual
SITA Keyword Manual
SITA Keyword Manual
Page 0 of 168
Section 11 Keywords
Page 1 of 168
Section 11 Keywords
EXAMPLES:
ALTM2) The required input should be entered immediately after the hyphen, without leaving
any blank spaces.
EXAMPLES:
ALT-EGLL
M-TEST ONLY
3) Keywords may be formatted one per line.
EXAMPLES:
ALT-EGLL
ETD-1615
FAL-330
4) Keywords may also be formatted with more than one per line, separated by a comma
(,) or a dollar sign ($).
Note: Care should be taken to ensure that keywords do not overrun the line length. An
invalid keyword format error will be received if the line length is exceeded.
EXAMPLES:
ALT-EGLL,ETD-1615$FAL-330
ERROR MESSAGES:
Page 2 of 168
Section 11 Keywords
CATEGORY INDEX
CATEGORY
DESCRIPTION
ACP
ATC
FUE
GEN
MET
NAV
SUM
Page 3 of 168
Section 11 Keywords
KWD
DESCRIPTION
CATEGORY
ATC
FUE
NAV
NAV
NAV
ATC
NAV
ATC
NAV
FUE
NAV
ACP
ACP
ACP
ACP
ACP
ACP
NAV
GEN
ACP
ACP
ACP
ACP
ACP
ACP
FUE
GEN
GEN
MET
NAV
ACP
ATC
SUM
NAV
MET
MET
FUE
FUE
FUE
NAV
ATC
ACP
GEN
FUE
ACP
GEN
ACP
GEN
ACP
ACP
Page 4 of 168
Page 5 of 168
Section 11 Keywords
SFISGFSHPSMBSMISMLSMZSPFSSFSWTSWXTAL TAXTDFTFUTLWTLXTNKTPATPETTITTOTWSTXITYFVIDWDAWDEWXSXFU1
SUM
ACP
GEN
SUM
SUM
SUM
SUM
GEN
ACP
SUM
MET
NAV
FUE
GEN
FUE
ACP
ACP
ACP
MET
MET
ACP
ACP
SUM
FUE
GEN
GEN
MET
MET
MET
FUE
Indicates that the keyword is flight plan format dependent. Contact the SITA Helpdesk for
further information.
Page 6 of 168
Section 11 Keywords
AFT-
PURPOSE:
Permits customers to send a flight plan or ATC plan to AFTN (Aeronautical Fixed
Telecommunications Network) addresses.
FORMAT:
AFT-
EXAMPLES:
1)
AFT-CFP/EGLLSOTX/EGLLXSUM
Forward complete flight plan to all specified AFTN addresses.
2)
AFT-SHP/EGLLSOTX/EGLLXSUM
Forward short flight plan to all specified AFTN addresses.
3)
AFT-ATC/EGLLSOTX/EGLLXSUM
Forward ICAO ATC plan to all specified AFTN addresses.
4)
AFT-AUTF/EGLLSITX
Forward ICAO ATC plan to AFTN addresses obtained from the FIR file only.
5)
AFT-AUTP/EGLLSITX
Forward ICAO ATC plan to AFTN addresses pre-stored in the parameter file
only.
6)
AFT-AUTO/EGLLSITX
Forward ICAO ATC plan to AFTN addresses obtained from the FIR and
parameter file.
Note: Removes any duplicate addresses.
Page 7 of 168
Section 11 Keywords
7)
AFT-AUT*/EGLLSITX/P
* AFT-AUTO, AUTP or AUTF
Attach AFTN addresses relevant to AUTF, AUTP, or AUTO input to flight plan.
Addresses will also be stored in the RFP file.
Note: Flight plan is not filed automatically if /P is added to the transaction.
ERROR MESSAGES:
AFTAFTAFTAFTAFTAFTAFTAFTAFTAFT-
ADDITIONAL INFORMATION:
Delay and cancellation of ICAO ATC plans can also be initiated. For further details, see the
RFP transaction in section 3 of the Flight Planning Reference manual.
For information on how to store AFTN addresses (via TypeB and/or QLLC) within the
parameter file please refer to section 5 of the Flight Planning Reference manual.
Page 8 of 168
Section 11 Keywords
KEYWORD:
AFU-
PURPOSE:
FORMAT:
EXAMPLE:
AFU-15000
Request 15000 kgs/lbs of additional fuel
ERROR MESSAGES:
AFUAFUAFU-
ADDITIONAL INFORMATION:
To request the maximum possible extra fuel uplift, see keywords XFU- or TFU-.
Page 9 of 168
Section 11 Keywords
KEYWORD :
ALT-
PURPOSE:
FORMAT:
ALT-
EXAMPLES:
1)
ALT-EGCC
Basic entry; use ICAO or IATA codes.
2)
ALT-EGCC/D/198
Override distance to an existing alternate or specify the distance to an alternate that
is not stored in the database.
Validation checks to ensure that the requested distance exceeds the great circle
route but does not check for a maximum distance.
D
198
= Distance
= Specified alternate distance
3)
ALT-NOALT
CFP is calculated without an alternate.
4)
ALT-NIFR
Holding fuel replaces diversion.
5)
ALT-EGCC/P
Request a flight plan to the shortest loaded alternate route.
6)
ALT-EGCC/S
Request a summary to the shortest loaded alternate route.
Page 10 of 168
Section 11 Keywords
7)
ALT-EGCC/P/12345
Request an alternate flight plan using the specified route, 12345.
8)
ALT-EGCC/S/12345
Request an alternate summary using the specified route, 12345.
ERROR MESSAGES:
ALTALTALTALTALTALTALTALTALTALTALTALTALTALT-
ADDITIONAL INFORMATION:
Request for ALT-NIFR will normally produce fuel equivalent for 2 hours holding at
destination at either optimum or TOD altitude depending on what is set in the Air Policy
file. This value can be changed in the Air Policy file only.
Alternate flight plan options are only available if at least one route exists between the
destination and the alternate unless RTE- is used to build route to the alternate.
Page 11 of 168
Section 11 Keywords
KEYWORD : AL2-
PURPOSE:
FORMAT:
AL2-
EXAMPLE:
1)
AL2-KJFK
Basic entry; use ICAO or IATA codes.
2)
AL2-KJFK/D/255
Override distance to an existing alternate or specify the distance to an alternate that
is not stored in the database.
Validation checks to ensure that the requested distance exceeds the great circle
route but does not check for a maximum distance.
D
255
= Distance
= Specified alternate distance
3)
AL2-KJFK/P
Request a flight plan to the shortest loaded alternate route.
4)
AL2-KJFK/S
Request a summary to the shortest loaded alternate route.
5)
AL2-KJFK/P/12345
Request an alternate flight plan using the specified route, 12345.
6)
AL2-KJFK/S/12345
Request an alternate summary using the specified route, 12345.
Page 12 of 168
Section 11 Keywords
ERROR MESSAGES:
AL2AL2AL2AL2AL2AL2-
ADDITIONAL INFORMATION:
The distance used in the alternate calculation is stored within individual airline alternate
records.
Alternate flight plan options are only available if at least one route exists between the
destination and the alternate.
Page 13 of 168
Section 11 Keywords
KEYWORD : AL3-
PURPOSE:
FORMAT:
AL3-
EXAMPLES:
All examples shown for keyword AL2- (second alternate) can be used, ensuring that
AL2- is replaced by AL3-.
ERROR MESSAGES:
AL3AL3AL3AL3AL3AL3-
ADDITIONAL INFORMATION:
The distance used in the alternate calculation is stored within individual airline alternate
records.
Alternate flight plan options are only available if at least one route exists between the
destination and the alternate.
Page 14 of 168
Section 11 Keywords
KEYWORD : ARM-
PURPOSE:
FORMAT:
ARM-
EXAMPLE:
1)
ARM-RMK/VIP FLIGHT
The output is shown in bold, below.
START OF ICAO FLIGHT PLAN
(FPL-SITTEST-IS
-A30B/H-SDHI/C
-EGLL1200
-N0468F270 DVR5F DVR UG1 KONAN UL607 KOK UG109 KRH UN850
ODINA UM727 AMTEL UL995 BOL DCT
-LIRF0201 LIRA
-EET/EBUR0020 EDUU0045 LSAS0107 LIMM0119 LIRR0141
REG/TEST SEL/ZZZZ
RMK/VIP FLIGHT)
END OF ICAO FLIGHT PLAN
ERROR MESSAGES:
ARM- REMARK TOO LONG , ONLY 68 CHARACTERS ALLOWED
ARM- ONLY 2 LINES ALLOWED
ADDITIONAL INFORMATION:
Maximum 68 characters per line, two lines available. Use ARM- input for each required
line.
Page 15 of 168
Section 11 Keywords
KEYWORD : ARP-
PURPOSE: Enables the creation of an airport for use as origin, destination or primary alternate.
FORMAT:
ARP-
REQUIRED FIELDS
/FIR
/AIRPORT ELEV
ARP-ZXXX/N4000E11650/ZSHAZR/157
ARP-ZYYY/N5000E11850/ZZZZZR/1
ARP-ZZZZ/N4915E11845/ZAAAZR/-1
ARP-ZYZY/N4920E11855/ZBBBZR/-5
ARP-ZYZZ/N4900E11845/ZCCCZR/-15
Use of the ARP keyword includes the mandatory use of the RTE keyword if the ORIG or
DEST airport is input using ARP.
If the ARP keyword is used to specify the primary ALT then the addition of the override
alternate distance on the ALT keyword is required.
ARP-ZXXX/N4000E11650/ZSHAZR/157
ALT-ZXXX/D/360
Copyright 2010 SITA. All rights reserved
The information contained herein is the property of SITA.
Legal action will be taken against any infringement.
Page 16 of 168
Section 11 Keywords
ARPARPARPARP
ARP
ARPARPARP
ARPARPARPARP-
Page 17 of 168
Section 11 Keywords
KEYWORD :
ATC-
PURPOSE:
FORMAT:
ATC-
EXAMPLES:
1)
ATCKeyword without further parameter (i.e. blank) provides an ATC plan where item
8 is assumed to be IS.
2)
ATC-IN
ATC-IS
Item 8 amended to show IN (IFR Non-scheduled) or IS (IFR scheduled).
3)
ATC-IN/1
ATC-IS/1
Amends item 8 to show IN or IS. The addition of /1 removes item numbering from
the ATC plan.
4)
ATC-N
Removes ATC request if this is a stored parameter.
Page 18 of 168
Section 11 Keywords
KEYWORD : AUS-
AUS-
PURPOSE:
FORMAT:
AUS-
EXAMPLE:
1)
2)
3)
4)
AUS-AUTO
AUS-AUTP
AUS-E
AUS-SY1A 16S130E
ERROR MESSAGE:
AUS MAY NOT BE USED WITH NAT, PAC OR HNL KEYWORDS
AUS UNRECOGNISABLE INPUT FORMAT
AUS 4 CHARACTER IDENTIFIER FOR AUS TRACKS
AUS FORMAT IS N OR S 2 DIGITS/W OR E 3 DIGITS
AUS CO-ORDS SHOULD BE SEPARATED BY A SPACE
AUS NO LAT/LONGS AVAILABLE FOR THIS TRACK
AUS MORE THAN 20 LAT/LONGS ENTERED
AUS LATITUDE (V) NOT BETWEEN 00 AND 80
AUS LATITUDES (V) & (V) NOT WITHIN 15 DEGREES
AUS LONGITUDES MUST BE HEADING IN SAME DIRECTION
AUS LONGITUDE (V) NOT BETWEEN 0 AND 180 DEGREES
AUS LONGITUDE (V) NOT A MULTIPLE OF 5
AUS LONGITUDES MAY NOT BE EQUAL ((V))
NOTE :
1)
AUTO is used to generate a Track Summary showing order of best track from
published AUSOTS message.
2)
AUTP has same function as AUTO, output is Track Summary and Flight Plan on
best track.
3)
Page 19 of 168
Section 11 Keywords
KEYWORD :
BAL-
PURPOSE:
FORMAT:
BAL-
EXAMPLE:
1)
BAL-1000
Up to 5 numerics; leading zeros not required
ERROR MESSAGES:
BAL- MUST BE NUMERIC,MAX 5 DIGITS & ABOVE 0
ADDITIONAL INFORMATION:
This fuel item relates to unusable, dead, calibration, residual or ballast fuel.
The BAL- input overrides the Residual Fuel value stored in the Air Policy file (see Air Policy file,
screen 1).
The specified BAL- fuel is carried throughout all phases of the flight plan calculation.
This keyword is flight plan format dependent. Contact the SITA Helpdesk for further information.
Whilst BAL fuel is included in the total tank fuel, its value is not included in any fuel checked
overhead the destination (MOD) or the Alternate (MOA). It is also not included in fuel available for
an ETOPS diversion.
Page 20 of 168
Section 11 Keywords
KEYWORD :
BLK-
PURPOSE:
FORMAT:
EXAMPLES:
1)
BLK-EGLLBIKF02
or
BLK-100123
Exclude one route:
i)
The first example uses a customer route name.
ii)
The second example uses a SITA route name.
2)
BLK-EGLLBIKF01/100123/LHRKEF04
Exclude 3 specific routes.
Customer and SITA route numbers can be combined.
ERROR MESSAGES:
BLK- ROUTE nn INVALID, MUST BE MAX OF 10 CHARACTERS.
BLK- BLK nn IS SAME AS EXIT USE EXT-0 TO OVERRIDE
BLK- ROUTE SPECIFIED, nn IS INVALID FOR SECTOR
Page 21 of 168
Section 11 Keywords
KEYWORD :
CAL-
PURPOSE:
Optimise flight level selection, whilst imposing a limitation on the maximum cruise
flight level. The selected flight level may be at or below the requested level.
FORMAT:
CAL-
EXAMPLE:
1)
CAL-280
Specified flight level must be 3 numerics.
ERROR MESSAGES:
CAL- VALUE MUST BE IN THE RANGE 010-490
CAL- MUST BE ABOVE MIN CRUISE LVL OF (V) FOR (V)
ADDITIONAL INFORMATION:
If the calculated flight level is below MORA then a warning can be displayed on the flight
plan.
CAL- will limit maximum flight level to that specified, whilst optimising calculation of Flight
Level at or below the specified value.
From this is follows that the value of CAL input may never be attained on the flight plan
as the optimum level could be lower.
Page 22 of 168
Section 11 Keywords
KEYWORD : CBF-
PURPOSE:
To override the climb fuel adjustment (degradation) factor held in the aircraft
attribute (ACATR) file.
The stored climb fuel flow (as supplied by airline/manufacturer), can be
increased/decreased by a specified percentage, in order to account for those
aircraft whose performance may vary from published figures.
FORMAT:
CBF-
EXAMPLE:
1)
CBF-1.025
Based on a climb fuel of 3000 kg, this CBF- input would increase the climb fuel
flow by 2.5% to 3075 kg.
2)
CBF-0.950
Based on a climb fuel of 3000 kg, this CBF- input would decrease the climb fuel
flow by 5% to 2850 kg.
ERROR MESSAGES:
CBF- FORMAT IS N.NNN, BETWEEN 0.850 & 1.250
CBF- VALUE MUST BE BETWEEN 0.850 - 1.250
ADDITIONAL INFORMATION:
An input of CBF-1.000 does not provide an adjustment factor (degradation): i.e. basic
unadjusted book values.
RELATED KEYWORDS:
For modification of cruise fuel, see CZF-.
Page 23 of 168
Section 11 Keywords
KEYWORD :
CID-
PURPOSE:
To define a Cost index, or override the pre-stored value for the purpose of
calculating a flight plan based on a least cost (ECON) cruise speed and altitude.
FORMAT:
CID-
EXAMPLE:
CID-038
(Maximum 3 numerics.)
ERROR MESSAGES:
CIDCIDCIDCIDCIDCID-
ADDITIONAL INFORMATION:
(2)
The units are defined as Imperial or Metric in the Air Policy File, if units detail is
absent then the default is Imperial
This facility enables the customer to provide cost data in a form which does not breach
confidentiality of fuel price and operating costs.
Where the Fuel Costs (FCO) and Time Costs (HOC) are in use, an input of CID will
overwrite the HOC used in the calculation.
If neither real fuel cost or time costs are available then the input of CID will set a
theoretical fuel price of $ 1 per US Gallon and then calculate from the CID value the Time
Costs
May also be used when Flight Plans are required to match PMS+ Cost Index setting
without accurate knowledge of fuel price or operating costs.
Where the aircraft attribute file holds a value of FMA, use of CID- requires that keyword
FMA-000 is used together with CRZ-1
Further information regarding the Cost Index calculation can be obtained from the SITA
Aircraft Performance department.
Page 24 of 168
Section 11 Keywords
KEYWORD : CPA-
PURPOSE:
FORMAT:
CPA
Followed by a flight level; value should be between 010 and 490
EXAMPLE:
1)
CPA-110
Alternate flight level is capped at FL110.
ERROR MESSAGES:
CPA- MUST BE 1-3 NUMERICS, 010-490
CPA- MUST BE ABOVE MIN CRUISE LVL OF (V) FOR (V)
CPA- MUST NOT BE ABOVE MAX LEVEL OF (V) FOR (V)
ADDITIONAL INFORMATION:
If the requested level does not conform with stored cruise table levels, the first available
level below will be used.
Page 25 of 168
Section 11 Keywords
KEYWORD :
CP2-
PURPOSE:
FORMAT:
EXAMPLE:
1)
CP2-110
Second alternate flight level is capped at FL110.
ERROR MESSAGES:
CP2- MUST BE 1-3 NUMERICS, 010-490
CP2- MUST BE ABOVE MIN CRUISE LVL OF (V) FOR (V)
CP2- MUST NOT BE ABOVE MAX LEVEL OF (V) FOR (V)
ADDTIONAL INFORMATION:
If the requested level does not conform with stored cruise table levels, the first available
level below will be used.
Page 26 of 168
Section 11 Keywords
KEYWORD :
CP3-
PURPOSE:
FORMAT:
EXAMPLE:
1)
CP3-110
Third alternate flight level is capped at FL110.
ERROR MESSAGES:
CP3- MUST BE 1-3 NUMERICS, 010-490
CP3- MUST BE ABOVE MIN CRUISE LVL OF (V) FOR (V)
CP3- MUST NOT BE ABOVE MAX LEVEL OF (V) FOR (V)
ADDTIONAL INFORMATION:
If the requested level does not conform with stored cruise table levels, the first available
level below will be used.
Page 27 of 168
Section 11 Keywords
KEYWORD :
CPN-
PURPOSE:
FORMAT:
CPN-
EXAMPLES:
1)
CPN-999999
System will optimise flight plan using SITA routes only.
2)
CPN-000000
System will optimise flight plan using customer routes.
Note: If customer routes cannot be found for the specified sector, the system will
automatically revert to CPN-999999, to optimise from stored SITA routes.
ERROR MESSAGES:
CPN- MUST BE NUMERIC, MAXIMUM 6 DIGITS
CPN- NO ROUTES EXIST FOR (V) / (V)
CPN- (V) INVALID FOR (V) / (V)
Page 28 of 168
Section 11 Keywords
KEYWORD : CPT-
PURPOSE:
FORMAT:
ERROR MESSAGE:
CPT- NAME MUST BE ENTERED, MAXIMUM OF 24 CHARACTERS
NOTE :
1)
The input is limited to 24 alpha characters. Full stops may be used (they will
count as one character.)
2)
This Keyword is format related, and may only be used when format is
programmed to print out Captain's name.
3)
The Error Message displayed above would apply when CPT- was pre-stored as a
mandatory Keyword and had been omitted from CFP request.
Page 29 of 168
Section 11 Keywords
EYWORD : CRP-
CRP-
PURPOSE:
FORMAT:
CRP-
EXAMPLE:
1)
2)
3)
ERROR MESSAGES:
CRP (V) INVALID, CRUISE MODE MUST BE 1-3
FORMAT IS CRP-9 OR -/9 OR -9/9
CRP FORMAT IS CRP-9 OR -/9 OR -9/9
1ST VALUE 1-3, 2ND VALUE 1-4
NOTE :
1)
2)
Page 30 of 168
Section 11 Keywords
KEYWORD : CRZ-
CRZ-
PURPOSE:
FORMAT:
EXAMPLE:
ERROR MESSAGES:
CFP-CRZ MUST BE NUMERIC 1, 3 or 5 ONLY
NOTE :
1)
2)
The input CRZ- will not override a loaded fixed mach number * See Keyword
FMA.
3)
CRZ- 1 - Cost factors must have have been previously provided to use this.
4)
5)
Page 31 of 168
Section 11 Keywords
KEYWORD : CZF-
CZF-
PURPOSE:
FORMAT:
CZF-
EXAMPLE:
1)
2)
CZF-1.025
CZF-0.950
ERROR MESSAGES:
CFP-CZF MUST BE NUMERIC IN FORMAT N.NNN, 0.850-1.250
NOTE :
1)
Some A/C types exhibit a loss in specific fuel consumption (LB/HR/LB thrust) or
specific range (LB/NAM) with age. i.e. they burn more fuel than that shown in
manufacturers data.
2)
Some newer A/C may show an improvement over manufacturers data i.e. they
burn less fuel than manuals would indicate.
3)
The cruise fuel adjustment factor (CZF-) allows the hourly fuel flow to be adjusted
accordingly, multiplying manufacturers hourly fuel flow by the specified amount.
4)
5)
6)
7)
As stated under the heading 'Purpose', the value input by CZF- will override the
ACATR file held value, so to use 1.020 (a 2% degradation) might override a 3%
value in the ACATR, thereby reducing the degradation otherwise used by 1%.
Page 32 of 168
Section 11 Keywords
KEYWORD : CZT-
PURPOSE:
FORMAT:
CZT-
EXAMPLE:
ERROR MESSAGES:
CZT
CZT
CZT
NOTE :
1)
The forecast temperature for which a cruise speed thrust check is made, will be
modified by the entered value.
2)
The default temperature pad currently applied in the SITA system is +5 degrees.
3)
4)
5)
6)
The temperature buffer stored in the Airpolicy file is still applied even in still air
and fixed temperature plans.
Page 33 of 168
Section 11 Keywords
KEYWORD : DMF-
PURPOSE:
FORMAT:
DMF-
EXAMPLE:
ERROR MESSAGE:
CFP-DMF MUST BE NUMERIC MAXIMUM 4 DIGITS
NOTE :
1)
This input can be used in place of DMT to provide a fixed amount of Departure
Manoeuvre fuel with no time credit.
Input actual value required.
In the Example 2200 KGS or LBS is the fuel quantity specified.
2)
3)
Page 34 of 168
Section 11 Keywords
KEYWORD : DMT-
DMT-
PURPOSE:
FORMAT:
DMT-
EXAMPLE:
ERROR MESSAGE:
CFP-DMT MUST BE NUMERIC, NOT GREATER THAN 20
NOTE :
1)
Departure manoeuvre time will move the T.O.C. position, which in turn will give
added cruise fuel to allow for the additional time spent in the cruise mode. The
overall effect will be an increase in trip fuel, which will be evident in the segment
T.O.C. to 1st waypoint.
2)
3)
Page 35 of 168
Section 11 Keywords
KEYWORD : DPP-
PURPOSE:
FORMAT:
DPP-
EXAMPLE:
1)
2)
3)
DPP-GCLP/PLATY
DPP-GCLP/PLATY/123400
DPP-GCLP/PLATY/AUTO
ERROR MESSAGES:
DPP INITIAL AIRPORT MUST BE 3 CHAR IATA OR 4 CHAR ICAO
DPP-DEST ICAO CODE - ZZZZ NOT FOUND FOR AIRLINE
DPP-ALT MUST NOT BE USED FORMAT XXX/9999 OR XXXX/9999
DPP- ONLY DPP OR RCR CAN BE USED
Notes:
1)
The DPP facility is very similar to Reclear and much of the flight plan calculation is
identical. There are 3 main differences between RCR and DPP, these are:
a. The term INITIAL DESTINATION in RCR is termed EN ROUTE ALTN
in DPP and there is NO further airport planned for after the En Route
Alternate specified.
b. The RECLEAR POINT (FIX) is termed DECISION POINT in DPP.
c. The theory of RCR is that the unburnt contingency between the Origin and the
Reclear point together with the other fuel remaining onboard is sufficient
to continue the flight to a Final Destination including terminal reserves. Any
in-balance of fuels at the Reclear Point is added as Balancing Fuel With
RCR the percentage of trip fuel used to calculate Contingency fuel normally
remains the same throughout the calculation.
With DPP the Contingency fuel is calculated (normal at 3%) from the Origin to
the En Route Alternate via the Decision Point. The Contingency for the route
to the Destination is 0% from the Origin to the Decision Point then normally
5% from the Decision point to the Destination. The fuels, Origin to the enroute
alternate and Origin to the Destination are compared at the Decision Point
and again any necessary, balancing fuel added to the required leg.
The effective contingency percentages are set on page 9 of the Air Policy File
In terms of the Air Policy file, page 9 retains the title Reclear . In terms of the
NAV Data, the waypoint loaded is still called a Reclear Fix, the position and
route can in fact be used for either a Reclear or a Decision Point
flight plan.
(continued)
Page 36 of 168
Section 11 Keywords
(continued)
KEYWORD : DPP2)
This is a multi parameter Keyword for specifying DPP details. The format is as
follows:
The first parameter is the En Route Alternate in ICAO/IATA code.
The second parameter is the Decision Point as a max five alpha/numeric
character field which must match exactly the identification of the waypoint
specified as the reclear point in the route description ( Note the term reclear is
used as described in Note 1.)
The third parameter is maximum landing weight at the En Route Alternate, omit
if unrestricted; add if specific landing weight restriction applies. Landing weight is
expressed in units. Add if overweight landing (for Flight Planning purposes) is
required.
* As Decision Points (Reclear fixes) are specific to a nominated route then an EXT
input must also be present in the CFP request.
EXAMPLE:
DPP-GCLP/PLATY/123400
Decision Point (Reclear fix) - PLATY
RLW-123400
3)
4) It is necessary that a user of DPP has pre arranged for a specific format be set up so
that the output for DPP can be correctly presented. Again, the terminology of such a
format would be a reclear format and its format code shown in the Air Policy Page 1
FORMAT GEN CODES - RECLEAR field.
Page 37 of 168
Section 11 Keywords
KEYWORD : DRM-
PURPOSE:
FORMAT:
DRM-
EXAMPLE:
ERROR MESSAGES:
DRM-ONLY ONE DRM LINE ALLOWED
NOTE :
1)
This Keyword is Format related. You must advise SITA Helpdesk where you
want the information displayed before it will print.
2)
Page 38 of 168
Section 11 Keywords
KEYWORD : DSP-
PURPOSE:
FORMAT:
DSP-
EXAMPLE:
DSP- SMITH
DSP- SMITH/BROWN
ERROR MESSAGE:
DSP DISPATCHER NAME MUST BE ENTERED
MAY ENTER 2 NAMES, MAX 24 CHARS EACH, JOIN WITH A /
DSP DISPATCHER LINE EXCEEDS MAXIMUM LENGTH OF 49
DSP INVALID CHARACTER "(V)" IN DISPATCHER NAME
DSP ONLY ONE "/" SEPARATOR ALLOWED
DSP ONE NAME EXCEEDS MAXIMUM LENGTH OF 24
NOTE :
1)
This Keyword is format related and may only be used when format is
programmed to print out dispatchers names (maximum 2).
2)
Page 39 of 168
Section 11 Keywords
KEYWORD : DTE-
PURPOSE:
FORMAT:
DTE-
EXAMPLE:
1)
2)
3)
4)
5)
6)
7)
All of the above can have a / followed by the probability factors 50 to 85 in steps of 5.
e.g. DTE-QTR2/75 - Second quarter with a probability of 75%.
8) DTE-24APR (where value input is current date).
This is used in order to use the next days weather if the time of the flight is more than
24 hours in the future. (Beyond 36 hours is not possible due to lack of weather
information). It can also be used if the time of the plan has already passed.
ERROR MESSAGES:
DTE- INVALID FORMAT
DTE-010MAR
INVALID FORMAT
DTE-MONTH- DTE IS INVALID, USE JAN, FEB ETC...
DTE-DAY 30 INVALID, ONLY 28 DAYS FEB
DTE- MONTH-XXX IS INVALID, USE JAN,FEB ETC..
*any other combinations such as DTE-OCTDEC will give a front-end validation error "DTE-INVALID
INPUT FORMAT"
Page 40 of 168
Section 11 Keywords
KEYWORD : ECT-
PURPOSE:
FORMAT:
EXAMPLE:
ECT-10236/5624/1483
ERROR MESSAGES:
ECT ROUTE (V) INVALID, MUST BE 1-6 DIGITS SEPARATED BY /
ECT MUST NOT BE ENTERED WITH CPN 999999
ECT ROUTE SPECIFIED, (V) IS INVALID FOR SECTOR
NOTE :
1)
This facility is the opposite to BLK-. The customer should employ either ECT- or
BLK- dependent on whether it is easier to block or elect specific routes.
2)
3)
ECT- may also be used to elect a specific ENTRY and EXIT segment in the
Oceanic case, (format remains the same). See NAT- Keyword.
Page 41 of 168
Section 11 Keywords
KEYWORD : EEP-
PURPOSE:
To define the ETOPS Entry and Exit airports and to initiate the
calculation of ETOPS Entry and ETOPS Exit times.
FORMAT:
EXAMPLE:
1)
2)
ERROR MESSAGES:
EEP
EEP
EEP
EEP
EEP
EEP
NOTE :
1)
2)
3)
The Entry Point is the point on the aircrafts outbound route which is the one hour
flying time at the approved single engine inoperative cruise speed from an
Adequate Airport. The same definition can be used for the Exit Point except it is
the point on the aircrafts inbound route etc. Between the Entry Point and the
Exit Point exists the ETOPS segment.
More than one ETOPS segment can exist on a given route hence it is possible to
make multiple inputs of EEP. (Maximum 10).
Whilst an Entry airport has to be specified each time EEP is used, it is not
mandatory to use a second (Exit) airport.
Page 42 of 168
Section 11 Keywords
KEYWORD : EQP
EQP-
PURPOSE:
FORMAT:
EQP-XXXXXX/Y
Where : X is between 1 and 10 ALPHA
characters. (NAV/COM equipment)
/ is a mandatory character
Y is a single ALPHA character. (SSR
equipment)
EXAMPLE:
EQP-SDIXY/C
ERROR MESSAGES:
EQP-MUST BE IN THE FORMAT EQP-XXX/Y
EQP-NON ALPHA CHARACTER USED
EQP-SSR CODE MUST BE EITHER N,A,C,X,P,I,S
NOTE :
1. The valid NAV/COM equipment codes are listed in ICAO Doc 4444-RAC/501
Appendix 2, Item 10. The Surveillance (SSR) equipment codes are also listed after
the NAV/COM codes.
2. Using the keyword will not update the Attribute file, only change the code for the CFP
being requested.
2)
.
4)
5)
EQP will overwrite ALL the detail in ITEM 10 in the Attribute file for
the CFP being requested, it does not add to existing codes therefore it
is important to supply all equipment codes when using the keyword.
In the Example the input EQP-SDIXY/C would cause the ICAO plan to
display the updated code, example: A310/H-SDIXY/C
If a W is part of the NAV/COM codes RVSM flight levels will be used
in the CFP calculation within the MNPS areas, exclusion of W will excluded
RVSM levels being considered.
Page 43 of 168
Section 11 Keywords
KEYWORD : EQT-
EQT-
PURPOSE:
FORMAT:
EQT-
EXAMPLE:
EQTEQT-EINN/LPLA/T390/L100/F04000
ERROR MESSAGES:
EQT
EQT
EQT
EQT
EQT
EQT
EQT
EQT
EQT
EQT
EQT
NOTE :
1)
The Keyword EQT- (without parameters) will produce a summary line appended
to the Flight Plan, showing Fuel burn, Elapsed time, and Distance; "all engines
operating" to the Equal Time Point between Origin and Destination.
2)
Maximum 10 Equi time points can be requested to generate an ETOPS EQTsummary. Each EQT- entry must include 5 parameters.
PARAM 1 and 2 are Airport pair ie. EINN/LPLA
PARAM 3 is True air speed from EQT ie. T390
PARAM 4 is Flight level from EQT ie.L100
PARAM 5 is Fuel flow from EQT ie.F04000 (strict 5 digits entered; max is
40,000 lbs or 18144 kgs).
Page 44 of 168
Section 11 Keywords
KEYWORD :
ERA-
ERA-
PURPOSE:
FORMAT:
ERA-
EXAMPLE:
ERA-EGCC
ERROR MESSAGES:
ERA-MUST BE 3 CHAR IATA
ERA-ZXZX IS NOT A VALID
ERA-CANNOT BE USED WITH
ERA-CANNOT BE USED WITH
ERA-CANNOT BE USED WITH
ERA-CANNOT BE USED WITH
Notes:
1)
The effect of using the ERA keyword is to change the effective percentage of
Contingency fuel calculated from the normal amount to that specified in the ERA
field on Page 8 of the Air Policy file. If no value or 000 is loaded then the normal
percentage will apply.
2)
The influence of any Minimum or Maximum Contingency and any Contingency Pad
specified elsewhere will be applied to the amount calculated using the percentage
modified by the ERA keyword.
3)
JAR-OPS 3% ERA rules state that the normal 5 PCT can be reduced to 3 PCT if an ERA
is both nominated and validated (Page 10 of the Air Policy file), if validation fails then 5%
will be used and a warning message appears at the top of the completed flight plan.
4)
5)
This keyword output is limited to airport name and can only be used when flight plan
format has been set to accommodate it; there is no flight plan calculation to the enroute
alternate.
6)
This keyword is format related and may only be used when the format has been set up to
include the data. Please contact SITA Helpdesk for further assistance.
Page 45 of 168
Section 11 Keywords
KEYWORD : ETA-
ETA-
PURPOSE:
FORMAT:
ETA- (4 numerics)
EXAMPLE:
ERROR MESSAGES:
ETA MUST BE 4 NUMERICS, 24 HOUR CLOCK FORMAT
ETA (V) IS NOT A VALID TIME
ETA MUST BE SPECIFIED FOR A 9999 FLIGHT
NOTE :
Mandatory input if /9999 parameter screen is used.
Page 46 of 168
Section 11 Keywords
KEYWORD : ETD-
ETD-
PURPOSE:
FORMAT:
ETD-
EXAMPLE:
ETD-0600
(4 numerics)
(24 hr clock)
ERROR MESSAGES:
ETD MUST BE 4 NUMERICS, 24 HOUR CLOCK FORMAT
ETD (V) IS NOT A VALID TIME
ETD FLIGHT DURATIONOF (V) HOURS (V) MINS IS NOT IN RANGE
MUST BE BETWEEN 10 MINS AND 18 HRS OF ETA
ETD MUST BE BETWEEN 10 MINS AND 18 HRS OF ETA
ETD MUST BE SPECIFIED FOR A 9999 FLIGHT
NOTE :
1)
2)
CFP requests received after the ETD- will be calculated using next day's
weather.
Page 47 of 168
Section 11 Keywords
KEYWORD :
ETE-
PURPOSE:
This is one of the ETOPS keywords. It is used to provide/print the fuel necessary
to reach the first airport listed in the ETE keyword in an ETOPS configuration
from a position on the flight plan route that is 60 minutes from the second airport
listed in the keyword. An example of where this might be used is
when the second airport cannot be used as an ETOPS Alternate because the
airport is outside ETOPS Weather minima.
FORMAT:
ETE-
EXAMPLE:
ERROR MESSAGES:
ETE-FIRST AND SECOND AIRPORTS MUST BE ENTERED.
ETE-AIRPORT MUST BE 3 CHAR IATA OR 4 CHAR ICAO.
ETE-UNRECOGNISABLE FORMAT
ETE-AIRPORT XYZ NOT FOUND ON AIRPORT DATABASE
ETE-ONLY 5 LINES ARE ALLOWED
ETE-SPEED SCHEDULE MUST BE 100 - 600 KIAS OR 999
ETE-DEGRDN FACTOR MUST BE FORMAT 9.999 (0.500 - 2.000)
Notes:
1)
In the examples used above, the fuel would be calculated to airport AAAA from the
intersection of the flight plan route with a 60 minutes circle drawn round BBBB. The fuel
calculation is based on the same ETOPS logic as is used to determine fuel to the airports
listed in an ETP or ETX calculation including the determination of any Critical fuel.
2)
If Critical fuel is found necessary the logic of either ETP or ETX is applied, which logic is
used is determine whether ETP or ETX has been used in the flight plan request. Therefore, if
ETP has been used, any Critical fuel found by the ETE calculation will be presented on the
flight plan ETOPS output with the necessary Warning Message. If ETX has been used then
any Critical fuel by the ETE calculation will be added to the total flight plan fuel.
3)
The input sequence of more than one ETE keyword must reflect the logical order of the route
being flown
4)
The Speed and/or Level input with the ETE keyword must be supported by data in the
Engine Out File for the aircraft type.
5) Currently Alternate Availability times do not use ETE diversion detail, that is the
Earliest/Latest times for the airport specified as AAAA in the example is not calculated.
This will be included in a later software release.
ETE-
Page 48 of 168
Section 11 Keywords
KEYWORD : ETP-
PURPOSE:
FORMAT:
ETP-
EXAMPLE:
1)
2)
3)
4)
5)
6)
7)
ERROR MESSAGES:
ETP
ETP
ETP
ETP
ETP
ETP
ETP
ETP
ETP
ETP
ETP
NOTE :
1)
The airports specified in the Keyword can be entered in ICAO or IATA format Up
to 10 airport pairs can be entered but must be in a logical sequence for the Flight
Plan route.
2)
The inclusion of the 'I' parameter causes the calculated Alternate fuel for both All
Engines and One Engine In-Op to be increased by the percentage required (prestored) for Icing conditions.
3)
The Example shows a degradation of 2.5 per cent needs to be applied to the
calculated Alternate fuels. For the ETP Alternate, this adjustment overrides the
degradation loaded in the ACATR file.
(continued)
Copyright 2010 SITA. All rights reserved
The information contained herein is the property of SITA.
Legal action will be taken against any infringement.
Page 49 of 168
Section 11 Keywords
KEYWORD : ETP-
(Continued)
4)
The Example shows the default one Engine In-Op speed schedule has been
overridden by a requirement to use the 300 KIAS schedule. If the schedule is not
loaded then an error message is produced.
5)
The Example shows the default Flight Level for One Engine In-Op (normally
FL100) has been overridden by a requirement to use the data loaded for Flight
Level 120. If data for the specified Flight Level is not loaded an error message
is produced.
5)
6)
7)
The example shows the default Rule Time has been overridden by a
requirement to use 120 mins for that alternate pair.
Page 50 of 168
Section 11 Keywords
KEYWORD : ETX-
ETX-
PURPOSE:
FORMAT:
ETX-
EXAMPLE:
ETX-HKNA/FIMP
ETX-HKNA/FIMP/I
ETX-HKNA/FIMP/1.025
ETX-HKNA/FIMP/300
ETX-HKNA/FIMP/L120
ETX-HKNA/FIMP/300/I/1.05/L120
ETX-HKNA-RIMP/T120
ERROR MESSAGES:
ETX
ETX
ETX
ETX
ETX
ETX
ETX
ETX
ETX
ETX
ETX
NOTE :
1)
The airports specified in the Keyword can be entered in ICAO or IATA format.
Up to 10 airport pairs can be entered but must be in a logical sequence for the
Flight Plan route.
2)
The inclusion of the 'I' parameter causes the calculated Alternate fuel for both All
Engines and One Engine In-Op to be increased by the percentage required for
Icing conditions.
Page 51 of 168
Section 11 Keywords
KEYWORD : ETX-
(continued)
3)
4)
The Example shows the default One Engine In-Op speed schedule has been
overridden by a requirement to use the 300 KIAS schedule. If the schedule is not
loaded then an error message is produced.
5)
The Example shows the default Flight Level for One Engine In-Op (normally
FL100) has been overridden by a requirement to use the data loaded for Flight
Level 120. If data for the specified Flight Level is not loaded, an error message
is produced.
6)
7)
Page 52 of 168
Section 11 Keywords
KEYWORD : EXT-
PURPOSE:
FORMAT:
EXT- (1 to 6 numerics)
EXAMPLE:
EXT-10123
ERROR MESSAGES:
EXT
EXT
EXT
EXT
NOTE :
1)
In the Example the EXIT number 10123 is specified, and this is the only route the
computer will examine and subsequently produce in the Flight Plan.
Page 53 of 168
Section 11 Keywords
KEYWORD : FAA-
PURPOSE:
FORMAT:
FAA-
EXAMPLE:
FAA-
Page 54 of 168
Section 11 Keywords
KEYWORD : FAL-
PURPOSE:
FORMAT:
FAL-
EXAMPLE:
FAL-250
(maximum 3 numerics)
ERROR MESSAGES:
FAL MUST BE NUMERIC, 010 TO 490
FAL MUST BE ABOVE MIN CRUISE LVL OF (V) FOR (V)
FAL MUST NOT BE ABOVE MAX LEVEL OF (V) FOR (V)
NOTE :
1)
The Flight Plan will indicate a climb to the specified altitude/Flight Level as soon
as possible within the thrust limits and buffet protection, overriding economic
considerations of optimum flight level, but conforming to ICAO tables of cruising
levels.
2)
In the Example flight level 250 is specified; the aircraft will climb to and maintain
25000 ft. (FL250)
3)
The specified FAL- will be the maximum level for the Flight Plan.
4)
5)
Generally used to fix the Cruise level at a height lower than that which would be
selected by the computer's height optimisation module.
Page 55 of 168
Section 11 Keywords
KEYWORD : FAX-
FAX-
PURPOSE:
FORMAT:
FAX-
EXAMPLE:
1)
FAX-11223334444
ERROR MESSAGES:
FAX MINIMUM OF 7 DIGITS
FAX MAXIMUM OF 20 DIGITS
FAX FIELD MUST BE NUMERIC
NOTE :
1)
2)
3)
4)
Flight Plan output is sent to HDQFAXS for processing in the same way as normal
message sent via SITATEX for FAX delivery.
5)
HDQFAXS will return advisory message to the CFP Originator (Airline Customer),
stating whether or not the plan has been delivered to the fax address.
6)
Fax numbers are not validated so messages sent using this facility must be
checked carefully.
7)
Page 56 of 168
Section 11 Keywords
KEYWORD : FCD-
FCD-
PURPOSE:
FORMAT:
FCD-
EXAMPLE:
FCD-2.0003
ERROR MESSAGE:
FCD MUST BE IN FORMAT 9.9999
NOTE :
1)
The FCD keyword input overrides any value held in the Fuel Price File for the
destination airport.
2)
This Keyword provides the destination fuel price to the Tankering program when
used together with the TNK Keyword
Page 57 of 168
Section 11 Keywords
KEYWORD : FCO-
PURPOSE:
FORMAT:
FCO-
EXAMPLE:
FCO-2.0003
ERROR MESSAGE:
FCO MUST BE IN FORMAT 9.9999
NOTE :
1)
The FCO keyword input overrides any value held in the Fuel Price File for the
origin airport.
2)
This Keyword provides the origin fuel price to the Tankering program when used
together with the TNK Keyword
.
3)
Page 58 of 168
Section 11 Keywords
KEYWORD : FLT-
FLT-
PURPOSE:
FORMAT:
FLT-
EXAMPLE:
FLT-932A
(4 to 8 numerics or alpha)
ERROR MESSAGE:
FLT INVALID FORMAT, SHOULD BE FLT-XXXXXXXX
NOTE :
1)
In the Example the stored flight number will be changed to 932A. The FLTfacility permits customers to amend the screen loaded flight number or extend it
from 4 to 8 characters.
2)
Page 59 of 168
Section 11 Keywords
KEYWORD : FMA-
FMA-
PURPOSE:
FORMAT:
FMA-
EXAMPLE:
FMA-840
(3 numerics)
ERROR MESSAGE:
FMA MUST BE NUMERIC, 270 - 900
NOTE :
1)
If a fixed Mach number is already in the stored records, this entry will override it.
If there is no fixed Mach number stored, this input will override any cruise details
normally in use *(see CRZ). When a fixed Mach number is loaded it cannot be
overridden by a CRZ- input.
2)
The loaded Mach number can be removed for the requested Flight Plan by input
of FMA-000; the Flight Plan will then be based on the screen loaded CRZ
selection or on any CRZ- input which will now override the loaded CRZ figure. In
the Example FMA-840 gives a fixed Mach number of .84. FMA-000 unfixes the
loaded Mach number.
3)
Page 60 of 168
Section 11 Keywords
KEYWORD : FMT-
PURPOSE:
FORMAT:
FMT-
EXAMPLE:
FMT-SHP
FMT-CFP/WXS/ATC
ERROR MESSAGES:
RFP-ONLY THREE FMT LINES ALLOWED
RFP-INVALID FMT LINE
RFP-NO OVERRIDE IDENTIFIER FOUND ON FMT LINE
RFP-INVALID IDENTIFIER FOUND ON FMT LINE
NOTE :
1)
This Keyword offers the customer the facility of having the calculated Flight Plan
repeated in optional format versions.
In the Examples:
FMT-SHP will produce the short plan format of a calculated
Flight Plan.
FMT-CFP/WXS/ATC will produce the segment of the upper air weather
display, with the ATC plan
Input Examples:
2)
QIFPMXS
ABCDEFG251630
RFP
A6YCW
FMT-SHP
- Destination address
- Origin address DTG
- RFP request
- Flight plan reference
- Format specification
Use of FMT-ATC will produce a separate printout of the ATC plan dispatched to
address specified on the original plan or to an override address when Keyword
MAD- is used.
Page 61 of 168
Section 11 Keywords
KEYWORD : FXH-
PURPOSE:
FORMAT:
EXAMPLE:
FXH-
FXH-260/MONDO/330/SPR/370/LAGEN
or
FXH-TDP/290/MEN/000/TBO/330/KORNO
or
FXH-TDP/310/N41W170/390
ERROR MESSAGES:
FXH
FXH
FXH
FXH
FXH
FXH
FXH
NOTE :
1)
This Keyword affords the user the facility to define a height/FL profile by
waypoint name.
2)
3)
In the Example:
i)
FXH-260/MONDO/330/SPR/370/LAGEN/000
Page 62 of 168
Section 11 Keywords
KEYWORD : FXH(Continued)
iii)
FAL- keyword may be used, but this will only limit the flight level in the optimum
segment of the Flight Plan.
iv)
FAL- keyword may be used, but this will only limit the flight level in the optimum
segment of the Flight Plan.
v)
vi)
Metric levels can be used on FXH inputs and these will adhere to cruise table
indicators
.
4)
In the Example:
i)
FXH-TDP/310/N41W170/390
From waypoint TDP to LAT/LONG position N41W170 FL310 will
be flown and from N41W170 up to TOD(top of descent) FL390 will be flown.
ii)
The screen stored data will be shown in the parameter file as per the following Example.
QLLC Customers will be able to view this and request that the data be stored if required.
12JUL98 11:12
SITA FLIGHT PLANNING FLIGHT PARAMETERS
------------------------------------ VIEW ------------------------------------AIRLINE FLIGHT NO ORIGIN DESTINATION VERSION INITIAL
XS
AB99
TLS
IST
01
KGS
------------------------------------------------------------------------------SIX FIXED ALTITUDES:~~~~~~~~~~~~~~~~~~~
FIXED-ALT TO WAYPOINT
01
02
03
04
05
06
210
250
350
000
000
000
FIXD
UNITS
GEN
SPL
Page 63 of 168
Section 11 Keywords
KEYWORD: FXM
FXM
PURPOSE:
FORMAT:
FXM
EXAMPLE:
FXM-GOMUP/800/PRAWN
or
FXM-TDP/800
or
FXM-N56W020/820/N56W050
ERROR MESSAGES:
FXM SPEED (V) INVALID, MUST BE 000 OR 500-900
FXM-WAYPOINT (V) MUST BE BETWEEN 1 AND 7 CHARACTERS LONG
FXM YOU CANNOT USE TOD OR TOC OR FIR AS FXM WAYPTS
FXM TOO LONG, ONLY 6 PAIRS ALLOWED
The following two error messages are currently set to Abend and the failure message be sent
directly to the customer (this is under review as it should work the same as FXH- i.e. front-end).
FXM WAYPOINT (V) NOT FOUND ON ROUTE (V), OR NON-COMPULSORY
FXM WAYPOINT (V) NOT ENTERED IN ROUTE SEQUENCE ORDER
NOTES:
1) This keyword affords the user the facility to define speed (constant mach or LRC) segment(s)
or portions within a flight plan profiled by waypoint name, regardless of default cruise
speed/mode.
2) The speed specified is to be calculated as a fixed speed and is to be calculated in the same
way as FMA-; 000 is a request for long range cruise (LRC).
CASES:
i) FXM-GOMUP/800/PRAWN
Page 64 of 168
Section 11 Keywords
A fixed speed of .80 mach is requested between waypoints GOMUP and PRAWN possibly to meet a
NAT TRACK or OCEANIC requirement.
ii) FXM-TDP/800
A fixed speed of .80 mach is requested from waypoint TDP to destination.
iii) FXM-N56W020/820/N56W050
A fixed speed of .82 mach is requested between the coordinates shown, note format used.
iv) FXM-000/DOGAL/800/DOTTY/000
A speed of LRC is requested up to waypoint DOGAL, a fixed speed of .80 mach between DOGAL
and DOTTY and then LRC to destination.
CONDITIONS:
a) FXM- is only valid for jet aircraft (front-end validation still to be set).
b) FAL-, CAL-, FXH-, PRF-, IAS- keywords all have priority over FXM- input
c) All weight and height summaries are calculated at primary cruise mode / speed.
d) FXM- is compatible with RCR-/DPP- flight plans on the final leg.
e) RRG- requires VIA-WPT/----- to mirror FXM- waypoints.
Page 65 of 168
Section 11 Keywords
KEYWORD : HDA-
PURPOSE:
FORMAT:
HDA-
EXAMPLE:
ERROR MESSAGES:
HDA HEIGHT MUST BE IN RANGE 000-490, MULTIPLE OF 5
FORMAT IS HHH OR HHH/TTT
HDA TIME MUST BE IN RANGE 010 AND 120 MINS
FORMAT IS HHH OR HHH/TTT
NOTE :
1)
This allows for flexible calculation of Holding fuel at a particular height and/or
time, providing appropriate hold data has been previously loaded into the SITA
type performance files.
2)
A holding time must always be supplied. If input holding height is 999 then the
best holding level will be selected by the program.
3)
4)
The time parameter must always be 3 digits; if necessary add leading zeroes.
i.e. for 25 mins, input 025.
Page 66 of 168
Section 11 Keywords
KEYWORD : HDB-
PURPOSE:
FORMAT:
HDB-
EXAMPLE:
ERROR MESSAGES:
HDB HEIGHT MUST BE IN RANGE 000-490, MULTIPLE OF 5
FORMAT IS HHH OR HHH/TTT
HDB TIME MUST BE IN RANGE 010 AND 120 MINS
FORMAT IS HHH OR HHH/TTT
HDB ONLY REQUIRED FOR RECLEAR FLIGHTS
NOTE :
1)
This allows for flexible calculation of Holding fuel at a particular height and/or
time, providing appropriate hold data has been previously loaded into the SITA
type performance files.
2)
3)
4)
The time parameter must always be 3 digits; if necessary add leading zeroes.
i.e. for 25 mins, input 025.
Page 67 of 168
Section 11 Keywords
KEYWORD : HDD-
PURPOSE:
FORMAT:
HDD-
EXAMPLE:
ERROR MESSAGES:
HDD HEIGHT MUST BE IN RANGE 000-490, MULTIPLE OF 5
FORMAT IS HHH OR HHH/TTT
HDD TIME MUST BE IN RANGE 005 AND 180 MINS
FORMAT IS HHH OR HHH/TTT
NOTE :
1)
This allows for flexible calculation of Holding fuel at a particular height and/or
time, providing appropriate hold data has been previously loaded into the SITA
type performance files.
2)
A holding time must always be supplied, (if input holding height is 999 then the
best holding level will be selected by the program).
Page 68 of 168
Section 11 Keywords
KEYWORD : HDR-
PURPOSE:
FORMAT:
HDR-
EXAMPLE:
ERROR MESSAGES:
HDR HEIGHT MUST BE IN RANGE 000-490, MULTIPLE OF 5
FORMAT IS HHH OR HHH/TTT
HDR TIME MUST BE IN RANGE 010 AND 120 MINS
FORMAT IS HHH OR HHH/TTT
NOTE :
1)
This allows for flexible calculation of Holding fuel at a particular height and/or
time, providing appropriate hold data has been previously loaded into the SITA
type performance files.
2)
3)
4)
The time parameter must always be 3 digits; if necessary add leading zeroes.
i.e. for 25 mins, input 025.
Page 69 of 168
Section 11 Keywords
KEYWORD : HLD-
PURPOSE
FORMAT:
HLD-5500/45
(see notes)
ERROR MESSAGES:
HLD FUEL MUST BE UP TO 5 DIGITS, NOT GREATER THAN 50000
FORMAT IS FFFFF OR FFFFF/TTT
HLD TIME MUST BE FROM 5 TO 180 MINS
FORMAT IS FFFFF OR FFFFF/TTT
WHEN FUEL IS ZERO, TIME MUST ALSO BE ZERO
NOTE :
1)
The Example input of 5500/45 is for 5500 units of fuel (Kgs or Lbs) and a related
holding time of 45 mins. The time input after the slash is optional. Leading
zeroes are not required. If an input of HLD-0 is entered then no Holding/Final
Reserve fuel will appear on the Flight Plan.
2)
If the time value is omitted, then the specified time field will default to the
standard value by the individual customer. (normally 30 mins)
Page 70 of 168
Section 11 Keywords
KEYWORD : HNL-
PURPOSE:
FORMAT:
HNL-
EXAMPLE:
1)
2)
HNL-A
HNL-W N28/W170 N33/E180 N35/E170 N36/E160
ERROR MESSAGES:
HNL
HNL
HNL
HNL
HNL
HNL
HNL
HNL
HNL
HNL
HNL
HNL
HNL
HNL
HNL
HNL
NOTE :
This Keyword must be used in conjunction with Keyword ECT - which specifies
ENTRY and EXIT routings to be used with the defined Oceanic segment.
(ENTRY specified first, EXIT second.)
2)
The Flight levels will be selected automatically to conform to 2000' sep. For use
outside the OTS, format 2, (using prefix W=Westbound, E=Eastbound) will
amend the selection to standard ICAO semicircular separation.
Page 71 of 168
Section 11 Keywords
KEYWORD : HNL-
(continued)
3)
Example 1 defines the desired daily track. Use of OTS entry/exit points is not
required; these points are the terminal points on the ENTRY/EXIT routings.
4)
The published tracks are loaded daily into the SITA database. For hard copy
printout of loaded tracks (see transaction TRK).
5)
These automatic options require suitable Entry/Exit routings (from origin to track
entry point and from track entry point to the destination to be stored in the
Navigation Data base.
Page 72 of 168
Section 11 Keywords
KEYWORD : HOC-
HOC-
PURPOSE:
FORMAT:
HOC-
EXAMPLE:
HOC-17345.99
ERROR MESSAGE:
HOC MUST BE IN FORMAT 99999.9, CANNOT BE 0
HOC CRZ 1 REQUIRED WITH THIS KEYWORD
NOTE :
1)
2)
The cost used is the summation of those operating costs which are time
dependant but exclude fuel cost.
3)
Page 73 of 168
Section 11 Keywords
KEYWORD : HRA-
PURPOSE:
FORMAT:
HRA-
EXAMPLE:
1)
2)
ERROR MESSAGES:
HRA MUST BE IN FORMAT 9.9, BETWEEN 0.5 AND 1.5
NOTE :
1)
Use of this Keyword is only effective in cases where HDD and/or HDA is
specified by Keyword or by default.
2)
This provides a method of adjusting holding fuel flow figures kept in the
Performance database.
3)
The value on file is multiplied by the input correction factor to obtain a new fuel
flow, if performing a racetrack holding pattern.
4)
See also HTA for ISA temperature correction factor. If HRA and HTA are
entered, then HRA is applied to the fuel flow first, followed by HTA.
Page 74 of 168
Section 11 Keywords
KEYWORD : HTA-
PURPOSE:
FORMAT:
HTA-
EXAMPLE:
1)
ERROR MESSAGES:
HTA MUST BE IN FORMAT 9.999, 0.001 TO 1.000
NOTE :
1)
Use of the Keyword is only effective in cases where HDD and/or HDA is specified
by Keyword or by default.
2)
This provides a method of adjusting holding fuel flow figures kept in the
Performance database.
3)
The value on file is increased by the appropriate input percentage for each 5
degrees that the air temperature is above ISA standard at the place and height
selected for an aircraft hold.
4)
5)
See also HRA for racetrack adjustment factor. If HRA and HTA are entered, then
HRA is applied to the fuel flow first, followed by HTA.
Page 75 of 168
Section 11 Keywords
KEYWORD : IAS-
PURPOSE:
FORMAT:
IAS-
EXAMPLE:
IAS-310/F270
ERROR MESSAGES:
IAS FORMAT MUST BE 999/F999, 180-500 & F010-F490
NOTE :
1)
This is a dual parameter keyword, the first three numbers provide the value of KIAS to be
used for the flight plan cruise speed. The second group, preceded by letter 'F', gives the
flight level up to which the value of KIAS is to be used. In the above example a cruise
speed of 310KIAS is to be used for all levels up to and including FL 270.
2)
Above the specified level, the default cruise mode and speed will be used.
3)
The program converts the KIAS to a Mach No., therefore the priorities and logic applicable
to FMA- are similarly used in the cruise calculation for levels up to and including the level
specified.
Page 76 of 168
Section 11 Keywords
KEYWORD : LTT-
PURPOSE:
FORMAT:
LTT-
EXAMPLE:
LTT-
ERROR MESSAGE:
LTT MAY NOT BE ENTERED WITH NAT
NOTE :
1)
The Least Time Track will be calculated using Forecast winds as defined by the
ETD/ETA used.
Page 77 of 168
Section 11 Keywords
KEYWORD : M-
PURPOSE:
FORMAT:
M-
EXAMPLE:
NOTE :
1)
The message lines normally print out at the top of the Flight Plan, and contain a
maximum of 64 characters per line. This is format related and can be printed in
the body of the Flight Plan.
2)
3)
3 lines are accessible by Keyword input. The fourth line is stored on request
from the customer airline and can only be changed or deleted by the SITA
operator on written instructions from the customer.
4)
All four lines are available for fixed/statistical weather analytical plans.
5)
M- should always be used on a separate line within the CFP input format.
Page 78 of 168
Section 11 Keywords
KEYWORD : MAD-
PURPOSE:
FORMAT:
MAD-
EXAMPLE:
ERROR MESSAGES:
MAD MAXIMUM LINE LENGTH OF 48 EXCEEDED
Up to 6 addresses of 7 alphas may be entered
MAD ADDRESS (V) IS INVALID
for a Cicsprint address, a slash must be in position 1
last two characters must be blank
characters 2 - 6 must be alphanumeric
please check your input
MAD MUST BE SPECIFIED FOR A 9999 FLIGHT
NOTE :
1)
The use of the override facility for addresses will remove all stored addresses. In
the Example the addresses are separated by a blank space; the plans will go to
the addresses specified, overriding any previously stored address.
2)
MAD- should always be used on a separate line within the CFP input format.
Page 79 of 168
Section 11 Keywords
KEYWORD :
MFU-
PURPOSE:
FORMAT:
MFU-999999
(Entered as weight value in units, 1-6 digits, no leading zeros are
necessary.)
ERROR MESSAGES
MFU MUST BE NUMERIC,MAXIMUM 6 DIGITS
MFU MUST NOT EXCEED MAX TANK WEIGHT:
MFU-ENTRY OF UNLIMITED MAXIMUM FUEL IS INVALID
NOTE :
1)
2)
If the calculated fuel for the requested ZFWT and other CFP inputs
is less than the MFU amount specified by this keyword then the
calculated amount will be shown on the CFP, MFU only acts a
limiting value not as a 'Minimum Fuel' requirement.)
3)
Page 80 of 168
Section 11 Keywords
KEYWORD : MOA-
PURPOSE:
FORMAT:
MOA-
EXAMPLE:
ERROR MESSAGES:
MOA MUST BE NUMERIC, MAXIMUM 6 DIGITS
MOA EXCEEDS MAX TANK LIMIT OF (V) FOR (V)
NOTE :
The Keyword will allow the specification of a Minimum Fuel value overhead the
Alternate.
Page 81 of 168
Section 11 Keywords
KEYWORD : MOD-
PURPOSE:
FORMAT:
MOD-
EXAMPLE:
ERROR MESSAGES:
MOD MUST BE NUMERIC, MAXIMUM 6 DIGITS
MOD EXCEEDS MAX TANK LIMIT OF (V) FOR (V)
NOTE :
1)
The Keyword will allow the specification of a Minimum Fuel value overhead the
Destination.
2)
8) Contingency fuel is assumed to have been burned off unless Switch 21 is sent ON in
Air Policy File page 10.
9) Destination manoeuvring fuel follows the rule set for it in the Air Policy file. If set to
be included in burn off then it is burnt off prior to the MOD check. If set to be
included in the landing weight then it is part of the fuel over destination.
Page 82 of 168
Section 11 Keywords
KEYWORD : MTF-
PURPOSE:
FORMAT:
MTF-
EXAMPLE:
MTF-17500
ERROR MESSAGES:
MTF MUST BE NUMERIC, MAXIMUM 6 DIGITS
MTF EXCEEDS TKW OF (V) FOR (V)
MTF EXCEEDS MAX TANK LIMIT OF (V) FOR (V)
NOTE :
A given quantity of fuel is already in tanks and a Flight Plan is required based on
this existing parameter.
2)
3)
Page 83 of 168
Section 11 Keywords
KEYWORD : MVD-
PURPOSE:
FORMAT:
MVD-
EXAMPLE:
ERROR MESSAGES:
MVD MUST BE NUMERIC, MAXIMUM 3 DIGITS
MVD ONLY ONE OF MVD AND MVF ALLOWED
NOTE :
1)
2)
An entered MVD- calculates fuel based on that distance and shows a time based
on 3NM/minute unless a specific time has been entered by Keyword MVT-.
3)
4)
Page 84 of 168
Section 11 Keywords
KEYWORD : MVF-
PURPOSE:
FORMAT:
MVF-
EXAMPLE:
MVF-1200
ERROR MESSAGES:
MVF MUST BE NUMERIC, 3-5 DIGITS
MVF MUST NOT BE GREATER THAN 50000
NOTE :
1)
The customer can choose his own Destination Manoeuvre Fuel instead of the
system calculation. Also see MVT-. The time printed out is a hardwired factor
dependent on customers specification, unless overridden by use of Keyword
MVT-.
2)
3)
Page 85 of 168
Section 11 Keywords
KEYWORD : MVT-
PURPOSE:
FORMAT:
MVT-
EXAMPLE:
MVT-10
(2 numerics)
ERROR MESSAGES:
MVT MUST BE 2 NUMERICS
MVT ALSO REQUIRES THE ENTRY OF MVD OR MVF
NOTE :
1)
This facility can only be used if MVD- or MVF- has been used.
2)
3)
Page 86 of 168
Section 11 Keywords
KEYWORD : MZF-
PURPOSE:
FORMAT:
MZF-
EXAMPLE:
ERROR MESSAGES:
MZF MUST BE NUMERIC, MAX 6 DIGITS & ABOVE 0
MZF MUST BE (V) TO (V) FOR (V)
NOTE :
1)
The Flight Planning System will allow a new Maximum Zero Fuel Weight to be
specified by the customer, within a built in tolerance factor of 10 percent less or
more than that currently held on file for this airframe.
Page 87 of 168
Section 11 Keywords
KEYWORD : NAT-
PURPOSE:
FORMAT:
1)
2)
3)
4)
NATNAT-A
NAT-AUTO
NAT-AUTP
EXAMPLE:
1)
2)
ERROR MESSAGES:
NAT
NAT
NAT
NAT
NAT
NAT
NAT
NAT
NAT
NAT
NAT
NAT
NAT
NAT
NAT
NAT
NAT
NAT
NAT
NAT
(continued)
Page 88 of 168
Section 11 Keywords
KEYWORD : NAT-
(continued)
NOTE :
1)
This Keyword must be used in conjunction with Keyword ECT-, except when
using NAT-AUTO or AUTP which specifies ENTRY and EXIT routings to be used
with the defined Oceanic segment. (ENTRY specified first, EXIT second).
2)
The Flight levels will be selected automatically to conform to North Atlantic OTS
vertical separation requirements. For use outside the OTS, format 2 (using prefix
W=Westbound, E=Eastbound) will amend the selection to standard ICAO
semicircular separation.
3)
Examples 1 & 2 define a desired NAT track. Use of OTS entry/exit points is not
required; these points are the terminal points on the ENTRY/EXIT routings.
4)
5)
Example 3 is used when a daily published North Atlantic Track in the Organised
Track System is required. Input should be NAT-A for Track Alpha NAT-D for
Track Delta etc.
The published tracks are loaded daily into the SITA data base.
6)
7)
Format 5 specifying AUTP has the same function as AUTO, plus the plan is
produced utilizing the best NAT track, EXIT and ENTRY.
Page 89 of 168
Section 11 Keywords
KEYWORD : NM1-
PURPOSE:
FORMAT:
NM1NM2-
EXAMPLE:
NM1-Lucy Hitchins
NM2-George Cromwell
ERROR MESSAGES:
NM1-NAME MUST BE ENTERED, MAXIMUM OF 24 CHARACTERS
NOTE :
1)
This Keyword is Format related only. You must advise QIFFQXS where you want
the information displayed before it will print.
2)
Page 90 of 168
Section 11 Keywords
KEYWORD: NTMPURPOSE:
FORMAT:
NTM-
EXAMPLES:
1)
NTMApplies default generic filtering. I.e. All valid NOTAM data will be
printed based on origin, destination, alternates and narrow route corridor.
2)
NTM-Q
Applies customer-specific filtering, using pre-stored NOTAM filters.
Further information can be obtained from the Flight Briefing Helpdesk.
3)
NTM-EGLL/LGW/EGSS/EGGW/MAN/EGNJ
Allows additional airports to be requested.
i. Up to 10 airports can be specified.
ii. A mixture of ICAO and IATA codes may be used.
iii. Applies default generic filtering, as in 1) above.
4)
NTM-Q/EGLL/LGW/EGSS/EGGW/MAN/EGNJ
Allows additional airports to be requested.
i. Up to 10 airports can be specified.
ii. A mixture of ICAO and IATA codes may be used.
iii. Applies customer-specific filtering, as in 2) above.
Page 91 of 168
Section 11 Keywords
ERROR MESSAGES:
NTM- CHARGEABLE KEYWORD NOT ALLOWED
Additional information:
This keyword function produces a separate request direct to the NOTAM production
machine (QIFNMXS), and the actual receipt of the data will follow shortly after the flight
plan.
Only Route Specific NOTAM data is received, based on the route used in the CFP
request.
Normal Alternates, Reclear Alternates (if applicable) and ETOPS Alternates (if
applicable) will be included.
Validity times will be based on ONE hour before ETD and ONE hour after ETA.
**Important note: NTM-Q can only be used after customer specific filters have been
loaded onto the NOTAM system. Any attempt to use NTM-Q prior to this will result
in a delay in the processing of NOTAM bulletin data.
Page 92 of 168
Section 11 Keywords
KEYWORD : OAL-
PURPOSE:
Enables a fixed fuel (and time) override for the final Destination to
Alternate segment.
FORMAT:
OAL-
EXAMPLE:
OAL-3700
(Must be Max 5 numerics Kgs/Lbs)
OAL-3700/45 (Includes override time of 45 mins)
ERROR MESSAGES:
OAL FUEL MUST BE UP TO 5 DIGITS, NOT GREATER THAN 50000
FORMAT IS FFFFF or FFFFF/TTT
OAL TIME MUST BE FROM 10 AND 120 MINS
FORMAT IS FFFFF OR FFFFF/TTT
NOTE :
1)
This Keyword function produces a fixed, rather than a calculated value of fuel to
the Alternate from the final Destination.
2)
No check is made that the OAL input value is greater than the fuel to Alternate
calculated by the SITA Flight Planning System.
3)
A value of OAL-0 suppresses any Alternate fuel printing on the Flight Plan.
4)
5)
The plan will print zero for Flight Level, Mach number, Wind Component. It will
change the Alternate time to zero unless a new time has been entered.
6)
Page 93 of 168
Section 11 Keywords
KEYWORD : OAR-
PURPOSE:
Enables a fixed fuel (and time) override for the Initial Destination
to Alternate segment in the Reclear (or Refile) case.
FORMAT:
OAR-
EXAMPLE:
ERROR MESSAGES:
OAR FUEL MUST BE UP TO 5 DIGITS, NOT GREATER THAN 50000
FORMAT IS FFFFF OR FFFFF/TTT
OAR TIME MUST BE FROM 10 TO 120 MINS
FORMAT IS FFFFF OR FFFFF/TTT
NOTE :
1)
This Keyword function produces a fixed rather than a calculated value of fuel to
the Reclear Alternate from the Initial (or Reclear) Airport.
2)
No check is made that the OAR input value is greater than the fuel to Alternate
calculated by the SITA Flight Planning System.
3)
A value of OAR-0 suppresses any Alternate Fuel printing on the Flight Plan.
4)
5)
The plan will print zero for Flight Level, Mach number, and wind component. It
will change the Alternate time to zero unless a new time has been entered.
6)
Page 94 of 168
Section 11 Keywords
KEYWORD : OFC-
PURPOSE:
To calculate the overflight charges for the route flown and to initiate
the calculation of least cost route selection.
FORMAT:
OFC-
EXAMPLE:
1)
2)
OFCOFC-F
ERROR MESSAGES:
CFP- OFC- MUST BE EITHER F OR BLANK
NOTE :
1)
2)
OFC-F will produce a full print of individual charges in the currency stated in the rules
- these are converted into USD. The exchange rate is included to allow recalculation
using your own rates.
3)
4)
5)
OFC keyword causes the Least Cost route selection to analyse the overflight
charges on available routes for a city pair. It then forms part of the costs used to
select the least cost route. (Fuel and Time cost being the others).
Page 95 of 168
Section 11 Keywords
KEYWORD : OWE-
OWE-
PURPOSE:
FORMAT:
OWE-
EXAMPLE:
ERROR MESSAGES:
OWE MUST BE NUMERIC, MAX 6 DIGITS & ABOVE 0
OWE GREATER THAN ZFWT OF (V)
OWE MUST BE (V) TO (V) FOR (V)
NOTE :
1)
This input is used in conjunction with either PLD- to calculate a zero fuel weight,
or with ZFW to calculate a required payload.
2)
If OWE is omitted from the CFP request, then the value stored in the aircraft
attribute file will be used.
3)
In the Example an A/C empty weight of 168500 is requested. Do not specify LBS
or KGS.
4)
5)
The sum of OWE and PLD cannot be less than stored OWE.
Page 96 of 168
Section 11 Keywords
KEYWORD : PAC-
PAC-
PURPOSE:
FORMAT:
PAC-
EXAMPLE:
1)
2)
3)
4)
5)
PAC-AUTO
PAC-AUTP
PAC-E
PAC-E S1O/E100
PAC-S10/E105
ERROR MESSAGE:
PAC
PAC
PAC
PAC
PAC
PAC
PAC
PAC
PAC
PAC
PAC
PAC
PAC
PAC
PAC
PAC
NOTE :
1)
AUTO is used to generate a Track Summary showing order of best track from
published Pacots message.
2)
AUTP has same function as AUTO, output is Track Summary and Flight Plan on
best track.
3)
Page 97 of 168
Section 11 Keywords
KEYWORD : PIC-
PURPOSE:
FORMAT:
PIC-
EXAMPLE:
1)
2)
PIC-IN/1/QIFPTXS
PIC-IS/QIFPTXS BRUEP7X
ERROR MESSAGES:
PIC MUST ENTER AT LEAST ONE ADDRESS
NOTE :
1)
This Keyword permits the User to send the ATC plan as a separate message. It
may also be sent to five additional addresses.
2)
Format of PIC- code must be the same as the ATC- input on the Flight Plan
request.
3)
4)
This is for sending to SITA addresses only and can be used with Type B, GraFlite and QLLC.
Page 98 of 168
Section 11 Keywords
KEYWORD : PLD-
PURPOSE:
FORMAT:
PLD-
EXAMPLE:
PLD-23160
(1 to 6 numerics, leading zeros not required)
ERROR MESSAGES:
PLD
PLD
PLD
PLD
NOTE :
1)
This input must be used in conjunction with an OWE entry, the product of which
is the ZFW.
2)
If both PLD- and OWE- are used as entries, then the ZFW field on the CFP
request should be left blank.
3)
Page 99 of 168
Section 11 Keywords
KEYWORD : PRF-
PURPOSE:
Provision of fixed height Flight Plan profile by waypoint name overriding the
normal flight level separation rules for a particular route or route segment.
FORMAT:
PRF-
EXAMPLE:
PRF-260/MONDO/330/SPR/370/LAGEN
or
PRF-TDP/290/MEN/000/TBO/330/KORNO
ERROR MESSAGES:
PRF
PRF
PRF
PRF
PRF
PRF
PRF
NOTE :
1)
2)
3)
In the Example:
i)
PRF-260/MONDO/330/SPR/370/LAGEN/000
Section 11 Keywords
KEYWORD : PRF(Continued)
ii)
iii)
iv)
4)
In the example:
i)
PRF-TDP/310/N41W170/390
Section 11 Keywords
KEYWORD : PRI-
PURPOSE:
FORMAT:
PRI-
EXAMPLE:
PRI-QD
ERROR MESSAGES:
PRI (V) INVALID, MUST BE 2 CHARS, QU, QN or QD
NOTE :
1)
Section 11 Keywords
KEYWORD : PSW-
PURPOSE:
FORMAT:
PSW-XX ZZZZ
Where XX is the Airline ID and ZZZZ is the customer
defined password.
EXAMPLE:
1)
TFR
PSW-XS X01A - where airline wishes to use security processing.
2)
ACD
PSW-XS - no security processing required
*(Example 1) XS = Airline ID X01A = Password
ERROR MESSAGES:
SECURITY FAILURE - MORE THAN ONE MAD LINE INPUT
SECURITY FAILURE - MORE THAN ONE PSW LINE INPUT
SECURITY FAILURE - PSW LINE NOT ENTERED
SECURITY FAILURE - INVALID AIRLINE ID IN PSW LINE
SECURITY FAILURE - NO PASSWORD ENTERED IN PSW LINE
SECURITY FAILURE - INVALID PASSWORD ENTERED IN PSW LINE
SECURITY FAILURE - OUTPUT ADDRESS(ES) INVALID
NOTE :
1)
2)
An option is provided for those airlines who do not wish to use the security facility
(Example 2).
3)
The selected applications protected by password are: ACD, PRM, TFR, TFRRPT.
Section 11 Keywords
KEYWORD : RA2-
PURPOSE:
FORMAT:
RA2-
EXAMPLE:
1)
2)
3)
RA2-EGKK
RA2-EGKK/P or /S
RA2-EGKK/P/12345 or/S/12345
ERROR MESSAGES:
RA2 MUST BE 3 CHAR IATA OR 4 CHAR ICAO CODE
RA2 ROUTE, IF ENTERED, MUST BE MAXIMUM OF 6 DIGITS
RA2 UNRECOGNISABLE INPUT FORMAT
RA2 INVALID FORMAT - USE XXX/9999 OR XXXX/9999
RA2 CANNOT BE ENTERED WITHOUT RCR KEYWORD
RA2 ALT CANNOT BE ENTERED RCR ALT NIFR
RA2 CAPPED HEIGHT MUST BE ABOVE (V) FOR (V)
RA2 2ND ALTN - (V) NOT VALID FOR DEST - (V)
NOTE :
1)
Keyword input of RA2- will produce the normal summary of Flight Level,
Distance, Mach No, Wind Component, Fuel burn off, and Time to a second
selected Alternate from the Reclear Airport using the distance stored in the
individual airline alternate records.
2)
In Example 1) EGKK is selected as the second Alternate. The distance and any
CAP altitude in the Alternate file will be used. In Example 2) the second alternate
is EGKK and with /P a full print of the shortest distance route between the
destination and EGKK or /S a summary route description will be printed at the
bottom of the Flight Plan. In Example 3) as for 2 except that the required route
number from destination to alternate is specified.
3)
/P or /S are only available if there is a route or routes built between the reclear
destination and the alternate airport.
Section 11 Keywords
KEYWORD : RA3-
PURPOSE:
FORMAT:
RA3-
EXAMPLE:
1)
2)
3)
RA3-EGLL
RA3-EGLL/P or /S
RA3-EGLL/P/12345 or /S/12345
ERROR MESSAGES:
RA3 MUST BE 3 CHAR IATA OR 4 CHAR ICAO CODE
RA3 ROUTE, IF ENTERED, MUST BE MAXIMUM OF 6 DIGITS
RA3 UNRECOGNISABLE INPUT FORMAT
RA3 INVALID FORMAT - USE XXX/9999 OR XXXX/9999
RA3 CANNOT BE ENTERED WITHOUT RCR AND RA2 KEYWORDS
RA3 ALT CANNOT BE ENTERED RCR ALT NIFR
RA3 CAPPED HEIGHT MUST BE ABOVE (V) FOR (V)
RA3 3RD ALTN - (V) NOT VALID FOR RECLEAR DEST - (V)
NOTE :
1)
Keyword input of RA3- will produce the normal summary of Flight Level,
Distance, Mach No, Wind Component, Fuel burn off, and Time to a third selected
Alternate from the Reclear Airport, using the distance stored in the individual
airline alternate records.
2)
In Example 1) EGLL is selected as the third Alternate. The distance and any CAP
altitude in the Alternate file will be used. In Example 2) the second alternate is
EGLL and with /P a full print of the shortest distance route between the
destination and EGLL or /S a summary route description will be printed at the
bottom of the Flight Plan. In Example 3) as for 2 except that the required route
number from destination to alternate is specified.
3)
Section 11 Keywords
KEYWORD : RCA-
PURPOSE:
FORMAT:
RCA-
EXAMPLE:
RCA-240
(3 numerics)
ERROR MESSAGES:
RCA MUST BE NUMERIC, MAX 3 DIGITS, 010-490
RCA CAPPED HEIGHT MUST BE ABOVE (V) FOR (V)
NOTE :
1)
This facility permits the capping of a flight level below that which would normally
be calculated by the Flight Plan.
2)
The Flight Plan program will always elect to fly at optimum levels, unless this cap
height is requested.
3)
In the Example the flight level between Initial or Reclear Destination and the
selected alternate is capped at FL240.
4)
Section 11 Keywords
KEYWORD : RCR-
PURPOSE:
FORMAT:
RCR-
EXAMPLE:
1)
2)
3)
4)
5)
RCR-GCLP/LPFR/PLATY
RCR-GCLP/LPFR/PLATY/123400
RCR-GCLP/LPFR/PLATY/P or/S
RCR-GCLP/LPFR/PLATY/P/123456 or /S/123456
RCR-GCLP/LPFR/AUTO
ERROR MESSAGES:
RCR
RC1
RCR
RCR
RCR
RCR
RCR
RCR
RCR
RCR
RCR
RCR
NOTE :
1)
This is a multi parameter Keyword for specifying reclear details. The format is as
follows:
The first parameter is the Initial Airport in ICAO/IATA code.
The second parameter is the Reclear Alternate ICAO/IATA code, optionally
followed by digit number as necessary. This will override loaded alternate
distance if required. (see Example 3).
Section 11 Keywords
KEYWORD : RCR-
(continued)
The third parameter is the reclear fix point as a max five alpha/numeric character
field which must match exactly the identification of the waypoint specified as the
reclear point in the route description (e.g. reclear point 1800S must be entered as
1800S and not S1800). It must not be present if an ocean reclear is to occur
(see definition for Keyword RC1-).
The fourth parameter is maximum landing weight at the Initial Airport: omit if
unrestricted; add if specific landing weight restriction applies. Landing weight is
expressed in units. Add if overweight landing (for Flight Planning purposes) is
required.
* As reclear fixes are specific to a nominated route then an EXT input must also be
present in the CFP request.
EXAMPLE:
RCR-GCLP/LPFR/PLATY/123400/P
(gives Init. Apt.- GCLP Alternate - LPFR)
Reclearfix - PLATY
RLW-123400/P
Plan of shortest distance route between GCLP and LPFR.
2)
If a print out of the route to the alternate is required then use Example 4 or 5 as
required.
3)
RCR-GCLP/LPFR/AUTO
RCR-GCVV/GMMN/AUTO
RCR-GCTS/GMAD/AUTO
RCR-LPFR/LEMD/AUTO
RCR-LPPT/LPPO/AUTO
Section 11 Keywords
KEYWORD : RC1-
PURPOSE:
FORMAT:
RC1-
EXAMPLE:
RCR-EGLL/EGKK
RC1-50.00N/020.00W/001374
ERROR MESSAGES:
RC1
RC1
RC1
RC1
NOTE :
1)
2)
3)
Run a non-reclear Random FLT PLN over the sector, to enable a Reclear point
to be determined.
4)
Section 11 Keywords
KEYWORD : RFX-
PURPOSE:
FORMAT:
RFX-
EXAMPLE:
1)
2)
RFX-1200
RFX-0
(1-5 numerics)
ERROR MESSAGES:
RFX MAY ONLY ENTER ONE OF RFX, RVF, RVT OR RVN
RFX MUST BE NUMERIC, MAXIMUM 5 DIGITS
RFX EXCEEDS MAX TANKS WT OF (V) FOR (V)
NOTE :
1)
This facility can only be used on non reclear flights, the Keyword input
determines a fixed reserve fuel. Example 1) gives a fixed fuel of 1200 KGS/LBS,
Example 2) gives Zero Contingency Fuel. The flight plan will fail If the calculated
time value for the required fuel value is greater than 3 hours.
2)
Section 11 Keywords
KEYWORD : RLW-
PURPOSE:
FORMAT:
EXAMPLE:
ERROR MESSAGES:
RLW
RLW
RLW
RLW
NOTE :
1)
Section 11 Keywords
KEYWORD :
PURPOSE:
RMN-
FORMAT:
EXAMPLE::
RMN-
ERROR MESSAGE:
RMN MUST BE NUMERIC,MAX 5 DIGITS & ABOVE 0
RMN CANNOT BE USED WITH RFX
RMN CANNOT BE USED WITH RVN
RMN CANNOT BE GREATER THAN MAXIMUM RESERVES
NOTE :
1) This fuel amount overrides any 'Minimum Reserves' loaded in the Air Policy file.
Section 11 Keywords
KEYWORD : RNY-
PURPOSE
To allow the ability to request a flight plan based upon one previously run and
starting at a specified waypoint.
FORMAT
RNY-
EXAMPLE
RNY-K25TV/0930/250000/055000/350
The format of the keyword must be as per the example above.
REF = Must be 5 alpha numeric and be a valid reference in the RFP file.
TIME = A valid time between 0000 and 2359
WEIGHT = Numeric max 6 (Weight of aircraft at start waypoint)
FUEL = Numeric max 6 (Fuel on board at start waypoint)
FL = Numeric 3 between 010 & 490
RTE is used to specify at which point the flight plan starts and which routing is to
be used to the destination. In the example above DVR is
the re-analysis point and then EXT-6625 is used to EGLL. The normal input
parameters for the RTE can be used.
DTE is a mandatory keyword. The date to input is the date of the time in the RNY
keyword and is required to ensure the correct weather is used in the re-analysis
flight plan.
Exceptions and the Rules
1.
2.
3.
4.
ERROR MESSAGES
CFP- RNY - MUST BE IN THE FORMAT RNY-REF/TIME/WEIGHT/FL
CFP- RNY - RTE MUST BE USED IF RNY REQUESTED
CFP- RNY - FLT PLAN IDENTIFIER NOT KNOWN OR OVER 24 HOURS OLD.
CFP- RNY - 1567 IS NOT A VALID TIME
CFP- RNY DTE MUST BE PRESENT WITH RNY
Section 11 Keywords
KEYWORD : RNY(Continued)
NOTE:
1. Certain keywords from the original request are not included in the RNY flight plan request.
Keywords to be excluded from all requests
AFT ATC BLK CBF CPN CRA CRP DMF
HDR HNL LTT NAT OAR PAC PIC
RFU RSF RSG RSN TAX TCL TDF
RVF NTM MTF EEP ETE MOD XTR
DMT
RA2
OFC
HDB
RC1
2. Additionally if the destination changes then the following keywords are also excluded :
Keywords to be excluded if destination changes
AL2 AL3 CPA CP2 CP3 HDA HDD
MVD MVF MVT OAL TXI
NTM
HLD
HRA
HTA
MOA
Section 11 Keywords
KEYWORD : RRG-
PURPOSE:
FORMAT:
CFPXX/9999/EGLL/EBBR/7474/999999
ETD-1000,ETA-1100,ALT-NOALT,MAD-ABCDEFG
RRG(Standard CFP input, with the addition of RRG).
EXAMPLE:
1)
VIA-DEP/MAX
VIA-WPT/LOGAN
VIA-WPT/WOD/EUR/EG
VIA-WPT/WOD/EUR/EG/D
VIA-WPT/WOD/EUR/EG/DB
VIA-SEG/WPT/AWY/WPT
VIA-NAT
VIA-NAT/A
VIA-ARR/MAX
VIA-ARR/CPT3G
EXC-WPT/LOGAN
EXC-WPT/WOD/EUR/EG
Section 11 Keywords
EXC-AWY/UM601
DTE-JAN/75
DTE-QTR1/75
Statistical weather for first quarter of the year. Options Quarters 1-4
and probability factors as above.
DTE-JANJUN
DTE-SUM
WDE-0
LVL-L
IGR
When running RRGs at flight plan request time it is also possible to request a Least Time Track
route across an ocean using the following entries
VIA-WPT/GOMUP
VIA-WPT/BREKI
VIA-LTT/GOMUP/BREKI
)
) all three entries together give LTT between points.
)
VIA-LTT by itself will produce an LTT for the oceanic area only. i.e. it is not
necessary to specify ocean entry and exit.
NB: RRG can only be used if this is set up for the airline. It is a chargeable
keyword. Please contact SITA Helpdesk for assistance if required.
Section 11 Keywords
KEYWORD : RSF-
PURPOSE:
FORMAT:
RSF-
EXAMPLE:
ERROR MESSAGE:
RSF MUST BE ALPHANUMERIC, MAX 10 CHARACTERS
NOTE :
1)
The route summary selected will be appended to the Flight Plan, thus giving a
summary of a route other than the Flight Plan route for comparative purposes.
2)
In the Example route (or EXIT) 2525 has been specified for comparison, and a
summary plan over this route will be appended to the main plan.
Section 11 Keywords
KEYWORD : RSG-
RSG-
PURPOSE:
FORMAT:
RSG-
EXAMPLE:
RSG-
NOTE :
1)
The output is a route summary showing fuel burn, elapsed time, air distance and
ZFW appended to the Flight Plan. The summary is for that stored route on the
sector with least track miles.
2)
If the Flight Plan has been calculated using the least distance route, the RSG
summary will be displayed as 'GC <route number> IS SAME AS EXPLICIT MAIN
PLAN ROUTE'.
Section 11 Keywords
KEYWORD : RSN-
PURPOSE:
FORMAT:
RSN-1
RSN-2 etc
NOTE :
1)
The summary will show Fuel burn/Elapsed time/Air Distance and ZFW for the
next best route.
2)
If only one route exists in the City Pair, then no summary will be calculated.
3)
If a fixed route has been requested using EXT- function, then this summary will
be based on the next best route for the City Pair, in consideration of the cruise
mode selected (Min Fuel / Cost or Time), excluding the route for which the main
Flight Plan has been calculated.
4)
Section 11 Keywords
KEYWORD : RTE
PURPOSE:
The RTE Keyword has been developed to give customers the ability to build their
own route at the time of the CFP request. This utilises the Station, Airway, Arrival-Departure and Route
files held within the Navigation database.
FORMAT:
The
RTEkeyword
format
follows
WAYPOINT/AIRWAY blocks, for example:
convention
of
RTE-Origin/SID Waypoint/Airway
RTE-Waypoint/STAR Destination
EXAMPLES:
1)
Basic input:
RTE-EGLL/DVR2F DVR/UG1 NTM/NTM1A EDDF
Uses published waypoints and airways. The format shows ORIGIN/Departure
WAYPOINT/Airway, WAYPOINT/Arrival, DESTINATION.
Note: Care must be taken when using a combination of RTE- and FXH: Any waypoint on
the FXH- input must also be entered in the RTE- line.
2)
Mixture of stations and SITA route number(s) and/or customer route identifiers:
RTE-EGLL/DVR3L DVR/131 EDDF
The example utilises a SITA Route number instead of an Airway.
The departure DVR3L is used from EGLL to DVR and then existing route number 131 is
used until destination EDDF.
Note: Validation is carried out to ensure that station(s) exist on the route specified. I.e.
Waypoint DVR must be present on route number 131.
RTE-LHR/DVR6J DVR/(LHRATH01) NEMES/NEME1C ATH
Above route allows for customer own route ID to be used. Route must be enclosed within
brackets ().
Section 11 Keywords
3)
4)
5)
Section 11 Keywords
6)
7)
Using waypoints and airways that are not stored in the SITA navigation database:
RTE-VHHH/DCT N2232.6E11408.0=BEKOL/DCT=A461
RTE-N2305.4E11351.2=SHL/DCT=J418
RTE-N2315.2E11338.3=ABYJZ/DCT ZGGG
The format of the RTE- keyword remains the same, in that waypoint/airway blocks
must be specified.
The example above indicates that:
i. Departure: Route follows direct flight out of VHHH.
ii. First waypoint is located at coordinates N2232.6E11408.0 and is called
BEKOL.
Note: Waypoint BEKOL prints in place of the full coordinates in the flight plan
output.
iii. From BEKOL, route takes a direct track to the next coordinates along an airway
that is not stored in the database A461.
Note: Airway A461 prints in place of DCTin the flight plan output.
iv. Arrival: From waypoint ABYJZ, located at coordinates N2315.2E11338.3,
a direct arrival is followed into ZGGG.
It is also possible to specify unpublished SIDs/STARs using this formula, for
example:
RTE-VHHH/DCT=BEK01A
RTE-N2220.2E11401.3=PORPA/DCT=BEK01A
RTE-N2214.9E11417.9=TD/DCT=BEK01A
Section 11 Keywords
RTE-N2232.6E11408.0=BEKOL/DCT=A461
Note: If the SID/STAR is not stored in the navigation database, all waypoints of
the departure/arrival must be specified in the RTE- input.
If the SID/STAR is loaded in the database, the normal RTE- input can be used,
for example:
RTE-VHHH/BEK01A
RTE-N2232.6E11408.0=BEKOL/DCT=A461
1)
Additional information:
The origin and destination codes must be specified as entered on the first line of
the CFP request. I.e. If ICAO codes are used on the CFP input; ICAO codes must
be used in the RTE- input.
Section 11 Keywords
The Airway direction is checked so that one-way Airways are not incorrectly
flown and any requests will be returned as an error.
Section 11 Keywords
KEYWORD : RTW-
PURPOSE:
FORMAT:
RTW-
EXAMPLE:
ERROR MESSAGES:
RTW MUST BE MAX 6 DIGITS
NOTE :
1)
Use when a restriction of take off weight is required. Use if MAX TOW is not
permitted. In the Example Restricted T.O.W. requested is 365400 KGS/LBS.
Section 11 Keywords
KEYWORD : RVF-
PURPOSE:
FORMAT:
RVF
EXAMPLE:
1)
2)
ERROR MESSAGES:
RVF MAY ONLY ENTER ONE OF RFX, RVF, RVT OR RVN
RVF MUST BE NUMERIC, MAX 3 DIGITS, NOT > 200
NOTE :
1)
The fuel related reserve policy figure in the aircraft attribute file can be overridden
for a specific Flight Plan, producing a new percentage of trip fuel as a reserve
figure.
2)
Section 11 Keywords
KEYWORD : RVN-
PURPOSE:
FORMAT:
RVN-
EXAMPLE:
RVN-
ERROR MESSAGE:
RVN MAY ONLY ENTER ONE OF RFX, RVF, RVT OR RVN
RVN FORMAT SHOULD BE RVN-
NOTE :
1)
This Keyword permits the calculation of a Flight Plan with NO fuel reserves
(Contingency).
Section 11 Keywords
KEYWORD : RVT-
PURPOSE:
FORMAT:
RVT-
EXAMPLE:
1)
2)
ERROR MESSAGE:
RVT MAY ONLY ENTER ONE OF RFX, RVF, RVT OR RVN
RVT MUST BE NUMERIC, MAX 3 DIGITS, NOT > 200
NOTE :
1)
The time related reserve policy figure in the aircraft attribute file can be
overridden for a specific Flight Plan, producing a new percentage of trip time as a
fuel reserve basis.
2)
3)
In Example 2) reserve policy is changed to 1.5% of trip time. Figures are entered
as tenths of a percentage.
Section 11 Keywords
KEYWORD : RWY-
PURPOSE:
FORMAT:
RWY-
EXAMPLE:
RWY-090/310
ERROR MESSAGES:
RWY-DEPARTURE AND ARRIVAL RUNWAYS REQUIRED
NOTE :
1)
This keyword is format related and may only be used when the format has been set up to
include the data. Please contact SITA Helpdesk for further assistance.
2)
This information is for display only. No calculation is affected should the actual
runways change before departure or arrival.
Section 11 Keywords
KEYWORD : SEL
PURPOSE:
FORMAT:
EXAMPLE:
1)
SEL-HFDS
ERROR MESSAGES:
SEL-MUST BE IN THE FORMAT SEL-ABCD
NOTE :
1)
Using the keyword will not update the Attribute file, only change the code for the
CFP being requested.
2)
In the Example the input SEL-HFDS would cause the ICAO plan to display the
updated code, example:
REG-G-PERF SEL/HFDSC
Section 11 Keywords
KEYWORD : SFI-
PURPOSE:
FORMAT:
EXAMPLE:
1)
2)
3)
4)
SFI-350
SFI-240/825
SFI-310/LRC
SFI-320/27
ERROR MESSAGE:
SFI FLT LEVEL MUST BE 3 NUMERICS (010-490)
(USE XXX/YYY, XXX=LEVEL, YYY = MACH CRUISE OR WAYPT)
SFI ONLY 3 SFI KEYWORDS ALLOWED
SFI FLT LEVEL AND/OR MACH VALUE MUST BE 3 NUMERIC
SFI WAYPOINT NUMBER MUST BE BETWEEN 01 AND 99
SFI CRZ MODE MUST BE ECO, LRC OR MNT
SFI MACH NUMBER MUST BE BETWEEN 500 AND 900
SFI SAME FLT LEVEL ENTERED IN 2 OR MORE LINES
SFI SAME MACH NUMBER ENTERED IN 2 OR MORE LINES
SFI FLT LEVEL MUST BE BETWEEN (V) & (V) FOR (V)
NOTE :
1)
The first parameter must be the Fixed Flight Level, within the minimum and
maximum cruising level range of the aircraft in use. Extreme limits are from
FL010 to FL490.
Section 11 Keywords
(Continued)
KEYWORD : SFI2)
The second parameter can be applied for 4 different options, as illustrated in the
Examples:
Example 1
Example 2
Example 3
3)
Example 4
Section 11 Keywords
KEYWORD : SGF-
PURPOSE:
FORMAT:
SGF-
EXAMPLE:
ERROR MESSAGES:
SGF MUST BE 3 DIGITS, BETWEEN 750 & 853
NOTE :
1)
2)
Section 11 Keywords
KEYWORD : SHP-
PURPOSE:
FORMAT:
SHP-
EXAMPLE:
SHP
The information printed on a short plan is dependent on each individual customers flight
plan format. Please contact SITA Helpdesk for any questions relating to short
plan if necessary.
Section 11 Keywords
KEYWORD : SMB-
PURPOSE:
FORMAT:
EXAMPLE:
1)
2)
SMB-40
SMB-40/785
ERROR MESSAGES:
SMB FLT LEVEL MUST BE 2 DIGITS, 20, 40, 60 OR 80 ONLY
SMB MUST BE NUMERIC, IN FORMAT XX OR XX/YYY
SMB MACH NUMBER MUST BE 3 DIGITS, 500 - 900
NOTE :
1)
The summary will print out at the end of the plan and will provide basic flight
details at different levels. An option to input a Mach Number is available.
2)
Section 11 Keywords
KEYWORD : SMI-
PURPOSE:
FORMAT:
SMI-
EXAMPLE:
SMI-
NOTE :
1)
Depending upon allowable cruise levels on each sector leg, the initial level may
fluctuate within the summary height profile to reflect appropriate semi-circular
rules.
Section 11 Keywords
KEYWORD : SML-
PURPOSE:
FORMAT:
SML-3
SML-825
EXAMPLE:
ERROR MESSAGES:
SML MUST BE CRZ MODE 1-6 OR MACH NUMBER 500-900
SML CANNOT HAVE SAME VALUE AS CRZ
SML CANNOT HAVE SAME VALUE AS FMA
NOTE :
1)
2)
Cruise Mode value must not be the same as the value input if CRZ Keyword is
used.
3)
Mach Number Value must not be the same as the value if FMA- is used.
Section 11 Keywords
KEYWORD : SMZ-
PURPOSE:
FORMAT:
SMZ-
EXAMPLE:
SMZ-
NOTE :
1)
Use of this Keyword will produce a Summary for a Max ZFW operation using the
Cruise Mode or Fixed Mach specified in the original CFP request.
2)
The Keyword is input without values. The summary printout will be appended to
the main Flight Plan.
Section 11 Keywords
KEYWORD : SPF-
PURPOSE:
Special Format
FORMAT:
SPF-
EXAMPLE:
SPF-4
ERROR MESSAGES:
SPF EXCEEDS MAXIMUM LENGTH OF 5 CHARS
SPF AIRLINE (V) DOES NOT EXIST
NOTE :
1)
This Keyword is used for Flight Plan format evaluation purposes only. To be
used with the CFP request for those airlines evaluating new or revised formats.
2)
Section 11 Keywords
KEYWORD : SSF-
PURPOSE:
FORMAT:
SSF-
EXAMPLE:
ERROR MESSAGES:
SSF MUST BE 3 DIGITS, FORMAT - N.N (0.1-2.0)
NOTE :
1)
The speed stability factor is used to determine the Long Range Cruise Speed
based on maximum Range Cruise Speed and increasing that speed by speed
stability factor. Long Range Cruise is normally defined as 99 per cent of Max
Range Cruise, that is 1 per cent displaced on the fast side of the fuel curve from
Maximum Range Cruise. Thus an SSF of 1.0 will produce a Flight Plan based on
99 per cent of Max Range Cruise which could be used as Long Range Cruise.
2)
A more refined value of Long Range Cruise can be made using a SSF less than
1.0. The Example above shows a SSF of 0.3. This will cause the Flight Plan to
show cruise speeds based on 99.7 per cent of max range cruise.
3)
Section 11 Keywords
KEYWORD : SWT-
PURPOSE:
FORMAT:
SWT-
EXAMPLE:
ERROR MESSAGES:
SWT MUST BE MAX 5 DIGITS, NOT GREATER THAN 50000
NOTE :
1)
The Example requests a summary at 2500 kgs/lbs weight interval above and
below planned ZFW.
Calculation assumes Cruise Mode or Fixed Mach as specified in the original CFP
request.
2)
3)
Section 11 Keywords
KEYWORD : SWX-
PURPOSE:
FORMAT:
SWX-
EXAMPLE:
1)
2)
3)
4)
5)
6)
7)
8)
9)
SWXSWX-FC
SWX-AUTO
SWX-FT/AUTO
SWX-SA/AUTO/EGLL
SWX-ALL/AUTO/JFK
SWX-AUTO/JFK/LAS/LGB
SWX-ALL/KMEM/KMIA
SWX-LHR/LBA/ABZ
ERROR MESSAGES:
SWX
SWX
SWX
SWX
NOTE :
1)
2)
Valid Surface Weather Keywords are FT, FC, FS, FFA, FCA, SA, ALL and FCST.
If no Surface Weather Keyword is entered the default is FCST which is a
combination of FC and FT.
3)
AUTO generates data for destination and alternates including Reclear Initial
Destination.
4)
Section 11 Keywords
KEYWORD : SWX-
SWX-
(continued)
= TAF
= Short Range Forecast
= Surface Actual
= FT + FC + SA
= FC + FT
= FT + SA
= FT + Last three Actuals
= FC + SA
Section 11 Keywords
KEYWORD : TAL-
PURPOSE:
FORMAT:
TAL-
EXAMPLES:
TAL-EGCC
ERROR MESSAGES:
TAL-ALTERNATE NOT VALID FOR ORIGIN AIRPORT (CHECK CODING)
This error message can be generated for either or both of these two reasons:
i) The elected TAL- must be listed as an ALTERNATE for the (ORIGIN) AIRPORTin the Oracle
database file: ALT - Alternate Airports
ii) The coding convention (ICAO or IATA) used for origin and destination must also be used for TAL-.
NOTE :
1)
JAR-OPS 1.295 states that An operator must select and specify in the operational
flight plan a take-off alternate if it would not be possible to return to the aerodrome
of departure for meteorological or performance reasons. The maximum range of
the take-off alternate in relation to the departure aerodrome is defined in the JAROPS reference.
2)
The use of this keyword is conditional on the user having supplied the maximum
range of the alternate in terms of a Max TAL Distance to Sita
for loading in the Air Policy file. If TAL is input without this detail having
been loaded, the second ERROR MESSAGE as shown above is produced.
3)
The other value supplied by the user for loading in the Air Policy File is the diversion
TAS. The diversion calculation assumes FL100 is used and takes the diversion TAS
and after applying the wind component computes the groundspeed and thereby the
Time for the diversion to the TAL.
The Grid Mora is established assuming a Great Circle Track.
Section 11 Keywords
4)
If the distance calculated exceeds the Maximum specified in the Air Policy File then
the third ERROR MESSAGE is produced, where xxxx is the TAL, yyyy is the
measured distance and zzzz is the Max TAL distance loaded in the Air Policy File
5)
The output of the TAL calculation is a fixed format, however the inclusion
of this detail and its location in the CFP format has be specified to the
format analysts beforehand. The output format includes the Maximum
Landing Weight used in the CFP calculation. The complete output is:
TRACK(T)
240
DIST TIME
222
0:40
ETA
10:40
90000
Section 11 Keywords
KEYWORD : TAX-
PURPOSE:
FORMAT:
TAX-
EXAMPLE:
ERROR MESSAGES:
TAX MUST BE NUMERIC, UP TO 5 DIGITS
NOTE :
1)
This facility will provide printout of TAXI fuel on the Flight Plan only if formatted to
accept this field.
2)
3)
If there is no TAXI field in the format, the request TAX- fuel will printout as part of
the Ramp Fuel figure if it is formatted for customer.
4)
If a taxi fuel value is loaded in the aircraft attribute file or on the screen then this
factor will be applied to the total fuel required calculation. In the case of a full
tanks uplift, provision for the specified taxi fuel is made in the calculation by
limiting the max Flight Plan fuel figure in order to accommodate the taxi fuel.
Section 11 Keywords
KEYWORD : TDF-
PURPOSE:
FORMAT:
TDF
EXAMPLE:
1)
2)
3)
4)
TDF - 1905
TDF - 0630/26
TDF - 9999
TDF - 9999/1830
ERROR MESSAGES:
TDF
TDF
TDF
TDF
TDF
TDF
NOTE :
1)
2)
If it is necessary to restrict the time at which a "9999" plan is run then a 'latest
time' may be entered in addition to the "9999". This means the plan will be
processed either after the next weather files update, or if this is delayed, at the
specified time.
3)
Section 11 Keywords
DIRECTORY LISTING:
-----------------------------TO LIST ALL FP REF NUMBERS ON TDF FILE FOR AIRLINE : BB
------------------------------------------------------------------------------------------
Line
1
2
3
4
TDF
DIR
PSW-BB AAA
MAD-/FPB02
- TRANSACTION NAME
- TYPE : DIR FOR LIST OR DEL TO CANCEL
- PASSWORD FOR AIRLINE
- MAD ADDRESS FOR CICSPRINT
Notes:
Line numbers 1,2,3 are mandatory
MAD address line is optional.
The resulting output from above request is :LIST OF DELAYED FLIGHT FPLANS FOR AIRLINE : BB
2)
ORIG
----
AAMJE
AAMJF
AAMJG
AAMJH
AAMJL
AAMJM
LFPO
LFPO
LFPO
LFPO
LFPO
LFPO
FIMP
FIMP
FIMP
FIMP
FIMP
FIMP
BB 0055.01
BB 0055.01
BB 0055.01
BB 0055.01
BB 0055.01
BB 0055.01
DD
DD
DD
DD
DD
DD
HR MN
HR MN
HR MN
HR MN
HR MN
HR MN
DD
DD
DD
DD
DD
DD
HR MN
HR MN
HR MN
HR MN
HR MN
HR MN
Line
1
2
TDF
DEL
3
4
PSW-BB AAAA
AAMJE/AAMJF/AAMFL
MAD -/FPB02
- TRANSACTION NAME
- TYPE : DIR FOR LIST OR DEL TO
CANCEL
- PASSWORD FOR AIRLINE
- UP TO 5 FPREF NOS SEPARATED
BY '/'
- MAD ADDRESS FOR CICSPRINT
(continued/)
Section 11 Keywords
)
(continued)
Notes:
Line nos 1,2,3,4 are mandatory.
MAD address line is optional.
The resulting output from above request is :THE FOLLOWING TDF FP REF NOS HAVE BEEN CANCELLED FOR AIRLINE: BB
REFNO
----AAMJE
AAMJF
AAMJL
FLT DETAIL
ORIG DEST DT REQ TIME DT SUB TIME
---------- ---- ---- -- -------- -- --------BB 0055.01
LFPO FIMP DD HR MN DD HR MN CANCELLED
BB 0055.01
LFPO FIMP DD HR MN DD HR MN CANCELLED
BB 0055.01
LFPO FIMP DD HR MN DD HR MN CANCELLED
DELETION OF DELAYED FLIGHT PLANS FROM TDF FILE AND REF NO NOT
FOUND
SAMPLE INPUT
----------------------
Line
1
2
TDF
DEL
3
4
5
PSW-BB AAAA
AAMJE
MAD-/FPB02
- TRANSACTION NAME
- TYPE : DIR FOR LIST OR DEL TO
CANCEL
- PASSWORD FOR AIRLINE
- UPTO 5 FPREF NOS SEPARATED BY '/'
- MAD ADDRESS FOR CICSPRINT
(continued)
Section 11 Keywords
(continued)
Notes:
2)
Line
SAMPLE INPUT
---------------------1
TDF
2
TIP
3
- TRANSACTION NAME
- TYPE : DIR FOR LIST OR DEL TO
CANCEL
PSW-BB AAAA - PASSWORD FOR AIRLINE
ERROR MESSAGE:
TDF - INVALID FORMAT - SECOND LINE MUST BE A DIR OR DEL
3)
SAMPLE INPUT
----------------------
Line
1
2
TDF
DIR
3
4
PSW-BB AAAA
AAAAA/AAAAA
- TRANSACTION NAME
- TYPE : DIR FOR LIST OR DEL TO
CANCEL
- PASSWORD FOR AIRLINE
ERROR MESSAGE:
TDF - INVALID FORMAT - FOURTH LINE IF ENTERED MUST BE A MAD LINE
Section 11 Keywords
(continued)
4)
SAMPLE INPUT
----------------------
Line
1
2
TDF
DEL
3
4
5
PSW-BB AAAA
AAMJE
MAD-/FPB02
- TRANSACTION NAME
- TYPE : DIR FOR LIST OR DEL TO
CANCEL
- PASSWORD FOR AIRLINE
UP TO 5 REFs SEPARATED BY '/'
- MAD ADDRESS FOR CICSPRINT
ERROR MESSAGE:
TDF - INVALID FORMAT-FOURTH LINE ONLY 5 REFNOS CAN BE CANCELLED
5)
SAMPLE INPUT
----------------------
Line
1
2
TDF
DEL
3
4
5
PSW-BB AAAA
AAMJE
MAD-/FPB02
- TRANSACTION NAME
- TYPE : DIR FOR LIST OR DEL
TO CANCEL
- PASSWORD FOR AIRLINE
UP TO 5 REFs SEPARATED BY '/'
- MAD ADDRESS FOR CICSPRINT
ERROR MESSAGE:
TDF - INVALID FORMAT - FOURTH LINE REFNO MUST BE SEPARATED BY '/'
Section 11 Keywords
KEYWORD : TFU-
PURPOSE:
FORMAT:
EXAMPLE:
1)
2)*
3)
ERROR MESSAGES:
TFU MUST BE NUMERIC, UP TO 6 DIGITS OR "MAX"
TFU EXCEEDS MAX TANK WT OF (V) FOR (V)
CFP- TFU- NOT ALLOWED FOR RECLEAR FLIGHTS. USE AFU.
NOTE :
1)
Payload will always take preference over any fuel tankerage specified.
2)
3)
Input of TFU-MAX (example 2) will produce max fuel uplift subject to the
restrictions of structural limitations and volumetric capacity. *
4)
Section 11 Keywords
KEYWORD : TLW-
PURPOSE:
FORMAT:
EXAMPLE:
ERROR MESSAGES:
TLW
TLW
TLW
TLW
TLW
NOTE :
1)
The weight specified here does not affect the stored landing weight or an entered
RLW, but it does allow the customer to apply a buffer of, say, 1500 between the
stored landing Weight/RLW and TLW.
2)
3)
4)
Relationship RLW/TLW:
RLW = Restricted Landing Weight (see Keyword RLW-)
5)
Section 11 Keywords
KEYWORD : TLX-
PURPOSE:
FORMAT:
EXAMPLE:
ERROR MESSAGES:
TLX MUST BE NUMERIC, MAXIMUM 6 DIGITS
TLX EXCEEDS 1.2 X MAX LND WT = (V) FOR (V)
TLX MAY NOT BE LESS THAN OWE VALUE OF (V)
TLX LESS THAN MIN ZFWT VALUE OF (V) FOR (V)
NOTE :
1)
2)
3)
The fuel uplift will be a maximum subject to the restrictions of structural limitation
and volumetric capacity and the TLX landing weight limit.
Section 11 Keywords
KEYWORD : TNK-
PURPOSE:
FORMAT:
EXAMPLE:
TNK-MAX
Calculates the Maximum Tanker fuel and includes the fuel in the Flight
Plan calculation. Provides a Tankering Analysis on the CFP.
TNK-MAX/S
As for TNK-MAX but does not include tanker fuel as fuel onboard in the
main flight plan calculation.
TNK-OPT
TNK-OPT/S
TNK-ANL
TNK-1000
Using a fixed amount, e.g 1000, will also apply that figure to the fuel
block unless a loss is made in tankering that amount, (a switch can be
applied to allow the chosen TNK- figure to print regardless of
profit/loss)
ERROR MESSAGE:
TNK-UNRECOGNISABLE INPUT
NOTE :
1)
Whilst TNK- initiates the tankering program, a tankering calculation will only be made
if Fuel prices at the Origin and Destination are defined, either by Keywords FCO and
FCD , or are held in the Fuel Price File. Furthermore, currently tankering will only be
calculated if the Fuel price at the Destination is equal or greater than the Fuel price at
the Origin plus the Tankering Criteria. Also if all these conditions are met, tankering
will currently be shown on the CFP providing there is a cost saving to be made and it
is possible to carry the fuel with respect to weight and tank limitations.
2)
Section 11 Keywords
KEYWORD : TPA-
PURPOSE:
FORMAT:
TPA-
EXAMPLE:
1)
2)
3)
TPA/-2
TPA/5
TPA/XX
(ISA - 2 to Alternate)
(ISA + 5 to Alternate)
(Alternate temperature value in the range ISA
deviation -20 to plus 20. Same rules as TPE.)
The minimum CFP entry requires the Keyword WDE to be used with a value.
To request a plan with zero Wind and ISA Temperature from Origin to Destination to
Alternate enter WDE/0 only.
EXAMPLE:
CFP
XX1234/EGLL/LGAT/0100/210000
WDE/30
TPA/-5
ERROR MESSAGE:
TPA INVALID, FORMAT IS TPA/-NN, BETWEEN 20 & -20
TPA (V) OUT OF RANGE, MUST BE BETWEEN 20 & -20
NOTE :
1)
The above request is asking for 30KT tailwind and ISA-5 to destination with zero
Wind and ISA Temperature to Alternate.
2)
If Keywords TPE-, WDA-, TPA- are not used, bearing in mind WDE- is
mandatory, the computer will set the values for these 3 items to zero. Any
Keyword not used after WDE- assumes a zero value.
Section 11 Keywords
KEYWORD : TPE-
PURPOSE:
FORMAT:
TPE-
EXAMPLE:
1)
2)
3)
TPE/-20
TPE/9
TPE/XX
The minimum CFP entry requires the Keyword WDE- to be used with a value.
To request a plan with zero Wind and ISA Temperature from Origin to Destination to
Alternate enter WDE/0 only.
EXAMPLE:
CFP
XX1234/EGLL/LGAT/0100/210000
WDE/30
TPE/-5
ERROR MESSAGE:
TPE INVALID, FORMAT IS TPE/-NN, BETWEEN 20 & -20
TPE (V) OUT OF RANGE, MUST BE BETWEEN 20 & -20
NOTE :
1)
The above request is asking for 30KT tailwind and ISA-5 to destination with zero
Wind and ISA Temperature to Alternate.
2)
If Keywords TPE, WDA, TPA are not used, bearing in mind WDE- is mandatory,
the computer will set the values for these 3 items to zero. Any Keyword not used
after WDE- assumes a zero value.
Section 11 Keywords
KEYWORD : TTI-
PURPOSE:
FORMAT:
EXAMPLE:
ERROR MESSAGES:
TTI-MUST BE LENGTH 1 OR 2 (0-99)
NOTE :
1) A default Taxi Time In value can be configured in an aircrafts Air Policy file. However,
when used, the value of the keyword TTI- will override this default value.
2) The default Taxi Time In value in the Air Policy file can be suppressed by using the
keyword TTI-0 on the flight plan request.
3) The flight plan format must be configured in advance in order to print the value of this
keyword. Please contact the SITA Helpdesk for more information.
Section 11 Keywords
KEYWORD : TTO-
PURPOSE:
FORMAT:
EXAMPLE:
ERROR MESSAGES:
TTO-MUST BE LENGTH 1 OR 2 (0-99)
NOTE :
1) A default Taxi Time Out value can be configured in an aircrafts Air Policy file. However,
when used, the value of the keyword TTO- will override this default value.
2) The default Taxi Time Out value in the Air Policy file can be suppressed by using the
keyword TTO-0 on the flight plan request.
3) The flight plan format must be configured in advance in order to print the value of this
keyword. Please contact the SITA Helpdesk for more information.
Section 11 Keywords
KEYWORD : TWS-
PURPOSE:
FORMAT:
TWS-
EXAMPLE:
TWS-13000 ( KGS/LBS)
ERROR MESSAGES:
TWS MUST BE MAXIMUM 5 DIGITS NOT GREATER THAN 50000
NOTE :
1)
The Example (TWS-13000) requests summaries at 13000 Kgs/Lbs weight interval above
and below planned T.O.W. Calculation is based on the main Flight Plan CRZ mode/Fixed
mach.
2)
3)
Achievement of structural and/or volumetric limitations will have the obvious effect of
constraining summary.
4)
Refer also to SWT- Keyword for summaries based on ZFW (both SWT- and TWS- are
mutually exclusive).
Section 11 Keywords
KEYWORD : TXI-
PURPOSE:
FORMAT:
TXI-
EXAMPLE:
ERROR MESSAGES:
TXI MUST BE NUMERIC, MAXIMUM 4 DIGITS
NOTE :
1)
The Example provides a Taxy In fuel figure of 600 Kgs/lbs. The maximum input
allowed is TXI-9999.
2)
Taxy In fuel will print out as a separate item in the fuel summary portion of a
Flight Plan, if the format allows for it; otherwise it will be added only to the
required fuel on board total.
Section 11 Keywords
KEYWORD : TYF
PURPOSE:
FORMAT:
TYF-
EXAMPLES:
TYF-RECLEAR
TYF-ETOPS/180
TYF-TEST FLIGHT
ERROR MESSAGES:
TYF-MAX 10 CHARACTERS ONLY
NOTE :
6)
7)
The output on the flight plan prints whatever follows the TYF- input and then is
followed by the suffix PLAN. Eg RECLEAR PLAN
The position of the output on the flight plan has to be advised in
advance to the format analysts.
8)
Section 11 Keywords
KEYWORD : VID-
PURPOSE:
FORMAT:
VID-
EXAMPLE:
VID-XS
ERROR MESSAGES:
VID MUST BE 2-3 ALPHANUMERICS
VID (V) INVALID, MUST BE 2-3 CHARACTERS
Section 11 Keywords
KEYWORD : WDA-
PURPOSE:
FORMAT:
WDA/
WDA/-150
WDA/5
WDA/XX
EXAMPLE:
1)
2)
3)
The minimum CFP entry requires the Keyword WDE- to be used with a value.
To request a plan with zero Wind and ISA Temperature from Origin to Destination to
Alternate enter WDE/0 only.
EXAMPLE:
CFP
XX/1234/EGLL/LGAT/0100/210000
WDE/30
TPE/-5
ERROR MESSAGE:
WDA INVALID, FORMAT IS WDA/-NNN, BETWEEN 200 & -200
WDA (V) OUT OF RANGE, MUST BE BETWEEN 200 & -200
WDA 2ND PARAMETER, IF ENTERED MUST BE CHARACTER A
NOTE :
1)
The above request is asking for 30KT tailwind and ISA-5 to destination with zero
Wind and ISA Temperature to Alternate.
2)
If Keywords TPE, WDA, TPA are not used, bearing in mind WDE is mandatory,
the computer will set the values for these 3 items to zero. Any Keyword not used
after WDE assumes a zero value.
Section 11 Keywords
KEYWORD : WDE-
PURPOSE:
FORMAT:
EXAMPLE:
WDE/-30
WDE/50/A
Enroute wind values in the range -200 to plus 200 KTS where NNN is the
wind speed value. Use 1-3 numerics for the wind speed with minus sign
in front of value if a headwind.
WDE/NNN/A If fixed wind component input then 2/3rds of value applied on climb and
descent and total value applied in cruise. If second parameter "A" also
input full value is applied to climb/cruise/descent and also for the
Alternate calculation.
EXAMPLE:
WDE/-30
WDE/50/A
The minimum CFP entry requires the Keyword WDE to be used with a value.
To request a plan with zero Wind and ISA Temperature from Origin to Destination to
Alternate enter WDE/0 only.
EXAMPLE:
CFP
XX1234/EGLL/LGAT/0100/210000
WDE/30
TPE/-5
ERROR MESSAGE:
WDE INVALID, FORMAT IS WDE/-NNN, BETWEEN 200 & -200
(or WDE/-NNN/A)
(continued/)
Section 11 Keywords
KEYWORD : WDE-
(continued)
NOTE :
1)
The above request is asking for 30KT tailwind and ISA-5 to destination with zero
Wind and ISA Temperature to Alternate.
2)
If Keywords TPE, WDA, TPA are not used, bearing in mind WDE is mandatory,
the computer will set the values for these 3 items to zero. Any Keyword not used
after WDE assumes a zero value.
Section 11 Keywords
KEYWORD : WXSPURPOSE:
FORMAT:
WXS-
EXAMPLE:
1)
2)
3)
4)
5)
6)
WXSWXS-A
WXS-A/99
WXS-2
WXS-2/99
WXS-N
ERROR MESSAGES:
WXS 1ST CHAR MAY BE N, A, H, D, 2 TO 9 ONLY
(format is WXS-, WXS-X or WXS-X/99)
WXS (V) - UNRECOGNISABLE FORMAT
WXS 2ND PARAMETER MAY BE 0,40, 44, 80, 88 OR 99 ONLY
NOTE :
1)
Number of Waypoints:
Blank or A means all waypoints. Values 2 to 9 states which waypoints to print,
ie. WXS-3 signifies every third waypoint. D means half hourly; H means
hourly; N overrides the weather summary keyword stored in the parameter for
that particular Flight Plan request.
2)
3)
EXAMPLE
WXS-2/40 requests summary at every other waypoint, for 4000ft above planned
height.
4)
Section 11 Keywords
KEYWORD : XFU-
PURPOSE:
FORMAT:
EXAMPLE: 1)
EXAMPLE: 2)*
XFU-MAX
ERROR MESSAGES:
XFU MUST BE NUMERIC, MAXIMUM 6 DIGITS. OR 'MAX'
XFU MAY NOT BE ENTERED WITH MTF
NOTE :
1)
This input will produce an uplift of extra fuel. This fuel does not have precedence
over payload. If the flight is overweight this fuel will be reduced.
2)*
The input XFU-MAX will produce max fuel uplift subject to the restrictions of
structural limitations and volumetric capacity.
3)