Rules Clarifications and Corrections

Official Race NOTAMs will be posted here
Only the Race Management Group will be able to post official NOTAMs

Moderator: Executive Committee

Locked
User avatar
srgalahad
Posts: 75
Joined: Sun Jan 13, 2013 9:59 pm
Race Team: Sim-Outhouse
Location: CYYC or MMSD

Rules Clarifications and Corrections

Post by srgalahad » Mon Feb 11, 2013 5:33 pm

2013 Special Rules
Rule 3. Routing

The closed airport at Woody Island is identified as Z24D. This is the ICAO identifier in FS9. The correct ICAO identifier for FSX is VH84

UPDATE: The Official Rules have been clarified and reposted at the Official FSRTWR Web Site.
Rob Ibey, Executive Committee

User avatar
Mike.MacKuen
Posts: 115
Joined: Mon Jan 21, 2013 3:07 am
Race Team: Avsim

Re: Rules Clarifications and Corrections

Post by Mike.MacKuen » Mon Feb 11, 2013 10:35 pm

2013 Special Rules. Rule 9. Special Aircraft Legs and Team Flights.

Scheduling Team Flights. Do either Three Motors or Three Tails during the first 24 hours and do the other after the first 24 hours have passed. You can do Three Wings and Three Jets at any time. No pair of Team Flights may be conducted back-to-back.

Just a clarification to be sure that the flight planning teams have these requirements under control.
Mike MacKuen, Executive Committee

User avatar
Mike.MacKuen
Posts: 115
Joined: Mon Jan 21, 2013 3:07 am
Race Team: Avsim

Re: Rules Clarifications and Corrections

Post by Mike.MacKuen » Mon Feb 11, 2013 10:43 pm

2013 Special Rules FAQ. Rule 6. Measuring the distance between airports.

Making Precise Measurements when necessary. From Special Rules FAQ. Rule 6.

"Note that the MSFS flight planner will give different distances between airports – distances that vary by the placement of the aircraft at the airport and the current runway. When the differences matter, then follow this procedure. Using the MSFS Flight Planner, plot a flight plan that includes the relevant airports as intermediate points. Then display and/or print the Navlog – which will show the distance between the airports. For example, you want the distance between airports A and B. Generate an MSFS flightplan from X-A-B-Z, where X and Z are the departure and destination airports. The navigation log (Navlog) will give the intermediate waypoint distances, including that between airports A and B."

If you have a close call when measuring the distance between airports, follow this awkward procedure which has been in place for a couple of years. No matter the runways selected, this procedure gives the same distance between the airports of interest, here A and B. (It is not enough to go to one airport and do a flightplan – the distance will vary by the runway selection.) When the distance differs by simulator (FS9 or FSX), and it will sometimes, the team should choose the simulator that they wish to use for the flight to produce the precise measurement.

While we have an exact measurement tool, it is likely to come into play only rarely. (It may matter in some specific instances.) Our experience is that if your regular flight planning tool gives you a margin of 5-10nm, then you probably don't need to double check your distances. But please understand that there is a crisp precise standard here for close cases.

If a case arises in which a team's measurement causes a problem, then we expect that any punitive penalty would be minimal. (The penalty might include a compensatory component that could be either quite small or it could be truly significant – depending on how critical was the distance in legalizing a flight path.)
Mike MacKuen, Executive Committee

Locked