Military Procedures

docs/controller-skills/military.md

@@ -30,10 +30,10 @@ It is the pilots responsibility to remain clear of Restricted Areas, however, th
 #### OCTA
 Outside controlled airspace, it is the responsibility of the controller to provide Safety Alerts on aircraft that will shortly enter, or have already entered, active restricted areas.
 
-!!! example
+!!! phraseology
     **CBW**: "Safety Alert, VFR aircraft overhead Cotter tracking southbound 2500, you will shortly be entering R430 restricted area, clearance not available, suggest immediate left turn to avoid"
 
-!!! example
+!!! phraseology
     **CNK**: "VFR aircraft overhead YCNK 3500 tracking westbound, confirm you will be remaining clear of the R564 restricted area?"  
     To which they will almost always reply with either *"Affirm"* or *"Huh?"*
 
@@ -46,7 +46,7 @@ You must separate all aircraft in controlled airspace by *half the applicable la
 Some Restricted Areas are not always active. Some may be active only on certain days, or certain hours of the day. More info can be found in the [ERSA](https://www.airservicesaustralia.com/aip/aip.asp){target=new}, or on the Restricted Areas window in vatSys
 
 ### NOTAM
-Some Restricted Areas will be activated by NOTAM, most commonly for use by RAAF Virtual. These are available on the [VATPAC NOTAMs Page](https://vatpac.org/publications/notam){target=new}. These Restricted Areas will automatically become active on vatSys with AIRAC updates, so they are visually displayed on the screen.
+Some Restricted Areas will be activated by NOTAM, most commonly for use by [RAAF Virtual](https://www.raafvirtual.org/){target=new}. These are available on the [VATPAC NOTAMs Page](https://vatpac.org/publications/notam){target=new}. These Restricted Areas will automatically become active on vatSys with AIRAC updates, so they are visually displayed on the screen.
 
 ##### Example
 <figure markdown>
@@ -55,11 +55,11 @@ Some Restricted Areas will be activated by NOTAM, most commonly for use by RAAF
 </figure>
 
 ### Aircraft operating inside Restricted Area
-Military aircraft are permitted to operate within their designated Restricted Area as per the relevant NOTAM. Even if this Restricted Area is inside your airspace, you have no control authority over it.
+Military aircraft are permitted to operate within their designated Restricted Area as per the relevant NOTAM. Even if this Restricted Area is inside civil airspace, Civil ATC has no control authority over it.
 
-!!! example
+!!! phraseology
     **ARA**: "DRGN379, shortly entering R604 Restricted Area, identification and control services terminated, frequency change approved. Contact me prior to leaving for airways clearance"  
-    **DRGN379**: "Wilco, DRGN379"
+    **DRGN379**: "Wilco, DRGN379"  
 
 ### ATC Activated Military Airspace
 Most Military TCUs and Tower positions, when online, control airspace that correspond to certain Restricted Area Activations. These are prescribed in the Local Instructions.
@@ -69,10 +69,51 @@ These Restricted Areas may be activated in vatSys, and the controllers of these
 Unless otherwise stated in Local Instructions, Restricted Areas activated for control by Military TCUs and Towers, will become **Class C** airspace.
 
 ## Formation Flights
+### Standard Formation
+A **Standard formation** is defined by more than one aircraft, separated by no more than **1nm** laterally/longitudinally, and no more than **100 feet** vertically, from the lead aircraft. All aircraft in the formation are treated as *one*. Ensure only the leader is squawking Mode C.
+
+!!! note
+    RAAF FIHA AD2 Supps and TERMAs can be found [here](https://ais-af.airforce.gov.au/australian-aip){target=new}
+
+!!! phraseology
+    **VIPR**: "Viper 1, 2, 3, 4, Brisbane Centre, Viper, Maintaining F280"  
+    **ARA**:  "Viper, Brisbane Centre" 
+
+### Close Formation
 Reserved.
 
-## Military Authority Assumes Responsibility for Separation of Military Aircraft (MARSA)
+### Block Formation
 Reserved.
 
+### In-Trail Formation
+Reserved.
+
+## MARSA Operations
+**Military Authority Assumes Responsibility for Separation of Military Aircraft** (MARSA) is a procedure which authorises pilots of military aircraft to assume responsibility for separation between their aircraft and other nominated military aircraft (or military contract civil aircraft) within Australian controlled airspace. 
+
+!!! warning "Important"
+    MARSA **cannot** be initiated by ATC, it **must** be initiated by the pilot(s).
+
+MARSA is to be assigned and terminated on pilots request, and when standard seperation can been applied.
+
+!!! phraseology
+    *MAPL01 is Maintaining F260. DRGN50 is maintaining Block F270-290 above them.*  
+    **MAPL01**: "Request Climb to Block F270-F290, MARSA DRGN50"  
+    **ARA**: "MAPL01, Climb to and maintain Block F270-290, MARSA DRGN50"  
+    **ARA**: "DRGN50, Maintain Block F270-290, MARSA MAPL01"  
+    ...  
+    **MAPL01**: "Request descent to F260 and termination of MARSA"  
+    **ARA**: "MAPL01, Descend to F260, MARSA DRGN50"  
+    *(After MAPL01 is maintaining F260)*  
+    **ARA**: "MAPL01 and DRGN50, MARSA terminated"
+
 ## NOCOM Operations
-Reserved.
+**Non-Continuous Communication** (NOCOM) Procedures are when Military Aircraft discontinue two-way radio communications with Civil ATC. NOCOM Procedures state that ATC Approval is required when Military Aircraft are in controlled airspace. Military Aircraft under NOCOM procedures fall under multiple categories:
+
+- Flights on "Area Freq" when OCTA
+- Flights that are "Radio Silent"
+- Flights that are in SUA
+- Flights that are on nominated route segments, except for short position reports when possible.
+
+!!! note
+    Military aircraft normally operate NOCOM in military Restricted Areas and Class G airspace only. **Do not** permit NOCOM operations in Civil CTA.

includes/abbreviations.md

@@ -304,4 +304,7 @@
 *[SUA]: Special Use Airspace
 *[CPDLC]: Controller-Pilot Datalink Communications
 *[LDA]: Landing Distance Available
-*[TORA]: Takeoff Run Available
+*[TORA]: Takeoff Run Available
+*[MARSA]: Military Authority Assumes Responsibility for Separation of Military Aircraft
+*[NOCOM]: Non-Continuous Communication
+*[AEWC]: Airborne Early Warning and Control