Terms of use

3.1 - The IVAO network is offered to you free of charge conditioned on your acceptance of the IVAO rules and regulations published on our website. Your use of the network constitutes your agreement to all IVAO rules and requirements. IVAO reserves the right to change the rules and requirements without notice. You are responsible for regularly reviewing these rules and regulations.

3.2 - As a condition of your use of the IVAO services, you will not use the network to spread unlawful material or information, including information that incites discrimination, hate or violence towards one person or a group because of their belonging to a race, a religion or a nation. You will not use the network for use prohibited by the rules and regulations. Abusive, inappropriate, profane, discriminating, obscene and indecent language is not tolerated.

3.3 - It is not allowed to restrict or inhibit any other user from using and enjoying the network services.

3.4 - IVAO makes no warranty that any IVAO service will be uninterrupted, timely, secure or error-free.

3.5 - Membership with IVAO is considered a privilege and a honor. If in the opinion of HQ, a member does not meet the requirements or abuses the Rules and Regulations, then HQ will make the sole determination of their membership status, up to and including termination of their membership account.

4.- General Rules and Regulations

4.1.1 - Only registered Users are allowed to utilize the services of IVAO and IVAN..

4.1.2 - Register at www.ivao.aero to obtain the user number and password necessary to connect to the network.

4.1.4 - You must use your real first- and last name during registration, it is not allowed to create a false identity for the purpose of misleading others.

4.1.5 - You must use your real e-mail address that is been given from your provider.

4.1.6 - To remain a registered user of IVAO a certain on-line activity is necessary. Users should at least log-in once every 3 month to preserve their "active" status. Users, not utilizing the IVAO services for more than 12 months, will be removed from the user lists.

4.2.4 - To monitor the on-line traffic IvAe "The Eye of IVAO", WhazzUp and ServInfo may be used.

4.3.1 - When connecting to the network you must use your real first- and last name, nicknames are not allowed.

4.3.4 - Staff members are allowed to have two connections opened at the same time as long as this is functional to perform a valid staff-task. This staff-task has to be mentioned in the ATIS or in the Flight Plan-remark. Valid staff-tasks are software development, training- and exam sessions. Supervisors may fly and temporary connect via IvAc to perform Supervisor tasks when no other supervisors are available.

4.4.1a - Country's without ICAO language should use English as mandatory language

4.4.1b - Country's with ICAO language should use English as the mandatory language and the country ICAO language. Both can be used.

4.4.1c - ICAO languages are English, Spanish, French, Arabic, Russian, and Chinese.

4.4.5 - On the IVAO network Hi-jacking, war simulation and all other forms of aggression are not allowed.

4.4.6 - Behave friendly and respectful, be patient with new pilots and controllers.

4.4.7 - While connected to the network, do not leave your PC for more than a few minutes.

4.4.8 - Users not responding to communications within a reasonable time (10 - 15 mins) will be disconnected from the network.

4.4.9 - Against users, obstructing the normal flow of traffic (f.i. connect while on Runway), immediate action can be taken.

4.4.10 - Within your capabilities, try to execute the simulation "as real as it gets".

4.4.11 - Follow up the instructions of supervisors and administrators. Their advice must be followed to ensure that everyone can enjoy the simulation

4.5.1 - In some cases the account of one user can be suspended for a period of time, which means it will be no possible connect to IVAN while suspension is active.

4.6 Ratings for Controllers and Pilots

4.6.1 Ratings for pilots and controllers shall be as described in the HQ Training Department section, "Basic Ratings", "Advanced Ratings", and "High Level Ratings".

4.6.2 Requirements for practical examinations for controllers "C1 to C3" and for pilots "FC to SFC" shall be as described in the HQ Training Department section, "Unit Requirements" and "Pilot Requirements", respectively.

4.6.3 Ratings of Ix or CCx are considered as Instructor ratings and require the member to full fill additional responsibilities as defined by the Training Departments at the HQ and/or Division level.
ĄĄ

5.- Controllers Rules and Regulations

5.1.1 - Controllers must have basic knowledge of the aviation communication procedures.

5.1.2 - Controllers must be familiar with the procedures of the airspace they want to control.

5.1.3 - Controllers must have installed the ProController or the IvAc software and be familiar with the use of it.

5.1.4 - If you are new or unfamiliar with the airspace you should connect as an "Observer" and study the material for that airspace which can be found in our database or on the website of the division the airspace belongs to.

5.1.5 - As an Observer you are not allowed to use "valid" callsign extensions (CTR, APP, TWR etc.) use the extension _OBS instead. You are also not allowed to communicate on any text or voice frequency in use by pilots and regular ATC.

5.1.6 - ATC positions should be manned in the order xxxx_CTR, xxxx_APP, xxxx_TWR, xxxx_GND (On the place of the xxxx's you should place the ICAO-identifier of the airspace).

5.1.7 - At certain airports FRA's (Facility Rating Assignments) are in effect. This means that on certain main Airports ATC must have a specific rating in order to be allowed to take a position. Example of a FRA could be: "The xxxx_APP position may only be taken by S3 or higher." This means that if you have the rating of S2 you are allowed to log-in as _DEL, _GND and _TWR on that particular Airport, you are however not allowed to log-in as _APP and _CTR. If there in no _APP controller available you may ACT as _APP if you feel confident enough, but by using FRA's the _APP and _CTR positions remain available for more experienced ATC, also the Pilots will know that you are not an experienced _APP or _CTR controller.
If applicable you will find information about FRA's on the main webpage of the Division the Airport belongs to.
Active FRA's can also be checked here

5.1.7a - All UPPER positions such as Maastricht Control (EUR_M_CTR) are restricted to Instructor 1 or higher ratings, unless a written permission was granted by TD/TAD/AOD/AOAD or HQ.

5.1.8 - Before connecting check "Who is on line?" and take the highest available position you are able and allowed to handle.

5.1.9 - Use only valid extensions, these are _CTR, _APP, (_DEP), _TWR _GND, _DEL, _FSS.

5.2.1 - Do not connect unless you are sure that you can stay controlling for at least 30 minutes.

5.3.1 - You are not allowed to control outside your own area (f.i. TWR) , unless the other area (APP) is not occupied.

5.3.2 - As soon as new ATC arrives for the foreign area (APP) you have to hand over all traffic in that area.

5.3.3 - Controllers should only use frequencies, callsigns and other information as they are published in the IVAO-database.

5.3.4 - Never use the emergency- (or guard-) frequency (121.50) other than for emergency situations.

5.3.5 - Update your ATIS on a regular basis, at least once every hour, in order to adapt procedures to the current weather conditions.

5.3.6 - Handover of aircrafts should be done only by coordination (via private chat) with other ATC.

5.3.7 - Taking aircrafts out of control of other ATC by means of asking the pilot, via guard- or private message, to transfer (stealing) is not acceptable and prohibited.

6.- Pilots Rules and Regulations

6.1.1 - Pilots must at least be able to take off with an aircraft and land it again on an airport.

6.1.2 - You also must be able to comply with simple ATC instructions like "turn left heading 220" or "descent and maintain FL 110" to participate in the simulation.

6.1.3 - Pilots must have installed the Squawkbox or IvAp software and be familiar with the basic use of it.

6.1.4 - Position your aircraft on the airport in a position that it is not on a Runway nor on a Taxiway. This prevents that you are causing a conflict when connecting to the network.

6.3.1 - It is not allowed to squawk standby except while on the the ground prior to initial contact with ATC.

6.3.2 - Before every flight a flightplan must be filed through IvAp/Squawkbox, and write your pilot rating in the Remark field.

6.3.3 - If you are new or inexperienced indicate this in your flightplan. ATC will help you..

6.3.4 - If there is no ATC available tune your Comm-radio to the "Unicom"-frequency (122.80).

6.3.5 - Check for ATC on a regular basis and contact the appropriate ATC as soon as one is available or if you are requested to do so.

6.3.6 - In exceptional cases FRA's (Facility Rating Assignments) can be in effect. FRA's are a kind of restrictions which can be in effect for instance during a very busy fly-in. An example of a FRA could be : "Pilots with Rating of FFO (First Flight Officer) or lower are not allowed to land at EHAM airport from 18.00 - 20.00 Zulu - the alternative Airport is EHRD".
You will find this FRA in the ATIS of the ATC in the form "FRA - no FFO at EHAM 18.00 - 20.00 Z (alt. EHRD)"
Active FRA's can also be checked here

6.3.7 - Never use the emergency- (or guard-) frequency (121.50) except in an emergency situation.

6.3.8 - Under normal situations Pilots must follow and readback ATC instructions.

6.4.1 - Under special operations we catagorise all aviation other then civil aviation. Examples are coastgard, resque- and military aviation. This kind af aviation is part of the real world and therefore part of the simulation. Not allowed on IVAO are simulations of terrorism and acts of war. Although terrorism and war excist in the real world we do not allow the simulation of any kind of aggression or armed violance on our network. For further information on this issue see the rules and regulations for Special Operations.

7.- Rules and Regulations for the use of voice communications.

7.1 - The use of voice communication is recommended because of the higher level of realism. There are however a lot of reasons why users do not (or are not able to) use voice communication, so on IVAO the use of voice is not preferred over the use of text. Both type of users should be handled and replied to equally.

7.4 - The use of IVAO voice servers is only allowed when you are connected to IVAN at the same time, they may only be used for voice communication simultaneously with the use of approved software.

7.5 - As an exception channels may be opened by Virtual Airlines as company channels, by Special Operations Groups for coordination purposes and by staff-members to execute staff-meetings.

7.6 - ATC Services shall use their ICAO identifier of their airspace and position for their call sign as the voice channel, e.g. EBBR_APP or KDFW_TWR. The use of a frequency, e.g. 112.80 or 113.10, as a TeamSpeak voice channel for ATC Services, is prohibited.

7.8 - Insulting ATC, in-appropriate language, and etc . . . will result in a suspension.

7.10 - Pilots shall use the same call sign as they are connected with their Pilot Client, e.g. IvAp.

7.11 - Playing of music is not allowed and will result in a suspension of 48 hours.

7.12 - The use of voice over text is preferred when controlling. However, ATC services can not be refused to a pilot if he/she does not have voice communication or at the discretion of the controller, due to language difficulties, text communication (which shall be in English) is more effective.

7.13 - TS Server Administrators, at their discretion, can ban a member who is not following these Rules. The length of time for this "Ban" will be determined by HQ.

8.- Division Rules and Regulations

8.1.1 - Every country can have one IVAO Division (DIV). The division callsign will be IVAO-XX, where "XX" has to be replaced by the countries ISO-code. Applications from local persons, living in the country, are preferred and have priority because of their local knowledge and to avoid difficulties due to time difference.

8.1.2 - To establish a division, a country must have at least 20 active users. In smaller countries HQ will have to decide if a division can be established.

8.1.3 - Establishment of a division has to be approved by IVAO Headquarters (HQ) . IVAO HQ can assign a person of their choice to maintain the approval.

8.1.4 - The division Director (DIR) and Assistant Director (ADIR) are appointed by IVAO HQ. All other division staff can be appointed by the DIV-DIR and DIV-ADIR. IVAO HQ reserves the right to deny staff membership to a person without statements of reasons

8.1.5 - The DIV-DIR must inform IVAO HQ about all additions and changes within the DIV-staff. The position of DIV-DIR and WM must be occupied at all times.

- Depending on the size of the Division, IVAO HQ can advise more or less staff positions

8.2.2 - All division staff members must comply with the IVAO staff-requirements which can be reviewed here

8.2.3 - Staff members can only be staff member in one division, unless approved by HQ.

8.2.4 - The division coordinators must work in full cooperation with the corresponding departments at IVAO headquarters and in other divisions.

8.2.5 - Divisions must provide a website for their members. Next to all relevant information about local ATC procedures this website should contain the necessary information about all IVAO services.
This website must be without popup windows, banners and any other form of advertisement. It must be viewable in a resolution of 800x600 and be checked in both MSIE and Netscape.The website should be based on the supplied example. More info can be found here. A redirect URL like "http://www.ivao.aero/XX/" will be provided by IVAO-NA.

8.2.6 - The division DIR will be responsible for the contents of the division website.

8.2.7 - Divisions must check the correctness of the information in the IVAO database regarding the actual data related to their division. Corrections and updates should be sent to hq@ivao.aero.

8.2.8 - For all information about airports, airspace, frequencies, callsigns, sectorfiles etc, published on the division website, the information should be taken from the IVAO database (see 8.2.7).

8.2.9 - Only IVAO mailinglists and IVAO forums are allowed for communications between staff and users and amongst the users.

8.2.10 - Divisions must organise and coordinate events and training for the users within their division. These events and training sessions should not only be published on the division website but should also be advertised throughout the Flightsimmimg community

8.2.11 - The contents and knowledge for theoretical and pratical exams should be equal for all divisions. Tests within divisions will be done by local examinators. Theoretical tests will be in the English language in order to prove a basic knowledge of the international "ATC"-language.

8.2.12 - Division staff must see to the correct behaviour of their users according to the rules and regulations issued by IVAO. Division staff must help and assist their users in case they have any problems.

9.- Staff member Rules and Regulations

To apply for a staff position at IVAO a user must meet the following requirements at the time of application:

9.1.1 - At least be 18 years of age. Division staff (except DIR and ADIR) can be appointed at the age of 16 years, but only when the DIV-DIR takes full responsibility for all actions taken by the, younger than 18 years, staff member. Staff under 18 cannot become a Supervisor.

9.1.3 - Must have at least Controller 1 or Flight Captain rating ( No restriction for WM and AWM, and MC/MAC need Student 3 or Captain rating ).

9.1.4 - Must have sufficient knowledge for the desired staff position. Depending on the position to man, a staff member must have extremely good knowlegde of IvAc, IvAp, ProController, Squawkbox, Flightsimulator and/or real world flying/ATC.

9.1.5 - Must be able to spend at least 5 hours per week to accomplish their tasks.

9.1.6 - All new staff members must be "On Trial" for at least 1 month. This isn't mandatory for a staff member moved to a new position, in this case it depends on Division Director's criteria.

9.1.7 - To be Div DIR/ADIR, you must be at least Controller 1 and Flight Captain rating. It's mandatory that the Division DIR/ADIR lives in the country from there division.

9.1.8 - IVAO recognises that, in some situations, it may be of benefit to the organisation to waive certain rules governing the formation and staffing of new divisions for a period to be determined by HQ but not exceeding two (2) years, to enable an active IVAO division to develop a division in a country where IVAO is not currently represented. It is a condition of such approval that interim-staff will resign their positions when HQ believes that the new division is capable for all practical purposes of self regulation and operation.

9.2.1 - Staff members are automatically subscribed to the IVAO Staff mailing list. It is required to check the forum on a regular basis.

9.2.2 - Staff members must use their IVAO E-mail account when sending IVAO related E-mails. Instructions for setting up your e-mail program can be find here

9.2.3 - Staff members must have a good knowledge about all information available on the IVAO website, therefore they must browse the website on a regular basis.

9.2.4 - For staff members it is not allowed to be a staff member of any competing organisation.

9.2.5 - Staff members cannot have more than one position, unless HQ approved to have more than one position.

9.2.6 - Staff members must follow- and act according IVAO-policy which is defined by the Council.

9.2.7 - Council members must attend regular staff meetings in order to determine and improve IVAO services.

9.2.8 - Staff members must fill out their date of birth in their user details prior become staff member.

9.3.1 - When going on-line, without the intention to be operational as Pilot or ATC, Staff members must log-in using their IVAO staff callsign.

9.3.2 - Staff members must maintain a presence on-line. On the IVAO network while using ProController or Squawkbox, but also in Flightsimulator related forums and newsgroups thus assisting and promotion our community on-line.

9.4.1 - To be concidered for a Supervisor rating, the person in question must be a staff member of a divison or a staff member of HQ at the time of application, and have at least 100 hours logged on IVAO.

9.4.2 - Supervisor recommendation and upgrade request has to be issued by the division DIR. IVAO HQ reserves the right to deny or downgrade/upgrade the appointment at its discretion, without statements of reasons.

9.4.3 - All candidates for Supervisor will have to pass an oral test with IVAO-DIR/ADIR/MD/MAD before the request will be study by HQ.

9.4.4 - A maximum of 1.5% of active division members can represent IVAO as Supervisors. Apart from this quota, the Division Director and Assistant Director can be appointed as supervisors, after proving themselves during their probatory period.

10. - Special Operations Rules and Regulations (Introduction)

10.1 - Welcome to the Introduction to IVAO Special Operations (SO) Rules and Regulations.
The SO department has been established to rule and regulate the use of the IVAO network for non civil aviation. This includes, but is not limited to, all police, search and resque, military and paramilitary activities.

10.2 - Single individuals flying a police, resque or military aircraft complying with the ICAO-rules for the normal civil procedures are not performing "Special Operations" and are therefore free to do as they like as long as they obey the standard IVAO User Rules and Regulations.

10.3 - As soon as training, exercise or other operations involve more people at once and/or other than the normal civil procedures, they have to comply with the SO rules and regulations which can be found on the webpages of the Special Operation Department. These kind of operations include, formation flights, air to air refuelling flights, search and resque missions, air carrier take off and landing practices, low level flights, awacs simulations and any other operation proposed to and approved by IVAO-HQ.

10.4 - Before you start any kind of special operations we want to draw your attention to this quote from the IVAO Mission Statement:

While simulation real world aviation "as real as it gets" we will avoid, at any price, to simulate or become involved in real world ethnical-, political- and religious conflicts and problems. We also will not allow the simulation of any form of agression or war. IVAO is an entertaining and educational network where every world-citizen, without any exception, is welcome to join the fun.

10.5 - In order to meet the contents of this quote, all air-to-air and air-to-ground excercises and attacks are prohibited on the IVAO network. Our network is established for flight- an ATC simulation, not for war simulation. Fans of wargames are served well on various other places on the Internet.

11.- Rules and Regulations for the use of Follow Me Car (FMC) and other Vehicles.

11.1 - The Division shall determine which airports, if any, where FMC's are allowed. This shall be as shown in the Facility Rating Assignment System (FRAS).

11.3 - Double connections or TWR's connecting with FM Services too, is not allowed and will be suspended for two (2) days.

11.4 - FMC Services shall be used in a correct coordination with ATC and with his/her approval.

11.5 - Speed Restrictions: Runways MAX 60 MPH (100 Km/h), Taxiways MAX 30 MPH (50 Km/h), and Gate Areas MAX 20 MPH (25 Km/h).

11.6 - Racing or anything that constitutes reckless operations of a vehicle, will result in a suspension for a minimum of seven (7) days.

11.7 - The FM car drive must be familiar with the airport procedures, have their lights on at all times, have a minimum ATC rating of C1, and adhere to the same Rules and Regulations for ATC procedures, where applicable.

11.8 - The call sign of the FM car shall be the ICAO of the airport and FMx, for example: Brussels, EBBRFM1 . . . if a second one EBBRFM2, and so on.

11.9 - Other land type vehicles or water craft, e.g boats, ships, and etc, are prohibited.

VA rules & requirements

Ąě1:	To become a VA affiliated with IVAO, your VA has to be free of charge for the members, and a non profit organization. Your VA will not profit directly or indirectly from using the IVAO network, neither use IVAO name to do publicity of the company.
Ąě2:	Registered VAs are responsible of the logos and names they submit to the IVAO database. *IVAO will not be responsible of copyright violations.*
Ąě3:	Your VA should use its assigned 3 letter code, to be able to use the network services provided, and only IVAO member VAs will have the right to mantain a registered ICAO code.
Ąě4:	VAs are required to log per week at least N?of users X 2 hours = Required hours. It does not mean each user must fly 2 hours, it means the total of hours flown by the company must be calculated with this formule. This is the minimum required to maintain their membership status in our Virtual Airlines System..
Ąě5:	VAs are required to update their membership details when they change (URL of website, e-mail, etc...). Not reply mails due to not existing mails will do the company will be removed from the database.
Ąě6:	Member VAs will link to IVAO using the logo provided to them on registration. The logo MUST be only the logo sent by us.
Ąě7:	IVAO reserves the right to accept, deny or remove a VA from the database and/or VA's system without any advise neither explanation if HQ decide it.
Ąě8:	To be included in the VA system, the company must have at least 5 users, and you have to send an email to the email account advised in the Virtual Airlines pages requesting become active in the system.
Ąě9:	Companies not having activity in the VA system for more than 4 months will be removed from VA system. The company will continue being in the IVAO database but not in the VA system..
Ąě10:	Companies not having contact mail or contact person in the database will be removed from the database.
Ąě11:	The VA's System is copyrighted by IVAO. Any company active on it can use it freely of charge. IVAO will only support problems with the pages, but will not support problems between the company and its users.

IVAO Rules and Regulations

3.- Terms of use.