1. 6th May 2002
Current Status of FAA Controller-Pilot Data Link Communication (CPDLC) -
Build 1, 1A, and Beyond
M J A Asbury
Presentation ATN3.3
The development of the operational requirements for data link applications started with the ICAO FANS-II Special Committee.
One of the declared objectives of the ICAO FANS II Special Committee was to -
'Harmonise Communications, Surveillance and Navigation globally using ATN-based data link technology'.
FANS recognised that the limitations of the present systems were intrinsic to the systems themselves and the problems could not be overcome on a global scale except by development and implementation of new concepts and new Communications, Navigation and Surveillance (CNS) systems to support future enhancements to Air Traffic Management (ATM). FANS proposed a new system concept, one which would evolve over a period of years, and which recognised that the pace of change cannot be the same everywhere on the globe.
ICAO recognised that implementation of the new systems concepts would require global co- ordination and planning on an unprecedented scale, and established the necessary machinery to help ensure a coherent, cost-beneficial, global implementation of the new system concept. Human factors and human/computer interfaces would also require careful consideration.
This highlighted the global need to -
'Review requirements and develop suitable systems/applications allowing air/ground and ground/ground operations with and/or without human intervention.'
This presentation reviews the air/ground element of these applications.
Presentation ATN 3.3
Air/ground Applications - FAA

2. Presentation Objectives
6th May 2002
The objective of this brief presentation is to describe the outline of the FAA Controller Pilot Data Link Programme, the changes brought about by the September 11th 2001 disaster, and the current status of the programme
The objective of this presentation is to outline and explain the Operational Requirements for the various air/ground applications of a data link based Air Traffic System (ATS) which allows the ATS to achieve its performance goals relating to safety, capacity and the expeditious movement of traffic.
Operational Requirements are the statements that amplify the high level Operational Concepts, and provide guidance for technical implementation and operational use.
The implementation of data link will not merely replicate the current systems, and opportunity has been taken in the development of the operational requirements to look forward to the use of developing technology for the implementation and integration of new practices and procedures
This presentation is aimed at any person who has anything to do with the management, policy, planning, development, implementation or use of an Air Traffic System which is expected to use data link as a significant means of communication.
The contents of this presentation are based to a very great extent on the ICAO Manual of Air Traffic System (ATS) Data Link Applications, developed by the then ICAO Automatic Dependent Surveillance Panel, now renamed Operational Data Link Panel - OPLINK These in their turn are based on the operational systems currently existing globally, with the overall emphasis on safety.
Air/ground Applications - FAA

3. FAA CPDLC Programme - An Overview (1)
FAA initially planned a three-stage approach to the introduction of ATN-based Controller Pilot Data link Communications into US domestic and oceanic airspace -
CPDLC Build 1 - Extremely limited message set - 4 routine, workload significant messages at one ARTCC;
CPDLC Build 1A - An additional 5 messages introducing tactical control, implemented at 23 ARTCCs; and
CPDLC Build 2 - A realistic implementation of an operational message set, with the option to add usage of additional messages from the CPDLC message set as demand increased

4. Pre September 2001- CPDLC Build 1 Plan
Prior to September 2001, the CPDLC Build 1 program read like this…….
On track for implementation of system into Miami ARTCC in June 2002, complying with ICAO SARPS Version 1
4 Services to be implemented
Transfer of Communications
Initial Contact
Altimeter setting
Pre-defined Message Text
American Airlines the launch airline

5. Pre September 2001- CPDLC Build 1A Plan
…...and the CPDLC Build 1A program read like this -
5 additional services to be implemented
Assigned Speed
Heading
Assigned Altitude
Route Clearance, and,
Pilot downlink
Implementation of system into the first of 23 En-route Centres (planned for June 2003) was in the midst of a re-scheduling/re-budgeting exercise which would have led to slippage to December 2003, with completion in 2005.

6. Pre September 2001- CPDLC Build 2 Plan
The CPDLC Build 2 program development plan had been defined, with initial implementation targeted at 2008, although there was no FAA baseline program established.

7. SEPTEMBER 2001
The events of September 2001 significantly altered data link implementation plans in the United States

8. SEPTEMBER-NOVEMBER 2001
All FAA programs underwent urgent stringent review.

9. Post September 2001- Revised CPDLC Build 1Plan ...
The revised CPDLC Build 1 program now reads like this…….
On track for introduction of system into Miami ARTCC in June 2002, but now complying with ICAO SARPS Version 2.
4 Services to be implemented
Transfer of Communications
Initial Contact
Altimeter setting
Pre-defined Message Text
American Airlines the launch airline

10. Revised CPDLC Build 1 Plan …Continued
Operational trials with American Airlines will continue
Controller training at Miami will take place
Evaluation of progress and decision in September 2002 as to whether or not to place the system into Initial Daily Use (IDU)

11. Post September 2001- Revised CPDLC Build 1Plan ...
The revised CPDLC Build 1A program is now much longer term…….
Introduction of system into in the first of the 23 En-route Centres not now until December 2005.
Late 2007/early 2008 before nation-wide rollout. (Biggest issue is training - up to 9 months at large facility like Atlanta.) ……..

12. Revised CPDLC Build 1 Plan …Continued
Same 5 additional services to be implemented
Assigned Speed
Heading
Assigned Altitude
Route Clearance, and,
Pilot downlink
ICAO SARPS Version 2 compliant
Compatible with but improvement on Eurocontrol Extended PETAL trials

13. Post September 2001- Revised CPDLC Build 2 Plan
The CPDLC Build 2 program development plan is currently sitting on the back burner, pending successful initial implementation of Build 1A plans.
No FAA funding is currently approved for this program.

14. CPDLC Build 1 Status ...
Build 1 continuing progress for operational evaluation in Miami ARTCC
Technical and operational evaluation will continue during the summer of 2002
Controller and pilot training taking place
American Airlines is preparing to add equipped aircraft to their fleet as launch airline
……..

15. CPDLC Build 1 Status …Continued
Decision point in September 2002 will indicate whether to proceed to Initial Daily Use (IDU) for Build 1
Expectation is that criteria will be met to continue operations of Build 1 beyond September 2002
System will remain in Miami until replaced by CPDLC Build 1A

16. CPDLC Build II Status
All FAA effort on the Build II program has stopped
FAA priority is to get Build 1A back on track before consideration of follow-on program
Build 2 could develop as add-ons to Build 1A

17. CPDLC - The Future
FAA (and its partners) committed to ATN-based CPDLC development and implementation.
Additional ‘High Benefit’ messages are being assesed as possible augmentation to Build 1A post completion of the 23-Centre implementation
Technical refreshment to bring the system up to SARPs Version 3 standard, including Security.

18. FAA Controller Pilot Data Link Program Status
6th May 2002
FAA Controller Pilot Data Link Program Status
THANK YOU FOR VIEWING
THIS PRESENTATION
Air/ground Applications - FAA