Those general rules for tours are applicable to all French division pilot's tours. Are excluded ATC tours and Special Operations tours.
Some tours might have specific rules. In case of conflict, specific rules overrule general rules.
All flight must be performed online on IVAO network, with real weather. They have to be accomplished in real time rate (simulation rate x1 only, accelerated mode prohibited)
Legs must be accomplished in the published order
Speed restrictions IAS<250kts below FL100 must be observed.
During cruise phases, a disconnection up to 20 minutes is tolerated, providing the fact that it does not disturb the network operation, especially under ATC coverage. Please report any disconnection in your pilot report.
The use of UNICOM in text mode, in absence of active ATC online, is MANDATORY. Legs might be rejected if not compliant.
All legs must be validated by sending a pilot report. It is essential to read and understand validator's comment for each leg, including if the leg is validated. We advise to not pursue the tour without validation of previous leg.
Pilot report must be sent within 12 days following the flight date. Any leg sent outside the window will be rejected.
Pilot report must include list of ATC contacted during the flight, and procedures performed during the flight.
A 'Direct to' is allowed, only with ATC instruction. Please mention any direct obtained in the pilot report.
It is mandatory to disconnect from the network at the end of each flight.
Pilots will be particularly aware of:
Minimum and maximum airways altitudes
Published procedures when ATC is offline
VFR circuit integration
Avoid P zones, as well as R zone when activated (Special Operations link)
Take a really good care of your flight plan:
Flight plan with wrong or misspelled airports will be rejected
Filled equipment must be compatible with the aircraft
Prevailing flight plan will be the active one during take off
Operate the flights under military or any other Special Operation type is not allowed. Type of flight must only be G, S or N.
It is requested to be connected on the network at least 2 minutes before take off, and stay connected at least 2 minutes after landing. This will allow the tracker to save your flight entirely.
An IFR route, IFPS compliant at the time it is published, might be proposed on some legs. It is only a suggestion, you can perfectly fly your own route.
One flight can only be reported once, for one leg on one tour, even if the leg can fit for 2 tours or more.
Flight as a crew of two pilots, with shared cockpit functionality, is permitted on division's tours. However, only the pilot "master" of the connection is allowed to fill a pirep. The second pilot, connected as an observer, will not be allowed to fill a report based on this flight.
Should there is any follow-up or contestation after a leg validation, everything has to be sent only at firstname.lastname@example.org. Supported languages are English or French. They have to be sent no later than 7 days after leg validation