1 / 35

EMMA2 outcomes from Toulouse trials

EMMA2 CPDLC trials in Toulouse. Airbus, Thales Air Systems, DSNA. EMMA2 outcomes from Toulouse trials. CPDLC Ground Clearance Function Procedures. Taxi out – global overview. Taxi out – nominal case (1/4). Voice contact on LFPG Delivery frequency. Notification (onboard initiated ) *.

maegan
Download Presentation

EMMA2 outcomes from Toulouse trials

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EMMA2 CPDLC trials in Toulouse Airbus, Thales Air Systems, DSNA EMMA2 outcomes from Toulouse trials

  2. CPDLC Ground Clearance Function Procedures

  3. Taxi out – global overview

  4. Taxi out – nominal case (1/4) Voice contact on LFPG Delivery frequency Notification (onboard initiated) * CPDLC establishment (ground initiated) * DELIVERY Departure Clearance request CONTACT LFPG GND 121.800 EXPECT ROUTING TO HOLDING POINT Z8 RWY 27R VIA TWY G N BD13 D Y11 RWY 27L K8 Z8 * Departure Clearance * * ROGER WILCO Pilot ATCO 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. Either through voice or through datalink ? If datalink, either CPDLC or A623 ? Pilot may append any foreseen constraints (if datalink: free text?specific message?) so that the EXPECT then provided may fulfil them EXPECT computed by ground system sent in response to Departure Cl. Request (controller may have to validate it)

  5. Taxi out – nominal case (2/4) Voice : DLH123, proceed by datalink * Voice : Ground 121.800 , DLH123 WILCO Voice : Proceeding by datalink , DLH123 GROUND #1 STAND D8 + REQUEST START-UP CLEARANCE + REQUEST PUSHBACK CLEARANCE * START-UP APPROVED & PUSHBACK APPROVED * Pilot ATCO Voice phraseology is only provided as an example Start-up and pushback requests may be sent separately with or without the current position. Start-up and pushback clearances are sent separately if requests had been sent separately

  6. Taxi out – nominal case (3/4) Voice : DLH123, proceed by datalink * CONTACT LFPG GND 121.600 * MONITOR LFPG TWR 119.250 * TAXI TO INTERSECTION N/NA2 VIA TWY G N Voice : Proceeding by datalink , DLH123 WILCO REQUEST TAXI WILCO WILCO Voice : Ground 121.600 , DLH123 WILCO TAXI TO RWY 27R VIA TWY N BD13 D Y11 HOLD SHORT RWY 27L * GROUND #1 GROUND #2 ATCO Pilot Transfer to Ground#2 frequency when near to N/NA2 Voice phraseology is only provided as an example 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

  7. Taxi out – nominal case (4/4) Voice: cleared for take-off runway 27 left, DLH 123* Voice: crossing runway 27 left and maintaining holding point K8, DLH123* Voice: lining up runway 27 left and waiting, DLH123 Voice: DLH123, cross runway 27 leftand 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: 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 * WILCO * TOWER Voice remains for runway clearances. The means through which the datalink information is sent is TBD. TAXI TO HOLDING POINT Z8 RWY 27R VIA TWY K8 Z8 * 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 * Pilot ATCO Voice 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) Only voice read-back required (no acknowledgment of the datalink information)

  8. Taxi in – global overview

  9. Taxi in - Nominal case with APP, TWR & GND equipped with CPDLC (1/3) RWY exit * ATIS * ATIS request ROGER EXPECT ROUTING TO STAND D8 VIA TWY V1 S2 RWY 26R S2 W2 N E GE2 G * EN ROUTE-APPROACH WILCO CONTACT LFPG TWR 119.25 * Pilot ATCO Either through voice or through datalink ? CPLDC already established with APP EXPECT computed from RWY exit, if available, otherwise “standard” routing (TBC) RWY exit data provided from ATC via TBD ground forwarding between Approach and Ground * 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. Transfer of CPDLC connexion between APP and ground system * (seamless transfer for the crew – no “manual” notification required)

  10. Taxi in - Nonimal case with APP, TWR & GND equipped with CPDLC (2/3) TOWER Voice: crossing runway 26 right and maintaining holding point S2, DLH123 * CONTACT LFPG GND 121.8 Voice: DLH123, wind 270 12 knots,runway26 left cleared to land. Report runway vacated or in case of missed approach. Voice: DLH123, cross runway 26 rightand maintain holding point S2 + datalink information confirming the cross clearance for moving map display purpose only * Voice: DLH123, hold short of runway 26 right on taxiway S2. Voice : Tower 119.25 , DLH123 Voice : Runway 26 left, cleared to land, DLH123 Voice : holding short of 26 right, on taxiway S2, DLH123 WILCO * Voice : Runway 26 left vacated on taxiway V1, DLH123 Pilot ATCO Voice 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) Transfer to Ground frequency

  11. Taxi in - Nonimal case with APP, TWR & GND equipped with CPDLC (3/3) GROUND TAXI TO STAND D8 VIA TWY S2 W2 N E GE2 G * Voice : DLH123, proceed by datalink * WILCO Voice : Ground 121.8 , DLH123 Voice : Proceeding by datalink , DLH123 ATCO Pilot Voice phraseology is only provided as an example The taxi clearance after landing may be provided without pilot request

  12. Expect Routing information use

  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. • taxiRoute] [taxiRouteClearance] Expected final destination Start of taxi Entry in an area depending on a different controller

  14. EXPECT ROUTING use (2/2) Departure Clearance request EXPECT ROUTING TO HOLDING POINT Z8 RWY 27R VIA TWY G N BD13 D Y11 RWY 27L K8 Z8 Departure Clearance ROGER • 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 ATCO Either through voice or through datalink ?

  15. Taxi clearance use

  16. TAXI CLEARANCE use (UL#241) – 1 / 4 A / Case of runway crossing, final destination known Start of taxi HP of RWY to cross Final destination 1st message Taxi To 1st message Taxi To 2nd message Taxi To 2nd message Taxi To TAXI TO [airportElement] TAXI TO [airportElement] VIA [taxiRoute] VIA [taxiRoute] HOLD SHORT OF [airportElement] (the end of clearance point corresponds to a holding point) [taxiRouteClearance] [taxiRouteClearance] 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..

  17. TAXI CLEARANCE use (UL#241) – 2 / 4 TAXI TO RWY 27R VIA TWY N BD13 D Y11 HOLD SHORT OF RWY 27L WILCO WILCO TAXI TO HOLDING POINT Z8 RWY 27R VIA TWY K8 Z8 A / Case of runway crossing, final destination known Pilot 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)

  18. TAXI CLEARANCE use (UL#241) – 3 / 4 B / Case of final destination unknown, ground control segmentation Final destination Start of taxi Ground control limit point 1st message Taxi To 1st message Taxi To 2nd message Taxi To 2nd message Taxi To TAXI TO [airportElement] TAXI TO [airportElement] VIA [taxiRoute] VIA [taxiRoute] [taxiRouteClearance] [taxiRouteClearance] 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.

  19. TAXI CLEARANCE use (UL#241) – 4 / 4 TAXI TO INTERSECTION N-NA2 VIA TWY G N CONTACT LFPG GND 121.8 Voice : DLH123, proceed by datalink WILCO WILCO WILCO Voice : Ground 121.8 , DLH123 Voice : Proceeding by datalink , DLH123 TAXI TO HOLDING POINT Y13 RWY 27L VIA N B BQ2 Y13 GROUND#2 B / Case of final destination unknown, ground control segmentation Pilot ATCO GROUND#1

  20. Revise taxi clearance use

  21. REVISE TAXI CLEARANCE use (UL#244) – 1 / 2 TAXI TO [airportElement] VIA [taxiRoute] HOLD SHORT OF [airportElement] [taxiRouteClearance] 1st message : 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. 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. Start of taxi End of taxi clearance point Current a/c position

  22. REVISE TAXI CLEARANCE use (UL#244) – 2 / 2 TAXI TO HOLDING POINT Y13 RWY 27L VIA N B BQ2 Y13 GROUND WILCO WILCO REVISE TAXI TO HOLDING POINT Y11 RWY 27L VIA B BD20 Y11 Pilot ATCO Long Term change in the cleared taxi route => revision only managed by datalink

  23. Mixed mode communication

  24. MIXED MODE COMMUNICATION (2/2) TAXI TO HOLDING POINT Y11 RWY 27L VIA N BD13 D Y11 GROUND WILCO WILCO Voice : Taxiing holding point Y11 runway 27 left via taxiway B BD20 Y11, DLH123 REVISE TAXI TO HOLDING POINT Y11 RWY 27L VIA B BD20 Y11 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) • Example : ATCO Pilot 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

  25. CPDLC Ground Clearance Messages Recommendations

  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:

  27. UPLINKS – Existing messages

  28. UPLINKS – Basics

  29. UPLINKS – Clearance revisions

  30. UPLINKS – EXPECT ROUTING

  31. UPLINKS – Options 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.

  32. UPLINKS – Runway clearances 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.

  33. UPLINKS – Traffic management

  34. DOWNLINKS – Existing messages

  35. DOWNLINKS – EMMA Messages

More Related