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 RTE- keyword format follows a convention of
‘WAYPOINT/AIRWAY’ blocks, for example:
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 ().
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.
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-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.
• Any compulsory waypoints on the airway will be displayed automatically in the flight plan output, regardless of whether they were included in the RTE-
keyword.
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 LINE TOO LONG, ONLY 53 CHARACTERS PER LINE ALLOWED RTE ONLY 5 PAIRS ALLOWED ON ONE LINE
RTE LAST STATION- (V) DOES NOT MATCH DESTINATION RTE INPUT ERROR (V) INVALID FORMAT
RTE FIRST STATION- (V) DOES NOT MATCH ORIGIN RTE NO RECLEAR ROUTING INPUT ON RTE
RTE RCR KEYWORD MUST BE ENTERED IF RECLEAR REQUIRED RTE RCR DEST (V) NOT FOUND IN RTE INPUT
RTE DESTINATION (V) NOT FOUND IN RTE INPUT
RTE CUSTOMER ROUTE (V) NOT ON FILE PLEASE CHECK INPUT RTE ORIGIN (V) ON RTE-(V) DOES NOT MATCH (V)
RTE DESTINATION (V) ON RTE-(V) DOES NOT MATCH (V) Reclear and Alternate RTE- keyword Error Messages:
RTE STATION - ABCD DOES NOT MATCH INITIAL DESTINATION RTE RCR KEYWORD CANNOT BE ENTERED WITH ALT KEYWORD
RTE ROUTE WITH ALT CANNOT BE USED WITH OVERIDE ALT DISTANCE RTE ROUTE TO ALTERNATE SHOULD END WITH AIRPORT
RTE FOR ROUTE TO ALTERNATE ABCD DEST. MUST BE REPEATED
RTE LAST STATION SSSS DOES NOT MATCH ALTERNATE DESTINATION RTE DESTINATION ABCD NOT FOUND IN RTE INPUT
RTE FOR ROUTE TO ALTERNATE CANNOT GO DIRECT TO ALTERNATE DESTINATION RTE ROUTE TO ALTERNATE FORMATTED INCORRECTLY
RTE ALT ROUTE nnnnnn NOT FOUND