Federal Aviation Administration Data Communications Implementation Team (DCIT) DCIT #24 En Route Route Clearances Draft Use Case Introduction Boeing – Arlington, VA S. Ferra

Federal Aviation Administration S1P2 Initial Route Clrnc Capability An Introduction to Draft FAA Use Cases S1P2 Initial Route Clearance Capability 1.Use Case: ABRR Provided Routes (“Go Button”) 2.Use Case: Controller Initiated Routes uM74 PROCEED DIRECT TO [position] uM79 CLEARED TO [position] VIA [routeclearance] uM80 CLEARED [routeclearance] uM83 AT [position] CLEARED [routeclearance] dM22 REQUEST DIRECT TO [position] Separate TA Use Case

Federal Aviation Administration S1P2 Initial Route Clrnc Capability Ref: ERAM ABRR Use Case, dated May 2012 To be deployed before Data Comm

Federal Aviation Administration S1P2 Initial Route Clrnc Capability Ref: ERAM ABRR Use Case, dated May 2012 Protected Segment The part of a flight-specific reroute that is important for achieving the goal of the reroute TMI. This segment will be protected from ERAM processing for adapted routings, excluding the convergence point. Sector controllers will avoid moving the aircraft off of this segment, except when operationally necessary. This part of a reroute is used by the TFM automation to determine reroute conformance. The last fix in the protected segment should be considered for auto route application. Convergence Point Fix where a flight rejoins original route to complete an airborne reroute. Convergence point may be destination. Shown in white. Divergence Point Point where a flight diverges from its current cleared route to begin following an airborne reroute. A divergence point can either be a fix on the current route, or if no fix is identified, current position. If on current route, shown in white, otherwise shown in cyan.

Federal Aviation Administration S1P2 Initial Route Clrnc Capability Ref: ERAM ABRR Use Case, dated May 2012 Current Route Pending TFM Reroute

Federal Aviation Administration Next Steps Back to you Rob