International Civil Aviation Organization

NEW FPL 2012

Transition Phase & Implementation Stages

Victor Hernandez RO ATM/SAR

New FPL implementation & Switchover

• The New FPL regional strategy; – Preparation, Transition, implementation & Post-Implementation Phases – Implementation activities are over the 90% of compliance

• New FPL Safety assessment & testing programme

• AICs and Trigger NOTAM publication

• ATC LOAs

• New FPL Training

• Contingency Measures

• NFPL Post-implementation

Review the New FPL Strategy & Implementation activities SL AN 13/2.5/12/53 - 21/Aug/12

ICAO Secretary General, AN 13/2.5-12/53 - 21 August 2012

Information to be posted on the FITS

• a) planned date for upgrades to Flight Data Processing Systems (FDPS) or any

other system in support of flight plan processing (or date completed);

• b) planned date for testing (or date testing commenced);

• c) planned date for acceptance of new flight plan for trial purposes (or date trials

commenced);

• d) planned date for issuance of Aeronautical Information Circular (AIC) or update

of Aeronautical Information Publication (AIP) (or date of publication); and

• e) planned date for update of Letters of Agreement (LoA) with air traffic services

(ATS) units of adjacent States, if necessary (or date LoA signed).

TRANSITION PHASE

Tactical actions Pre-Tactical actions Strategic actions

Final Training Sessions for Dispatchers, Pilots and ATCOs

Post Implementation Monitoring Programme

Conduct Risk Analysis of

errors, duplication/lack and rejected flight plan data

based on SMS principles

Implementation of mitigation measures

Teleconferences, as

required

NFPL Implementation Project

Trigger NOTAM

September October November November 2 Nov 15 Sep 10 Nov 14 Nov 00 UTC 15 Nov 00 UTC 1 Oct 30 Nov

Application of Contingency Measures (as required)

Publication of posters

20 Oct

On line Testing and Interface

Flight plan data processing

PRESENT and NEW

ANSPs Users

31 Oct 20 Sep

Publication of SUPPLEMENT in the AIP the procedures to fill and

submit FPL data and contact information of the NFPL

Coordination Unit

Development of Contingency

Measures

Identify Switchover TEAM &

NFPL Coordination Unit

120 Hrs.

Verification of submitted

flight plan data

24 Hrs.

Last minute briefings for Staff on duty

Verification of ALL submitted

flight plan data

Switchover Stage

Additional Staff in ATS Units, so as to ensure proper

coordination of NEW FPL/CPL data, as required

IMPLEMENTATION

New FPL Safety Assessment

OBJECTIVE:

• Improve ATS capacity to process the New FPL data

• Demonstrate the feasibility implementation of New FPL, through:

– New FPL Testing Programme

– Analysis of impact of the ATS workload

– Prevent contingency actions

– Determine training programme needs

– Determine mitigation actions to meet the safety goals, based on SMS risk analysis

• Establish post-implementation monitoring programme

New FPL Testing Programme

• Assess impact of PRESENT and NEW flight plan data in processing systems

• Conduct off-line and on-line testing /trails operations with other stakeholders

• Assess various scenarios on errors, duplication and missing flight plan data

• Coordinate applicable mitigation actions with air operators and ATS units

• Determine applicable ATS messages and change-over date (only on-line process)

• Determine technical requirements and operational procedures to ensure process of New FPL data

• Establish change-over date/hour for on-line process of New FPL only

• Determine and publish required information for all stakeholders through bulletins, AICs, NOTAMs. etc.

LOAs, Doc 4444 – Chapter 10

• Objective: – apply standardized procedures for the coordination and transfer of control of flights, in

order to reduce the need for verbal coordination • ATC Units, airspace jurisdiction and classification(s), and responsibilities (and any

delegation of responsibility) for provision of ATS

• Coordination Messages of flight plan and control data using ATS automated systems and/or verbal means

– FPL/RPL for ATFM services at least 60 minutes in advance of the flight – FPL for ATC services 30 minutes prior ETOB

• CPL immediately after take off, or 20 minutes prior transferring point to the UTA/CTA of the adjacent ATC Unit

• EST only after FPL or CPL, 20 minutes prior the transfer control point or boundary point to the adjacent ATC Unit jurisdiction

– Movement and control messages (FPL, DLA, CHG, CNL, DEP, ARR) – Other coordination messages (ACP, LAM, RQP, RQS, SPL)

• Transfer of control: (points, levels or times) • Transfer of communication: (points, levels or times)

LOAs….

• Applicable conditions to transfer and acceptance of control, such as altitude/flight level,

specific separation minima,

• ATS surveillance system coordination procedures, SSR code assignment

• Procedures for approval requests

• Procedures for departing traffic (closer aerodromes to the boundaries); & Holding fixes

and procedures for arriving traffic

• Means of communication

– AFTN, AMHS, Telephone & FAX numbers, email address, etc.

• Applicable contingency procedures and/or ALR/RCF messages

• AIDC messages (Doc 4444, par. 11.4.2.5, Appendix 6) through ATS automated system

• Other coordination provisions

Training Aspects

• Filled and submission of FPL process (Annex 2) • Content and procedures of NFPL, Amendment 1 to Doc 4444

(differences PRESENT – NEW form model) • EEOT -24/120 hrs. • Aircraft capability • PBN Sensor, Item 18

• Applicable ATS messages • Completion of a flight plan • Changes to a flight plan • Closing a flight plan

• LOAs • NOTAMs • Contingency Measures

Navigation Specification and sensor NAV specification Communication and Surveillance Navigation

RNAV 10 (RNP 10) Determined in the implementation process in accordance to local and regional characteristics

No ground-based Navaids required

RNAV 5 (B RNAV) • Direct pilot to ATC Communications • Radar monitoring by ATS

• VOR/DME • DME/DME • INS/IRS • GNSS

RNAV 2/ RNAV 1 • Direct pilot to ATC Communications • Radar surveillance by ATS

• GNSS • DME/DME • DME/DME/IRU • DME/VOR

RNP 4 Determined in the implementation process in accordance to local and regional characteristics (CPDLC, ADS-C, …)

GNSS

RNP 2 Determined based on operational considerations (route spacing, traffic density, etc.)

GNSS

RNP 1 (Basic) • Direct pilot to ATC Communications GNSS

RNP APCH No specific requirements. Obstacle clearance required

• GNSS down to LNAV or LNAV/VNAV minima (SBAS, etc.)

• MIssed approach segment (conventional navaids)

RNP AR APCH No specific requirements. GNSS DME/DME as alternative

RNP 0.3 No specific requirements. GNSS

FPL, PBN Operational reference

PBN, Navigation Specification

NAVEGATION SPECIFICATION

FLIGHT PHASE

En-route Oceanic/ Remote

En-Route Continental Arrival

Approach

DEP Initial Interm. Final Miss

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

2 2

RNP 1 1a 1a 1ab 1a,c

Advanced RNP 2 2 or 1 1 1 1 0.3 1 1

RNP APCH 1 1 0.3 1 RNP AR APCH 1-0.1 1-0.1 0.3-0.1 1-0.1

RNP 0.3 0.3 0.3 0.3 0.3 0.3 0.3

FPL, Aircraft capabilities • A GBAS landing system

• B LPV (APV with SBAS)

• C LORAN C

• D DME

• E1 FMC WPR ACARS

• E2 D-FIS ACARS

• E3 PDC ACARS

• G (GNSS)

• H HF RTF

• I Inertial Navigation

• J1 CPDLC ATN VDL Mode 2

• J2 CPDLC FANS 1/A HFDL

• J3 CPDLC FANS 1/A VDL Mode A

• J4 CPDLC FANS 1/A VDL Mode 2

• J5 CPDLC FANS 1/A SATCOM (INMARSAT)

• J6 CPDLC FANS 1/A SATCOM (MTSAT)

• J7 CPDLC FANS 1/A HFDL SATCOM (Iridium)

• K MLS

• M1 ATC RTF SATCOM (INMARSAT)

• M2, M3 ATC RTF (Iridium)

• O VOR

• P1-P9 Reserved for RCP

• R PBN approved

• T TACAN

• U UHF RTF

• W RVSM approved

• X MNPS approved

• Y VHF with 8.33 channel spacing

• Z Other equipment carried or other capabilities

ICAO New FPL 2012 & PBN

RNAV specifications AI RNA 10 (RNP 10)

B1 RNAV 5 all permitted sensors

B2 RNAV 5 GNSS

B3 RNAV 5 DME/DME

B4 RNAV 5 VOR/DME

B5 RNAV 5 INS or IRS

B6 RNAV 5 LORANC

C1 RNAV 2 all permitted sensors

C2 RNAV 2 GNSS

C3 RNAV 2 DME/DME

C4 RNAV 2 DME/DME/IRU

D1 RNAV 2 all permitted sensors

D2 RNAV 1 GNSS

D3 RNAV 1 DME/DME

D4 RNAV 1 DME/DME/IRU

RNP specifications

In Item 10: R = PBN levels that can be met are shown in Item 18 if FPL In Item 18:

PBN/ indication of RNAV and/or RNP capabilities. Include as many of descriptors below, as apply to the flight, up to a maximum of 8 entries, i.e. a total of not more than 16 characters.

L1 RNP4

O1 Basic RNP 1 all permitted sensors

O2 Basic RNP 1 GNSS

O3 Basic RNP 1 DME/DME

O4 Basic RNP 1 DME/DME/IRU

S1 RNP APCH

S2 RNP APCH with BARO-VNAV

T1 RNP AR APCH with RF (special authorization required)

T2 RNP AR APCH without RF (special authorization required)

Filled and Submission of New FPL data

• Air Operators and users should ensure timely and correct data submission of FPL, CHG, CNL, SPL and/or ARR messages

• Ensure training for related staff

• Ensure sufficient staff and software support during switchover stage

• Coordinate proper mitigation actions with appropriate NFPL coordination Unit, as required

NFPL Contingency Measures Unit

Additional Staff

AIC SUP NOTAM

Training (Military,

GA, others)

ALT. COMM LOAs PROCEDURES

Who are concerned? X X

Local, regional X X X

Use of Convertor (Central America, Kingston, Curacao)

X X X X X

Errors/Lack NFPL data (originator, rejected data)

X X X X X

Qualified Personal X

Lack of Communication (TX/RX)

X X X X X

Lack of NFPL information X X X X X X

Lack of training for Pilots (GA, Military, others)

X X X X X X X

Pre-Implementation Stage (120 hrs. before)

Switchover • Establish NFPL Coordination Unit, as required to monitor

Switchover activities • Identification of the ANSP Switchover Team to ensure data

process for – New FPL Reception – New FPL Revision data – New FPL Submission

• Identify New FPL duplication, error and rejection data • Analyze and Coordinate mitigation measures of flight plan

data with air operators and adjacent ATS units • Conduct regional TELECONFERENCES

16

Implementation Stage (24 hrs. before)

• Reinforcement of technical & ATC staffing and supervision shift

• Last minute briefings for Technical & Operational Staff on duty

• Review and Ensure communication and software support

• Active NFPL Coordination Unit for air operators

• Implementation of Contingency measures, as required

NFPL coordination Unit E-mail: nfpl@anspunit.com Phone: + () xxx + () xxx Fax: + () xxx

Implementation Stage

• Starting at 0000 UTC of 15/NOV/12, ALL Stakeholders should comply with ICAO provisions for the New FPL form

• Maintain availability to conduct regional coordination 24 hrs prior until 24 after the New FPL Implementation Time (0000 UTC 15/11/12)

• Provide first implementation progress report on 18.00 UTC 16/11/12

• Provide daily reports to ICAO as of 15/11/12 (until cancelled)

• Carry out coordination with stakeholders and other ANSPs, as needed

NFPL Post-Implementation Phase

• Based on historical Testing Programme conducted during the transition phase assess errors, duplication and missing flight plan data

• Conduct risk analysis based on SMS principles

• Define required risk mitigation actions

• Conduct close coordination with air operators and ATS units to implement applicable mitigation actions and/or new procedures

• Maintain historical document of risk analysis and management actions

• Define and implement new technical requirements and/or operational procedures to correctly process the New FPL

• Publish new required regulations and/or procedures

NEW FPL Implementation activities

QUESTIONS?