**Change Effective August 1st 2018**: 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.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 prioritizing. Users connected as pilot are allowed 20 minute- 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, will be disconnected from the network. Additionally the user could be suspended and/or online statistics can be deleted.
2.1.9: User behaviour shall reflect the mission statement. All abusive and/or offensive communication on the network 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 a 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. Reconnection shall be coordinated with ATC if applicable, to avoid conflict.
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. (Vallid 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)