EUR Flight Planning Guidance Kim Breivik Operational Requirements Network Management EUROCONTROL

Filing the Nav Capability From a PBN perspective: As a Pilot or Flight Dispatch: Identify which to PBN NAV spec “approvals” you hold for each phase of flight (from Oceanic to Approach) Step 1 Slide 3 Step 2 File “R” for PBN in Item 10 Enter “PBN/” in Item 18 and apply the rules to reduce the number of indicators in item 18 (max 8) Step 3 Slide 4 Identify the specific NAV equipment supporting each Nav Spec and file in Item 10 ensuring conformity with the content of Item 18 Step 4 Slides 11 & 12 FPL2012 24 April 2012

Step 1. - Identify Ops Approvals to PBN Nav Specs. Identify all the relevant codes (if any) per flight phase: Note (*): P-RNAV is to be filed as RNAV 1 Note: As P-RNAV is not exactly the same as RNAV 1 operators have a duty of care to ensure they meet RNAV 1 equipments in other ICAO regions. See ICAO Doc 9613 for clarification. FPL2012 24 April 2012

Step 3. - Apply the rules to reduce the number of PBN/ indications For RNAV 10 and RNP 4, file respectively A1 or L1 RNAV 5 (B-RNAV): B1 to be filed instead of B2, B3, B4, B5 (LORAN is not needed/required) B6 (LORAN) to be explicitly indicated if ever applicable For RNAV 2, RNAV 1 and RNP 1: If DME/DME and DME/DME/IRU capable then only file C4, D4 or O4 e.g. file C4 if C3 and C4 apply, D4 for D3 and D4 and O4 for O3 and O4 If “all sensors but IRU” capable then only file C1, D1 or O1 e.g. file C1 instead of C2 and C4, D1 for D2 and D4 and O1 for O2 and O4. For RNP APCH only file S1 or S2 (subject to capability) For RNP AR APCH only file T1 or T2 (subject to capability) FPL2012 24 April 2012

Step 3 cont. - Apply the rules to reduce the number of PBN/ indications If the number of PBN/ capabilities remains greater than 8: Identify the indications considered to be least relevant for the planned flight (from Oceanic to Approach) e.g. Oceanic requirements (A1) for a flight planned entirely within continental EUR airspace Add ‘Z’ to Field 10a and insert the least relevant indication(s) within NAV/ in Field 18 FPL2012 24 April 2012

Step 4. - Ensure Item 10 in conformity with PBN content Sensors must be reflected in Field 10 otherwise FPL rejection For any Nav Spec: If ‘all sensors’ or GNSS filed then G must be in Field 10 If ‘all sensors’ or DME/DME filed then D must be in Field 10 If ‘all sensors’ or INS/IRU filed then I must be in Field 10 If DME/DME/IRU filed then D and I must be in Field 10 Specific rules relating to RNAV 5 (B-RNAV): If filing B1 or B4 then O or S and D must be in Field 10 FPL2012 24 April 2012

FPL2012 24 April 2012

Filing Surveillance Capability (Field 10b) Within each of the following categories of surveillance capability: Transponder (Modes A, C, S) Only one of the published indicators is required ADS-B Either B1 or B2, and/or Either U1 or U2, and/or Either V1 or V2 ADS-C D1 and/or G1 FPL2012 24 April 2012