add vatnz template

.github/workflows/ci.yml

@@ -0,0 +1,17 @@
+name: ci 
+on:
+  push:
+    branches: 
+      - master
+      - main
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-python@v2
+        with:
+          python-version: 3.x
+      - run: pip install mkdocs-material 
+      - run: pip install -r requirements.txt
+      - run: mkdocs gh-deploy --force

.gitignore

@@ -0,0 +1 @@
+site

.vscode/settings.json

@@ -0,0 +1,5 @@
+{
+  "cSpell.words": [
+    "mkdocs"
+  ]
+}

README.md

@@ -0,0 +1,26 @@
+# VATNZ SOPs Refresh Project
+
+[![ci](https://github.com/vatnz-dev/sops/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/vatnz-dev/sops/actions/workflows/ci.yml) [![pages-build-deployment](https://github.com/vatnz-dev/sops/actions/workflows/pages/pages-build-deployment/badge.svg)](https://github.com/vatnz-dev/sops/actions/workflows/pages/pages-build-deployment) 
+[![wakatime](https://wakatime.com/badge/user/aee2c50b-3ced-4d92-a929-de0362daeb37/project/f9b51418-4a41-46c9-ae52-5b5b8a9600a9.svg)](https://wakatime.com/badge/user/aee2c50b-3ced-4d92-a929-de0362daeb37/project/f9b51418-4a41-46c9-ae52-5b5b8a9600a9.svg)
+
+The VATNZ SOPs Refresh Project is an open-source collaborative project allowing members of the VATNZ community to work together to create high-quality SOPs for the virtual New Zealand FIR.
+
+## Contributing
+
+Contribution guidelines can be found within the project under [Assist Us](https://vatnz-dev.github.io/sops/assist-us/). 
+
+**Before contributing** you should liaise with the VATNZ Operations Team to ascertain whether that particular SOP is needed. There is a fine-line between enabling a realistic service, and making our SOPs easy to navigate and understand.
+
+A specific channel for SOP development discussion exists on the VATNZ Discord. Please message the Operations Director to gain access to this channel.
+
+## Build and Deployment
+
+This project uses some basic CI to automatically push the latest commits to the `main` branch to GitHub Pages. 
+
+Because of this, all changes should be made as a Pull Request. This also ensures - 
+  * That everybody has visibility of what you're working on, and can provide commit-by-commit commenting and review.
+  * A much better method of version control, as most PR's will be squashed and merged into `main`.
+
+## Project Control
+
+The owner for this project is the Operations Director. Members of the Operations Team are also able to review PR's.

docs/.pages

@@ -0,0 +1,8 @@
+nav:
+    - Home: index.md
+    - Oceanic and Pacific: oceanic-pacific
+    - Enroute: enroute
+    - Aerodromes: aerodromes
+    - Controller Skills: controller-skills
+    - Assist Us: assist-us
+

docs/CNAME

@@ -0,0 +1 @@
+vatnz-dev.github.io/sops/

docs/aerodromes/.pages

@@ -0,0 +1,9 @@
+# Edit this page to get:
+# - Title for the whole directory
+# - Titles for specific pages or subdirectories
+# - Order of pages (otherwise alphabetical order)
+
+title: Aerodromes
+nav:
+    - Overview: index.md
+    - ...

docs/aerodromes/Class C/.pages

@@ -0,0 +1,9 @@
+# Edit this page to get:
+# - Title for the whole directory
+# - Titles for specific pages or subdirectories
+# - Order of pages (otherwise alphabetical order)
+
+title: Class C 
+nav:
+    - Overview: index.md
+    - ...

docs/aerodromes/Class C/NZQN/.pages

@@ -0,0 +1,3 @@
+title: NZQN - Queenstown
+nav:
+  - ...

docs/aerodromes/Class C/NZQN/notes.md

@@ -0,0 +1,83 @@
+---
+  title: Queenstown AD Notes
+---
+
+--8<-- "includes/abbreviations.md"
+
+## Use of Taxiways
+
+Queenstown has two parallel runway entry taxiways `A3` and `A4`. Usually the outbound aircraft will take the taxiway closest to the departure runway, and the vacating traffic will take the taxiway closest to the terminating end.
+
+**For example** - If RWY 23 is active, aircraft will enter at `A4` and exit at `A3`. If RWY 05 is active, aircraft will enter at `A3` and exit at `A4`.
+
+## General Rules of Thumb
+
+### RNP Approaches
+
+There are two RNP approaches per runway - the RNP Y or RNP Z. The RNP Y is used for Approach Category C or D aircraft (jet aircraft), whereas the RNP Z is to be used for Approach Category B aircraft, such as turboprops.
+
+!!! information
+    The RNP Yankee and Zulu approaches follow the same lateral path, but have differing vertical paths. For example, on the go-around for the RNP-Z 23, there are speed restrictions placed on the initial climb fixes to `QN737`. This forces the aircraft to gain altitude quicker.
+
+### Departures
+
+Queenstown is surrounded by significant terrain, so aircraft should stick to the departure path where possible. However, once the aircraft has climbed above the surrounding terrain, they may be cleared direct to their SID termination fix, where they can resume their filed plan.
+
+## Procedure Assignment
+
+### RWY 23
+
+#### STARs
+
+vatSys and EuroScope will usually assign the most appropriate arrival for that aircraft's flightplan. 
+
+| Arrival Direction | Transition Fix | STAR             | Notes                                    |
+| ----------------- | -------------- | ---------------- | ---------------------------------------- |
+| NE                | ELRUV          | ELRUV 2A         | WN/CH traffic. AA traffic if using AAQN4 |
+| N                 | DOVOT          | UBDAM 4B / DOVOT | AA traffic, if using AAQN2               |
+| SE                | SUNGU          | SUNGU 4B         | NV traffic                               |
+| W                 | ADKOS          | UBDAM 4B / ADKOS | Oceanic traffic                          |
+| NW                | LIBLA          | UBDAM 4B / LIBLA | Oceanic traffic                          |
+
+#### Approaches
+
+All of Runway 23's STARs terminate at either `UGPED` or `ATKIL`, which are the IAF for both the RNP and back-up RNAV approaches. Category B aircraft should be given the RNP Z, and Category C/D aircraft should be given the RNP Y.
+
+Aircraft unable to fly the RNP approaches can be issued the RNAV G or H. These approaches follow the general path of the RNP approaches, albeit with a higher profile. Both of these approaches end in visual circling segments to both runways. 
+
+!!! danger "Heads up!"
+    If you assign the RNAV G or H approaches to aircraft, you should expect them to **not** follow the visual segment. This significantly limits your runway occupancy, and increases the potential for conflict.
+
+#### Missed Approaches
+
+The Missed Approach for both RNPs have the aircraft climb to 10,000 feet and enter a hold at `SUNGU`. For aircraft unable to reach this altitude, they are to continue onwards to `NV`, climbing to 10,000 feet.
+
+Due to the holding point also being a STAR commencement fix, aircraft may be given a `SUNGU` based STAR for another attempt.
+
+#### Departures
+
+The assignment of departures out of Queenstown is largely governed by aircraft performance. This can be either climb performance, or navigation performance. 
+
+!!! info ""
+    Departures out of Queenstown that have a `A` or `B` suffix are RNP departure procedures. In this case, the entirety of the departure has lateral and vertical path to ensure separation from terrain.
+
+    Departures that have a `D`, `C`, `F`, `P`, `Q`, `S` or `T` suffix is a RNAV departure, with a visual initial climb segment.
+
+    Not all aircraft that fly into Queenstown are able to perform RNP procedures, so you may choose to issue a departure that is true to real life.
+    On the network, in reality, most pilots aren't going to mind whether or not their departure is accurate - so the replication of that is up to you.
+
+| Departure Direction | SID | Available Transitions | A/C Cat | Preferred Departure? | Notes |
+|---|---|---|---|---|---|
+| N | ANPOV 3B | ANPOV, SAVLA, TIMJO | A B C | Yes | RNP - Once a/c above MSA, clear direct transition |
+| N | ANPOV 4D | SAVLA, TIMJO | A B C | No | Initial circling visual segment to `ENKUV` |
+| N | ANPOV 3F | SAVLA, TIMJO | A B C | No | Identical to `ANPOV 4D`, with additional climb restrictions. |
+| N | ANPOV 3S<br>ANPOV 3T | SAVLA, TIMJO | A B C | No | 3S: Initial visual segment tracking via Rat Point, then direct `DULUL`.<br>3T: Initial visual segment tracking south via Frankton Arm, then <br>direct `DULUL` via over the airfield |
+| W | IPNOR 3B | ADKOS, LIBLA | A B C | Yes | RNP - westbound international departures |
+| W | IPNOR 3D | ADKOS, LIBLA | A B C | No | Initial circling visual segment via `ENKUV` |
+| SE | REDOL 1B | ADLUP | B | Yes | RNP - Once aircraft have passed `TUMTA` (not above 9,000 feet) <br>and climbed above area MSA (12,000 feet), they can be cleared direct `ADLUP`<br>or further |
+
+
+### RWY 05
+
+
+## Runway Occupancy

docs/aerodromes/Class C/index.md

@@ -0,0 +1,8 @@
+---
+  title: Test Aerodrome
+
+---
+
+--8<-- "includes/abbreviations.md"
+
+

docs/aerodromes/Class D/.pages

@@ -0,0 +1,9 @@
+# Edit this page to get:
+# - Title for the whole directory
+# - Titles for specific pages or subdirectories
+# - Order of pages (otherwise alphabetical order)
+
+title: Class D 
+nav:
+    - Overview: index.md
+    - ...

docs/aerodromes/Class D/NZPM/.pages

@@ -0,0 +1,4 @@
+title: NZPM - Palmerston North
+nav:
+  - Aerodrome Overview: index.md
+  - ...

docs/aerodromes/Class D/NZPM/arrivals.md

@@ -0,0 +1,5 @@
+---
+  title: Arrivals
+---
+
+--8<-- "includes/abbreviation"

docs/aerodromes/Class D/NZPM/departures.md

@@ -0,0 +1,5 @@
+---
+  title: Departures
+---
+
+--8<-- "includes/abbreviation"

docs/aerodromes/Class D/NZPM/index.md

@@ -0,0 +1,30 @@
+---
+  title: Overview
+---
+
+--8<-- "includes/abbreviations.md"
+
+## Control Positions and Navaids
+
+| Position Name     | Callsign  | Frequency   | Usage      |
+| ----------------- | --------- | ----------- | ---------- |
+| D-ATIS            | NZPM_ATIS | 129.700 MHz | ATIS       |
+| Palmerston Ground | NZPM_GND  | 121.700 MHz | Event Only |
+| Palmerston Tower  | NZPM_TWR  | 120.600 MHz | Primary    |
+| Ohakea Approach   | NZOH_APP  | 125.100 MHz | Primary    |
+
+
+
+## Aerodrome Usage
+
+Purpose of the aerodrome, typical traffic patterns, typical aircraft, unusual things about the AD (weird approaches, weird airspace, etc)
+
+### Aerodrome Layout
+
+#### Runways
+
+Information about runway restrictions, etc
+
+#### Taxiways
+
+Taxiway restrictions, normal taxi 

docs/aerodromes/Class D/NZPM/vfr-procedures.md

@@ -0,0 +1,7 @@
+---
+  title: VFR Procedures
+---
+
+--8<-- "includes/abbreviation"
+
+## Title

docs/aerodromes/Class D/NZTG/.pages

@@ -0,0 +1,4 @@
+title: NZTG - Tauranga
+nav:
+  - index.md
+  - ...

docs/aerodromes/Class D/NZTG/arrivals.md

@@ -0,0 +1,57 @@
+---
+  title: Arrivals
+---
+
+--8<-- "includes/abbreviations.md"
+
+## Standard Terminal Arrivals
+
+
+
+### Runway 07
+
+#### STARs
+
+| Arrival Direction | Transition Fix | STAR     | Notes                                               |
+| ----------------- | -------------- | -------- | --------------------------------------------------- |
+| NW                | BIKOT          | BIKOT 1A | Light IFR                                           |
+| NW                | URBUX          | URBUX 1A | Auckland arrivals                                   |
+| W                 | OLDON          | OLDON 1A | Hamilton arrivals                                   |
+| SW                | FALLS          | FALLS 1A | Wellington arrivals when `OROPI` route is congested |
+| SE                | GOBUK          | GOBUK 1A | Any eastern arrivals                                |
+| S                 | OROPI          | OROPI 1A | Wellington or Christchurch arrivals                 |
+| E                 | PIBOV          | PIBOV 1A | Eastern arrivals from Whakatane or Gisbourne        |
+
+### Approaches
+
+All arrivals terminate at `RUSTA` or `MORTA`, which are the IAF for the RNAV approach.
+
+If aircraft are visual they can report "`Callsign, IAF, inbound, visual RNAV 07`". It is then up to the Controllers discretion whether the aircraft is cleared visual or not. 
+
+### Missed Approach
+
+In the event of a missed approach, aicraft should be instructed to carry out the published missed approach procedure. This will have the aircraft climbing to 2000 feet, turning left direct to `LETGU`, before holding at `RUSTA` 5000 feet or above. Aircrft can then be re-cleared for the RNAV approach, or cleared a visual approach, should the conditions be suitable.
+
+## Runway 25
+
+#### STARs
+
+| Arrival Direction | Transition Fix | STAR     | Notes                                               |
+| ----------------- | -------------- | -------- | --------------------------------------------------- |
+| NW                | BIKOT          | BIKOT 1B | Light IFR                                           |
+| NW                | URBUX          | URBUX 1B | Auckland arrivals                                   |
+| W                 | OLDON          | OLDON 1B | Hamilton arrivals                                   |
+| SW                | FALLS          | FALLS 1B | Wellington arrivals when `OROPI` Route is congested |
+| SE                | GOBUK          | GOBUK 1B | Any eastern arrivals                                |
+| S                 | OROPI          | OROPI 1B | Wellington or Christchurch arrivals                 |
+| E                 | PIBOV          | PIBOV 1B | Eastern arrivals from Whakatane or Gisbourne        |
+
+### Approaches
+
+All Arrivals Terminate at `UBSET ` or `TODAN`, which are the IAF for the RNAV approach.
+
+If aircraft are visual they can report "`Callsign, IAF, inbound, visual RNAV 25`". It is then up to the Controllers discretion whether the aircraft is cleared visual or not. 
+
+### Missed Approach
+
+In the event of a missed approach, aicraft should be instructed to carry out the published missed approach procedure. This will have the aircraft climbing to 2000 feet, turning right direct to `LETGU`, before holding at `UBSET` at 4000 feet or above. Aircrft can then be re-cleared for the RNAV approach, or cleared a visual approach, should the conditions be suitable.

docs/aerodromes/Class D/NZTG/departures.md

@@ -0,0 +1,36 @@
+---
+  title: Departures
+---
+
+--8<-- "includes/abbreviations.md"
+
+## Procedure Assignment
+
+Our Controller Clients will usually assign the most suitable departure for that aircraft's flight plan, although is is important to understand the Departures and their typical assignment rules.
+
+### Runway 07
+
+#### SIDs
+
+
+| Departure Direction | SID      | Transition                              | Notes                                                                             |
+| ------------------- | -------- | --------------------------------------- | --------------------------------------------------------------------------------- |
+| NW                  | UBSET 2P | `NOBAR`                                 | Auckland or Northland bound aircraft                                              |
+| SE                  | TODAN 2P | `OLDON` `FALLS` `ODOLO` `GOBUK` `PIBOV` | Wellington or Chrishchurch traffic - occasionally Hamilton.                       |
+| W                   | BELET 3  | `DOTAR`                                 | Non-RNAV departure. Typically issued to GA IFR, due to not being fitted for GNSS. |
+
+
+### Runway 25
+
+#### SIDs
+
+| Departure Direction | SID      | Transition                              | Notes                                                                             |
+| ------------------- | -------- | --------------------------------------- | --------------------------------------------------------------------------------- |
+| NW                  | RUSTR 2R | `NOBAR`                                 | Auckland or Northland bound aircraft                                              |
+| S                   | MORTA 2R | `OLDON` `FALLS` `ODOLO` `GOBUK` `PIBOV` | Wellington or Chrishchurch traffic - occasionally Hamilton.                       |
+| W                   | DOTAR 3  | `DOTAR`                                 | Non-RNAV departure. Typically issued to GA IFR, due to not being fitted for GNSS. |
+
+### Visual Departures
+
+!!! info
+    Visual departures are almost never given in Tauranga, due to the SID being cancelled early by Bay Approach. Most aircraft will typically be cleared direct the transition fix, traffic depending.