diff --git a/docs/aerodromes/classc/Oakey.md b/docs/aerodromes/classc/Oakey.md
index 5e53304c0..c7f92aa88 100644
--- a/docs/aerodromes/classc/Oakey.md
+++ b/docs/aerodromes/classc/Oakey.md
@@ -14,7 +14,132 @@
| **Oakey ATIS** | | **124.300** | **YBOK_ATIS** |
## Airspace
-OK ADC owns the airspace within 5 DME of the OK VOR from `SFC` to `A025`. This airspace is designed to facilitate circuit traffic.
+OK ADC owns the airspace within 5 DME of the OK VOR from `SFC` to `A030`. This airspace is designed to facilitate circuit traffic.
+
+
+{ width="600" }
+ YBOK ADC Airspace
+
+
+## Manoeuvring Area
+
+### Manoeuvring Area Responsibility
+
+
+{ width="600" }
+ Manoeuvring Area Responsibility
+
+
+### Taxiway Bravo
+
+Four helipads are available on Taxiway Bravo from east to west, they are named Pad 1, Pad 2, Pad 3 and Pad 4. Taxiway Bravo may be used for helicopter arrivals and departures in any direction as specified by ATC. These pads are inside the manoeuvring area and treated like a runway, requiring a takeoff and landing clearance from OK ADC.
+
+Aircraft taxiing outbound from the RSAF and Military Aprons shall be instructed to hold short of the most appropriate taxiway when necessary, to provide separation with helicopters operating on Taxiway Bravo.
+
+
+{ width="600" }
+ Taxiway Bravo
+
+
+### Lanes
+
+Three helicopter lanes are located immediately north of Runway 09/27, aligned in the 09/27 cardinal direction. Lanes 1 and 3 are sealed pavement, while Lane 2 is grass. Each lane may only be occupied by one aircraft at a time. These lanes are inside the manoeuvring area and treated like a runway, requiring a takeoff and landing clearance from OK ADC.
+
+Lanes may be used for circuits and low-level operations. Aircraft cleared to land or enter a lane may conduct operations within that lane. Lane operations permit hover not above `A003` within the respective lane.
+
+
+{ width="600" }
+ YBOK Lanes
+
+
+## Local Procedures
+
+### Oakey Flying Training Area
+
+#### Flying Training Areas
+
+R654A, B, C and D are divided into the Western, North West and North East FTAs, these areas overlay the LFAs.
+
+
+{ width="600" }
+ Flying Training Areas
+
+
+#### Low Flying Areas
+
+There are eight LFAs within the OFTA, LFAs are the primary location for military helicopters conducting low level operations. LFAs are numbered 1-8 with the prefix L, pronounced as, "LIMA (number)".
+
+#### SAAFRs
+
+SAAFRs provide efficient movement through the OFTA to specific LFAs during periods of increased traffic. They are defined as 2nm wide, and are named "X-Ray", "Yankee" and "Zulu".
+
+#### Transit Areas
+
+Three transit areas, named "Whiskey" (western), "Charlie" (central) and "Echo" (eastern) are located between the Oakey CTR and inner boundaries of their respective LFAs. Transit Areas exist to provide flexibility in routing when leaving or enter Oakey CTR.
+
+!!! tip
+ Detailed images depicting LFAs, SAAFRs and Transit Areas are available on the [Oakey AD2 SUP](https://ais-af.airforce.gov.au/australian-aip)
+
+## Departure and Arrival Procedures
+
+### Departures
+
+By default, transit to LFAs will **not** be achieved through the use of SAAFRs and Transit Areas, direct tracking to the requested LFA shall always be issued.
+
+!!! phraseology
+ **FRTL21:** "Oakey Delivery, helicopter FRTL21, for Lima 1, request clearance"
+ **OK ACD:** "FRTL21, Oakey Delivery, cleared Lima 1 direct, not above A030, squawk 7264"
+ **FRTL21:** "Cleared Lima 1 direct, not above A030, squawk 7264, FRTL21"
+
+
+Aircraft requesting clearance to LFAs through a specific SAAFR or Transit Area should be cleared as requested.
+
+Not all SAAFRs and Transit Areas provide access to every LFA, each SAAFR and Transit Area connects to various LFAs. Aircraft should be cleared as requested, however if the requested SAAFR or Transit Area does not connect to the intended LFA, the aircraft must be recleared via the most appropriate alternative.
+
+!!! example
+ Aircraft requesting clearance to Lima 4 via Yankee, shall be cleared via X-Ray, as Yankee does not connect to Lima 4.
+
+=== "SAAFRs"
+ | Name | Connected LFAs |
+ | ---- | ---- |
+ | X-Ray | Lima 1, 3, 4, 5, 6 |
+ | Yankee | Lima 1, 5, 6, 7, 8 |
+ | Zulu | Lima 8, 7 |
+
+=== "Transit Areas"
+ | Name | Connected LFAs |
+ | ---- | ---- |
+ | Whiskey | Lima 2, 3, 4 |
+ | Charlie | Lima 1 |
+ | Echo | Lima 8 |
+
+!!! phraseology
+ **RSCU904:** "Oakey Delivery, helicopter RSCU904, for Lima 2, via Whiskey, request clearance"
+ **OK ACD:** "RSCU904, Oakey Delivery, cleared Lima 2, via Whiskey, not above A030, squawk 7314"
+ **RSCU904:** "Cleared Lima 2, via Whiskey, not above A030, squawk 7314, RSCU904"
+
+Aircraft requesting clearance for the FTAs, shall be cleared not above `A030`.
+
+!!! phraseology
+ **CYCP90:** "Oakey Delivery, helicopter CYCP90, for the northeast training area, request clearance"
+ **OK ACD:** "CYCP90, Oakey Delivery, cleared northeast training area, not above A030, squawk 7324"
+ **CYCP90:** "Cleared northeast training area, not above A030, squawk 7324, CYCP90"
+
+Aircraft will depart the CIRA visually and track direct to their LFA, or the requested outbound SAAFRs / Transit Area as cleared.
+
+!!! phraseology
+ **OK ADC:** "FRTL21, make right turn, cleared for takeoff"
+ **FRTL21:** "Make right turn, cleared for takeoff, FRTL21"
+
+### Arrivals
+
+OK TCU will clear inbound aircraft to YBOK direct, not above `A030`. OK TCU will transfer the aircraft to ADC approaching the CTR boundary. Instruct the aircraft to join the circuit for the applicable duty runway or lane and clear them for a visual approach (traffic permitting).
+
+!!! phraseology
+ **KNGT31:** "Oakey Tower, helicopter KNGT31, A030, request Lane 3"
+ **OK ADC:** "JUNO76, Oakey Tower, join base Lane 3, cleared visual approach"
+ **KNGT31:** "Join base Lane 3, cleared visual approach, KNGT31"
+
## Runway Modes
### Circuits
@@ -42,7 +167,15 @@ The Standard Assignable level from **OK ADC** to **OK TCU** is:
| Aircraft | Level |
| -------- | ----- |
-| All | The lower of `F120` and `RFL` |
+| Fixed-wing | The lower of `F120` and `RFL` |
+| Rotary-wing | The lower of `A030` and `RFL` |
+
+### Departures Controller
+When a TCU controller is online, aircraft shall be issued with a departure frequency during their airways clearance in accordance with the table below. If no TCU controllers are online, the Advisory frequency shall be issued.
+
+| Runway | Via | Departure Frequency |
+| ------ | ---- | -------------------- |
+| All | All | 125.4 (OKA) |
### Departures Controller
When a TCU controller is online, aircraft shall be issued with a departure frequency during their airways clearance in accordance with the table below. If no TCU controllers are online, the Advisory frequency shall be issued.
diff --git a/docs/aerodromes/classc/img/YBOK-CTR.png b/docs/aerodromes/classc/img/YBOK-CTR.png
new file mode 100644
index 000000000..b6c663b69
Binary files /dev/null and b/docs/aerodromes/classc/img/YBOK-CTR.png differ
diff --git a/docs/aerodromes/classc/img/YBOK-FTAs.png b/docs/aerodromes/classc/img/YBOK-FTAs.png
new file mode 100644
index 000000000..c452158aa
Binary files /dev/null and b/docs/aerodromes/classc/img/YBOK-FTAs.png differ
diff --git a/docs/aerodromes/classc/img/YBOK-Lanes.png b/docs/aerodromes/classc/img/YBOK-Lanes.png
new file mode 100644
index 000000000..ce5526062
Binary files /dev/null and b/docs/aerodromes/classc/img/YBOK-Lanes.png differ
diff --git a/docs/aerodromes/classc/img/YBOK-ManoeuvringAreaResponsibility.png b/docs/aerodromes/classc/img/YBOK-ManoeuvringAreaResponsibility.png
new file mode 100644
index 000000000..83c32847c
Binary files /dev/null and b/docs/aerodromes/classc/img/YBOK-ManoeuvringAreaResponsibility.png differ
diff --git a/docs/aerodromes/classc/img/YBOK-TaxiwayBravo.png b/docs/aerodromes/classc/img/YBOK-TaxiwayBravo.png
new file mode 100644
index 000000000..5c2b46503
Binary files /dev/null and b/docs/aerodromes/classc/img/YBOK-TaxiwayBravo.png differ
diff --git a/docs/terminal/amberleyoakey.md b/docs/terminal/amberleyoakey.md
index 9a3ef6807..20bb39935 100644
--- a/docs/terminal/amberleyoakey.md
+++ b/docs/terminal/amberleyoakey.md
@@ -21,47 +21,48 @@ The vertical limits of the AMB and OK TCUs are `SFC` to `F210`.
### Airspace Division
-####AMB TCU
-**AMA** owns the airspace contained within:
+=== "AMB TCU"
+ **AMA** owns the airspace contained within:
-- R625A (`A015`-`A085`)
-- R625B (`A025`-`A085`)
-- R625C (`A045`-`A085`)
-- R625D (`A085`-`F210`)
+ - R625A (`A015`-`A085`)
+ - R625B (`A025`-`A085`)
+ - R625C (`A045`-`A085`)
+ - R625D (`A085`-`F210`)
-
-{ width="952" }
- AMB TCU Restricted Areas
-
+
+ { width="952" }
+ AMB TCU Restricted Areas
+
-**AMB ADC** owns the Class C airspace in the AMB CTR from `SFC` to `A015`.
+ **AMB ADC** owns the Class C airspace in the AMB CTR from `SFC` to `A015`.
-####OK TCU
-**OKA** owns the airspace contained within:
+=== "OK TCU"
+ **OKA** owns the airspace contained within:
-- R654A (`SFC`-`A065`)
-- R654B (`SFC`-`A065`)
-- R654C (`A065`-`F125`)
-- R654D (`A065`-`F125`)
+ - R654A (`SFC`-`A065`)
+ - R654B (`SFC`-`A065`)
+ - R654C (`A065`-`F125`)
+ - R654D (`A065`-`F125`)
-
-{ width="1060" }
- OK TCU Restricted Areas
-
+
+ { width="1060" }
+ OK TCU Restricted Areas
+
-**OK ADC** owns the Class C airspace within 5 DME of the OK VOR from `SFC` to `A025`.
+ **OK ADC** owns the Class C airspace within 5 DME of the OK VOR from `SFC` to `A025`.
## Extending
AMA is **expected** to extend to OKA and vice versa; callsigns remain the same. See [Controller Skills](../controller-skills/extending.md) for details.
## Local Procedures
-### Coded Clearances (Fast Jets)
+### YAMB
+#### Coded Clearances
High performance military jet aircraft with planned operations in offshore SUA, or intending to depart to the east, will be assigned a Coded Clearance departure. These aircraft may arrive back to YAMB via the same corridor. These Coded Clearances provide a standardised corridor avoiding civilian traffic in the adjacent airspace.
!!! tip
Descriptions of the coded clearances are available in the [FIHA AD2 Supps](https://ais-af.airforce.gov.au/australian-aip){target=new}.
-#### Departures
+##### Departures
Aircraft will depart the circuit visually and track overhead YAMB to begin tracking for their initial waypoint. Aircraft cleared the BYRON1 must turn to the west on departure, and may set course for their inital waypoint within 10TAC AMB, remaining within the lateral limits of the AMB CTR in order to meet the inital constraint at `COWIE`.
AMB ACD will clear relevant departures via the appropriate coded clearance departure, update the FDR route field with the respective tracking points, and write the departure name in the Global Ops Field.
@@ -77,16 +78,16 @@ The routes are shown below:
!!! important
Ensure that aircraft meet the `F190` requirement by the first waypoint to ensure separation assurance is maintained with civil aircraft in the adjacent airspace.
-#### Arrivals
-Aircraft will be cleared for the coded clearance by **INL**/**NSA**, with the procedure terminating at the AM TMA airspace boundary.
+##### Arrivals
+Aircraft will be cleared for the coded clearance by **INL**/**NSA**, with the procedure terminating at the AMB TMA airspace boundary.
-### Civil Training Area
+#### Civil Training Area
Civil operators (including Australian Air Force Cadets) conduct flying operations within the South Western Training Area (SWTA), located between the 10DME and 20DME arcs to the southwest of the AMB CTR. The SWTA is divided in half by the Rosewood-Mt Walker-Aratula Road into SWTA Alpha (north) and SWTA Bravo (south). The training area is classified Class G airspace but some pilots may request to climb into CTA to facilitate flight training (such as stall practice).
!!! tip
Consider restricting an aircraft operating in the CTA above the SWTA to either SWTA Alpha or Bravo where doing so would provide lateral segregation from other traffic operating in the AMB CTA.
-#### Outbound Aircraft
+##### Outbound Aircraft
Aircraft outbound from YAMB for the SWTA will exit the CTR at `A025` via the following waypoints:
| **Duty Runway** | **Routing** |
@@ -95,7 +96,7 @@ Aircraft outbound from YAMB for the SWTA will exit the CTR at `A025` via the fol
| 33 | CLVT |
| 04 or 22 | As required |
-#### Inbound Aircraft
+##### Inbound Aircraft
Inbound aircraft will contact AMB TCU when ready to return to YAMB. They shall be cleared via the following waypoints, at either `A015` or `A025` (as desired):
| **Duty Runway** | **Routing** |
@@ -114,6 +115,102 @@ Transfer these aircraft to ADC approaching the boundary.
**AMA**: "ASTR203, contact Amberley Tower, 118.3"
**ASTR203**: "118.3, ASTR203"
+### YBOK
+
+#### Oakey Flying Training Area
+
+There are eight LFAs within the OFTA, LFAs are the primary location for military helicopters conducting low level operations. LFAs are numbered 1-8 with the prefix L, pronounced as, "LIMA (number)".
+
+SAAFRs provide efficient movement through the OFTA to specific LFAs during periods of high traffic. They are defined as 2nm wide, and are named "X-Ray", "Yankee" and "Zulu".
+
+Three transit areas, named "Whiskey" (western), "Charlie" (central) and "Echo" (eastern) are located between the Oakey CTR and inner boundaries of their respective LFAs. Transit Areas exist to provide flexibility in routing when leaving or enter Oakey CTR.
+
+The boundaries of some LFAs cross the lateral boundary of R654A/B. An ATC clearance to operate in a LFA, authorises an aircraft to leave and re-enter R654A/B within the dimensions of the cleared LFA.
+
+
+!!! tip
+ Detailed images depicting LFAs, SAAFRs and Transit Areas are available on the [Oakey AD2 SUP](https://ais-af.airforce.gov.au/australian-aip)
+
+##### Ops Normal
+
+Aircraft shall report established once within the LFA, and nominate an Ops Normal time. If the pilot does not volunteer an Ops Normal time, provide one that is on an even hour or half hour, between 30 minutes to 60 minutes from the current time.
+
+!!! phraseology
+ **FRTL31:** "Oakey Approach, FRTL31, established in Lima 1"
+ **OKA:** "FRTL31, call ops normal time 30"
+ **FRTL31:** "Ops normal time 30, FRTL31"
+
+!!! tip
+ You can set the Ops Normal timer by right clicking on the ACID in the label, and entering the agreed upon time.
+
+##### Number
+
+When practical, for aircraft tracking to an LFA, provide their number in the sequence, for that LFA.
+
+!!! example
+ **OKA:** "FRTL21, number 1 Lima 8"
+ **OKA:** "RSCU904, number 2 to CYCP90, CH47, inbound from Lima 3"
+
+##### Transit
+
+Aircraft may wish to transit from their existing LFA to another LFA. In this case, they shall be cleared to their requested LFA, via their existing LFA, not above `A030`.
+
+!!! phraseology
+ **CYCP90:** "Oakey Approach, CYCP90, request Lima 6"
+ **OKA:** "CYCP90, recleared Lima 6, via Lima 3, not above A030, number 1 Lima 6"
+ **CYCP90:** "Recleared Lima 6, via Lima 3, not above A030, CYCP90"
+
+Aircraft may also request to track through a SAAFR or Transit Area when transiting between LFAs, and should be cleared via the requested routing as appropriate.
+
+!!! phraseology
+ **SHRK37:** "Oakey Approach, SHRK37, request Lima 4, via X-Ray"
+ **OKA:** "SHRK37, recleared Lima 4, via X-Ray, not above A030, number 1 Lima 4"
+ **SHRK37:** "Recleared Lima 4, via X-Ray, not above A030, SHRK37"
+
+Not all SAAFRs and Transit Areas provide access to every LFA, each SAAFR and Transit Area connects to various LFAs. Aircraft should be cleared as requested, however if the requested SAAFR or Transit Area does not connect to the intended LFA, the aircraft must be recleared via the most appropriate alternative.
+
+!!! example
+ Aircraft requesting clearance to Lima 4 via Yankee, shall be cleared via X-Ray, as Yankee does not connect to Lima 4.
+
+=== "SAAFRs"
+ | Name | Connected LFAs |
+ | ---- | ---- |
+ | X-Ray | Lima 1, 3, 4, 5, 6 |
+ | Yankee | Lima 1, 5, 6, 7, 8 |
+ | Zulu | Lima 8, 7 |
+
+=== "Transit Areas"
+ | Name | Connected LFAs |
+ | ---- | ---- |
+ | Whiskey | Lima 2, 3, 4 |
+ | Charlie | Lima 1 |
+ | Echo | Lima 8 |
+
+##### Operations
+
+When operating within LFAs, aircraft may additionally request to operate in SAAFRs or Transit Areas. Prolonged operations in SAAFRs and Transit Areas should only be approved, subject to volume of aircraft in the Oakey CTR.
+
+!!! phraseology
+ **RSCU903:** "Oakey Approach, RSCU903, request operations within Lima 7, and SAAFR Yankee"
+ **OKA:** "RSCU903, cleared Lima 7, and operations SAAFR Yankee, not above A030, RSCU903"
+ **RSCU903:** "Cleared Lima 7, and operations SAAFR Yankee, not above A030, RSCU903"
+
+## Departure and Arrival Procedures
+
+### Departures
+
+By default, transit to LFAs will **not** be achieved through the use of SAAFRs and Transit Areas, direct tracking to the requested LFA will always be issued. Aircraft outbound from YBOK for LFAs will depart the CIRA visually and track direct to their LFA, or the requested outbound SAAFRs / Transit Area as cleared.
+
+
+### Arrivals
+
+Inbound aircraft will contact OK TCU when ready to return to YBOK. They shall be cleared to YBOK direct, not above `A030`, and be instructed to contact ADC at 5 miles.
+
+!!! phraseology
+ **KNGT43:** "Oakey Approach, helicopter KNGT43, operations complete in Lima 6, request RTB YBOK"
+ **OKA:** "KNGT43, Oakey Approach, cleared to YBOK direct, not above A030, at 5 miles, contact Oakey Tower, 120.1"
+ **KNGT43:** "Cleared to YBOK direct, not above A030, at 5 miles, contact Oakey Tower, 120.1, KNGT43"
+
## Coordination
### Enroute
#### Departures
@@ -130,7 +227,7 @@ All aircraft transiting from INL to **AMB TCU** and **OK TCU** must be [Heads-up
#### Departures
[Next](../controller-skills/coordination.md#next) coordination is required from AMB ADC to AMB TCU for all aircraft.
-The Standard Assignable Level from **AMB ADC** to **AMA** is:
+The Standard Assignable Level from **AMB ADC** to **AMB TCU** is:
| Assigned Departure | Level |
| ------------------ | ----- |
@@ -139,11 +236,12 @@ The Standard Assignable Level from **AMB ADC** to **AMA** is:
[Next](../controller-skills/coordination.md#next) coordination is required from OK ADC to OK TCU for all aircraft.
-The Standard Assignable level from **OK ADC** to **OKA** is:
+The Standard Assignable level from **OK ADC** to **OK TCU** is:
| Aircraft | Level |
| -------- | ----- |
-| All | The lower of `F120` and `RFL` |
+| Fixed-wing | The lower of `F120` and `RFL` |
+| Rotary-wing | The lower of `A030` and `RFL` |
### BN TCU
All aircraft transiting from **BN TCU** to **AMB TCU** and vice versa must be [Heads-up](../controller-skills/coordination.md#heads-up) coordinated prior to the boundary.
diff --git a/includes/abbreviations.md b/includes/abbreviations.md
index 1b26d710a..bc0340078 100644
--- a/includes/abbreviations.md
+++ b/includes/abbreviations.md
@@ -377,4 +377,9 @@
*[TSAT]: Tactical Start Approved Time
*[AOBT]: Actual Off Blocks Time
*[CTOT]: Calculated Take Off TIme
-*[ATOT]: Actual Off Blocks Time
\ No newline at end of file
+*[ATOT]: Actual Off Blocks Time
+*[OFTA]: Oakey Flying Training Area
+*[FTAs]: Flying Training Areas
+*[LFAs]: Low Flying Areas
+*[SAAFRs]: Standard Use Army Aircraft Flight Routes
+*[RTB]: Return To Base