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

YWLM Procedures #403

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open

YWLM Procedures #403

wants to merge 7 commits into from

Conversation

ST6-Bravo
Copy link
Contributor

Summary

Updated Military SOPs for Williamtown, ready for review.

Changes

Additions:
Added Military SIDs and other procedures.

Initial Procedures
Added Military SIDS and other Procedures
Dont know why pearce md is in here
@mattkelly4
Copy link
Collaborator

Thanks @ST6-Bravo

Looks like this PR will delete the pearce.md file, are you able to revert the commits which reference that file?

@ST6-Bravo
Copy link
Contributor Author

Thanks @ST6-Bravo

Looks like this PR will delete the pearce.md file, are you able to revert the commits which reference that file?

Does that fix it?

@mattkelly4
Copy link
Collaborator

Thanks @ST6-Bravo
Looks like this PR will delete the pearce.md file, are you able to revert the commits which reference that file?

Does that fix it?

That's added the file back in, it's just put your changes from your YPEA PR in there too. I think if you also revert the first commit, it should remove it from the equation

This reverts commit 748f56e.
@ST6-Bravo
Copy link
Contributor Author

Thanks @ST6-Bravo
Looks like this PR will delete the pearce.md file, are you able to revert the commits which reference that file?

Does that fix it?

That's added the file back in, it's just put your changes from your YPEA PR in there too. I think if you also revert the first commit, it should remove it from the equation

Yep that fixed it

Wrong Callsign
Comment on lines 57 to 69
WLM Eastern Airspace
G1 029/25
G2 050/25
G3 068/25 (Lighting Corrider Entry)
G4 088/25
G5 105/25
G6 125/25
G7 135/25
G9 007/25
WLM Western Airspace
UKDIP 311/25 (Thunder Corridor Entry)
SAWR (Salt Ash Weapons Range)
OLVEP 033/10
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm assuming that G1 029/25 means Gate 1 which is bearing 029 at 25nm? Is there any chance we could get a diagram showing these positions?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, there is one in the ad2 sup, that I could modify into vatsys.


!!! example
WGTL21 plans to enter M550 via Gate 4 for Military Training.
**WLM ADC**: "WGTL21, cleared to YWLM via Gate 4, flight planned route. Runway 12, Classic 1 Departure. Climb to `F125`. Squawk 5001, Departure Frequency 133.300"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is it likely that aircraft would file Gate 4 in their flight plan, or is it an ATC responsibility to amend their flight plan via the most appropriate gate?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Typically, we file M550 and assume ATC gives us Gate 4.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I put in a note saying Gate 4 is the most common if that helps @mattkelly4

Copy link
Collaborator

Choose a reason for hiding this comment

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

In that case, we'll need guidance for controllers to be able to make these sorts of decisions. We have to assume the controller reading this content has no knowledge of the local operations (because they likely don't)

Comment on lines +40 to +41
ACFT Departing RWY 12 for G3-7 are required to avoid SAWR on the Classic 1.
ACFT Departing on Classic 1 will be issued a direction of turn during take off clearance, preferablly to the south in order not to impede on the SAWR boundries on the departure.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is there any guidance on how these aircraft should track to avoid the weapons range?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Typically either climb quickly up to F130 or depart to the south.

Comment on lines +72 to +75
<figure markdown>
![WLM Gates](){ width="700" }
<figcaption>WLM Gates</figcaption>
</figure>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Just seen this, looks like this <figure> doesn't reference an image

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Havent finished it yet, just a reminder that I need to put a diagram in

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mattkelly4 Anychance you can make the diagram in vatsys? I dont know how to get the restriced airspace to show

Copy link
Collaborator

Choose a reason for hiding this comment

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

@ST6-Bravo I won't have a chance for a while unfortunately but if you want to give it a crack, use the Restricted Areas window to find the PRD, then set the activation time from 0000 to 2400 and hit apply. It'll appear on the map
image

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will give it a crack then

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Just dont know how to get the fancy text like in the tindal one to appear, guessing @alphadelta332 would know?

@tylerthetiletiler tylerthetiletiler added the notify Send notification to Discord on merge label Dec 22, 2024
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.

3 participants