Future Datalink Applications

1
Future Data-link Applications

• WG44/SC206 30th January 2006
• Dragos Tonea
• Directorate of Strategies-ATC Domain
• dragos.tonea_at_eurocontrol.int

European Organisation for the Safety of Air
Navigation
2
Introduction

• Background
• Present day situation
• Future developments
• Conclusion

3
Strategic Context
ATC Domain
LINK 2000 Mode S EHS
CASCADE
Airborne Separation Trajectory
negotiation Autonomous Separation
Departure Clearance Digital-ATIS Oceanic
Clearance Classical Radar

• Strategic Context
• Objectives
• Scope
• Approach

ACARS
PS RADAR
Mode S
2000gt
2005 gt
2010 gt
4
ATC Domain

• Part of Directorate of Strategies
• Responsible for
• Future Operational Concepts
• Advanced ADS-B (ASAS Separation Self Separation)
  and
• Advanced Data-link Applications (focus on 4D
  Trajectory Applications)
• Role
• Initial development of applications
• Feasibility assessment
• Initial validation exercises
• Support cross-domain activities (e.g.
  Communication Domain AP17- COCR)
• SESAR alignment / input

5
Data-link Background

• Data-link essential in future concepts
• PETAL, PETAL2, Air ground Co-operative Programme
• 2 Eurocontrol implementations Programs
• Link2000
• CASCADE
• More advanced data-link applications
• ATC Domain (Advanced ADS-B Data-link WP)

6
Future Data-link Scope

• Beyond implementation Programs
• Focus
• Medium-term future
• Long-term future
• Support enhancement of ATS (as defined by ICAO)
• Air Traffic Control
• Alerting Services
• Flight Information Service
• Support future operational concept

7
Future Data-link Approach

• Identify operational need
• Develop initial OR and OSED
• EUROCONTROLS stakeholder consultation
• Pilot, ATCO, data-link experts, etc.
• Validation
• Simulations (FTS, RTS)
• Operational trials
• Initial steps before an implementation Program is
  created
• Priorities set according to Eurocontrol
  stakeholders requirements (ODT- ATS Business
  Division Steering Group)

8
Medium-term

• Pragmatic approach
• Re-use infrastructure already available when
  possible
• Base development on operational need
• Use development cycle that have proven successful
  
• ATS
• Initial 4D applications e.g. DYNAV
• Alerting Services D-ALERT
• FIS D-RVR, D-ORIS
• Enhance ATCO support tools (e.g. AMAN),
• SWIM support

9
FIS applications medium-term

• D-RVR
• Initial OR agreed at expert level (ODIAC)- AGC
  ORD 1.0
• Validation exercises envisaged
• Feedback results in initial OSED development
• D-ORIS (text)
• High level description
• Development of initial OSED foreseen for 2006
• Use information already available (e.g., en-route
  NOTAM, SIGMET, PIREPs)
• Base development on D-OTIS experience

10
Long-term

• More advanced data-link applications
• Move towards
• Advanced 4D Trajectory COTRAC
• Support to Advanced ADS-B applications
  (separation self separation)
• Support to CDM applications
• Advanced FIS applications
• Graphic integration seen as essential!
• Build on available data-link applications
• Develop new ones (when required)
• Use available information (not dealing with
  format)
• Derive initial safety and performance
  requirements
• UAVs, SWIM support

11
Thank you!

• Operational Concept development- input to SESAR
• Initial steps in data-link applications lifecycle
  
• Scope of activities flexible to reality on the
  ground but
• Activities and priorities will be aligned with
  SESAR