pbn task force

8/2/2019 PBN Task Force

1/23

1

THE NAVIGATION APPLICATIONS &THE NAVIGATION APPLICATIONS &NAVAID INFRASTRUCTURE STRATEGYNAVAID INFRASTRUCTURE STRATEGY

FOR THE ECAC AREAFOR THE ECAC AREA

ICAO PBN Task ForceICAO PBN Task Force


2/23

2

NAVIGATIONNAVIGATIONSTRATEGY FORSTRATEGY FOR

ECAC AREAECAC AREA ICAOSPBN

CONCEPT

ECTLECTL

ENVIRON.ENVIRON.

POLICY &POLICY &

STRATEGYSTRATEGY

EVOLVINGEVOLVING

TRADETRADE--OFFSOFFS

NEWNEWAIRCRAFT OPRAIRCRAFT OPR

A380/B787A380/B787

VLJ/UASVLJ/UAS

GNSSGNSS

POLICYPOLICY

A Changing ContextA Changing Context

2015ECAC

AIRSPACE

CONCEPT

2020+

SESARSESARCONOPSCONOPS

ICAOGLOBAL

ATMCONCEPT

2015ECAC

AIRSPACE

CONCEPT

2020+

SESARSESARCONOPSCONOPS


3/23

3

NAV Developments: A 2-Phase Approach

En-Route and TMA

2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 202x

Too large a step in functionalityToo large a step in functionality

Too long a delay to benefit from latest capabilityToo long a delay to benefit from latest capability

Today 2020+SESARSESAR

CONOPSCONOPS

2015ECAC

AIRSPACE

CONCEPT


4/23

4

En-Route and TMA

2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 202x

NowB-RNAV Mandatory en-route

Above defined FLP-RNAVfor TMA RNAV

SESARBusiness

Trajectories4D NAV

Too large a step in functionalityToo large a step in functionality

Too long a delay to benefit from latest capabilityToo long a delay to benefit from latest capability

2015 ECAC2015 ECAC

Airspace ConceptAirspace Concept

and Strategyand StrategyVNAVVNAV

RTARTARF/FRT etcRF/FRT etc

NAV Developments: A 2-Phase Approach


5/23

5

ECAC RNAV Applications

B-RNAV

Initial application En-route nominally

above FL95

Not suitable for TMA 5NM 95%

Identical to RNAV 5

P-RNAV

1NM 95% Support Terminal

Operations

Basis of RNAV 1 Some differences

related to DME/Inertialapplication


6/23

6

THE NAVIGATION APPLICATION &

NAVAID INFRASTRUCTURE STRATEGY

4 Strategic4 StrategicStreamsStreams

2

008

2

02

0


7/23

7



4 Strategic4 StrategicStreamsStreams

2

008

2

02

0

EN ROUTE

TERMINAL

APPROACH &

LANDING

NAVAID

INFRASTRUCT.


8/23

8



U

S

E

R

P

R

E

F

E

R

R

E

D

T

R

A

J

EC

T

O

R

I

E

S

IMP OR VEDACCESS/SAFETY

IMPROVEDLO

RWVSI OPE .

Phased improvement of Nav capability towards 4D contract

PhasedimprovementofNavcapabilitytowards4Dcontract

IncreaseVerticalGuida

nceonAPCH/Eliminate

NPAs

Enablingnewtechnologytoimpro

veLowVisOPR

Rationalise Ground-Based Navaids

Increasing use of GNSS

EN ROUTE

TERMINAL

APPROACH &

LANDING

NAVAID

INFRASTRUCT.


9/23

9



2

008

2

02

0

EN ROUTE

TERMINAL

APPROACH &

LANDING

NAVAID

INFRASTRUCT.

AA--RNP 1 Spec.RNP 1 Spec.

RFRF IIIIRoutesRoutes FRTFRT IIIIRoutesRoutes

IIIIOffsetOffset

RTARTA

3D3D ManagemManagem..

RNAV HoldingRNAV Holding

20152015

20152015


10/23

10



2

008

EN ROUTE

TERMINAL

APPROACH &

LANDING

NAVAID

INFRASTRUCT.

4D4D Bus.Bus.TrajectTraject..

202x202x

202x202x


11/23

11



2

008

2

02

0

EN ROUTE

TERMINAL

APPROACH &

LANDING

NAVAID

INFRASTRUCT.

End ofEnd of Dive &Dive &

DriveDrive removeremove

NPANPAss


12/23

12



2

008

202

0

EN ROUTE

TERMINAL

APPROACH &

LANDING

NAVAID

INFRASTRUCT.

ImprovedImproved

AccessAccess

More LandingMore Landing

SystemsSystems


13/23

13



2

008

202

0

EN ROUTE

TERMINAL

APPROACH &

LANDING

NAVAID

INFRASTRUCT.

DecommissionDecommission

NDBs .. VORsNDBs .. VORs

Over timeOver time..


14/23

14



2

008

202

0

EN ROUTE

TERMINAL

APPROACH &

LANDING

NAVAID

INFRASTRUCT.

IncreasingIncreasing

Reliance onReliance on

GNSS / withGNSS / withGalileoGalileo


15/23

15


NAVAID INFRASTRUCTURE STRATEGY2008 2010 2012 2014

2013 2015 2020

EN ROUTE

TERMINAL

(ARR & DEP)

APPROACH,

&

LANDING

P-RNAV

A-RNP1

P-RNAV

RNP

APCH1LPV 200

(SBAS)

Cat IIIILS

Cat I GLS(GBAS/ GPS)

Cat III GLS(GBAS/ GPS)

Ca t III GLS

(Multiconstellation)

4DA-RNP1

Increa sing use: Spac e-b ased Nava ids

LPV

(SBAS)

1a2

2

3

3

4

5 8

9

A

Cat IIIMLS

Rationa lisation: Ground -b ased Navaids

EVOLUTION

OF NAVAI D

INFRASTRUCT.

B CD

7

11 12

E

Loc alizer Perf.

with Vert. Guidance

ILS

Sustainme nt

1

RNP ARAPCH 13

GBAS EGNOSGALILEO

1c

1e

1b

U

S

E

R

P

R

E

F

E

R

R

E

D

TR

A

J

E

C

T

O

R

I

ES

1f

GPS L5

1d

2009 2011

6

10

4D

IMPOR VED

ACCESS/SAFETY

IMPROVEDLO

RWVSI OPE .


16/23

16

Nav Application Evolution

P-RNAV

B-RNAV

Advanced RNP

2005 2010 2015 2020

E

NROUTE

P-RNAV

B-RNAV

Advanced RNP

CONVENTIONAL

RNP APCHc

LPV (APV I)

NPA: CONV.RNAV (LNAV)

LPV 200APPROACH

GBAS Cat IIIa

GBAS Cat IIIb

ILS/MLS (All Cat)GBAS Cat I

awith GPS

bwith GalileoT

/O

&

LANDIN

G

TERMINAL

c


17/23

17

Implementation DriversImplementation Drivers

Safety

Capacity

Efficiency

Environmental


18/23

18

BB--RNAVRNAV

Enables ARN route structure changes

Removed bottlenecks

Reduced track miles

Enables additional routes

Did not use RNP terminology pre-PBN

Identified that functionality more important than accuracy

Terminology ICAO EUR Doc 003

First step

Implemented 1998

En-route only

Expected to be replaced by future requirements


19/23

19

PP--RNAVRNAV

Provides link from en-route structure to airports

Needed urgently as BRNAV not suitable Increase procedure flexibility

But

P-RNAV certification slow

Forced many states to find alternatives (BRNAV+ etc)

Harmonisation was protracted

PRNAV applications will extend: Accuracy requirement in line with present capabilty

Probably employed en-route as well as TMA

But A-RNP 1 could start to replace in 2017 timescale


20/23

20

Advanced RNPAdvanced RNP--11

Placeholder in PBN Manual

Consultation on functionality starting - PBNSG Provide capabilty for

closely spaced routes

Holding

Vertical

Possibly Initial timing control- RTA

Aim at capabilty available in the most advanced

systems today Needed to provide performance needed for dense

continental airspace

Benefits analysis underway


21/23

21

Next StepsNext Steps EnEn--Route and TMARoute and TMA

A-RNP-1 needs strong business case

Route Network Development identified need for2017 period closely spaced routes

Airspace Strategy identified need for a step towardsSESAR in 2017 period

Timescales

For 2017 implementation need 2010 agreement

EASA AMC development timescale 2011 earliest?

Placeholder in PBN Manual


22/23

22

APVAPV

SBAS APV and APV Baro VNAV both being enabled

Safety

Improved access

Replace Dive and Drive procedures

Seeking to support Service providers to implement

Wide variation in airport requirements

Customer base

Prevailing met conditions

Unlikely to be able to produce ECAC wide businesscase

Support individual business cases


23/23

23

DiscussionDiscussion

PBN Implementation

Concentrate initially on APV

Maintain B-RNAV/P-RNAV

Avoid any confusion by changing target

avoid interruption of progress on P-RNAV

Support development of A-RNP 1

Longer term ATM potential

Move to A-RNP in 2017 period

pbn task force

Documents