Está en la página 1de 15

Flight Planning from a PBN perspective

Aline TROADEC (EUROCONTROL)


RNAV Approach specialist
18/10/2012

Flight dispatch / flight planning training (TR3)


Table of content

• 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
• What comes next and Conclusion
Flight Planning from a PBN perspective 2
FPL 2012 – what it is

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


FPL 2012:
PBN capabilities and approvals (Item 18)
• PBN codes are made of:
Sensor certified for use with the nav spec
– a “Letter”: the NAV spec
– A “Number”: the sensor(s)

All permited sensors

(or VOR/DME for B4)


certified for use with the

DME/DME/IRU
NAV spec

DME/DME

INS/IRS

LORAN
GNSS
The sensor
(1) (2) (3) (4) (5) (6)
The NAV spec
RNAV 10 A1
Navigation Specification

(A)
RNAV 5 (B) B1 B2 B3 B4 B5 B6
RNAV 2 (C) C1 C2 C3 C4
RNAV 1 (D) D1 D2 D3 D4
RNP 4 (L) L1
RNP 1 (O) O1 O2 O3 O4
RNP APCH (S) S1 or S2 (with Baro) (1)
RNP AR APCH (T) T1 or T2 (with RF) (1)

(1) Contrary to other NAV specs, Number "1" and "2" aren't used for the sensor.
Flight Planning from a PBN perspective – extra slides 4
Guidelines for pilots and
flight dispatchers within EUR region
Identify PBN NAV spec “approvals” you hold for each phase of
Step 1
flight
Step 2 File “R” for PBN in Item 10
Enter “PBN/” in Item 18 and apply rules to reduce the number of
Step 3
codes in item 18

More than
8 codes? No
Yes Sine qua
Identify those considered least relevant none FPL will
Step 4 to the planned flight and insert them be rejected!
within Item 18 under “NAV/”
Identify the specific NAV equipment supporting each Nav Spec
!
Step 5
and file in Item 10 ensuring conformity with the content of Item 18

Developed by EUROCONTROL &


the European 2012 Task Force
Flight Planning from a PBN perspective 5
Example – Filling a FPL (1/4)

Approvals
• MNPS • Boeing 757
• AMC 20-12
– RNAV 10 (RNP 10) based on dual
INS/IRU
• AMC 20-4 Nav equipment
– RNAV 5 (B-RNAV) based on • ADF
DME/DME, VOR/DME and
INS/IRU
• DME
• ILS
• AC 90-100A
• INS
– RNAV 1, RNAV 2 based on
DME/DME/IRU • VOR
Flight Planning from a PBN perspective – extra slides 6
Example – Filling a FPL (2/4)
step 1 (ops approvals)
Sensor certified for use with the nav spec
No ops approval for
All permited sensors

(or VOR/DME for B4)


Terminal

DME/DME/IRU
DME/DME

INS/IRS

LORAN
To be retained for Item
GNSS

(1) (2) (3) (4) (5) (6) 18 under PBN/:


Oceanic
RNAV 10 (A) A1 - A1
RNP 4 (L) L1
RNAV 5 (B) B1 B2 B3 B4 B5 B6 - B3 B4 and B5
En-Route RNAV 2 (C) C1 C2 C3 C4
- C4
RNAV 1 (D) D1 D2 D3 D4

Terminal
RNAV 1 (D) D1 D2 D3 D4 - D4
RNP 1 (O) O1 O2 O3 O4
RNP APCH (S) S1 or S2 (with Baro) (1) (’R’ will have to be
Final
RNP AR APCH (T) T1 or T2 (with RF) (1)
filled in Item 10)
NMPS approved ‘X’ retained for Item 10

Flight Planning from a PBN perspective – extra slides 7


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

Item 10
• ADF • F
NAV • DME • D√
equipment • INS • I √
• ILS • L or S
• VOR • O or S√

MNPS approved • X

Nb of codes ≤ 8

Item 18
• PBN/ A1 B3 B4 B5 C4 D4 • R
Either G and/or I O D
Note: ‘S’ would be used instead of ‘O’ & ‘L’ if the aircraft is also fitted with VHF & RTF
Flight Planning from a PBN perspective – extra slides 8
Example – Filling a FPL (4/4)
Final FPL content
• Nav equipment (Item 10)
– ADF, DME, ILS, INS, VOR.
– MNPS - only filed in Item 10 (X)
T RULES TYPE OF FLIGHT

• PBN (Item 18)


de vol Type de vol

10 EQUIPMENT
Équipement

DFH I S R X E
– RNAV 10
• Dual Inertial
– RNAV 5
18 OTHER INFORMATION
• DME/DME, VOR/DME, INS/IRU
Renseignements divers

– RNAV 1 and 2
PBN / A1 B3 B4 B5 C4 D4 • DME/DME/IRU
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)
Flight Planning from a PBN perspective – extra slides 9
What’s next?

• ICAO doc 9613 will be updated before end 2012 (new


NAV specs : RNP 2, A-RNP & RNP 0.3 )
• … but “FPL 2012” does not capture this
• PANS-ATM will likely have to be updated
– In compatibility with FPL 2012 (alphanumerical logic)
– “max 8 codes” limit to be withdrawn
• How this information about advanced CNS and PBN
capabilities will be used is not completely clear, but
this shall be correct information for when this is
useful information to enable maximising the
potential benefits of these new applications.
Flight Planning from a PBN perspective 10
Where to find more
information?

• Information and status of States:


http://www2.icao.int/en/FITS/Pages/home.aspx
• FAA Implementation:
http://www.faa.gov/go/fpl2012
• Guidelines for EUR and training material available
on the EUROCONTROL website:
http://publish.eurocontrol.int/sites/default/files/cont
ent/documents/nm/flight-planning/icao-2012/icao-
2012-guidance-latest.pdf
http://publish.eurocontrol.int/articles/icao-flight-
planning-modifications-2012-training
Are we ready for the
change on 15th
November 2012 ?
BACKUP SLIDES
FPL 2012 guidelines :
consistency table (Item 10 vs. 18)

Flight Planning from a PBN perspective – extra slides 14


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 15