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 15 commits into
base: main
Choose a base branch
from
Open

YWLM Procedures #403

wants to merge 15 commits into from

Conversation

ST6-Bravo
Copy link
Contributor

@ST6-Bravo ST6-Bravo commented Dec 14, 2024

Summary

Updated military SOPs for Williamtown.

Changes

Additions:

  • Military SIDs
  • Stereo gates

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
@tylerthetiletiler tylerthetiletiler added the notify Send notification to Discord on merge label Dec 22, 2024
@ST6-Bravo
Copy link
Contributor Author

@alphadelta332 Everything is done now

mattkelly4
mattkelly4 previously approved these changes Jan 6, 2025
@mattkelly4 mattkelly4 requested a review from a team January 6, 2025 07:11
@ST6-Bravo
Copy link
Contributor Author

@alphadelta332 Its done if you would like to review it?

@alphadelta332
Copy link
Collaborator

@alphadelta332 Its done if you would like to review it?

Hey mate, we're a few soldiers down at the moment, and just trying to find the time to get around to reviewing what's required. Expect a bit of delay due to RL commitments taking precedence. Thanks for your patience

@ST6-Bravo
Copy link
Contributor Author

@alphadelta332 Its done if you would like to review it?

Hey mate, we're a few soldiers down at the moment, and just trying to find the time to get around to reviewing what's required. Expect a bit of delay due to RL commitments taking precedence. Thanks for your patience

Yeah, no worries I get that, just making sure it wasnt forgotten about.

alphadelta332
alphadelta332 previously approved these changes Jan 16, 2025
Comment on lines 31 to 38
| Tracking Gate | Departure | Initial Constraint | Route |
| ----- | ---------| --------------- | ------------------------ |
| G1-G2 | PEPPER 1 | `A080` at ERVEV | ERVEV G1/G2 (Transition) |
| G3-G7 | CLASSIC 1| `F125` at G3-G7 |
| G9 | RADAR | `F125` at G9 |
| UKDIP | CLASSIC 1| `A090` at UKDIP |
| OLVEP | CLASSIC 1| `F130` at OLVEP |

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 looks like we're missing the rest of the route cells in the table. Also, is there any chance you might be able to source/create a diagram so our controllers can visualise the procedures?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The rest are radar transitions, is it possible to have the ad2 supp diagram?

Copy link
Collaborator

Choose a reason for hiding this comment

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

We've been creating our own diagrams to avoid copyright infringement with the AIP, I'm not sure if the RAAF have any rules, but our other military pages have had vatSys diagrams. I'm sure we can make one if necessary.

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 was looking through the YWLM FIHA AD2 but could only find the table at 2.10.5. Are you aware of any diagram or text which actually describes each procedure?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sorry, I mean in the terma.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Gotcha. Looks like they're actual SIDs rather than coded clearances, I'll push a commit this afternoon to update.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Sorry didn't manage to get this done but shall do pronto, then we can merge.

docs/aerodromes/classc/Williamtown.md Outdated Show resolved Hide resolved
@mattkelly4 mattkelly4 added the DO NOT MERGE This PR is not ready to be merged. Do not merge until approval from the Publications Manager. label Jan 19, 2025
@ST6-Bravo ST6-Bravo requested a review from mattkelly4 January 21, 2025 04:42

| Tracking Gate | Departure | Initial Constraint | Route |
| ----- | ---------| --------------- | ------------------------ |
| G1-G2 | PEPPER 1 | `A080` at ERVEV | ERVEV G1/G2 (Transition) |
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 looks like the PEPPER1 has instructions for gates 1-7, did you find any reference which limits its use to only gates 1 & 2?
image

Copy link
Collaborator

@mattkelly4 mattkelly4 Jan 21, 2025

Choose a reason for hiding this comment

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

Also I can see that OLVEP and UKDIP are the only RNAV waypoints used in the procedures, but from what I can see looking at the charts, it appears that they are tracking points are not gates themselves. Was there a list of gates you found?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Gates are in the ad2 supp, typically aircraft use the classic one to avoid the sawr when possible as such pepper is only seen for the gates around the sawr

Copy link
Collaborator

Choose a reason for hiding this comment

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

I've found this, but it doesn't reference OLVEP and UKDIP as gates. Did you find anything which says otherwise?

These are some very complicated procedures (from our civil perspective anyway), so I think we might proceed with the gates listed below and try to simplify the controller actions required to process these aircraft.

image

@mattkelly4 mattkelly4 added the Awaiting Changes Awaiting requested changes from the pull request author label Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Changes Awaiting requested changes from the pull request author DO NOT MERGE This PR is not ready to be merged. Do not merge until approval from the Publications Manager. notify Send notification to Discord on merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants