1. European Organisation for the Safety of Air Navigation Presentation to ICAO Workshop Kiev 28 July – 1 July 2010 EUR Regional Implementation of Flight Plan Amendment 1 for 2012 Issues with Certain Fields Andrew.Hill@eurocontrol.int Version d4

2. 2 Field 10a – NAV/COM Equipment and Capability Syntax: ["N"] | [ 1 { "A" | "B" | "C" | "D" | "E1" | "E2" | "E3" | "F" | "G" | "H" | "I" | "J1" | "J2"| "J3" | "J4" | "J5" | "J6" | "J7" | "K" | "L" | "M1" | "M2"| "M3" | "O" | "P1" | "P2" | "P3" | "P4" | "P5" | "P6" | "P7" | "P8" | "P9" | "R" | "S" | "T" | "U" | "V" | "W" | "X" | "Y" | "Z" } ]  Description:The descriptor "N" or one or more of the listed descriptors without repetition, therefore a theoretical limit of 64 characters  No longer accepted: E, P, M, J, Q.  New: Letter&Digit combinations Semantics: If ‘R’ present  PBN/ expected in F18. If ‘Z’ present  at least one of COM/, DAT/, NAV expected in F18

3. 3 Field 10b – SUR Equipment and Capability Syntax: ["N"] | (1{ ("I" | "P" | "X") | "A" | "C"}3 | 1{ "A" | "C" | "E" | "H" | "L" | "S"}6) [1{"B1"| "B2" | "D1" | "G1" | "U1" | "U2" | "V1" | "V2"}8 ]  Description: The descriptor 'N' or, either one or more of the descriptors ‘I’, ‘P’, ‘X’, ‘A’, ‘C’ with ‘I’, ‘P’, ‘X’ being mutually exclusive i.e. only one may be present, or one or more of the descriptors ‘A’, ‘C’, ‘E’, ‘H’, ‘L’, ‘S’. Plus optionally one or more of the descriptors ‘B1’, ‘B2’, ‘D1’, ‘G1’, ‘U1’, ‘U2’, ‘V1’, ‘V2’ without repetition. A total limit of 20 characters shall be applied  No longer accepted: D  New: Letter&Digit combinations Semantics: None

4. 4 F18 & Flexibility - Background  Amendment 1 indicates for Field 18: Note.— Use of indicators not included under this item may result in data being rejected, processed incorrectly or lost INSERT 0 (zero) if no other information, OR, any other necessary information in the preferred sequence shown hereunder, in the form of the appropriate indicator selected from those defined hereunder followed by an oblique stroke and the information to be recorded

5. 5 F18 & Flexibility - Background  A specified list of indicators in Field 18 Some ‘missing’ in use in Europe today. (RVR/, RFP/, IFP/, STAYINFOn, AWR/, SRC/)  A specified list of indicators in STS/ Some ‘missing’ (EXM833, PROTECTED, NONRNAV, CPDLCX)  Possibility to add new indications (without 4444 amendment) ?? Only RMK/, a free text field, seems to offer any flexibility

6. 6 F18 & Flexibility – Use of Doc.7030  Doc. 7030 to provide EUR requirements Retention of RVR/ and RFP/ as currently specified Introduction of EUR/ to provide specific EUR status and exemption indications (EXM833, PROTECTED, CPDLCX)  Proposed amendment to Doc. 7030 presented to APDSG on 26-28 May, COG Nov?, EANPG Dec

7. 7 F18 & Flexibility – Technical Implementation Recommended: Globally, ATC end-user systems should accept an un-recognised indicator in Field 18 Alternatively, they must remain current with all planned 7030 updates involving new data items within the FPL If ATC systems only accept the published list of Field 18 indicators, then how can we evolve without the need for global synchronisation for every new data item requirement?

8. 8 Field 18 – IFPS will Accept Syntax: [ "0" ] | [ 1{"STS/" | "PBN/"| “EUR/” | "NAV/" | "COM/" | "DAT/" | "SUR/" | "DEP/" | "DEST/" | "DOF/" | "REG/" | "EET/" | "SEL/" | "TYP/" | "CODE/" | "RVR/" | "DLE/" | "OPR/" | "ORGN/" | "PER/" | "ALTN/" | "RALT/" | "TALT/" | "RIF/" | "RMK/" | "STAYINFOn/" | "RFP/" } ]  Description: Either the descriptor "0" (zero) or one or more of the listed elements without repetition.  Order of fields not important to IFPS.  New: PBN/, DLE/, ORGN/, TALT/, EUR/ Semantics: If PBN/  ’R’ in F10a

9. 9 Field 18 – Transmitted by IFPS Syntax: 1{ [ "0" ] | ["STS/" | "PBN/" | “EUR/” | "NAV/" | "COM/" | "DAT/" | "SUR/" | "DEP/" | "DEST/" | "DOF/" | "REG/" | "EET/" | "SEL/" | "TYP/" | "CODE/" | "RVR/" | "IFP/" | "DLE/" | "OPR/" | "ORGN/" | "PER/" | "ALTN/" | "RALT/" | "TALT/" | "SRC/" | "RIF/" | "RMK/" | "STAYINFOn/" | "RFP/" | "AWR/" ] }  Description: Either the descriptor "0" (zero) or one or more of the listed elements in the order shown above.  The indicators "SRC/", "AWR/" and "IFP/" shall not be output by IFPS to unknown ‘AD’ line addressees

10. 10 Field 18 – STS/ Syntax: 1{ "ALTRV" | "ATFMX" | "FFR" | "FLTCK" | " HAZMAT" | "HEAD" | "HOSP" | "HUM" | "MARSA" | "MEDEVAC" | "NONRVSM" | "SAR" | "STATE" }  Description: one or more of the listed descriptors without repetition.  No longer accepted: ATFMEXEMPTAPPROVED, EXM833, PROTECTED, NONRNAV, RNAVINOP, Other free text reasons to be provided in RMK/  New: ATFMX, FFR, FLTCK, HAZMAT, MARSA, MEDEVAC

11. 11 Field 18 – DEPT, DEST, ALTN Syntax: [adname [(brng distnc) | (lattd longtd)]] | [ptid | lattd longtd] adname = 1{LIM_CHAR}50  Description: The name of the departure aerodrome (up to 50 characters) plus optionally (for aerodromes not listed in the relevant AIP) the location of the aerodrome given either as bearing and distance from a significant point or as a latitude and longitude. Or, if the aircraft did not depart from an aerodrome, the first point on the route (given by a Nav. Aid, Waypoint or Marker Beacon designator) or by latitude & longitude. e.g. DEP/ MALAHIDE DUB11015 DEP/ MALAHIDE 5327N00608W DEP/BAGSO DEP/5327N00608W

12. 12 Field 18 – DLE Syntax: 1{ALPHANUM}11 4{DIGIT}4  Description: a significant point followed by an indication of a time period in hours and minutes e.g. DUB0040 ; DUB1800400030  A DLE/ indication will be retained by IFPS and provided to ATC Units as received regardless of the location of the DLE point (inside/outside IFPZ)  The CFMU profile shall reflect the additional flight time as appropriate  The STAY indication will be retained for use for flights which remain entirely within the IFPZ, as today.

13. 13 Modifying Field 18 cont. (CHG-ABC123-EBBR2230-EDDF-DOF/100323-18/REG/OOSAX)  F18= PBN/B3 DOF/100323 REG/OOSAX i.e. PBN & DOF have been removed ! FPL:F18= PBN/B3 DOF/100323 REG/OOSAB Note : When modifying a Field 18 element complete Field 18 must be provided, not just the modified element. Elements not repeated will be deleted.

14. 14 Use of DOF/ FPL:F18= STS/HOSP DOF/100304 PBN/B3 F13b= 2230 Flight is delayed until 0200 i.e. a delay over midnight. (DLA-ABC123-EBBR0200-EDDF-DOF/100304) OR (CHG-ABC123-EBBR2230-EDDF-DOF/100304-13/EBBR0200 18/STS/HOSP DOF/100305 PBN/B3) Note 1: The DOF (or Off Block Date) as provided in Field 18 shall always refer to the last notified Off Block Date & Time (EOBD/EOBT). Note 2: A modification to F18, via Field 22, must contain the complete F18 information, otherwise the ‘missing’ data will be removed from the FPL.

15. 15 Field 18 In Other Messages  Field 18 required in CNL, DLA, CHG, DEP, RQS, RQP  IFPS will raise an error if not present (but it can just be ‘0’)  IFPS will ensure Field 18 containing only DOF/ is always included in CNL, DLA, CHG, DEP messages sent to ATC Units.

16. 16 Field 18 - Other Message – Input Examples 1.(CHG-EIN105-EIDW1200-KORD-DOF/100304-9/E346/H) 2.(CNL-EIN105-EIDW1200-KORD-DOF/100304) 4.(CNL-EIN105-EIDW1200-KORD-STS/ATFMX MARSA FLTCK PBN/A1C3L1 NAV/GBAS SBAS DAT/NO SPECIFIC DESIGNATORS SUR/ADDITIONAL INFO DEP/MALAHIDE 5327N00609W DOF/100305) 3.(CNL-EIN105-EIDW1200-KORD-0) Examples of valid message compositions:

17. 17 Questions?