Data Communications DCIT Plenary - OWG Update Presented to: DCIT By: Andy Fry, Thane Inc. Date: March 29, 2016 Federal Aviation Administration Original Initial Revised Clearance – TDLS Development Items to Note: •APALO3.APALO should be displayed as APALO3 •This should be fixed in a future build – Submit to ER board – Mid April build? Data Communications Program March 29, 2016 Federal Aviation Administration 2 Production TDLS Revised Initial Clearance Items to Note: At the end of the second Free Text line the following was added” “THIS IS A REVISED CLEARANCE.” The reason for the two periods is due to message formatting rules – One is applied by TDLS and the other is applied by the avionics – Resolution is remove the one from TDLS. Submit to the ER board – Mid April build? Data Communications Program March 29, 2016 Federal Aviation Administration 3 Message Formatting discussion – Option 1 At the request of DCIT the OWG wished to explore the option of formatting the Revised Initial Clearance to improve readability with the following rules: 1 7 5 6 L E A R E D •Align like Clearance information together – C L E A R A N •Align This is a revised Clearance with “Cleared to Airport” information. •Align Climb Via with DP information A F T E R K O A K A R E Data Communications Program March 29, 2016 T C U P T O S T L L I C E . S T L A R P V I S V I C L E A R E D T F I L E D . E D C L E A R A P A L O 3 C L I M B V I E X P E C T F L 3 5 0 1 0 - - - - C O N T A •This is a Revised Clearance is paired with Route information A N K S C •Route Free Text character count – 66 •DP/Climb Via Free Text character count - 75 z T C M E S S A G I N U A T R T O T H I A N C E . A S I D I N M E D - - 1 / 2 A T U S O P E N O U T E S I S A F T - - - L O G > E •DP is paired with Climb Via info Federal Aviation Administration 4 Additional Format Options – Post meeting discussion 1 7 5 6 z C C A K I A E L L F O S P X E E T A A A E K A A L P E - - A T C R E D R A N C R S T A R P R E V O 3 C C T F - - - A T C T E L T I L L C U P L I N K 1 / S T A T O P S T L V I A R O U O . S I 3 O C A E M 5 N L E A R E D S F I L E D C L E A B V I A 0 1 0 M T I N U E D M E S S A G E Option 3 D R S I T A I N - 1 7 5 6 z 2 U S E N T E O T H I S N C E . D A F T - - - L O G > Paired info C C A A K I E L L P F O S X E E A T A A A L E K A P E - - A T C R E D T R A N C E O 3 C L R S T L A R P T R E V I C T F L - - C A T C O . I M C A S E 3 5 O N U P L I N K 1 / S T A T O P S T L V I A R O U B V I A L E A R E S F I L D C L E 0 1 0 T I N U E S I D D T O E D A R A N M I N D - - T C A L H E F O 2 U S E N T E I S . T G > M E S S A G E Option 4 •The above formats are added post the March 9th telecom asking to highlight the section – “THIS IS A REVISED CLEARANCE”. • Option 3 – This is a revised clearance is paired with the route information. Formatting limits where you add the “-”. This can be replaced with a PLUS but didn’t come across very well •Option 4 – Pared the Route and DP/TRN together •Need some feedback from the community to finalize the recommendation to Systems Engineering. – Right now the group consensus – Option 1,3, and 4. What say you… Data Communications Program March 29, 2016 Federal Aviation Administration 5 Additional Format Options – Additional User Input •Option 5 format brings forward the “This Is A Revised RTE” as a leading statement . •This also changes the text form Clearance to RTE. •Input still required form the community on the direction they would like to go. •Also, is there a need for controller input? •Discussion is based on a TDLS build Late June-July timeline Data Communications Program March 29, 2016 1 7 5 6 z A T C U P L I N K S C L E A R E D C L E A R A N + + T H I S R T + + T O A P A T E K O A A L O 3 - - - - C M E C A K C S S T O E . I S F T A S T L U S O P E N O U T E E D S E D C L E A R I L E D . S I D - - - - L O G E R S T L R P T A S L I M B V I A C O N N U E G T I V A A A E I 2 I R F D R / V A T T 1 > E Option 5 Federal Aviation Administration 6 Work Group items Discussion • Climb – out “None” Discussion – At the ER board – Usually occurs when there is a change in routing and the DP is repeated. See comments from Chad. • When there is a speed change to a published profile (Climb Via): Waiting on Flt Stds.. – FAA 7110.65V citation from Page 5–7-3: EXAMPLE− 2. “Cross Alisa at one zero thousand, then climb via the TIMMY One departure, except maintain two two zero knots.” • To the FDWG – Do you believe we should pursue this with the ATC work group – Chad… • CPDLC Uplink Content – Open – Waiting on Flt Stds.. See Climb Via discussion – Option field info in RTE section – Speed within the route section • Briefed CNS TF PCPSI group, Recommend that the facilities use the procedures as designed and not repeat published information • Flight Manual “CPDLC - DCL” notes contained in the airport pages? Review in progress • FAA flight Information - Airport Facilities directory, Notam’s, ATIS - Complete Data Communications Program March 29, 2016 Federal Aviation Administration 7 Ops Work Group Discussion – Con’t • Inclusion of DP/TRN with Rwy in all loadable uplinks when part of the clearance – Open Item • Altitude/Speed uplinks Enroute and Descent – Constraints discussion Discussed at DCIT 46 - Closed • NSDA – Planning discussion – What needs to been done to be ready for NSDA IOC??? Is there a specific date we can look for implementation? – Discussed at DCIT 46 – Update DCL and Frequency Management DCIT documents • • Logging On when on the ground – Standard Procedure? Disconnects to connect up with the Ocean Environment – Open discussion… • DCIT FDWG/Production DCL End2End User Guide Update – Will be distributed this week by 11 March for review and Plenary approval on 29 March 2016 • Started effort with Harris concerning documentation and tracing. • Need to address Enroute changes and incorporate into the DCIT docs. Data Communications Program March 29, 2016 Federal Aviation Administration 8 Questions or Comments? North Korea Over Flight Permit Data Communications Program March 29, 2016 Federal Aviation Administration 9