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

YBCG Overhaul #452

Merged
merged 16 commits into from
Feb 2, 2025
Merged

YBCG Overhaul #452

merged 16 commits into from
Feb 2, 2025

Conversation

llamavert
Copy link
Contributor

Summary

Addition of multiple new concepts to YBCG SOPs from real-world procedures

Changes

Additions:

  • Hospital Helipads, arrivals and departures
  • Coastal Low-Level Flights
  • VFR Inbound & Outbound Procedures
  • Western VFR Route

alphadelta332
alphadelta332 previously approved these changes Jan 27, 2025
@alphadelta332 alphadelta332 requested review from mattkelly4 and a team January 27, 2025 05:06
@alphadelta332 alphadelta332 added the notify Send notification to Discord on merge label Jan 27, 2025

!!! phraseology
**JCZ:** "Gold Coast Tower, JCZ, HASS, A015, inbound fullstop, request clearance"
**CG ADC:** "JCZ, Gold Coast Tower, cleared overwater northbound, not above A015, clearance limit CIS"
Copy link
Collaborator

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.

Copy link
Contributor Author

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.

Copy link
Collaborator

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?

Copy link
Contributor Author

@llamavert llamavert Jan 28, 2025

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

Copy link
Collaborator

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?

Copy link
Contributor Author

@llamavert llamavert Jan 31, 2025

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"

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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"

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

@mattkelly4
Copy link
Collaborator

@llamavert some really great work here, thanks for putting this together. I'm happy with everything, just want to clarify a few points (see comments).

docs/aerodromes/classc/Goldy.md Outdated Show resolved Hide resolved
docs/aerodromes/classc/Goldy.md Outdated Show resolved Hide resolved
docs/aerodromes/classc/Goldy.md Outdated Show resolved Hide resolved
docs/aerodromes/classc/Goldy.md Outdated Show resolved Hide resolved
docs/aerodromes/classc/Goldy.md Outdated Show resolved Hide resolved
docs/aerodromes/classc/Goldy.md Outdated Show resolved Hide resolved
docs/aerodromes/classc/Goldy.md Outdated Show resolved Hide resolved
docs/aerodromes/classc/Goldy.md Outdated Show resolved Hide resolved
docs/aerodromes/classc/Goldy.md Outdated Show resolved Hide resolved
@mattkelly4 mattkelly4 merged commit 3659482 into vatpac-technology:main Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
notify Send notification to Discord on merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants