Presented to: DCIT By: Andy Fry, Thane Inc. Date: September 20, 2011 Federal Aviation Administration...

Presented to: DCIT

By: Andy Fry, Thane Inc.

Date: September 20, 2011

Federal AviationAdministrationData Communications

DCIT #9

Flight Deck

Working Group

Data Communications Program2Federal Aviation

AdministrationSeptember 20, 2011

Agenda• System Engineering Action Item

– Review and Discuss CPDLC Disconnect after Takeoff– DCL Clearance Delivery Time – ATC Discussion

• Review the DCL Services description – UM80 Initial DCL– UM79 & UM83 Revised Clearances– Make recommendations to End-To-End Use Case

• Review and Discuss Flight Deck Procedures– CPDLC LOGON for Trial– FMS Loading– FMS RTE and LEGS Checking requirements

• Catalog Airline Specific Aircraft Capability:– ATS Print Functionality Discussion– Nav Data Base Configuration – Customized for airline operations?– Integrated FMS Capability – Open Discussion

• Discuss MITRE DCL Demo of Initial and Revised Clearance



Disconnecting CPDLC Link• System Engineering Action Item

– Review and Discuss CPDLC Disconnect after Takeoff• Boeing and Airbus differences

– Boeing always notifies the flight crew with a Aural and Visual cockpit indication of CPDLC status - Termination

– Airbus does not alert the flight crew of CPDLC termination when your session has been discontinued – display status

– Ground System will send a CPDLC system level message that the CPDLC session has been Discontinued after Takeoff

• Aircrew will be notified• Options for this message are Altitude or Time or Pilot Initiated Log Off

– Altitude Advantage: Predictable and can be set to not interfere with other flight crew activities (Checklist, Sterile Cockpit)

– Time/Handoff: Handoff can vary due to other controller / ground system activities, Time is a variable set in the ground system D+3min

– Pilot Initiated Log Off: Time Consuming, changes flight deck procedures• Recommendation: Altitude disconnect @ 12000 FT MSL. 2nd Option – Time Adaptable handoff D+10 Mins

– DCL Clearance Delivery Time – ATC Discussion• Flight Deck request an earlier delivery of DCL clearance changed from 30 mins to a DCL Clearance

Delivery of 45 mins prior to Proposed Departure Time• Recommendation: Flight Deck requires DCL Clearance Delivery 45 mins prior to Proposed Departure Time

- Tower will investigate, Spurious messages will be investigated for occasional revised messages



Review the DCL Services description

• UM80 Initial DCL– Analysis is Complete

• ATC working group working with FAA Tower to determine if modification will be necessary for the following:

– EXP ALT WI 10 MINS– DEP FREQ

• Recommendation: No changes, continue with current solution

• UM79, UM83 and UM80 Revised Clearances– Action is to recommend to the DCIT any further Flight Deck

concerns or needs• Coordinate with ATC working Group concerning any issues• Recommendation: No changes, continue with current solution

• Make input to End-To-End Use Case– Format Descriptions were submitted for DCIT review

• Recommendation: Input to the End2End was completed from flight deck working group



J50

J50

Initial DCL – Base Line Clearance w/RNAV SIDUM80 {RouteClearance}

Urg(N)/Alr(A)/Resp(W/U)/Rec(RC)

Airport Departure[0]Airport Destination [1]Procedure Arrival [6]Route information [7]

KDFWKMIASSCOT1.SZWEIC..AEX.J50.CEW.J2.SZW

(6) Optional if a ARR is not part of the route Information

EICEIC

AEXAEXMCBMCB

CEWCEWSZWSZW

UM169 [freetext]

Urg(N)/Alr(L)/Resp(R)

FreeText ::= IA5String (SIZE (1..256))

CLARE2.EIC RNAV SID Manual Entry by the Flight Crew

SSCOT1.SZWSSCOT1.SZW

CLARE2.EIC

J2

•Loaded Data

KDFWKDFW

KMIAKMIA



Initial DCL – Base Line Clearance w/RNAV SID

UM Number

Response Attributes

ASN1Definition

Sample Clearance Lab Validation

UM80 {RouteClearance}



KDFWKMIASSCOT1.SZWEIC..AEX.J50.CEW.J2.SZW

(6) Optional if a ARR is not part of the route Information

UM169 [freetext]



CLARE2.EIC RNAV SID

UM19 MAINTAIN [level]

Urg(N)/Alr(A)/Resp(W/U)/Rec(VC)

LevelType ::= CHOICElevelFeet [0]levelFlightLevel[2]

MAINTAIN 10000FT

UM169 [freetext]



EXP FLXXX WI 10 MINAFT DEP. DEP FREQ 118.55EDCT 2145Z

FL/FT, MIN/MILES, Freq is Ctrl selected from DP, EDCT – display if HADS provides

UM123SQUAWK [code]

Urg(N)/Alr(M)/Resp(W/U)

Code ::= SEQUENCE SIZE (4) OF CodeOctalDigitCodeOctalDigit ::= INTEGER (0..7)

SQUAWK 0562



Revised DCL – UM83 – AT POSITION CLEARED

J50J50

EICEIC

AEXAEXMCBMCB

CEWCEW

SZWSZW


CLARE2.EIC

UM83AT [position] CLEARED [routeClearance]


PositionPosition ::= SEQUENCE SIZE (2) OF Position – atpositionRouteClearance ::= SEQUENCEAirport Destination [1]Procedure Arrival [6]Route information [7]

CEW

KMIASSCOT1.SZWKRSTO..SZW

All previously entered data (Man or via FMC Load) is retained except for wind data at point KRSTO and beyond to destinationNOTEDP, RWY, T/O Data, Performance Data and Wind Data to CEW is retained.

KRSTOKRSTO

UM83 can modify anything from a DP Transition Fix on an existing route of flight to

destination - No change to the DP or Transition

• Yellow is the loadable uplink

•Red = new RTE on Nav Display

KDFWKDFW

KMIAKMIA



UM83Route Modification: from a point on an existing route of flight to destination. No change to the DP or Transition. Route information: Route change from point on original route to destination to include arrival procedure as applicable.

UM Number

Response Attributes

ASN1Definition


UM169 [freetext]



REVISED ROUTE

UM83AT [position] CLEARED [routeClearance]


PositionPosition ::= SEQUENCE SIZE (2) OF Position – atpositionRouteClearance ::= SEQUENCEAirport Destination [1]Procedure Arrival [6]Route information [7]

CEW

KMIASSCOT1.SZWKRSTO..SZW




MAINTAIN 10000FT



J50

Revised DCL - UM79 - Cleared TO VIA

EICEIC

AEXAEXMCBMCB

CEWCEWSZWSZW


CLARE2.SWB

J2

UM79CLEARED TO [position] VIA [routeClearance]


PositionPosition ::= SEQUENCE SIZE (2) OF Position – topositionRouteClearance ::= SEQUENCEAirport Departure[0]Airport Destination [1]Route information [7]

MCB

KDFWKMIASWB

All previously entered data (Man or via FMC Load) is retained FROM MCB and beyond to destinationNOTEDP is manually entered by the flight crew.RWY, T/O Data, Performance Data and Wind Data From MCB to destination is retained.

UM169 [freetext]


FreeText ::= IA5String (SIZE (1..256)) CLARE2.SWB Requires manual entry by the flight crew

SWBSWB

UM79 can modify anything to a point on an existing route of flight – Last modification point is limited to the

Transition Fix on the Arrival - No change to the Arrival Procedure or Transition is allowed


•Red = new RTE on Nav DisplayKDFWKDFW

KMIAKMIA



UM79:Procedure Departure and different transition fix. Route information: different transition fix, links with an existing downstream route of flight waypoint

UM Number

Response Attributes

ASN1Definition


UM169 [freetext]



REVISED DP TRSN AND RTE

UM79CLEARED TO [position] VIA [routeClearance]


PositionPosition ::= SEQUENCE SIZE (2) OF Position – topositionRouteClearance ::= SEQUENCEAirport Departure[0]Airport Destination [1]Route information [7]

CLEARED TO MCB

KDFWKMIASWB

UM169 [freetext]



CLARE2.SWB




MAINTAIN 10000FT



J50

J2

Q102

Q102

Q102

J86

J50

UM80 Reroute - Complete Change of Flight

EICEIC

AEXAEXMCBMCB

CEWCEWSZWSZW




KDFWKMIACYY.CYY6CLL.IAH.J86.LEV.Q102.CYY

Removes all previously loaded data – RWY, DP, T/O Data, Wind Data

UM169 [freetext]



ARDIA3.CLL RNAV SID Manual Entry by the flight crew

BAGGSBAGGS

CLLCLL

IAHIAHLEVLEV

BLVNSBLVNS

CYYCYY

KDFWKDFW

KMIAKMIA


•Red = new RTE on Nav Display

ARDIA3.CLL

CYY.CYY6



UM80 – Revised Clearance:Complete change of route using UM80 - Procedure Departure and different transition fix, Route information: different transition fix, change of route to connect to a new arrival procedure to original destination

UM Number

Response Attributes

ASN1Definition


UM169 [freetext]



REVISED DP AND RTE




KDFWKMIACYY.CYY6CLL.IAH.J86.LEV.Q102.CYY

UM169 [freetext]



ARDIA3.CLL RNAV SID




MAINTAIN 10000FT

UM169 [freetext]



REVISED DEP FREQ 125.12



Flight Deck Procedures

• CPDLC LOGON– Flt ID: FDX765 “ICAO ID”– Tail Number: N787BA– Facility: Trial will be Facility ID (e.g., KLAS)

• FMS Loading: See next slides• FMS RTE and LEGS Checking requirements:

See next slides• Recommendation: No changes,

– Next step is to review current airline procedures and review at the next DCIT Flight Deck Working group



ATC MSG / Response Attributes



DCL Request / DP and RWY Entry

Request a Departure Clearance (DCL) Manual Entry of DP and Runway ATC MCDU

Key……………………………..Select Clearance 4R…………………….

…………..Select REQUEST CLEARANCE……………………

Select (Some airplanes) SEND…..

………………………………………..Select

Dept/ARR…………………….……………….Select

RWY………………………..……………………Select Procedure………………..

…………………..Select Transition…………………………….

……….Select RTE………………………………………..

……..Select Verify the appropriate Departure procedure, Runway and Transition are correct against the DCL with no Route Discontinuities

Execute…………………………………….…..Select



FMS RTE and Legs Check



Catalog Airline Specific Aircraft Capability

• Aircraft Configuration– ATS Print Functionality Discussion

• Airlines? Will send a request to all DCIT Airlines for input

– Nav Data Base Configuration – Customized for airline operations?

• Airlines? Will send a request to all DCIT Airlines for input

– Integrated FMS Capability – Open Discussion• Access to Messages• Complex Clearances• Duplicate Waypoints• Shared Displays

– Postponed until next DCIT



MITRE DCL Demo

• Discuss MITRE DCL Demo of Initial and Revised Clearance– Lab Environment

• B777 Like cockpit• Hosted FMS / CPDLC Application• Aircraft already Logged on

– Initial DCL: UM80 Full RTE Clearance DFW-MIA– Revised DCL: UM83 due to WX near “CEW”

• Retention of DATA• Reduced Flight Crew Workload vs. “Old” UM80 Revised

Clearance procedures



Backup



Action Items:

Presented to: DCIT By: Andy Fry, Thane Inc. Date: September 20, 2011 Federal Aviation Administration...

Documents

Transcript of Presented to: DCIT By: Andy Fry, Thane Inc. Date: September 20, 2011 Federal Aviation Administration...