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

FSD connection to assign squawks at uncontrolled airfields #1583

Open
luke11brown opened this issue May 8, 2024 · 1 comment
Open

FSD connection to assign squawks at uncontrolled airfields #1583

luke11brown opened this issue May 8, 2024 · 1 comment

Comments

@luke11brown
Copy link

luke11brown commented May 8, 2024

Maybe outside the scope of this project, but I'm asking anyway, because why not.

vNAS provides U.S. departures at uncontrolled airfields with a squawk code before departure, so that when a controller comes online, everyone is already on a discrete squawk.

Suggest all IFR flights are given the same in the UK.

Even better:
API to check if aircraft is on Hoppie, if yes, send squawk allocation by Hoppie. If no confirmation reply within 5 minutes, revert to message via FSD.

@AndyTWF
Copy link
Contributor

AndyTWF commented May 8, 2024

In principle it sounds reasonable! The problem with FSD is that it's a closely guarded secret and I don't think I'm one of the chosen-few!

However, doing this via Hoppie is very possible - as we do with stand assignments, in the manner you suggest.

The only caveat is that without access to FSD, we won't be able to have it preset in EuroScope when a controller connects - they'll have to assume the aircraft via one of the lists, which will then cause the plugin to go the backend and fetch the pre-assigned squawk. At the very least, this'll remove a step: you won't have to tell the aircraft the squawk on frequency, but your ES will still need to do the assignment process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants