1 / 21

D-TAXI service review 78/214 Maastricht, June 9, 2009 Christian Bousmanne

D-TAXI service review 78/214 Maastricht, June 9, 2009 Christian Bousmanne. DUG planning. SUMMER 2009. Core of the D-TAXI OSED Operating method tables & diagrams Ors. Message set. Graphic chapter. END 2009. END 2009. Map reqts. example.

nitsa
Download Presentation

D-TAXI service review 78/214 Maastricht, June 9, 2009 Christian Bousmanne

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. D-TAXI service review 78/214 Maastricht, June 9, 2009 Christian Bousmanne

  2. DUG planning SUMMER 2009 • Core of the D-TAXI OSED • Operating method tables & diagrams • Ors Message set Graphic chapter END 2009 END 2009 Map reqts

  3. example « Cleared to holding point 25 R via taxiway C B A hold short of taxiway D expect taxi via taxiway K O“ TAXI[taxi route] + HOLD SHORT [ground position] + EXPECT TAXI [taxi route]

  4. Graphical chapter review • Synchronization mechanism of displayed routing with VOICE clearance • Related Message uplink TEXT and/or GRAPHIC • Related Message content. • Text • Graphic • Graphical data as “element” or “parameter”? • Precision for the airport map data base • Hot spot and virtual data concerns

  5. Initial cleared routing t 0 B TAXI VIA A A

  6. Initial cleared routing t 2 ATCO Turn left via taxiway Bravo PILOT Wilco B A

  7. Voice clearance received / graphic not yet updated t 10 B A

  8. Voice clearance received / graphic updated t 20 B Sync DL Message A

  9. Voice clearance received / graphic updated R t 30 B A

  10. Sync DL Message = 3 options possible VOICE GRAPHIC UPDATE (2) ROUTING VIA TWY B (3) Graphic routing data (1)

  11. “Crossing the reds”? (Voice/DL) 19R ATC voice “LINE UP RUNWAY 19 R”

  12. Where to put the Graphical data information • TAXI [taxi route] • HOLD SHORT [ ground position ] • EXPECT TAXI [taxi route] 4 elements ATC status needed, one single graphic element + [graphic taxi route] 3 elements ATC status not needed Graphic data embedded in msg TAXI [taxi route, + Graphic data] HOLD SHORT [ ground position +Graphic data ] EXPECT TAXI [taxi route +Graphic data]

  13. Selection of message intent • Graphic routing data ∑ (IDLIN , ATC status) ∑ (IDLIN ) )

  14. Graphical chapter review • Synchronization mechanism of displayed routing with VOICE clearance • Related Message uplink TEXT and/or GRAPHIC • Related Message content. • Text • Graphic • Graphical data as “element” or “parameter”? • “ATC status” • Content of a “routing data” • Precision for the airport map data base • Hot spot and virtual data concerns

  15. Routing DATA ∑ (IDLIN , ATC status) ∑ (IDLIN ) + TURN indication ?

  16. Construction Area Stand Guidance Line Flexible precision for alerts, RWY incursion & to minimize A/C data base needs Painted & virtual data List of needed elements to be confirmed Unique “IDLIN” necessary for each line OTHERS ??

  17. virtual’…s

  18. On (ground) airport map data base • List of required database elements confirmed • Virtual elements confirmed, even virtual rwy exit line, • Precision “Fine” is enough, • Airport reporting position needs to be very precise • HOT SPOTs & future wordings for “locations” • Catered for via the parameter “named point” now extended to 18 characters, in the ISPR.

  19. Thank you for your support Christian.Bousmanne@Eurocontrol.int

More Related