Data Communications Program

Data Communications Program Program Definition & Services Discussion

FAA Data Communications Program • Flight Plan to NextGen • Partnership • Data Communications Program Overview • Technology Alternatives • Outreach Efforts • Data Communications Services • Data Comm Program Needs • Conclusion

2025 2022 2017 2012 Avionics Development Automation Evolution Standards Development Today Requirements Basis ATMAC Letter to AOA-1 - Start a Data Comm Program JPDO NextGen Concept of Operations P-ATM Performance Based ATM concepts – Mitre Lab COCR Future Comm Study – Data Comm Services Menu PARC Datalink Roadmap and Rulemaking OEP Operational Evolution Plan NextGen Flight Plan to NextGen Enhanced Capability Full Capability Rule Effective Initial Ops Capability Data Comm Benefits

User Inputs Need industry participation to collaboratively move forward • Validation of the operational concept and segmentation of operational capabilities • Standards updates & development • Collaboration on avionics requirements • Rulemaking • Performance-Based Ops / RCP • Coordinate avionics investments

Program Overview • Only for support of ATS Safety Communications • Advisory services currently remanded to alternative links or commercial sources e.g., FISDL • In Investment Analysis (IA) phase of AMS. • Requesting FY08 funding to complete IA activities with initial Contract Award(s) in FY09 • New CIP project • Application for Domestic CONUS Operations only • Effectively replaces CPDLC & NEXCOM-1B budget lines • Will learn from Oceanic, but not develop / implement technology in ATOP • Covers all elements between the Air & Ground for selected functions • Data Comm funds the modification &/or development & deployment of data comm capabilities to ERAM / STARS & C-ARTS / TDLS / TFM automation platforms; all HMI & Training plus the G-G & A-G comm networks • Capabilities introduced in ~3 continuously progressive segments

Requests For Information • Multiple Requests for Information (RFI) are planned to solicit industry information and opinions on program acquisition • GEIA Meeting held early April 2007 • Initial request focused on providing air/ground communications services • Released in March 2007 • RFI’s for End-to-End service delivery and/or automation development also planned for release later in summer 2007

Technology Alternatives • Per guidance to AOA-1 from ATMAC, sub-net will be VDL-2 • Alternatives review is for acquisition of service only • Likely to require additional 25kHz spectrum to support expected equipage/data rates • Hope to avoid 8.33 kHz • Some prioritization/ground station handoff SW added on ground in later segments to balance communications load • Mature NextGen may require new sub-net which will be that developed under Future Communications Study results

Technology Alternatives (con’t) • Application level protocols to be supported include: • ATN for CPDLC (incl. DCL & D-TAXI), ADS-C & D-ATIS functions • FANS for CPDLC (incl. D-TAXI) & ADS-C functions • DLUF said no to DCL via FANS • 623 for DCL, D-TAXI & D-ATIS functions • 620/POA for PDC & D-ATIS • Existing PDC users NOT eligible for revisions/full route clearances, or multiple PDCs per day • POA sunset timeframe??? • Multi-Stack approach will require knowledge of aircraft application protocol(s) at some point in advance, methodology is???

Overview - Schedule & Milestones 2006 2007 2008 Task Name O N D J F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S • IARD …………………………………………………………….. • Develop Evaluation Criteria ……………………………………. • Alternatives Analysis …………..……………………………….. • Determine A/G Subnet Strategy ………….…………………… • Operational Services Analysis ………..……………………….. • Develop Each Alternative Life Cycle Plan …..……................ • Preliminary Program Requirements....……….……………….. • Benefits Analysis Activities …………...……………………….. • Business Case Analysis Report ………….………………....... • Exhibit 300 Material ………..…………………………………… • Coordination & Review …….………………..…………………. • Initial Investment Decision (6/08) .………….………………….

2025 NextGen Vision Data Communications Program Roadmap a Today 2010 2015 2020 2025 Human – Human Voice Sector-Based Operations Voice / Data Performance-Based Operations Automation – Automation Data / Voice Area-based Strategic Ops Mandatory Equipage Segment 3 Widespread 4-D Agreements Widespread M&S / C&P / ITP Red = Terminal Function Black = En Route Function Purple = Cross Domain Function Segment 2 Initial 4-D Agreements Conformance Management TRACON Data Comm incl. Routine Clearances, Comm Mgmt, 4-D TAP/CDA & CTA Segment 1 Initial 4-D TAP/CDA to OEP’s Airport field status & Taxi-In NAS Status/Delays/Constraints • En Route Clearances, Comm Mgmt, TFM Reroutes & CTA Original + Revised Departure Clearances, D-ATIS & Taxi-Out Standards Activities

Functionality Awaiting Confirmation • Data Comm Aeronautical Information Services under investigation • Safety or Advisory service requirement? • Infringement on Commercial Sector e.g., FISDL, Jeppesen? • En Route Operational Information Service, Terminal Operational Information Service, RVR, SIGMET, AIRMET, etc. per FAAO 7110.10(x) • WX products could be done as updates to pre-departure product download(s) that are converted on-board to display graphics/text to reduce bandwidth needs • Awaiting guidance from JPDO WX IPT / ATO-P

Functionality Awaiting Confirmation (con’t) Virtual Tower Aircraft Derived Data needs?? Available sensors & link over the bus??? Can we feed ADS-B and/or ADS-C??? What kind of update rate can be supported???

Functionality Awaiting Confirmation (con’t) Virtual Tower Aircraft Derived Data needs Available sensors & link over the bus??? Can we feed ADS-B &/or ADS-C??? What kind of update rate can be supported???

AEEC SAI Reactions • Does SAI see any issues??? • Does service set cover needs??? • Does segmentation seem reasonable??? • To support TFM, what mechanisms besides ATS implementation of duplicate functions would be available for getting items like e.g.,: • OOOI data direct from aircraft • Gate/Stand • Aircraft weight • Distance required for Take-off/Landing. Can Weight & Balance calculations provide this??? • Work w/SAI or another venue to provide mechanisms for items such as these??? • Need to start wrapping up service requirements baseline for IA

Data Comm Program Needs • Industry agreement with program definition through ATMAC Reps • Program definition in line with ATMAC & PARC recommendations • TAP is one of the 1st capabilities planned to be exploited beginning in the En Route domain • Determine differences between TAP & CDA • Develop Ops based on best of both • Need to consider future TAP Ops in the context of a busy NAS environment • Both En Route & TRACON domains

Data Comm Program Needs (con’t) • Extending TAP principals to 4-D Trajectory Based Ops requires collaborative effort for positive business case both Air & Ground • Definition & integration path for: • ERAM & STARS automation w/Trajectory Model • Procedures development across domains • Assistance in standards definition • Safety, Performance & Interoperability Standards definition for program services is necessary by late FY-09 for rulemaking effort • Includes A/G & G/G Trajectory Exchange Messaging • Both ATN & FANS CPDLC contexts • Includes Conformance Management definition using ADS-C • Is FANS acceptable???

Data Comm Program Needs (con’t) • Correct path to the integrated avionics suite? • Result of Safety Case??? • Includes positive business case • Includes standards work • Extent of FANS Accommodation??? • New ADS-C under discussion • Needed in aircraft for 2015 timeframe

Data Comm Program Conclusion • FAA & the ATO recognize: • “Bad Blood” produced from withdrawal of Miami CPDLC Program • FAA committed to NextGen Vision • Data Comm recognized as critical component • Requires a portfolio program • No individual piece of the system can do it alone • Data Comm only brings the pipe & applications • Need Automation, Cultural Changes & Procedures • Takes a systems approach • Includes Air & Ground development

Questions???

Back-Up For COCR to DCP Service Set Definitions

ATS Services Voice or Data ACM, ACL, ARMAND, DCL, D-ATIS, D-FLUP, D-OTIS, D-ORIS, D-RVR, DSC, D-SIGMET, D-TAXI, PPD, SAP Data Only AIRSEP, AMC, A-EXEC, COTRAC, DLL, DYNAV, D-ALERT, D-SIG, FLIPCY, FLIPINT, PAIRAPP, URCO, WAKE Surveillance ADS-B, ADS-C, & TIS-B which support: ATC Surveillance, Airborne Situational Awareness, Enhanced Visual Acquisition, M&S, ITP, C&P AOC Services AOCL, OOOI, Free Text, WX Request, NOTAM’s, Position Report, Flight Status, Fuel Status, Gate & Connecting Flight Info, Engine Performance Report, Maintenance Troubleshooting, Flight Plan Request/Response, Load Sheet Request, Flight Log Transfer, Real Time Maintenance, Graphical WX, Real Time WX Report, On-Line Technical Troubleshooting, Technical Logbook Update, Electronic Library Update, Software Loading, Cabin Logbook Transfer COCR Services vs. Data Comm Program (in bold, definitions in back-up)

COCR Service Definitions • Data Link Logon (DLL) - The Flight Crew activates the data-link system and enters the flight identification into the page. The additional data required, i.e. data link applications supported, to logon with ATS is stored inside the avionics and the remainder of the DLL takes place automatically without Flight Crew involvement. Logon and contact with the system encompasses the data link exchanges between an aircraft and an ATSU required to enable the other data link services. • ATC Communications Management (ACM) - When a flight is about to be transferred from one sector/ATSU to another, the Flight Crew is instructed to change to the voice channel of the next sector/ATSU. The ACM Service provides the air/ground exchanges between an Aircraft and its transferring ATSU as well as with its receiving ATSU to establish communications control of the flight. In addition, when data link communications are involved, the ACM service manages the data link connection transfer.

COCR Service Definitions • ATC Clearance (ACL) - An aircraft under the control of an ATSU transmits reports, makes requests and receives clearances, instructions and notifications through ACL. The ACL service specifies dialogue exchanges via air/ground communications between Flight Crews and Controllers working the specific position/sector associated with the aircraft’s physical location. Some ACL exchanges, e.g. Altimeter Settings and SSR transponder code assignments, can be done without human intervention. ACL can be done via voice, data link, or a combination of voice and data-link communications in all flight phases (except only in the buffer zone for the AOA domain). This service is the basic building block for trajectory conformance management. In Phase 2 this service is largely superseded by COTRAC for equipped aircraft. • Downstream Clearance (DSC) - In specific instances, Flight Crews need to obtain clearances or information from ATSU’s that will be responsible for control of the aircraft in the future. The DSC Service provides assistance for requesting and obtaining clearances from a D-ATSU. Only the Flight Crew can initiate the DSC Service with a D-ATSU. The D-ATSU Controller replies with a clearance that must be acknowledged by the Flight Crew. Any clearances received must only apply to the route within the D-ATSU airspace. Exceptions to this rule must be co-ordinated with the C-ATSU prior to activation. In Phase 2 this service is largely superseded by COTRAC for equipped aircraft.Note: For the DC in Support of NextGen program we functionally cover this service by G-G transfer of the info to the aircrafts current managing position.

COCR Service Definitions • Common Trajectory Coordination (COTRAC) - The purpose of COTRAC is to establish and agree on 4-D trajectory contracts in real time using graphical interfaces and automation systems, in particular the FMS. COTRAC allows new trajectory contracts involving multiple constraints (latitude/longitude, altitude, airspeed, etc.). The initial implementations of COTRAC will most likely be utilising 2-D trajectories of e.g. departure point, top of climb, top of descent and arrival fix crossing constraints. As air and ground system capabilities expand, COTRAC is expected to become a fully integrated 4-D trajectory exchange tool. The following are the messages used to develop the 4-D trajectory contract: • Trajectory-based flight plan: A flight plan enhanced from the current form to include a series of 4-D points, including key points (i.e., top-of-descent, etc.), estimated times of arrival (ETA’s), required times of arrival (RTA’s) (as needed), required time of departure (RTD) (if needed), and additional information such as CNS performance characteristics (e.g. RNP-4, RCP-120), tolerance of time variability from the proposed departure, and priority ranking relative to other flights proposed by that user. The times at the points along the trajectory, as desired and predicted by the user, are referred to as ETA’s. The trajectory-based flight plan is the filed flight plan that will later be negotiated prior to flight and is a ground-ground communication. • Trajectory Constraints: Uplink from the ground that specifies the constraints e.g., RTA’s, 4-D waypoints, etc., which must be complied with when initiating the COTRAC service. This message is responded to with a Trajectory Request. • Trajectory Request: Request from the aircraft in response to a trajectory constraint message, or it can be a Flight Crew request for a change of the existing trajectory. It will include a series of 4-D points, including RTA’s. This message is responded to with a Trajectory Clearance. • Trajectory Clearance: Based on the constraint and request exchanges, a trajectory clearance is uplinked which establishes a contract between the air and the ground on the trajectory to be flown. The clearance is closed with an operational response. • Trajectory Non-Conformance: Report from the aircraft that one or more of the constraints, previously agreed for the remaining or an interim portion of the flight, can no longer be complied with. Depending on the dynamics of the situation, the response to this message is a Trajectory Constraint, or a Trajectory Clearance. This message happens as a result of an event report which is generated by the FLIPINT service.Note: COCR V2.0 to update Non-Compliance to Non-Conformance due to the security contexts.

COCR Service Definitions • Departure Clearance Service (DCL) - A flight due to depart from an airfield must first obtain departure information and clearance from the C-ATSU. The DCL Service enables the Flight Crew to request and receive their departure clearance and related route of flight information by data link. It consists of a request from the flight crew and a response from the controller or ATSU automation. • Arrival Manager (AMAN) Information Delivery Service (ARMAND) - The ARMAND service automatically transmits relevant advisories directly from the ground automation to Flight Crews that are within the optimum-planning horizon of the AMAN, but may be beyond the limits of the ATSU that contains the flight’s destination airport. The ARMAND service transmits target, expected or revised approach-time advisories relevant to the destination airport. This exchange may subsequently be followed by an ACL transaction to cross a significant point at a specified time. These exchanges are consistent with the principle of not modifying the aircraft’s route in another sector’s airspace. When COTRAC becomes available, ARMAND will be superseded for those that are equipped. Note: COCR V2.0 may update this service to be Arrival or Departure.

COCR Service Definitions • ATC Microphone Check (AMC) - When the voice channel is blocked, such as when an aircraft has a stuck microphone, the AMC Service provides a means of contacting other aircraft, as well as the one with the stuck microphone, via data link. This allows a message to be dispatched to one, some, or all aircraft being controlled by that sector/position. The AMC Service is a one-way uplink, which requires no response and is initiated by the Controller. It may be sent via broadcast, point to point, or point to multi-point methods. • Data Link Taxi (D-TAXI) - An aircraft preparing to depart from an airport, or an aircraft that has just landed or is on final approach, must obtain a series of clearances from the C-ATSU in order to proceed from its gate/stand to the runway or from the runway to its gate/stand. The objective of the D-TAXI Service is to provide automated assistance to Controllers and Flight Crews to perform these communication exchanges for ground-movement operations. Ground automation produces the route for the controller who approves and sends the clearance. D-TAXI messages require a response from the Flight Crew. • Data Link Flight Update (D-FLUP) - The D-FLUP Service provides all the ATM-related operational data and information aimed at the optimisation of flight preparation supporting punctual departure at the departure airport. Examples of these data include flight specific information related to the departure sequence, CDM agreements, slot-time allocations, as well as expected target approach times. Special operations such as de-icing will be supported using this service. This service is event driven. Note: COCR V2.0 will update this service to be phase of flight independent. Potential to add D-ORIS & D-OTIS to cover need.

COCR Service Definitions • Pilot Preferences Downlink (PPD) - Flight Crew may have preferences or limitations on the way a flight is to be conducted for various operational reasons. In order to execute pertinent control strategies, Controllers need to be aware of these preferences. The PPD Service allows the Flight Crew, in all phases of a flight to provide the Controller with a set of preferences not available in the filed flight plan (e.g., maximum flight level) as well as requests for modification of some flight plan elements (e.g., requested flight level). It automates the provision to Controllers of selected Flight Crew preferences even before the aircraft reaches their sector. PPD consists of a one-way exchange which is generated from the flight crew to the ATSU any time they enter the information. PPD information can also be sent upon ground request. The controlling ATSU passes the PPD information along to the next ATSU as part of the ground-ground co-ordination if the information is still pertinent. The Controller accesses the ground database to assess these parameters in the normal course of planning traffic flows. • System Access Parameters (SAP) - The scope of the SAP Service is to make specific, tactical flight information, i.e., current indicated heading, air speed, vertical rate, and wind vector, available to the Controller or ground automation by extracting the relevant data from the airborne system. The use of the SAP parameters by the ground system should be considered as a means to provide enhancements to the existing ATC surveillance functions. The SAP service is established by the ATSU automation and conducted on a periodic or event driven basis and is available in all phases of flight. The Controller uses the data to reduce congestion on the voice channel by using the SAP information instead of asking for it from the Flight Crew.

COCR Service Definitions • Flight Path Intent (FLIPINT) - The FLIPINT Service consists of the downlink of the trajectory predicted by the FMS (e.g. ADS-Contract) with some additional information, e.g. meteorological data, in order to support the FDPS trajectory prediction. ADS-Contract (ADS-C) has been traditionally used in non-radar airspace to supplement command and control functions of ATS, however in the context of the future concepts extrapolated in this document, ADS-C will become a traditional source of surveillance in any domain where the cost benefit has warranted its use over, or in conjunction with, other forms of surveillance. FLIPINT can supersede the necessity to implement the FLIPCY service by utilising the downlinked information to check the consistency of the information with that which is stored in the ATSU automation. Unlike ADS-B, ADS-C downlinks addressed position reports to ATSU’s on a contract basis. FLIPINT is established by the ATSU automation and the data is downlinked on demand, periodically or on occurrence of an event and will include the position in latitude and longitude, altitude, ground speed, and up to 128 subsequent waypoints with time, altitude, and speed projections as appropriate. The Controller also has the capability to modify or initiate the FLIPINT service manually.

COCR Service Definitions • Digital Automatic Terminal Information Service (D-ATIS) - D-ATIS provides terminal information relevant to a specified airport(s) in any phase of flight (except in the AOA domain outside of the buffer zone). Weather, active runway(s), approach information, NOTAM information is provided by data link rather than by voice. This service operates on demand, by event, or periodically. The D-ATIS information may be included in the D-OTIS service. • Data Link Surface Information & Guidance (D-SIG) - The D-SIG Service provides automated assistance to Flight Crews by delivering a current, static graphical airport map. D-SIG presents an updated and integrated representation of all the airport elements (e.g., taxiway closures, runway re-surfacing) necessary for ground movements to the Flight Crew. D-SIG is a one-way exchange initiated by the ground automation upon completion of the DCL process for departures or recognition of transition to initial approach for arrivals. In Phase 1, it is not anticipated that aircraft avionics will have advanced to the stage of implementing a moving map where the D-TAXI instruction would be overlaid on the D-SIG. Therefore, the D-SIG information in Phase 1 is used for situational awareness only. In Phase 2, it is assumed that the integration of the displays has occurred and therefore the D-SIG information would be used for surface navigation in all flight conditions.

COCR Service Definitions • Paired Approach (PAIRAPP) – The PAIRAPP service permits closely spaced simultaneous parallel approaches to runways with as little as 750 feet spacing between runway centrelines. PAIRAPP extends current visual-based operations into IMC to achieve reduced final-approach phase separation without requiring aircrews to visually acquire either the runway or their partner aircraft. Typically, COTRAC would bring aircraft to the point in their approaches where minimal standard separation is reached. Upon initiation of PAIRAPP the COTRAC service would be terminated. PAIRAPP would then allow the participating aircraft to close to, and maintain spacing necessary to conduct the simultaneous, parallel (e.g. wingtip-to-wingtip) approach.Note: COCR V2.0 will update this definition. • In-Trail Procedure (ITP) - The ITP service uses the same broadcasts as ATC surveillance to allow one aircraft in a pair to perform a climb, descent, or station keep relative to the other. The service requires a CDTI and the capability to utilise ACL instructions. • Crossing Passing (C & P) - The C&P service uses the same broadcasts as ATC surveillance to allow one aircraft in a pair to perform a crossing or passing manoeuvre relative to the other. The service requires a CDTI and the capability to utilise ACL instructions. • Merging & Spacing (M & S) - The M&S service uses the same broadcasts as ATC surveillance to allow one aircraft in a pair to merge and space itself behind another aircraft. The service requires a CDTI and the capability to utilise ACL instructions.Note: COCR V2.0 will update this definition for M&S vs. S&M

Data Communications Program