Welcome to the Rules & Regulations Section,

Here you will find all necessary information you need in order to act according to the Rules & Regulations. All your questions on how to act correctly when being online and what is and is not allowed will be answered here step by step.

Please keep always in mind that IVAO is a place where you and others want to enjoy the same hobby. It will be normal that you will suffer a problem one day, but please always be friendly to your colleague and try to find a solution for your problem together with him. As in Real, you will also find situations, which will give you a big questionmark and where you dont know what to do. You can always refer to the Rules & Regulations, which are last updated;

Revised 18 April 2009 

However, should you have any questions left which might not be answered here, you can always contact the Turkish Division Staff - they will be more then happy to help and explain you whatever is needed.

The Rules & Regulations Section is divided into several parts - please read all of them to ensure enjoying IVAO - Thanks !

  1.- Mission Statements.

1.1 - The mission of IVAO™ ( The International Virtual Aviation Organisation ) is to provide an environment for a realistic Flight and Air Traffic Control simulation via the internet, utilizing IVAN ( International Virtual Aviation Network ) without charging money and available to anyone who agrees with the membership requirements.

1.2 - The main goals are to provide:  1) An experience which is "As Real As It Gets" while having fun in a friendly atmosphere, 2) Supplying the required internet services, and 3) Information and training in real life procedures for both Pilots and Air Traffic Controllers.

1.3 - When simulating real world aviation in the "As Real As It Gets" environment, we will avoid, at any price, to simulate or to become involved in real world ethnical, political and religious conflicts and problems.. We also will not allow the simulation of any form of aggression or war. IVAO is an entertaining and educational network where every world citizen, without any exception, is welcome to join the fun and pursue there virtual aviation experience.

  2.- Privacy Statement.

2.1 - IVAO collects personally identifiable information, such as your first- and last name and your e-mail address during registration. There is also information about your computer hard- and software that is automatically collected each time you log in to the network, such as, but not necessary limited to, your IP address and access times.

2.2 - IVAO collects and uses your personal information to operate the network and to deliver the services you have requested. Your personal information, with the exception of your e-mail address, can be reviewed by the public in the user database.

2.3 - IVAO does not sell, rent or lease its user lists to third parties.

2.4 - IVAO will disclose your personal information, without notice, if required to do so by law or in the good faith belief that such action is necessary to conform to the edicts of the law.

2.5 As a member of IVAO, notices are mailed to all members in the form of NOTAM’s via email. In this manner, important information concerning revisions to the Rules and Regulations, Executive Commitee staff changes, awards issued by Headquarters, and specific announcements related to departmental activities are communicated to our members. Likewise, we encourage our members to visit the IVAO forums where additional information and topics can be found concerning Divisions, General Membership, and Departments. If a member does not want to receive NOTAM's, then the member can request their name be removed from the NOTAM mailing list.

  3.- 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 - It is not allowed to restrict or inhibit any other user from using and enjoying the network services except in the way and with the manners described in the Rules and Regulations. For further information, a list of actions that could lead to a suspension of an account can be found here.

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 Executive Commitee, a member does not meet the requirements or abuses the Rules and Regulations, then Executive Commitee 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. -  Registration.

4.1.1 - The use of IVAO™ and IVAN services is reserved for registered users

4.1.2 - Anyone wishing to join IVAO™ may register at www.ivao.aero to become a "normal member." A normal member will receive a user ID and password to connect to the network.

4.1.3 - Each individual person is only allowed to have one registered account.

4.1.4 - Membership registration must contain the member's real first and last name. A false user name will result in the account being removed.

4.1.5 - To remain as an active member of IVAO, members must logon as a pilot or ATC at least once every three (3) months. Observer connections do not count towards this requirement. Accounts with no activity will be removed after nine (9) months from the date of registration. If a member's account becomes inactive or has been removed, the member may contact the members department and request re-activation.

4.1.6 - Upon initial registration, members will be asked to chose a division that they wish to join. A member may request a division transfer at any time, however, all transfers are subject to approval by the Divisional HQ of the member's current division, the Divisional HQ of the member's requested division, and the Membership Department.

4.1.7- Upon registration, you must provide a valid, working e-mail address to be used for communications about the IVAO™ network. It is the member's responsibility to make sure that the address on file is current at all times.

4.2. - Approved software.

4.2.1 - Only approved software is permitted for connecting to the network and for voice communications.

4.2.2 - Approved software can be downloaded from http://www.ivao.aero/network/so/

4.2.3 - Online traffic can be monitored using approved software.

4.2.4 - For voice communications between pilots and ATCs, approved software is used.

4.3. - Connecting.

4.3.1 - When connecting to the network as pilot, ATC, or observer, members must use their real first and last name which must be the same as name used in the registration process. Nicknames or fake names are not allowed. Staff members may connect using their approved staff callsign, when performing their staff function.

4.3.2 - Members must connect to the network using their own login and password regardless of location (e.g. a friend's house, aero-club, etc).

4.3.3 - Members must not have more than ONE connection to the network at any given time. Exceptions are stated in the next point.

4.3.4 - Staff members are allowed to have temporarily two simultaneous connections to the network provided it is to perform a valid staff task. The reasons for the multiple connections must be clearly stated in the flight plan remarks section or ATIS. Valid staff tasks include software development or training/exam sessions. Supervisors may also have a double connection in order to temporarily perform a supervisor function provided no other supervisors are available to assist.

4.4. - On-line.

4.4.1.a - Divisions located in a country without an approved ICAO language must use English.

4.4.1.b - Divisions with an approved ICAO language must use English as the primary language. The official ICAO language may also be used as a secondary language provided both the ATC and pilot speak the language, however, the ATC must still be able to control in English.

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

4.4.2 - Communication between Pilots and ATC may be in text, voice or both.

4.4.3 - Vulgarities and abusive language will not be tolerated, in any form of communications (public, private, voice, mail, etc).

4.4.4 - Usage of the network, e.g. text messages, is limited to information and material concerning IVAO.  Usage of the network to communicate information and material other than IVAO information, e.g. VA publicity, is prohibited and is subject to a suspension of membership privileges.

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

4.4.6 - Members are expected to behave in a friendly and respectful manner. Please be patient with new pilots and controllers.

4.4.7 - You are expected to be at your computer while online as a pilot or controller. Short breaks lasting no longer than 20 minutes are permitted.

4.4.8 - Users not responding to communications with ATC or to Supervisor's calls 20 minutes after the first attempt at communication will be disconnected from the network. This period of time could be reduced depending on the particular circumstances of the situation. In addition, a suspension of membership privileges could be issued and/or the flight/ATC hours of the day up until the suspension moment can be deleted.

4.4.9 -

4.4.10 - Within your ability, try to maintain an "as real as possible" attitude. New members are encouraged to add "newbie" to the remarks section of their flight plan or in the ATIS section as appropriate

4.4.11 - Within your capabilities, try to execute the simulation "as real as possible".

4.4.12 - Users must follow the instructions of supervisors and administrators to ensure everyone can enjoy the simulation.

4.5 - Suspensions.

4.5.1 - During the period of an account suspension, the user will be unable to connect to the network.

4.5.2 - Suspensions are issued by Supervisors or Administrators, but are subject to review by Executive.

4.5.3 - Click here if you want to check the suspensions' table. Suspension durations for infractions which are not predetermined from the Suspension Table are reviewed by Executive.

4.5.4 - In addition, Executive can issue a ban from the forum should circumstances warrant.

4.6 Ratings for Controllers and Pilots

4.6.1 - Ratings for pilots and controller shall be classified as "Basic Ratings", "Advanced Ratings", and "High-Level Ratings", by the Training Department.

4.6.2 - Practical examination requirements for controllers and pilots to achieve "Advanced Ratings" shall be described as "Unit Requirements" and "Pilot Requirements" within the Training Department website 

4.6.3 - Ratings for ATC Instructors (AI) and Pilot Instructors (PI) require the member to fulfill additional instructional responsibilities as defined by the Training Department.  The Training Department reserves the right to downgrade a member if the additional requirements are not met.  The ratings of Chief ATC Instructor (CAI) and Chief Pilot Instructor (CPI) are ratings reserved for past and present Training Directors and/or Training Assistant Directors.  These ratings are designated by the Executive and as such, members can not apply for these ratings.

5.- Controllers Rules and Regulations

5.1. - Before Connecting.

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, if not, an IVAO™ supervisor or administrator could ask them to leave the position

5.1.3 - Controllers must use approved software and be familiar with them.

5.1.4 - If you are newbie 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 the "valid" callsign extensions of _CTR, _FSS, _APP, _DEP, _TWR, _GND, _DEL. You must 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 - At certain airports FRA's (Facility Rating Assignments) are in effect. This means that on certain 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 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.7 - Maastricht Control (EDYY_XXX_CTR) is restricted to I1/C4 or higher ratings, unless written permission was granted by TD/TAD/OD/OAD/AOM/AOAM or Executive. Divisional HQ responsible for each Maastricht sector may also request members they would like to control to the people listed.

5.1.8 - Before connecting, check "Who is on line?" (link) or use the approved software included in 4.2.2. It is suggested, but not mandatory, to 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.1.10 - Prepare your ATIS before connecting to the network.

5.2. - Connecting.

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

5.3. - On-line.

5.3.1 - Controllers are prohibited from controlling outside of their Area of Responsibility. For example, if a member is logged on as tower, he/she shall not practice approach duties.

5.3.2 - When a controller logs on a position underlying a member's airspace, (Example - CTR controller providing coverage to a sector when an APP controller logs on) the member shall hand off all traffic in the underlying airspace as soon as practical.

5.3.3 - Controllers should only use frequencies, callsigns and other information as they are published in the IVAO-database. This information should be kept up to date by the divisions concerned. Any errors that may be found should be reported to the division staff. It remains the responsibility of the Division HQ to determine if the errors will be changed.

5.3.4 - Never use the Emergency (also known as GUARD) frequency of 121.500 for anything other than an emergency situation. Informing members an ATC position is online and asking a pilot to contact a specific ATC frequency do not constitute an emergency.

5.3.5 - If trying to contact a pilot, controllers should make use of the Force Act and private chat functions of the controlling software. GUARD should not be used. If a pilot does not respond using the two methods mentioned, they are unlikely to respond to any GUARD message.

5.3.6 - Handoffs of aircraft between controllers should be done using the transfer feature in the controlling software. Transfers may first be coordinated via private chat or using the IVAO™ Intercom.

5.3.7 - Controllers shall not attempt to take control of an aircraft who is under the control of another controller by informing the pilot to contact via force acting, guard or private message. Coordination must be initiated between both controllers to solve the situation.

   6.- Pilots Rules and Regulations

6.1. - Before Connecting.

6.1.1 - As a minimum, pilots must be able to take off and land at an airport.

6.1.2 - Pilots must be able to comply with basic air traffic control instructions such as being instructed to turn onto a particular heading or being given a level to climb or descend to.

6.1.3 - Pilot users must connect only with the approved software and have a basic understanding of how to use it.

6.1.4 - Pilot users shall not connect to the network while positioned on a runway or taxiway as this may cause conflicts with other aircraft.

6.1.5 - Pilot callsigns should be either three letters (ICAO) with numbers/letters to represent Commercial Carriers, e.g. NWA1014 "Northwest Airlines Flight 1014" or represent a typical country registration, e.g. Germany DAAYA, where the "-" is not used. In the case of a military flight, callsigns are country specific and the country military callsigns should be consulted. For more information on typical callsigns by country, please go to this link: http://en.wikipedia.org/wiki/Aircraft_registration.

6.2. - Connecting.

6.2.1 - For the enjoyment of all members, it is strongly recommended that you connect as a pilot user only if you intend to complete your entire flight. Exceptions are given to "long haul" flights where a pilot user may chose to only complete a portion of a flight and return later to complete the remaining portion. In this case, pilot users are encouraged to disconnect and reconnect while over the ocean where the possibility of a conflict is minimal. This rule does not apply to any tour which has its own rules.

6.2.1a - If disconnecting during a flight to connect at a later time (as described in 6.2.1) , the user should check to see if any ATC is online in the vicinity. If ATC is online, the user should inform the controller the position they wish to connect in before doing so.

6.3. - On-line.

6.3.1 - Pilot users must have transponder activated whilst in the air.

6.3.2 - Prior to each flight, all pilot users are required to file a flight plan through the approved pilot software.

6.3.3 - If you are a new or inexperienced user, it is recommended that you place a remark indicating this in your flight plan so air traffic controllers know to provide you with extra assistance if required.

6.3.4 - In areas without air traffic control, pilot users must monitor "UNICOM" 122.800 on their communications radio.

6.3.5 - In areas without air traffic control, pilot users should check for air traffic control on a regular basis and contact the appropriate air traffic control station when requested to do so.

6.3.6 - Never use the Emergency (also known as GUARD) frequency of 121.500 for anything other than an emergency situation.

6.3.7 - Pilots should always readback and follow ATC instructions unless doing so could endanger the operation of the aircraft.

6.3.8 - Simulation of a radio failure (i.e. squawking 7600) is not cause to ignore ATC instructions in case of a conflict or requests from supervisors.

6.4 - Special Operations.

6.4.1 - Coast Guard operations, search and rescue missions, and military aircraft are examples of "Special Operations". As Special Operations are a part of real-world aviation, they are also a part of the simulation, however, certain aspects of special operations are prohibited on the network including simulation of terrorism and acts of war. Although armed conflicts do exist in the real-world, we do not allow the simulation of any form of aggression or violence on the network. For further information regaring our policy, please see the rules and regulations for the special operations.

6.4.2 - Read the Special Operations Rules and Regulations.

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

7.1 - The use of voice communications is recommended due to the heightened sense of realism, however, there are numerous reasons why members do not use voice communications. As such, voice and text are both equally acceptable forms of communications and ATC services can not be refused to a pilot using text communications. At the discretion of the controller, communications by text may be more efficient depending upon work load, language skills, or typing ability.

7.2 - Only approved voice software is permitted for voice communications.

7.3 - Password protected channels are not allowed.

7.4 - The use of IVAO™ voice servers is only allowed when you are also connected to IVAN with approved software. IVAO™ voice servers may be used for IVAO™ meetings without being connected to IVAN.

7.5 - As an exception, channels may be opened by registered virtual airlines as "company channels," by special operations groups for coordination purposes, and by staff members for staff meetings. Member virtual airlines are allowed to create a "registered" company channel on the nearest teamspeak server to the airline's division of registry. The channel shall be created in the format ICAO_CC where ICAO stands for the three letter ICAO code of the airline. As an example, Netherline VA = NHL_CC, Topic = http://www.netherline.nl, Description = (VA may include a short description here).

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.7 - Users may create teamspeak channels, however, may not create channels which are "registered" nor may they change the "max users" option. These options are reserved for supervisors, administrators, staff members, or as noted in the following rules.

7.8 - Deleting Staff Channels is prohibited.

7.9 - Pilots shall use the same call sign as they are connected with their Pilot Client.

7.10 - Playing of music and/or other broadcasting of sound, not related to the simulation, is not allowed and will result in a suspension of 48 hours.

7.11 - Voice server administrators, at their discretion, may "ban" a member who has violated a rule in this section. The length of the "ban" shall be determined by Executive.

7.12 - For training purposes " debriefing " channels are not allowed to be password protected. However the "Max Users" can be restricted.

7.13 - When taking an ATC position your are allowed to create a "Registered" channel (Keep in mind that when another member taking over your ATC position to grant him your Channel Admin rights).

7.14 - Above all, be nice, speak clearly, and have patience with new members.

 8.1. - General.

8.1.1 - Every country is eligible for one IVAO™ Division. The division callsign will be in the format of IVAO-XX where XX represents the country ISO code. Applications from country residents are preferred and will take priority due to local knowledge and time zones.

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

8.1.3 - IVAO™ Executive reserves the right to approve or deny establishing a division. IVAO's Executive can assign a person of their choice to establish a division or to maintain it if necessary.

8.1.4 - Divisional Directors and Assistant Directors are appointed by IVAO™ Executive. Divisional staff may be appointed by the Divisional Director / Assistant Director. IVAO™ Executive reserves the right to deny any divisional staff appointments.

8.1.5 - Every division shall have an active Director and Webmaster at all times.

8.1.6 - Divisional Directors are responsible for sending a divisional report to Executive upon request.

               8.2. - Division requirements.8.2.1 - A division can have the following staff positions:

- Division Director (XX-DIR)

- Division Assistant Director (XX-ADIR)

- Flight Operations Coordinator (XX-FOC)

- Flight Operations Assistant Coordinator (XX-FOAC)

- ATC Operations Coordinator (XX-AOC)

- ATC Operations Assistant Coordinator (XX-AOAC)

- Special Operations Coordinator (XX-SOC)

- Special Operations Assistant Coordinator (XX-SOAC)

- Training Coordinator (XX-TC)

- Training Assistant Coordinator (XX-TAC)

- Events Coordinator (XX-EC)

- Events Assistant Coordinator (XX-EAC)

- Membership Coordinator (XX-MC)

- Membership Assistant Coordinator (XX-MAC)

- Webmaster (XX-WM)

- Assistant Webmaster (XX-AWM)

- VARTCC/FIR Chiefs (if more than one FIR in the division)

- For some departments, the Division can have Advisors, for example: for the training department

.- Depending on the size of the Division, IVAO™ Executive 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 - Members can only be staff in one division, unless approved by Executive.

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

8.2.5 - Divisions must provide a website for their members. As well as all relevant information about local ATC procedures this website should contain the necessary information about all IVAO ™ services. The use of popup windows, banners and any other forms of advertising must not be used without the agreement of Executive. It must be viewable in a resolution of 800x600 and be checked in any modern browser. More info can be found here. A redirect URL like "http://xx.ivao.aero/" will be provided by the Logistics Department.

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 ATC Operations department.

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™ mailing lists 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 examiners. Theoretical tests will be in the English language in order to prove a basic knowledge of the international "ATC" language.

8.2.12 - Divisions must not have their own theoretical and practical exam system unless permitted by the IVAO™ Training Department. All theoretical and practical exams must be done through the systems supplied by IVAO.

8.2.13 - Division staff must set an example to division members by behaving correctly at all times as described within the IVAO™ Rules and Regulations.

8.2.14 - In addition to 8.1.5 and 8.2.1 the order of preference of appointments within division staff is TC then EC. The remaining positions can be allocated as required within the division.

  9.- Staff member Rules and Regulations

9.1. - Application requirements.

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

9.1.1 - Staff members shall be at least 18 years of age with the following exceptions: 1) Divisional staff may be appointed at age 16, however, the division director shall take full responsiblity for their actions. 2) Senior staff or Divisional DIR/ADIR may be appointed at age 16, however, will remain "on trial" until they have reached age 18. 3) Supervisors must be at least 18 years of age.

9.1.2 - Prospective staff members must be an active IVAO™ member for at least 6 months prior to appointment.

9.1.3 - Prospective staff members must have at least Controller 1 or Flight Captain rating except the following:

- MC/MAC require minimum Student 3 or Captain rating

- WM/AWM/PR advisors require no minimum rating

9.1.4 - Prospective staff members must have sufficient knowledge for the desired staff position. Depending on the position to man, a staff member must have extremely good knowledge of approved software, flight simulators, Xplane and/or real world flying/ATC

9.1.5 - Staff members must be able to devote at least 5 hours per week to their position. Enforcement of this provision will be by Executive, the Department responsible and Division HQ. As an example, the Training Department can review the Training Coordinator, Training Assistant Coordinator, or Training Advisors and propose a course of action to Executive up to and including dismissal.

9.1.6 - New divisional staff members shall be "On Trial" for at least 1 month. Senior Staff and Divsional Director/Assistant Directors shall be "On Trial" for at least 2 months. If a divisional staff member is moving from one position to another, the "On Trial" period may be waived.

9.1.7 - A Division Director/Assistant Director shall hold at least a Controller 1 and Flight Captain Rating, shall be a resident of the country in which the division represents, and shall be required to pass an interview with a member of Executive. Only one staff member, either DIR or ADIR, is required to be a resident.

9.1.8 - IVAO™ recognizes that, in some exceptional situations, it may be of benefit to the organization to waive certain rules governing the formation and staffing of new divisions for a period to be determined by Executive 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 Executive believes that the new division is capable for all practical purposes of self regulation and operation.

9.1.9 - Staff members must be able to speak and read/write at least one official language of the country represented.

9.1.10 - The Training Director/Training Assistant Director reserve the right to monitor and evaluate Training Staff during practical exams and, if required, take appropriate action.

9.2. - General.

9.2.1 - Staff members are automatically subscribed to IVAO™ staff mailing lists and are required to check the IVAO™ 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 found here

9.2.3 - Staff members must have a good working knowledge of the information available on the IVAO™ website and therefore are encouraged to browse the website on a frequent basis.

9.2.4 - Staff members are prohibited from being staff members of any competing organization.

9.2.5 - Staff members, as a general rule, should not hold more than one operational position within the following departments: Members, Events, Training, and Operations. The division director shall assess and approve any staff members holding more than one operational staff position at the divisional level for a limited time in order to accomplish the priorities set forth in 8.2.13. Executive assessment and approval is required in the case of a senior staff member holding more than one operational positioin. In either case, a person may hold no more than four staff positions. Server Administrator positions do not count towards this quota.

9.2.6 - Staff members are directed to follow IVAO™ policies which are set forth by the Board of Governors.

9.2.7 - Staff members are required to attend regular staff meetings.

9.2.8 - Staff members are required to disclose their date of birth via their user profile prior to staff appointment.

9.3. - On-line conduct.

9.3.1 - When connecting to the network without the intention of acting as a pilot or air traffic controller, staff members are encouraged to use their IVAO™ Staff callsign.

9.3.2 - Staff members are required to maintain an online presence not only on the IVAO™ network but also in flight simulator related forums and newsgroups to assist and promote our community. In particular, division directors, assistant directors, and operational staff members should maintain a regular presence on the network. Lack of activity from staff members for a period of three months can lead to removal from the staff position.

9.4. - Supervisors.

9.4.1 - To be considered for Supervisor appointment, the candidate must be an IVAO™ staff member at the time of application with at least 200 hours logged on IVAO™ and hold a Controller 2 AND Senior Captain ratings. Supervisor applications can be requested for Divisional Staff by the Division HQ, or for Senior Staff by Executive. The hour and rating requirements are not applicable to Server Administrators.

9.4.2 - IVAO™ Executive reserves the right to deny any application or downgrade any supervisor.

9.4.3 - All supervisory candidates must pass an oral interview with a member of Executive or with the Membership Director/Assistant Director prior to being considered by Executive for Supervisor status. This interview will assess the candidate's English language ability, decision making ability, and knowledge of IVAO™ rules and regulations. Under exceptional circumstances, the interview may be conduted via text.

9.4.4 - A maximum of 1.5% of active division members can represent IVAO™ as Supervisors. Division Directors and Division Assistant Directors are not counted in this quota. Staff appointed as senior staff are not counted as part of this quota unless they are also a member of the divisional staff.

   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 the Executive Commitee.

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.2 - A TWR must be manned before the FM car(s) can be used.

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.

   Rules & Regulations for Virtual Airlines

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 Executive Commitee decide it.

8 - To be included in the VA system, the company must have at least 10 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 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

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