Follow on discussion: [distance] BEFORE/AFTER [position] CSG 10/26/2011 SC-215 CSG

1. Follow on discussion: [distance] BEFORE/AFTER [position] CSG 10/26/2011 SC-215 CSG Cedar Rapids, Iowa

2. Not agreeing, but acknowledging : ) Acknowledging 10/25/2011’s discussion of Pilot acceptability regarding BEFORE/AFTER (e.g. CROSS [distance] BEFORE or AFTER [position] AT …) Consider alternative solution using SPR defined Along Track Waypoint ATW: Variable - Route clearance enhanced Parameter - Route information additional sec (O) Parameter ATW along track waypoint Given: ATS Functions doc requires FMS integration for any msg containing the routeinformation additional sec and any msg containing a waypoint that the pilot must manually create, Question: Are we left only with the issue of how this crossing clearance is displayed across flight systems (FMC route pages, NAV display, CPDLC MCDU pages)?

3. BACKUP SLIDE • ATS Function (21 Oct 2011). • Section 2.4.1.2 CPDLC integration with the aircraft’s Flight Management System • Conditions when CPDLC messages exchanges require CPDLC/FMS integration: • a message that contains a [routeClearance][route information] or [route information additional sec] parameter. • a clearance message that contains a [routeClearance] parameter with a waypoint or fix that the pilot must create by either latitude and longitude, or two place bearings). • a clearance message concatenated with that contains a [routeClearance] parameter and more than one speed or altitude instruction (as part of the RouteClearance parameter or in a separated message elements). • automatic triggering of a CPDLC report that are required to be sent on the occurrence of an event (i.e. Position Report supported by CPDLC).

4. BACKUP SLIDE VARIABLE: Route information additional sec PARAMETER: Sequence: Sequence 1-8 ATW along track waypoint (O) Reporting points (O) Sequence 1-4 intercept course from (O) Sequence 1-8 Hold at waypoint(O) Sequence 1-32 Waypoint speed level(O) Sequence 1-32 RTAsec Required time arrival (O)

5. BACKUP SLIDE VARIABLE: ATW along track waypoint ATW distance ATW distance tolerance ATW level ATW level tolerance PARAMETER: Sequence: Position (M), ATW distance (M), Speed (O), ATW level (M) or (O) ? ? Sequence: ATW distance tolerance (M), Distance (M) Specifies the tolerance of the ATW level “Plus”, or “Minus” Sequence: ATW Level Tolerance (M), Level (M) Specifies the tolerance of the ATW level as “At”, or “At or above”, or “At or below”

6. Example #1: Providing clearance within a CROSSing msg: MLB ATW level (O) allows this example. Um46 CROSS [position] AT [level], where position is defined as an ATW without the ATWlevel LEBUR Example CDU text : CROSS TOPPR+10NM AT 9000FT CROSS TOPPR/+10NM AT 9000FT ? ? ? TOPPR X BLUFI 30nm HEATT

7. Example #2: Providing clearance within a route clearance msg: MLB Um79 CLEARED TO [position] VIA [route clearance], where route clearance includes route information additional, which includes an ATW with an ATWlevel LEBUR Example CDU text : CLEARED TO BLUFI VIA LEBUR.TOPPR.[TOPPR+10NM/9000FT].BLUFI ? ? ? TOPPR Is a route clearance uplink the best msg choice when there is no change to the lateral routing? Doesn’t this approach require either the automation or controller to compose a route clearance when the intent is really just to insert a Crossing constraint along the current route. X BLUFI 30nm HEATT