Account profile: Place where the registered user or organizational account can check their account information.
An active account: A registered user or organisational account which has been active as a pilot or controller on IVAN within the past 3 months.
Administrator: A network status given to specific staff (Governors and some Logistics staff).
Channel Admin: Status assigned to the controller that creates a new channel for his position in the TeamSpeak 2 software client.
Connection: An active Internet connection to the IVAO Network (IVAN).
Department: Organizational entity being in charge of a set of specified tasks such as training, events or operations.
Division: Organizational entity that is responsible for a specific country or region.
Division staff: Member that has an assigned staff position at the divisional level.
Event account: 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 member rating.
GCA: Guest Controller Approval. A permission that allows a foreign controller to provide service in a division which differs from the member's registered division.
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 by the Executive Council and Departments, who are responsible for 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 a period longer than 3 months.
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: Organizational entity that is responsible for a specific country or region, but that is not fully independent from the support of the HQ; Entity that is expected to become a division after a probation period.
Multi-country Division: Organizational entity that is responsible for multiple countries or a region where shared resources are used to manage the area.
Observer: Type of connection restricted only to observe and listen to activities in IVAN.
Organisational account: Account with the purpose to be 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 by using IVAC or IVAP.
Reconnection: Re-establishing a connection to the network in order to resume a previously started flight.
Registration: The voluntary submission of first and last name, valid e-mail- and 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.
Senior staff: Members that have an assigned position of a Department at an HQ level who give assistance to divisions and are responsible for areas where there is no active Division.
Staff: Users with a specific responsibility in a Department. See Division Staff and Senior 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 subject to review by Executive. 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 R&Rs. Only Supervisors and Administrators can view this information.
Unicom: Frequency exclusively used by text to coordinate with other users in IVAN when there are not available ATCOs (122.800).
Users: Τhe natural or legal person registered in IVAO network.
2.1.1: Users connecting to IVAN shall use their real first and last name written in full.
2.1.2: Multiple connections are prohibited except for IVAO designated staff as a temporary requirement for training, exams or software development and for organizational 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.
2.1.3: The primary language for text and voice communication on the network is English. All users of IVAO need to have and apply a basic proficiency in aviation English both in voice and text. Divisions may allow or demand the use of additional languages and will have to publish these requirements on their website.
2.1.4: Users shall only use approved software downloaded from the IVAO website to connect to the IVAO network and shall ensure he/she has 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 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, -behaviour and -innuendos. Offenders 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.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.
2.2.4: An ATS unit shall not control outside its area of responsibility.
2.2.5: Once a user has connected as ATC he shall coordinate with other ATC about the handover of traffic, a user shall not force-act a pilot under control of another controller. Traffic shall be transferred between controllers by using the handoff option of 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 impose 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 no reason for ignoring ATC instructions unless instructed by IVAO trainers/examiners.
2.3.3: Pilots shall never connect on a runway or 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 activated during flight. If during flight no ATC is available pilots shall monitor “UNICOM” freq. 122.800 on their radio and announce their intentions on “UNICOM” to other pilots.
2.3.6: Simulating ‘hijack' (SSR code 7500) is prohibited.
2.3.7: 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 observer shall use the _OBS suffix and never include one of the ATC suffixes or staff callsigns. 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: With exception of the CC TeamSpeak server all other IVAN voice servers shall only be used when connected to IVAN as pilot, ATC or observer. Users shall use their IVAN callsign when connected. In case of a controller change the Channel Admin (CA) rights shall be transferred to the new controller if possible.
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 authorized administrator on behalf of the executive. 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 division or HQ website and require at least an ADC rating for the operator and the appropriate responsible ATC station online. The vehicles shall use the callsign format “ICAO CODE”_“TYPE”_“NUMBER” (example: ZZZZ_FM_01 meaning ZZZZ FollowMe 01).