1 / 7

D-TAXI Intersection Messages

D-TAXI Intersection Messages. Sept. 21, 2010 Vers . A. Intersection Departures. Problem: How can the flight crew tell the ground controller that they can accept a departure from a runway intersection instead of using the full length?

kyria
Download Presentation

D-TAXI Intersection Messages

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 Intersection Messages Sept. 21, 2010 Vers. A

  2. Intersection Departures • Problem: How can the flight crew tell the ground controller that they can accept a departure from a runway intersection instead of using the full length? • Current Solution: DM142 - ABLE INTERSECTION [intersection] RUNWAY [runway]

  3. Problems With DM142 • Problem #1: Controllers on a recent CSG teleconference didn’t like the phrase “Able Intersection” in the suggested text. This is not a phrase they would expect from a flight crew • Problem #2: Pilots are concerned that the message could be misused. It should only be used for departures.

  4. Potential Solution for DM 142 • The phrase “We Can Accept…” is used in other messages • DM 115, DM116, DM 117, DM 130, DM131, DM132, and DM154. • The word “Departure” could be added to the suggested message text. • Change: ABLE INTERSECTION [intersection] RUNWAY [runway] • To: WE CAN ACCEPT INTERSECTION [intersection] FOR DEPARTURE RUNWAY [runway]

  5. Issue with UM324 • Currently UM324 is: CAN YOU ACCEPT INTERSECTION [position information] FOR RUNWAY [runway] • The Response Attribute of A/N • Response required: AFFIRM, NEGATIVE, STANDBY, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY, ERROR, LOGICAL ACKNOWLEDGEMENT (only if required) • It would be good to have DM142 as a potential response. • Same issue as DM142, could be used for more than departure

  6. Solutions to UM324 • Change the response attribute to ‘Y’ • Any CPDLC downlink message, LOGICAL ACKNOWLEDGEMENT (only if required) • The flight crew could respond with; DM4 (Affirmative), DM5 (Negative), or with DM142 • DM142 could be used if the flight crew was offering an alternate intersection that would be better • Add the word “Departure” to the suggested text of the message • Change suggested text to: CAN YOU ACCEPT INTERSECTION [position information] FOR DEPARTURE RUNWAY [runway]

  7. Do We Need Another Message? • Scenario #1: Flight Crew has accepted an intersection departure, but then finds that they cannot use the intersection • i.e. weight, location on the airport • Scenario #2: Flight Crew has knowledge that ATC will ask if they can use an intersection and they want to tell ATC on initial contact they cannot use the intersection. • Solution: Another DM message • WE CANNOT ACCEPT INTERSECTION [intersection] FOR DEPARTURE RUNWAY [runway]

More Related