General Regulations

S.1.1 Special Operation flights are all flights operating as Operational Air Traffic (OAT) regulations.

S.1.2 Special Operations on IVAO are defined as aerial military operations, aerial work and other aviation flights, be that activities or operations that are performed under rules and procedures other than those that fully comply with ICAO Standard and Recommended Practices (SARPs) or other civil rules and procedures. Controlling military units and other units, other than civil air traffic services, responsible for flights mentioned above also fall under the regulation of Special Operations.

• S.1.2.1 The definition in Regulation 1.2. includes, among others, the following (this list is NOT exhaustive): Aerial Military Operations, Aerial Work or Specialised Operations, Police and Customs Operations, Any Specialised or High-Risk Aerial Operations and Any Other Aviation Flight (activities or · operations) that deviate from ICAO SARPS or other civil rules and procedures (such as flights conducted below minimum heights, helicopter operations outside the height velocity diagram etc.)

S.1.3 Special Operations Regulations and any other addition (permanent or temporary) are mandatory for compliance by all IVAO users.

S.1.4 It is strictly prohibited to organise or perform any activity on the IVAO network that recreates either entirely or in part, present or past, any real-world warfare or significant real-world event that led to the loss of life. Furthermore, it is prohibited to conduct any activities or operations that may antagonise any user of IVAO or create controversy, irrespective of the reason.

S.1.5 Military operations constitute a significant part of Special Operations; the execution of specific military operations in full compliance with these regulations shall not be interpreted by spectators as a simulation of aggression. Furthermore, real-world perspectives or events shall not influence a spectators’ interpretation of military operations when they are being performed in compliance with these regulations.

S.1.6 Special Operations activities or operations may only be carried out by users within the airspace of their Division as stated on their profile. Exemptions to this are:

• S.1.6.1 Approval has been obtained from a Division other than the members own and their VID is present on that Division’s current Special Operations Order.
• S.1.6.2 In a division that has declared that there is no requirement to get permission to fly SO within that Division. (as per Regulation 1.7).
• S.1.6.3 Partaking in (unplanned) activities or operations where traceable permission (message, email) form the hosting Division has been obtained, and the activities are supervised by division staff for the duration of the activities.
• S.1.6.4 Partaking in activities or operations as part of a Special Operations Event.
• S.1.6.5 Partaking in activities or operations as part of a Special Operations Tour.
• S.1.6.6 Partaking in activities or operations of a Special Operations Group which is registered to that Division and the user is an enrolled member or has been included in such activities or events by a SOG that it is registered in a division.
• S.1.6.7 Partaking in activities or operations in a country where no established division exists (as per Regulation 1.6).

S.1.7 It is prohibited to perform Special Operation activities or operations/missions of a military kind in a country without an active division. Non-military activities or operations can be performed so long as the aircraft type(s) being utilised are not capable of carrying weapons or munitions by design. Aircraft that can carry munitions can only fly in such countries to transit via the area and shall not conduct any missions and therefore not conduct a Special Operations flight.

S.1.8 A Division may wish to forgo the requirement for users from other divisions to gain permission to fly SO in the Division. Therefore, allowing any users to conduct SO without prior permission and this shall be indicated within the divisions SO Order.

S.1.9 Aircraft shall not be flown in segregated or restricted airspace that has been published in a Division’s Special Operations Orders or on the IVAO NOTAM system except under the conditions of the airspace restrictions.

S.1.10 It is prohibited for a user to perform interceptions, targeting or escorting of any traffic outside of the Division stated on their profile. Exceptions to this regulation can be made for users actively participating in a Special Operations Divisional/ International Event or has been cleared in other divisions, being listed in their SO Order.

S.1.11 A user may perform interceptions, targeting or escorting, so long as all parties (the user(s) being intercepted and the user(s) intercepted) have a written agreement, via private message through IVAO clients, in place PRIOR to the interception commencing. This type of activity must also be conducted in one of the following two ways:

• S.1.11.1 Inside segregated airspace – Users may conduct interceptions, targeting or escorting without the requirement of an online air traffic controller inside any segregated airspace published under Item 1 of the Division’s current approved Special Operations Order.
• S.1.11.2 Outside segregated airspace – Users may conduct interceptions, targeting or escorting outside of the published segregated airspace so long as there is an active air traffic controller connected who is responsible for the area(s) desired to be utilised and the user has the controller’s written approval, via private message through IVAO clients, to operate within their airspace. This approval can be withdrawn at any time, and the activity or operations must not be a nuisance to a fellow user(s) of that airspace.
• S.1.11.3 SO Pilots can conduct interception, targeting and escort missions of any MILITARY aircraft flying inside their division (or in any division where it is cleared to conduct SO), same rules apply as before, need to have a written clearance from target aircraft and ATC (if online).
• S.1.11.4 Interception of unresponsive pilots flying inside controlled airspace (with active ATC): SO Pilots can conduct Interception and Identification missions if it ́s requested by the ATC for:
  • S.1.11.4.1 Unresponsive aircraft flying inside their airspace with transponder off or not valid.
  • S.1.11.4.2 Deviates from a filled flight plan.
  • S.1.11.4.3 Does not establish a 2 way communication with active ATC.
  • S.1.11.4.4 Interception and identification of unresponsive aircraft ends at 1 NM horizontally and 1000ft vertically, intercepting pilots are not allowed to fly closer to target aircraft.
• S.1.11.5 All interceptions performed for identification of civil aircraft must be conducted following ICAO Annex 2, appendix 2 “INTERCEPTION OF CIVIL AIRCRAFT” https://www.icao.int/Meetings/anconf12/Document%20Archive/an02_cons%5B 1%5D.pdf

S.1.12 Formation flights shall be based on realism and be used for the purpose of formation flying only. While formation flying is not a special operation, most military forces conduct their flights in formation. Do not confuse formation flying from A to B (NOT SO!) with a mission such as a Combat Air Patrol (YES, SO!).

S.1.13 Formation flights shall not be seen as escorting unless explicitly stated. All parties involved shall agree to partake in any formation. Formation flying shall not be used as a means to intercept a user who does not wish to be intercepted.

S.1.14 IVAO users can obtain approval to conduct Special Operations in a Division other than that stated on their profile by emailing the relevant Divisional Special Operations Staff or Division HQ. Once permission has been granted, and an updated Special Operations Order has been approved and published with the user’s VID listed, they may perform Special Operations in that Division with no additional restrictions placed. This permission is not required by some divisions and will be stated in the Division’s Special Operations Order if this is the case.

Air Refuelling Operations

S.2.1 Any pilot can provide AAR to others in any occasion, this activity won’t be restricted to only events, following these guidelines:

• S.2.1.1 Tanker pilot is flying either inside the registration division or in any division where has been cleared to conduct SO and is listed in said division SO Order.
• S.2.1.2 Tanker pilot has coordinated airspace use and general AAR operations with the divisional Special Operations Department or the HQ Special Operations Department for places where there is not an established divisional Special Operations Department.
• S.2.1.3 Tanker pilot is following standard procedures for AAR, such as ATP56, or HQSOD documents, and communicating via voice to the receivers using either VHF on IVAO Pilot clients or HQSOD Discord #boom channels.

S.2.2 In cases where both tanker and receivers are flying together and perform AAR en route, it will be allowed as long as they are in formation.

S.2.3 At no time can an AAR be performed if there is no coordination between pilots and divisional / HQ staff.

Use of Weapons

S.3.1 Use of any form of weapon against any civilian object, structure, aircraft, or individual, whether this is explicit or implicit is strictly prohibited. It is also strictly prohibited for participants of Special Operations Events that involve the use of weapons to use them against any other traffic which is not partaking in that event.

S.3.2 The use of any form of weapons are only authorised inside designated special areas that have been published on the IVAO data system and have been declared as a “Weapon Range” by the corresponding Divisional Special Operations Staff.

S.3.3 A user may only use weapons when operating within the airspace of the Division as stated on their profile or if the user has obtained permission to operate in a foreign division and published in the Division’s Special Operations Order. Exemptions to this is when participating in a Divisional or International Event.

S.3.4 The final authority on the use of weapons within a Division is the decision of the Divisional Special Operations Staff by establishing, or not establishing, a range.

AWACS Operations

S.4.1 Any pilot can conduct AEW orbits in any occasion, this activity won ́t be restricted to only events, following the same guidelines as stated for AAR, but we will add the following:

• S.4.1.1 AWACS pilots are meant to be flying the aircraft inside an orbit; double connection (as pilot and ABM) won ́t be allowed.
• S.4.1.2 Air Battle Managers / Combat controllers are the real operators of the AWACS radar and sensors, and they will be able to connect using “ABCD_AEW_CTR” on their IVAO Control clients.
• S.4.1.3 AEW_CTR positions will be created on request by email, in accordance with each divisional SO Order, in case where an AEW_CTR position is required and there ́s no local SO Dept, contact HQSOD.
• S.4.1.4 AEW_CTR positions can be requested for events and Special Operations activities inside a division. As before, always coordinating with the divisional Special Operations Department or HQ Special Operations Department.

Special Areas (Navigation Warnings)

S.5.1 Special areas are pieces of airspace that shall be established to allow certain activities or operations to be conducted in a safe manner. These restrictions can be permanent or temporary and should, if possible, be based on a real-world equivalent and must be established as per Special Operations Instruction No. 4.

S.5.2 Areas that allow the use of live ordnance or weapons shall be declared as a “Weapon Range”.

S.5.3 The following activities or operations listed below must make use of special areas designated for such activities when being conducted on the IVAO network: application of weapons (S.3.2), air combat training, launching and recovery of space vehicles, mass movements (mass aerial activity) of aircraft within a relatively small volume of airspace, interceptions (quick reaction alerts, targeting, escort, as well as training of these activities etc.) unless operating as per Regulation S.1.11.2., the dropping of objects or paratroopers, any other activities or operations that are likely to pose a hazard to civil aviation.

S.5.4 Segregated airspace may be created or requested by the following: Special Operations HQ (SOD, SOAD or SOAx), Division HQ (DIR, ADIR), Division Special Operations Staff (SOC, SOAC, SOAx), Event organising parties with permission from the host Division, Special Operations Groups for training, sent via their Divisional Special Operations staff.

S.5.5 A minimum of one Special Area shall be established by an active Division and must be stated in their Divisional Special Operations Order, but there are no minimum requirements to have a published Weapons Range.

S.5.6 All special areas established in a Divisional Special Operations Order shall be activated by one of the following methods:

• S.5.6.1 Permanently Active – the special area is permanently active.
• S.5.6.2 By date and time – the special area is active on specific dates and/or times that are stipulated in the Divisional Special Operations Order.
• S.5.6.3 By NOTAM – the special area will be activated by a published NOTAM on the IVAO Data System stating the start and end date/ time of activation and closure.
• S.5.6.4 By Air Traffic Controllers – the special area can be activated by an air traffic controller connecting and stating in their ATIS that a specific airspace within their area of responsibility is active. This method can be used in conjunction with any other method previously mentioned in Regulation S.5.6.

S.5.7 Temporary special areas can be established under the methods stated in S.5.6.2, S.5.6.3 or S.5.6.4 without the need to be published in a Division Special Operations Order. In all instances, these temporary areas of airspace must be listed on the IVAO Data system (NOTAM’s and/or special areas) and be active for a period of no more than 72 hours.

Special Operations Group (SOGs)

S.6.1 The status of a Special Operations Group, and its acronym “SOG”, are explicitly reserved for use by approved groups that have achieved and maintained the standards and requirements as set out in Special Operations Instruction No. 1 and are listed on the Special Operations Group page.

S.6.2 Once a Special Operations Group has achieved this status, they receive access to extra privileges that not available to regular users, these are:

• S.6.2.1 To request, via Division Special Operations Staff, the establishment of special areas for use by the Special Operations Group for training missions.
• S.6.2.2 To organise their own Special Operations International Events.

S.6.3 Unless specified in the Special Operations Groups’ own internal rules, a user may join any Special Operations Group and perform flights under their privileges irrespective of their Division stated on their profile.

S.6.4 A Special Operations Group is tied to their founding user’s Division as of the time of filing an application to become a Special Operations Group. This country will be known as the Special Operations Group’s ‘country of registration’.

S.6.5 Special Operations Groups may only operate in their country of registration unless they are:

• S.6.5.1 Partaking in an approved International Special Operations Event if registered (if required) and in Divisional Special Operations Events with prior approval from the Division.
• S.6.5.2 Partaking in a published Divisional Special Operations Tour or Special Operations HQ World Tour.
• S.6.5.3 Approved by another Division to conduct Special Operations in their country and the Special Operations Groups are listed under Item 7 of the Division Special Operations Order alongside any restrictions the Division may wish to put in place.

S.6.6 Groups wishing to become an approved Special Operations Group must follow the procedure and meet the requirements as stated in Special Operations Instructions No. 1.

S.6.7 Special Operations Groups are required to continuously meet the requirements as stated in Special Operations Instruction No. 1 and the Special Operations Department has the right to revoke the status of approved Special Operations Group at any time, without notice, if these requirements are not maintained.

Events

S.7.1 International Special Operations Events may be organised by Special Operations HQ, Divisional Special Operations Staff and approved Special Operations Groups. The initial approval of Special Operations Events lies with the host division, and final approval is given by Special Operations HQ. International Special Operations Events are the only type of event where members can achieve points towards a Special Operations Award. International Special Operations Events are open for all IVAO users to participate in.

S.7.2 Divisional Events are localised events that are targeted to users of the host division and therefore do not require Special Operations HQ approval. However, they are required to abide by the Special Operations Regulations and are not able to award Special Operations Points.

• S.7.2.1 Any IVAO user may attend a Divisional Special Operations Event, but users who are not from the host Division shall obtain prior written approval from the Divisional Special Operations Staff.

S.7.3 An International Special Operations Event may be run parallel, or in conjunction with an ordinary network event. However, participants of the International Special Operations Event will be unable to claim points or awards for participation in the ordinary network event; their participation is in one or the other.

S.7.4 International Special Operations Events shall be created and conducted following Special Operations Instruction No. 5.

S.7.5 Divisional Special Operations Events shall be created and conducted following Special Operations Instruction No. 6.

S.7.6 Users who do not register on the Special Operations HQ website for an event that is using the mandatory registration process will be regarded as not participating by the organiser and Special Operations HQ and is therefore not eligible for Special Operations points.

S.7.7 A Special Operations Event shall only take place in the Division where the event organiser (Division Staff or Special Operations Group founding user) is registered unless the event is co-organised with another Division(s).

S.7.8 For participation in an International Special Operations event each participant, both Air Traffic Controllers or Pilots, will be awarded two (2) Special Operations points per event. If the event is held over multiple days, the participant will be awarded one (1) Special Operations point per day they have attended.

• S.7.8.1 Additional points may be awarded by Special Operations HQ where they feel the participation in multi-day events is more deserving than one (1) point per day. This clause is at the complete discretion of Special Operations HQ.

S.7.9 Special Operations HQ wishes to acknowledge the contribution members make to the Department by attending and supporting events. Accumulated points contribute towards Special Operations Awards and the requirements to achieve each one are detailed on the Special Operations Awards page.

Tours

S.8.1 There are two types of Special Operations Tours that can be established: Special Operations HQ World Tour and Division Special Operations Tour.

S.8.2 World Tours are created and managed by Special Operations HQ with tour legs moderated by World Tours HQ. Any flight flown for these tours shall be logged on https://www.wt.ivao.aero.

S.8.3 Any IVAO user may participate in any Special Operations Tour: both Divisional and World Tour.

S.8.4 Divisional Special Operations Tours are developed and managed by the Divisional Special Operations Staff of the respective Division following Special Operations Instruction No. 6a.

S.8.5 Divisional Special Operations Tours are required to be available in English. They can be hosted on either the Division’s website or via an IVAO Tours System.

S.8.6 Divisional Special Operations Tours that do not contain activities or operations that are considered by these regulations as Special Operations will not be classed as a Special Operations Tour.

S.8.7 It is prohibited for a Divisional Special Operations Tour to partly or wholly operate in a country where no established division exists. Overflight of these countries is permitted, as long as the flights are conducted in conjunction with ICAO or local standard operating procedures (SOPs).

S.8.8 Divisional Special Operations Tours can contain parts of their tour in another Division’s airspace other than their own, but these tours must be co-organised with the other Division.

S.8.9 It is strictly prohibited for Divisional Special Operations Tours to include legs that involve the use of weapons.

Divisional Special Operations Departments

S.9.1 A Divisional Special Operations Department is considered to be active if a minimum of a Special Operations Coordinator appointed and a Divisional Special Operations Order approved and published.

S.9.2 The following duties and responsibilities lie with Division HQ in relation to Special Operations:

• S.9.2.1 MANDATORY (even in the absence of a Special Operations Coordinator):
  • S.9.2.1.1 Familiarisation and compliance with all Special Operations Regulations, Instructions and other official published documents.
  • S.9.2.1.2 Development and publication of a Divisional Special Operations Order in compliance with Special Operations Instruction No. 3.
  • S.9.2.1.3 Management of Special Operations Groups
  • S.9.2.1.4 Processing requests from IVAO users, external from the Division, to person Special Operations Flights within the Division.
• S.9.2.2 With a Special Operations Coordinator appointed:
  • S.9.2.2.1 Development of a Divisional manual on controlling military units and other Special Operations units. This must be written in English, but can additionally be in the Division’s local language(s).
  • S.9.2.2.2 Development and maintenance of a Special Operations section on the Division website and forum.
  • S.9.2.2.3 Development and publication of Special Operations related materials for the Divisional Special Operations community.
  • S.9.2.2.4 Undertaking active steps in promoting Special Operations at a Divisional level.
  • S.9.2.2.5 Engage with the Divisional Special Operations community.
  • S.9.2.2.6 Engage with members of the Special Operations community who are not yet registered with the network.
  • S.9.2.2.7 Develop and execute Divisional and International Special Operations Events.
• S.9.2.3 The duties stated in Regulation S.9.2.2 are considered as generic. A detailed list of duties for Divisional Special Operations Staff to comply are found on the IVAO Roles and Responsibilities Wiki page.

Documents

S.10.1 Divisional Special Operations Orders are a Division’s extension of the Special Operations Regulations and following such orders have mandatory compliance when conducting Special Operations within the respective Division.

S.10.2 Special Operations Orders shall be created in accordance with Special Operations Instruction No. 3.

S.10.3 Special Agreements are documents that establish a formal agreement between multiple parties.

S.10.4 Special Agreements are highly detailed documents that define a procedure or protocol between parties or can be used as exemptions from the Special Operations Regulations or other published documents. These agreements cannot be made with individual users or unregistered Special Operations Groups. These agreements shall be established in accordance with Special Operations Instruction No. 7.

S.10.5 The current list of Special Operations Instructions are as follows:

• S.10.5.1 Special Operations Instruction No. 1 – Special Operations Groups
• S.10.5.2 Special Operations Instruction No. 2 – Special Operations Departments
• S.10.5.3 Special Operations Instruction No. 3 – Special Operations Order
  • S.10.5.3.1 Annex A – Divisional Special Operations Order (Example)
• S.10.5.4 Special Operations Instruction No. 4 – Airspace restrictions and reservations
• S.10.5.5 Special Operations Instruction No. 5 – International Special Operations Events
• S.10.5.6 Special Operations Instruction No. 6a – Divisional Special Operations Tours
• S.10.5.7 Special Operations Instruction No. 6b – Divisional Special Operations Events
• S.10.5.8 Special Operations Instruction No. 7 – Special Agreements

Training Department

General

T.1 IVAO examination regulations and GCAs are controlled by 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.

GCA

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.2.1 All users with an ADC (or higher) rating can apply for a GCA.
• T.2.2 The GCA shall only be used to determine if a user is able to properly apply the local procedures on the respective FRA restricted position. Divisions may require a checkout to assess the level of competence. Divisions reserve the right to revoke a GCA in case the required level of competence is no longer met.
• T.2.3 Divisions may require GCA holders to speak the local language but must demonstrate this requirement based on real-world need.
• T.2.4 The Training Director, Training Assistant Director and Senior Regional Training Advisors are allowed to log onto any ATC position on the network regardless of GCA restrictions for training and exam purposes.

Exam

T.3.1 IVAO pilot and/or ATC exams can only be performed in approved IVAO 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. 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 Regional Training Advisors.

T.3.6 All IVAO exam results are pending validation by the Training Director, Training Assistant Director and/or Senior Regional Training Advisors. Successful completion of the exam after validation by IVAO HQ, will result in the 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 to Senior Regional Training Advisors. They 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 to the Training Director and Training Assistant Director. 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 may not request any practical exam for 90 days. Exceptions can be made by the Training Director and Training Assistant Director after consultation with the division’s Senior Regional Training Advisor.

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.

World Tours

WT.1 Flights must be completed in real-time mode (1x sim rate). No other mode (slew or acceleration) is permitted on the IVAO Network.

WT.2 Flights must be completed online using real-weather injection from the simulator (if available) or from software capable of providing real-weather.

WT.3 Legs need to be flown in the correct order and a PIREP must be submitted within 7 days. PIREP’s must be reported in UTC format as ‘Take-Off’ and ‘Landing’ times.

WT.4 After connecting to the network, your aircraft must be stationary (park brake ON), on the apron or at the gate for a minimum of 1 minutes. After landing and taxiing to the apron or to the gate, your aircraft must be stationary (park brake ON) while still online for a minimum of 1 minutes.

WT.5 After completing a flight and after waiting for 1 minutes, you must disconnect from the network before starting your next flight.

WT.6 A maximum disconnection time of 30 minutes will be accepted for flights longer than 2 hours, due to a simulator or PC crash (you must report UTC times with a brief explanation when submitting the flight). When reconnecting to the network, your flight must be initiated no further than 100 NM from the point of disconnection.

WT.7 Unless the published limits of the airspace allows, or unless instructed by online ATC, the Maximum Allowed Speed below FL100 (10000 ft) is 250KIAS.

WT.8 The pilot is responsible for ensuring the flight plan is correct before departing. Flights with the wrong: a) ICAO codes for Departure / Destination / Alternate Airports, or b) Flight Rule Type, or c) with incorrect Aircraft information, after take-off, will not be accepted. If the flight plan is changed after take-off or after landing for a) or b) or c) until disconnection (even if you submit a next flightplan), the leg will not be accepted!

WT.9 Flight plans with a valid route are required. Flights with DCT where there is a valid real life route and/or DCT/GPS or simple DCT as a route in the flight plan will not be accepted! Composite flight plans Y and Z, will be accepted only if the departure/destination airport requires so. Legs that allow composite flight plans are indicated in the description of the tour/leg.

WT.10 Your flight plan must include at least one real alternate airport. It is the pilot’s responsibility to ensure a valid alternate airport is included in your flight plan. The departure or destination airport of that leg (or next leg) will not be accepted as a valid alternate, with the exception that the departure or destination airport is remote. The legs which feature remote airports are indicated in the description of the leg.

WT.11 As Pilot in Command (PIC), you must choose an aircraft that is suitable and can operate safely and within limits for every airport of the tour or as stated in the tour rules or leg description. See the description of the tour or the description of the leg. No refueling stop(s) or diversions to alternate are allowed.

WT.12 Every flight must include RMK/WORLDTOUR in the remarks section of your flight plan.

WT.13 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 in addition to the regulations here.

---