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

2. 2 Federal Aviation Administration Data Comm SE DCIT#32, 16 April 2014 S1P2 ARRIVAL ROUTES IN DCL - DRAFT

3. 3 Federal Aviation Administration Data Comm SE DCIT#32, 16 April 2014 Arrival Procedure Uplink Background –Arrival procedures FP contains arrival transition & procedure, ATF.STAR, at end of route Uplink may include proc (type, procedurename, transition) eg proc(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. 4 Federal Aviation Administration Data Comm SE DCIT#32, 16 April 2014 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. 5 Federal Aviation Administration Data Comm SE DCIT#32, 16 April 2014 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. 6 Federal Aviation Administration Data Comm SE DCIT#32, 16 April 2014 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 arr proc, or –error the DCL

7. 7 Federal Aviation Administration Data Comm SE DCIT#32, 16 April 2014 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. 8 Federal Aviation Administration Data Comm SE DCIT#32, 16 April 2014 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 N o- T ransition case 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 proc arr, 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. 9 Federal Aviation Administration Data Comm SE DCIT#32, 16 April 2014 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. 10 Federal Aviation Administration Data Comm SE DCIT#32, 16 April 2014 S1P1 DCL ROUTE RULES- DRAFT

11. 11 Federal Aviation Administration Data Comm SE DCIT#32, 16 April 2014 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. 12 Federal Aviation Administration Data Comm SE DCIT#32, 16 April 2014 Uplinks with RouteAllocationS1P1 implemented RuleNotes UM79System-routeinfo starts with first route element (departure transition if present) -routeinfo ends with -{position} when route would have ended with airway, else -element prior to {position} -no dep proc in routeclearance optional DeptArpt included UM83System-routeinfo begins with -{position} when route would have started w/ airway, else -element after {position} -routeinfo ends with last route element (arrival transition if present) optional DestArpt included UM80System-routeinfo begins with departure transition (if present) and ends with arrival transition (if present) -no dep proc in routeclearance S1P1 Route Construction (draft)

13. 13 Federal Aviation Administration Data Comm SE DCIT#32, 16 April 2014 Route ElementAllocationS1P1 implemented RuleNotes Departure Procedures – SID/No Transiton SystemFor CAF, UM79/80, and non-route revisions, whether controller selected (eg EWR1) or filed (eg PORTE5.PORTE), uplinks include -freetext SID, no DTF -route begins with tower-adapted, published fix SID/DTF always freetext Tower can adapt no first fix (eg EWR1) or first fix in proc (eg WAGES for PORTE5) Departure Procedures – SID/Published Transition SystemFor CAF, UM79/80, and non-route revisions: - freetext SID, DTF - first element in routeinfo = DTF Departure Procedures – SID/fix on transition but not a published DTF (eg mid-transition exit) System/ Procedure - only tower-adapted SID/DTF combinations eligible for uplink - if adapted, uplinked same as published transition Tower adapted, or FP filing Arrival ProceduresSystem/ Procedure For UM80/83: - procedure (arr, STAR, ATF) as received from ERAM -last element in routeinfo = ATF No-transition and mid- transition joins uplinked S1P1 Route Construction (draft), continued

14. 14 Federal Aviation Administration Data Comm SE DCIT#32, 16 April 2014 Route ElementAllocationS1P1 implemented RuleNotes RadialsSystem/ Procedure - cannot uplink route with radials - can uplink um79 w/TO point prior Revise ERAM applied rte NAT TrackSystemSystem will not uplink route with NAT track name; Can uplink UM79 Airport to AirwayProcedureNo system requirement; uplink as rec’vd Revise ERAM applied rtes; FP filing Airway to AirwayProcedureNo system requirement; uplink as rec’vd ERAM applied rtes /waypoint dev / aircrew procedure < 4 char AirportProcedureSent as received Lat/Long limits-No check to ensure <21 lat/longs {position}-- not limited to fixnames, navaids or airports - not verified to appear only once in route S1P1 Route Construction (draft), continued