banner

Home NOTAMs About the Race Official Rules Rules FAQ Follow the Race Resources Forum

The rules for the Race are divided into two parts. The first part, the General Rules and Charter, stays the same from year to year. The second part of the rules is known as the Special Rules and Routing and will vary from year to year.

2010 RTW Race Information:

Official Starting Time: 9:00 AM US Eastern Time (1400Z) Saturday, 20 February, 2010 for the Optional Start Event.
The Race portion will begin at 11:30 AM PM US Eastern Time (1630Z) Saturday, 20 February, 2010.
Special Rules Release Time: NOW RELEASED.

2010 Flight Simulator Around-The-World Race
ROUTING AND SPECIAL RULES

  1. Starting Time.

    The race will begin with a special kickoff event at 1400 UTC (0900EST, 1400L) at Manston Airport, England, United Kingdom (EGMH).

  2. Special Optional Start for the 2010 Race - Operation Dynamo.

    Overview.

    70 years ago during May 1940, one of the greatest retreats in world history took place when the Allied forces (198,229 British and 139,997 French) were evacuated from the French beaches of Dunkirk. The success of Dynamo prevented a breathtaking disaster and turned the tide of the war.

    The Royal Air Force, using Spitfires, Defiants, Albacores, Swordfish, Skua's, Roc's and others, flew in support protecting the perimeter as the German forces advanced. Flying from Manston 40nm away, the flights would converge in the sea lanes and beyond Dunkirk to stop the advancing Germans. As a result, the beachhead was seriously threatened by the Luftwaffe on only two days. In all, the RAF lost 100 aircraft protecting the evacuation. (Most of the air battles were fought inland—and thus invisible to the desperate troops.)

    Here we recreate the spirit of Dunkirk, using aircraft to "rescue" the troops.

    The Rescue Operation.

    The rescue flight demands a transport-capable aircraft be flown from Lydd in the UK (EGMD) to the MK NDB north of Calais-Dunkerque Airport (418.00 – 37.5 nm range approx dist 42 nm course 089). There the aircraft turns toward Dunkirk (approximately 10 nm on course 060). The pilot then executes a full-stop water landing at Dunkirk to effect the rescue. (To minimize the chance of Luftwaffe interception, the pilot should fly at less than 1,000ft. This altitude will not be enforced.) The leg is authenticated with the standard Duenna post.

    The transport aircraft then takes off and flies to Manston – making either a water landing in Pegwell Bay or in Ramsgate harbor near the Manston airfield, or on the runway at Manston (EGMH). (The second leg is approximately 42 nm on course 295.) Any aircraft capable of a water landing may be used as long as it has at least 4 seats. That includes the default FS2004 Caravan, FSX de Havilland Beaver and FSX Grumman Goose.

    If desired, the pilot may take off from the Channel near Lydd and land on the Channel near Manston, as long as the Duenna shows the baton picked up within 4 nm of EGMD and dropped within 4 nm of EGMH. (For more details on water landings, see the FAQ.)

    In addition, to earn bonus credit a combat air patrol (CAP) must be flown by another pilot in a warbird. The warbird must takeoff from Rochester (EGTO) and fly over Lydd at approximately the same time as the takeoff of the paired transport. The CAP must fly the same route and circle over Dunkirk while the transport makes the water landing and takeoff. The CAP aircraft will land at Manston. Any standard race-eligible fighter aircraft may be used in this mission (though period accurate RAF aircraft get style points).

    Each successful pair of aircraft earn a bonus of 30 minutes cumulating up to a maximum of four hours bonus time.

    The baton posts are to be made on a separate thread. The first post would list both pilots and the aircraft. Subsequent posts must include the takeoff posts for each aircraft, the water landing and then takeoff at Dunkirk, and then the two safe arrival posts at Manston. If one pilot crashes, the flight is invalid. Both pilots must restart at EGTO/EGMD.

  3. Race Start from Manston (EGMH).

    On February 20, 2010, following the special start outlined in Rule 2 above, the scored portion of this year’s race will begin and end at Manston Airport, England. From there, you can fly anywhere, but in order to win, each team must meet both the general and the special route requirements (see below).

    Round-the-World flight operations commence at 1630 UTC with the post of an official thread by the Race Executive Committee on each of the teams' forums. Teams begin after the official post or, optionally, they may delay their departure to complete Operation Dynamo. The teams may not start early: the initial departure is to be posted as a reply to the official start thread.

    On the Saturday after the event, all teams and pilots are invited to participate in a celebration flight from Manston to the newly liberated Calis-Dunkerque Airport with a flyover of Dunkirk.

  4. Routing - Continental Briefing Sheets.

    This year, a Continental Briefing Sheet routing system replaces the traditional RTWR routing requirements. Teams must land at the same 12 designated airports, located two per continent. Those 12 airports are fixed before the race, probabilistically selected by the chair of the Executive Committee, who does not participate in the race, and their identities described in six separate briefing sheets. Teams will be able to request these sheets as they proceed around the world.

    All teams fly to the same designated airports. What may vary is the sequence in which the teams open the continental briefing sheets. This special requirement for 2010 replaces the general rules requirement that teams land at two continental airports at least 1,000nm apart. There is no North-South requirement.

    The system works in the following way:

    1. At least 48 hours before the race, each team will form a briefing committee whose members must register with the race organizers. Then, 24 hours before the race, that committee will receive the secret team username and password as well as, separately, a password for each of the continents. Teams are responsible for maintaining the security of these items. The briefing committee may immediately access the first continental briefing sheet by using the secret username and password to sign on to the briefing sheet website here. (The first briefing sheet will already be open. The remaining five must remain locked.)

    2. Teams become eligible to see the briefing sheet for one (1) additional continent upon reaching (that is, completing a leg at) the first required airport at which they arrive on a given continent, or shortly thereafter, (but not another when reaching the second required airport.) They go to the briefing sheet website and, on confirming that they are eligible, unlock the briefing sheet they desire and proceed accordingly. Thus teams are able to ‘see’ only one continent into the future routing of the race.

    3. Teams may not unlock briefing sheets before the team becomes eligible to make them. Because the system is automated, the requested continent will be unlocked whenever it is requested, regardless of whether the team is eligible. Thus the integrity of the race depends on strict adherence to this rule. Accordingly, we have put the following security measure into place:

      All requests to unlock a briefing sheet are logged. Premature requests will be investigated and assessed an eight (8) hour penalty per request. Again, the responsibility for maintaining security lies with the team.

    4. In case of system failure, contact the Executive Committee Duty Officer.

    5. Teams need to organize a way to maintain internal control over the team's username and passwords. If the team username and password are made public, then anyone can use them to make bogus requests. Teams are responsible for maintaining the security of their team username and password and ensuring that they are not used before the team becomes eligible.

      In view of this, each team needs to identify the group of individuals it wishes to grant access to the team password and forward their names and e-mail addresses to the Executive Committee at fsrtwrace@gmail.com. This "briefing" committee must be formed before the distribution of the secret username and passwords - which happens 24 hours before the race.

    6. Teams need not announce publicly that they have reached a required airport or have accessed the briefing website. The identity of a continent's airports may be strategic information and it need not be shared with other teams.

    7. If a team wishes to share the contents of a briefing sheet with another team, it must share that information with all other teams by making the information public. Secret covenants contradict the spirit of the race.

  5. Bonus Airports.

    Fourteen (14) bonus airports are scattered across the globe, two on each continent and two more in the Caribbean. The continental briefing sheets contain the identities of these airports. For each full stop landing at up to six (6) of these airports, a team earns 3 hours bonus time — yielding a maximum of 18 hours. Teams may choose the airports, if any, at which they land.

  6. Normal Legs and Wildcards.

    In 2010, normal legs may extend to a maximum distance of 750nm but remain limited to two hours in duration. In addition, each team has two wildcard flights. The first has a maximum distance of 2,100 nm and the second a maximum distance of 1,650 nm. There is no time limit on these flights. Pilots must fly an aircraft with a takeoff weight of 30,000 pounds or more, they may not exceed the maximum gross weight, and they may choose either a normally race eligible aircraft or a subsonic jet.

  7. Jets.

    In addition to the wildcards, teams may complete up to 5 normal legs in subsonic jet aircraft. There is no weight limit here. The 2 hour duration and 750nm limits of normal legs apply.

    As a special feature, a few airports include a "Bonus Jet" that the teams may optionally use in the departure leg. These subsonic jets are eligible for normal legs and are available for every team reaching the airport. Their use supplements the above-mentioned five jet stockpile.

  8. Special Aircraft Requirements for the 2010 Race.

    Helicopters.

    A total of 250 nm must be flown in helicopters. Both default and add-on helicopters may be used to satisfy this requirement. The V-22 is not considered a helicopter for the purposes of this rule, while the Pitcairn and Kellet Autogyros are.

    Variety.

    Any single aircraft type may be used freely for up to 20 legs maximum. For every leg thereafter, a one hour "maintenance" penalty is incurred on arrival. Realistic models of the Beech King Air, Lockheed P-38, and North American P-51B/C/D (but not H) may be flown without leg limits. See the FAQ for details.

    In 2010, the FSX Acceleration P-51 Racer is eligible for use.

  9. Team Flight Bonus Opportunities.

    During the course of the race, teams may participate in up to two "Team Flights," in which many team pilots accompany the baton carrier and earn bonus time for the team.

    Team Flights available for the 2010 Race are as follows:

    Each Team Flight requires a baton pilot and participating pilots. These flights can take place in any location and at any time—with three restrictions. First, no team flight may be flown during the first 12 hours following the start of the Round-the-World portion of the Race; second, team flights may not be flown concurrently with Airmanship Challenge flights; and third, team flights may not be consecutive—there must be at least one normal leg between two team flights.

    Each participating pilot, not counting the baton carrier, who completes and validates a successful leg will earn a 30-minute bonus for the team. A maximum total of 5 bonus hours can be earned from the two Team Flights combined, of which no more than 3 hours may be earned in a single event. Once a category of team flight has been flown, it may not be re-flown by the same team.

    The baton pilot and all participating pilots must fly aircraft of a specified class, as listed above. The participating pilots do not have to fly the same aircraft as the baton holder. The baton pilot and all participating pilots must takeoff from and land at the same airports.

    Participating pilots may not take off until after the baton pilot has departed. They may land before the baton pilot, but must complete and post their legs within 30 minutes after the baton pilot's "Baton is free" post. The team may continue to advance the baton on the next leg while participating pilots are landing and completing their validations.

    All participating pilots must post their aircraft type, takeoff, landing, and authentication in the normal manner. (A Duenna authentication needs only the textfile.) Finally, after the event and authentications are completed, the team must post a "Team Flight Summary" indicating the number of bonus hours earned in this event and then make the appropriate entry into the Bonus Bank.

  10. Airmanship Challenge

    Teams may optionally choose to complete one (1) Airmanship Challenge. This is a brace of three airports which must be connected by two consecutive legs. A team scores six (6) hours for a successful completion. Three sites host the challenge: teams may choose which they complete. Note that each challenge is available only for daylight or for nighttime operations.

    The daytime challenge must be initiated after the break of local dawn and completed before the end of local dusk. The nighttime challenge must be initiated and completed during local nighttime hours. If a team misses the explicit completion deadline, the team forfeits two minutes of the bonus for each minute by which the deadline was missed. Daytime challenges are CLOSED after local dusk and before local dawn.

  11. Weather.

    In 2010, all flights will be conducted using FS2004 or FSX live weather engine (as supplied by Jeppesen). The appropriate setting is Real Weather with 15 minute updates. Special exceptions will be made for pilots who cannot comply. If the Real Weather system fails for everyone, pilots should switch to the "Fair Weather" theme, contact the Executive Committee Duty Officer, and follow any subsequent instructions from the Executive Committee.

  12. Bonus Bank.

    To speed up the race, teams will keep open accounts of their bonus hours and also be able to apply those hours against any penalty time that they incur. Teams gain bonus hours for the Kickoff Event, Team Flights, Airmanship Challenges and Bonus Airports. This Bonus Bank is public and everyone can quickly keep track of the competition. Care should be exercised to insure as much security as possible.

    Teams are to keep track of bonuses and penalties in the web application located at: http://rtw.eamonnwatson.com/

    Once teams have earned bonus bank hours, they may apply that time against any penalties incurred. (A team may not go in deficit!)

    After a team has earned or expended bonus hours, it is the team’s responsibility to adjust the proper entries to indicate (a) the bonus time earned or expended and (b) the current net balance of hours “in the bank”. The team must complete this accounting within one hour of the transaction. There is no penalty for failure to post the numbers except that the team will forfeit the bonus or will be required to return and serve the penalty in place. (Appeals may be made in the case of accounting errors or a tardy posting. The Executive Committee will be lenient on the first instance of a mistake.) Keeping good records is a team responsibility, not a baton pilot responsibility.

  13. Executive Committee Duty Officer

    The Executive Committee has this year set up a system whereby a Committee member will be available to provide on-the-spot resolution of problems, clarifications, and initiation of the appeal proocess around-the-clock for the duration of the race. This system revolves around an individual Committee member serving as 'Duty Officer' at all times during the race. The system works in the following way:


Flight Simulator Around-The-World Race
GENERAL RULES AND CHARTER

1.    Organization of Rules.

The General Rules for the Race are codified in this document. In addition to these General Rules, which apply to every Around-The-World Race, each year's race will have a set of Special Rules specific to that race alone. These rules will contain the race's starting airport, corridors (special flight routes in which long flights are allowed), and any additional rules, such as special bonuses or prohibitions that are specific to an individual race. They will be made public at least 24 hours before the race start.

2.    Official Website.

http://www.fsrtwrace.com
 
3.    Participants.

4.    Starting Time.

The race begins annually on the weekend following St. Valentine's Day with a post from a member of the Executive Committee in each team’s race forum. The specific starting time for each year’s race will be made public via forum posts and the race website well in advance of the race.

5.    Objective.

The objective of the race is to be the team to successfully carry a virtual baton around the globe in the fastest possible time* by completing and authenticating a series of flight legs using Microsoft Flight Simulator.
 
At the beginning of the event, the organizers start the official Race Thread in each team’s forum, whereupon the first volunteer who responds by stating that they “have the baton” becomes the “baton holder.” This pilot must then immediately go to the race’s starting airport within FS and fly to another airport carrying the baton.
 
Upon completion of the leg the pilot must communicate to the team via the forum that “the baton is free” Upon posting this message, the baton is available again for a new volunteer to take in a similar fashion and the race continues around the planet.
 
The new pilot must start from the airport where the previous leg finished and is free to choose which airport to fly to next. This cycle repeats itself until each forum has made it back to the race starting point, where the fastest team is declared the winner.
 
*Time is defined as the period between the race start and team's arrival at the race end point having completed all race requirements, adjusted for any credits and penalties accrued during the race, as measured by each forum clock.
 
6.    Requirements.

    i.     Routing Requirements.

        a)    General

Teams must begin at the starting airport and return to it by:
        b)     Special requirements.

Teams must complete any requirements specific to a given race, as defined in the Special Rules and Requirements for that race.
 
    ii.         Pilot Requirements.

        a)     General

Any flight simulator pilot is eligible to fly in the race. A pilot may fly for whichever forum they like, but may fly for only one forum during the race.

        b)     Leg eligibility.

A pilot may claim the baton when it is released or transferred by another pilot. However, no pilot may advance the baton in consecutive legs.
 
    iii.         Aircraft Requirements.

        a)     General.

Aircraft must meet all of the following requirements to be eligible for use in the race.

They must be either:
In addition at least 10 real-life flying examples of the model, type, and specific version of the simulated aircraft must have been produced and put into service.
 
Finally, the flight simulator model must have been designed for use in FS2002, FS2004 or FSX, and have been openly available to the general public, either as a commercial product or as freeware, at least two weeks before the race.

        b)     Aircraft modifications.

The only modifications you may make to your aircraft are to its avionics, sounds, and textures. Aircraft may not be equipped with non-certified ferrying tanks or engine tweaks.  Single and twin engine prop aircraft available with drop tanks or ferry tanks may not be flown for any leg longer than 800 nm. Autoland capability is prohibited unless it is integrated with the aircraft’s autoflight system and is realistic for the aircraft type being flown. More generally, any special gauges and modifications that produce unrealistic behavior are prohibited.

        c)     Exceptions.

The Executive Committee reserves the right to except aircraft from sections (a) and (b) of this rule.  That is, aircraft ordinarily eligible found to be insufficiently realistic for race purposes may be declared ineligible, and aircraft ordinarily ineligible found to be suitable for the race may be declared eligible.  Aircraft that fall into this category will be posted conspicuously on the Official Website of the Race.

        d)     Appeals and Clarification.

To appeal an aircraft’s eligibility or ineligibility, or for clarification on a specific aircraft’s status, interested parties may contact any member of the Executive Committee.

    iv.         Leg Requirements.

        a)     Definition.

A leg:
        b)     General.

Each leg must begin and end at an airport included in the Flight Simulator 2002, 2004 or FSX database of airports.

        c)     Time limit.
        d)     Distance limit.

There is an absolute distance limit of 700 nautical miles for each leg.  Legs exceeding this limit will be declared invalid.

    v.         Flight Simulator Requirements.

        a)     Eligible Simulators.

Microsoft Flight Simulator X, Flight Simulator 2004, and Flight Simulator 2002 are the only simulators eligible for flight in this race.

        b)     Time Settings.

You must fly in real-time. In other words, your flight simulator clock, when you are flying in your home time zone, must be set to read the same as your desktop clock.

        c)     Weather settings.

You must fly using only the built-in Real-World Weather (aka Jeppesen) feature as the data source. You must enable the following settings:
        d)     Realism Settings.

You must fly with: The following are not allowed:
7.    Baton Procedures.

    i.         Claiming the baton.

The baton may be claimed and relinquished only through each team’s official public forum.  The first pilot to claim the baton after its relinquishment, as measured by the forum software, is awarded possession.
 
The pilot must post in the forum a message in the following format:
    ii.         Relinquishing the baton voluntarily.

Pilots must relinquish the baton upon completing a leg.
 
Upon successfully completing a leg, the baton holder must post a message in the forum in the following format: The other ways in which the baton may be voluntarily relinquished are:
    iii.         Involuntary relinquishment of the baton.

The baton-carrier automatically loses possession of the baton in any of the following circumstances:
 
    iv.         Authentication Procedures.

        a)     Time.

All legs must be authenticated within one hour of their termination.

        b)     Normal Procedure.

Pilots must use the RTW-Duenna flight tracking utility, available from the official race website, to track their flight. The authentication graphic and text produced by this utility are uploaded to the fsrtwrace.com server at the termination of a flight. The pilot will be notified of a successful upload. The pilot authenticates their flight on the team forum by posting either links to the uploaded verification files, or the Duenna graphic and text file to their Team forum.

        c)     Uploading Errors.

If a pilot does not receive notification that their authentication was successfully uploaded, the pilot must post the Duenna graphic and text file to their team's forum.

        d)     Duenna Errors.

In the case of an error in the RTW-Duenna software, pilots may take a screenshot of Flight Simulator's Flight Analysis window upon their arrival. This screenshot must show the entirety of the flight route, to the best capability of the program. Pilots should also make public any other evidence they may have in support of the authenticity of their flight. The Executive Committee will examine all evidence and come to a decision as to whether to certify or invalidate the leg while the team continues to advance its baton around the world.

        e)     Team Events.

For team flights and other special events, pilots must post their authentication to their team's forum and may not rely on the automatic upload feature of the Duenna software.

 
    v.         Failure to authenticate.

Should a leg not be authenticated within the time limit, the leg in question will automatically become void. All progress after the void leg will also become void, any current flights cancelled, and the team will be required to return to the last authenticated arrival airport.  In such a case: The baton carrier has the sole authority to decide whether to wait for authentication or to assume that the previous flight leg will not be authenticated in time and restart.
 
These provisions may be suspended for authentications under review; other remedies may be applied. Normally, a leg will be considered valid if it is not challenged within 24 hours of its completion.

    vi.         Pilot Reports.

Our goal is that at least one half of all completed legs must be accompanied by a Pilot Report that includes a narrative of at least 50 words and at least one screenshot, ideally posted together with other Pilot Reports in a thread separate from the main race thread. The report and screenshot may be crafted by anyone, not only the pilot in charge. (The Kickoff, Team Flights, and Finale are exempt from this rule.)

 
8.    Incomplete Legs.

In the case of premature termination of a leg due to a crash, computer error, or other reason, it may be necessary not to finish a flight or even a leg.

    i.         Restarting the flight.

The baton holder may restart the flight from the departure airport by issuing a suitable post in the team forum.  The leg time continues to be measured from the lead pilot's original "I have the baton" post, except in the case of a pilot restarting due to failure of the previous pilot to authenticate his leg.

    ii.         Transfer to wingman.

The baton holder may transfer the baton to their wingman, as provided for in rule 9.

    iii.         Aborting the leg

The baton holder may abort the leg and relinquish the baton.  This option:
9.    Wingmen.

After a pilot (now the "Lead Pilot") has claimed the baton on the forum, a second pilot eligible to carry the baton may declare, "I am flying Wing".
 
The wingman may choose to restart his flight or abort his flight. In the latter case another pilot may declare, "I am flying Wing" and depart from the original airport.

    i.         Invoking the Wingman Transfer Rule

The lead pilot may, via a post on the official race thread, transfer the baton to the wingman.  In such circumstances:
A team may choose to invoke the Wingman Transfer Rule on a completed leg. In such circumstances, the initial 30-minute delay, plus an additional delay of 15 minutes, is imposed upon the next departing flight.

10.  Team Organization.

    i.         Team communications.

It is expected and encouraged that teams will plan their route, organize aircraft, and help each other.  It is understood that in order to accomplish these goals teams will set up private channels of communication.
 
Each team:
    ii.         Responsibility.

The baton-carrier has the final say on any given flight – its route, aircraft, and all other aspects of the flight – are his/her responsibility.
 
    iii.         Claiming the baton and team orders.

Pilots wishing to fly are responsible for claiming the baton.  Team plans regarding who will carry the baton on a given flight are non-binding.  This said; it is hoped that pilots will act unselfishly and in the best interest of their team and the spirit of the race.

11.  Intentional Foul Play.

This Race is meant to be fun and light-hearted. If there is intentional foul play--and this must be obvious to everyone--then the Team may declare the particular flight "Null and Void" and ask the pilot to refrain from further participation. Foul play might include flying in the absolute wrong direction, or worse; it does not include cases where pilots do something suboptimal but well-intentioned. In such cases appropriate adjustments will be applied to make the victimized nearly whole.

12.  Rules Enforcement and Appeals.

The Executive Committee is responsible for enforcing the race rules. If a race pilot or spectator feels that a rule has been violated, they inform any member of the Executive Committee via e-mail. The Committee will then determine if a violation has indeed taken place. If it is concluded that a rule was violated, the Committee will take appropriate action and issue appropriate NOTAMs.
 
Race participants may appeal any rule or Executive Committee decision.  To do this, they may either contact the Executive Committee directly, via e-mail, or contact a member of any advisory body convened by the Executive Committee, who will then present the request to the Committee.

13.  Race Administration.

The Race is administered and its rules set by an Executive Committee.  This committee has the final authority over all aspects of the race.  They are responsible for setting and interpreting the rules, administering the race, assessing penalties, and handling appeals.  The Executive Committee consists of the following people: From time to time, the Executive Committee may convene special advisory committees to aid them in setting race policy or administering certain parts of the race. The volunteers' efforts are key to the race's success. That being said, these committees exist as advisory bodies. Final responsibility remains with the Executive Committee.
 
Above all, the goal of this race is to have fun. It is our belief that if we all follow the rules, we cannot possibly fail in this respect.

Flight Simulator Around-The-World Race Official Website - Contact Matt Smith with any questions.