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

Update ZME Approach Controls #353

Merged
merged 9 commits into from
Jan 29, 2024
Merged

Update ZME Approach Controls #353

merged 9 commits into from
Jan 29, 2024

Conversation

CJP1021
Copy link
Contributor

@CJP1021 CJP1021 commented Jan 25, 2024

Update LIT, JAN, FSM, CBM, HOP and NMM approach control boundaries and the FSM recognized prefixes.

Description

These changes include updating several approach control boundaries to include notable airspace shelf areas and corrections. FSM position prefixes modified to coincide with vNAS network position callsign changes.

Motivation and Context

The original data pulled from the ZME sector file into the Project did not contain the airspace fidelity that the ARTCC currently uses. ZME decided it was in the best interest of the pilots using the resource and the controller providing service to show the greatest extent of the approach control airspace. Additionally, the CBM and NMM approach control boundary used invalid boundary data.

How to prove the effect of this PR?

CBM:
CBM RAPCON Viewer
CBM RAPCON ERAM

FSM:
FSM TRACON Viewer
FSM TRACON ERAM

HOP:
HOP ARAC Viewer
HOP ARAC ERAM

JAN:
JAN TRACON Viewer
JAN TRACON ERAM

LIT:
LIT TRACON Viewer
JAN TRACON ERAM

NMM:
NMM RATCF Viewer
NMM ERAM

Additional info

Is this a breaking change?

  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

  • My change or addition follow the formatting standard of the project.
  • I am on the list of approved contributors. (ZME FE pending approval requested 10/2023).

@kmoberg kmoberg merged commit 82b7645 into vatsimnetwork:main Jan 29, 2024
1 check passed
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

Successfully merging this pull request may close these issues.

2 participants