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

YBAF Helicopter Procedures #420

Merged
merged 20 commits into from
Feb 15, 2025
Merged

Conversation

llamavert
Copy link
Contributor

@llamavert llamavert commented Dec 22, 2024

Summary

Adds helicopter procedures to YBAF, including detailed inbound/outbound and circuit operations.

Changes

Additions:

  • Helicopter procedures at YBAF
  • YBAF helicopter training areas diagram
  • Brisbane City helicopter scenic ops

Fixes:

  • Brisbane TCU page example typo

@llamavert
Copy link
Contributor Author

If anyone would like to make changes to the helicopter areas image I've attached the photoshop .psd file below;

ybaf-helicopter-areas.zip

@tylerthetiletiler tylerthetiletiler added the notify Send notification to Discord on merge label Dec 22, 2024
Copy link
Collaborator

@mattk04 mattk04 left a comment

Choose a reason for hiding this comment

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

Really great work here @llamavert, thanks for putting the effort in to get these procedures published. I've commited a few minor formatting changes and just have a few questions/comments with what you've got here, but should be easy to clarify. Thanks for your efforts

@llamavert llamavert requested a review from mattk04 December 28, 2024 04:49
@mattk04 mattk04 added the DO NOT MERGE This PR is not ready to be merged. Do not merge until approval from the Publications Manager. label Dec 30, 2024
@mattk04 mattk04 added Awaiting Changes Awaiting requested changes from the pull request author and removed DO NOT MERGE This PR is not ready to be merged. Do not merge until approval from the Publications Manager. labels Jan 21, 2025
Copy link
Collaborator

@mattk04 mattk04 left a comment

Choose a reason for hiding this comment

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

Just formalising the state of this PR.

Just need to determine what triggers the use of each helicopter training area so we can provide guidance to controllers on the most appropriate one to choose from. Also might be good to expand the ATIS section to show an example with the circuit direction specified (as per the notes in the description of each training area). @llamavert indicated that they were researching that, if necessary, we can try to source some LIs.

@llamavert
Copy link
Contributor Author

Apologies just getting back into this PR, few notes. Regarding the circuit area specified in the ATIS for each training area, that was sourced from the ERSA however I've never actually seen it be used in the ATIS. As it's always just stated which helicopter area is active. I wasn't able to find anything regarding which triggers what helicopter areas. However from what I can tell, say runways 04/22 were in use, clearly you can't use helicopter area alpha, so you'd have to operate within helicopter area charlie. However, when the two parallel runways are in use, you can use helicopter area alpha, which is used pretty much 90% of the time.

@mattk04
Copy link
Collaborator

mattk04 commented Feb 9, 2025

Apologies just getting back into this PR, few notes. Regarding the circuit area specified in the ATIS for each training area, that was sourced from the ERSA however I've never actually seen it be used in the ATIS. As it's always just stated which helicopter area is active. I wasn't able to find anything regarding which triggers what helicopter areas. However from what I can tell, say runways 04/22 were in use, clearly you can't use helicopter area alpha, so you'd have to operate within helicopter area charlie. However, when the two parallel runways are in use, you can use helicopter area alpha, which is used pretty much 90% of the time.

Ok no worries, I'll write something up today and see if we can get this merged.

@mattk04 mattk04 requested a review from a team as a code owner February 9, 2025 02:25
@mattk04 mattk04 self-requested a review February 9, 2025 02:25
@mattk04 mattk04 removed the Awaiting Changes Awaiting requested changes from the pull request author label Feb 9, 2025
mattk04
mattk04 previously approved these changes Feb 9, 2025
LeGiraffe
LeGiraffe previously approved these changes Feb 9, 2025
@llamavert llamavert dismissed stale reviews from LeGiraffe and mattk04 via cdefdbd February 9, 2025 03:26
@mattk04 mattk04 requested a review from LeGiraffe February 15, 2025 05:50
@tylerthetiletiler tylerthetiletiler merged commit c33aeff into vatpac-technology:main Feb 15, 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.

5 participants