Data Communications Implementation Team (DCIT) DCIT Meeting 03/10/2011 Federal Aviation Administration March DCIT Agenda and Objectives • • • • • • - Trials Implementation Plan: Workflow/Milestone planning Facility/Airline outreach/agreements, etc. Facility/Airline Selection Considerations: Selection methodology Airline feedback and recommendation input PDC to DCL Transition: How we think Trial(s) are going to be conducted Normal DCL scenario (use case) walk through DCIT invitation criteria going forward: Direct participant involvement for targeted planning focus DCIT Charter: Next Steps: Upcoming program activities Federal Aviation Administration 2 Action Items Origin Action Item Status Gaylon Koenning 03/10/11: Submitted revised Continental Trials Questionnaire with the B737 equipage information. 03/10/11: Received information and DLUF slides from Moin Abulhosn and Tom Kraft. 03/10/11: No Updates Continental 2 FedEx Requested information or link for the North Atlantic mandate that all aircraft should be equipped with FANS by 2014 DCIT Team or FAA Moin Abulhosn 3 DCIT Team Rick Shay 4 Participants 5 FedEx Provide updated list of aircraft equipage ready to participate the trials beyond the August start date considering phases of the trials. Develop a Trials Value Evaluating process that will provide guidance in how the team will rate value to participants i.e. sites. Provide number of B777 that may be qualified to participate in the trials. 6 Participants 7 Participants Provide list for B737s that may be equipped beyond August time frame. Identify at least three airports as potential sites for trials considering the value proposition. Draw multiple scenarios (including SID, revised full route, and revised free text) for every condition that will explain revised messaging options. Due Date Actionee Item # 1 DCIT Team and Participants 03/10/11: To be discussed during the meeting. John McCormick 03/10/11: Received information from John McCormick. 03/10/11: To be discussed during the meeting. DCIT Team Ron Boyd 03/10/11: To be discussed during the meeting. Federal Aviation Administration 3 Data Communications Implementation Team (DCIT) Proposed Site Selection Process To: DCIT Date: 03.10.2011 Presenter: Craig Morris, Thane Inc. Jerry Smith, Thane Inc. Federal Aviation Administration Trials Planning • • • • • • • • • • • • • • Design of Trial(s) Architecture/Requirements SRMD/Safety Ground to Ground Connectivity Facilities Selections Airline Agreement(s) DTAP Contract Service Provider Agreement Test NCP Testing Training Procedures Site Implementation Data Collection and Analysis Federal Aviation Administration 5 Federal Aviation Administration 6 Site Selection Overview • • • • • • • Gather User Preferences, Possibilities Develop Site Selection Considerations Coordinate with FAA HQ, Regions and Facilities Compile Site Evaluation Table Establish Priorities for 1st, 2nd site Synchronize with Users Select Site(s) Open for Discussion Federal Aviation Administration 7 User Preferences • Down select from list of all user-identified airports • First cut criteria: 1. DCL Eligible 2. Minimum possible number of operations • Initial List of Candidate Airports: • • • • • • • ATL DFW DTW EWR IAD IAH JFK • • • • • • • LAX MEM MIA MSP ORD SDF SFO Federal Aviation Administration 8 Trials Site Selection Considerations • • • • • • • • • • • • Equipment availability (# and mix of properly equipped aircraft) # of potential Initial DCL Ops (per day) # of potential Revised DCL Ops (per day) User’s location preference Airline flexibility to accommodate DCL changes Tower configuration (e.g. physical space for equipment) Facility planned activities and internal relations Potential operational value from DCL (e.g. delay avoidance) Potential Ops impact(s) during initial deployment Cost Considerations Airport suitability to support BEBS Airport willingness to conduct BEBS Federal Aviation Administration 9 Site Evaluation Matrix ATL DFW DTW EWR IAD IAH JFK LAX MEM MIA MSP ORD SDF SFO Federal Aviation Administration 10 Site Priorities ATL DFW DTW EWR IAD IAH JFK LAX MEM MIA MSP ORD SDF SFO Scenario 1: Minimize Risk at Site 1 Federal Aviation Administration 11 Site Priorities ATL DFW DTW EWR IAD IAH JFK LAX MEM MIA MSP ORD SDF SFO Scenario 2: Maximize DCLs at Site 1 Federal Aviation Administration 12 Site Priorities ATL DFW DTW EWR IAD IAH JFK LAX MEM MIA MSP ORD SDF SFO Scenario 3: Maximize Benefits at Site 1 Federal Aviation Administration 13 Site Selection Completion • Complete Site Evaluation Table • • • HQ, Region and Site One-on-One discussions Airline One-on-One discussions Internal assessment • Finalize Site Priorities • Propose Site Selection and Progression • • Finalize Trials Sites • • • Socialize with stakeholders Ink Facility MOUs Ink Airline Agreements Begin Trials! Federal Aviation Administration 14 Data Communications Implementation Team (DCIT) PDC to DCL Transition To: DCIT Date: 03.10.2011 Presenter: Andy Fry, Thane Inc. Ron Boyd, Thane Inc. Federal Aviation Administration Transition from PDC to DCL Curremt Operational Development Activities 1.Candidate airline to identify routes to be flown receiving DCL’s. 2.Analyze routes for DCL challenges and cockpit FMS issues. 3.Domestic routes (between the pluses routing etc.) 4.International routes (North Atlantic Tracks etc.) 5.Identify HOST/ERAM data for building FANS compliant message and cockpit HMI display issues. 6.Based on analysis of routes and HOST/ERAM data, communicate to the candidate airline what AOC flight plan filing requirements will be required for DCL aircraft. 7.Communicate to AOC requirement of gate information upon receipt of courtesy copy of initial DCL. 8.Candidate airline to communicate proposed departure times for DCL’s. 9.Obtain the number of crews that need training and requirements to accomplish. Current Facility Activities 1.Coordinate with Air Traffic Service Center and gain approval for the facilities identified by airlines as candidates for DCL service. 2.Present and seek approval from identified Air Traffic facilities the proposed DCL Trials based on: ( not inclusive) a. Management/ Labor relations NATCA, PASS b. Space availability in the operating quarters. c. Determination if separate position needed. d. Location of equipment in operating quarters. e. Space availability in the equipment room f. Identify any safety issues g. Determine if any security issues. h. Identify training issues and location. i. Possible procedural changes. Federal Aviation Administration 16 Post Airline/Facility Selection Activity 1.Baseline identified air traffic facility. 2.Conduct SRMD activities. 3.Coordinate between air traffic facility and the selected airline: a. Proposed departure times of candidate flights. b. Identify means of communicating daily departure times between selected air traffic facility and selected airline. c. Identify key contacts at the selected air traffic facility and selected airline. d. Coordinate with Service area and Headquarters training and procedural changes for trials conduct at the identified air traffic facility. e. Conduct air traffic training on the vendor’s system and the identify differences between delivering PDC and DCL clearances. f. Identify any changes required to current air traffic procedures in order to support the DCL trials. g. Coordinate with identified air traffic facility any badge requirements for vendor installation and contract observers. h. Coordinate with Tech Ops and Air Traffic the times and personnel needed for equipment installation. Federal Aviation Administration 17 USE CASE Sample: Normal Initial and Revised 1. 2. 3. 4. 5. 6. 7. AOC files flight plan for identified flights. a. Filing is in accordance with analysis previously conducted on identified routes. For example, between the pluses routing that normally would be processed by HOST/ERAM, now would be eliminated. About thirty minutes prior to proposed departure time, HOST/ERAM sends flight data to the tower via the HAADS/PCRCU interface to the vendors HMI. At this time a courtesy copy of the DCL is sent to AOC with a gate number as reply. This activity is the same for the legacy PDC, but is used as an acknowledgment that the AOC received the PDC. Pilot performs log on function and requests departure clearance from the system. How the pilot receives the legacy PDC is unknown to the controller. It could be delivered via ACARS automation from the AOC, printed at the departure gate or printed at local airline operations. Pilots loads DCL clearance into the FMS. After conducting appropriate cockpit procedures, the flight crew replies with Wilco, Unable or Standby. The reply functionality is not used for the legacy PDC clearance since the legacy PDC is not sent directly to the aircraft. CD receives WILCO and marks flight progress strip as being delivered and hands to appropriate ground controller (GC). If Unable is received the controller reverts to voice to deliver the departure clearance .Current local procedures would be used to indicate delivery of the PDC, DCL, or voice clearance on the flight progress strip. Pilot pushes back and contacts GC. Federal Aviation Administration 18 8. Round control taxis aircraft to departure runway. 9. CD receives revised data from HOST/ERAM. 10. CD formulates revised DCL with the data that has changed from the initial DCL: route of flight (departure) airport, SID, En Route waypoints, arrival procedure, if filed, and arrival airport) initial altitude, expect altitude, departure frequency and beacon code. Revisions for PDC aircraft must be voiced to the flight crew since revisions are ineligible for PDC. 11. CD coordinates with appropriate controller to send revised data. 12. CD sends revised data. At the same time, the system sends to the AOC the revised data. 13. Flight crew receives indication that revised data available. 14. Flight crew processes revised data and responds with WILCO. If flight crew or avionics cannot accept revised data, then the flight crew responds with Unable and reverts to voice. If the flight crew responds with Standby and fails to respond with WILCO, the CD controller will be alerted by the system and the controller will revert to voice to deliver the revised data. 15. CD marks flight progress strip as delivered. 16. Once the flight departs and the ASR9/11 beacon antenna acquires the transponder code, a departure message (DM) is sent to HOST/ERAM, which in turn sends to the tower, via HAADS, a DM that the system will process to terminate the CPDLC session. Except for the return DM to the tower, the automatic DM from the ASR9/11 is applied to all departures. Federal Aviation Administration 19 Dept Clearance - DCL B737/747/757/767 TWR Flight Plan Message KDFW.SOLDO2.MEI.HONIE7.KATL 1 5 0 2 z A T C U P L I N K Cleared Route Clearance Uplink KDFW.MEI.HONIE7.KATL 1 / 1 S T A T U S O P E N C L E A R E D AN N838NN/AP DFW FLIGHT 0536/25 DFW -ATL PDC AAL536 XPNDR 0562 B738/Q P1210 390 KDFW SOLDO2 MEI HONIE7 KATL MAINT 10,000 EXP REQ ALT 10MIN AFT T/O CHECK DEPARTURE PROCEDURE FOR FREQUENCY END S O L D O R O U T E T WO MA I N T A I N S Q U AWK R N A V C L E A R A N C E D E P T 1 0 0 0 0 F T . 0 5 6 2 . S T A N D B Y < S E N D L O A D > A C C E P T < R E J E C T S E N D > Green = FMS Loadable Red = FLT Info or Manually Entered Flight Data Federal Aviation Administration Revised DCL – B737/747/757/767 Revised TWR Flight Plan Message KDFW.DARTZ3.TNV.DAS.LCH.J22.MEI.HONIE7.KATL 1505z ATC UP L I N K 1 / 2 S TATUS OP EN R E V I S E D R OU T E & R NA V S I D C L E A R E D R OU T E C L E A R AN C E DAR T Z T HR E E RNAV D E P T MA I N T A I N 1 0 0 0 0 F T . S Q U AWK 0 5 6 2 . Cleared Route Clearance FMC Uplink KDFW.TNV.DAS.LCH.J22.MEI.HONIE7.KATL 1505 z - - - - - C ON T I NU E D ATC UP L I NK 2/2 - - - - - L OG > A T C ME S S A G E S T ANDB Y < S E ND Green = FMS Loadable Red = FLT Info or Manually Entered Flight Data L AC <RE J ECT S - - - - - - - - - - - - - - - - - AT C ME S S A G E Federal Aviation Administration OA D> CEPT E ND> - - - L OG> DCL – B777 & 787 1 5 0 2 z TWR Flight Plan Message KDFW.SOLDO2.MEI.HONIE7.KATL A T C ^ U P L I N K C L E A R E D R O U T E C L E A R A N C E O R I G I N : K D F W D E S T : K A T L A R R I V A L : H O N I E 7 AN N838NN/AP DFW FLIGHT 0536/25 DFW -ATL PDC AAL536 XPNDR 0562 B738/Q P1210 390 V I A T O D I R E C T M E I S O L D O T W O M A I N T A I N S Q U A W K R N A V 1 , D E P T 1 0 0 0 0 F T , 0 5 6 2 . KDFW SOLDO2 MEI HONIE7 KATL MAINT 10,000 EXP REQ ALT 10MIN AFT T/O CHECK DEPARTURE PROCEDURE FOR FREQUENCY END ACCEPT LOAD FMC PRINT STANDBY REJECT REASONS REJECT Green = FMS Loadable Red = FLT Info or Manually Entered Flight Data Federal Aviation Administration Revised UM80 – B777/787 1 5 0 2 z A T C R E V I S E D Revised TWR Flight Plan Message KDFW.DARTZ3.TNV.DAS.LCH. J22.MEI.HONIE7.KATL Cleared Route Clearance Uplink KDFW.TNV.DAS.LCH.J22.MEI. HONIE7.KATL R O U T E R O U T E ^ U P L I N K & R N A V S I D C L E A R A N C E O R I G I N : K D F W D E S T : K A T L A R R I V A L : H O N I E 7 V I A T O D I R E C T T N V D I R E C T D A S D I R E C T L C H J 2 2 M E I D A R T Z M A I N T A I N S Q U A W K ACCEPT R N A V T H R E E 1 D E P T 1 0 0 0 0 F T . 0 5 6 2 . LOAD FMC PRINT STANDBY REJECT REASONS Green = FMS Loadable Red = FLT Info or Manually Entered Flight Data Federal Aviation Administration REJECT DFW-LHR – Departure Clearance ATC Filed Flight Plan N0488F370 NOBLY3 LIT J66 MEM Q34 SWAPP J42 BKW J147 CSN DCT ENO DCT VCN DCT CYN DCT HTO J121 SEY DCT YAHOO DCT WHALE N29B RAFIN/M084F390 NATU LIMRI/M084F390 NATU ETBO/N0472F410 DCT EVRIN UL607 NUMPO UP2 OKESI Y3 BEDEK .TULDDAA 232224 FROM CMD AN N774AN/AP DFW - QUTULDDAA010050CLR FLIGHT 0050/23 DFW -LHR PDC AAL50 XPNDR 2204 H/B772/Q P2240 370 ******** REVISED SEGMENT ******** -TRISS3 TXK J42 MEM******** FILED CLEARANCE ******** KDFW NOBLY3 LIT J66 MEM Q34 SWAPP J42 BKW***EGLL *************REMARKS************* MAINT 10,000 EXP REQ ALT 10MIN AFT T/O CHECK DEPARTURE PROCEDURE FOR FREQUENCY 1 5 0 2 z C R O V D J Q J J D D D L O R I I 6 3 4 1 I I I E U I A R 6 4 2 4 R R R A T C U P L I N K A R E D T E C L E A R A N C E G I N : K D F W T E C T L M S B 7 C E C T E E C T V E C T C LOAD FMC ^ D E S T : E G L L O I E W K S N C Y T M A P P W N O N N PRINT END Federal Aviation Administration 1 DFW-LHR DCL Continued 1 5 0 2 z V D J D D N D D D D D D I I 1 I I 2 I I I I I I A R 2 R R 9 R R R R R R E 1 E E A E E E E E E A T C T H S Y W R V N N N N L C T C T C T C C C C C C U P L I N K T T T T T T LOAD FMC PRINT O T E A H A O 4 4 5 5 I O Y H O A L F I D O 5 W 8 W 1 W 2 W M R O E N R 0 0 0 0 I ^ 2 5 4 3 2 0 0 0 0 1 5 0 2 z V D D U U Y N M S I I I L P 3 O A Q A T C A R E C T R E C T 6 0 7 2 U P L I N K T X E N O B B L Y T H R E E R N A I N T A I N 1 0 0 0 0 F U A K 2 2 0 4 ACCEPT LOAD FMC PRINT O E V U K E V T T R M E D B I P S E D ^ O N O I K E P T A R T U R E . STANDBY REJECT REASONS Federal Aviation Administration REJECT 3 Revised DCL Headers using UM169 Free Text 1 5 0 5 z A T C R E V I S E D U P L I N K 1 / 1 S T A T U S O P E N A L T I T U D E R E V I S E D E X P E C T R E V I S E D R O U T E C L E A R A N C E R E V I S E D R O U T E & R E V I S E D S I D R E V I S E D R N A V R E V I S E D S Q U A W K R E V I S E D E D C T R E V I S E D N O T E S A L T I T U D E R N A V S I D S I D Federal Aviation Administration Questions? 1 5 0 2 z A T C U P L I N K 1 / 1 S T A T U S O P E N C L E A R E D S O L D O R O U T E T WO MA I N T A I N S Q U AW K R N A V C L E A R A N C E D E P T 1 0 0 0 0 F T . 0 5 6 2 . S T A N D B Y < S E N D L O A D > A C C E P T < R E J E C T S E N D > Federal Aviation Administration Backup Federal Aviation Administration AOC Coordination • AOC Distribution List • Identifies who will be receiving a DCL • Courtesy Copies • AOC response with a Gate ID • Other Information provided to the aircraft • AOC Wind, Performance and T/O Data Federal Aviation Administration