SITA Keyword Manual (1)

Flight Planning Reference Manual

Page 0 of 168

Section 11 Keywords

Flight Planning Keyword Manual

Flight Planning Keyword Manual 11 KEYWORDS A CFP input consists of keywords, thus allowing the user to tailor each request to the exact requirements for a particular flight. The mandatory keywords for an ad-hoc flight plan are described in Section 3. All other keywords mentioned in this section are optional, but may be subject to combination restrictions. Any keyword combination restrictions are mentioned in the relevant text.

11.1 KEYWORDS: Basic Rules 1) Keywords can be either 1 or 3 characters long and must be followed by a hyphen (-)

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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:

***-INVALID KEYWORD ENTERED,MUST BEGIN XXX- OR M-

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 2 of 168

Section 11 Keywords

11.2 KEYWORDS: Categories To assist access to the online help facility, all available keywords are categorised within the following three character abbreviations:

CATEGORY INDEX

CATEGORY

DESCRIPTION

ACP ATC FUE GEN MET NAV SUM

Aircraft Performance Related ATC Plan Related Fuel Related General Purpose Weather Related Navigation Related Summary Related

The following index is in keyword alphabetical order:

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 3 of 168

Section 11 Keywords

KWD

DESCRIPTION

AFT- AFTN Addressing AFU- Uplift additional fuel (mandatory fuel: priority over payload) ALT- Primary Alternate AL22nd Alternate AL33rd Alternate ARM- Facility to add remarks in item 18 of the ATC plan ARP- Enables the creation of an airport for use as origin, destination or primary alternate ATC- Requests ICAO ATC plan AUS- Request Australian AUSOT track 1 BAL- Specify a fixed amount of residual/dead fuel BLK- Exclude specific routes from optimisation CAL- Cap cruise flight level CBF- Climb fuel degradation factor CIDCost Index value CPA- Cap flight level between destination and first alternate CP2- Cap flight level between destination and second alternate CP3- Cap flight level between destination and third alternate CPN- City Pair Number 1 CPT- Captains name CRP- Cruise and descent mode selection for turboprop CRZ- Cruise mode (LRC/Econ/Min Time) CZF- Cruise fuel degradation factor CZT- Cruise thrust limit temperature buffer DMF- Departure manoeuvre fuel DMT- Departure manoeuvre Time DPP- Allows flight plan calculation based on decision point procedure 1 DRM- Dispatch Release Message 1 DSP- Dispatcher's Name DTE- Specify date or statistical weather ECT- Specify routes for optimisation EEP- Define ETOPS Entry & Exit airports & initiate calculation of ETOPS Entry & ETOPS Exit times EQP- Specify equipment in ITEM 10 of ICAO flight plan EQT- Determine Equal Time Point 1 ERA- Enroute Alternate ETA- Amend stored Estimated Time of Arrival ETD- Amend stored Estimated Time of Departure ETE- ETOPS keyword to provide fuel to first airport listed ETP- Determine equal time point between specified airports and access engine out data (ETOPS) ETX- As ETP, but adds computed critical fuel to the flight plan calculation EXT- To specify a particular route name or number FAA- Requests ICAO FAA domestic plan FAL- Fix cruise flight level FAX- Send facsimile of whole or component part of flight plan FCD- Fuel cost at destination (Tankering) FCO- Fuel cost at origin (Econ Cruise & Tankering) FLT- Amendment of stored flight or service number FMA- Override default cruise speed FMT- Format specification (for use with RFP transaction) FXH- Specify fixed flight level profile FXM- Specify fixed speed flight plan profile © Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

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

Flight Planning Reference Manual Section 11 Keywords

HDA- Holding height and time selection for alternate FUE HDB- Holding height and time selection at initial alternate FUE HDD- Holding height and time selection at final destination FUE HDR- Holding height and time selection at initial destination FUE HLD- Override normal holding fuel/time FUE HNL- Specify of Honolulu FTR NAV HOC- Hourly operating cost (Econ Cruise) ACP HRA- Holding race track adjustment factor FUE HTA- Holding ISA temperature correction factor FUE IASIndicated air speed/level ACP LTT- Request least time track non-flyable route between any 2 airportsNAV MPlain text message line GEN MAD- Delivery address GEN MFU- Override maximum tanks weight FUE MOA- Minimum fuel overhead alternate FUE MOD- Minimum fuel overhead destination FUE MTF- Specify minimum fuel in tanks FUE MVD- Amend manoeuvering (inst.app) distance at destination ACP MVF- Specify destination manoeuvering fuel ACP MVT- Specify destination manoeuvering time ACP MZF- Override default maximum zero fuel weight ACP NAT- Specify North Atlantic Routing NAV 1 GEN NM1- Display crew names, NM1 – NM9 NTM-Q Request route specific NOTAMs using customer defined filter GEN OAL- Override computed fuel/time value to (final) primary alternate FUE OAR- Override computed fuel/time value to (initial) primary alternate FUE OFC- Calculate routing over flight charges NAV OWE- Override stored operating weight empty (dry operating weight) ACP PAC- Request Pacific routing NAV PICSend ICAO ATC plan as separate Sitatex (Type-B) message ATC PLD- Specify payload ACP PRF- Specify fixed flight level profile, overriding normal flight level separation rules. NAV PRIOverride message transmission priority GEN PSW- Password protection for selected transactions GEN RA2- 2nd alternate for initial airport NAV RA3- 3rd alternate for initial airport NAV RCA- Cap flight level to initial airport alternate NAV RCR- Specify reclear parameters NAV RC1- Specify oceanic reclear NAV RFX- Specify fixed fuel reserves FUE RLW- Restrict landing weight ACP RMN- Specify minimum reserve fuel FUE RNY- Re-analysis flight plan FUE RRG- Automatically generate a route between NAV any two airports in the database RSF- Route summary, specified route SUM RSG- Route summary, least distance route SUM RSN- Route summary, next best route SUM RTE- Route Build in ARINC 424 format NAV RTW- Restrict take-off weight ACP RVF- Modify fuel reserve policy (FUEL) FUE RVN- Remove fuel reserves FUE RVT- Modify fuel reserve policy (TIME) FUE RWY- Specify runway used Origin/Destination GEN SEL- Specify SELCAL code to appear in ICAO ATC flight plan ATC © Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Page 4 of 168

Flight Planning Reference Manual

Page 5 of 168

Section 11 Keywords

SFISGFSHPSMBSMISMLSMZSPFSSFSWTSWXTAL TAXTDFTFUTLWTLXTNKTPATPETTITTOTWSTXITYFVIDWDAWDEWXSXFU1

Fuel summary at fixed flight level, mach no., or cruise mode at or to a specific waypoint Override default specific gravity of fuel value Short or summary flight plan Summary at a lower flight level Summary for entire flight at initial TOC level Summary at selected mach no. or cruise mode Summary at maximum zero fuel weight Specify flight plan format number Speed stability factor Summaries at weight intervals above/below computed ZFW Request surface weather reports for specified airfields 1 Define a take-off alternate Taxi out fuel Delay processing of flight plan input Specify tankering fuel Tankering landing weight Tanker fuel to specified landing weight Initiate tankering program Alternate ISA deviation Origin-destination ISA deviation 1 Specify taxi-in time 1 Specify taxi-out time Take-off weight summaries Override taxy-in fuel 1 Specify type of flight Change airline designator printing on the flight plan Apply fixed wind to alternate Obtain flight plan with fixed winds and temperatures Upper air wind and temperature summaries Uplift extra fuel (optional fuel: payload has priority)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 6 of 168

Section 11 Keywords

11.3 KEYWORDS: Descriptions KEYWORD:

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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-

ADDRESS NUMBER (V) IS INVALID AT LEAST ONE ADDRESS NEEDED OR TOO MANY ENTERED INVALID TYPE- (V) MUST BE CFP, SHP or ATC INVALID TYPE- AUT MUST BE CFP,ATC,SHP OR AUT* AT LEAST ONE ADDRESS NEEDED OR TOO MANY ENTERED AFT-AUTP CAN ONLY BE USED IF ATC HAS BEEN USED AFT-AUTF CAN ONLY BE USED IF ATC HAS BEEN USED AFT-AUTO CAN ONLY BE USED IF ATC HAS BEEN USED AFT-INPUT MUST BE AUT*/P FOR RETURNING ADDS TO ORIGIN AFT-ORIGIN ADDRESS MUST BE ENTERED IF AFT-AUTO IS USED

ADDITIONAL INFORMATION: •

Ensure that the first AFTN address is the originating address.

•

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 8 of 168

Section 11 Keywords

KEYWORD:

AFU-

PURPOSE:

To request mandatory additional fuel

FORMAT:

AFUEntered as weight value in units - maximum 6 digits

EXAMPLE: AFU-15000 Request 15000 kgs/lbs of additional fuel

ERROR MESSAGES: AFUAFUAFU-

MUST BE NUMERIC, MAXIMUM 6 DIGITS ENTRY OF UNLIMITED ADDITIONAL FUEL IS INVALID THIS WOULD GIVE A NIL PAYLOAD CALCULATION EXCEEDS MAXIMUM TANK WT OF (V) FOR (V)

ADDITIONAL INFORMATION: •

Additional fuel takes precedence over payload. I.e. AFU is mandatory.

•

An input of AFU-999999 would cause a NIL PAYLOAD calculation, as the effect is to request max fuel uplift subject to restrictions of structural limitations and volumetric capacity. Therefore, if AFU-999999 is entered, a validation error message is received.

•

To request the maximum possible extra fuel uplift, see keywords XFU- or TFU-.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 9 of 168

Section 11 Keywords

KEYWORD :

ALT-

PURPOSE:

To define the primary alternate in a CFP request. Mandatory keyword in CFP requests.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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-

MUST BE 3 CHAR IATA OR 4 CHAR ICAO CODE UNRECOGNISABLE INPUT FORMAT INVALID FORMAT - USE XXX/D/9999 XXXX/D/9999 MUST BE SPECIFIED FOR A 9999 FLIGHT NIFR MUST NOT BE FOLLOWED BY A DISTANCE MUST BE IATA OR ICAO CODE OR NOALT AN ALTERNATE IDENTIFIER MUST BE ENTERED ALTERNATE NOT EQUAL TO ORIGINAL ALTERNATE ALTERNATE - (V) NOT LOADED FOR DESTINATION - (V) ROUTE NUMBER X IS INVALID AIRLINE AND CUSTOMER ROUTE NOT FOUND A/P EGKK ELECTED DIST IS LESS THAN G/C FROM DEST OVERRIDE DISTANCE MUST BE NUMERIC MAX 4 DIGITS NO ROUTES LOADED FOR THIS ALTERNATE

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 11 of 168

Section 11 Keywords

KEYWORD : AL2-

PURPOSE:

To define the secondary alternate in a CFP request.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 12 of 168

Section 11 Keywords

ERROR MESSAGES: AL2AL2AL2AL2AL2AL2-

MUST BE 3 CHAR IATA OR 4 CHAR ICAO CODE ROUTE, IF ENTERED, MUST BE MAXIMUM OF 6 DIGITS UNRECOGNISABLE INPUT FORMAT INVALID FORMAT - USE XXX/9999 OR XXXX/9999 MAY NOT BE ENTERED WITHOUT ALT2ND ALTN - (V) NOT VALID FOR DESTINATION - (V)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 13 of 168

Section 11 Keywords

KEYWORD : AL3-

PURPOSE:

To define the third alternate in a CFP request.

FORMAT:

AL3-

EXAMPLES:

All examples shown for keyword AL2- (second alternate) can be used, ensuring that ‘AL2-‘ is replaced by ‘AL3-’.

ERROR MESSAGES: AL3AL3AL3AL3AL3AL3-

MUST BE 3 CHAR IATA OR 4 CHAR ICAO CODE ROUTE, IF ENTERED, MUST BE MAXIMUM OF 6 DIGITS UNRECOGNISABLE INPUT FORMAT INVALID FORMAT - USE XXX/9999 OR XXXX/9999 MAY NOT BE ENTERED WITHOUT ALT- AND AL23RD ALTN - (V) NOT VALID FOR DESTINATION - (V)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 14 of 168

Section 11 Keywords

KEYWORD : ARM-

PURPOSE:

Enables plain language remarks to be entered within item 18 of ICAO ATC plan.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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

a). ICAO CODE This mandatory field will consist of 4 characters (possibly alpha-numeric) to signify an Airport ICAO code. b). LATITUDE/LONGITUDE This mandatory field will consist of 11 characters in the format North/South and 4 characters numeric plus East/West plus 5 characters numeric c).FIR This field will consist of the 4 character FIR code applicable to the airport plus the 2 character sub code for it. d). AIRPORT ELEVATION This field will consist of the height of the airport in feet above sea level. This can be expressed in a numeric value (max 4 characters). Airports with an elevation below sea level will have a leading minus sign. Example Input ICAO CODE/LAT LONG

/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.

Flight Planning Reference Manual

Page 16 of 168

Section 11 Keywords

Validation and Error Messages:

ARPARPARPARP– ARP– ARPARPARP– ARPARPARPARP-

RTE-KEYWORD MANDATORY WITH ARP INPUT CODE DUPLICATED INPUT CODES ALLOWED ORIG/DEST/ALT INPUT CODE NOT ON RTE OR ALT INPUT ALT ONLY AVAILABLE WITH ARP (NOT AL2/AL3 on ARP) INVALID INPUT FORMAT, ICAO/LAT-LONG/FIR/ELEVATION ALT MUST INCLUDE OVERIDE DISTANCE ALT-XXXX/D/NNNN RRG NOT AVAILABLE WITH ARP ICAO CODE xxxx ALREADY LOADED LAT LONG MUST BE IN THE FORMAT N/SNNNN E/WNNNNN ELEV MUST BE IN THE FORMAT N OR –N (UP TO 4 CHARACTERS) FIR MUST BE IN THE FORMAT XXXXZX

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 17 of 168

Section 11 Keywords

KEYWORD :

ATC-

PURPOSE:

Production of ICAO ATC plan appended to the main flight plan. Item 8 (flight rules and type of flight) can be amended with the addition of further parameters; see examples below.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 18 of 168

Section 11 Keywords

KEYWORD : AUS-

AUS-

PURPOSE:

To define required Australian Organised Track in a Flight Plan.

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)

A maximum of 7 Co-ordinates per line up to a maximum of 20 in total.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 19 of 168

Section 11 Keywords

KEYWORD :

BAL-

PURPOSE:

To specify the amount of unusable fuel.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 20 of 168

Section 11 Keywords

KEYWORD :

BLK-

PURPOSE:

To exclude, or block, a particular route(s) from an optimised route search of all pre-stored routes between an airport pair.

FORMAT:

BLKUse SITA or customer route names. Maximum length of route name = 10 alphanumeric characters Maximum number of routes to be excluded = 12 Separate each route name with a forward slash, ‘/’.

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

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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: •

Terrain clearance is not checked during the flight plan calculation.

•

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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-.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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-

MUST BE NUMERIC BETWEEN 1 AND 500 MUST BE 1-3 NUMERICS, BETWEEN 1 AND 500 CID MAY NOT BE ENTERED WITH FCO AND HOC MAY NOT BE ENTERED WITH HOC REQUIRED WHEN NO COST INDEX ON AIRCRAFT FILE CRZ 1 REQUIRED WITH THIS KEYWORD

ADDITIONAL INFORMATION: •

Must be used in conjunction with cruise mode 1 (CRZ-1).

•

Cost index is a ratio. There are 2 definitions : (1)

(2)

TIME BASED OPERATING COSTS PER HOUR COST OF 100 LBS OF FUEL

known as Imperial Units

TIME BASED OPERATING COSTS PER MINUTE COST OF 1 KG OF FUEL

known as Metric Units

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 24 of 168

Section 11 Keywords

KEYWORD : CPA-

PURPOSE:

Cap the altitude/flight level between destination and first alternate.

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.

•

Terrain clearance is not checked.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 25 of 168

Section 11 Keywords

KEYWORD :

CP2-

PURPOSE:

Cap the altitude/flight level between destination and second alternate.

FORMAT:

CP2Followed by a flight level; value should be between 010 and 490

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.

•

Terrain clearance is not checked.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 26 of 168

Section 11 Keywords

KEYWORD :

CP3-

PURPOSE:

Cap the altitude/flight level between destination and third alternate.

FORMAT:

CP3Followed by a flight level; value should be between 010 and 490

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.

•

Terrain clearance is not checked.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 27 of 168

Section 11 Keywords

KEYWORD :

CPN-

PURPOSE:

To instruct the system to use either SITA or customer routes.

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)

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 28 of 168

Section 11 Keywords

KEYWORD : CPT-

PURPOSE:

Specification of Captains name on Flight Plan print out.

FORMAT:

CPT- MERRYWEATHER (up to 24 letters)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 29 of 168

Section 11 Keywords

EYWORD : CRP-

CRP-

PURPOSE:

Cruise and Descent Mode selection for Turbo Propeller Aircraft only.

FORMAT:

CRP-

EXAMPLE:

1) 2) 3)

CRP-3 (Cruise schedule 3) CRP-2/3 (Cruise schedule 2, descent schedule 3 CRP-//2 (descent schedule 2)

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)

This Keyword enables a particular cruise and/or descent schedule to be selected for turbo propeller aircraft operation.

2)

If a cruise schedule or descent schedule is not entered then a cruise or descent related to CRZ- Keyword will be chosen automatically by the Flight Planning program.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 30 of 168

Section 11 Keywords

KEYWORD : CRZ-

CRZ-

PURPOSE:

To override pre-stored cruise mode (ECON/LRC/MIN TIME), held in the ACATR file.

FORMAT:

CRZ-1 (indicate cruise number required)

EXAMPLE:

CRZ-3 (would give LRC)

ERROR MESSAGES: CFP-CRZ MUST BE NUMERIC 1, 3 or 5 ONLY

NOTE : 1)

The following cruise selections are available: 1 = Economic (given dry weight) 3 = Long Range (given dry weight) 5 = Minimum Time (given dry weight)

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)

CRZ- 3 - Will be the least fuel burn off.

5)

CRZ- 5 - Altitude/Flight Level is selected for min time regardless of operating costs and may be a significantly lower than normal Flight Profile or Terrain clearance.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 31 of 168

Section 11 Keywords

KEYWORD : CZF-

CZF-

PURPOSE:

To override the cruise fuel adjustment (degradation) factor held in the A/C attribute (ACATR) file.

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 manufacturer’s data.

2)

Some newer A/C may show an improvement over manufacturer’s 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 manufacturer’s hourly fuel flow by the specified amount.

4)

In Example 1) a fuel flow of say 10,000kg/hr would be increased by 2.5% to 10,250kg/hr.

5)

In Example 2) a fuel flow of 10,000kg would be decreased by 5% to 9500kg/hr.

6)

CZF- 1.000 will effect a calculation with no adjustment factor (degradation) applied, that is: basic unadjusted book values.

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%.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 32 of 168

Section 11 Keywords

KEYWORD : CZT-

PURPOSE:

Cruise thrust limit temperature override.

FORMAT:

CZT-

EXAMPLE:

CZT-P15 (plus 15) CZT-P0 (Zero)

ERROR MESSAGES: CZT CZT CZT

TOO LONG, MAXIMUM IS 3 CHARACTERS 1 DIGIT THEN MUST BE ZERO FORMAT - P OR M FOLLOWED BY 1-2 DIGITS, 1-20

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)

If zero Thrust Limit temperature correction required input P0 or 0.

4)

Temperature override value must be between zero and + 20 degrees.

5)

Use of values above P5 may cause a significant reduction in Altitude capability and thus in Payload/Range.

6)

The temperature buffer stored in the Airpolicy file is still applied even in still air and fixed temperature plans.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 33 of 168

Section 11 Keywords

KEYWORD : DMF-

PURPOSE:

Specification of Departure Manoeuvre Fuel

FORMAT:

DMF-

EXAMPLE:

DMF-2200 (Maximum 4 digits)

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)

If a Departure Manoeuvre value is already programmed for a specific customer, then the DMF input will provide fuel in addition to that value.

3)

DMF- & DMT- should not be used together.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 34 of 168

Section 11 Keywords

KEYWORD : DMT-

DMT-

PURPOSE:

Specification of Departure Manoeuvre Time

FORMAT:

DMT-

EXAMPLE:

DMT-05 (Maximum 2 digits - range 00 to 20) DMT-00 (For zero Departure Manoeuvre Time)

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)

DMF- & DMT- should not be input together.

3)

In Example 1 a departure manoeuvre time of 5 minutes is specified.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 35 of 168

Section 11 Keywords

KEYWORD : DPP-

PURPOSE:

To provide a facility to calculate a flight plan based on the DECISION POINT PROCEDURE as described in JAR OPS 1.255

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)

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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)

Instead of specifying a particular decision point it is possible to use an AUTO feature. If the decision point (reclear fix) is entered as AUTO the program will examine all preloaded ‘reclear fixes’ and associated ‘reclear’ routes stored in the Navigation database for the specified enroute alternate. An analysis is done based on route distances only, to identify the ‘reclear fix’ which should give the optimum effect, and a DPP plan will be based on this selected reclear fix. A message line will be shown a the top of the plans follows ***COMPUTER CALCULATED RECLEAR FIX*** (Note again the use of the term ‘reclear’ as common to DPP and RCR)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 37 of 168

Section 11 Keywords

KEYWORD : DRM-

PURPOSE:

Additional print of Dispatch Release Message

FORMAT:

DRM-

EXAMPLE:

DRM-Note that additional fuel has been requested

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)

Only one line is allowed per CFP request, up to 51 characters in length.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 38 of 168

Section 11 Keywords

KEYWORD : DSP-

PURPOSE:

To permit dispatchers name to print on the Flight Plan

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)

Each name may be up to 24 characters in length (alpha numerics acceptable) if two dispatchers names are required insert a slash (/) between the names.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 39 of 168

Section 11 Keywords

KEYWORD : DTE-

PURPOSE:

This keyword has two functions: (1) To calculate a flight plan using statistical weather instead of Forecast weather (see example 1-7) (2) To calculate a flight plan with an ETD earlier than the time of the request or more than 24 hours ahead

FORMAT:

DTE-

EXAMPLE: 1) 2) 3) 4) 5) 6) 7)

DTE-FEB (Months – first three letters) DTE-QTR1 (Quarterly 1st 2nd 3rd 4th) DTE-JANJUN (Average of the period January to June)* DTE-JULDEC (Average of the period July to December)* DTE-SUM (Summer months April to September) DTE-WIN (Winter months October to March) DTE-YEAR (whole year)

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 day’s 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"

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 40 of 168

Section 11 Keywords

KEYWORD : ECT-

PURPOSE:

To elect ROUTE(S)/EXIT NUMBER(S) thereby limiting the best route search to specific ROUTE(S)/EXIT NUMBER(S)

FORMAT:

ECT- (4 or 5 numerics per block separated by a slash, maximum 12 blocks)

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)

In the EXAMPLE, only EXIT NUMBERS 10236/5624/1483 will be searched to provide the best route. All other EXITS in the City Pair number (sector) will be ignored.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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:

EEP- (followed by the Entry airport ICAO or IATA code. Following a “/” the Exit airport may be entered).

EXAMPLE: 1) 2)

EEP-FMEE (FMEE used as Entry Airport). EEP-FMEE/VABB (FMEE used as Entry and VABB used as Exit Airport).

ERROR MESSAGES: EEP EEP EEP EEP EEP EEP

NO AIRPORT AFTER EEP ENTRY/EXIT AIRPORTS CANNOT BE THE SAME ZZZZ IS NOT A LOADED AIRPORT REQUIRES AN ETP OR ETX INPUT XXXX CANNOT BE THE ENTRY AIRPORT AND DESTINATION YYYY CANNOT BE THE EXIT AIRPORT AND ORIGIN

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 aircraft’s 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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 42 of 168

Section 11 Keywords

KEYWORD : EQP

EQP-

PURPOSE:

To specify the detail required to be filed as Item 10 in the ICAO plan for the CFP being requested. The code input will override the ITEM 10 detail loaded in the Attribute file for the aircraft specified in the CFP request..

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 43 of 168

Section 11 Keywords

KEYWORD : EQT-

EQT-

PURPOSE:

To define the Equi-Time Point for administrative (4 engines) and ETOPS purposes (engine out). If engine out performance data is stored with SITA (see ETP- ETX-)

FORMAT:

EQT-

EXAMPLE:

EQTEQT-EINN/LPLA/T390/L100/F04000

ERROR MESSAGES: EQT EQT EQT EQT EQT EQT EQT EQT EQT EQT EQT

ONLY ONE OF EQT, ETP OR ETX ALLOWED ONLY 10 LINES MAY BE ENTERED UNRECOGNISABLE FORMAT MISMATCH OF AIRPORTS IN SUCCESSIVE ENTRIES SPEED OUTSIDE LIMITS 100 - 600 KTS LEVEL OUTSIDE LIMITS 010 - 490 TOO MANY PARAMETERS ENTERED NOT ENOUGH PARAMETERS ENTERED AIRPORT (V) NOT FOUND ON AIRPORT DATABASE FUEL FLOW OUTSIDE LIMITS 00454 TO 18144 KGS FUEL FLOW OUTSIDE LIMITS 01000 TO 25000 LBS

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).

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 44 of 168

Section 11 Keywords

KEYWORD :

ERA-

ERA-

PURPOSE:

To define an En–Route Alternate or a JAR-0PS 3% ERA.

FORMAT:

ERA-

EXAMPLE:

ERA-EGCC

(Either in ICAO or IATA format)

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

OR 4 CHAR ICAO CODE ICAO OR IATA AIRPORT CODE RVN RVT RVF RCR

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)

ERA cannot be used with a Reclear flight plan.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 45 of 168

Section 11 Keywords

KEYWORD : ETA-

ETA-

PURPOSE:

To amend stored Estimated Time of Arrival

FORMAT:

ETA- (4 numerics)

EXAMPLE:

ETA-1500 (24 hr clock)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 46 of 168

Section 11 Keywords

KEYWORD : ETD-

ETD-

PURPOSE:

To amend stored Estimated Time of Departure

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)

Mandatory input if /9999 parameter screen is used.

2)

CFP requests received after the ETD- will be calculated using next day's weather.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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:

ETE-AAAA/BBBB (Either in ICAO or IATA format) ETE-AAAA/BBBB/I -applies the Icing correction ETE-AAAA/BBBB/1.025 -applies/overrides the degradation factor ETE-AAAA/BBBB/300 –applies/overrides the diversion KIAS (see note 4) ETE-AAAA/BBBB/L150 –applies/overrides the diversion flight level (see note 4)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

ETE-

Flight Planning Reference Manual

Page 48 of 168

Section 11 Keywords

KEYWORD : ETP-

PURPOSE:

This Keyword is specifically provided for Extended Range (Twin Engine A/C) Operation - ETOPS. (see also Keyword ETX-) It provides for the calculation of the Equ-Time Point (as for Keyword EQT-) and to dynamically calculate the fuel to the airports specified in the Keyword, including a provision to apply Icing factors and degradation to the calculated fuel.

FORMAT:

ETP-

EXAMPLE:

1) 2) 3) 4) 5) 6) 7)

ETP-HKNA/FIMP - see note (1) ETP-HKNA/FIMP/I - see note (2) ETP-HKNA/FIMP/1.025 - see note (3) ETP-HKNA/FIMP/300 - see note (4) ETP-HKNA/FIMP/L120 - see note (5) ETP-HKNA/FIMP/300/I/1.05/L120 - see note (6) ETP-HKNA/FIMP/T120 – see note (8)

ERROR MESSAGES: ETP ETP ETP ETP ETP ETP ETP ETP ETP ETP ETP

ONLY ONE OF EQT, ETP OR ETX ALLOWED INVALID FORMAT, PARAMETERS REQUIRED ONLY 10 LINES ARE ALLOWED UNRECOGNISABLE FORMAT MISMATCH OF AIRPORTS IN SUCCESSIVE LINES NUMBER OF ENGINES MUST BE 1 - 3 SPEED SCHEDULE MUST BE 100 - 600 KIAS OR 999 FLT LEVEL MUST BE IN RANGE 090 - 490 DEGRDN FACTOR MUST BE FORMAT 9.999 (0.500 - 2.000) AIRPORT (V) NOT FOUND ON AIRPORT DATABASE ENGINE OUT DATA NOT HELD FOR AIRCRAFT

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.

Flight Planning Reference Manual

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)

It is possible to include all or any combination of the additional parameters to the basic ETP- input shown in the first Example.

6)

If an Equi-Time Point (EQT-) between Origin and Destination is also required on a Flight Plan that utilises the ETP- facility, then Keyword EQT- must be included in the CFP request. No other parameters should follow the (-) of EQT-.

7)

The example shows the default Rule Time has been overridden by a requirement to use 120 mins for that alternate pair.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 50 of 168

Section 11 Keywords

KEYWORD : ETX-

ETX-

PURPOSE:

As for Keyword ETP- but where it is necessary that any shortfall of fuel required for an ETOPS Alternate, compared to the calculated Flight Plan fuel at the Equi-Time Point will cause the Flight Plan to be recalculated with the required fuel being added to the total Flight Plan fuel. The resultant fuel on board at any Equi-Time Point will, therefore, always be sufficient to meet the most critical fuel scenario, even if a reduction of payload is necessary.

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

see note (1) see note (2) see note (3) see note (4) see note (5) see note (6) see note (8) ETP

ERROR MESSAGES: ETX ETX ETX ETX ETX ETX ETX ETX ETX ETX ETX

ONLY ONE OF EQT, ETP OR ETX ALLOWED INVALID FORMAT, PARAMETERS REQUIRED ONLY 10 LINES ARE ALLOWED UNRECOGNISABLE FORMAT MISMATCH OF AIRPORTS IN SUCCESSIVE LINES NUMBER OF ENGINES MUST BE 1 - 3 SPEED SCHEDULE MUST BE 100 - 600 KIAS OR 999 FLT LEVEL MUST BE IN RANGE 090 - 490 DEGRDN FACTOR MUST BE FORMAT 9.999 (0.500 - 2.000) ENGINE OUT DATA NOT HELD FOR AIRCRAFT AIRPORT (V) NOT FOUND ON AIRPORT DATABASE

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 51 of 168

Section 11 Keywords

KEYWORD : ETX-

(continued) 3)

The Example shows a degradation of 2.5 percent needs to be applied to the calculated Alternate fuels. For the ETX- Alternate, this adjustment overrides the degradation loaded in the ACATR file.

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)

It is possible to include all or any combination of the additional parameters to the basic ETX- input shown in the first Example.

7)

If an Equi-Time Point (EQT) between Origin and Destination is also required on a Flight Plan that utilises the ETX- facility, then Keyword EQT- must be included in the CFP request. No other parameters should follow the (-) of EQT-

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 52 of 168

Section 11 Keywords

KEYWORD : EXT-

PURPOSE:

Selection of a specific EXIT (route)

FORMAT:

EXT- (1 to 6 numerics)

EXAMPLE:

EXT-10123

ERROR MESSAGES: EXT EXT EXT EXT

MUST BE NUMERIC, MAXIMUM 6 DIGITS MUST NOT BE ENTERED WITH CPN 999999 ROUTE SPECIFIED, (V) IS INVALID FOR SECTOR AIRPORT (V) NOT FOUND ON AIRPORT DATABASE

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 53 of 168

Section 11 Keywords

KEYWORD : FAA-

PURPOSE:

Production of ICAO FAA Domestic plan appended to the main Flight plan.

FORMAT:

FAA-

EXAMPLE:

FAA-

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 54 of 168

Section 11 Keywords

KEYWORD : FAL-

PURPOSE:

Used to fix an altitude/flight level

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)

Terrain clearance is not checked.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 55 of 168

Section 11 Keywords

KEYWORD : FAX-

FAX-

PURPOSE:

To provide the ability to send Calculated Flight Plan (CFP) or send a Repeat Flight Plan (RFP) by facsimile (FAX).

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)

Where 11 is Country Code.

2)

Where 22 is Area Code, if any.

3)

Where 3334444 is the facsimile number.

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)

Each Plan will arrive without a Header page.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 56 of 168

Section 11 Keywords

KEYWORD : FCD-

FCD-

PURPOSE:

Provides application of fuel cost to the Flight Plan calculation.

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

.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 57 of 168

Section 11 Keywords

KEYWORD : FCO-

PURPOSE:

Provides application of fuel cost to the Flight Plan calculation

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)

This Keyword relates to economic cruise (CRZ-1) and is involved in the calculation of COST INDEX. It must be accompanied with either a Cost Index or an Hourly Cost. These values can be entered by Keyword or held on the aircraft files as defaults. For Econ Cruise calculations see CID- in this section.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 58 of 168

Section 11 Keywords

KEYWORD : FLT-

FLT-

PURPOSE:

Amendment of loaded flight number

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)

Print out of alpha/numerics beyond 4 is format dependant.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 59 of 168

Section 11 Keywords

KEYWORD : FMA-

FMA-

PURPOSE:

Used to change or fix a Mach number.

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)

FAL takes precedence over FMA.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 60 of 168

Section 11 Keywords

KEYWORD : FMT-

PURPOSE:

Allows access of parts of an already calculated and delivered Flight Plan.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 61 of 168

Section 11 Keywords

KEYWORD : FXH-

PURPOSE:

FORMAT:

EXAMPLE:

Provision of fixed height Flight Plan profile by waypoint name.

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

HEIGHT (V) INVALID, MUST BE 000-490 WAYPT (V) NOT FOUND ON ROUTE (V), OR NON-COMPULSORY HT (V) MUST BE ABOVE MIN CRZ LVL OF (V) FOR (V) WAYPOINT (V) MUST BE BETWEEN 1 AND 5 CHARACTERS LONG WAYPOINT (V) NOT ENTERED IN ROUTE SEQUENCE ORDER YOU CANNOT USE "TOD" OR "TOC" OR "FIR" AS FXH WAYPTS TOO LONG, ONLY 6 PAIRS ALLOWED

NOTE : 1)

This Keyword affords the user the facility to define a height/FL profile by waypoint name.

2)

The FL specified is to be calculated as a 'fixed' level and is to be calculated in the same way as FAL and must adhere to the cruise tables. 000 is a request for optimum flight level.

3)

In the Example: i)

FXH-260/MONDO/330/SPR/370/LAGEN/000

TOC at FL260 to waypoint MONDO then FL330 from waypoint MONDO to waypoint SPR, then FL370 from waypoint SPR to waypoint LAGEN, then optimum FL from waypoint LAGEN to TOD. Flight level may be defined for up to 6 (six) segments of the route and these may be split onto two separate lines if necessary. ii)

Flight levels printed out will conform to ATC available levels.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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)

Terrain clearance is not checked.

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 accepted LAT/LONG format for FXH is seven characters

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

-------------------------------------------------------------------------------PFKEYS: 7/19:BRSE BWD 8/20:BRSE FWD 10:BOT 11:TOP 3/15:PREVIOUS SCREEN

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 63 of 168

Section 11 Keywords

KEYWORD: FXM

FXM

PURPOSE:

Provision of fixed speed flight plan profile by waypoint name.

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

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 65 of 168

Section 11 Keywords

KEYWORD : HDA-

PURPOSE:

Holding height and time at the final Destination Alternate.

FORMAT:

HDA-

EXAMPLE:

HDA-230/025 (Holding height FL230, time 25 mins)

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)

Holding fuel is assumed to be included in the landed fuel reserves.

4)

The time parameter must always be 3 digits; if necessary add leading zeroes. i.e. for 25 mins, input 025.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 66 of 168

Section 11 Keywords

KEYWORD : HDB-

PURPOSE:

Holding height and time at the Reclear Alternate.

FORMAT:

HDB-

EXAMPLE:

HDB-250/010 (Holding height FL250,time 10 mins)

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)

A holding time must always be supplied.

3)

Holding fuel is assumed to be included in the landed fuel reserves.

4)

The time parameter must always be 3 digits; if necessary add leading zeroes. i.e. for 25 mins, input 025.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 67 of 168

Section 11 Keywords

KEYWORD : HDD-

PURPOSE:

Holding height and time at the final Destination.

FORMAT:

HDD-

EXAMPLE:

HDD-110/015 (Holding height FL110,time 15 mins)

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).

6) Holding fuel is assumed to be included in the landed fuel reserves. 7) The time parameter must always be 3 digits; if necessary add leading zeroes. i.e. for 25 mins, input 025.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 68 of 168

Section 11 Keywords

KEYWORD : HDR-

PURPOSE:

Holding height and time at the Reclear Destination Airport.

FORMAT:

HDR-

EXAMPLE:

HDR-150/020 (Holding height FL150,time 20 mins)

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)

A holding time must always be supplied.

3)

Holding fuel is assumed to be included in the landed fuel reserves.

4)

The time parameter must always be 3 digits; if necessary add leading zeroes. i.e. for 25 mins, input 025.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 69 of 168

Section 11 Keywords

KEYWORD : HLD-

PURPOSE

Enables Holding Fuel/Time held on file to be overridden.

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)

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 70 of 168

Section 11 Keywords

KEYWORD : HNL-

PURPOSE:

To define required Oceanic Track in a Flight Plan, or to specify a daily HNL track in the OTS.

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

MAY NOT BE USED WHEN NAT, PAC OR AUS KEYWORDS ENTERED USE A, B, 11, OR 12 FOR HONOLULU ROUTES MUST NOT BE ENTERED WITH CPN 999999 NOT VALID WITH AUTO OR AUTP USE A SINGLE LETTER ON HONOLULU TRACKS INVALID FORMAT (V) USE N OR S 2 DIGITS / W OR 3 DIGITS EG- N12/W123 FLIGHT LEVEL PREFIX MUST BE 1,2,W, OR E NO LAT/LONG AVAILABLE FOR THIS TRACK MORE THAN 20 LAT/LONGS ENTERED LATITUDE NOT BETWEEN 00 AND 80 LATITUDES (V) AND (V) NOT WITHIN 15 DEGREES LONGITUDES MUST BE HEADING IN SAME DIRECTION LONGITUDE (V) NOT BETWEEN 100 AND 180 LONGITUDE (V) NOT A MULTIPLE OF 5 LONGITUDES MAY NOT BE EQUAL ((V)) LONGITUDES (V) AND (V) NOT WITHIN 15 DEGREES

NOTE :

A maximum of 7 co-ordinates per line up to a maximum of 20 in total. 1)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 72 of 168

Section 11 Keywords

KEYWORD : HOC-

HOC-

PURPOSE:

Provides application of hourly operating costs to the Flight Plan calculation

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)

This Keyword relates to economic cruise (CRZ-1) and is involved in the calculation of COST INDEX. Cost must be between 00000.01 and 99999.99.

2)

The cost used is the summation of those operating costs which are time dependant but exclude fuel cost.

3)

For Econ Cruise calculations see CID- in this Section

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 73 of 168

Section 11 Keywords

KEYWORD : HRA-

PURPOSE:

Race track adjustment factor to apply to holding fuel flow.

FORMAT:

HRA-

EXAMPLE:

1) 2)

HRA-0.9 (Fuel flow 90% of filed value) HRA-1.4 (Fuel flow 140% of filed value)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 74 of 168

Section 11 Keywords

KEYWORD : HTA-

PURPOSE:

ISA temperature adjustment percentage factor to apply to holding fuel flow

FORMAT:

HTA-

EXAMPLE:

1)

HTA-0.002 (Fuel flow increased/decreased by 0.002% per 5 degrees)

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)

No correction is applied to negative air temperature

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 75 of 168

Section 11 Keywords

KEYWORD : IAS-

PURPOSE:

Used to change the Cruise speed up to a defined flight level.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 76 of 168

Section 11 Keywords

KEYWORD : LTT-

PURPOSE:

Request for a Least Time Track between any 2 airports loaded in Data Base. The resultant plan will contain a non flyable route showing only crossing positions at each intervening 10 degrees of Longitude

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 77 of 168

Section 11 Keywords

KEYWORD : M-

PURPOSE:

Provision of Free Form Message lines

FORMAT:

M-

EXAMPLE:

M-NON STANDARD FUEL RESERVES M-PLEASE REFER TO NOTAM REF XXX M-R/WY LENGTH AT DEST XXXX IS XXXX M

ERROR MESSAGES: CFP-INVALID MSG LINE

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)

Use of a continuous series of dots, dashes, or the inclusion of a series of slashes (/) or commas (,) should be avoided. This will corrupt input format and produce error messages.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 78 of 168

Section 11 Keywords

KEYWORD : MAD-

PURPOSE:

Override of screen loaded addresses

FORMAT:

MAD-

EXAMPLE:

MAD-CDGOWXX JFKOKXX CAIOWXX (7 letter maximum of 6 addresses)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 79 of 168

Section 11 Keywords

KEYWORD :

MFU-

PURPOSE:

To define a maximum amount of tank fuel to be used in the CFP calculation, the value will override the maximum tank weight in the Aircraft Attribute file but cannot exceed it.

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)

The purpose of this keyword is to allow a flight calculation to be made and therefore a payload to be determined with a fuel amount which is less than the maximum value held in the aircraft database.

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)

As MFU is in units of weight, the maximum volume of fuel used by the program will be the MFU value converted to volume at the fuel S.G used in the CFP calculation.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 80 of 168

Section 11 Keywords

KEYWORD : MOA-

PURPOSE:

To provide a minimum fuel over the Alternate.

FORMAT:

MOA-

EXAMPLE:

MOA-4500 (Max 6 numerics).

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 81 of 168

Section 11 Keywords

KEYWORD : MOD-

PURPOSE:

To provide a minimum fuel over the Destination.

FORMAT:

MOD-

EXAMPLE:

MOD-4000 (Max 6 numerics)

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)

Fuel over Destination is comprised of several elements: eg. Holding/Alternate fuel etc. If this total fuel over destination falls short of the minimum specified, then a differential value will be added to bring it up to the minimum requested.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 82 of 168

Section 11 Keywords

KEYWORD : MTF-

PURPOSE:

Initiate calculation of a Flight Plan based on a fixed amount of fuel on board. If the fuel required is more than this fixed amount MTF will be ignored.

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 :

Keyword designed to cater for the situation when: 1)

A given quantity of fuel is already in tanks and a Flight Plan is required based on this existing parameter.

2)

A specified fuel uplift is desired.

3)

Limitation is ignored when MTF is insufficient for the flight.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 83 of 168

Section 11 Keywords

KEYWORD : MVD-

PURPOSE:

To override existing destination manoeuvering distance

FORMAT:

MVD-

EXAMPLE:

MVD-26 (MAX 3 NUMERIC)

ERROR MESSAGES: MVD MUST BE NUMERIC, MAXIMUM 3 DIGITS MVD ONLY ONE OF MVD AND MVF ALLOWED

NOTE :

1)

To delete a distance completely use MVD-0. Also see MVT-.

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)

In the Example a destination manoeuvering distance of 26 NMS is requested.

4)

MVF- & MVD- cannot be used together.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 84 of 168

Section 11 Keywords

KEYWORD : MVF-

PURPOSE:

To enable customer to specify Destination Manoeuvre Fuel

FORMAT:

MVF-

EXAMPLE:

MVF-1200

(3 to 5 numerics in range 100-50000)

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)

In the Example a destination manoeuvre fuel of 1200 KGS/LBS (units dependent on format specification) is requested.

3)

MVF- & MVD- cannot be used together.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 85 of 168

Section 11 Keywords

KEYWORD : MVT-

PURPOSE:

To specify Destination Manoeuvre Time

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)

It is not fuel related.

3)

In the Example the request specifies a Destination Manoeuvre Time of 10 minutes.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 86 of 168

Section 11 Keywords

KEYWORD : MZF-

PURPOSE:

To specify a Maximum Permissible Zero Fuel Weight for the aircraft to replace that in the Aircraft Attribute (ACATR) file.

FORMAT:

MZF-

EXAMPLE:

MZF-232500 (1 to 6 numerics; leading zeroes not required)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 87 of 168

Section 11 Keywords

KEYWORD : NAT-

PURPOSE:

To define required oceanic track in a Flight Plan, or to specify a published NAT in the OTS, or to request best NAT track selection as a plan or summary.

FORMAT:

1) 2) 3) 4)

NATNAT-A NAT-AUTO NAT-AUTP

EXAMPLE:

1) 2)

NAT-50/10 52/20 52/30 54/40 55/50 NAT-W 50/10 52/20 52/30 54/40 55/50

ERROR MESSAGES: NAT NAT NAT NAT NAT NAT NAT NAT NAT NAT NAT NAT NAT NAT NAT NAT NAT NAT NAT NAT

MAY NOT BE USED WITH HNL, PAC OR AUS KEYWORDS MUST NOT BE ENTERED WITH CPN 999999 ECT KEYWORD MUST ALSO BE USED ECT KEYWORD CANNOT BE USED WITH AUTO OR AUTP 2 ECT VALUES MUST BE ENTERED (ENTRY/EXIT) LATITUDE (V) NOT BETWEEN 10N & 80N LATITUDES (V) AND (V) NOT WITHIN 15 DEGREES LONGITUDE (V) NOT 08, 13 OR MULTIPLE OF 5 LONGITUDES MAY NOT BE EQUAL ((V)) LONGITUDES (V) AND (V) NOT WITHIN 15 DEGREES LONGITUDES MUST EITHER BE ASCENDING OR DESCENDING UNRECOGNISABLE INPUT FORMAT (V) INVALID CPN (V) ASSOCIATED WITH AUTO OR AUTP USE SINGLE LETTER W OR E FOR N.ATLANTIC TRACKS FLIGHT LEVEL PREFIX MUST BE 1 OR 2 FORMAT SHOULD BE 2 DIGITS/2DIGITS CO-ORDS SHOULD BE SEPARATED BY A SPACE NO LAT/LONG AVAILABLE FOR THIS TRACK MORE THAN 20 LAT/LONGS ENTERED INVALID CPN, (V) ASSOCIATED WITH AUTO OR AUTP

(continued)

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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)

Format input is a series of 2 numerics/2 numerics groups each group separated by a space, maximum of 8 groups per line, with maximum of 20 groups. (each line must be preceded with Keyword NAT- (or NAT-W or NAT-E) Difference in latitude must not exceed 15 between successive groups. (Longitude inputs must be in multiples of 5 (exceptionally, 08 and 13 are accepted). Latitudes are assumed to be North, with range between 10N and 80N. All Longitudes are assumed to be West.

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)

Format 4 specifying AUTO is to request a summary showing order of best NAT track, next best etc; with associated EXIT and ENTRY routes.

7)

Format 5 specifying AUTP has the same function as AUTO, plus the plan is produced utilizing the best NAT track, EXIT and ENTRY.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 89 of 168

Section 11 Keywords

KEYWORD : NM1-

PURPOSE:

Printing Crew names

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)

Up to 9 names can be printed per CFP request (NM1-NM9)

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 90 of 168

Section 11 Keywords

KEYWORD: NTMPURPOSE:

Enables Route Specific NOTAMs to be requested from within the CFP request.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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.

•

Both Airport and FIR data will be included.

•

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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)

Example 1 produces 3700 units of fuel.

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)

This value is not a calculated quantity.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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:

OAR-10200 (Must be max of 5 numerics Kgs/Lb) OAR-6500/20 (includes override time of 20 mins)

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)

Example 1 produces 10200 units of fuel.

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)

This value is not a calculated quantity.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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)

OFC- will produce a single line total amount converted to USD.

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)

The calculation is made using the actual route flow.

4)

The option to use published Eurocontrol fixed distances is in development.

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).

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 95 of 168

Section 11 Keywords

KEYWORD : OWE-

OWE-

PURPOSE:

To specify operating weight empty of a given aircraft

FORMAT:

OWE-

EXAMPLE:

OWE-168500 (1 to 6 numerics leading zeros not required)

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)

Inputs below stored OWE are accepted to a maximum of 10%.

5)

The sum of OWE and PLD cannot be less than stored OWE.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 96 of 168

Section 11 Keywords

KEYWORD : PAC-

PAC-

PURPOSE:

To define required Oceanic Track in a Flight Plan, or to specify a published PAC in the OTS.

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

MAY NOT BE USED WITH NAT,AUS OR HNL KEYWORDS MUST NOT BE ENTERED WITH CPN 999999 UNRECOGNISABLE INPUT FORMAT INVALID CPN (V) ASSOCIATED WITH AUTO OR AUTP USE SINGLE LETTER FOR PACIFIC TRACKS FORMAT IS N OR S 2 DIGITS/W OR E 3 DIGITS FLIGHT LEVEL PREFIX MUST BE 1 OR 2 CO-ORDS SHOULD BE SEPARATED BY A SPACE NO LAT/LONGS AVAILABLE FOR THIS TRACK MORE THAN 20 LAT/LONGS ENTERED LATITUDE (V) NOT BETWEEN 00 AND 80 LATITUDES (V) & (V) NOT WITHIN 15 DEGREES LONGITUDES MUST BE HEADING IN SAME DIRECTION LONGITUDE (V) NOT BETWEEN 100 AND 180 DEGREES LONGITUDE (V) NOT A MULTIPLE OF 5 LONGITUDES MAY NOT BE EQUAL ((V))

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)

A maximum of 7 Co-ordinates per line up to a maximum of 20 in total.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 97 of 168

Section 11 Keywords

KEYWORD : PIC-

PURPOSE:

To file an ICAO ATC Plan or send it to a SITA address or addresses as a separate message.

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)

Example 1 indicates IFR flight plan, Non-Scheduled and 1 is to remove numbering from the ATC plan items.

4)

Example 2 is sending an IFR Scheduled plan to more than one address.

This is for sending to SITA addresses only and can be used with Type B, GraFlite and QLLC.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 98 of 168

Section 11 Keywords

KEYWORD : PLD-

PURPOSE:

Specification of Payload required

FORMAT:

PLD-

EXAMPLE:

PLD-23160 (1 to 6 numerics, leading zeros not required)

ERROR MESSAGES: PLD PLD PLD PLD

MUST BE NUMERIC, MAX 6 DIGITS NOT ALLOWED IF ZFWT = 999999 MUST NOT BE GREATER THAN ZFWT MINUS OWE GREATER THAN ZFWT OF (V)

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)

In the Example a Payload of 23160 is requested.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

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

HEIGHT (V) INVALID, MUST BE 000-490 WAYPT (V) NOT FOUND ON ROUTE (V), OR NON-COMPULSORY HT (V) MUST BE ABOVE MIN CRZ LVL OF (V) FOR (V) WAYPOINT (V) MUST BE BETWEEN 1 AND 5 CHARACTERS LONG WAYPOINT (V) NOT ENTERED IN ROUTE SEQUENCE ORDER YOU CANNOT USE "TOD" OR "TOC" OR "FIR" AS PRF WAYPTS TOO LONG, ONLY 6 PAIRS ALLOWED

NOTE : 1)

This Keyword affords the user the facility to define a height/FL profile by waypoint name overriding normal cruise table rules.

2)

When a flight level input on the PRF- keyword can't be achieved for performance reasons then the program should produce the next valid* flight level achievable until such a time that the level specified can be met.(*valid flight level meaning a flight level available with respect to the cruise tables applicable for the route.)

3)

In the Example: i) PRF-260/MONDO/330/SPR/370/LAGEN/000

TOC at FL260 to waypoint MONDO then FL330 from waypoint MONDO to waypoint SPR, then FL370 from waypoint SPR to waypoint LAGEN, then optimum FL from waypoint LAGEN to TOD. Flight level may be defined for up to 6 (six) segments of the route.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 100 of 168

Section 11 Keywords

KEYWORD : PRF(Continued) ii)

iii) iv) 4)

FAL- keyword may be used, but this will only limit the flight level in the optimum segment of the Flight Plan. Terrain clearance is not checked. Metric levels can be used on PRF inputs.

In the example: i)

PRF-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) 5)

The accepted LAT/LONG format for PRF is seven characters.

When this keyword is used a warning message will be printed on the flight plan to advise the dispatcher and crew that the normal flight level selection, according to ICAO separation/flight level rules, have been overridden e.g.

***NORMAL FLIGHT LEVEL SELECTION OVERRIDDEN BY DISPATCHER BY USE OF PRF- KEYWORD ON CFP INPUT***

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 101 of 168

Section 11 Keywords

KEYWORD : PRI-

PURPOSE:

Override Type B message priority indicator code on the following transactions:. CFP, NDP,(covering CPN,NVP,ALT,ADP), PRM, ACD This is used to give a lower priority only, as the highest priority QU will be used automatically. QN – normal QD – deferred

FORMAT:

PRI-

EXAMPLE:

PRI-QD

ERROR MESSAGES: PRI (V) INVALID, MUST BE 2 CHARS, QU, QN or QD NOTE :

1)

All Computer transactions are normally assigned QU to ensure priority delivery.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 102 of 168

Section 11 Keywords

KEYWORD : PSW-

PURPOSE:

Used for security checking on selected applications, in conjunction with the Airline ID. Minimum 4 characters alphabetic A-Z or numeric 0-9 only.

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)

This is used on applications on which security checking is performed at airline level.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 103 of 168

Section 11 Keywords

KEYWORD : RA2-

PURPOSE:

Summary of flight details for a second selected Reclear Alternate. Three options are available.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 104 of 168

Section 11 Keywords

KEYWORD : RA3-

PURPOSE:

Summary of flight details for a third selected Reclear Alternate. Three options are available.

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)

/P or /S are is only available if there is a route or routes built between the Reclear destination and the alternate airport.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 105 of 168

Section 11 Keywords

KEYWORD : RCA-

PURPOSE:

To cap altitude/flight level between Reclear Initial airport and related Alternate airport.

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)

Terrain clearance is not checked.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 106 of 168

Section 11 Keywords

KEYWORD : RCR-

PURPOSE:

Specifying reclear parameters and if required obtain a print out of the route to the alternate.

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

NOT VALID WITHOUT PARAMETERS REQUIRED IF NO AWYFIX IS SPECIFIED INITIAL AIRPORT MUST BE 3 CHAR IATA OR 4 CHAR ICAO ALT MUST BE 3 CHAR IATA OR 4 CHAR ICAO ALT MUST BE IN FORMAT XXX/9999 OR XXXX/9999 ROUTE, IF ENTERED MUST BE MAX 6 DIGITS AWYFIX IS INVALID, MUST BE 2-6 ALPHA/NUMERIC LANDING WEIGHT MUST BE NUMERIC, UP TO 6 DIGITS RECLEAR ICAO/IATA MUST BE ENTERED DEST IATA CODE - (V) NOT FOUND FOR AIRLINE DEST ICAO CODE - (V) NOT FOUND FOR AIRLINE ALTERNATE - (V) NOT VALID FOR DEST - (V)

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).

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 107 of 168

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)

Instead of specifying a particular reclear fix it is now possible to use an AUTO feature. If the reclear fix is entered as AUTO the program will examine all preloaded reclear fixes and associated reclear routes stored in the Navigation database for the specified initial airport. An analysis is done based on route distances only, to identify the reclear fix which should give the optimum effect, and a reclear plan will be based on this selected reclear fix. A message line will be shown a the top of the plans follows

***COMPUTER CALCULATED RECLEAR FIX*** Additionally this request can be expanded to allow up to five Initial Destination/Alternate pairings. The system will compare the results and select the optimum: EXAMPLE:

RCR-GCLP/LPFR/AUTO RCR-GCVV/GMMN/AUTO RCR-GCTS/GMAD/AUTO RCR-LPFR/LEMD/AUTO RCR-LPPT/LPPO/AUTO

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 108 of 168

Section 11 Keywords

KEYWORD : RC1-

PURPOSE:

Specifying Reclear parameters (Oceanic)

FORMAT:

RC1-

EXAMPLE:

RCR-EGLL/EGKK RC1-50.00N/020.00W/001374

ERROR MESSAGES: RC1 RC1 RC1 RC1

LATITUDE MUST BE 99.999, N OR S FORMAT IS 99.99N/99.99E OR 99.999N/99.999E LONGITUDE MUST BE 99.99 OR 99.999, E OR W OCEANIC EXIT ROUTE MUST BE 5 OR 6 DIGITS

NOTE : 1)

This is a multi parameter Keyword. If used it will be entered in conjunction with the RCR- input Keyword. It specifies the particular oceanic point from which reclearance is to occur as a latitude and longitude. From that point a least time track to a specified exit related to the Initial Airport will be made. The final parameter is the number of the exit orientated along the likely reclearance track. Example: 50.00N/020.00W/001374 Example shows a reclearance point of 50.00 degrees North and 020.00 degrees West with an exit number of 001374 . If the RC1- code is used then reclear fix (parameter three) of RCR- code is not required.

2)

An Example of RCR- and RC1- codes together is: RCR-EGLL/EGKK RC1-50.00N/020.00W/001374 Here an ocean reclear point of 50.00 degrees North and 020.00 degrees West is required with an Initial Airport of EGLL using EGKK as its alternate specifying EXIT 001374 to EGLL from the reclearance point.

3)

Run a non-reclear Random FLT PLN over the sector, to enable a Reclear point to be determined.

4)

Ensure initial Airport is defined in ICAO code (4 alphas).

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 109 of 168

Section 11 Keywords

KEYWORD : RFX-

PURPOSE:

Specification of a Fixed Fuel Reserve

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)

WARNING, THIS KEYWORD OVERRIDES EXISTING LOADED RESERVE FUEL POLICY.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 110 of 168

Section 11 Keywords

KEYWORD : RLW-

PURPOSE:

Restriction of Landing Weight

FORMAT:

RLW(Entered as weight value in units - max 6 digits)

EXAMPLE:

RLW-255400 (to request 255400 KGS/LBS)

ERROR MESSAGES: RLW RLW RLW RLW

MUST BE MAX 6 DIGITS, GREATER THAN 0 EXCEEDS MAX LANDING WGT OF (V) FOR (V) MUST NOT BE LESS THAN OWE VALUE LESS THAN MIN ZFWT OF (V) FOR (V)

NOTE : 1)

Use if Max. Structural Landing Weight is not permitted. In the Example, a Restricted Landing Weight of 255400 KGS/LBS is specified.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 111 of 168

Section 11 Keywords

KEYWORD :

PURPOSE:

RMN-

To specify a minimum amount of reserve/contingency fuel.

FORMAT:

EXAMPLE::

RMN-

RMN-1000 (1-5 numerics leading zeros not required)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 112 of 168

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.

RTE and DTE must be included if RNY used. Re-Analysis point does not have to be on the original flight plan. ALT mandatory if destination changes. 4. If first airway on RTE input is DCT then second airway must be a published airway and if the first waypoint name is duplicated in the station file then the one with the least distance is used. 5. If the first two consecutive airway inputs are DCT then first waypoint must be a Latitude Longitude or else an error message sent.

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

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 113 of 168

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

ETP ETX FAA RA3 RCA RCR

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

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

HLD

HRA

HTA

MOA

Flight Planning Reference Manual

Page 114 of 168

Section 11 Keywords

KEYWORD : RRG-

PURPOSE:

To generate a Route automatically between any two airports in the database. If RRG- is used the stored Routes are ignored. (Realtime Route Generator)

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)

RRG- (Minimum input for Automatic Route Build).

Parameters that are possible and the meanings are as follows:VIA-DEP/CPT3G

Via departure specified.

VIA-DEP/MAX

Maximum distance departure procedure (or MIN )

VIA-WPT/LOGAN

Via waypoint specified – if that waypoint is unique

VIA-WPT/WOD/EUR/EG

Via waypoint specified – if that waypoint is not unique

VIA-WPT/WOD/EUR/EG/D

Via waypoint which is not unique – and is a VOR (where there is an NDB with the same name)

VIA-WPT/WOD/EUR/EG/DB

Via waypoint which is not unique – and is an NDB (where there is an NDB with the same name)

VIA-SEG/WPT/AWY/WPT

Via segment or segments of an airway specified

VIA-NAT

Via NAT tracks. Other tracks available eg PAC/AUS

VIA-NAT/A

Via a particular track e.g. NAT Track A

VIA-ARR/MAX

Maximum distance arrival procedure (or MIN)

VIA-ARR/CPT3G

Via departure specified.

EXC-WPT/LOGAN

Exclude waypoint specified – if that waypoint is unique

EXC-WPT/WOD/EUR/EG

Exclude waypoint specified – if waypoint is not unique

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 115 of 168

Section 11 Keywords

EXC-AWY/UM601

Exclude airway specified

EXC-SEG/WPT/AWY/WPT Exclude segment or segments of an airway specified EXC-FIR/LFFF

Exclude a particular FIR

DTE-JAN/75

Statistical weather for January (or any month) with a probability factor of 75%. Options 50-85% in increments of 5. If nothing specified default is 50%.

DTE-QTR1/75

Statistical weather for first quarter of the year. Options Quarters 1-4 and probability factors as above.

DTE-JANJUN

Statistical weather of the months January to June. JULDEC also available; probability factors as above.

DTE-SUM

Summer statistical weather (months April to September). WIN for winter (months October to March), YEAR for an average for the year. Probability factors may be used as above.

WDE-0

Used to ignore forecast winds and give the minimum ground distance.

LVL-L

Used to specify Low (LVL-L) or High (LVL-H) airways. This can also be defined in the heading and the default is for high-level airways if nothing has been specified.

IGR

Ignores any restrictions.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 116 of 168

Section 11 Keywords

KEYWORD : RSF-

PURPOSE:

Provision of a route summary, with details of FUEL BURN / ELAPSED TIME/ AIR DISTANCE and ZFW, over a specified route.

FORMAT:

RSF-

EXAMPLE:

RSF-2525 (MAX 6 NUMERICS)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 117 of 168

Section 11 Keywords

KEYWORD : RSG-

RSG-

PURPOSE:

Provision of summary details of least distance route (nearest to Great Circle).

FORMAT:

RSG-

EXAMPLE:

RSG-

ERROR MESSAGE: NONE

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 IS SAME AS EXPLICIT MAIN PLAN ROUTE'.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 118 of 168

Section 11 Keywords

KEYWORD : RSN-

PURPOSE:

Provision of a route related Flight Plan Summary appended as next best route to that planned. Up to four summaries can be requested.

FORMAT:

RSN-1 RSN-2 etc

ERROR MESSAGE: RSN-MUST BE EITHER 1, 2, 3 OR 4

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)

Up to 4 route summaries may be requested, providing that there are 4 additional routes stored for the sector (excluding the main plan route). Example: RSN-4.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 119 of 168

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:

a

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 ().

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 120 of 168

Section 11 Keywords

3)

Utilising the Oceanic Track System: RTE-EGKK/LAM2M LAM/UB3 BPK/UB4 ROBIN/UR3 RTE-WAL/UB3 BEL/NATC SCROD/DCT VALIE/NA212 RTE-TAFFY/DCT SEAER/J79 HYA/J174 DIW/AR14 RTE-METTA/ARI HONOE/DCT KM1A This example uses the North Atlantic Track System. The routing up to the NAT track is entered in the same manner as in the previous examples. However, the oceanic track should be specified as an entry point, track identifier and an exit point. The example above utilises NAT C: BEL/NATC SCROD Where the track entry point is ’BEL’, the actual track is ’NATC’, and the track exit point is ’SCROD’. The same philosophy is used for PACOT and FTRS routes in the Pacific using ‘PAC’ and ‘HNL’ and for AUSOTS routes in Australia using ‘AUS’.

4)

Utilising the Oceanic Track System and stored SITA routes: RTE-EGKK/337 SHA/1628 BURAK/NATH RTE-YAY/83230 KLAX Oceanic entry and exit routes may also be specified in the RTE- input. The example above indicates that: i. Route number 337 is used until waypoint SHA. ii. Oceanic entry number 1628 is used until waypoint BURAK. iii. NAT H is followed until waypoint YAY. iv. Oceanic exit number 83230 is used until the final destination, KLAX.

5)

RTE- keyword and Reclear routing: RTE-EGLL/MIDIJ MID/83105 HBV/HBVIC FAJS/RCR RTE-VVL/UA400 LV/DCT FLLS RCR-FLLS/FLND/VVL The routing from Origin to Final Destination is entered first, followed by the reclear routing identifier, ’RCR’ after the final destination. The routing from the reclear fix to the Initial Destination is then entered. The example above indicates that: i. Normal RTE input is used from origin EGLL to final destination FAJS. ii. Use of ‘RCR’signifies that a reclear route is to follow. iii. The routing from the reclear fix, ‘VVL’to the initial destination, ‘FLLS’is then entered. Note: The RCR- keyword must also be used when entering a Reclear routing.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 121 of 168

Section 11 Keywords

6)

Using full latitude/longitude coordinates: RTE-EGKK/337 SHA/DCT N5400W01500/DCT RTE-N5400W02000/DCT N5500W03000/DCT RTE-N5500W04000/DCT N5600W05000/DCT RTE-YAY/83230 KLAX Coordinates can be entered as above, but may also include decimal places, for example, RTE-EGFF/30229 BIG/DCT RTE-N5109.8E00121.6/DCT RTE-N5114.8E00200.0/DCT RTE-MADUX/30229 EBBR Both of the examples above produce direct routing between the latitude and longitudes and can only be used with an Airway identifier of ’DCT’.

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 ’DCT’in 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

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 122 of 168

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)

RTE- keyword and First Alternate routing: RTE-EGFF/30229 EBBR/ALT RTE-EBBR/47622 EDDF The routing from Origin to Destination is entered first, followed by the alternate routing identifier, ’ALT’ after the final destination. The routing from the final destination to the first alternate is then entered. The example above indicates that: i. Normal RTE input is used from origin EGFF to final destination EBBR. ii. Use of ‘ALT’signifies that the alternate route is to follow. iii. The routing from the final destination, ‘EBBR’to the first alternate, ‘EDDF’is then entered. It is also possible to construct the alternate route based on a mixture of inputs: RTE-EGFF/30229 EBBR/ALT RTE-EBBR/DCT ETENO/Y863 NTM/47622 EDDF iv. From the final destination, EBBR, a direct track is taken to ETENO to join airway Y863. v. From waypoint NTM, SITA route number 47622 is followed until alternate EDDF. Note: In order to see a flight plan to the alternate on a CFP, the ALT-…./P keyword must also be used on the CFP request.

Additional information: •

Up to five waypoint/airway pairs can be entered on one line.

•

Up to ten lines of data can be entered

•

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 123 of 168

Section 11 Keywords

•

Any compulsory waypoints on the airway will be displayed automatically in the flight plan output, regardless of whether they were included in the RTEkeyword. Note: Exception is when using the format shown in example 7, where ALL waypoints along an airway must be specified.

•

Unless specified in the RTE- input, non-compulsory waypoints will not be included in the flight plan output.

•

The Airway direction is checked so that one-way Airways are not incorrectly flown and any requests will be returned as an error.

Examples of Error Messages: RTE RTE RTE RTE RTE RTE RTE RTE RTE RTE RTE RTE

LINE TOO LONG, ONLY 53 CHARACTERS PER LINE ALLOWED ONLY 5 PAIRS ALLOWED ON ONE LINE LAST STATION- (V) DOES NOT MATCH DESTINATION INPUT ERROR (V) INVALID FORMAT FIRST STATION- (V) DOES NOT MATCH ORIGIN NO RECLEAR ROUTING INPUT ON RTE RCR KEYWORD MUST BE ENTERED IF RECLEAR REQUIRED RCR DEST (V) NOT FOUND IN RTE INPUT DESTINATION (V) NOT FOUND IN RTE INPUT CUSTOMER ROUTE (V) NOT ON FILE PLEASE CHECK INPUT ORIGIN (V) ON RTE-(V) DOES NOT MATCH (V) DESTINATION (V) ON RTE-(V) DOES NOT MATCH (V)

Reclear and Alternate RTE- keyword Error Messages: RTE RTE RTE RTE RTE RTE RTE RTE RTE RTE

STATION - ABCD DOES NOT MATCH INITIAL DESTINATION RCR KEYWORD CANNOT BE ENTERED WITH ALT KEYWORD ROUTE WITH ALT CANNOT BE USED WITH OVERIDE ALT DISTANCE ROUTE TO ALTERNATE SHOULD END WITH AIRPORT FOR ROUTE TO ALTERNATE ABCD DEST. MUST BE REPEATED LAST STATION SSSS DOES NOT MATCH ALTERNATE DESTINATION DESTINATION ABCD NOT FOUND IN RTE INPUT FOR ROUTE TO ALTERNATE CANNOT GO DIRECT TO ALTERNATE DESTINATION ROUTE TO ALTERNATE FORMATTED INCORRECTLY ALT ROUTE nnnnnn NOT FOUND

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 124 of 168

Section 11 Keywords

KEYWORD : RTW-

PURPOSE:

Restriction of Take Off Weight

FORMAT:

RTW-

EXAMPLE:

RTW-365400 (Max 6 numerics wt shows in units)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 125 of 168

Section 11 Keywords

KEYWORD : RVF-

PURPOSE:

Modification of Fuel Reserve Policy (Trip Fuel related).

FORMAT:

RVF

EXAMPLE:

1) 2)

RVF-120 (1 to 3 numerics) (LIMIT 200 = 20%) RVF-12

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)

In Example 1) the reserve policy is changed to 12% of trip fuel. In Example 2) the reserve policy is changed to 1.2% of trip fuel. Figures are entered as tenths of a percentage.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 126 of 168

Section 11 Keywords

KEYWORD : RVN-

PURPOSE:

Removal of fuel reserves from Flight Plan calculation.

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).

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 127 of 168

Section 11 Keywords

KEYWORD : RVT-

PURPOSE:

Modification of Fuel Reserve Policy (Time Related).

FORMAT:

RVT-

EXAMPLE:

1) 2)

RVT-155 (1 to 3 numerics) (LIMIT 200 = 20%) RVT-15

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)

In Example 1) reserve policy is amended to 15.5% of trip time.

3)

In Example 2) reserve policy is changed to 1.5% of trip time. Figures are entered as tenths of a percentage.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 128 of 168

Section 11 Keywords

KEYWORD : RWY-

PURPOSE:

Display Departure/Arrival Runway heading.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 129 of 168

Section 11 Keywords

KEYWORD : SEL

PURPOSE:

To specify the SELCAL code to be printed on the ICAO plan. The code input will override the Selcal code loaded in the Attribute file for the aircraft specified in the CFP request..

FORMAT:

SEL-ABCD (Where ABCD is the required code)

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

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 130 of 168

Section 11 Keywords

KEYWORD : SFI-

PURPOSE:

Produces up to three Fixed Flight Level plan summaries appended to the Main Flight Plan. It will contain Time, Fuel, Mach and Cruise Mode.

FORMAT:

SFI-XXX/YYY (XXX=Flt Level; YYY=Mach Nbr) SFI-XXX/ZZZ (XXX=Flt Level; ZZZ=Cruise Mode) SFI-XXX/NNN (XXX=Flt Level; NNN=Waypoint Number)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 131 of 168

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

SFI-350 Cruise Mode and Mach the same as for the Flight Plan SFI-240/825 Mach Number of 825 for summary (Mach range 500 to 900) SFI-310/LRC Cruise Mode LRC for summary (options ECO,LRC,MNT, these correspond to CRZ 1,3, 5 respectively.) SFI-320/27 Fixed Level only to Waypoint 27, numbered from Destination end.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 132 of 168

Section 11 Keywords

KEYWORD : SGF-

PURPOSE:

Indication of Fuel Specific Gravity

FORMAT:

SGF-

EXAMPLE:

SGF-805 (2-3 NUMERICS) (BETWEEN 750 and 853)

ERROR MESSAGES: SGF MUST BE 3 DIGITS, BETWEEN 750 & 853 NOTE :

1)

This input will override the screen loaded SGF. (The Example changes Fuel SG. to .805).

2)

The value of SGF is based on LBS/IMP. GALLON.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 133 of 168

Section 11 Keywords

KEYWORD : SHP-

PURPOSE:

This allows a customer to have a short or summarised plan.

FORMAT:

SHP-

EXAMPLE:

SHP

The information printed on a short plan is dependent on each individual customer’s flight plan format. Please contact SITA Helpdesk for any questions relating to short plan if necessary.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 134 of 168

Section 11 Keywords

KEYWORD : SMB-

PURPOSE:

Summary details indicating: fuel burn, elapsed time, height profile at a specified flight level gap below the flight level in the main Flight Plan.

FORMAT:

SMB-XX/YYY (Where XX is hundreds of feet below the primary Flight Plan level. YYY is nominated Mach Number, this is optional)

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)

In Example 2 a summary is requested at 4000 ft below the primary Flight Plan level at a Mach Number of 785.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 135 of 168

Section 11 Keywords

KEYWORD : SMI-

PURPOSE:

Produces a summary appended to the Flight Plan showing fuel, elapsed time and height profile assuming flight at the initial planned Flight Level only.

FORMAT:

SMI-

EXAMPLE:

SMI-

ERROR MESSAGE: None.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 136 of 168

Section 11 Keywords

KEYWORD : SML-

PURPOSE:

Prints a summary appended to the Flight Plan indicating Time/Fuel/Flt Level profile for a selected Mach No or selected Cruise Mode (differing from value selected for main Flight Plan).

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)

In the FORMAT Example XXX = numerics 1, 3 or 5 when Cruise Mode summary required XXX = numerics 500-900 when Mach Value summary is required.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 137 of 168

Section 11 Keywords

KEYWORD : SMZ-

PURPOSE:

Provision of a Flight Plan Summary at Max ZFW for the sector, indicating Time, Fuel and Flight Profile.

FORMAT:

SMZ-

EXAMPLE:

SMZ-

ERROR MESSAGE: NONE

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 138 of 168

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)

SPF numbers as in example will be allocated by SITA on a temporary basis.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 139 of 168

Section 11 Keywords

KEYWORD : SSF-

PURPOSE:

To change the default Speed stability factor

FORMAT:

SSF-

EXAMPLE:

SSF-0.3 (numeric range 000 to 2.0)

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)

This factor has no relevance to fixed Mach Cruise schedules.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 140 of 168

Section 11 Keywords

KEYWORD : SWT-

PURPOSE:

The provision of 2 Flight Plan summaries based on a fixed weight interval one above and one below the calculated ZFW.

FORMAT:

SWT-

EXAMPLE:

SWT-2500 (KGS or LBS)

(Max 5 numerics between 1 and 50000)

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)

At Min or Max ZFW one interval will obviously be 0.

3)

Achievement of Structural and/or Volumetric limitations will have the obvious effect of constraining summary. i.e. Tank limits (WT&VOL), RTW, LDG WT. etc.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 141 of 168

Section 11 Keywords

KEYWORD : SWX-

PURPOSE:

To allow access to the Surface Weather system with a Flight Plan request. Gives the weather for the destination and all alternates used in the flight plan request.

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

LINE IS TOO LONG ( > 49 CHARS) UNRECOGNISABLE INPUT IATA CODE, (V) NOT ON FILE ICAO CODE, (V) NOT ON FILE

NOTE : 1)

Up to 8 additional ICAO/IATA may be entered.

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)

Format shown in seven, SWX-AUTO/EGLL/EGKK, gives destination, alternates and up to eight other airports as specified.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 142 of 168

Section 11 Keywords

KEYWORD : SWX-

SWX-

(continued)

AIRPORT ICAO OR IATA SHOULD NOT BE MIXED. The following is a brief description of the above Examples: EXAMPLE 1) Shows just the format SWX-, this is the minimum needed. FCST and AUTO will be generated as defaults. EXAMPLE 2) Includes the Keyword FC, AUTO is generated as default. EXAMPLE 3) Will generate FCST for destinations and alternates including Reclear when appropriate. EXAMPLE 4) Shows FT and AUTO. No ICAO/IATA's are entered, they are not compulsory. EXAMPLE 5) 5 and 6 are similar, one has ICAO entered and the other has IATA entered. Up to 8 ICAO/IATA are permitted. EXAMPLE 7) Has no defined report, as Example 1, default is FCST. EXAMPLE 8) Shows the Keyword all with the ICAO'S KMEM and KMIA. They will be converted to the IATA MEM and MIA automatically, to access USA generated reports. EXAMPLE 9) Just shows 3 IATA codes, as in Examples 1 and 6, the default is FCST. The IATA code will be automatically converted to ICAO for non US generated reports. SWX-LHR/LBA/ABZ becomes SWX-EGLL/EGNM/EGPD NOTE : Surface Weather system codes are as follows: FT FC SA ALL FCST FS FA FCA

= TAF = Short Range Forecast = Surface Actual = FT + FC + SA = FC + FT = FT + SA = FT + Last three Actuals = FC + SA

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 143 of 168

Section 11 Keywords

KEYWORD : TAL-

PURPOSE:

To define a Take Off Alternate in the CFP request

FORMAT:

TAL-

EXAMPLES:

TAL-EGCC

(coding convention must match origin to destination i.e. ICAO or IATA)

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-.

TAL-NO TAL TAS OR MAX DIST VALUES IN AIR POLICY FILE TAL-ALTN xxxx IS yyyy NM FROM ORIGIN, MAX DIST IS zzzz (see note 4 below)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 144 of 168

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:

TAKE OFF ALTN LGKR

TRACK(T) 240

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

DIST TIME 222

0:40

ETA 10:40

MORA MAX LWT 3400

90000

Flight Planning Reference Manual

Page 145 of 168

Section 11 Keywords

KEYWORD : TAX-

PURPOSE:

Provision of Taxi Fuel

FORMAT:

TAX-

EXAMPLE:

TAX-600 (Max. 5 numerics weight shows in units).

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)

The Example will give a taxi fuel of 600 kgs/lbs.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 146 of 168

Section 11 Keywords

KEYWORD : TDF-

PURPOSE:

To specify the Date/Time for the start of Flight Plan computation

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

FACILITY NOT AVAILABLE, TRY AGAIN LATER MUST BE HHMM OR 9999 FOR NEXT METEO UPDATE MUST BE HHMMM/DD IF ENTERING DATE DATE MUST NOT BE MORE THAN 3 DAYS FROM TODAY EXPECTED FORMAT - 9999/HHMM INVALID FORMAT, SHOULD BE TDF-XXXX

NOTE : 1)

This Keyword allows customers to request Flight Plans to be run at a specified time. The customer may input time only in the format HHMM time and date in the format HHMM/DD. The maximum time allowed will be 3 days from current date. If the time input is "9999" then the Flight Plan will be processed at the time of the next weather files update. Plan to be delayed, not processed immediately. It will be processed either at the specified time or at the next Weather Update.

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)

See following page for transaction on this Keyword.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 147 of 168

Section 11 Keywords

)

KEYWORD : TDF- TRANSACTIONS FACILITY SECTION A: DEFINE TYPICAL INPUT TO EXTRACT INFORMATION 1)

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)

REFNO FLT DETAIL -------------- ----

ORIG ----

DEST DT REQ TIME DT SUB TIME -- -------- -- --------

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

DELETION OF DELAYED FLIGHT PLANS FROM TDF FILE TO DELETE FP REF NUMBERS ON TDF FILE FOR AIRLINE : BB ----------------------------------------------------------------------------------------

Line 1 2

TDF DEL

3 4

PSW-BB AAAA AAMJE/AAMJF/AAMFL

5

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/)

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 148 of 168

Section 11 Keywords

KEYWORD : TDF- TRANSACTIONS FACILITY

) (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

SECTION B : ERROR MESSAGES 1)

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)

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 149 of 168

Section 11 Keywords

KEYWORD : TDF- TRANSACTIONS FACILITY

(continued) Notes:

Line numbers 1,2,3,4 are mandatory MAD address line is optional. The resulting output from above request is :-

THE FOLLOWING TDF FP REFNOS HAVE BEEN CANCELLED FOR AIRLINE: REFNO FLT DETAIL ORIG DEST DT REQ TIME DT SUB TIME ----- ---------- ---- ---- -- -------- -- --------REFNO: AAMJE NOT DELETED AS RECORD NOT FOUND ON FILE

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

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 150 of 168

Section 11 Keywords

KEYWORD : TDF- TRANSACTIONS FACILITY

(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 '/'

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 151 of 168

Section 11 Keywords

KEYWORD : TFU-

PURPOSE:

To request Tankering Fuel.

FORMAT:

TFU(Entered as weight value in units - max 6 digits)

EXAMPLE:

1) 2)* 3)

TFU-17000 (to request 17000 KGS/LBS) TFU-MAX (to tanker to max tank wt/vol limit) TFU-1000

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)

This entry can be used in conjunction with TLW.

3)

Input of TFU-MAX (example 2) will produce max fuel uplift subject to the restrictions of structural limitations and volumetric capacity. *

4)

Tankering Fuel is treated as Freighted Fuel - and the calculation assumes carriage through to the Alternate.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 152 of 168

Section 11 Keywords

KEYWORD : TLW-

PURPOSE:

Definition of Tankering Landing Weight

FORMAT:

TLW(Entered as weight value in units- max 6 digits)

EXAMPLE:

TLW-247000 (to request 247000 KGS/LBS)

ERROR MESSAGES: TLW TLW TLW TLW TLW

MUST BE NUMERIC, MAXIMUM 6 DIGITS MUST BE GREATER THAN RLW EXCEEDS 1.1 X MAX LNDG WT, (V) FOR (V) LESS THAN OWE VALUE OF (V) FOR (V) LESS THAN MIN ZFWT VALUE OF (V) FOR (V)

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)

Example shows a Tankering Landing Weight of 247000 KGS/LBS.

3)

Should be used in conjunction with TFU-.

4)

Relationship RLW/TLW: RLW = Restricted Landing Weight (see Keyword RLW-)

5)

TLW is a more precise definition of the Landing Weight requirement related to the carriage of fuel. It is a requirement rather than a restriction.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 153 of 168

Section 11 Keywords

KEYWORD : TLX-

PURPOSE:

To maximise tanker fuel uplift, overriding structural max landing weight (if required)

FORMAT:

TLX(Entered as weight values in units- max 6 digits)

EXAMPLE:

TLX-240000 (to request 240000 KGS/LBS)

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)

This Keyword is provided to give customers flexibility in the tankering of fuel; an overweight landing figure may be specified provided it is no greater than 120% of the Max Landing Weight value held on file.

2)

Use of this Keyword will trigger automatic calculation of freighted/tankered fuel without a TFU value, (refer to TFU-) being requested.

3)

The fuel uplift will be a maximum subject to the restrictions of structural limitation and volumetric capacity and the TLX landing weight limit.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 154 of 168

Section 11 Keywords

KEYWORD : TNK-

PURPOSE:

To initiate the tankering program.

FORMAT:

TNK- (followed by the one of the following options)

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

Calculates the Optimum Tanker fuel and includes the fuel in the Flight Plan calculation. Provides a Tankering Analysis on the CFP.

TNK-OPT/S

As for TNK-OPT but does not include tanker fuel as fuel onboard in the main flight plan calculation.

TNK-ANL

This option would provide an analysis of MAX, 80, 60, 40 and 20 percent of the possible tanker fuel.

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

(Produced if any input other than the above is made)

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)

Zero Fuel Weight/Payload is never reduced to achieve tankering.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 155 of 168

Section 11 Keywords

KEYWORD : TPA-

PURPOSE:

To apply an ISA deviation to the Alternate calculation of a Fixed Wind and Temperature Flight Plan.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 156 of 168

Section 11 Keywords

KEYWORD : TPE-

PURPOSE:

To apply an ISA deviation to the Origin-Destination portion of a Fixed Wind and Temperature Flight Plan.

FORMAT:

TPE-

EXAMPLE: 1) 2) 3)

TPE/-20 TPE/9 TPE/XX

(ISA - 20 whole Route) (ISA + 9 whole Route) (Enroute temperature value in the range ISA -20 to plus 20 degrees. Enter minus sign in front of value if a minus on ISA deviation required.) (Use 1 or 2 numerics for value.)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 157 of 168

Section 11 Keywords

KEYWORD : TTI-

PURPOSE: FORMAT: EXAMPLE:

Used to specify the Taxi Time In (in minutes) TTI- (minimum value is 0, maximum value is 99 minutes) TTI-22

ERROR MESSAGES: TTI-MUST BE LENGTH 1 OR 2 (0-99)

NOTE :

1) A default Taxi Time In value can be configured in an aircraft’s 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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 158 of 168

Section 11 Keywords

KEYWORD : TTO-

PURPOSE: FORMAT: EXAMPLE:

Used to specify the Taxi Time Out (in minutes) TTO- (minimum value is 0, maximum value is 99 minutes) TTO-22

ERROR MESSAGES: TTO-MUST BE LENGTH 1 OR 2 (0-99)

NOTE :

1) A default Taxi Time Out value can be configured in an aircraft’s 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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 159 of 168

Section 11 Keywords

KEYWORD : TWS-

PURPOSE:

Provision of two Flight Plan summaries based on a fixed weight interval one above and one below the calculated T.O.W.

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)

At min or max T.O.W. one interval will obviously be zero.

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).

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 160 of 168

Section 11 Keywords

KEYWORD : TXI-

PURPOSE:

To specify taxy in fuel as an override to the normal aircraft default value.

FORMAT:

TXI-

EXAMPLE:

TXI-600 (Must be max 4 numerics in units Lbs/Kgs)

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 161 of 168

Section 11 Keywords

KEYWORD : TYF

PURPOSE:

To specify the Type of Flight on the CFP.

FORMAT:

TYF-

EXAMPLES:

TYF-RECLEAR TYF-ETOPS/180 TYF-TEST FLIGHT

ERROR MESSAGES: TYF-MAX 10 CHARACTERS ONLY

NOTE : 6)

The Type of Flight specified by the keyword has no effect in the calculation of the flight plan, it serves to append ‘text’ onto the calculated flight plan

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)

JAR-OPS 1.1060 (Operational flight plan) (a) Item 11 is addressed by the facility provided by this keyword

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 162 of 168

Section 11 Keywords

KEYWORD : VID-

PURPOSE:

To change the User Identification which prints out on the Flight Plan, irrespective of which airline's aircraft is utilised for the Flight.

FORMAT:

VID-

EXAMPLE:

VID-XS

ERROR MESSAGES: VID MUST BE 2-3 ALPHANUMERICS VID (V) INVALID, MUST BE 2-3 CHARACTERS

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 163 of 168

Section 11 Keywords

KEYWORD : WDA-

PURPOSE:

To apply fixed wind and temperatures to the alternate. Note: To apply fixed wind and temperatures to the destination, see WDE-.

FORMAT:

WDA/

Followed by Wind speed in KTS

WDA/-150 WDA/5 WDA/XX

Headwind 150 KTS Tailwind 5 KTS Alternate Wind value in the range -200 to plus 200KTS over the sector from Destination to Alternate. Same rules as WDE-.

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 164 of 168

Section 11 Keywords

KEYWORD : WDE-

PURPOSE:

To obtain a Flight Plan with Fixed Winds and Temperatures. Also refer to TPA-, TPE- and WDA-.

FORMAT:

WDE/ Followed by Wind speed in KTS

EXAMPLE:

WDE/-30 WDE/50/A

FIXED WINDS AND TEMPERATURES WDE/NNN

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

Headwind 30KTS on cruise; 20 KTS CLB/DESC Tailwind 50KTS throughout flight

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/)

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 165 of 168

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.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 166 of 168

Section 11 Keywords

KEYWORD : WXSPURPOSE:

Enables a summary of all or selected waypoint wind temperature values to be appended to the Flight Plan.

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)

Height Extent Parameter: Blank or Zero means 4000ft above and below height profile 40 means 4000ft above only 44 means 4000ft above and below 80 means 8000ft above only 88 means 8000ft above and below 99 means all flyable flight levels between FL180 and FL450

3)

EXAMPLE WXS-2/40 requests summary at every other waypoint, for 4000ft above planned height.

4)

Origin and Destination winds/temps are always printed.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

Flight Planning Reference Manual

Page 167 of 168

Section 11 Keywords

KEYWORD : XFU-

PURPOSE:

To request Extra fuel where payload has priority.

FORMAT:

XFU(Entered as weight values in units - max 6 digits).

EXAMPLE: 1)

XFU-3000 (to request 3000 KGS/LBS)

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)

EXTRA fuel should not be confused with ADDITIONAL fuel.

© Copyright 2010 SITA. All rights reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.