ATC rules (English)
IVAO establishes guidelines for the users of the network as described in its Rules & Regulations (hereinafter R&R), leaving space in some of them to be specified by each Division. In this section we will specify those that apply to the airspace and premises of the Spanish Division.
See the R&R on the wiki:
- Rules: https://wiki.ivao.aero/en/home/ivao/rules
- Regulations: https://wiki.ivao.aero/en/home/ivao/regulations
Rules
→ 2.1.3: For all ground stations, the local language can be used based on local regulations. However, the English language shall be used, on request from any user. All users of IVAO need to have and apply a basic proficiency in aviation English both in voice or text. For air-to-air communication, use of the English is compulsory when traffic in close proximity is not proficient in the local language.
Implementation: In addition to English (mandatory), communications are authorised in Spanish, the latter being therefore a mandatory language for controllers and elective for pilots.
→ 2.2.1: Before connecting users shall ensure they are familiar with and able to apply the appropriate local procedures, prepare the required information and are able to be online for at least 30 minutes.
Note: Local procedures are defined on the web pages of each FIR. For reasons of simplicity, meteorological considerations, timetable or availability of scenarios, some of these procedures may be different from those published in the AIP, but in all cases the procedures of the Spanish Division shall take precedence.
→ 2.2.2: Divisions may restrict ATC positions by a FRA and/or GCA. These restrictions shall be published on the respective division website.
Implementation: All Spanish ATC units will be restricted by FRA, having the corresponding rank is mandatory -as well as the divisional GCA in case of belonging to another Division- to serve in each one.
If you belong to another Division and want to control in Spain, apply for GCA clearance by following these steps.
→ 2.7.1: Vehicles other than aircraft, used for aviation simulation purposes, are only allowed as published on the divisional website. The vehicles shall use the callsign format “ICAO CODE”“TYPE”“NUMBER” (example: ZZZZFM01 meaning ZZZZ FollowMe 01).
Implementation (daily): Follow Me vehicles may be available at any aerodrome as long as there is at least one active local unit (en-route / CTR positions are excluded) and all users involved in the operation of such a vehicle comply with the general rank restriction (both drivers and ATCs must be ADC or above).
Application (events with shift schedule): AS3 users will be able to connect as "follow-me" vehicles when the event coordinator has scheduled their participation or they participate in an enabling course (always notified by NOTAM).
Note: Drivers shall be aware of the general and local procedures provided for controllers, with special emphasis on compliance with rules IR.2.1.2 and IR.2.2.1. Finally, drivers shall only occupy the ATC frequency when operating outside the platforms, leaving the rest of the coordination to a private channel (Discord).
The following maximum vehicle speeds are established:
- Platform: 30 km/h (20 MPH)
- Taxiways: 50 km/h (30 MPH)
- Runways: 100 km/h (60 MPH)
Racing or any other reckless use of the vehicle is strictly prohibited.
Examples of application:
- Double connections (e.g. as ATC and as vehicle at the same time) ar not allowed.
- If the GND controller is ADC or higher, but TWR is not, the vehicle shall only be able to transit the apron and taxiways.
- If only TWR is present and this is ADC or above, the vehicle may transit the entire movement area.
- If GND or whoever takes over is AS3 or below, there can be no vehicle operations, even if the TWR ATC is a senior ADC.
- At an airport with different taxiing and apron direction controls, the vehicle may only operate in the areas of responsibility of controllers who are ADC or above.
Regulations
→ A.2.1.2: Users shall follow published IVAO NOTAMs.
Note: The use of real NOTAMs that are not implemented in IVAO-ES is prohibited. IVAO Spain encourages the simulation of some temporary modifications published in the AIP amendments and supplements. For this purpose, an application and implementation regulation has been drafted that establishes the conditions for a real modification to be implemented in IVAO-ES. In all cases, an ATC is not authorised to refuse a procedure to a pilot who does not wish/cannot comply with that NOTAM.
→ A.2.3.1: It’s not required for area controllers to perform ATC duties in Terminal Control or Aerodrome Control airspaces when the appropriate controllers are not online, unless division or exam procedures describe otherwise. If a restricted coverage is being applied, the controller shall clearly state this in the ATIS.
Implementation 1: In the Spanish Division this regulation does not apply, with higher positions having to take care of any responsibilities of lower non-active units according to a top-down hierarchy. This regulation may be overridden in situations of heavy traffic for en-route positions (CTR) during events at the coordinator's discretion, stating: "No control on XXXX due to divisional event (A.2.3.1)" in the ATIS.
Note: Two parallel hierarchies are distinguished: CAG (civilian traffic) and CAO (military traffic), so that higher CAO units will only serve lower military units (CAO). In the absence of the homologous CAO position, all transits will communicate with the corresponding civilian unit (CAG), and may continue to operate under CAO rules as long as it does not interfere with civilian traffic in the airspace.
Implementation 2: The opening sequence of the ATC positions in each facility is indicated in the corresponding local procedures website. CAVOK students that have received approval from their tutor will be able to connect in certain GND positions without the TWR position being connected.
→ A.3.2.1: Users are encouraged to plan and schedule anytime when ATC service is bound to be provided. For events, divisions may create special systems for schedule and users shall follow the details in event announcement.
Implementation 1: For divisional events the ATC Operations department may authorise the creation of a shift schedule which shall be properly announced together with all other information relevant to the event and coordinated by the FIRs concerned. In all cases, such shift schedule shall be published prior to the start of the event, so that other cleared controllers can join at the last minute and any subsequent disputes can be resolved by the network SUPervisors. According to the general regulation, when this occurs, the ATC Scheduler will become invalid.
If you want to join an event with a shift schedule at the last minute, don't hesitate to contact the event coordinator (also announced on the shift schedule) so that he/she can assign you to the position where you can be of most help to your fellow controllers.
Most events, whether using shift schedules or bookings, usually change the FRAs of the affected positions. For more information, consult the publication made by the Events department and the NOTAMs of the ATC Operations department.
Implementation 2: In some divisional events, provided that the creation of a quadrant has been established, priority for allocation of control positions may be given to members of an ATC Team. This priority must be clearly announced along with all other information relevant to the event and coordinated in advance with the FIR concerned.
Implementation 3: In events with shift schedules and FRA restrictions, in case any relevant position of the event cannot be covered, the ATC Department on request by FIR staff may grant FRA exemptions to users with knowledge in such positions, who are interested in participating.
Implementation 4: SEC ranked exams - due to their specific requirements - could be considered as an "event", triggering a series of special restrictions and allocation of adjacent positions. These changes and conditions will be announced via NOTAM.
→ A.3.2.2: Schedule slots for ATC have priority for the user that booked it. However, the user can only make use of the booked facility until 10 minutes after the booking start time, for examinations this is extended to 1 hour and for events is reduced to 5 minutes. After that, if the member is not online, any other user is allowed to login to the position.
Implementation 1: Each user may book a maximum of 4 hours in the booking system (ATC Scheduler). The division staff may delete without prior notice those that incur in abuses such as unfulfilled periodic bookings, as long as this deletion is approved by ATC HQ and the Executive.
Implementation 2: The priority on the 1 hour extended reservation for exams will also apply to training sessions.
Implementation 3: Reservations relating to schedulled exams or training sessions shall invalidate any reservation laterly scheduled in any adjacent position in accordance with the evaluation criteria described in the Training Department regulations for each rank and may not be occupied or express permission to occupy by the person in charge of such session is required.
Note: The adjacent position to each sesion and rank can be found at the end of the following documents:
-ADC: https://es.ivao.aero/training/departamento/controlador/adc
-APC: https://es.ivao.aero/training/departamento/controlador/apc
-ACC: https://es.ivao.aero/training/departamento/controlador/acc
The coordinator is a figure used in divisional events. He/she is responsible for ensuring compliance with the shift schedule. He/she assists the ATCs by helping them to solve any problems detected, coordinating with other units / FIRs to regulate the flow of arrivals / departures, as well as any other coordination / assistance action necessary for the proper functioning of the ATC service at the event. As a general rule, the position of coordinator should be assumed by some FIR Staff involved, although it could be assigned to any person from the ATC Team knowledgeable of the sector. The coordinator will remain connected as OBS or Staff for the duration of the event.
→ E.5.1: Users participating in events integrating the IVAO Events Support Award must comply with the event’s requirements which are located in the forum in order to be eligible for the point towards the described award. Users participating in events integrating the IVAO Connect Events Award must comply with the event’s requirements which are located in the forum in order to be eligible for the point towards the described award.
Implementation : All participants in any event in the Spanish Division must comply with the requirements set out in the forum post about the event, including always using the correct aircraft for the airfield involved. The event must be conducted in accordance with all IVAO rules, regulations and policies, being of special interest to note compliance with IR 2.3.1