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.

2009 RTW Race Information:

Official Starting Time: 2:30 PM US Eastern Time (1930Z) Saturday, February 21, 2009 for the Optional Start Event.
The Race portion will begin at 5:00 PM US Eastern Time (2200Z) Saturday, Feb 21, 2009.
Special Rules and Routing Release Time: NOW OFFICIALLY RELEASED.


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

  1. Starting Time

    The race will begin with a special kickoff event at 1930Z (1430EST, 0630L) at Essendon Airport, Melbourne, Victoria, Australia (YMEN).

    The Route – 75th Anniversary of the MacRobertson Race:

    Following the special start outlined in Rule 2 below, the scored portion of this year’s race will begin and end at Essendon Airport, Melbourne, Victoria, Australia (YMEN). 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). Please note the special Finish requirements listed in Rule 4 below.

  2. Special Optional Start for the 2009 Race – Tasmanian Wildlife Rescue.

    Overview.

    The 2009 race will begin at 1930Z with a special event on the island of Tasmania. Eight endangered animals per team may be collected from various locations in Tasmania and brought to Melbourne's Essendon Airport, for a bonus of 1/2 hour per animal, or 4 hours maximum.  Teams are not required to participate in this event, however they may not begin their around-the-world route until 2200Z.

    Wildlife Rescue.

    While gathering for the 2009 Round the World Race, the pilots were ‘volunteered’ by the race committee to assist the Wildlife Preservation Society of Australia in the rescue of several endangered animals from Tasmania. Most of the pilots will be pre-staged at Launceston Airport (YMLT). From that location, flights must be made to eight (8) specific airports on the island of Tasmania or nearby islands to pick up the animals, and then return the animals to Launceston for zoological screening before transporting the animals from Launceston to Melbourne's Essendon.

    Aircraft and Flight Restrictions.

    All pilots will fly small General Aviation aircraft (see the General Aviation Piston Aircraft list below). In addition, pilots may use the Cessna 208/Caravan (Default or Wilco/Feel There). Finally, each team has two specially-fitted Beech King Airs (Default KA350, Aeroworx B200, or AFG B300) available at Launceston (YMLT) at the start of the event.

    Due to size and weight requirements, the aircraft which carry the animals must have a minimum of four seats for the collection flights. (Imagine that they must carry a passenger/handler for the flight. Further, each pickup will include a pair of the animals. Hence, four seats.) Once the animals have been brought to Launceston (YMLT) they may be consolidated into larger aircraft for transport to Essendon (YMEN). Teams may fly backup aircraft as insurance in case of problems.

    Flight Operations.

    On February 21, 2009, flight operations commence at 1930Z with the post of an official thread by the Race Executive Committee on the team forums. Immediately the team pilots may post and depart Launceston to pick up the animals.

    Pilots fly directly from YMLT to the designated airfield. There they will execute a full stop landing to pick up a pair of animals (posting an authenticated baton release) and return the animals directly to YMLT for scientific screening and documentation. This accomplished, the team must then transfer the collected animals to Essendon and Melbourne's zoological center.

    The final transfers may be done in one or more flights. The team may decide to wait until all animal pairs have been collected and then put one of each kind in a King Air and fly the set to YMEN. (Doing so, they may also put the second of each pair into the second King Air and fly the second set to Melbourne as backup.) Alternatively, the team may send the animals one at a time (or in other combinations) in eligible small GA aircraft, keeping in mind that the aircraft must have enough seats for the pilot, a handler and one seat per animal on board.

    Pilots should authenticate each completed flight with the Duenna textfile (but not the jpg) posted on the team forum. Pilots should not use the Duenna's flight tracking feature here. Teams may not begin the circumnavigation portion of the race until the official post initiating it is made at 2200Z.

    Specific Flight Routes.

    From Launceston Airport (YMLT) to collect animals:

    From Launceston Airport (YMLT) to Essendon Airport (YMEN):

    Bonus Awards.

    Each Team receives a bonus of 30 minutes for each distinct animal type that it brings to Essendon (YMEN). The maximum is 4 hours credit.

  3. Race Start from Essendon (YMEN)

    On February 21, 2009, flight operations commence at 2200Z (Local Time in Australia: 0900 Sunday) with the post of an official thread by the Race Executive Committee on each of the teams' forums.

  4. Required Finish for the 2009 Race – MacRobertson 75th Anniversary Salute

    The MacRobertson Race from London to Melbourne in October 1934 is one of the most astonishing accomplishments in aviation history.  In commemoration of this, the final leg of the race must be flown from an airport used in the original race direct to Essendon (YMEN) without stops.

    Routes.

    (Team members are invited to participate in a celebratory flight to return the animals from YMEN to YMLT on Saturday, Feb 28 beginning at 1930Z. Team members are encouraged to fly with other teams for this celebration.)

  5. Routing.

    After leaving YMEN, teams must fulfill several geographic requirements.

    Teams must make a full-stop landing within the following geographical entities:

    Additionally Teams must land at one of the following MacRobertson Race Airports:

    Teams must make at least two (2) full-stop landings at least 500nm apart for each of these categories:

    For 2009, normal legs are limited to 700nm.

  6. Corridors and Air Bridges

    Air Bridges

    Due to the reduction in the maximum allowable leg distance to 700nm, a flight around the world is no longer possible without a special consideration. These exception airport pairs are optional and may be used should a team choose that route. These airport pairs must be flown as listed - in either direction. No landings at alternate airports are allowed. Normal race eligible aircraft must be used: any special corridor aircraft may not be used on these airport pairs. There is a time limit for each pair; exceeding that time limit will result in the same 3 x 1 time penalty as a normal race leg.

    Corridors.

    Corridors allow the use of alternate paths across the oceans, and avoid having only one "best and fastest" workable route around the world. Teams may use any of the corridors listed below. Full stop landings and an exchange of the baton must be made at each airport in the corridor. The stops must be made in the order listed, or reverse order. Additionally, up to three optional stops may be made in a corridor - provided the airport for that stop is within 300nm of a listed corridor airport.

    Corridor

    Route

    Total Mileage

    Leg Distances

    PAC-N

    PAJN-PHOG-PLCH-NSFA

    4,863

    2,439-1,136-1,288

    PAC-S

    SAZS-SCIP-NTTO-NCRG

    4,959

    2,056-1,824-1,080

    ATL-S

    GFLL-FHAW-SBNT-SBBR

    3,201

    998-1,248-955

    ATL-N

    LXGB-LPAZ-CYYT-CYOW

    3,278

    955-1,370-953

    Corridor Aircraft.

    Subsonic jet aircraft may be used on any corridor leg longer than 1,200 nm. Legs less than 1,200 nm must be flown in a normal race eligible aircraft. For corridor flights of 1,000nm or longer, pilots must fly an aircraft with a takeoff weight of 30,000 pounds or more, and not in excess of the maximum gross weight.

  7. Wildcard.

    Each team has one wildcard flight, with a maximum distance of 1,650 nm. There is no time limit on this flight. This flight must be in a normal race eligible aircraft. The wildcard flight may not depart before 1900Z, Sunday, February 22.

  8. Jet Continent.

    Teams may make flights in subsonic jet aircraft over the continent of South America for a maximum cumulative distance of 3,500 nm. For these flights, the takeoff and landing airport must be on the main landmass of South America. The 2 hour time penalty and 700nm limits of normal legs apply. Jet aircraft may not be used for the SBBR-SBNT corridor flight.

  9. Special Aircraft Requirement for the 2008 Race.

    Classics.

    The default aircraft must be flown for the minimum mileage listed:

    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 or Kellet Autogyros are.

  10. Team Flight Bonus Opportunities.

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

    Team Flights available for the 2009 Race are as follows:

    In a team flight, pilots choose one of the aircraft listed for that flight and accompany the baton carrier. Their validated leg earns a bonus for their team.

    Each Team Flight requires a baton pilot and participating pilots. The potential maximum bonus of three (3) hours for a single Team Flight requires a baton pilot and six additional pilots. These flights can take place at any time and in any location during the race following the conclusion of the starting event. However, Team Flights may not be consecutive. There must be at least one normal leg between two team flights. Additional pilots above the minimum, to provide protection in the event of crashes or computer failure, are optional. Bonus - Each participating pilot, not counting the baton carrier, who completes and validates a successful flight will earn a 30-minute bonus for the team. A maximum total of six (6) hours bonus can be earned from all Team Flights combined, of which no more than three (3) hours bonus 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.

    Aircraft.

    The baton pilot and all participating pilots must fly aircraft of a specified category, as listed above. The participating pilots do not have to fly the same aircraft as the baton holder.

    Airports.

    The baton pilot and all participating pilots must takeoff from and land at the same airports.

    Timing.

    Participating pilots may not take off until after the baton pilot has claimed the baton and taken off. All participating pilot flights must be completed no more than 30 minutes after the baton pilot's "Baton is free" post. Completed means landing and post flight successfully completed on the forum. Participating pilots may land before the baton pilot. The team may continue to advance the baton on the next leg while participating pilots are landing and completing their validations.

    Post.

    All participating pilots must make following posts on the official forum thread. After the baton pilot has claimed the baton, participating pilots must post, "I am taking off from _____ in the ____ aircraft participating in the Team Flight", "I have landed at ____, completing a Team Flight." All participating pilot legs must then post a normal authentication within an hour of the landing post. (In this case, a Duenna authentication needs only the textfile, not the picture.) The first six pilots who validate earn the bonus. Finally, after the event and authentications are completed, the baton pilot or a substitute must post a "Team Flight Summary" indicating the number of bonus hours earned in this event and the cumulative bonus hours in all Team Flights to date.

    Special Aircraft Requirement.

    Team Flights may be used to fulfill a Special Aircraft Requirement flight, using those special rules. (Be sure that you meet both distance requirements, which are not identical.)

    Aircraft Modifications

    Classic era aircraft must be flown in default form and modern aircraft may have alternate panels. In some cases, substitutions are allowed. See the Aircraft Upgrades and Substitutions below. FS9 classic aircraft flying in FSX are acceptable.

  11. Special Challenge for 2009.

    To mark the 75th Anniversary of the 1934 MacRobertson Race, teams may optionally choose to fly no more than two of the following segments of that race in aircraft taken from the fleet of 1934 Race Aircraft. Each segment has a specific bonus reward for completion and can be flown in either direction. Normal rules apply.

    1934 Aircraft:

    To be flown in stock form. No panel or avionic upgrades are allowed.

    Optional Special Challenge Segments (Pick no more than two):

  12. Bonus Airports.

    Optional Bonus Airports – 3 hours' bonus for each Airport Tour completed.

  13. Cabin-Class Aircraft.

    Pilots who wish to fly aircraft distinct from the normal racing types have available “Cabin Class” aircraft with the following provisions:

    The following simulations qualify for this program:

  14. Aircraft Upgrades and Substitutions for the Kickoff, Finale, Special Aircraft Requirement and Team Flights.

    The "Historic Classics" are to be flown in default form. The Modern Aircraft may be upgraded, and in some cases substituted for, as indicated below.

    Historic Classics (which must be flown in pure default form):

    Modern Aircraft (for which avionics may be upgraded):

    Allowable alternate aircraft for Kickoff, Special Aircraft Requirement, and Team Flights are:

    General Aviation Piston Aircraft (available for Kickoff and GA Team Flight):

  15. Bonus Bank.

    To speed up the race, this year 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 Team Flights, Special Challenges and Bonus Airports. Additionally, teams gain handicap hours for flying official Cabin Class legs of more than 500nm (those 45 minute increments serve as bonus hours).

    Teams must keep track of their bonus/handicap hours in a special thread on their forum to be entitled “Bonus Bank.” This thread needs to be open to the race officials and to all the participating teams. After a team has earned bonus hours or a Cabin Class handicap, it is the team’s responsibility to add a post to their thread that indicates (a) the bonus/handicap time earned and (b) the current net balance of hours “in the bank”. The team must complete this accounting within one hour of earning the bonus. There is no penalty for failure to post except that the bonus will be forfeit. (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.

    Once teams have earned Bonus Bank hours, they may apply that time against any penalties that the team incurs. (The team may not go in deficit!)


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.

        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 either the built-in Real-World Weather feature or a third-party weather program of at least equal realism. If you are using the built-in Real-World Weather feature:
        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.