courtesy copy messages n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Courtesy Copy Messages PowerPoint Presentation
Download Presentation
Courtesy Copy Messages

Loading in 2 Seconds...

play fullscreen
1 / 6

Courtesy Copy Messages - PowerPoint PPT Presentation


  • 92 Views
  • Uploaded on

Courtesy Copy Messages. DCIT WG meetings 3/6/2012. Messages Initial Clearance Revised Clearances Acknowledgement Initial and Revised messages virtually identical Format allows for flexibility Format intended to be similar to existing (PDC) messages from TDLS. . Clearance .

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Courtesy Copy Messages' - jersey


Download Now 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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
courtesy copy messages

Courtesy Copy Messages

DCIT WG meetings

3/6/2012

slide2

Messages

    • Initial Clearance
    • Revised Clearances
    • Acknowledgement
  • Initial and Revised messages virtually identical
  • Format allows for flexibility
  • Format intended to be similar to existing (PDC) messages from TDLS.
clearance
Clearance

^AQU {IATA address TO}

. {IATA address FROM} {DDHHMM}

^B CCI <- new TEI

{Sequence number} COURTESY COPY – NOT AN ATC CLEARANCE

{Flight ID *A} {Beacon code field #20} {field #1}

{Equipment *B} P{Departure time *C}

{Computer Identifier *D} {field #19}

{Route Information *E} three copies of this field allowed

{Free Text *F} six copies of this field allowed

{Free Text Additional *G} additional fields allowed as needed

notes
Notes
  • A: Flight ID is not in the FANS message, should it be blank or derived from other DTAP information?
  • B: Equipment type is not in the FANS message, should it be blank or derived from other DTAP information?
  • C: Departure time is not in the FANS message, should it be blank or derived from other DTAP information?
  • D: Computer Identifier is not in the FANS message, should it be blank or derived from other DTAP information?
  • E: Route information consists of fields #2, #3, #4, #5, #6, #7, #8.
  • F: Free text consists of fields #10, #13, #14, 15, #16, #17, #18, #20, #21
  • G: Free text added consists of fields #18, #20, #21. This field includes all of the fields that are not in the PDC message today.
outstanding questions issues
Outstanding questions/issues
  • The message size is limited and likely will not support a clearance with 128 route elements.
  • It is not clear how RouteInformationAdditional is used in DCL. For now we assume that it is simply converted to text and included in the {free text}.
  • We assume that Special Instruction [freetext] will be included in the {free text} portion of the message.