zlsa / atc

https://openscope.co/
342 stars 107 forks source link

Parallel landings and takeoffs #699

Closed kaitsu71 closed 7 years ago

kaitsu71 commented 7 years ago

Would parallel landings and takeoffs be possible to implement without separation penalty? http://atcradarsim.com/parallel-landings-takeoffs-at-sfo/

erikquinn commented 7 years ago

For sure! The only thing that's tough is how we deal with differentiating. For example:

So it's hard to achieve all of the below at the same time:

To solve it, we could add yet another property to the airport files I guess, specifying whether or not they are authorized for simultaneous independent parallel approaches, simultaneous dependent parallel approaches, or neither. I just didn't think we were really there yet in terms of dealing in those sorts of details personally.

I will admit, it would be nice to have when you're working at some of these airports with triple parallels... running staggers all day long is a wonderful challenge, but not entirely real-world accurate...

erikquinn commented 7 years ago

Anybody else want to weigh in on this?

n8rzz commented 7 years ago

TL;DR totally possible, but it will take some work.

To solve it, we could add yet another property to the airport files I guess, specifying whether or not they are authorized for simultaneous independent parallel approaches, simultaneous dependent parallel approaches, or neither. I just didn't think we were really there yet in terms of dealing in those sorts of details personally.

I think you'd have a hard time doing this without adding a new property. But, once it's there, I'd say that it would be very possible to handle those different rulesets. This would require:

erikquinn commented 7 years ago

The ATC repository is being migrated to it's new home at https://github.com/openscope/openscope, and thus, all issues are being closed. If this is still an issue with the latest version of the sim (accessible at http://www.openscope.co), or is a feature you still think we are lacking, please reopen the issue at the new repo.

Please note that the vast majority of these issues have been copied to the new repository, or else are covered by other issues created there. See the below screenshot for what it looks like when your issue is known in the new repo:

image

Thank you!

Closing this issue.