1. - Introduction

1.1 - The number of registered IVAO-users is increased to over 25.000, and we have several hundreds of users online every day.
The efforts of the training department and the introduction of the exams have caused a giant leap in both ATC- and Pilots quality within our community.
We think now is the time to increase the overall online quality by careful introducing and implementing the "Facility Rating Assignments System" (FRA's).
Careful because we have mixed interests. On the one hand we like to improve the overall quality of IVAO, on the other hand we do not want to discourage new and unexperienced users by raising the treshold too much.
Taking the above into consideration we have compiled the following quidelines for FRA's

2. - General

2.1 - FRA's should mainly be applied to International and/or "main"-airports, thus leaving regional airports available to new and/or unexperieneced users for learning- and training purposes.

2.2 - These are a Guidelines about how FRA's could be implemented for ATC-positions.
Users with an ATC-rating of Student 1 should only be allowed on Delivery- Ground- and Tower positions on regional airports.
Users with a ATC-rating of Student 2 should be allowed on all positions on regional airports, or on Delivery-, Ground- and Tower positions in main airports.
Users with a ATC-rating of Student 3 should be allowed on all positions on all airports, including International and "main"-airports.

2.3 - These restrictions do not mean that f.i. a Student 1 is not allowed to "act" as an Approach controller when there is no Approach available, he is however not allowed to "connect" to a _APP position. Thus leaving the _APP position available for more experienced users logging in at a later time.

2.4 - These are a Guidelines about how FRA's should be implemented for Pilots.
At this moment we give no recomendations for Pilots restrictions. In special cases, like Fly-in's or Exam's etc, Divisions can decide to activate FRA's for pilots on certain Airports. Because it can not be expected that Pilots visit the web of every destination they plan to visit, Pilot FRA's should also be included in the ATIS of that Airport, together with an alternative Airport. Example : "FRA - no FFO at EHAM 18.00 - 20.00 Z (alt. EHRD)" Also see User's R&R - Pilots - 6.3.6
CTR airspaces and regional Airports cannot be restricted to pilots, independently of their rating.

2.5 - FRA's can be specified in the form of a time-roster. With f.i. little restrictions during hours with low traffic and more restrictions during peak hours. For practical reasons this roster should be a "standard"-table (always the same) available to all users of the division. Exceptions to the roster, f.i. when a fly-in takes place, should be announced by notam e-mail together with the announcement of the fly-in.

3. - Implementation

3.1 - The Divisions are responsible for FRA's in their countries.

3.2 - Division's DIR/ADIR will have access to all their country FRAs. FIR Chiefs will have access to their own FIR FRA's.

3.3 - Exception to the guidelines in 12.2.2 can be made when very dense traffic is expected, f.i. during organised fly-ins.
In that case f.i. _APP and _CTR could be reserved for C1 controllers. It is a matter of course that this is dependant of the availability of C1 controllers.

3.4 - FRA's have to be clearly announced in the Division's main page, and it should be explained very well to all users how FRA's work.

3.5 - Division Staff members will have to check that their users follow the established FRA's. Talk with users not following FRA's. If there occur any problem, call the assistence of a Supervisor. Supervisors will follow Supervisor Guidelines instructions.

3.6 - IVAO HQ reserves the right to modify, add or cancel any FRA's at discretion, without statements of reasons.

3.7 - On AOC/AOAC discretion: for some events ATC will be asked to subscribe by AOC/AOAC.
Depending the event, possibly the FRA will be temporarily changed by DIR/ADIR.

3.A. For Belgium