Feb 14, 2008 Airbus, Thales Air Systems, DSNA EMMA2 CPDLC trials in Toulouse EMMA2 outcomes from Toulouse trials.

Feb 14, 2008

Airbus, Thales Air Systems, DSNA

EMMA2 CPDLC trials in Toulouse

EMMA2 outcomes from Toulouse trialsEMMA2 outcomes from Toulouse trials

Page 2

CPDLC Ground Clearance Function Procedures

Page 3

Taxi out – global overview

Page 4

Taxi out – nominal case (1/4)

Pilot ATCO

Notification (onboard initiated) *

CPDLC establishment (ground initiated) *

Departure Clearance request

EXPECT ROUTING TO HOLDING POINT Z8 RWY 27R VIA TWY G N BD13 D Y11 RWY 27L K8 Z8 *

ROGER

CONTACT LFPG GND 121.800

WILCO

DE

LIV

ER

Y

Voice contact on LFPG Delivery frequency

Either through voice or through datalink ? If

datalink, either CPDLC or A623 ?

Departure Clearance * *

EXPECT computed by ground

system sent in response

to Departure Cl. Request (controller

may have to validate it)

Pilot may append any foreseen constraints (if

datalink: free text?specific message?) so that the EXPECT then

provided may fulfil them

Only one CPDLC

connection is envisioned for

ground operations

(TBC). Ground system

will be in charge to

propose the messages to the relevant

control position.

Page 5


Pilot ATCO

Voice : Ground 121.800 , DLH123

Voice : DLH123, proceed by datalink *

STAND D8 + REQUEST START-UP CLEARANCE + REQUEST PUSHBACK CLEARANCE *

START-UP APPROVED & PUSHBACK APPROVED *

Start-up and pushback requests may be sent separately with or without the current

position.

WILCOStart-up and

pushback clearances are sent separately if requests had

been sent separately

GR

OU

ND

#1Voice

phraseology is only

provided as an example

Voice : Proceeding by datalink , DLH123

Page 6


Pilot

CONTACT LFPG GND 121.600 *

WILCO

TAXI TO RWY 27R VIA TWY N BD13 D Y11 HOLD SHORT RWY 27L *

REQUEST TAXI

TAXI TO INTERSECTION N/NA2 VIA TWY G N

WILCO

WILCO

MONITOR LFPG TWR 119.250 *

WILCO

GR

OU

ND

#1G

RO

UN

D #2

ATCO



Transfer to Ground#2 frequency when near

to N/NA2

The next taxi clearance may be

provided without pilot request

Transfer to Tower

frequency when near to RWY 27L.

Message could either be

Monitor or Contact

Voice phraseology

is only provided as an example


Page 7


Pilot

TAXI TO HOLDING POINT Z8 RWY 27R VIA TWY K8 Z8 *

WILCO *

Voice: DLH123, cross runway 27 left and maintain holding point K8 + datalink information confirming the cross clearance,

for moving map display purpose (removal of stop bar) and Runway Incursions alerting capability *

Voice: crossing runway 27 left and maintaining holding point K8, DLH123 *

Voice: DLH123, line-up runway 27 left and wait + datalink information confirming the cross clearance,

for moving map display purpose (removal of stop bar) and Runway Incursions alerting capability *

Voice: lining up runway 27 left and waiting, DLH123

Voice: DLH123, cleared for take-off runway 27 left wind 280 degrees 10 knots + datalink information confirming the take-off clearance,

for moving map display purpose *

Voice: cleared for take-off runway 27 left, DLH 123 *

TO

WE

R

ATCOVoice remains

for runway clearances. The means through

which the datalink

information is sent is TBD.

Only voice read-back required (no

acknowledgment of the datalink information)

TBC according to airport

configuration (i.e. relevant

through datalink or

voice?)Only voice read-back

required (no acknowledgment of

the datalink information)



Voice remains for runway

clearances. The means through

which the datalink


Page 8

Taxi in – global overview

Page 9

Taxi in - Nominal case with APP, TWR & GND equipped with CPDLC (1/3)

Pilot ATCO

EXPECT ROUTING TO STAND D8 VIA TWY V1 S2 RWY 26R S2 W2 N E GE2 G *

ROGER

CONTACT LFPG TWR 119.25 *

WILCO

ground forwarding between Approach and Ground *

CPLDC already established with APP

Transfer of CPDLC connexion between APP and ground system *

(seamless transfer for the crew – no “manual” notification required)

EN

RO

UT

E-A

PP

RO

AC

HATIS request

ATIS *

Either through voice or through datalink ?

EXPECT computed from RWY exit, if

available, otherwise “standard”

routing (TBC)

RWY exit *RWY exit data

provided from ATC via TBD

Ground forwarding

may enable the Approach to

exchange, with the pilot, data

related to ground

operations (e.g. taxi route information)

Transfer to Tower frequency

Only one CPDLC connection is envisioned for ground

operations (TBC). Ground system will be in charge to propose the message to the relevant control position.

Page 10

Taxi in - Nonimal case with APP, TWR & GND equipped with CPDLC (2/3)

Pilot ATCO

Voice : Tower 119.25 , DLH123

Voice: DLH123, wind 270 12 knots,runway26 left cleared to land. Report runway vacated or in case of missed approach.

Voice : Runway 26 left, cleared to land, DLH123

Voice : Runway 26 left vacated on taxiway V1, DLH123

Voice: DLH123, hold short of runway 26 right on taxiway S2.

Voice : holding short of 26 right, on taxiway S2, DLH123

TO

WE

R

Voice: DLH123, cross runway 26 right and maintain holding point S2 + datalink information confirming the cross clearance for moving map

display purpose only *

Voice: crossing runway 26 right and maintaining holding point S2, DLH123 *


WILCO *

Voice remains for runway

clearances. The means through

which the datalink




Transfer to Ground frequency

Page 11

Taxi in - Nonimal case with APP, TWR & GND equipped with CPDLC (3/3)

TAXI TO STAND D8 VIA TWY S2 W2 N E GE2 G *

WILCO

GR

OU

ND

Pilot ATCO



The taxi clearance after landing may be

provided without pilot request

Voice phraseology

is only provided as an example


Page 12

Expect Routing information use

Page 13

EXPECT ROUTING use (1/2)

• Purpose: It intends to inform the flight crew of the taxi route or at least the final destination, i.e. the take-off runway for taxi out and the stand/parking for taxi in, even if the controller sending this information message is not in charge of the final destination

• Taxi out : 2 messages possible

• UL#243 : EXPECT ROUTING TO [airportElement] VIA [

provides the expected taxi route to the final destination

• UL#254 : EXPECT ROUTING TO [airportElement] WITH PUSHBACK FACING [direction]

only the final destination and optionally the pushback direction are known

Note: the airportElement and the taxiRoute elements are the information displayed on the DCDU and the taxiRouteClearance element is dedicated to the graphical depiction on the moving map.

Expected final destination

Start of taxi Entry in an area dependingon a different controller

•taxiRoute] [taxiRouteClearance]

Page 14

EXPECT ROUTING use (2/2)

• Taxi out (cont.) :

• Information useful during flight preparation, i.e. at the same time departure clearance is granted

• Taxi in : only one message relevant

• UL#243 : EXPECT ROUTING TO [airportElement] VIA [taxiRoute] [taxiRouteClearance] , same intent/features as for taxi out

• Information useful early during the approach phase (appropriate moment is TBD- not worthy while a/c on ground)

Pilot

EXPECT ROUTING TO HOLDING POINT Z8 RWY 27R VIA TWY G N BD13 D Y11 RWY 27L K8 Z8

ROGER

ATCODeparture Clearance request

Departure Clearance

Either through voice or through datalink ?

Page 15

Taxi clearance use

Page 16

TAXI CLEARANCE use (UL#241) – 1 / 4

A / Case of runway crossing, final destination known

1st message Taxi To 2nd message Taxi To

Final destinationStart of taxi HP of RWY to cross


TAXI TO [airportElement] TAXI TO [airportElement]

VIA [taxiRoute] VIA [taxiRoute]

[taxiRouteClearance] [taxiRouteClearance]

HOLD SHORT OF [airportElement](the end of clearance point corresponds to a

holding point)

Note: the airportElement and the taxiRoute elements are the information displayed on the DCDU and the taxiRouteClearance element is dedicated to the graphical depiction on the moving map..

Page 17


A / Case of runway crossing, final destination known

Pilot

TAXI TO RWY 27R VIA TWY N BD13 D Y11 HOLD SHORT OF RWY 27L

WILCO

TAXI TO HOLDING POINT Z8 RWY 27R VIA TWY K8 Z8

WILCO

ATCO

Aircraft cleared to cross RWY 27L

Note: the use of datalink taxi clearance after runway crossing is TBC according to airport configuration (i.e. relevant through datalink or voice? A priori interviewed ground controllers mentioned they would aim at always updating their system even when few remaining taxi route but it should be confirmed)

Page 18


B / Case of final destination unknown, ground control segmentation


Final destinationStart of taxi Ground control limit point


TAXI TO [airportElement] TAXI TO [airportElement]

VIA [taxiRoute] VIA [taxiRoute]

[taxiRouteClearance] [taxiRouteClearance]


Page 19


B / Case of final destination unknown, ground control segmentation

Pilot

TAXI TO INTERSECTION N-NA2 VIA TWY G N

WILCO

TAXI TO HOLDING POINT Y13 RWY 27L VIA N B BQ2 Y13

WILCO


WILCO

GR

OU

ND

#1G

RO

UN

D#2

ATCO


Voice : DLH123, proceed by datalink


Page 20

Revise taxi clearance use

Page 21

REVISE TAXI CLEARANCE use (UL#244) – 1 / 2

End of taxi clearance pointStart of taxi

End of revise taxi Clearance point

REVISE TAXI TO [airportElement] VIA [taxiRoute] HOLD SHORT OF [airportElement] [taxiRouteClearance]

2nd message :

Revision is sent from the current position of the aircraft (not from the deviating point)

The end of the revise taxi clearance point may be the same as the end of initial taxi clearance point provided that a part of the taxiRoute is different.

Current a/c position

TAXI TO [airportElement] VIA [taxiRoute] HOLD SHORT OF [airportElement] [taxiRouteClearance]

1st message :


Page 22

REVISE TAXI CLEARANCE use (UL#244) – 2 / 2

ATCOPilot

TAXI TO HOLDING POINT Y13 RWY 27L VIA N B BQ2 Y13

WILCO

REVISE TAXI TO HOLDING POINT Y11 RWY 27L VIA B BD20 Y11

WILCO

GR

OU

ND

Long Term change in the

cleared taxi route => revision only

managed by datalink

Page 23

Mixed mode communication

Page 24

MIXED MODE COMMUNICATION (2/2)

• Example :

Pilot

TAXI TO HOLDING POINT Y11 RWY 27L VIA N BD13 D Y11

WILCO

REVISE TAXI TO HOLDING POINT Y11 RWY 27L VIA B BD20 Y11

WILCO

ATCO

Voice : DLH123, disregard CPDLC TAXI message. Turn right on B. + simultaneous sending of a datalink warning dedicated to the airport moving map (e.g. TAXI CLEARANCE: CHANGE IN PROGRESS)

Voice : Taxiing holding point Y11 runway 27 left via taxiway B BD20 Y11, DLH123

GR

OU

ND

Near intersection

N/B

Voice phraseology is TBC and the use

of a datalink warning dedicated

to the airport moving map is to

further studied

Page 25

CPDLC Ground Clearance Messages Recommendations

Page 26

How to read the message tables

• Caption

UM : Uplink Message

DM : Downlink Message

In [ ] : parameter

In italic : optional field

• Sorting into groups (to be normalized or not)

Meaning of colours used:

EMMA2 messages to be evaluated before normalisation of D-TAXI

EMMA2 messages to be modified for normalisation of D-TAXI

Messages recommended for normalisation of D-TAXI

EMMA2 messages not recommended for normalisation of D-TAXI

Page 27

UPLINKS – Existing messages

UM# In EMMA2 AIF Std2 trialsRecommendation for normalisation of D-TAXI

Justification

0 UNABLE UNABLEBasic PAM (Pilot Acknowledgement Messages)

1 STANDBY STANDBY

3 ROGER ROGER

73 [departureClearance]

Modification of the format defined in SARPs ATN (newUM73=UM288 envisioned by WG78 at 1st of march 09)

The introduction of DCL service through CPDLC service should be further studied

117CONTACT [unitName] [frequency]

CONTACT [unitName] [frequency] ATC Communication Management

(ACM) for voice communication transfer120

MONITOR [unitName] [frequency]

MONITOR [unitName] [frequency]

158 ATIS [ATISCode] ATIS [ATISCode]Reminder of ATIS code number, to be used in conjunction with start-up, pushback, taxi, or take-off clearances.

199 Free text Free text Operational free text

Page 28

UPLINKS – Basics


Justification

239 [clearanceType] APPROVED [airportLocation]

[clearanceType] APPROVED [airportLocation] [time]

Can be used for pushback and start-up clearances.

The optional parameter [airportLocation] may include a stand position or a pushback direction.

The time parameter is optional and could be appended to provide further information

240 TAXI TO [airportElement]

VIA [taxiRoute]

HOLD SHORT OF [airportElement]

Not recommended for normalisation

If the parameter [taxiRouteClearance] is made optional, this message becomes useless.

241 TAXI TO [airportElement]

VIA [taxiRoute]


[taxiRouteClearance]

TAXI TO [airportElement]

VIA [taxiRoute]



1) The parameter [taxiRouteClearance], containing the data for graphical display, should be made optional, so that it allows a flexible use with or without the graphical data.

2) The parameter [taxiRouteClearance] should allow a flexible definition of the taxi route to be displayed on a moving map, with either a sequence of type Lat/Long, or a sequence of type taxiway identifiers (still to be defined according to airport data bases).

Page 29

UPLINKS – Clearance revisions


Justification

244 REVISE TAXI TO [airportElement]

VIA [taxiRoute]



REVISE TAXI TO [airportElement]

VIA [taxiRoute]



Same remarks as for UM#241 on the parameter [taxiRouteClearance].

This message should have a higher priority characterization.

253 REVISE TAXI TO [airportElement]

VIA [taxiRoute]


Not recommended for normalisation

If the parameter [taxiRouteClearance] is made optional, this message becomes useless.

Page 30

UPLINKS – EXPECT ROUTING


Justification

243 EXPECT ROUTING TO [airportElement]

VIA [taxiRoute]


EXPECT ROUTING TO [airportElement]

VIA [taxiRoute]


Same remarks as for UM#241 on the parameter [taxiRouteClearance].

254 EXPECT ROUTING TO [airportElement]

WITH PUSHBACK FACING [direction]

EXPECT ROUTING TO [airportElement]

WITH PUSHBACK FACING [direction]

This new message is a counterpart of UM243 with only the destination, which is the most important parameter.

The part with the [direction] parameter is optional. If the detailed taxiRoute is unknown, at least a provision of the pushback direction is useful to pilots.

This message is not a key element of the message set (optional).

The direction parameter needs to be more precise if graphical.

Page 31

UPLINKS – Options


Justification

250DUE TO [airportElement] CONGESTION

OptionalTo be used in conjunction with UM0 UNABLE.

Not very useful operationally.251

DUE TO FLOW REGULATION

Optional

The following messages answer a specific graphical need, but should not require an answer from pilots, and even should not be presented as a textual CPDLC message.


Justification

258TAXI CLEARANCE: CHANGE IN PROGRESS

TAXI CLEARANCE : CHANGE IN PROGRESS

This UM is meant for controllers to alert pilots that the previous TAXI CPDLC clearances are invalidated (superseded by voice for short term change).

This message is more dedicated to the map and may be useless on DCDU. Further study should be performed to determine if CPDLC is thus appropriate. No answer should be required from pilots.

This message should have a higher priority characterization.

xxx RESUME OWN TAXITo be used following a use of voice (e.g. requiring the a/c to stop) if the previous datalink taxi clearance is still valid. No answer should be required from pilots.

Page 32

UPLINKS – Runway clearances

UM#

In EMMA2 AIF Std2 trialsRecommendation for normalisation of D-TAXI

Justification

242 CROSS [runwayInformation] CROSS [runwayInformation] Further study should be performed on the appropriateness of CPDLC runway clearances. It is recommended to study a procedure where runway clearances are provided through voice and the associated datalink messages (CPDLC?) would only be a graphical support.

These messages are a pre-requisite for an onboard safety net against runway incursions.

Several combinations may be envisioned, eg. BACKTRACK + LINE UP + AND MAINTAIN, TAXI TO...VIA... + BACKTRACK, CROSS + TAXI TO...

xxx AND MAINTAIN

xxx BACKTRACK [runwayinformation]

255 LINE-UP [runwayInformation] LINE-UP [runwayInformation]

256CLEARED FOR TAKE-OFF [runwayInformation]

CLEARED FOR TAKE-OFF [runwayInformation]

These messages answer a specific graphical need, but should not require an answer from pilots, and even should not be presented as a textual CPDLC message.

Page 33

UPLINKS – Traffic management


Justification

257BEHIND [aircraftFlightIdentification] [aircraftType]

BEHIND [aircraftFlightIdentification] [aircraftType]

Messages linked to traffic - should be further evaluated, especially regarding the a/c identifier issue.

[aircraftType] (ie A320, B777) is optional.

This message could be appended to taxi/revision clearance or pushback approval.

xxxGIVE WAY TO [aircraftFlightIdentification] [aircraftType]

Page 34

DOWNLINKS – Existing messages

DM#

In EMMA2 AIF Std2 trialsRecommendation for normalisation of D-TAXI

Justification

0 WILCO WILCOBasic PAM (Pilot Acknowledgement Messages)

UNABLE is scarcely used operationally.

1 UNABLE UNABLE

2 STANDBY STANDBY

3 ROGER ROGER

25[airportLocation] REQUEST [clearanceType]

[airportLocation] REQUEST [clearanceType]

clearanceType = Start-up, Pushback, Taxi, Departure.

Could possibly be used for Line-up, Take-off

Note: WG78 envisions to define a dedicated DM for departure request (DM118 REQUEST DEPARTURE CLEARANCE [departureClearanceRequestData]- TBC)

66DUE TO AIRCRAFT PERFORMANCE

DUE TO AIRCRAFT PERFORMANCE

67 Free Text Free Text

Page 35

DOWNLINKS – EMMA Messages

DM# In EMMA2 AIF Std2 trialsRecommendation for normalisation of D-TAXI

Justification

114 [airportLocation] [airportLocation]

[airportLocation] would be used optionally at Start-Up or Push-Back in conjunction with DM#25.

The position reporting at parking is essential to controllers.

115 DUE TO AIRCRAFT TYPE DUE TO AIRCRAFT TYPE For taxiway compatibility (weight, wing span)

118

FOR [runwayInformation]

ABLE INTERSECTION TAKE-OFF FROM [intersection]

FOR [runwayInformation]

ABLE INTERSECTION TAKE-OFF FROM [intersection]

Message to be further evaluated.

To be used optionally in conjunction with DM25 REQUEST TAXI CLEARANCE, to request a taxi for intersection take-off.

The message has two parts, which are optional: FOR [runwayInformation], and ABLE INTERSECTION TAKE-OFF FROM [intersection]

Feb 14, 2008 Airbus, Thales Air Systems, DSNA EMMA2 CPDLC trials in Toulouse EMMA2 outcomes from Toulouse trials.

Documents