Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Military Procedures #398

Merged
merged 13 commits into from
Dec 17, 2024
61 changes: 56 additions & 5 deletions docs/controller-skills/military.md
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand All @@ -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.

!!! 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.
Expand All @@ -69,10 +69,61 @@ 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.

An additional **1nm** must be applied to any lateral separation standards for aircraft in a Standard Formation (Surveillance standards, for example, become *6nm* for Enroute, *4nm* for ADC/TCU).

!!! note
RAAF FIHA AD2 Supps and TERMAs can be found [here](https://ais-af.airforce.gov.au/australian-aip){target=new}

When Military formations make initial contact with a new sector, they will commonly "check in" with all of the members of the formation, to ensure they've all made the frequency transfer. This involves all the individual members of the formation saying their own number in order on the first call. Formations are most commonly referred to by their base radio telephony callsign, without any numbers (eg, VIPR, BLKT, WGTL).

!!! phraseology
**VIPR**: "Viper 1, 2, 3, 4, Brisbane Centre, Viper, Maintaining F280"
**ARA**: "Viper, Brisbane Centre"
Comment on lines +82 to +84
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know that the first part of this transmission is each aircraft checking in on the new frequency, but I'm wondering if it might confuse controllers to see it displayed like this. Should we start with the transmission with just 'Brisbane Centre, Viper...' and leave the check in out? I can see controllers interpreting it as the lead aircraft identifying all of the aircraft which form part of the formation, rather than separate transmissions from four different aircraft.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thats what I had initially before alphadelta modified it + only check in if its not a plannned com switch so I think the orginal idea was better.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah my bad, some crossed wires then. We'll discuss on our end

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thats what I had initially before alphadelta modified it + only check in if its not a plannned com switch so I think the orginal idea was better.

Formations do require a full check in for all members for initial contact with all civil units, whether the comm switch is planned or not. That being said, I have added a clarification line above it to establish what is going on and avoid any confusion for ATC


Any subsequent calls will only be made by the leader, representing the entire formation.

!!! phraseology
**ARA**: "Viper, Climb to F340"
**VIPR**: "Climb to F340, Viper"

### 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.
5 changes: 4 additions & 1 deletion includes/abbreviations.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Loading