nextgen overview with focus on data link

1 | © 2017 Rockwell Collins. All rights reserved. Proprietary Information.

NextGen Overview with Focus on Data Link

Rockwell Collins Operators Conference

Presented by Christian Renneissen


Agenda

Future Air Navigation System FANS 1/A+

ICAO GOLD Document

Components of FANS 1/A+

Logon and Handoff Process

Coverage Maps

Mandates and Requirements

PBCS

FANS CPDLC DCL

U.S. Enroute CPDLC

ARINCDirect Support

ARINCDirect FANS Testing


The Idea of Data Link The third step…

1. Visual

– Beacons and Signage

2. Aural

– Voice

3. Data-to-Text

– A method communicating with an aircraft, while limiting voice radio traffic


FANS 1/A+

FANS 1/A is the suite of software upgrades that implement CPDLC, ADS-C, AFN and AOC communications over ACARS protocols. FANS 1 was originally developed by Boeing, while FANS A was developed by Airbus. The two systems are functionally identical so standardization efforts changed the naming convention to FANS 1/A.

FANS 1/A+ added the message latency timer function

Future Air Navigation System 1/A+


FANS 1/A+

Three components:

1. Air Traffic Facilities Notification (AFN) – aircraft logon to ATC Center

2. Controller Pilot Data Link Communication (CPDLC) – data link messaging for communications between air traffic controllers and crews

3. Automatic Dependent Surveillance – Contract (ADS-C) –contract based position reporting

Via data link over VHF (VDL Mode A or VDL Mode 2) or SAT (Inmarsat or Iridium)

Future Air Navigation System 1/A+


GOLD Document Global Operational Data Link Document

• ICAO's GOLD Document is a worldwide, collaborative effort to standardize Data Link procedures. It is the result of the progressive evolution of two documents:

• The FANS 1/A Operations Manual, prepared initially by the informal South Pacific Air Traffic Services Coordinating Group (ISPACG); and

• The Guidance Material for ATS Data Link Services in North Atlantic Airspace, produced by the North Atlantic FANS Implementation Group (NAT FIG), on behalf of the North Atlantic Systems Planning Group (NAT SPG)

• Current: Second Edition dated 26 April 2013

• Next edition was planned for November 2016


CPDLC

CPDLC is a means of communication between controller and pilot, using text messaging via data link for Air Traffic Control (ATC) communication. The CPDLC application has three primary functions:

the exchange of controller/pilot messages with the controlling ATC authority

the transfer of ATC authority over that aircraft and downstream clearance delivery

or the opportunity of adjacent ATC centers to view the aircraft reports

Pre-defined message set, with free text if required

Replaces verbal ATC instructions and crew requests over radio frequencies reducing frequency congestion

Communication via data link significantly reduces receive and read back errors

Controller Pilot Data Link Communications


ADS-C

ADS-C is a contract between a ground ATC system and the aircraft using various systems on board the aircraft to automatically provide aircraft position, altitude, speed, intent, and meteorological data

ATC establishes the reporting period and information requested in the ADS-C Contract and up to 5 ATC Centers can monitor the aircraft simultaneously

Avionics report contracts as established by ATC with no intervention from the flight crew

Replaces position reports by HF radio reducing frequency congestion

Types of ADS-C reports: Periodic, Demand, Event and Emergency

Automatic Dependent Surveillance - Contract


FANS Logon and Handoff Process


Human Factors Considerations

Increased “head down time” for flight crew.

Flight deck Human Machine Interface limitations and issues.

Time required for reading/interpreting uplinks.

Time required for selecting/composing/sending downlinks

Maintaining a shared crew awareness of the progress of ATC data link communications.

Situational awareness and the inability of pilots to monitor other data link transmissions in the area of operations.


Current Enroute FANS Coverage


FANS Coverage in Europe


FANS CPDLC Mandates

Phase 2A

As of Feb 2015 FL 350-390 on all North Atlantic (NAT) Tracks

Phase 2B - Current

Dec 2017 FL 350-390 within NAT Data Link Mandate (DLM) Region

Phase 2C

January 2020 - Above FL 290 within NAT Data Link Mandate (DLM) Region


NAT DLM Region vs. ATS Airspace

Blue outline: NAT DLM Region

Pink areas: not included in NAT DLM. ATS Surveillance Airspace (via land-based RADAR or ADS-B)


FANS Requirements

Equipment Requirements:

VHF Data Link (VDL Mode A or VDL Mode 2)

HF Data Link (HFDL) or;

SAT Data Link (Inmarsat, Iridium, or MTSAT)

FAA approved FANS CPDLC training

Letter of Authorization for US based operators conducting FANS 1/A operations outside of the United States

ICAO Flight Plan filing with required equipment codes and information


Equipment/Flight Plan Requirements for FANS 1/A+

FANS CPDLC/ADS-C

capable

Letter of Authorization

File ICAO Flight Plan

Indicate equipage in

Fields 10 & 18

• Item 10a of the ICAO Flight Plan:

•"J2" for FANS CPDLC HFDL •"J3" for FANS CPDLC VDL Mode A •"J4" for FANS CPDLC VDL Mode 2 •"J5" for FANS CPDLC SATCOM (Inmarsat) •"J6" for FANS CPDLC SATCOM (MTSAT) •"J7" for FANS CPDLC SATCOM (Iridium)

• Item 10b of the ICAO Flight Plan:

•“D1“ ADS-C with FANS Capabilities

• Indicate tail number in Field 18 (Other Information) REG/


Performance Based Communication and Surveillance

AC 90-117 Data Link Communications for U.S. Operators (LOA)

PBCS assures CPDLC and ADS-C perform to desired ATM levels.

PBN complements but is not PBCS :

– PBN: deals with RNP/RNAV criteria allocated to aircraft/operator

– PBCS: deals with RCP/RSP criteria allocated to ATS/CSP/aircraft/operator

By 29 March 2018 U.S. Operators must submit a new A056

– Indicate whether or not PBCS is desired to be used

– Indicate performance level (e.g. RCP240/RSP180)

– Otherwise seize data link ops

Let’s talk paperwork


Definitions of RCP/RSP

• Required Communication Performance (RCP): The RCP Transaction Time defines the maximum time required for the completion of the transaction after which the initiator should revert to an alternative procedure.

• Required Surveillance Performance (RSP): The RSP Surveillance Data Transit Time describes the time required for delivery of surveillance data in seconds.


PBCS Monitoring

Required as per Chapter 6 of AC 90-117

Review the PBCS monitoring results for your aircraft at https://www.faa.gov/air_traffic/separation_standards/PBCS_Monitoring/

Results indicating failure

Follow directions to remedy

Insufficient Performance Data

Initial compliance can be based on Statement of Compliance (SOC), obtained from your OEM, and proof of any monitoring.

https://www.faa.gov/air_traffic/separation_standards/PBCS_Monitoring/

https://www.faa.gov/air_traffic/separation_standards/PBCS_Monitoring/


PBCS Basics

Do we need it?

PBCS Approval not required to merely enter airspace

PBCS Approval and PBN required to partake in PBCS separation

RlatSM (23NM lateral) in OTS are designated as PBCS Tracks

Review item 3 in OTS message for use of RlatSM


Where is PBCS Airspace?

Flight Planning


Indicate PBCS Level

Flight Planning

By 29 Mar 2018 PBCS must be indicated to partake in PBCS operations

P1 (RCP400) corresponding entry in Field 18: SUR/RSP400

P2 (RCP240) corresponding entry in Field 18: SUR/RSP180

P3 (RCP400) – SATVOICE not planned for use in near term


Rockwell Collins ARINC is signatory to the PBCS Charter

Alternate Means of Compliance as per AC 90-117 #4.5

N 8900.446 adds to the requirements for your OpSpec and LOA A056:

Operator to prove CSP meets FAA Requirements

AC 90-117 §4.5 offers Alternate Means of Compliance: Global PBCS Charter

Rockwell Collins/ARINC is signatory as your CSP


U.S. Domestic FANS CPDLC DCL

FANS Logon to DCL Capable Tower via VDL Mode A or VDL Mode 2

No LOA required for US registered aircraft

Flight Plan Field 10a and Field 18 entries required

DCL does not replace PDC

Data Link Departure Clearance


U.S. FANS DCL Airports

A global first

The first step to domestic Data Link

All FANS equipped operators may use

FANS DCL is not ARINC 623 DCL

56 online since 2016


Domestic use of FANS DCL

Departure Clearance Service (DCL) provides automated clearance delivery for initial and revised departure clearances

CPDLC message elements for the following:

Flight plan route

Initial and requested altitude

Beacon code assignment and

Departure frequency

Data Link Departure Clearance


How is a CPDLC capable airport depicted?


Equipment/Flight Plan Requirements for FANS DCL

Must use VDL as media for FANS

File ICAO Flight Plan

Indicate equipage in

Fields 10a & 18

Depending on your equipage item 10a of the ICAO Flight Plan may indicate:

“J3” for FANS CPDLC VDL Mode A and, or

“J4” for FANS CPDLC VDL Mode 2

The FAA does not recognize SAT Data Link as media for FANS DCL

Indicate DCL and PDC preferences in Field 18 DAT/

E.g. “DAT/1FANS2PDC” or “DAT/1FANSP2PDC”

Alternatively indicate DCL and PDC preferences via the FAA’s Subscriber Database


Logon to “KUSA”

New ident due to NSDA

Up to 90 mins prior filed ETD

Logon “Accepted” = AFN_AK

No additional action required


ATC Comm Established

CPDLC is Active

30 mins prior filed ETD

Clearance Delivery approves FPL

Behind the scenes exchange:

ATC sends “CR1”

Aircraft responds “CC1”

CPDLC is now active


ATC Message

DCL Received

Aural Warning

Visual Warning


DCL Review

Acceptance

Both crew should:

Review the DCL separately

Discuss the clearance

Choose to accept or reject


No 60 sec timer on the ground

DCL comes w/ loadable route

May receive a revision during taxi

Auto-logoff after departure


Logon Failure

Any CPDLC Failure

Revert to voice

Controller receives an error message

2nd preference “PDC” only works if DCL is inop at the ATC level.


Looking ahead into NextGen

Transition from individual Logons to National Single Data Authority (NSDA) supporting enroute CPDLC

A single FANS Logon designed to carry through the enroute phase

Enroute CPDLC rollout later in 2018

Future integration with foreign partners

FANS DCL is just the beginning


Participation in U.S. Enroute CPDLC

Only VDL Mode 2 equipped operators (“J4” in Field 10a)

Indicate Enroute FANS in Field 18 using “DAT/FANSE”

Other possible entries:

U.S. Requirements


Where is Domestic CPDLC? Resources

Limited Data Comm Functional Verification (DFV) between May and September

KZKC (Kansas City)

KZME (Memphis)

KZID (Indianapolis)

Work with your Service Provider for continued updates.


Scenarios

DCL Departure from within Enroute CPDLC enabled airspace

DCL Departure from outside of Enroute CPDLC enabled airspace

Non-DCL Departure from within Enroute CPDLC enabled airspace

Non-DCL Departure from outside of Enroute CPDLC enabled airspace

Resources


ARINCDirect supports FANS CPDLC, ADS-C and DCL FANS Testing for ARINCDirect customers is Free of Charge

FANS Testing is done over the live network via VHF or Satellite data link so data link issues can also be identified

Customers can test for new installations, training purposes, refresher before trips and for troubleshooting any FANS issues

Two types of testing: Manual and Automated

Access to and transcripts of messaging logs

FANS Training and LOA Assistance


Support needed? Contact me: [email protected]

mailto:[email protected]


Aircraft Surveillance Evolution ADS-B

Mode S ELS (mandatory)

Flight ID

Mode S EHS (mandatory)

Hdg, Roll

TAS/IAS/GS/VS

TK, TKE, Mach

Sel ALT

ADS-B DO-260

(voluntary)

24bit ID

Position and quality

Baro Altitude

Velocities

Flight ID

ADS-B DO-260A

(voluntary)

24bit ID

Position and quality

Baro Altitude

Velocities

Flight ID

Emer code

SPI / GS

ADS-B DO-260B

(mandatory) Vehicle length+width

GPS Antenna offset

Velocity accuracy

System Design Assurance

UAT/1090ES capability

Aircraft category

Emerg code

NIC / NACp / NACv

GPS altitude

TCAS status

Common for ADS-B: Pos: GNSS based XPDR: Modes A+C Ident: 4 digit + flight ID Ident: 24bit unique ID

Automatic Dependent Surveillance - Broadcast

nextgen overview with focus on data link

Documents