GADSS & TBO

IFALDA/EUFALDA

Atlanta, 8th May

Henk J. Hof

Head of ICAO and Concept Unit

Henk.hof@eurocontrol.int

2

Global Aeronautical Distress and Safety

System (GADSS)

The WHY

4/15

Instant and accurate information

Instant cooperation

Instant action

Global

Maritime example:

GMDSS: Global Maritime Distress and Safety System;

LRIT: Long Range Identification and Tracking

Different levels of Information sharing

Need for a consistent “overlay”

Alerting and SAR needs

The Need

2014 Mar.

2009 June

Know where aircraft fly

Know when aircraft are in distress

Enhance ability to rescue

Enhance ability to recover

MH370 AF447

Timely identification and location of aircraft in distress

Availability and sharing of valuable information

Effective and regularly trained procedures

Vulnerability

5/15

Global Aeronautical Distress and Safety

System Overview

Global Aeronautical Distress Safety System

AT

ADT

PFLR

Aircraft Tracking

Autonomous Distress Tracking

Post Flight Localisation & Recovery

GADSS

Information

Management

Airline

ATS

RCC

ALERT SAR

Accident

Investigation

6/15

High Level GADSS Objectives

Ensure timely detection of aircraft in distress

To timely initiate SAR actions

Ensure tracking of aircraft in distress and timely and accurate location of

end of flight

To accurately direct SAR actions

Enable efficient and effective SAR operations

Ensure timely retrieval of Flight Recorder Data

7/15

Aircraft Tracking

“A process, established by the operator that maintains and

updates at standardised intervals a ground based record of the

four dimensional position of individual aircraft in flight (Annex 6)”

MTOW > 45.500 kg Shall

MTOW > 27.000 kg Should

> 19 seats

8/15

Aircraft Tracking with Automated Surveillance

AOC ATSU

RESCUE COORDINATION CENTER

Normal

Distress Information Sharing

& Procedures

Repository

AO PoC

RCC PoC

ATSU PoC

9/15

Aircraft Tracking without Autom. Surveillance

AOC ATSU

RESCUE COORDINATION CENTER

Normal

Distress Information Sharing

& Procedures

Repository

AO PoC

RCC PoC

ATSU PoC

Tracking / 15 min.

Tracking / 1 min Oceanic

Area

4D

position

Record

10/1

5

Aircraft Tracking - practical

• Aircraft Operators to assess their route network

• Oceanic airspace

• Surveillance services

• Update rate

• When necessary: implement tracking solution

• 3rd party possible

• Implement processes

• Detection of missing reports

• Initiating contacts with ATSU’s

11/1

5

Missed position report process

12 12/15

Autonomous Distress Tracking

• The capability using transmission of information from which a

position of an aircraft in distress can be determined at least once

every minute which is resilient to failures of the aircraft’s electrical

power, navigation and communication systems

• Resilient to human factors

• Shall only be able to de-activate by the same mechanism that

activated it.

• Objective: locating an accident site to within a 6 NM radius.

13/15

Tracking Scenarios

14/15

Information sharing

• Right information

• Right time

• Right place

• If ATSU detects a distress condition they will notify the RCC;

• If the operator detects a distress condition they will notify the ATSU

who will in turn notify the RCC;

• If an ELT or ELT-DT is activated the RCC will be notified via the

COSPAS/SARSAT system;

• The RCC may receive notification directly from outside sources.

• Latitude

• Longitude

• Time stamp

• Aircraft identification (i.e. registration)

• 2Dt source (e.g. ELT, Iridium, INMARSAT)

15/15

16

DNA Principles

• Single login for DNA Services

• Duplication of data elements avoided.

• User data is exchanged at the sole discretion of the User, based the

rules of subscribed Services.

• SWIM enabled

DATA EXCHANGE PHILOSOPHY FOR DNA SERVICES

DNA

Data Exchange (Published once, consumed

by many)

OPERATOR

Contacts

ATC Contacts

AOC USOAP

AIRCRAFT TRACKING CONTACTS DATABASE

FOREIGN OPERATOR

APPLICATIONS TOOL

ATC Services

GADSS Ver 6 • Concept of Operations

Annex 6 Part I • Operator’s responsibility to track aircraft • Location of an Aircraft in Distress • Flight Recorder Data Recovery

Aircraft Tracking Implementation Guidelines (Cir 347) • “Normal” aircraft tracking

Manual on Location of Aircraft in Distress Flight Recorder Data Recovery (Doc 10054) • “Distress” aircraft tracking • Post flight localization and recovery

ICAO Documents

17

To be completed in Q1 2018

Global Aeronautical Distress and Safety

System GADSS

Know where aircraft fly

Know when aircraft are in distress

Enhance ability to rescue

Enhance ability to recover

18/15

Aviation is safe because it has the culture

to react and take lessons out of

rare events

19/15

Trajectory Based Operations (TBO)

The paradigm change

21

Air Transportation – Coordination Today

Manage interactions through coordination between participants

ATFM Automation

FOC Automation

FD Automation

ATC Automation

Flight Data Exchange across support automation

Limited In-Flight Coordination

Automation not Informed

High Uncertainty

Disparate Plans in

Automation

Imprecise Execution

Imprecise execution

Plan not followed

Multiples Participants Control a Flight All Affect the Trajectory

Transform to Trajectory-Based: Decision-Making, Control and Coordination

ATFM

23

Trajectory Based Operations >>bringing it together

Years Months Minutes Days Hours Depart In Flight

Long-term Planning

Mid-term Planning

Tactical Planning Execution

AUO

DCB

AOM

TS

CM

Capacity Management

Flow Management

Scheduling Flight Planning

Separation Provision

Traffic Synchronisation

Re-optimisation

ATFM ATC AM AU

AM Airspace Management ATFM Air Traffic Flow Management AU Airspace User ATC Air Traffic Control AO Aerodrome Operator

AO Departure AO

Arrival AO

Co

llab

ora

tio

n

A0

Trajectory Based Operation: Evolution

24

Airspace User

FPL

Pre-departure

Negotiation

Post-departure

Negotiation

FOC

FD

Trajectory Accuracy

Adapted Values

Shared Paramet

ers

FOC

EFB Aircraft-Derived

Aircraft 4DT (EPP)

ADS-C

Clearances

Voice

Initial CPDLC

Precise Clearances

ATM Components

TBO Components

Ground Synchroniza

tion

Full TBO Integration

FF-I

CE/

Pla

nn

ing

Significant interactions

between columns

FF-ICE/Planning (Flight and Flow Information for a Collaborative

Environment)

25

Replaces current Flight Plan

• More flexibility • Scalable • SWIM • Foundation for TBO

New Services

• Planning Service

• Supporting collaboration

• Trial Service

Performance Based Deployment

• No Big Bang transition • Europe/US: +/- 2020 • Sunset date FPL TBD

New Services

26

FF-ICE Services

Planning Service

(Optional)

Trial Service

(Optional)

Filing Service

(Mandatory)

Related Messages:

Preliminary Flight Plan Message

Flight Plan Update Message

Flight Plan Cancellation Message

Submission Response Message

Planning Status Message

Related Messages:

Trial Request Message

Submission Response Message

Trial Status Message

Related Messages:

Filed Flight Plan Message

Flight Plan Update Message

Flight Plan Cancellation Message

Flight Departure Message

Flight Arrival Message

Submission Response Message

Filing Status Message

Flight Information Service

(Mandatory)

Related Messages:

Request Flight Plan Information

Message

Flight Plan Information Response

Message

Publication Service

(Optional)

FF-ICE/Planning progress

• ICAO Provisions • Ready • High Level

• Implementation guidance • In progress

• Development FIXM (Flight Information eXchange Model)

• In progress • Version 4 available and being tested

• Implementations • US/Europe in progress • Involvement of CFSP

27

FF-ICE/Execution Scope

• Extend pre-departure negotiation to post-departure

• Ground synchronization • Extend present-day Notification & Coordination

processes

• Improve prediction accuracy by sharing consistent trajectory information

28

Trajectory Based Operation: Evolution

29

Airspace User

FPL

Pre-departure

Negotiation

Post-departure

Negotiation

FOC

FD

Trajectory Accuracy

Adapted Values

Shared Paramet

ers

FOC

EFB Aircraft-Derived

Aircraft 4DT (EPP)

ADS-C

Clearances

Voice

Initial CPDLC

Precise Clearances

ATM Components

TBO Components

Ground Synchroniza

tion

Full TBO Integration

FF-I

CE/

Exe

cuti

on

Significant interactions

between columns

Post-Departure Negotiation

30

FOC ASP

ASP-AU Negotiation may involve FOC/FD in various ways, transparent to ASP

Negotiation may be with downstream ASP

Smooth, well-defined transition between FF-ICE/1 and FF-ICE/2 processes

I want to negotiate

I want to negotiate

Negotiation may be initiated by AU or ASP

Inter-ASP coordination of constraints affecting trajectory

Negotiate beyond some tactical horizon

Outcome: An Agreed trajectory that can be delivered through a clearance

Negotiation with ASP ATFM functions ATC within tactical horizon delivers clearances

Continuous Notification

31

Today: ABI (Advanced Boundary Information) No interaction at this time (beyond LAM/LRM)

Flight Data Publication

Note: Continuous Notification provides more content than exists in ABI. Content might also include cancellation of notification.

MAC – to cancel notification

32

ASP FOC

ASP Review and Negotiates

ICAO ATMRPP, Montreal, October

10-20, 2017

33

Flight is still in Italy; Hotspot in Zurich UIR

Hostspot saturation leading to local trajectory revision

TBO and FF-ICE

• Trajectory Based Operation: Paradigm change for ATM • Collaboration • Performance • All airspace users

• Gradual implementation through FF-ICE • FF-ICE/planning: pre-departure >> replaces current FPL • FF-ICE/execution: post-departure >> supports in flight

negotiation/ground synchronisation • Full TBO : integration of the aircraft

• ICAO • FF-ICE planning provisions ready by 2020 • TBO Concept presented to Air Navigation Conference 2018 • TBO fully integration in Global Air Navigation Plan 2019

34

TBO >>transformation of ATM

35