Account profile: Place where the registered user or organisational account can check their account information.
Administrator: A network status given to holders of specific staff positions.
Air-to-air communication: two-way communication between aircraft in the air.
An active account: A registered user or organisational account which has been active as a pilot or controller on IVAN for at least 30 minutes within the past 3 months.
Channel Admin: Status assigned to the controller that creates a new channel for their position in the TeamSpeak 2 software client.
Connection: An active Internet connection to the IVAO Network (IVAN).
Department: Organisational entity being in charge of a set of specified tasks across IVAO such as training, events or operations.
Departmental staff: Members that have an assigned position of a Department at HQ level who give assistance to divisions and are responsible for areas where there is no active division.
Division: Organisational entity that is responsible for a specific country or region.
Division staff: A user that has an assigned staff position at divisional level.
Event account: An account issued by the membership department to an IVAO division for use during events, these accounts may have multiple connections to the network.
Force-act: An automated message sent by an active controller to a pilot that is within their airspace requesting pilot contact for the purpose of providing ATC services.
FRA: Facility Rating Assignment. A system used to filter the connection to ATC positions by rating. They are set to ensure a minimum level of expertise for the position according to the user rating.
GCA: Guest Controller Approval. A permission that allows a controller to provide an air traffic control service in a division which differs from the user’s registered division.
Ground station: stations or locations on the surface of the earth that provide an ATS (Air Traffic Service) to aircraft which can consist of a flight information service, alerting service, air traffic advisory service and/or air traffic control service.
GUARD frequency: Frequency that can be used by the pilot to request assistance in case of emergency (121.500 MHz).
Handoff: Air Traffic Control procedure that consists of transferring control of an aircraft to another air traffic controller.
HQ/Headquarters: Headquarters is composed of the Board of Governors, the Executive Council and Departments, who are responsible for Strategy, Network Operations, Management, and providing assistance to divisions in their tasks.
Inactive account: A registered user or organisational account which has been inactive as pilot or controller on IVAN for less than 30 minutes for a period longer than 3 months.
Information storage: Storage of information as described in the privacy policy and in accordance with Belgian law.
IVAN: International Virtual Aviation Network. The simulation network provided by IVAO.
Local procedures: Aeronautical procedures specific for a division or aerodrome and published on the divisional website.
Mini Division: Organisational entity that is responsible for a specific country or region, but that is not fully independent from the support of HQ. The entity is expected to become a division after a probation period.
Multi-Country Division: Organisational entity that is responsible for multiple countries or regions, where shared resources are used to manage the area.
Observer: Type of connection restricted only to observe and listen to activities within IVAN.
Organisational account: Account with the purpose of being used by organisations, these accounts may have multiple connections to the network.
Private conversation: Any conversation which occurs on IVAN that is between 2 or more people that is not visible to any other person who is not part of that conversation.
Private message: Message sent to a particular user, or users, by using an IVAO controlling client or an IVAO pilot client.
Reconnection: Re-establishing a connection to IVAN in order to resume a previously started flight.
Registration: The voluntary submission of a legal first and last name (as listed on an official government document), valid e-mail address, and the collection of the user's IP address. Also includes an agreement to adhere to all rules and regulations.
Sandbagging: Is the action of leaving an active IVAN connection unattended.
Scheduling System: System to be used to schedule an Air Traffic Control position on the network, to a specific location and timeframe, which supersedes an active connection with same conditions in favour of the scheduled user.
Staff: Users with a specific responsibility in a Division, Department, the Executive Council or Board of Governors. Also see “Division Staff” and “Departmental Staff”.
Supervisor: A network rating granted to individuals in order to help connected users in IVAN. Supervisors are also responsible for enforcement of the rules and regulations of IVAO. See also “Suspension”.
Supervisor note: An entry into the account profile of a user regarding a non-punitive action. Only Supervisors and Administrators can view this information.
Suspension: A disciplinary action applied to any user who violates the rules and regulations. Only Supervisors and Administrators can view this information.
Text-only traffic: users connected neither with audio nor with voice to communicate.
Unicom: frequency used to coordinate with other users in IVAN when there is no ATC available (122.800).
Users: Τhe natural or legal person registered in IVAO network.
2.1.1: Users connecting to IVAN shall use their first and last name that was provided upon registration, which is as written on government issued forms of identification.
2.1.2: Multiple connections are prohibited except for IVAO designated staff for training, software development, supervisors carrying out a supervisory function, and for organisational or event accounts in which case the number of allowed connections is noted on the account profile. Multiple connections by staff shall be stated in the ATIS or Flightplan remarks and should be only for the duration needed to complete the required task.
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.
2.1.4: Users shall only use approved software downloaded from the IVAO website to connect to the IVAO network and shall ensure they have basic knowledge on how to use this software.
2.1.5: Users shall have basic knowledge of aviation procedures. This includes but is not limited to flight procedures, airspaces, radio-telephony.
2.1.6: The GUARD frequency (121.500) shall only be used for emergency communications. It is prohibited to use GUARD for any other type of communication. Informing pilots that ATC is online or requesting pilots to contact ATC are not emergency communications.
2.1.7: If a user requires assistance on the network the user can use the .wallop command to request assistance from a supervisor. The .wallop command shall include a short description of the situation. Users shall always follow supervisor or administrator instructions.
2.1.8: Users connected to IVAN shall respond to voice and/or text communication which are considered equal and free of prioritising. Users connected as a pilot are allowed 15 minute breaks and ATC are allowed 5 minute breaks if traffic permits. Users not responding to a supervisor call via text within the maximum permitted break time or shorter if circumstances deem necessary, shall be deemed to be sandbagging and will be disconnected from the network. Additionally, the user could be suspended according to the suspension table and/or online statistics could be deleted.
2.1.9: User behaviour shall reflect the mission statement. All abusive, defamatory and/or offensive communication on IVAO related communication channels (including, but not limited to, Teamspeak, social media and Discord) whether public or private, regardless of transmission means, will not be tolerated. Usage of and communication in the network is limited to information and material concerning IVAO, e.g. VA publicity, is prohibited.
2.1.10: IVAO prohibits all forms of criminal activity and dissemination/transmission of harmful information including, but not limited to, pornography, grooming, sexual propositions, inappropriate behaviour, and sexual innuendos which are outlined in our Safeguarding Policy to assist in prevention. Users may face sanctions up to and including a referral for criminal prosecution. Reasonable attempts for parental notification of minor victims shall be made and for minor suspects, considered.
2.1.11: Simulation of real world ethnic, political or religious conflicts or problems including simulation of any form of war or aggression, are strictly prohibited.
2.1.12: Recording/streaming of user identifiable data, in violation of the privacy policy, is prohibited. Users are permitted to record, transmit and/or stream all user generated content provided this content is not in violation of the IVAO privacy policy and/or subject to copyright. Users cannot record/stream private conversations without the consent of the participants of that conversation. Users recording or streaming shall note this as a remark in their flightplan or ATIS.
2.1.13: Users are prohibited to be connected to the IVAO network, whilst under the influence of alcohol or other physically impairing substances.
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.
2.2.2: Divisions may restrict ATC positions by an FRA and/or GCA. These restrictions shall be published on the respective division website.
2.2.3: When connecting as ATC, users shall use the appropriate frequency, station name and callsign as published on the (division) website. Available ATS units and their use are subject to and part of the local procedures set by staff members.
2.2.4: A controller shall not attempt to control, assume responsibilities, or impose restrictions beyond those dictated by airspace class or local procedures.
2.2.5: Once a user has connected as ATC he shall announce his connection to adjacent ATC and coordinate traffic handovers. A user shall not force-act a pilot under control of another controller. Traffic shall be transferred between controllers using the handoff feature within the software.
2.2.6: ATC shall request pilots to contact them by using a force-act or private message if required. GUARD shall not be used for this purpose.
2.3.1: Pilots shall read back and comply with ATC instructions and flight procedures unless these instructions pose immediate danger to the simulated flight.
2.3.2: Pilots shall contact applicable ATC and/or reply to ATC calls or force acts. Simulation of a radio failure (SSR code 7600) is not a valid reason to disregard ATC instructions. The only exception to this when instructed to do so by a trainer or examiner during an active training or exam session.
2.3.3: Pilots shall never connect to the network on a runway, taxiway or in the air. To avoid conflict, re-connection shall be coordinated with available ATC prior to connecting.
2.3.4: Pilots shall use a valid (military or civil) callsign when connecting, and file a complete and valid flight plan before flight, following ICAO standard.
2.3.5: Pilots shall have their transponder “ON” during flight, if equipped.
2.3.6: If no ATC is available, pilots must monitor and report on the “UNICOM” frequency 122.800. For air-to-air communications, messages shall be limited to broadcasting a pilot’s position and/or intentions to assist with the avoidance of conflict and sequencing.
2.3.7: Traffic communicating via voice must consider that text-only pilots will not receive their reports, therefore they should establish proper coordination or ensure separation with close proximity text-only traffic.
2.3.8: Simulating ‘hijack' (SSR code 7500) is prohibited.
2.3.9: Pilots shall ensure they fly with a simulator rate of 1 regardless if this is adjusted manually or automatically.
2.4.1: Users connecting as observers shall use the _OBS suffix. Users connected with the _OBS suffix shall never use the created ATC channel/frequency for text or voice communication. (Valid observer callsigns are for example: EHAM_OBS, BP_OBS, EGLL_1_OBS).
2.5.1: Only IVAN voice servers shall be used when connected to IVAN as a pilot, ATC or observer. Users shall use their IVAN callsign when connected.
2.5.2: Playing of music and/or other broadcasting of sound, not related to the simulation or noise, obstructing clear communications, is prohibited. Channel restrictions by users are prohibited, with the exception of channel restrictions published in the department guidelines.
2.5.3: Users shall not use voice distortion software to change their transmitted voice.
2.6.1: Users violating the IVAO rules and regulations can be subject to a suspension issued by a supervisor or an administrator authorised by Local Services, on behalf of the Executive Council. Appeal to the issued suspension shall only be done as described in the email received after suspension.
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).
2.7.2: In the absence of published divisional criteria, and areas outside active divisions, vehicle connections will require at least an ADC rating for the operator and the appropriate responsible ATC station online.