¶ Introduction
The present document, created together between Special Operations and ATC Operations departments, aims to guide staff when regulating ATC stations in Airspaces that are purely military and airspaces where combined Mil/Civ operations take place. The following cases are currently covered:
- Airport Use.
- Airspace Use.
- Airspace managed by Military ATC Units for Mil. use ADs.
- Airspace managed by Military ATC Units for Mil. or joint use ADs.
- Airspace managed by Civilian ATC Units for joint and Mil. use ADs.
- Military airspace and the “Top down” rule.
¶ SOD regulations
https://sod.ivao.aero/regulations
¶ 1.- Glossary
¶ GAT.:
General air traffic (GAT) encompasses all flights conducted in accordance with the rules and procedures of the International Civil Aviation Organisation (ICAO). These may include military flights for which ICAO rules satisfy their operational requirements.
¶
OAT.:
Special Operations on IVAO are defined as aerial military operations, aerial work, and other aviation flights (activities, operations) that are performed in accordance with rules and procedures other than those that fully comply with ICAO SARPs or other civil rules and procedures. Controlling military units and other units other than civil ATS responsible for aforementioned flights (activities, operations) also fall under the framework of Special Operations.
Examples include military flights operating under military rules, firefighting, police operations, search and rescue operations, aerobatic flights & flying display, construction work, aerial photography, air ambulance, and other types of state, specialised and aerial work (this list is not exhaustive).
¶ Military Airspace:
MCTR, MCTA, MATZ... or those for which the responsible ATC unit is part of the military. These include TWR, GND, APP... stations for Airports of military use:
Bear in mind that an airspace being classified as military does not mean all operations will be conducted under OAT.
¶ AoR.:
Area of responsibility.
¶ Airport Use:
Primary use of the airport in question.
¶ Joint-Use Airport:
The term "joint-use airport" means an airport owned/operated by the Department of Defense/Ministry of defense/Military or equivalent state agency, at which both military and civilian aircraft make shared use of the airfield.
Bear in mind a Military use airport might admit civilian traffic regularly or under certain conditions and yet is not to be considered Joint-Use.
¶ 2.- Divisions with an SO Order
¶ Military Airspace
Those divisions where an S.O. order is in force can decide whether to establish special requisites to allow connection on purely Military ATC positions.
E.g.: (Airbase)_TWR / _APP or _ MIL_TWR / MIL_GND...
Military ACC stations regardless of having _MIL_ in their connection ID.
¶ Joint Use Airport/Airspace
Divisions shall not restrict members from connecting as military ATC units that are the only available ATC position to provide ATC service to civilian traffic in that specific joint use airspace/AD.
Special requirements might be applied for events or special activities taking place.
E.g.: (Joint use AD.)_APP or (Airbase)_APP.
A Military unit providing Approach services to both civilian and military traffic that share the same AD (Regardless of GAT/OAT). Or to any combination of Mil./Civ. ADs below the Mil. Airspace*.
*Uncontrolled ADs. not to be considered.
Divisions are encouraged to use the FRA system to reflect these complexities instead. Divisions can restrict users from connecting on _MIL_TWR; _MIL_GND; _MIL_APP...etc. positions that exist for these Joint use ADs./Airspaces. It is also possible to restrict connection on ATC units tasked exclusively with OAT. functions such as GCA/PAR/SRA approach radars.
E.g.:
Given a Joint-Use aerodrome XXXX, divisions can restrict connection on XXXX_MIL_APP. As long as XXXX_APP or an alternative exists to provide APP service to civilian traffic.
For those aerodromes that share dual ICAO codes, one for the military and one for the civilian side, divisions might restrict connections under the military ICAO code.
E.g.: Brussels Airport and Melsbroek Airbase, EBBR and EBMB.
Palma de Mallorca and Son Sant Joan, LEPA and LESJ.
¶ Military Airspace below Civilian ATC Units
When a military AD. or airspace lies below the AoR of a civilian ATC Unit:
(E.g.: There is an airbase with its Military CTR controlled by a military unit but lying below a Civilian managed TMA where a civilian ATC unit provides Approach services for both).
Divisions cannot restrict connections in the civilian position. Military traffic will be responsible to contact and follow ATC instructions at least until released by the civilian ATC unit.
Divisions may restrict the AoR (Or its top-down application) of the Civilian ATC to exclude the purely military portions of airspace below its AoR. If such restrictions exist, divisions must define procedures defining how and when to release/establish control of aircraft entering/departing military airspace.
If no procedures are published and available, no restriction shall take place.
¶ 3.- Divisions without an SO Order
No restrictions
Those divisions without S.O. order shall not restrict connection as Military ATC units for their members.
Whenever general traffic and SO. traffic coincide in any type of airspace, the member connected as ATC can choose to provide General Air Traffic services to both based on his knowledge and experience to ensure safety of operations.
Lack of restrictions does not waive IVAO R&R regarding knowledge of local procedures.
¶ 4.- Airspace Outside Divisions
No restrictions
HQ ATC Operations department does not restrict connection as Military ATC units for members.