Flight Planning from a PBN perspective

Aline TROADEC (EUROCONTROL) RNAV Approach specialist

18/10/2012

ATM technical requirements for FPL (AMT3)

2

• The requirement: To provide aircrew and aircraft related PBN information to ATFM systems and ATC

• The solution: ICAO FPL 2012 (mandatory from 15th November 2012)

• Guidelines to pilots and flight dispatchers for adoption of the new provision for EUR region

• Challenges for the future

Flight Planning from a PBN perspective

Table of content

3

• FPL layout is unchanged • Item 10

– NAV equipment/sensor – Unchanged codes: D, F, G, O, T and I – Removed code: P for P-RNAV – New codes: R (for PBN amplified in Item 18),

B (in case of APV SBAS (LPV) approved) and S

• Item 18 – PBN capability and associated approval – Captures under PBN/… with a maximum of 8 codes (16

characters)

Flight Planning from a PBN perspective

FPL 2012 – what it is

4

• PBN codes are made of: – a “Letter”: the NAV spec – A “Number”: the sensor(s)

certified for use with the NAV spec

FPL 2012: PBN capabilities and approvals (Item 18)

All p

erm

ited

sens

ors

GNS

S

DME/

DME

DME/

DME/

IRU

(or V

OR/

DME

for B

4)

INS/

IRS

LORA

N

(1) (2) (3) (4) (5) (6)

(A) A1(B) B1 B2 B3 B4 B5 B6(C) C1 C2 C3 C4(D) D1 D2 D3 D4(L) L1(O) O1 O2 O3 O4(S)(T)

RNP APCHRNP AR APCH

S1 or S2 (with Baro) (1)

T1 or T2 (with RF) (1)

Sensor certified for use with the nav spec

Nav

igat

ion

Spe

cific

atio

n RNAV 10RNAV 5RNAV 2RNAV 1RNP 4RNP 1

The NAV spec The sensor

(1) Contrary to other NAV specs, Number "1" and "2" aren't used for the sensor. Flight Planning from a PBN perspective – extra slides

5 Flight Planning from a PBN perspective

Guidelines for pilots and flight dispatchers within EUR region

Step 1

Step 3

Step 5 Identify the specific NAV equipment supporting each Nav Spec and file in Item 10 ensuring conformity with the content of Item 18

Enter “PBN/” in Item 18 and apply rules to reduce the number of codes in item 18

Identify PBN NAV spec “approvals” you hold for each phase of flight

Step 2 File “R” for PBN in Item 10

Step 4 Identify those considered least relevant to the planned flight and insert them within Item 18 under “NAV/”

More than 8 codes?

Yes No

Developed by EUROCONTROL & the European 2012 Task Force

Sine qua none FPL will

be rejected!

!

6 Flight Planning from a PBN perspective

What about new NAV specifications?

• ICAO doc 9613 will be updated before end 2012 • Inclusion of new NAV specs : RNP 2, A-RNP & RNP 0.3 • These are not covered in “FPL 2012” provision • We need more codes in PANS-ATM (before FF-ICE)

– Compatible with FPL 2012 (alphanumerical logic) – ASSUMPTION : “max 8 codes” limit to be withdrawn

• Detailed information on advanced CNS and PBN capabilities will now be available, next step in the process is using this so as to maximise the potential benefits of these new applications.

Are we ready for the

change on 15th November 2012 ?

BACKUP SLIDES

Approvals • MNPS • AMC 20-12

– RNAV 10 (RNP 10) based on dual INS/IRU

• AMC 20-4 – RNAV 5 (B-RNAV) based on

DME/DME, VOR/DME and INS/IRU

• AC 90-100A – RNAV 1, RNAV 2 based on

DME/DME/IRU

• Boeing 757

Nav equipment • ADF • DME • ILS • INS • VOR

Example – Filling a FPL (1/4)

Flight Planning from a PBN perspective – extra slides 9

No ops approval for Terminal

To be retained for Item 18 under PBN/: - A1 - B3 B4 and B5 - C4 - D4 (’R’ will have to be filled in Item 10)

NMPS approved ‘X’ retained for Item 10

Example – Filling a FPL (2/4) step 1 (ops approvals)

All

perm

ited

sens

ors

GN

SS

DM

E/D

ME

DM

E/D

ME/

IRU

(o

r VO

R/D

ME

for B

4)

INS/

IRS

LOR

AN

(1) (2) (3) (4) (5) (6)

(A) A1(L) L1(B) B1 B2 B3 B4 B5 B6(C) C1 C2 C3 C4(D) D1 D2 D3 D4(D) D1 D2 D3 D4(O) O1 O2 O3 O4(S)(T)

S1 or S2 (with Baro) (1)

T1 or T2 (with RF) (1)

RNAV 1

Oceanic

En-Route

Terminal

Final

Sensor certified for use with the nav spec

RNAV 10

RNAV 5RNAV 2

RNAV 1

RNP 4

RNP 1RNP APCHRNP AR APCH

Flight Planning from a PBN perspective – extra slides 10

Item 10 • F • D • I • L or S • O or S

• X

• R

Note: ‘S’ would be used instead of ‘O’ & ‘L’ if the aircraft is also fitted with VHF & RTF

• ADF • DME • INS • ILS • VOR

NAV equipment

√ √

MNPS approved

√

• PBN/ A1 B3 B4 B5 C4 D4 Item 18 Nb of codes ≤ 8 √

Example – Filling a FPL (3/4) steps 2, 3, 4 and 5

Either G and/or I D O

Flight Planning from a PBN perspective – extra slides 11

T RULES de vol

10 EQUIPMENT Équipement

TYPE OF FLIGHT Type de vol

• Nav equipment (Item 10) – ADF, DME, ILS, INS, VOR. – MNPS - only filed in Item 10 (X)

• PBN (Item 18) – RNAV 10

• Dual Inertial

– RNAV 5 • DME/DME, VOR/DME, INS/IRU

– RNAV 1 and 2 • DME/DME/IRU

DFH I S R X E

18 OTHER INFORMATION Renseignements divers

PBN / A1 B3 B4 B5 C4 D4

A1 RNAV 10 (sensors not required in Item 10)

B3 RNAV 5 DME/DME (D in Item 10)

B4 RNAV 5 VOR/DME (O or S in Item 10)

B5 RNAV 5 INS/IRU (I in Item 10)

C4 RNAV 2 DME/DME/IRU (D and I in Item 10)

D4 RNAV 1 DME/DME/IRU (D and I in Item 10)

Example – Filling a FPL (4/4) Final FPL content

Flight Planning from a PBN perspective – extra slides 12

FPL 2012 guidelines : consistency table (Item 10 vs. 18)

Flight Planning from a PBN perspective – extra slides 13

FPL 2012 guidelines step 3: rules for PBN codes in Item 18

• RNAV 5 (B-RNAV): – Insert only B1 if the flight qualifies for all of the following: B2, B3, B4,

B5. – Insert B6 if the flight qualifies by using LORAN C.

• RNAV 2, RNAV 1 and RNP 1: – Insert C4, D4 or O4, as appropriate, if the flight qualifies via DME/DME

and DME/DME/IRU e.g. file C4 if both C3 and C4 apply, file D4 if both D3 and D4 apply, etc. – Insert only C1, D1, O1, as appropriate, if “all sensors and IRU” capable e.g. file C1 if both C2 and C4 apply, file D1 if both D2 and D4 apply, etc.

• RNP APCH: – Insert either S1 or S2, subject to capability

• RNP AR APCH: – Insert either T1 or T2, subject to capability

Flight Planning from a PBN perspective – extra slides 14