Change request: Receiver of tag transfer becomes tag owner before assume

[Matisse VanWezer]

Hi

We've switched to silent handoffs a long time ago now. This means that a controller initiates a voice and tag handover to the next controller but that the receiver will only assume the track once the aircraft calls in on frequency. As a result, the receiving controller cannot make changes to the tag until the pilot switches and calls in. 

This can be annoying when you want to anticipate the call and set the tags (directs/CFLs/scratch pad/change STARs/runways/route amendments..) since you have to wait for them to call in before you can instruct them and make changes. Some of the time, you end up working the tag longer than call, extending the time before you can call the next aircraft.

Changing ownership on transfer would give the next controller more flexibility to make amendments whenever he has time. Co-ownership during transfer would hold the same benefits. (Which I think from a technical standpoint already somewhat exists (?) since a transferred tag can be assumed by both the initiator and receiver)

Those who do not use silent handoffs won't be affected as they immediately assume the tag and can already make those inputs before the pilot calls in. 

Regards

 

Edited September 27, 2022 at 09:04 AM by Matisse VanWezer

[Harry Sugden]

Interesting take. In the UK, we work by the mantra “Input as you speak. Read as you listen.”

Otherwise, if you forget to issue something that is already in the tag, then the tag might not reflect what is actually happening. Is that not a bit of a risk with this functionality?

[Andreas Fuchs]

I do like to pre-plan things as well and when accepting a new tag I cross-check whether the pilot seems to be doing what the tag-data says.

[Matisse VanWezer]

32 minutes ago, Harry Sugden said:

“Input as you speak. Read as you listen.”

That's what most of us do for almost all inputs but especially for those that take that extra time this mantra won't work either (as you'd still be making inputs while listening). Hence I'd like to plan ahead instead of lag behind. 

Of course, if implemented, anyone can still choose to only do the tag inputs when the aircraft has called in. But at least it's a choice and not a restriction anymore.

 

Another planning argument I forgot to mention is that the use of SEP tools to see if a given direct (when flying on route but also to resume own nav) is free of conflict isn't possible either as said direct must be set (which you can't do) for those tools to work. Being able to plan this ahead is safer and more efficient than doing on the fly when the pilot calls in or in a follow up call when you finally got it all figured out. 

Edited September 27, 2022 at 09:53 AM by Matisse VanWezer