-
Notifications
You must be signed in to change notification settings - Fork 20
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
YBBN Helicopter Operations #395
base: main
Are you sure you want to change the base?
Conversation
@llamavert this looks like great work, thanks so much for putting it together! Edit: Scratch that, looks like we haven't pushed that update yet, where it is is good for now. |
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.
Some really great work here, just a few minor wording changes.
We need to work out how the helicopter procedures will fit in with the existing airspace structure, either by assigning jurisdiction of the CTR to ADC so they can manage it themselves, or by setting up coordination rules so that the TMA can maintain ownership but use visual separation standards maintained by ADC.
|
||
#### Departures | ||
|
||
Refer to [Maneuvering Area Responsibility](#maneuvering-area-responsibility) to determine which SMC or ADC position (when non-standard positions are online) is responsible for managing helicopter arrivals and departures. |
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.
We'll need to decide which ADC is responsible for each part of the aerodrome, since ADC doesn't own any airspace by default. This might need to be coordinated with the TMA or we might need to give ADC some airspace to manage it themselves. @alphadelta332 thoughts?
!!! example | ||
**RSCU533:** "Brisbane Tower, helicopter RSCU533" | ||
**BN ADC:** "RSCU533, Brisbane Tower, cleared visual approach H2" | ||
**RSCU533:** "Cleared visual approach H2, RSCU533" |
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.
We'll need to sort out the coordination required if ADC is going to clear the aircraft for a visual approach. Might be easier to give BN ADC ownership of the CTR
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.
Not sure if it's worth mentioning, but IRL ADC (120.5) often clears aircraft landing on H2 for the visual approach, and pretty sure ADC-N (118.0) clear aircraft for the visual approach F4 HLS.
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 cool, I guess that makes sense based on their likely inbound direction.
**BN ADC:** "RSCU533, Brisbane Tower, cleared visual approach H2" | ||
**RSCU533:** "Cleared visual approach H2, RSCU533" | ||
|
||
During times of peak fixed wing traffic, instruct helicopters to orbit in present position or overhead the VFR waypoint until advised, and maintain own separation on approach to the helipad. |
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.
Are the heli waypoints separated from fixed wing ops? If so, we might suggest that as a course of action exclusively, rather than present position.
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.
The heli waypoints are separated from fixed wing ops, the actual suburb / waypoint of Bald Hills is 6nm north of 01L/19R. I only added the present position call in case the helis are pasted Bald Hills are over some of the closer suburbs. But from what i've heard IRL, Bald Hills doesn't necessarily act as a clearance limit, just an inbound reporting point. However I may be wrong and it could be important that we mention it similar to how Sydney's coded arrivals work with holding at the 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.
Ah right, that's good then. There's also a likelihood that these aircraft will enter the CTR directly from class G. I suspect we'll end up going down the line of TMA clearing them to say A010V and issuing a clearance limit of the waypoint, then contacting TWR for visual approach clearance (who will instruct them to remain clear of any fixed wing traffic if necessary). If the aircraft is going Class G->CTR, they will likely be told to remain OCTA until that takes place. Hold tight for now and we'll see whether we want to redo the BN CTR jurisdiction
Co-authored-by: Matt Kelly <[email protected]>
Co-authored-by: Matt Kelly <[email protected]>
Co-authored-by: Matt Kelly <[email protected]>
Co-authored-by: Matt Kelly <[email protected]>
Co-authored-by: Matt Kelly <[email protected]>
Co-authored-by: Matt Kelly <[email protected]>
Co-authored-by: Matt Kelly <[email protected]>
docs/aerodromes/classc/Brisbane.md
Outdated
Traffic information must be issued to both aircraft. | ||
|
||
!!! example | ||
**BN ADC:** "UTY7241 traffic is a rescue helicopter north of the field overhead Bald Hills, they will maintain own separation and pass behind you on approach, runway 01L, cleared to land" |
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.
Runway 01L
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.
Fixed
Summary
Apologies if the PR has any issues, not used github for a while.
Thanks,
Charlie 1713821