S1P1/P2 Production System: DCL Route Rules DCIT#32 16 April 2014

1. S1P1/P2 Production System: DCL Route Rules DCIT#32 16 April 2014

2. S1P2 Arrival Routes in DCL - DRAFT

3. Arrival Procedure Uplink • Background • Arrival procedures • FP contains arrival transition & procedure, ATF.STAR, at end of route • Uplink may include proc (type, procedurename, transition)egproc(arr,TUDOR2,RBV) • ERAM treats the route element prior to the STAR as the name of the fix where the aircraft joins the arrival procedure • Avionics use the ATF (if present) to select which, if any, transition to load • proc(arr, TUDOR2, - ) loads the TUDOR2 procedure with no transition • Avionics needs route to ‘connect’ to arrival • Last fix in routeinfo must be the fix where aircraft starts (joins) arrival procedure • Only impacts uplinks that contain a route and arrival procedure • Three arrival procedure cases • Published Transition • No Transition • Mid-Transition Join

4. Arrival Procedures • Published Transition • Fixname prior to STAR in route is a named/published transition • Fixname is the Arrival Transition Fix, ie where the aircraft will join the procedure • Fixname is in the aircraft NavDB • To load, AC requires: • Last element in routeinfo = ATF • Transition in proc uplink = ATF • proc (arr, TUDOR2, RBV) • TDLS can create loadable uplink with no additional info

5. Arrival Procedures • No Transition Arrival • Fixname prior to STAR in route is either: • First fix in the base/common leg of the arrival procedure (eg PIECH.TUDOR2) • The name of the arrival procedure with no transition (eg TUDOR.TUDOR2) • ERAM assumes the procedure is joined at the fix in the route prior to the STAR (eg PIECH) • To load, aircraft requires: • Last element in routeinfo = first fix in base/common leg • Transition in proc uplink = blank • TDLS needs to know: • Route contains a no-transition arrival • proc (arr, TUDOR2, - ) • First fix in base/common leg (PIECH)

6. Arrival Procedures • Mid-transition Join (joining procedure after a published ATF) • Fixname prior to STAR in route is where the aircraft joins arrival proc • Between the published ATF and first fix in the base/common leg (EWOKS.TUDOR2) • ERAM assumes the procedure is joined at that fix • No universally loadable uplink format • For some aircraft, uplink is loadable if it has: • Last element in routeinfo = fixname • Transition in proc uplink = fixname • TDLS needs to know: • This is a mid-transition join • What to do: • Include/exclude the arrproc, or • error the DCL

7. Arrival Procedure Uplink changes • ERAM already advises if the fix is a transition fix, or not • To maximize loadability, TDLS could use: • Type of arrival transition • First fix in the arrival (No-Transition case) • Include/exclude the arrival, or not to send the DCL (Mid-Transition Join) • Type and last fix could come from ERAM • Handling Mid-transition Join could be national setting (adaptation)

8. Arrival Procedure Uplink Alternatives • A procedural option could simplify: • To make No-Transition Arrivals loadable, require the FP filing to use the first fix in the base/common leg as the ATF (eg PIECH.TUDOR2) • In this case, ERAM only needs to indicate this is a No-Transitioncase • Another procedural option could further simplify: • Advise FP filers to file mid-transition joins only if their target aircraft can load them • In this case, TDLS doesn’t need to know if the arrival is a mid-transition join – • TDLS would include transition in procarr, and as the last route element. • ?: Prevalence/remedy of ERAM applied routes that use mid-transition join • Then TDLS would only need one new bit • Arrival is No Transition case (yes or no) • Used to include or blank the transition in the uplink proc

9. Arrival Procedure Uplink • Next Steps • Review procedural simplifications with user community • Determine quantity/remedies for ERAM applied mid-transition joins • Assess LoE for ERAM to provide additional data in ERAM-TDLS i/f • Decide when to incorporate in TDLS, and S1P2 • Review results/recommendations with DCP

10. S1P1 DCL Route Rules- DRAFT

11. S1P1 Route Construction • S1P1 Routes • Constructed and validated by ERAM, from FP/etc • All revisions to route processed by ERAM • TDLS creates routeclearance/routeinfo from route • Maximizes loadability • Does not revise routing • TDLS Route Processing • Uplink message selection (CAF, initial um79, um80, etc) • Packaging for inclusion in uplink • Message and format rules may mean DCL uplink not possible • Adding first or last route elements to routeinfo, for loadability • Determine appropriate value for certain variables, etc

12. S1P1 Route Construction (draft)

13. S1P1 Route Construction (draft), continued

14. S1P1 Route Construction (draft), continued