diff --git a/docs/aerodromes/Flight Service/assets/nzmf-airspace.png b/docs/aerodromes/Flight Service/assets/nzmf-airspace.png
new file mode 100644
index 00000000..ef54c545
Binary files /dev/null and b/docs/aerodromes/Flight Service/assets/nzmf-airspace.png differ
diff --git a/docs/aerodromes/Flight Service/assets/nzpp-airspace.png b/docs/aerodromes/Flight Service/assets/nzpp-airspace.png
new file mode 100644
index 00000000..e8937a07
Binary files /dev/null and b/docs/aerodromes/Flight Service/assets/nzpp-airspace.png differ
diff --git a/docs/aerodromes/Flight Service/nzmf.md b/docs/aerodromes/Flight Service/nzmf.md
new file mode 100644
index 00000000..0d4d7bac
--- /dev/null
+++ b/docs/aerodromes/Flight Service/nzmf.md
@@ -0,0 +1,77 @@
+---
+title: NZMF - Milford Flight Service
+---
+
+--8<-- "includes/abbreviations.md"
+
+!!! Danger "Important"
+ The following are designated as Event Only positions, and may only be staffed during a VATNZ event where approved, or if explicitly authorised by the Operations Director.
+
+## Positions
+
+| Position Name | Shortcode | Callsign | Frequency | Login ID | Usage |
+| ---------------------- | --------- | ---------------------------------------- | --------- | -------- | ---------- |
+| Milford Flight Service | MFS | Milford Flight Service / Milford Traffic | 118.200 | NZMF_TWR | Event Only |
+
+## Area of Responsibility
+
+Milford Flight Service provides an Aerodrome Flight Information Service (AFIS) within the Milford Sound Common Frequency Zone (CFZ).
+
+
+ 
+ Milford CFZ
+
+
+The AFIS area extends to `A110` within the published Milford Sound CFZ.
+
+The Flight Service Operator is responsible for providing:
+
+- Weather information.
+- Traffic information.
+- Relevant safety information.
+
+!!! danger "Air Traffic Control"
+ Flight Service Operators do **not** provide Air Traffic Control and shall **not** issue taxi, take-off or landing clearances.
+
+## Standard Operations
+
+!!! info "Scenic Flight Environment"
+ Milford Sound is a busy scenic flying environment. Aircraft frequently operate at low level between visual reporting points within the CFZ.
+
+ Flight Service Operators should maintain a good awareness of all reported traffic and provide relevant traffic information whenever required.
+
+## Standard Phraseology
+
+Refer to the **AFIS** [guide](../../controller-skills/flight-service.md#standard-phraseology).
+
+## VFR Procedures
+
+### Scenic Flight Operations
+
+!!! note "Common Reporting Areas"
+ Scenic flights commonly operate between:
+
+ - Harrison River
+ - Pembroke Junction
+ - St Anne Point
+
+ Traffic information should be passed to aircraft operating within these areas whenever appropriate.
+
+## IFR Operations
+
+!!! warning "IFR Operations"
+ Milford Sound is primarily a VFR aerodrome. IFR procedures are not routinely provided by Milford Flight Service.
+
+ Where IFR operations are required, coordinate with the overlying ATS unit as appropriate and refer to the **Paraparaumu Flight Service** procedures for IFR guidance.
+
+## Frequency Changes
+
+!!! note
+ As Flight Service is an advisory service, formal handoffs are not required.
+
+ Aircraft leaving the CFZ will normally:
+
+ - Change to the **VATSIM Advisory Frequency** when remaining outside controlled airspace.
+ - Contact the appropriate ATS unit when entering controlled airspace (CTA).
+
+ If an aircraft remains on the Flight Service frequency after leaving the CFZ, remind the pilot to change to the appropriate frequency.
diff --git a/docs/aerodromes/Flight Service/nzpp.md b/docs/aerodromes/Flight Service/nzpp.md
new file mode 100644
index 00000000..34c95181
--- /dev/null
+++ b/docs/aerodromes/Flight Service/nzpp.md
@@ -0,0 +1,93 @@
+---
+title: NZPP - Paraparaumu Flight Service
+---
+
+--8<-- "includes/abbreviations.md"
+
+!!! Danger "Important"
+ The following are designated as Event Only positions, and may only be staffed during a VATNZ event where approved, or if explicitly authorised by the Operations Director.
+
+## Positions
+
+| Position Name | Shortcode | Callsign | Frequency | Login ID | Usage |
+| -------------------------- | --------- | ------------------------------------------------ | --------- | -------- | ---------- |
+| Paraparaumu Flight Service | PFS | Paraparaumu Flight Service / Paraparaumu Traffic | 118.300 | NZPP_TWR | Event Only |
+
+!!! note "Pronunciation"
+ The unofficial real-world pronunciation of **Paraparaumu** is **"Paraparam"**, and this pronunciation should be used on the network.
+
+## Area of Responsibility
+
+Paraparaumu Flight Service provides an Aerodrome Flight Information Service (AFIS) within the Paraparaumu MBZ.
+
+
+ 
+ Paraparaumu MBZ
+
+
+The AFIS area extends:
+
+- Below `A045` north of NZPP.
+- Below `A025` and `A035` south of NZPP (the lower limit of the Wellington CTA).
+
+The Flight Service Operator is responsible for providing:
+
+- Weather information.
+- Traffic information.
+- Relevant safety information.
+- Relaying IFR clearances
+
+## Standard Phraseology
+
+Refer to the **AFIS** [guide](../../controller-skills/flight-service.md#standard-phraseology).
+
+## VFR Procedures
+
+### Preferred Arrival and Departure Routes
+
+VFR aircraft should use the published preferred arrival and departure routes whenever practicable.
+
+[AIP Chart refers](https://www.aip.net.nz/assets/AIP/Aerodrome-Charts/Paraparaumu-NZPP/NZPP_35.3_35.4.pdf){ target=new }
+
+### Circuit Operations
+
+Pilots should remain on the Flight Service frequency whilst taxiing, operating within the circuit and manoeuvring within the MBZ.
+
+## IFR Operations
+
+### IFR Departures
+
+Paraparaumu Flight Service may relay IFR clearances issued by Wellington Approach.
+
+Clearances remain **invalid** until Wellington Approach advises that they are released.
+
+### IFR Arrivals
+
+Aircraft conducting instrument approaches should remain with Wellington Approach until instructed to contact Paraparaumu Flight Service.
+
+Once established within the MBZ, provide weather information and any relevant traffic information.
+
+## Coordination
+
+### IFR Departure Clearance
+
+Prior to relaying an IFR clearance, Paraparaumu Flight Service shall obtain the clearance from Wellington Approach.
+
+!!! example "Coordination For Clearance"
+ **Paraparaumu Flight Service** -> **Wellington Approach**: "Clearance Request KVY, GUGAK6 Departure, KAMET Transition, at 5000 feet, Runway 34."
+ **Wellington Approach** -> **Paraparaumu Flight Service**: "KVY, Approved."
+
+!!! example "Coordination For Release"
+ **Paraparaumu Flight Service** -> **Wellington Approach**: "Request Release KVY"
+ **Wellington Approach** -> **Paraparaumu Flight Service**: "KVY Released"
+
+## Frequency Changes
+
+As Flight Service is an advisory service, formal handoffs are not required.
+
+Aircraft leaving the MBZ will normally change to:
+
+- **Wellington Approach** when entering controlled airspace.
+- **Paraparaumu Traffic** or **VATSIM ADVISORY FREQUENCY** when operating outside the MBZ.
+
+If a aircraft remains on the Flight Service frequency after leaving the MBZ, remind the pilot to change to the appropriate frequency.
diff --git a/docs/aerodromes/index.md b/docs/aerodromes/index.md
index 91b7b9a2..c81c55f2 100644
--- a/docs/aerodromes/index.md
+++ b/docs/aerodromes/index.md
@@ -8,7 +8,7 @@ This section covers aerodrome specific procedures, separated by airspace class.
Class C airspace is applied to CTRs at large international aerodromes, associated CTAs, and en‑route airspace covering principal domestic air routes.
-In this airspace IFR and VFR traffic are separated from each other at all times. Within a CTR, IFR aircraft are separated from special VFR (operating below visual meteorological conditions) aircraft, and special VFR aircraft are eparated from each other when visibility is less than 5 km.
+In this airspace IFR and VFR traffic are separated from each other at all times. Within a CTR, IFR aircraft are separated from special VFR (operating below visual meteorological conditions) aircraft, and special VFR aircraft are separated from each other when visibility is less than 5 km.
Where separation is not being provided, air traffic controllers are required to pass appropriate traffic information to VFR aircraft about other VFR aircraft, or special VFR aircraft when visibility is less than 5 km. VFR aircraft, however, must maintain their own separation from each other.
diff --git a/docs/controller-skills/flight-service.md b/docs/controller-skills/flight-service.md
new file mode 100644
index 00000000..6e4bc3f7
--- /dev/null
+++ b/docs/controller-skills/flight-service.md
@@ -0,0 +1,230 @@
+---
+title: Aerodrome Flight Information Service (AFIS)
+---
+
+--8<-- "includes/abbreviations.md"
+
+# Aerodrome Flight Information Service (AFIS)
+
+!!! danger "Event Only Positions"
+ The following positions may only be staffed during approved VATNZ events, or when authorised by the Operations Director.
+
+## Positions
+
+| Position Name | Shortcode | Callsign | Frequency | Login ID | Usage |
+| ------------- | --------- | -------- | --------- | -------- | ----- |
+| Paraparaumu Flight Service | MFS | Paraparaumu Flight Service / Paraparaumu Traffic | 118.300 | NZPP_TWR | Event Only |
+| Milford Flight Service | PFS | Milford Flight Service / Milford Traffic | 118.200 | NZMF_TWR | Event Only |
+
+## Overview
+
+An **Aerodrome Flight Information Service (AFIS)** provides pilots with information to assist the safe and efficient conduct of flight operations at non-controlled aerodromes.
+
+!!! info "ATC vs AFIS"
+ Unlike Air Traffic Control, an AFIS **does not issue clearances or provide separation**. Pilots remain responsible for the safe operation of their aircraft.
+
+!!! note "Supervised UNICOM"
+ Think of AFIS as a supervised UNICOM. The AFIS Operator provides information to improve situational awareness, while pilots remain responsible for making operational decisions.
+
+## AFIS Responsibilities
+
+An AFIS Operator should provide:
+
+- Preferred runway.
+- Surface wind.
+- QNH.
+- Traffic information.
+- Weather information.
+- Known hazards affecting operations.
+
+!!! danger "AFIS Limitations"
+ AFIS Operators **must not**:
+
+ - Issue taxi, take-off or landing clearances.
+ - Sequence aircraft.
+ - Separate aircraft.
+ - Issue ATC instructions.
+ - Amend or issue IFR clearances.
+
+## Traffic Information
+
+!!! note "Pilot Coordination"
+ If pilots are already communicating directly with one another, there is generally no need to repeat traffic information they already know.
+
+## IFR Operations
+
+!!! warning "IFR Clearances"
+ An AFIS Operator may relay an IFR clearance issued by the responsible ATS unit.
+
+ AFIS Operators must **not** issue, amend or cancel IFR clearances.
+
+## Standard Phraseology
+
+The following examples demonstrate generic AFIS phraseology. Aerodrome-specific reporting points, frequencies and local procedures are published on each aerodrome's individual page.
+
+
+### VFR Operations
+
+!!! example "Aircraft Operating Within the AFIS Area"
+
+ **Pilot**: *"[Aerodrome] Flight Service, KAL"*
+
+ **AFIS**: *"KAL, [Aerodrome] Flight Service"*
+
+ **Pilot**: *"KAL, [Aircraft Type], on the apron, 2 POB, to operate [area], [altitude]"*
+
+ **AFIS**: *"KAL, preferred runway SEAL 34, surface wind 340 degrees 10 knots, QNH 1001, traffic is [traffic information]"*
+
+ **Pilot**: *"Runway 34, QNH 1001, copy traffic and conditions, KAL"*
+
+ **Pilot**: *"KAL taxiing to Holding Point Alpha"*
+
+ **AFIS**: *"KAL"*
+
+ **Pilot**: *"KAL lining up SEAL 34"*
+
+ **AFIS**: *"KAL, [traffic] short final SEAL 34"*
+
+ **Pilot**: *"KAL, roger, holding short SEAL 34"*
+
+ **AFIS**: *"KAL"*
+
+ **Pilot**: *"KAL lining up SEAL 34 behind the [traffic]"*
+
+ **AFIS**: *"KAL"*
+
+ **Pilot**: *"KAL rolling SEAL 34 departing [direction]"*
+
+ **AFIS**: *"KAL"*
+
+ **Pilot**: *"KAL operating [area], [altitude]"*
+
+!!! note "Operations Within the AFIS Area"
+ Pilots should remain on the Flight Service frequency whilst operating within the AFIS area or circuit.
+
+ AFIS Operators should continue providing traffic information as required. If pilots are already coordinating directly with one another, there is generally no need to repeat information they already have.
+
+---
+
+### VFR Arrival
+
+!!! example "Inbound Aircraft"
+
+ **Pilot**: *"[Aerodrome] Flight Service, TWN"*
+
+ **AFIS**: *"TWN, [Aerodrome] Flight Service"*
+
+ **Pilot**: *"TWN, [Aircraft Type], [position], [altitude], two POB, joining, full stop"*
+
+ **AFIS**: *"TWN, preferred runway SEAL 34, surface wind 340 degrees 10 knots, QNH 1001, traffic is [traffic information]"*
+
+ **Pilot**: *"Runway 34, QNH 1001, copy traffic and conditions, TWN"*
+
+ **Pilot**: *"TWN joining left downwind SEAL 34"*
+
+ **AFIS**: *"TWN, [relevant circuit traffic]"*
+
+ **Pilot**: *"Copy traffic"*
+
+ **Pilot**: *"TWN left downwind SEAL 34, full stop"*
+
+ **AFIS**: *"TWN"*
+
+ **Pilot**: *"TWN rolling through SEAL 34 to vacate"*
+
+ **AFIS**: *"TWN"*
+
+---
+
+### IFR Departure
+
+!!! example "Relaying an IFR Clearance"
+
+ **Pilot**: *"[Aerodrome] Flight Service, KVY"*
+
+ **AFIS**: *"KVY, [Aerodrome] Flight Service"*
+
+ **Pilot**: *"KVY at the apron, six POB, request IFR clearance to [Destination], 5000 feet"*
+
+ **AFIS**: *"KVY, preferred runway SEAL 34, surface wind 320 degrees 10 knots, QNH 1000, clearance on request"*
+
+ *See **Coordination with the Overlying ATS Unit** below.*
+
+ **AFIS**: *"KVY, clearance available"*
+
+ **Pilot**: *"KVY, ready to copy"*
+
+ **AFIS**: *"[Approach] clears KVY via the [] departure, [] transition, [altutide], squawk [code], clearance not yet valid, remain outside of controlled airspace report ready for departure"*
+
+ **Pilot**: *"Cleared... , KVY"*
+
+ **AFIS**: *"KVY, readback correct, clearance not yet valid"*
+
+ **Pilot**: *"KVY, Ready for departure"*
+
+ *(Once advised by the controlling ATS unit.)*
+
+ **AFIS**: *"KVY, clearance now valid, enter controlled airspace via the GUGAK6 departure "*
+
+ **Pilot**: *"KVY, enter controlled airspace via the GUGAK6 departure, lining up SEAL 34"*
+
+ **AFIS**: *"KVY, passing 2000 feet contact [Approach] [frequency], no reported IFR traffic"*
+
+ **Pilot**: *"Passing 2000 feet contact [Approach], copy traffic, KVY, rolling SEAL 34 departing [direction] climbing to 5000 feet"*
+
+ **AFIS**: *"KVY"*
+
+---
+
+### IFR Arrival
+
+!!! example "Arrival from Controlled Airspace"
+
+ **TMA**: *"KAL, cleared [arrival] arrival for the RNP approach Runway 34 at [Aerodrome], when ready descend 3000 feet"*
+
+ **Pilot**: *"Cleared [arrival] arrival, RNP Runway 34, when ready descend 3000 feet, KAL"*
+
+ *(When established on the approach.)*
+
+ **Pilot**: *"KAL established RNP Runway 34"*
+
+ **TMA**: *"KAL, cleared to leave controlled airspace on the RNP approach Runway 34, contact [Aerodrome] Flight Service on [frequency]"*
+
+ **Pilot**: *"Cleared to vacate controlled airspace on the RNP approach Runway 34, contact [Aerodrome] Flight Service on [frequency], KAL"*
+
+ **Pilot**: *"[Aerodrome] Flight Service, KAL, [distance] [direction] of the field descending through 3500 feet on the RNP approach to land"*
+
+ **AFIS**: *"KAL, [Aerodrome] Flight Service, surface wind 290 degrees 12 knots, QNH 1007, no significant traffic"*
+
+ **Pilot**: *"Copy traffic and conditions, QNH 1007, KAL"*
+
+!!! note "Approach Completion"
+ From this point, pilots should continue making appropriate position reports until clear of the runway.
+
+ The AFIS Operator should provide updated traffic information whenever required.
+
+### Passing Traffic Info
+
+Traffic Info should be passed in the following format.
+
+- Callsign
+- Aircraft type
+- Last reported location
+- Last reported altitude
+- Tracking/Intentions
+
+## Coordination with the Overlying ATS Unit
+
+IFR departure clearances shall be coordinated with the appropriate overlying ATS unit before being relayed to the pilot.
+
+The pilot must **not** be advised that the clearance is valid until the overlying ATS unit has confirmed that the clearance is valid.
+
+!!! note
+ See the individual aerodrome SOPs for examples of local coordination procedures.
+
+## Local Procedures
+
+Aerodrome-specific procedures, reporting points and phraseology are published separately:
+
+- [Paraparaumu Flight Service](../aerodromes/Flight%20Service/nzpp.md)
+- [Milford Flight Service](../aerodromes/Flight%20Service/nzmf.md)