Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle same callsign, new flightplan #4

Open
AndyTWF opened this issue Jan 15, 2019 · 2 comments
Open

Handle same callsign, new flightplan #4

AndyTWF opened this issue Jan 15, 2019 · 2 comments
Labels
type: bug Something isn't working

Comments

@AndyTWF
Copy link
Contributor

AndyTWF commented Jan 15, 2019

  • Aircraft stays connected, but files a new flightplan
  • These aircraft should be force assigned a new squawk
@AndyTWF AndyTWF added the type: bug Something isn't working label Jan 15, 2019
@hazzas-99
Copy link
Contributor

I will need to check for sure, but I also believe that even with a change of callsign and flightplan, if someone logs off and on again in a short amount of time it sometimes leaves them with the same squawk assignment.

@hazzas-99
Copy link
Contributor

@AndyTWF just to say, I think this is still the case. Aircraft flies into EGNX as ANDY123 with squawk 7431. They disconnect, refile a new flightplan under the callsign GHAZA but forget to reset their squawk to 2000 before connecting. Me (as a controller using Mode C, in case that makes a difference) assigns them 7431 in their next clearance as it hasn't reassigned it!

Is that because the allocation method doesn't see there being a problem as long as ANDY123 has disconnected, since the squawk is effectively now available?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants