Merge pull request #395 from llamavert/ybbn

YBBN Helicopter Operations
vatpac-technology · Dec 31, 2024 · d9952da · d9952da
2 parents 771d96e + 6917483
commit d9952da
Show file tree

Hide file tree

Showing 3 changed files with 110 additions and 3 deletions.
diff --git a/docs/aerodromes/classc/Brisbane.md b/docs/aerodromes/classc/Brisbane.md
@@ -112,15 +112,88 @@ Non-Jet aircraft, and aircraft that cannot accept a Procedural SID, shall be ass
     Non-Jet Aircraft planned via WACKO, assigned runway 01R, shall be assigned the BN (RADAR) SID.
 
 ## ATIS
-#### Operational Info
+### Operational Info
 When parallel runways are used for departures, the ATIS OPR INFO shall include:  
 `INDEPENDENT PARALLEL DEPARTURES IN PROGRESS`  
 When SODPROPS are in operation, the ATIS OPR INFO shall include:  
 `SIMULTANEOUS OPPOSITE DIRECTION PARALLEL RUNWAY OPERATIONS IN PROGRESS`
 
-#### Approach Types
+### Approach Types
 The ATIS shall always have `EXP INST APCH` as the approach type. Visual Approaches are permitted on request, as long as a separation standard exists between the aircraft and any aircraft arriving on the parallel runway during PROPS, or departing from the parallel runway during SODPROPS.
 
+## Helicopter Operations
+Brisbane has one helipad located on taxiway **F4**. Most rescue helicopters are based within the general aviation maintenance area and may operate from taxiway **H2**.
+
+ADC shall inform SMC of any inbound helicopters so that they may prevent other aircraft from taxiing on the HLS.
+
+!!! tip
+    Refer to [Maneuvering Area Responsibility](#maneuvering-area-responsibility) to determine which SMC or ADC position is responsible for managing helicopter arrivals and departures.
+
+### Waypoints
+In VMC, all helicopters shall be processed via two visual waypoints (outlined below) positioned north and south of the field. Where VMC does not exist, IFR helicopters will conform to fixed wing ops and be processed via the **BN (RADAR) SID** from an appropriate runway.
+
+
+| Direction of Flight  | Inbound/Outbound Tracking Point |
+| ------------------ | -------------- |
+| North      | BLHS   |
+| South      | MBHM   |
+| East      | MBHM   |
+| West      | BLHS   |
+
+### Departures
+Where a helicopter has not filed via the appropriate waypoint, they should be rerouted.
+
+!!! phraseology
+    **RSCU533:** "Brisbane Delivery, helicopter RSCU533, MEDEVAC, for YXHE, request clearance"  
+    **BN ACD:** "RSCU533, Brisbane Delivery, cleared to YXHE via amended BLHS, YXHE, climb A025, squawk 1256, departure frequency 124.7"  
+    **RSCU533:** "Cleared to YXHE via amended BLHS, YXHE, climb A025, squawk 1256, departures 124.7, RSCU533"
+
+Both taxiways **H2** and **F4** are inside the maneuvering area and treated like a runway, requiring a takeoff and landing clearance from BN ADC. Helicopters departing on other surfaces outside the maneuvering areas should be instructed to *"report airborne"*. 
+
+!!! phraseology
+    **RSCU533:** "Brisbane Tower, helicopter RSCU533, Taxiway H2 ready"  
+    **BN ADC:** "RSCU533, Brisbane Tower, Taxiway H2 cleared for takeoff"  
+    **RSCU533:** "Taxiway H2 cleared for takeoff, RSCU533"
+
+    **BN ADC:** "RSCU533, contact departures"  
+    **RSCU533:** "Departures, RSCU533"
+
+### Arrivals
+Helicopters arriving to YBBN during VMC shall be cleared by **BN TCU** via the appropriate inbound waypoint, with that waypoint issued as the clearance limit. TCU shall coordinate the arrival with ADC and transfer the aircraft approaching the clearance limit.
+
+ADC shall assess the current traffic situation and, if necessary, instruct the pilot to hold and/or maintain own separation with any arriving or departing aircraft, then clear them for a visual approach to their nominated landing site. 
+
+If holding is required prior to arrival, helicopters shall be instructed to hold at the following positions:
+
+| Inbound Via | Holding Position |
+| ----------- | ---------------- |
+| BLHS        | Brisbane Entertainment Centre *(3nm northwest of runway 01L/19R)* |
+| MBHM        | MBHM             |
+
+!!! phraseology
+    <span class="hotline">**TCU** -> **ADC**</span>: "North, helicopter X6G, inbound at A010, clearance limit BLHS"  
+    <span class="hotline">**ADC** -> **TCU**</span>: "X6G"  
+
+    **X6G**: "Brisbane Tower, helicopter X6G, for Taxiway F4"  
+    **BN ADC**: "X6G, Brisbane Tower, cancel clearance limit, track to and hold at the Brisbane Entertainment Centre, maintain A010"  
+    **X6G**: "Cancel clearance limit, track to and hold at the Brisbane Entertainment Centre, maintain A010, X6G"
+
+    **BN ADC**: "X6G, report sighting, and able to maintain own separation with, a Qantas 737, 4nm final runway 19R"  
+    **X6G**: "Traffic sighted, and we are able to maintain own separation. X6G"  
+    **BN ADC**: "X6G, cancel hold, pass behind the 737, maintain own separation, caution wake turbulence, cleared visual approach Taxiway F4"  
+    **X6G**: "Cancel hold, pass behind the 737, maintain own separation, cleared visual approach Taxiway F4, X6G"
+
+Remember to pass traffic information to both aircraft.
+
+!!! phraseology
+    **BN ADC**: "QFA1852, traffic is a helicopter, currently 3nm northwest of the field at A010, they'll pass behind you on approach to the F4 helipad and maintain own separation with you, runway 19R, cleared to land"
+
+Both taxiway **H2** and **F4** are inside the maneuvering area and treated like a runway, requiring a takeoff and landing clearance by BN ADC. Helicopters landing on other surfaces outside the maneuvering areas should be instructed to *"report on the ground"* so the controller knows when they are no longer active in their airspace.
+
+!!! phraseology
+    **BN ADC:** "X6G, Taxiway F4, cleared to land"  
+    **X6G:** "Taxiway F4, cleared to land, X6G"
+
 ## Coordination
 ### Auto Release
 'Next' coordination is **not** required to BN TCU for aircraft that are:

diff --git a/docs/terminal/brisbane.md b/docs/terminal/brisbane.md
@@ -95,6 +95,38 @@ These standard runway assignments may be modified strategically by the BAS or BF
 !!! phraseology
     **BAS:** “QFA660, Turn left heading 040, join final Runway 01L, from that heading Cleared Independent Visual Approach Runway 01L, not below 2400 until established on the PAPI”    
 
+## Helicopter Operations
+In VMC, helicopters inbound to or outbound from YBBN shall be processed via two visual waypoints (outlined below) positioned north and south of the field. Where VMC does not exist, IFR helicopters will conform to fixed wing ops.
+
+
+| Direction of Flight  | Inbound/Outbound Tracking Point |
+| ------------------ | -------------- |
+| North      | BLHS   |
+| South      | MBHM   |
+| East      | MBHM   |
+| West      | BLHS   |
+
+### Departures
+BN ADC will clear outbound helicopters via the [appropriate waypoint](#helicopter-operations) and transfer the aircraft to TCU. Where VMC does not exist, IFR helicopters will be assigned the **BN (RADAR) SID** and processed as per fixed wing ops.
+
+### Arrivals
+Helicopters arriving to YBBN during VMC shall be cleared by **BN TCU** via the appropriate [inbound waypoint](#helicopter-operations), with that waypoint issued as the clearance limit. TCU shall coordinate the arrival with ADC and transfer the aircraft approaching the clearance limit.
+
+!!! phraseology
+    **X6G**: "Brisbane Approach, helicopter X6G, 14nm north of Brisbane, A010, inbound, received Bravo, request clearance"  
+    **BN TCU**: "X6G, Brisbane Approach, remain outside Class C airspace, squawk 0445"  
+    **X6G**: "Remain OCTA, squawk 0445, X6G"  
+
+    <span class="hotline">**TCU** -> **ADC**</span>: "North, helicopter X6G, inbound at A010, clearance limit BLHS"  
+    <span class="hotline">**ADC** -> **TCU**</span>: "X6G"  
+
+    **BN TCU**: "X6G, identified, cleared to YBBN via BLHS, maintain A010, clearance limit BLHS"  
+    **X6G**: "Cleared to YBBN via BLHS, maintain A010, clearance limit BLHS, X6G"  
+
+    **BN TCU**: "X6G, contact Brisbane Tower, 120.5" 
+
+**BN ADC** will assess the traffic situation and clear the aircraft for a visual approach to their nominated landing site.
+
 ## Offline Towers
 ### AF ADC Offline
 Due to the low level of CTA (`A015`) in the AF CTR when **AF ADC** is offline, it is best practice to give airways clearance to aircraft at the holding point, to ensure departing aircraft can have uninterrupted climb.

diff --git a/includes/abbreviations.md b/includes/abbreviations.md
@@ -310,6 +310,8 @@
 *[CPDLC]: Controller-Pilot Datalink Communications
 *[LDA]: Landing Distance Available
 *[TORA]: Takeoff Run Available
+*[BLHS]: Bald Hills
+*[MBHM]: Manly Boat Harbour
 *[MARSA]: Military Authority Assumes Responsibility for Separation of Military Aircraft
 *[NOCOM]: Non-Continuous Communication
-*[AEWC]: Airborne Early Warning and Control
+*[AEWC]: Airborne Early Warning and Control