Update BNA and HOP Approach Control Boundaries #473
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dirtyformal
requested changes
Sep 24, 2025
|
Email recieved and contributer status added to list |
|
Woohoo! Merging! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates for both BNA and HOP boundaries due to BNA airspace expansion
Description
BNA airspace boundary expanded to the south, west and north. HOP boundary modified at the extreme southeast corner
Motivation and Context
This change is required due to real-world airspace and procedure changes. BNA now serves additional airports not included inside of the current boundary.
How to prove the effect of this PR?
New BNA Airspace Boundary:
Old BNA Airspace Boundary:
New HOP Boundary:
Old HOP Boundary:
New BNA and HOP Boundaries:
Checklist