T.1 IVAO GCA- and exam regulations are subject to the IVAO HQ training department. None of the published IVAO training department procedures and/or regulations shall be altered, without prior written approval by the Training Director and/or Training Assistant Director.
T.2 Divisions may require members of foreign divisions to obtain a Guest Controller Approval before providing ATC services. Divisions shall announce their participation and publish their requirements on the division’s website. Such GCA requirement(s) shall be published on the division website in English language.
T.3.1 IVAO pilot and/or ATC exams can only be performed in approved IVAO (mini-) divisions which are assigned by the Training Director and/or Training Assistant Director. The approved divisions shall be published on the IVAO website.
T.3.2 IVAO users can not apply for an IVAO exam outside the division they are registered with.
T.3.3 Exam procedures and marking standards are solely to be determined by the HQ training department. Divisions not executing the proper procedures and marking standards, may have their pilot and/or ATC examiner assignment revoked.
T.3.4 IVAO exams shall be assessed on the IVAO network via approved IVAO software. The approval of the IVAO software for exams is determined by the Training Director and/or Training Assistant Director and shall be published on the IVAO website.
T.3.5 Practical IVAO exams may only be assessed by IVAO training staff with an active IVAO examiner status. Approval of IVAO examiners shall be granted by the Training Director and/or Training Assistant Director. Approval of staff exams shall be done by the Training Director, Training Assistant Director and/or Senior Training Advisor.
T.3.6 All IVAO exam results are pending validation by the Training Director, Training Assistant Director and/or appointed HQ training staff. Successful completion of the exam after validation by IVAO HQ, will result an equivalent ATC or pilot rating being assigned to the user. This rating may be revoked/downgraded if certain standards are no longer met.
T.3.7 IVAO users can be suspended or excluded from IVAO exams for reasons of exam fraud, scoring 10% or less on an exam or violation of the IVAO rules and regulations. The type and length of exclusion is determined by the Training Director and/or Training Assistant Director.
T.3.8 The ratings of SFI/SAI are assigned and revoked by the Training Director and/or Training Assistant Director. The rating of CFI/CAI is honorary and assigned by the Executive Council. This rating is not removed upon resignation from the position of Training Director and/or Training Assistant Director.
T.3.9 After switching divisions users are not allowed to request any practical exam within 90 days. Exceptions can be made by the Training Director, Training Assistant Director and division mentor.
T.3.10 Only users with an active account are allowed to request and perform exams. Users with inactive or suspended accounts are excluded from requesting and/or performing exams until their status is active again.
M.1 In case of doubt on the user identity by the membership department the user will be asked to provide a copy of an official ID to prove his identity.
M.2 E-Mail address containing the word IVAO are not accepted.
M.3 Division Change request A user may once per 12 months request a division transfer, all transfers are subject of approval by the users prospective division and the Membership Department.
For the right procedure please refer to https://wiki.ivao.aero/en/home/members/faqs
A.1.1 Aerodrome Control: All DEL, GND and TWR positions.
A.1.2 Terminal Control: All APP and DEP positions or TWR positions with TMA responsibilities
A.1.3 Area Control: All ACC positions responsible for CTA and UTA airspace
A.1.4 FSS: Stations performing Flight Station Service
A.2.1 Aerodrome Control Regulations
A.2.2 Terminal Control Regulations
A.2.2.1 An approach shall perform the ATC duties in all controlled aerodromes (TWR, GND and DEL) under the airspace he’s responsible in the absence of online members.
A.2.3 Area Control Regulations
A.3.1 FRA Regulations
A.3.2 Scheduling System Regulations
F.1.1 IVAO FOD will provide a website for VA listing, statistics and ACARS.
F.1.2 Approval and management is the responsibility of the division FOC and FOAC or in their absence DIR and ADIR. VA removal however has to be requested by the divisions to the FOD.
F.1.3 FOD always reserves the right to remove a VA from the registered VA list. Reasons for this action should be forward to the Executive.
F.1.4 The Executive Council always reserves the right to remove a VA from the VA registered VA list. This could be based on any serious and/or regular transgressions of the IVAO R&R.
F.2.1 To become a registered IVAO™ VA, your VA has to be free of charge for the members, and should not have a commercial goal. Your VA will not profit directly or indirectly from using the IVAO network, neither use IVAO™ name to do publicity for the company.
F.2.2 Registered VAs are responsible for the logos and names they submit to the IVAO database. IVAO™ will not be responsible for copyright violations. If a VA is based on a real airline it is solely the responsibility of the VA to obtain and maintain approval from the real airline to use its name, logo and other materials.
F.2.3 Only IVAO™ member VAs will have the right to maintain a registered ICAO code. You can choose your own ICAO code during the registration process and it will be assigned to you. Multiple VAs with the same call sign can be included in the IVAO VA registered list. If the VA you are registering is based on a real airline, then you will be assigned the ICAO code of that real airline. Note: the reference for real airlines is ICAO Doc 8585.
F.3 To be an IVAO™ member VA and to maintain the registration, a VA must fulfil the following requirements:
F.3.1 The CEO/Owner must:
F.3.2 It is mandatory for VAs to use the IVAO ACARS system and are required to log every 6 months 50 legs/flights using the VA ICAO code from the date of the registration. If they fail to do so, then the system will automatically delete the VA from the registered list. Note: VAs can use their own ACARS parallel with the IVAO one.
F.3.3 The registration form must be completed and submitted by the CEO/Owner of the VA. This is to ensure a direct communication channel between the IVAO Flight Operations and VA management personnel.
F.3.4 VA website shall display, at least on the homepage of the website, the provided official IVAO VA logo linked to IVAO™ main website.
F.3.5 Registered VAs must adhere to the GDPR and any deviation from the GDPR will result in termination of the VA membership from IVAO.
S.1 Special Operation flights are all flights operating as Operational Air Traffic (OAT) regulations.
S.2 Referrer to the Special operations directive for the Special Operations regulations under this link.
E.1.1 Events Categories, Events Types, and list of abbreviations: http://wiki.ivao.aero/en/home/events/typeofevents.
E.1.2 IVAO Rules, Regulations & Policies: http://wiki.ivao.aero/en/home/ivao/information.
E.1.3 IVAO Events forum board: http://forum.ivao.aero/index.php?board=326.0.
E.1.4: IVAO Events Reporting System: http://hqe.ivao.aero.
E.2.1 Organisation, planning, and/or participation at any IVAO Event is to be conducted in accordance with all IVAO Rules, Regulations & Policies.
E.2.2 All IVAO Events must be booked in the IVAO Calendar System and published on the IVAO Events forum board, provided the proposed event is in accordance with E.1.1.
E.2.3 Divisions are allowed to host, extraordinarily, IVAO Division-only Events (see E.1.1) as long as these events are not booked in the HQ Calendar System by the Divisional Events Departments, therefore these events can only be published and advertised within their respective division.
E.2.4 PDEs: These can be requested by a division when intending to represent IVAO at a live stand (eg. Live fair, airshow...)
E.2.5 IVAO Events with HQ support, Memorial Events, Real Flight Events, Real Flight Operations Events, and Mega Slot Events require prior approval by the IVAO Events Department before these events are added to the IVAO Calendar System.
E.2.6 The maximum number of IVAO Events booked in the Calendar System is 4 (four) per day.
E.2.7 Divisional Events Department are not allowed to organise events outside their designated country/region. Divisional Events Departments are not allowed to organise events in non-active IVAO divisions. IVAO Multidivisional Events may be organised only if all involved IVAO Divisions agree to participate in the event proposal.
E.3.1 Only 2 (two) RFE/RFO/MSE Events are allowed per day. A gap of 6 hours between the first RFE/RFO/MSE finishing and the second RFE/RFO/MSE is required.
E.3.2 Users who book a flight slot in the divisional slot booking system for a RFE/RFO/MSE event will get priority to participate at the RFE/RFO/MSE Event. Participations without a booked slot are not eligible for the point towards the IVAO Events Support Award (if available).
E.3.3 Divisional Events Departments are required to publish their RFE/RFO/MSE Event announcement in the IVAO Events forum board not later than one (1) month before the event date. The divisional slot booking system must be available for bookings not later than fifteen (15) days before the event date.
E.3.4 Divisional Events Departments are required to follow the proper procedures to request, organise and host an RFE/RFO/MSE. The procedures are published in the IVAO Events Department Circulars.
E.4.1 An unlimited amount of Approved PDEs are allowed per day.
E.4.2 Any controllers or pilots directly involved in hosting i.e. Streaming the Public Demonstration Event must have in their ATIS/Flight Plan the following notice: “Public Demonstration Event participant – Session recording/broadcasting approved”.
E.4.3 Divisional Events Departments are required to publish their PDE announcement in the IVAO Events forum board no later than one (1) month before the event date.
E.4.4 Divisional Events Departments are required to follow the proper procedures to request, organise, and host a PDE. The procedures are published in the IVAO Events Department Circulars.
E.5.1 Only one (1) IVAO Events Support Award or IVAO Connect Event Award is allowed per day.
E.5.2 The IVAO Events Department may approve exceptions for the E.5.1 regulation, provided the following conditions are met:
E.5.3 The IVAO Events Department implements a token system for the IVAO Events Support Award usage. The token system states that:
E.5.4 Divisional Events Departments, when hosting IVAO Events with HQ support, must assure that ATC coverage is guaranteed during the entirety of the event timeframe. Divisional Events Departments are also encouraged to use Air Traffic Flow Management procedures (e.g., booking slots, departure separation, et cetera) to avoid overflow of air traffic during events in this category.
E.5.5 Divisional Events Departments are required to publish their IVAO Event with HQ support in the IVAO Events forum board not later than fifteen (15) days before the event date, except in the cases described by E.3.3 and E.4.3.
E.5.6 Divisional Events Departments are required to follow the proper procedures to request, organise, and host an IVAO Events Support Award event. The procedures are published in the IVAO Events Department Circulars.
E.5.7 In case of participations in events integrating the IVAO Events Support Award that are taking place during a PDE or other live event using an “Event Account”, the participants IVAO VIDs must be submitted to the IVAO Events Department via email@example.com by the Divisional DIR/ADIR.
E.5.8 The IVAO Events Department can hold an unlimited number of events integrating the IVAO Events Support Award. Per year, the IVAO Events Department can hold twelve (12) events integrating the IVAO Connect Events Award.
E.5.9 The IVAO Connect Event type consists of six airports (two airports per division/area) agreed upon by the Divisional Events Department and the IVAO Events Department; the standard duration of the event is at least four hours. The IVAO Events Department is, solely, responsible for the organisation of these events in non-active divisions and shall work in coordination with Divisional Events Department in areas with active divisions.
E.6.1 Users participating in events integrating the IVAO Events Support Award must comply with the event’s requirements which are located in the forum in order to be eligible for the point towards the described award. Users participating in events integrating the IVAO Connect Events Award must comply with the event’s requirements which are located in the forum in order to be eligible for the point towards the described award.
E.6.2 Participation in IVAO Events with HQ Support or IVAO HQ Events must be submitted via the IVAO Events Reporting System not later than one (1) month after the event date.
E.7.1 All IVAO Divisions are allowed to host a maximum of one (1) Divisional Online Day event per week.
E.7.2 All Divisional Online Days must be visible here: http://forum.ivao.aero/index.php?topic=333006.0.
E.7.3 Divisional Events Department are encouraged to avoid hosting Divisional-only Events (see E.2.3). If the usage of this event category becomes necessary, Divisional Events Department are advised to avoid hosting these events during the timeframe of important events in the network such as PDEs, RFEs, RFOs, MSEs, et cetera.
E.8.1 All User Events must follow the User Events Guidelines and Procedures published here: http://forum.ivao.aero/index.php?board=1604.0.
W.1 World Tour flights are to be conducted in accordance to IVAN Rules and Regulations.
W.2 In addition to IVAN Rules and Regulations, a number of World Tour Department specific procedures must be observed and followed. These are defined on the website of the World Tour Department. https://wt.ivao.aero/rules
W.3 Every World Tour will also include separate and specific regulations that apply only to that World Tour. These regulations are published on the Description page of the tour. These regulations are complimentary to the World Tour Department’s General regulations.
X.1.1 Department Directors and assistant Directors are appointed by the Executive Council once they have passed a successful interview, and approval by the BOG within a period of 5 days. Following a resignation of a Department Director, the Executive Council can:
X.1.2 Department Directors and assistant Directors are representatives of the organization to their departments. Their responsibility, in addition to the functions of the position, is to support and assist the Executive Council inside the departments.
X.1.3 The official communication channels between a department and the Executive are the IVAO forum, IVAO staff mail, IVAO NOTAM system and the IVAO Staff Discord server.
X.2.1 Division and Department HQ are appointed by the Executive Council. Divisional coordinators are appointed by the respective division HQ Departmental staff members are selected by HQ Department Directors and appointed by the Executive Council. All staff members, after being appointed in a position, shall be on trial for a minimum of 3 months.
X.2.2 The following age requirements applies for the respective positions at the time of appointment:
X.2.3 The following rating requirements applies for the respective positions at the time of appointment:
X.2.4 In order for a user to be eligible for a division staff position, a minimum membership duration of 3 consecutive months is required in the respective active division. This regulation does not apply to the construction of a new division.
X.2.5 To be eligible for a staff position, a user must have had an active registration with IVAO for a minimum of 6 months.
X.2.6 Staff producing any material such as, but not limited to, websites, software and systems are required to sign an IVAO Copyright Agreement. All staff will be required to sign an IVAO NDA. Prospective staff members, under the age of 18, and their legal guardian will be required to fill in and sign an NDA (and a Copyright Agreement, if necessary) before appointment as a staff member commences. NDAs and Copyright Agreements for staff members over the age of 18, must be signed within 7 days of the appointment.
X.2.7 The Division Director (DIR) or Assistant Director (ADIR) must be a resident in the country of the division. For a multi country division, the Division Director (DIR) or Assistant Director (ADIR) must be resident in one of the countries participating in the multi country division.
X.2.8 Staff members are prohibited from holding any staff position(s) of any competing organization.
X.2.9.1 Staff are required to maintain an active IVAO account and online presence, at all times.
X.2.9.2 Registration and participation on IVAO Staff Discord server is mandatory for all staff. Server usage guidelines for this server, and can be found here; https://www.ivao.aero/documents/Discord.pdf
X.2.9.3 Division HQ are responsible for establishing minimum quotas for online presence for their respective staff. On average, this quota may not be less than a minimum of 2 hours per week.
X.2.10 A user can only hold divisional staff position(s) in their respective division. Any user may not hold more than four (4) staff positions in total.
X.2.11 Staff members are not allowed to store any data containing personal information related to IVAO, on any physical media, or in any software databases or repositories, as well as any online cloud storage which is outside the realm of the IVAO VZW.
X.2.12 Staff must always act as a good representative of IVAO, towards the users and the general public, and always ensure to act within the IVAO Rules, Regulations and procedures.
X.2.13 For a resignation from a Division Director (DIR) or Assistant Director (ADIR) to be accepted, the resignation must contain a proposal(s) for suitable successor candidate(s), as well as a proper handover process.
X.2.14 Staff that are not fulfilling the above requirements may be removed from their position.
X.2.15 All Division staff are required to comply with all GDPR policies and guidelines. If a Division does not comply with, or respond to any GDPR requests within 7 days, then a reminder email will be sent. If there is still no answer 14 days after the original request was sent, then the status of the Division will be set to Under Construction.
X.3.1 Only IVAO staff members can hold a Supervisor status.
X.3.2 Senior HQ (Department Director and Assistant Directors) are automatically eligible to become a Supervisor, as long as the other Supervisor requirements are also met.
X.3.3 An IVAO staff member can be nominated to become a Supervisor by any Division HQ or Department Directors.
X.3.4 Division HQ, can only nominate staff members in their own division to become Supervisors.
X.3.5 To be eligible as a Supervisor, the staff member must; Have been a staff member at HQ or divisional level for at least 3 consecutive months; Have held the rating of Senior Private Pilot (SPP) and Approach Controller (APC) for at least 6 months; Have a minimum of 100 hours logged as a staff member; Successfully pass an interview with the Executive Council Agree to sign the Confidentiality Agreement.
X.3.6 Supervisors represent the Executive Council in their roles and responsibilities, therefore they are appointed, managed, monitored and disappointed by the Executive Council.
X.3.7 A Supervisor appointment is a global network appointment, not a divisional appointment.
X.3.8 Requirements, procedures and guidelines for Supervisors are established and maintained by the Executive Council.
X.3.9 All Supervisors are obligated to monitor and deal with requests and situations throughout the network, and while online, respond to all wallops sent by any member, and for any reason, unless otherwise occupied.
X.3.10 Supervisors must follow and act in accordance to IVAO R&R. In situations where required, these cases may be reported to IVAO Executive.
X.3.11 Any Supervisor’s actions that take place, without adhering to the guidelines will be subject to warnings and the possibility of having their Supervisor status revoked.
X.4.1 Every country is eligible for one IVAO Division or Mini Division. Every group of countries are eligible for one IVAO Multi Country Division or Mini Division. The ISO code of a division is assigned by the Executive Council.
X4.2 There are three (3) types of divisions: Division; consisting of a single country Mini Division; also consisting of a single country, but less minimum requirements than a Division Multi Country Division; consisting of 2 or more countries
X.4.3 It is the full discretion of the Executive Council to open, close or regulate a division.
X.4.4 Divisions may be requested to provide IVAO Executive Council with quarterly, bi-annually or annually progress reports. If requested, the report must be submitted no later than 30 days after the request was made.
X.4.5 The only official communication channels between a division and its members are the IVAO forum, IVAO staff mail, IVAO NOTAM system and the division’s website.
X.5.1.1 Minimum staff position requirements for a Mini Division are:
X.5.1.2 Minimum staff position requirements for a Division and/or a Multi Country Division are:
X.6.1.1 IVAO divisions are of different sizes and orientation, as such a number of additional staff positions may be required. Divisions and Multi Country Divisions may request activation of Advisor positions, following the procedures published in our documentation.
X.6.1.2 The maximum number of Advisors in a division, is at the discretion of IVAO Executive Council.
X.7.1.1 The creation and closure of a division is determined by the Executive Council.
X.7.1.2 The proposing Division Director and any initial staff must meet the general IVAO Staff requirements as detailed in our Rules and Regulations.
X.7.1.3 To commence creating a new division, the proposed Division Director and/or staff team is required to prepare a proposal to be presented to the Executive Council, as published in the Division Creation Procedure.
X.8.1.1 A Division must provide a website for users of the Division and IVAO. The website may be in the local language, but some content (stated below) must also be in English. As a minimum, the website must;
X.8.1.2 The website shall be hosted on IVAO VZW servers.
X.8.1.3 The website, once uploaded on IVAO VZW server, becomes the intellectual property of IVAO.
X.8.1.4 Division HQ and Division Webmaster are responsible for all content on the website
X.9.1 The Executive Council reserves the right to waiver any regulation or requirement, if deemed necessary in special situations.
P.1 For the public demonstration events procedure please referrer https://doc.ivao.aero/events:procedures:pde
All websites and tools are owned and copyrighted by/to IVAO. Any attempts of decompiling, exploiting, hacking and any other kind of activities in the purpose of gaining access to restricted/encrypted material or areas, are strictly prohibited.
Users that reveal any security related issue in IVAOs software are entitled to report it to DEVOPs in order to get the problem solved. Exploiting or spreading the revealed issue to third parties is prohibited. If such activities are detected and/or not being reported to appropriate instances (i.e. DEVOPs or Executive Council), an appropriate sanction (i.e. suspension) will be established by the Executive Council.
D.2 Flight data tracking
According to IVAO R&R 2.1.2 members details are confidential. Confidentiality means – in relation with flight data tracking – that only IVAO staff members are allowed to view flights from others. Divisions using their own flight data tracking system are enforced to make sure, the privacy requirements are met at all times. If DEVOPs are notified about a violation of this rule, the access to Whazzup (see Regulation D.4 below) may be revoked.
D.3 Login API approval
1) All IVAO Login API requests are subject to an approval process by DOD/DOAD or the Executive Council started by either:
Requests from other parties then the before mentioned will be declined. 2) Once usage of the API was approved, the requestor will receive an unique API usage key, which has to be kept confidential. 3) If the API isn’t being used for more than 90 consecutive days, DEVOPs reserves the right to revoke access to the IVAO Login API. In this case re-application is possible by going through the approval process again.
D.4 Whazzup usage (live network data)
D.5 Hosting divisional websites on HQ Servers
D.6 Access to divisional website content
D.7 Backup of divisional websites
Every division – regardless if they are being hosted on IVAO HQ servers or not – are enforced to regularly (at least once per quarter) send backups of their websites to DEVOPs. This backup must contain all files, databases, offered downloads (e.g. Charts (if being offered), Sectorfiles, …) and other related things, which are needed for running the website. Divisions DIR/ADIR/WM/AWM is responsible for this process to be monitored and handled regularly.
D.8 Regularly change of access credentials
B.1 Rules and Regulations
B.2 Executive Council elections