The ATC activities within the France division take place according to the IVAO Rules and Regulations (R&R, section "ATC Operations Department"). However, some rules specific to France division, eventually published via NOTAM, are also applicable in addition to R&R.
Last updated : 30/08/2022
It is in the good practices of the Air Traffic Controller to prepare his ATIS before connecting on the network and to fill it in as quickly as possible once connected and before the taking the charge of traffic awaiting. The content of the ATIS must be in accordance with the information given in the real ATIS as far as practicable.
The French division strictly applies the "Regulation" §A.2.1.2. Which means that the systematic and mandatory use of real NOTAM is forbidden outside of extraordinary publications from IVAO HQ or Divisions. However, specific and temporary procedures inspired from the real world may be proposed exclusively by the ATC and indicated on his/her ATIS only whenever they are compatible with the technical limitations of the IVAO network and of the flight simulators. In all cases, an ATC is not allowed to refuse a procedure to a pilot who would not wish/be able to apply that NOTAM.
It is reminded that the "mode S" transponder is mandatory in France since March 31st 2007 for all IFR flights and for VFR flights in some airspaces.
For all other VFR flights the "mode C" transponder is the minimum required. On IvAc 1, the $ flag will be displayed on the label of any aircraft not equipped with the mode S transponder.
It is forbidden to accept a flight with a flight plan not including an active transponder ("mode N").
The assignment of transponder codes on IVAO is under the initiative of ATC. Nevertheless, it is recommended to comply with the following instructions:
For all flights meant to cross the airspace of, or land in the United Kingdom, a discrete transponder code (≠ 1000) should be assigned as part of the departure clearance received in the airport of origin.
As long as the traffic density allows it, the ATC of French-sectors handing off a flight to the ATC of a UK-sector will make sure a discrete transponder code is assigned.
Taking into account ATC software performance (Aurora) and with the aim of harmonizing the possibilities of all approach sectors, the lateral separation minima under radar control within France division are:
In the case of ATC exams under the responsibility of the Training department, any radar separation (within a TMA and associated airspaces) greater or equal to 3 NM and lower than 5 NM is not sanctioned by an automatic failure. Nevertheless:
The corresponding NOTAM of this rule is available here: N-FR-0421-1_EN.
Within the French division, the opening of civil secondary positions (DEL, DEP and U_CTR) is as follows :
DEL positions, wherever they exist, may only be opened if the corresponding GND position (or higher) is active and according the current applicable FRAs.
DEP positions, wherever they exist, may only be opened if the corresponding APP and TWR positions are active and according the current applicable FRAs.
Moreover, before any opening of a DEP position, the controller of the APP position must have given a written consent to the controller wishing to open the DEP position.
U_CTR positions, wherever they exist, may only be opened if all the primary CTR positions belonging to the same FIR are active and according the current applicable FRAs.
Moreover, before any opening of a U_CTR position, the controllers of all the primary CTR positions must have given a written consent to the controller wishing to open the U_CTR position.
In general, primary CTR positions will delegate their airspace above FL295 whenever U_CTR positions are active.
Diagrams and operational details relative to these positions are available in the LoAs of the Division.
The list of primary and secondary CTR positions can be found hereunder:
The corresponding NOTAM of this rule is available here: N-FR-0121-1_EN.
An ATC schedule is established by the FIR Chiefs involved in the event as well as the Event Department and is approved by the ATC Department.
The only people allowed to open the ATC positions related to an event are the ones which were registered in the ATC schedule (or the people exceptionally allowed to do so by the FIR Chiefs or the ATC Department).
Whenever a member who is not registered in the ATC schedule has already booked a position concerned by the event on the IVAO ATC Scheduling System, the ATC Department will contact the member and delete his booking.
Some events are eligible to a point counting toward the attribution of the « ATC Event Award ». The points are given by the ATC Department based on the list of people present during the event.
The Training Department is in charge, among other activities, of tower position trainings and ADC rating exams. Within this framework, all procedures and skills proper to ground and delivery control are also taught and evaluated.
Therefore, during the following activities:
The GND position cannot be opened. This also includes the DEL position.
Any member connected on the GND or DEL position, notwithstanding if he has booked the position or not, will have to leave his position when asked by a trainer/examiner (or any staff member of the division).
The activities linked to the Training Department (ATC School modules, Trainings, Exams) systematically go in pair with a booking on the IVAO ATC Scheduling System by the concerned member. However, if the booking cannot occur because another booking already exists, the ATC activity of the Training Department takes precedence over the existing booking. In this case, the ATC Department will delete the booking of the member not concerned by the Training activity after having informed him.
Regarding the ATC positions which are directly adjacent to the one where a training activity occurs:
Any member is free to book these positions on the IVAO ATC Scheduling System. However, it is actively recommended to contact the controller in training to inform him and ask if one’s booking is acceptable.
If the controller in training has foreseen specific controllers to open the directly adjacent positions, a systematic booking on the IVAO ATC Scheduling System shall be done by these controllers. However, if the bookings cannot occur because other bookings already exist, the will of the controller in training takes precedence over the existing bookings. In this case, the ATC Department will delete the bookings of the members not foreseen by the controller in training after having informed them.
In any case, no booking will be deleted less than 12h before the activity linked to the Training Department.
The NOTAM corresponding to this rule is available here: N-FR-1117-3_EN.
It is possible to open a position called “AFIS” on IVAO. This type of position is controlled in a slightly different way than a conventional "tower". This is why, in order to announce to the pilots that there will be no control service but only information and alert services, we recommend two things to the controller:
We insist on the fact that these two "rules" are recommendations only. Indeed, nothing would forbid to open an AFIS position with the callsign "LFXX_TWR".
The NOTAM corresponding to this rule is available here: N-FR-1018-1_EN.
The « Flight Service Station » position is used on IVAO as the position which provides the information and alert ATC services. It corresponds to the ATC-units which we commonly call “Information”.
In French Division we do not use the FSS Positions because the “Information” ATC-units are bound to an Approach position. In practice, this means that an Approach position managing one (or more) TMA also manages one (or more) SIV (“Secteur d’information de vol” which translates to “Flight Information Sector”).
It’s worth mentioning that when the Approach services are provided by a Centre position, the “SIV” is always considered open and that the “Information Service” is due to pilots. However, if traffic does not permit the ATC to provide such service, it can be temporarily suspended as long as an explicit indication is written in the remarks of the ATIS.
The NOTAM corresponding to this rule is available here: N-FR-0822-1_EN.
Aurora gives the possibility to transmit a Voice ATIS like in real life via the ATIS frequency of an aerodrome. There are 2 types of transmission possible: TTS (Text-To-Speech) and VOICE (Recording of a controller’s voice) which are described here-below.
The manual of this functionality can be found by clicking on this link.
The Aurora Sectorfile of the French Division is configured in such a way that TTS follows the recommended sequence of the French CAA in their Phraseology Manual. It has been lightly adapted to reflect IVAO’s need. This sequence is pre-filled with tags where the content depends on the parameters filled in the ATIS Menu Bar.
Certain common abbreviations are read with their full word signification when typed in the “Remarks” field. This is the case for RWY or TWY which will be read aloud as “Runway” or “Taxiway” respectively.
The standard language linked to ATIS on IVAO is English. Even though the VOICE transmission type allows to record an ATIS in French, it is mandatory to record an ATIS in English before continuing with an ATIS in French.
If you are not comfortable with the idea to record yourself in English, please use the TTS transmission type.
The basic text to pronounce during the recording can be found below. Make sure to replace the [tags] by the corresponding information.
A METAR should be decoded vocally and not include the following elements: ICAO of the aerodrome, the date and time (since this information is already transmitted at the beginning of the recording) as well as the code “AUTO”.
Any information regarding runway condition like: GRF, MOTNE, … is considered unnecessary on IVAO.
Bonjour, this is [STATION_NAME] information [ATIS_LETTER].
Recorded at [ATIS_TIME] UTC.
Runway in use [DEP RWY] for departure and [ARR RWY] for arrival.
Transition altitude [TA]. Transition level [TL].
Inform [STATION_NAME] on initial contact you have received information [ATIS_LETTER].
Bonjour, this is [Blagnac] information [Alpha].
Recorded at [0_8_2_0] UTC.
Runway in use [3_2_Right] for departure and [3_2_Left] for arrival.
Transition Altitude [5000 feet]. Transition Level .
[Position closing at 1_0_0_0 UTC ; Expect ILS Approach ; …].
[Wind variable, 3 knots, clouds few 1_300 feet, broken 2_600 feet. Temperature 3_3, dew point 1_2. QNH 1_0_1_0. NOSIG].
Inform [Blagnac] on initial contact you have received information [Alpha].
Bonjour, ici [NOM_DE_LA_STATION] information [LETTRE_ATIS].
Enregistrée à [HEURE_ATIS] UTC.
Piste en service [DEP RWY] pour les départs et [ARR RWY] pour les arrivées.
Altitude de Transition [TA]. Niveau de transition [TL].
Informez [STATION_NAME] dès le premier contact que vous avez reçu l’information [ATIS_LETTER].
Bonjour, ici [Blagnac] information [Alpha].
Enregistrée à [0_8_h_20] UTC.
Piste en service [32_Droite] pour les départs et [32_Gauche] pour les arrivées.
Altitude de Transition [5000 pieds]. Niveau de transition .
[La position fermera à 10_h_10 UTC ; Prévoyez une approche ILS ; …].
[Vent variable, 3 nœuds. Nuages peu à 1_300 pieds, fragmentés à 2_600 pieds. Température 33, point de rosée 12. QNH 1_0_1_0. NOSIG].
Informez [Blagnac] dès le premier contact que vous avez reçu l’information [Alpha]