OPS-59: Add NZZO and Oceanics

docs/oceanic/.pages

@@ -1,4 +1,6 @@
 title: Oceanic
 nav:
-    - index.md
-    - ...
+  - index.md
+  - ...
+
+order: desc

docs/oceanic/index.md

@@ -2,20 +2,78 @@
   title: Oceanic Overview
 ---
 
---8<-- "includes/abbreviations.md"
-
 !!! important "Pacific Oceanic Partnership"
     The pages contained within the Oceanic section of this website act as the Local Instructions, as required under Section 2.3(3) of the Pacific Oceanic Letter of Agreement.
 
-!!! important "Supported Controller Clients for Oceanic Positions"
-    At the moment, VATNZ only supports vatSys for oceanic operations. The "Auckland Radio" dataset is the current preferred profile for Auckland Radio operation, whereas the "South Pacific" dataset is the current preferred profile for NTTT, NCRG or NSFA operations.
+## Airspace
+
+VATNZ is responsible for three Oceanic FIRs in the Pacific area, and can be logged onto by anybody who possesses an [Oceanic Endorsement](https://www.vatnz.net/members/oceanic){ target=_blank }:
+
+- **NZZO** - Auckland Oceanic
+- **NZCM** - McMurdo Oceanic
+- **NTTT** - Tahiti Oceanic
+
+VATNZ is responsible for maintaining these sectors, as well as any aerodromes or services that fall within them. 
+
+## Pacific Oceanic Agreement
+
+VATNZ is party to the [Pacific Oceanic Letter of Agreement](https://www.vatnz.net/vatnz/policies/LOAs/pacific-oceanic-letter-agreement-v1-1-1/){ target=_blank } - allowing any Oceanic Controller from a participating organisation to control any of the participating FIR's Oceanic positions. 
+
+!!! important "VATNZ and VATPAC Reciprocal Controller Rights"
+    You should note that the Pacific Oceanic LOA and the VATNZ/VATPAC Inter-Division Visiting Controller LoAs are different, although achieving largely the same outcome. 
+
+    The Visiting Controller Policy allows any VATPAC Controller to control within any VATNZ FIR as if it were their Home Division, providing they're controlling in line with their rating or endorsements. 
+
+    The Pacific Oceanic Agreement specifically authorises **only** Oceanic Endorsed Controllers to control only Oceanic Positions in any FIR - this does not authorise them to control any other position, such as a Tower or Enroute.
+
+<figure markdown>
+  ![Oceanic Control FIRs in the Pacific](./assets/POCA.png) 
+  <figcaption>Oceanic Control FIRs in the Pacific. Not shown are VATMEX's Oceanic FIRs.</figcaption>
+</figure>
+
+The following Divisions are participants to the agreement:
+
+- VATNZ (NZZO, NZCM and NTTT)
+- VATPAC (YMMM, YBBB, NFFF, AGGG, ANAU)
+- VATUSA (KZAK)
+- VATJPN (RJTG)
+- VATMEX (MMFO)
+
+### Control Positions
+
+| Sector Name                          | Callsign            | Frequency        | Logon ID     | Division | Notes                       |
+| ------------------------------------ | ------------------- | ---------------- | ------------ | -------- | --------------------------- |
+| KZAK - Oakland Oceanic               | San Francisco Radio | 11.282 (129.400) | ZAK_FSS      | VATUSA   |                             |
+| YBBB - Brisbane Oceanic              | Brisbane Radio      | 17.904 (124.650) | BN-TSN_FSS   | VATPAC   | Also controls AGGG, ANAU    |
+| YMMM - Melbourne Oceanic             | Melbourne Radio     | 17.904 (124.650) | ML-IND_FSS   | VATPAC   |                             |
+| NZZO - Auckland Oceanic              | Auckland Radio      | 8.867 (129.000)  | NZZO_FSS     | VATNZ    | Can be split into -E sector |
+| NZZO-TSN - Auckland Oceanic (Tasman) | Auckland Radio      | 5.567 (129.500)  | NZZO-TSN_FSS | VATNZ    |                             |
+| NZCM - McMurdo Oceanic               | McMurdo Radio       | 9.032 (128.700)  | NZCM_FSS     | VATNZ    |                             |
+| NFFF - Nadi Oceanic                  | Nadi Radio          | 8.846 (123.600)  | NFFF_FSS     | VATPAC   |                             |
+| NTTT - Tahiti Oceanic                | Tahiti Radio        | 9.116 (125.500)  | NTTT_FSS     | VATPAC   |                             |
+| RJTG - Tokyo Oceanic                 | Tokyo Radio         |                  |              | VATJPN   |                             |
+| MMFO - Mexico                        |                     |                  |              |          |                             |
+
+!!! warning "Use of the /O Suffix"
+    Controllers are no longer required to use the `/O` suffix when logging onto Oceanic positions. This is due to the Division Controller Roster fulfilling the requirements for publishing a Controller's right to control Oceanic positions.
+
+### Currency Requirements
 
-    A new profile is currently being developed to merge all of these datasets into one.
+In order to utilise your Oceanic Endorsement, and by extension, exersise your rights under the Pacific Oceanic Agreement, you must meet the following criteria:
 
-!!! danger "Heads up!"
+- A Participating Organisation must require a permitted controller to log 1 hour on a permitted oceanic position, within the previous 3 months, for them to be considered active; and
+- A permitted controller who does not meet the hour requirement specified above, will be considered inactive; and
+- An inactive permitted controller may become active again, by performing a buddy session with a permitted controller who is approved to do so by that PO; and
+- Any additional currency or activity requirements imposed by a PO on local or visiting controllers do not apply to permitted controllers.
 
-    VATNZ's Oceanic and Pacific sectors are currently undergoing a refresh project, aimed at overhauling how our Pacific sectors operate, in addition to providing additional information to Controllers.
+### Procedures for participating Oceanic Sectors
 
-    This project is still underway, and elements of this Oceanic section **may not** be reflective of the current state of the network. This is annotated where appropriate.
+Procedures for Divisions that are participating in the Pacific Oceanic Agreement can be found in the following table.
 
-VATNZ has responsibility for not only the NZZC sector, but also the NZZO and NTTT FIRs. These FIRs cover a variety of areas - ranging from the tropical paradise of French Polynesia, to the bitter cold of Antarctica.
+| Sectors    | Divison | Procedures Link                                                                                                                      |
+| ---------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| YBBB, YMMM | VATPAC  | [VATPAC SOPs](http://sops.vatpac.org/oceanic/)                                                                                       |
+| NFFF       | VATPAC  | [VATPAC SOPs](http://sops.vatpac.org/pacific/)                                                                                       |
+| RJTG       | VATJPN  | To be added                                                                                                                          |
+| MMFO       | VATMEX  | To be added                                                                                                                          |
+| KZAK       | VATUSA  | [ZAK Standard Operating Procedure](https://oakartcc.org/web/viewer.html?file=/controllers/file/e8a98e09-1c16-11ec-9430-2a32edb55910) |

docs/oceanic/nzzo/.pages

@@ -1,5 +1,4 @@
 title: Auckand Radio (NZZO)
 nav:
     - index.md
-    - reporting.md
     - ...

docs/oceanic/nzzo/index.md

@@ -4,33 +4,32 @@
 
 --8<-- "includes/abbreviations.md"
 
-Auckland Radio is an oceanic control station that covers the entirely of the NZZO FIR from FL245 to FL600, except where intersected by the NZZC and NZCM FIRs. In the real-world, radar coverage over this large area over the ocean is not possible - therefore non-radar procedures are used to ensure the separation of aircraft.
+Auckland Radio is responsible for managing oceanic air traffic control within the NZZO FIR. This vast area spans much of the open ocean, where radar coverage is unavailable, necessitating the use of non-radar procedural control to ensure safe separation of aircraft. Auckland Radio works in close coordination with neighbouring FIRs, including NZZC and NZCM, to maintain efficient and safe operations across these boundaries.
 
 ## Positions
 
-There are three approved positions that can be staffed within the NZZO FIR. 
-
-| Callsign   | Position Name         | RTF Designator | Frequency                    | Notes               |
-| ---------- | --------------------- | -------------- | ---------------------------- | ------------------- |
-| NZZO_FSS   | Auckland Radio        | Auckland Radio | 8.867 (VHF alias 129.00MHz)  |                     |
-| NZZO-E_FSS | Auckland Radio - East | Auckland Radio | 5.643 (VHF alias 131.500MHz) | Event Only Position |
-| NZCM_FSS   | MacMurdo Center       | Mac Center     | 9.032 (VHF alias 128.700MHz) |                     |
+| Callsign     | Position Name           | RTF Designator | Frequency                    | Notes                                       |
+| ------------ | ----------------------- | -------------- | ---------------------------- | ------------------------------------------- |
+| NZZO_FSS     | Auckland Radio          | Auckland Radio | 8.867 (VHF alias 129.000MHz) | Primary Position                            |
+| NZZO-TSN_FSS | Auckland Radio - Tasman | Auckland Radio | 5.643 (VHF alias 129.500MHz) | Secondary Position, covering the TAS sector |
+| NZZO-E_FSS   | Auckland Radio - East   | Auckland Radio | 5.643 (VHF alias 131.500MHz) | Event Only Position                         |
+| NZCM_FSS     | MacMurdo Center         | Mac Center     | 9.032 (VHF alias 128.700MHz) | Covers NZCM FIR                             |
 
 
 ## Airspace Overview
 
 ![Airspace](../assets/nzzo-area.png){ align=right width="40%"}
 
-Auckland Radio is airspace begins at FL245, and tops-out at FL600. The lateral boundaries of NZZO can be seen to the right, as is bounded by:
+Auckland Radio controls the airspace within the NZZO FIR, which extends from FL245 to FL600. The lateral boundaries of NZZO are shown in the diagram to the right and are defined as follows:
 
-  - **West:** Brisbane Radio - Indian South, Tasman and Lord Howe Island sectors.
-  - **North West**: Nadi Oceanic
-  - **North**: Oakland Oceanic
-  - **North-East**: Tahiti Oceanic
-  - **East**: Pascula
-  - **South**: MacMurdo Center
+- **West**: Brisbane Radio (Indian South, Tasman, and Lord Howe Island sectors)
+- **North West**: Nadi Oceanic
+- **North**: Oakland Oceanic
+- **North-East**: Tahiti Oceanic
+- **East**: Mataveri Radio (Easter Island)
+- **South**: MacMurdo Center
 
-It is important to note that NZZO **does not** provide coverage over, or within the NZZC FIR.
+It’s important to note that NZZO **does not** provide coverage over or within the NZZC FIR.
 
 Below is an overview of the various classes of airspace that can be found within the NZZO. 
 

docs/oceanic/nzzo/procedures.md

@@ -0,0 +1,125 @@
+---
+  title: Procedures
+---
+
+--8<-- "includes/abbreviations.md"
+
+## Methods of Communication
+
+The primary method of communication is via HF Voice.
+
+CPDLC is not yet supported but may be offered as a secondary means of communication if available. ARO's CPDLC logon code shall be `NZZO`.
+
+### HF
+
+Simulated HF radio is used as the primary long-range radio communications medium. The nature of HF radio makes it highly vulnerable to atmospheric distortion and noise, so radiotelephony procedures on HF tend to be more formal to maximize clarity.
+
+#### SELCAL
+
+Given the background noise level experienced on HF radio frequencies, flight crews usually prefer to turn down the audio level of their HF receiver. SELCAL uses a unique 4-letter code for each aircraft (e.g. `QR-AC`), transmitted over the communications frequency to sound an alert for the flight crew.
+
+Controllers must check each aircraft’s flight plan for a discrete SELCAL code. If aircraft have nominated a discrete code (for example, `QR-AC`), a SELCAL check shall be completed on initial contact.
+
+!!! important "Use of SELCAL"
+    Where a SELCAL check has been completed successfully, all subsequent communications shall be conducted prefaced by a SELCAL chime.
+
+!!! example "RTF Example for readback of a Position Report"
+    **Auckland Radio**: *"UAE412, standby SELCAL check."*  
+    Aircraft awaits the SELCAL chime before replying.  
+    **UAE412**: *"SELCAL check OK, UAE412."*    
+    Then continue with routine communications.
+
+### CPDLC
+
+!!! info "Not yet supported in NZZO"
+    These procedures will be produced when CPDLC is supported in NZZO.
+
+
+## Position Reports
+
+As NZZO is procedural airspace, pilots are required to provide regular position reports to ATC, which can then be entered into your Controller Client software.
+
+A Position Report will contain the following elements:
+
+- Callsign
+- Position & Time
+- Flight level
+- Next position and time over
+- Ensuing significant point
+- Specified Speed (if assigned)
+
+If an aircraft fails to report its position within 3 minutes of its estimated time, controllers must attempt to establish contact with that aircraft and obtain a position report.
+
+ATC shall acknowledge a position report by using the aircraft's callsign. A readback of the report is not required unless the controller needs to confirm the information provided.
+
+!!! example "RTF Example for readback of a Position Report"
+    **UAE412**: *"Auckland Radio, Auckland Radio. UAE412 with position."*  
+    **Auckland Radio**: *"UAE412, pass position report."*    
+    **UAE412**: *"UAE412 is position TATAS time 1853. Estimating SAMAD at 1953. OSUGA next."*  
+    **Auckland Radio**: *"UAE412, Auckland Radio copies position report."*  
+
+!!! tip "Position Report Formatting Tool"
+    If pilots in your airspace are struggling to provide accurate position reports, you can send them the [Oceanic Report Tool](https://www.vatnz.net/pilots/oceanic-report-tool/){ target=_blank } to help them out.
+
+## Transfer of Control Point
+
+### NZZC Enroutes to ARO
+
+NZZC enroute sectors must provide a 10-minute warning to Auckland Radio (ARO) before an aircraft crosses the FIR boundary.
+
+### ARO to NZZC Enroutes
+
+Aircraft entering an NZZC enroute sector must do so via a named fix at their assigned flight level. Pilots shall be instructed to contact the appropriate NZZC sector frequency when crossing the boundary fix.
+
+Since aircraft crossing into NZZC enter a surveillance environment, prior coordination with NZZC sectors is not required provided the aircraft meets the conditions above.
+
+!!! example "RTF Example for handing off to a NZZC sector"
+    **Auckland Radio**: *"UAE412, at position PEBLU, contact Auckland Control on 123.900."*    
+    **UAE412**: *"UAE412 at position PEBLU, contact Auckland Control on 123.900."*
+
+#### Oceanic Airspace delegated to STH
+
+ARO delegates airspace to the STH sector along the western boundary of the NZZC FIR near NZQN. Aircraft within this delegated airspace follow a 130nm arc from the `QN VOR`, which includes four waypoints: `BEBOB`, `DADLU`, `MADOK`, and `EKODA`. These waypoints are boundary fixes and serve as the transfer of control points between STH and ARO, in both directions.
+
+### ARO to other Oceanic FIRs
+
+For flights leaving NZZO to enter other oceanic FIRs, voiceless transfers may be used. There shall be no changes to the route or cleared flight level (CFL) within 15 minutes of the FIR boundary.
+
+#### Transferring to YBBB or YMMM
+
+Most airways over the Tasman Sea have only two waypoints within the NZZO FIR, both being boundary fixes. As a result, flights may receive contact instructions for the next sector during their initial radio call with ARO. ARO shall retain control over the flight tag until the common airspace boundary.
+
+For flights that include an additional waypoint within the NZZO sector, contact instructions for the next sector shall be issued at the waypoint immediately preceding the boundary fix.
+
+!!! example "RTF Example for short Tasman routes"   
+    **ANZ204**: *"Auckland Radio, Auckland Radio. ANZ204 with position."*  
+    **Auckland Radio**: *"ANZ204, pass position report"*      
+    **ANZ204**: *"ANZ204 is position PEBLU time 1832. Estimating SASRO at 1911. MIKEG next."*  
+    **Auckland Radio**: *"ANZ204, Auckland Radio copies position report. Standby SELCAL check."*    
+    Aircraft waits for the SELCAL chime before replying. <br />
+    **ANZ204**: *"Auckland Radio, ANZ204 on SELCAL."*  
+    **Auckland Radio**: *"ANZ204, Auckland Radio accepts primary guard on 129.000, negative secondary. At SASRO, contact Brisbane Radio on primary 124.650."*  
+    **ANZ204**: *"Auckland Radio, ANZ204 primary guard on 129.000, negative secondary. At SASRO, contact Brisbane Radio on primary 124.650."*  
+
+## NZCI to NZZC
+
+### Below FL245
+
+ARO shall not pass IFR clearances to aircraft requesting to operate below FL245 whilst on the ground or following departure from the Chatham Islands. ARO shall not accept radio guard for aircraft operating below FL245.
+
+- The aircraft shall broadcast their position on UNICOM, and shall monitor ARO's frequency.
+- Aircraft may be passed traffic information at their requested altitude or levels.
+
+Before reaching the NZZO boundary, the aircraft shall be instructed to contact the NZZC sector for clearance into controlled airspace.
+
+!!! example "RTF Example for NZZC entry instructions"   
+    **Auckland Radio**: *"CVA554, prior to position ATABU, contact Ohakea Control on 126.200 for clearance into controlled airspace."* 
+
+### Above FL245
+
+Aircraft operating above FL245 shall be handed between NZZO and NZZC controllers in accordance with standard handover requirements. 
+
+For aircraft requiring descent below FL245, the aircraft shall be instructed to leave controlled airspace by descent, as well as the traffic status at NZCI, if known.
+
+!!! example "RTF Example for descent below FL245"
+    **Auckland Radio**: *"TNZ123 (when ready | at/after time/position) leave controlled airspace by descent. Report passing FL240. (Traffic is.. | No reported IFR traffic)"*