1 / 18

CPDLC at Maastricht

CPDLC at Maastricht. CPDLC at Maastricht JAA – 30 th November 2005 Paul CONROY. CPDLC at Maastricht History. PETAL trials 1995 - 2001 [Officially] Concluded that using CPDLC.. .. .. .. in the right circumstances Non-time critical .. in the right way Strategic

luann
Download Presentation

CPDLC at Maastricht

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CPDLC at Maastricht CPDLC at Maastricht JAA – 30th November 2005 Paul CONROY

  2. CPDLC at Maastricht History PETAL trials1995 - 2001 [Officially] Concluded that using CPDLC.. .. .. .. in the right circumstances • Non-time critical .. in the right way • Strategic • Non-tactical • Routine .. .. it had a place in continental, high-density airspace

  3. CPDLC at Maastricht History Current experience 2001 – to present day Maastricht experience with CPDLC since PETAL .. .. Fully supports this conclusion !!

  4. CPDLC at Maastricht Benefits Main benefits of CPDLC Reduction in voice channel occupancy • Allows / encourages some routine transmissions to be made by datalink Assistance in workload redistribution • Allows some CPDLC actions by the Planning controller Provision of second communications channel • With unambiguous text • Especially useful for 8.33 spacing

  5. CPDLC at Maastricht Technology Technology employed at MASUAC Maastricht has, for many years, used a multi-stack CPDLC architecture Allows CPDLC communication with several underlying technologies • ATN • FANS • [NEAN] Technology is not displayed to controllers [or pilots] • Don’t know the difference • Most don’t WANT to know • Shown if CPDLC or not CPDLC connected

  6. CPDLC at Maastricht Messages CPDLC Messages June 2003 • Uplinks Contact DCT TO SSR Mike check • Downlinks - Aircrew requests for DCT TO Added in December 2004 • Uplinks for .. Flight levels Turns Headings • Downlinks - Aircrew requests for Flight Levels All profile changing uplinks supported by crew Voice Readback

  7. CPDLC at Maastricht Statistics Overview of CPDLC Airborne Partners / Flights From June 2003 to Aug 2005 . .. . .. 22199 Successful CPDLC connections 18402 Operational CPDLC flights [At least one operational CPDLC message exchanged]

  8. CPDLC at Maastricht Statistics Overview of Message figures From June 2003 to Aug 2005 . .. . .. • Over 48,600 CPDLC operational messages • Less than 1000 downlink requests • Factor of airspace control / downlinks permitted Normally, per month • 1100 + CPDLC flights • 3300 + Operational uplinks More messages in first 6 months of 2005 than in entire 2004

  9. CPDLC at Maastricht Statistics Operational clearances / requests used since June 2003 25177 CONTACT 13801 ROUTE 3757 NSSR 3701 LEVEL 434 Route req. 429 Level req. Voice occupancy time saved [seconds] 300,000 = 80+ HOURs of voice communication time

  10. CPDLC at Maastricht Statistics Operational Response Times Currently . .. . .. • Average operational response 28 seconds • PETAL average operational response 40+ seconds Now hearing more positive controller comment on connection speed • Some responses very fast [10 seconds] • Especially viewed in context of 2 minute operational timeout

  11. CPDLC at Maastricht Developments December 2004 Introduction of CPDLC functionality on radar label • CONTACT • NSSR Radar label is the natural working place for controllers Uplink functionality still available, however, in the datalink window Very positive feedback from controllers

  12. CPDLC at Maastricht Developments February 2005 Automation of CPDLC NSSR [Next SSR Code] uplink • Defined parameters • CPDLC connected, FL250 +, well inside the airspace • Indicated on HMI Controller can always stop auto-uplink Transparent to the receiving aircrew, who respond as usual

  13. CPDLC at Maastricht Developments OR Auto-uplink of NSSR Completes the development path for this uplink .. • Executive only giving code change by voice • Executive having possibility to use voice or CPDLC • Executive having possibility to delegate CPDLC task to Planner • Controllers can also now allow ground system to automatically uplink

  14. CPDLC at Maastricht Developments April 2005 Introduction of Human Factors reporting mechanism • Voluntary controller reporting • On local INTRANET Seeking to capture issues like • HMI Issues • Selection errors etc. • Inappropriate uplinks, misunderstandings Doing it BEFORE ‘issues’ might become ‘problems’ Suggestion to make one available for pilots too

  15. CPDLC at Maastricht Developments More exposure Controllers becoming more and more used to CPDLC aircraft • Regularly seeing 4 or 5 together in a sector • Would like to see even more

  16. CPDLC at Maastricht Developments More activity Controllers using CPDLC more often with more aircraft • One flightwith 15 operational clearances / responses / requests

  17. CPDLC at Maastricht New partners Upcoming airborne partners    

  18. In short - It’s working ..

More Related