North Atlantic Initiatives Monday, 17 March 2014; Session 4 (3:30 5:00) PRESENTED BY: Terry Cecil FAA International Operators Conference Tampa, FL March 17 20, 2014
Briefing Objective North Atlantic Initiatives Objective of the briefing is to: Review existing and planned North Atlantic initiatives that affect: operator plans and programs for aircraft equipage and operation with Comm/Nav/Surveillance systems and, where applicable, State operator authorizations 2
North Atlantic Systems Planning Group Major Working Groups Air Traffic Management Group (ATMG) Operations and Airworthiness Subgroup (OPS/AIR) Comm/Nav/Surveillance Group (CNSG) Safety Analysis & Reduced Separation Implementation Group (SARSIG) Implementation Management Group (IMG) North Atlantic Systems Planning Group (NAT SPG) - 3
Websites & NAT Reference Documents ICAO and FAA Sites ICAO European & North Atlantic (EUR/NAT) Office wwwparisicaoint>>eur & NAT Documents>>NAT Documents NAT Doc 007 (NAT Operations & Airspace Manual (2013) NAT Operations Bulletins & NAT Region Update Bulletins NAT Service Development Roadmap (SDR) Planning documents supporting separation reductions & initiatives FAA NAT Resource Guide For US Operators: search on Google Emphasis Items Initiatives Comm/Nav/Surveillance NAT Airspace, etc - 4
Initiatives Currently Underway RLongSM & DLM Phase 1 Reduced Longitudinal Separation Minimum (RLongSM) 5-minute longitudinal separation applied between eligible pairs Gander & Shanwick Control Areas Eligibility: MNPS Authorization, FANS 1/A CPDLC & ADS-C connection Tracks to be loaded using RLongSM at a TBD future date Data Link Mandate (DLM) Phase 1 2 core OTS tracks (identified in OTS track message), FL 360-390 (inclusive) Data Link authorization in accordance with State requirements FANS 1/A (or equivalent) CPDLC & ADS-C operation required - 5
Initiatives Currently Underway (continued) 30 NM lateral, 30 NM & 50 NM longitudinal separation Applied in New York Oceanic between eligible aircraft pairs 30 NM requirements: RNP 4, CPDLC & ADS-C 50 NM longitudinal requirements: RNP 10, CPDLC & ADS-C 50 NM lateral separation in Santa Maria Oceanic Starting 6 March 2014, 50 NM lateral separation applied to aircraft authorized RNP 10 (minimum) or RNP 4 MNPS authorization required Aircraft not authorized RNP 10 or RNP 4 will be accommodated using 60 NM lateral separation - 6
Initiatives Currently Underway (cont) ADS-B Out (5-10 NM separation) Used currently in Canadian coastal regions and southern Greenland primarily to aid in enabling climb and descent Iceland and Portugal scheduled to implement ADS-B services in 2014 Compliance required with EASA AMC 20-24 or equivalent Avionics functionality compliant with DO 260, Do 260A or DO 260B NavCanada AIC 31/11 addresses operator requirements for Operational Specifications or completion of an equipment survey NavCanada AIC 29/13 supplements AIC 31/11 with Flight Crew & ATC procedures 7
FANS 1/A (or equivalent) Data Link Mandate NAT DLM Plan Overview Equipage with and use of CPDLC and ADS-C required in DLM airspace with limited exceptions (eg, State, Humanitarian) Objective: enhance comm, surveillance and ATC intervention capabilities to reduce collision risk Plan announced in ANSP AICs and FAA Notice in 4/Q 2013 Non-DLM airspace: DLM not to be applied in NAT ATS Surveillance Airspace, north of 80 north or, until regulatory action completed, in New York Oceanic NAT ATS Surveillance Airspace: surveillance provided by radar or ADS-B to suitably equipped aircraft (transponder/ads-b Extended Squitter transmitter) - 8
NAT Data Link Mandate (continued) DLM Phase 2A: 5 Feb 2015 target date DLM to be implemented on all NAT OTS tracks between FL 350-390 (inclusive) Operation in non-dlm airspace remains an option NAT DLM Phase 2B: 7 Dec 2017 target date DLM to be applied in all NAT Region airspace between FL 350-390 (inclusive) except specified non-dlm airspace NAT DLM Phase 2C: 30 Jan 2020 target date To be applied in all NAT Region airspace at FL 290 and above except specified non-dlm airspace See previous slide for non-dlm airspace 9
NAT ATS Surveillance Airspace Preliminary Depiction: to be updated in 2014 10
Reduced Lateral Separation Minimum RLatSM trial provisions 25 NM lateral separation and ½ degree track spacing to be applied on designated tracks ½ degree waypoints to be used to define RLatSM tracks (eg, 54 degrees-30 minutes North, 30 degrees West) Only RLatSM eligible aircraft will operate on RLatSM tracks and adjacent tracks Operators need to determine if their aircraft nav databases will need update with NAT ½ degree waypoints (NavCanada leading effort to make ½ degree waypoint data package available in November/December timeframe) Strategic Lateral Offsets (SLOP) will continue to be used 11
RLatSM Trials Enabling technology ADS-C functionality includes: Conformance monitoring alerts controller when reports do not match current flight plan (monitors NEXT waypoint and NEXT PLUS 1) ADS periodic contracts at specified intervals ADS event contracts include the following: lateral deviation event (LDE) of 5 NM or less; level range deviation event (LRDE) 300 ft or less; and waypoint change event (WCE) at compulsory reporting points CPDLC provides enhanced ATC intervention capabilities Operator/Aircraft Requirements MNPS authorization RNP 4 authorization CPDLC and ADS-C equipage and operation All RLatSM CNS systems required to be operational 12
RLatSM Trials (Trial Phases) RLatSM Phase 1 trial NEW target date: 12 Nov 2015 25 NM lateral separation to be applied on three core OTS tracks between FL 350-390 (inclusive) RLatSM tracks to be identified in OTS track message RLatSM Phase 2 trial target date: approx one year after Phase 1 start date RLatSM planned to be applied on all OTS tracks between FL 350-390 (inclusive) RLatSM Phase 3: target date is TBD RLatSM planned to be applied between eligible aircraft in the NAT Region between TBD FLs - 13
RLatSM Trials Operator responsibilities Pilots must understand ½ degree waypoint display on aircraft maps and FMCs Pilots must be disciplined in executing waypoint insertion procedures to avoid navigation errors Will need to independently confirm correct insertion of degrees and minutes of latitude and longitude for each waypoint Will need to independently perform checks to compare Computer Flight Plan to FMC track and distance Pilots must be prepared to execute ICAO Doc 4444 contingency procedures for turn-backs, diversions and for weather deviations to avoid conflict with other aircraft 14
RLatSM Trials Operator Responsibilities (cont) Pilots should maximize use of TCAS II (ACAS II) for situational awareness and collision avoidance Provisions for operational TCAS II (ACAS II) under discussion Operator guidance and direction on RLatSM operations being developed in NAT SPG working groups 15
MNPS to PBN Transition Plan Performance-based Navigation (PBN) transition 2013 2015 Use of RNP 10 as Navigation Specification (NavSpec) to qualify for MNPS authorization endorsed in NAT Regional SUPPS Use of MNPS NavSpec remains valid Proposed for 1 Jan 2015: RNP 10 (minimum) and RNP 4 to replace MNPS as NavSpec for NEW MNPS authorizations Existing MNPS authorizations not affected Date TBD: MNPS designation for NAT airspace will be replaced with designation oriented to Performance Based Operations Current proposal is: NAT High Level Airspace - 16
MNPS to PBN Transition Plan Continued 2020 All aircraft operating in NAT PBO airspace will be authorized RNP 10 (minimum) or RNP 4 MNPS NavSpec no longer valid State (country) authorization processes Individual State authorization processes and documents will need to be updated to reflect MNPS transition provisions Operators will need to coordinate with their State authorities to determine State requirements as transition progresses 17
Performance Based Comm & Surveillance PBCS Implementation Plan Required Communication Performance (RCP) Type: a label (eg, RCP 240) that represents values for communication transaction time, continuity, availability and integrity parameters Required Surveillance Performance (RSP) Specification: a set of ATS provisions, including communication services, aircraft and operator requirements (eg RSP 180) needed for surveillance performance within a defined airspace NAT PBCS Implementation Plan being progressed by NAT SPG working groups NAT CNS Group is the lead 18
NAT PBCS Implementation Status RCP 240 and RSP 180 being used to assess CPDLC and ADS-C performance in NAT operations Provisions to incorporate RCP and RSP into operator data link programs and, where applicable, operator data link authorizations are being progressed in ICAO Panels and NAT SPG groups Suggest that operator groups remain informed on development of PBCS implementation plans 19
Conclusion Significant NAT initiatives progressing in 2014 Operators need to remain informed on status of NAT projects ICAO EUR/NAT Office Website and FAA NAT Resource Guide For US Operators serve as sources for operator information NAT Doc 009 (NAT Service Development Roadmap (SDR)) posted on ICAO Paris EUR/NAT Office Website under NAT Documents SDR provides a listing of NAT initiatives along with schedules for their progression 20