-
Notifications
You must be signed in to change notification settings - Fork 23
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
YBCG Overhaul #452
Merged
Merged
YBCG Overhaul #452
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
693e454
init
llamavert ff7b799
more stuff
llamavert bc8038a
local callsign change
llamavert 9d27eae
touch ups
alphadelta332 c8f436e
typo fix
llamavert 6bbc8a9
Update docs/aerodromes/classc/Goldy.md
alphadelta332 b35a113
Update docs/aerodromes/classc/Goldy.md
alphadelta332 db6a608
Amend VFR procedures
mattkelly4 6eadd67
Update abbreviations.md
mattkelly4 0053d7a
Update docs/aerodromes/classc/Goldy.md
alphadelta332 ec01cef
Update docs/aerodromes/classc/Goldy.md
alphadelta332 eb65a98
Update docs/aerodromes/classc/Goldy.md
alphadelta332 52fce05
Update docs/aerodromes/classc/Goldy.md
alphadelta332 915cb2f
Update docs/aerodromes/classc/Goldy.md
alphadelta332 7c4d95f
Update docs/aerodromes/classc/Goldy.md
alphadelta332 1dd1ded
Update docs/aerodromes/classc/Goldy.md
alphadelta332 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does CIS provide any procedural separation with SIDs/STARs/other traffic by chance? Or is it just something you hear being used a lot? Would be good to include some information about why to issue the clearance limit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is pretty much used every time for arrivals northbound over water, it's location allows tower to issue holds if jets are inbound while not infringing on any SIDs or STARs at any point. It's mainly used for when runway 14 is in use as most of the time if it isn't busy and runway 32 is in use, tower will just clear aircraft @ HASS for the visual approach.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok great, thanks. Also, I'm assuming VFR departures normally just depart a leg of the circuit into class G?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, mostly tracking south to the training area into class G
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@llamavert is an explicit airways clearance given (cleared to XXXX, not above A015) for VFR departures into class G, or is it just a takeoff clearance after reporting ready for an upwind departure, etc?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For VFR departures into Class G yes I'm pretty sure that an explicit airways clearance is given, however for stuff like parachuting and training area flights from memory it's something along the lines of "Cleared standard drops, squawk 1234" likewise for VFR departures into Class G to the training area "Cleared to the training area, squawk 1234"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah for stuff like PJE ops, its usually associated with a letter of agreement between the PJE company and ATC, that may involve a coded clearance that implies a clearance to operate in a certain area, certain radius, certain levels, etc etc. Obviously something we won't be simulating online