2018-A League Rules and Guidelines

Written By: Brodie Hannah

Last Updated: 2/5/2018 (Changes in RED)



    1.1 Mission Statement
    2.1 League Expectations
    2.2 Attendance Requirements
    2.3 Flaming
    2.4 Cutting The Track
    2.5 Reckless Driving
    2.6 Intentional Contact
    2.7 Intentional Cautions / Spins
    2.8 Unintentional Contact
    2.9 Cheating
    3.1 Yellow Line Rule
    3.2 Self-Spin Rule
    3.3 Caused Caution Rule
    3.4 Mandatory Practice
    3.5 Racing Incidents
    3.6 Lucky Dog
    3.7 Pacing and Pace Laps
    3.8 Session Restarts
    3.9 Cautions
    3.10 Pitting
    3.11 Ending Under Caution
    3.12 Starts and Restarts
    3.13 Lapped / Damaged Cars
    3.14 Bump-Drafting
    3.15 Warping / Bad Connection
    3.16 Server Issues
    3.17 Provisionals
    3.18 Rookie Stripes
    3.19 Eligibility Requirements
    3.20 League Tryouts
    3.21 Dropped Races
    3.22 Race Server Capacity
    4.1 Car Number Assignment
    4.2 Car Number Abandonment
    4.3 Custom Paint Schemes
    5.1 In-Game Communication
    5.2 Hearing-Impaired Communication
    5.3 Teamspeak
    5.4 Usage of Text Chat / Voice Chat
    5.5 Streaming and Recording
    6.1 Prize Money & Earnings
    6.2 Penalties and Forfeiture
    6.3 End of Season Payout
    7.1 File A Protest
    7.2 Penalty Review
    7.3 Determination of Penalties
    7.4 Mid-Race Penalties
    7.5 Driver Ejection
    7.6 Penalty Discussion
    7.7 Post-Race Penalties
    7.8 Appeals
    7.9 Assurance of Fairness





Section 1

Our Mission


1.1 Mission Statement - Full Throttle Sim Racing was created to provide a fun, exciting and entertaining environment while promoting clean, courteous and professional conduct on and off the track in each sanctioned event.




Section 2

Driver Conduct


2.1 League Expectations – All members of FTSR are expected to conduct themselves in a professional manner while in any and all FTSR-sanctioned sessions both on and off the track. There shall be no reckless driving, driving backwards, intentional wrecking of yourself or another driver, dangerous driving or any other actions that negatively impact the experience of other drivers. Drivers should also refrain from profanity, racial slurs, negative comments about others and any other actions or words that may negatively affect others. This applies to all practice sessions, race events and all other times while in a FTSR-sanctioned server.


2.2 Attendance Requirements - Members are expected to attend races and compete regularly. Drivers who miss 3 consecutive races in a single series without prior notification may be removed from the series. This is done to keep our rosters current and to allow other drivers opportunities to participate in the event of a full series roster. 


2.3 Flaming - Flaming is defined as a hostile and/or insulting interaction between persons over the internet, often involving the use of profanity. Flaming other members of FTSR is not permitted at any time. Violation of this rule can lead to varying penalties, suspensions, and/or expulsion. If you have a disagreement with another driver, we suggest that you take care of this in a professional manner and in a private setting. If you have an issue with a penalty of call by a league administrator or race official, please contact them in private to discuss this.


2.4 Cutting the Track - If you cut corners on on the track with the intent of gaining a competitive edge over the competition, you will be penalized. It is suggested that you keep 2 tires on the racing surface at all times. If you put more than 2 tires off of the racing surface with the intent of gaining a competitive edge, you will be penalized 1 lap for each infraction. This does NOT include aprons on oval tracks, although the yellow line rule is in effect for super speedway tracks.


2.5 Reckless Driving - If you are in violation of a rule or have put your car in a situation that could easily be avoided and cause an accident, you will be penalized for reckless driving. Reckless driving is defined as avoidable actions taken by a driver that puts another car in danger or risks causing a caution. This will be a judgment call among race officials. Penalties for this will vary.


2.6 Intentional Contact - Intentional contact will NOT be tolerated. The race administrators will determine the severity of the penalty based on previous actions, intention and result of the actions taken. Drivers must not take it upon themselves to show displeasure with other drivers on the track. If a driver causes issues on the track, it is best to let league officials deal with the issue rather than to intervene and risk receiving a penalty as well.


2.7 Intentional Cautions / Spins - Drivers who intentionally cause a caution or wreck another driver to improve their position or the position of another driver will be removed from the race server and suspended no less than 1 race.


2.8 Unintentional Contact - This is any incident where a driver makes contact with another driver accidentally. This is the result of hard racing and will not be penalized if it is clearly unintentional and is not considered reckless driving.


2.9 Cheating - FTSR has a zero-tolerance policy regarding cheating. Cheating is defined as anything that a driver does to gain a competitive edge that is not permitted by the rules. Cheating will not be a problem in this league. The iRacing simulation has cheat detection programs designed to detect and prevent cheating. If you are cheating, don’t even bother joining the server as you will be immediately kicked. Cheating also includes using track glitches to gain a competitive edge over other drivers. Cheating is strictly prohibited and will result in a permanent ban from the league.





Section 3

Rules and Procedures


3.1 Yellow Line Rule - This league abides by the yellow line rule at Daytona and Talladega for every series. Any driver that improves his/her position while under the yellow line will be penalized unless you relinquish the position(s) to the driver(s) passed within a reasonable time frame. If you pass below the yellow line and do not relinquish the position(s), you will be penalized 1 lap at the end of the event. If you were forced below the yellow line, then you will not be penalized and may hold your position. Drivers need to use their very best judgment here. If you have passed below the yellow line and there is a chance you were at fault, it would be wise to give the position back and try again later rather than to take that chance of receiving a penalty.


3.2 Self-Spin Rule - Self spins and one car incidents that cause cautions slow the pace of the race and take away from the fun and excitement of racing. Drivers that cause cautions with one car incidents will be given 1 warning. If a driver spins the car on his own or otherwise brings out a caution on his own after being given the warning, the driver will be asked to park the car in the interest of competition, to protect other drivers, and to prevent unwanted and unneeded cautions. Drivers who bring out the caution in this manner must alert race control and take responsibility for their actions. If a driver spins and a caution comes out, but the driver is unsure if they are the cause of the caution, they should alert race control of this so that the incident can be reviewed after the race. If the driver is found to be at fault after the race and it leads to a second self-spin for the race, race results will be adjusted accordingly and the driver will be disqualified. Any attempt to mislead or misinform race control or hide an incident will lead to penalties.


3.3 Caused Caution Rule – If a driver is determined to have caused a total of 3 cautions at any time during an event, that driver will be asked to park the car in the interest of competition, to protect other drivers, and to prevent unwanted and unneeded cautions. This can include self spins, reckless driving and unintentional contact. Drivers who are at fault in an incident that causes a caution must alert race control and take responsibility for their actions. If a caution is caused and the driver is unsure if they are to blame, they should alert race control of this so that the incident can be reviewed after the race. If the driver is found to be at fault after the race and it leads to a third caused-caution for the race, race results will be adjusted accordingly and the driver will be disqualified. Any attempt to mislead or misinform race control or hide an incident will lead to penalties.


3.4 Mandatory Practice - All drivers are required to be in the server on race night by 8:45pm EST and complete at least 1 lap in practice prior to qualifying to be allowed to start the event. Drivers who enter the server after 8:45pm EST and/or fail to complete at least one lap in practice will be removed from the server prior to qualifying. We also understand that there may be rare occasions where you may not be able to enter the server by this deadline due to real life circumstances. If you notify an administrator prior to practice that you will not be able to make the cutoff time, you will be allowed to start the race from the rear.

Practice is used to learn tracks, observe changes to the track surface due to heat and rubber, learn the habits and behaviors of other drivers you will be racing with, test equipment, ensure hardware and software are working properly and also to prepare yourself for the upcoming race. This is done to protect drivers from unprepared drivers and to reduce the chance of unprepared drivers causing issues during a race. 


3.5 Racing Incidents – In racing, there will be times where the actions of both drivers are to blame for contact or determined to be the cause of an accident. These are often referred to as "racing deals" or "just racing". We understand that sometimes it is impossible to blame one single driver for an accident. In these instances, both rivers must acknowledge that this was the case. If both drivers are in agreement, we will not assign a caused caution to either party and simply ask that you understand what caused the issue, correct the issue and move on, as will we. After all, its racing.


3.6 Lucky Dog Rule – The first car one or more laps down when the caution comes out AND not involved in the incident that caused the caution will receive the Lucky Dog and will regain 1 lap back. A driver that receives the “Lucky Dog” may ONLY pass the field and gain their lap back when instructed by the on-screen prompt and/or spotter. Drivers receiving the lucky dog may pass on the RIGHT SIDE of the field and must do so CAREFULLY and SLOWLY. Incidents caused during this process will be reviewed and penalties will be assessed.


3.7 Pacing and Pace Laps - Drivers should take care during the initial pace laps and while under caution. There shall be no excessive swerving. Do not leave the racing surface unless pitting. Drivers are not to make contact with other drivers while pacing. Drivers must pay close attention to their spotters and on-screen prompts while pacing to understand what position they should be in. Drivers should also take care to give space to the right between their car and the wall during caution laps to allow drivers who receive the “Lucky Dog” to pass safely. Drivers who conduct themselves inappropriately during this time may be penalized.


3.8 Session Restarts - in iRacing, there is no way to restart a race once it has started. We cannot stall, delay or restart the current race server. The only way to do a complete restart is to move to another server, which will be avoided at all costs for obvious logistical reasons. Drivers who cause problems before the start of the race will be removed from the server. League officials reserve the right to restart the race if it is determined to be in the best interest of the drivers, the event and the league.


3.9 Cautions – When a caution is activated, drivers should slow at a reasonable, smooth and steady pace to avoid contact with other cars. The leader should look for the pace car and gradually slow behind the pace car. The leader is urged to advise where the pace car is when he is approaching the pace car to alert other drivers. Do not leave the racing surface unless pitting. Drivers are not to make contact with other drivers under caution. Drivers must pay close attention to their spotters while under caution to understand what position they should be in.


3.10 Pitting – Drivers are encouraged to signal either verbally or in chat when pitting and/or exiting. This prevents unwanted accidents, confusion and frustration.

   a. Entering Pit Road - Drivers may enter the pits according to the track specifics.

   b. On Pit Road - While on pit road, drivers must stay to the right-most lane of pit road as much as possible. This allows drivers the opportunity to view their pit boxes. Drivers must not make contact when pitting. Drivers should also avoid driving through others pit boxes when entering or exiting their pit stall, as this hampers the drivers' ability to see their pit sign and stall. Drivers who fail to conduct themselves in this manner while on pit road may receive a penalty.

   c. Exiting Pit Road - Drivers must reenter the racing surface in a safe manner and without obstructing faster cars. Drivers getting up to speed must yield to faster cars on track.Drivers are encouraged to reenter the track on the backstretch of a track, as it is the safest place to do so.

Drivers who impede faster cars or cause incidents while entering or exiting the pits are subject to penalties.


3.11 Ending Under Caution – If a caution comes out and the race cannot be restarted, the race will end under caution. Unfortunately, iRacing does not currently permit Green-White-Checkered finishes.


3.12 Starts and Restarts – Drivers will start and restart the race based on the simulation. The leader of the race will accelerate when the green light appears on the screen or the starter indicates the start or restart of the race. Drivers must NOT start before this signal is given. Drivers are to remain in their lane and maintain their position until they cross the start-finish line. Any driver who breaks the plane of the rear of a car he is starting directly behind prior to the start/finish line must relinquish the position completely before the completion of the lap or face penalties. Any driver who applies brakes unnecessarily, fails to maintain constant pace speed or accelerates prior to the start or restart in an attempt to gain an advantage over his competition will be penalized. Drivers should be respectful of other drivers on starts and restarts.


3.13 Lapped / Damaged Cars - Lapped cars and damaged cars should yield to lead lap cars if off the pace. Every car on the track has the same right to race with any car for a position, although if you choose to do so while off the pace or in a way that endangers other cars, you may be penalized. It would be wise and appreciated by all if lapped cars yield the preferred line to the leaders. Damaged cars and slow cars are required to yield to faster cars in a safe and timely manner.


3.14 Bump-Drafting - Bump-Drafting is allowed, although strongly discouraged if you are uncomfortable with the practice. Excessive bump-drafting is considered reckless driving and the driver may be penalized. There is no rule preventing push-drafting. It is our stance that a rule should not be created to prevent a car from performing an action that is the result of the design of the car itself.


3.15 Warping / Bad Connection - If a car is observed "warping" or moving erratically due to a poor connection or connection issue, the driver will be notified of the issue. This should be a signal to the driver to avoid close-quarters racing and to yield when available to avoid further issues. If the issues continue, the driver may be asked to move to the rear of the field. If a driver neglects to yield his position, he may be removed from the server to prevent further issues. Any issues that are observed during practice may also lead to administrators asking the driver to start from the rear of the field to prevent further issues and to ride out the issue until it improves. Race administrators will do everything in their power to allow you to race, but we cannot allow drivers with bad connections to cause issues. Drivers are strongly encouraged to use practice sessions to sort out any possible issues. Drivers should also make sure there are no programs running in the background that could cause issues before entering the server.


3.16 Server Issues - In the event of a server crash or malfunction, we will follow the following guidelines.

   a. If 50% or more of the race is completed by the leader, the race will be deemed official and we will revert back to the last lap completed. Points will be awarded as if the race reached its complete distance.

   b. If less than 50% is complete, the race will not count and the race may or may not be rescheduled. No driver who was previously out of the race will not be allowed to reenter a rescheduled event.


3.17 Provisionals - The league does not utilize provisionals at this time. Only drivers who race will receive points based on their finishing position. This is done in the interest of simplicity and ease of league management.


3.18 Rookie Stripes - All new drivers in FTSR will be marked with an asterisk (*) preceding their name. This is to help league officials identify new drivers and to help other drivers be cautious and aware of new drivers to the league. In most cases, this mark will be removed after a few races. In some cases, the asterisk will remain if league officials deem that the driver will need more track time before before the mark can be removed. The mark may also be reapplied if a driver is deemed to still be of some concern after being approved earlier or has caused incidents in previous races. This system helps drivers notice drivers who are new or unknown. 


3.19 Eligibility Requirement - When applying for a series, the drivers must meet the eligibility requirements for that series. Eligibility requirements look at the drivers iRating and License Class. Each series has a different set of eligibility requirements that must be met in order to compete in that series. Eligibility requirements are observed at the beginning of a season and whenever a new driver applies to a series during a season. Once it is determined that the driver meets eligibility requirements, the driver will be contacted and invited to participate in a league tryout session with league administrators.


3.20 League Tryouts - Drivers who meet eligibility requirements and apply for the league are required to participate in a league tryout session with at least 2 league admins. Admins will contact you and set up a time to run laps with you and chat with you. This may also be conducted in a practice session with other members or already-scheduled practice sessions. League administrators will monitor performance, attitude, personality, skill-level and other areas before making a determination. Drivers who are approved will be asked to provide an available car number to be used in the series. Drivers attempting to join multiple series will only need one league tryout session. Once approved, drivers are approved for any and all racing series.


3.20 Dropped Races - Each series will allow drivers to drop their 2 lowest finishes of the season when calculating championship points at the end of the season. This will include races missed for the season. Any driver starting after the first race of the season will have his 2 dropped races applied to races previously missed and will not be awarded any additional opportunities. We feel this provides flexibility and eases the requirement for drivers to compete every week throughout a season while still giving drivers who show up each week more opportunities to gain points and improve their lowest finishing position.


3.21 Race Server Capacity - There may be times where a race server becomes full. Entry into a race will always be on a first come, first served basis for approved members. There are no provisional positions for drivers who are higher in the point standings. In the event that the race server becomes full, FTSR will not open a second server or expand the capacity of the server past the number of pit stalls available. We do not feel that expanding the field size of a race is in the best interest of the league or its members. This may be experienced more often at short tracks that have fewer than 43 pit stalls. Drivers are encouraged to join the one hour pre-race practice early to reserve their spot for the race.  





Section 4

Car Numbers and Paint Schemes


4.1 Car Number Assignment – Thanks to the car number prioritization ability of iRacing, we are able to assign car numbers to drivers in the simulation. Car numbers may be reserved or changed by the driver at any time. Car numbers can be reserved or changed by notifying the league administrator or series official through the iRacing messaging system. Drivers should check the members tab of the series iRacing league page to see what numbers are available. Car numbers are allocated on a first come, first served basis. Any driver that does not reserve a car number will be assigned one by the league to prevent drivers who did not reserve a number taking car numbers from drivers who did so. Car numbers reset after a single season (ex. 2017-B, 2017-C, etc.), however, current series drivers will have the opportunity to keep their number from a previous season before it is released and allowed to be used by others. Drivers who have not indicated that they wish to retain their number forfeit their right to the number and the number will be available for use by other members.


4.2 Car Number Abandonment –  Any driver who misses 3 consecutive races in a single series without prior notification will lose rights to their car number for the series and the car number will be available for use by other drivers. This is done to allow drivers who race frequently to select more popular car numbers and to prevent car numbers that are not being used from being unavailable to active drivers. 


4.3 Custom Paint Schemes – Drivers are allowed to run custom paint schemes (paint schemes created outside of the iRacing web-based program) for races.  All custom car paint schemes must be available through Trading Paints. There shall be no vulgarity (nudity, foul language, derogatory comments, racial slurs, drug related content, violent comments or pictures, etc.) on the cars.




Section 5

Media and Communication

5.1 In-Game Communication - The league uses the in-game voice chat as the primary line of communication during the races. League officials will pass information through this line of communication only. All drivers must have proper voice chat hardware (microphone, headphones and/or speakers) and must be able to prove that they can receive messages during the race. Drivers who cannot follow directions will be removed from the server.


5.2 Hearing-Impaired Communication -  Drivers who are hearing impaired may communicate with text chat, but must understand the difficulties that are faced when trying to do so and that a response will not always be able to be given during a race. Hearing impaired drivers are to make sure to understand rules and procedures fully and to pay close attention to other drivers on the track to prevent incidents due to lack of communication during a race. This is a difficult situation for all involved, but we will attempt to work with any driver facing this issue.


5.3 Teamspeak - The league provides a Teamspeak server for its members, however drivers are not required to use Teamspeak during the race. Teamspeak is, however, the only form of communication that broadcast companies use during the race. Drivers are encouraged to use Teamspeak during broadcast races. Only drivers who are in Teamspeak during or after broadcast races will be eligible for interviews. Members may also use Teamspeak at times we do not have a race. This can be used to chat with other members or used while playing other games. The league Teamspeak is free to use by all members of FTSR.


5.4 Usage of Text Chat / Voice Chat - Drivers are to limit excessive chatter and chat messages while in the server to prevent confusion and frustration of other drivers. Driver should not spam the chat with unnecessary messages or talk excessively in the voice chat. This includes sounds, unnecessary messages and any other message found to be disruptive or unproductive to the function of the league. There shall be NO TEXT OR VOICE CHAT DURING QUALIFYING. Drivers who are in violation of this rule will be penalized


5.5 Streaming and Recording - Recording, streaming, transmission or distribution of any communication, actions, video, races, broadcasts or other content of this league without written permission from the league owner is prohibited. Members may also opt out of being recorded by contacting the league in writing requesting omission from broadcasts, recorded chats and other forms of media.




Section 6

Prize Money and Payout


6.1 Prize Money & Earnings - At the beginning of a season, administrators will announce an amount of Championship prize money that will be paid to the winner and other finishing positions in the final championship point standings for each series, as well as any additional awards. This will be combined and will be paid in one lump sum to the driver. Drivers may also earn additional prize money throughout the season for special events, challenges and other accomplishments.


6.2 Penalties and Forfeiture -  Any driver who incurs a penalty during a season is subject to forfeiture of any or all prize money. This will be handled as a "fine" to the driver. In severe cases, penalties could also include a complete forfeiture of Championship prize money. Drivers are to conduct themselves professionally in order to take advantage of these incentives.


6.3 End of Season Payout - Drivers are eligible to collect prize money for a series as long as the following conditions are met:

   a. No Outstanding Penalties - The driver has no outstanding penalties following the conclusion of the final race of the series season.

   b. More than $5 Earned - Unfortunately, drivers who earn less than $5 total will forfeit their prize money. This is due to the minimum set by iRacing for gift certificates.  

Winnings will be paid out at the completion of the season. Officials will announce the final earning totals and distribute iRacing gift certificate codes via the iRacing messaging system at a predetermined time in the announcement. Drivers may donate their earnings to the league. To do so, a driver should notify an official of their intent to do so quickly as to prevent unwanted gift certificates being generated. Drivers may not, however, ask the league to redirect their earnings to another member. If a driver wishes to transfer his earnings, he may do so AFTER codes are distributed by the league.



Section 7

Penalties and Appeals


7.1 File a Protest - Drivers who feel that a driver took actions during a race that are in direct conflict with rules in this rulebook may now file a Driver Protest via the league website. Drivers can do so by visiting the website (www.ftsr.net) and choose "More" on the main menu, then click "File a Protest". This will bring you to a form where you can indicate Series, lap number, car involved and more. These requests are sent directly to league officials for review. These reports can be filed anonymously, but we urge drivers to leave contact information in the event that more information is needed.


7.2 Penalty Review - When a driver protest is received, League Officials attempt to look at every aspect and consider all situations possible before assessing a penalty. Race officials are trained to know what is or is not a penalty. All decisions made by the FTSR administrators and officials are in the interest of fairness, fun, and to provide drivers with the best simulation racing experience possible.


7.3 Determination of Penalties - Penalties are determined by the League Administrators, the League President, League Officials, and Race Officials. Penalties include but are not limited to, warnings, point deductions, race suspensions, league expulsion, lap penalties, and stop-and-go penalties. Most penalties are not predetermined because different situations will require different consequences. Every situation is unique and it would be extremely difficult to cover every instance with one set guideline.


7.4 Mid-Race Penalties - Unfortunately, sometimes there are mid-race judgement calls when penalties are applied. We wish it was black and white, but sometimes you have to make the best decision you can when viewing an incident and even make decisions very quickly. The race administrators will make the best possible mid-race call on which driver they think caused the incident, whether penalties are assessed, and other issues. Officials attempt to look at every aspect and consider all situations before making judgement calls. All mid-race penalties are at the race officials’ discretion and may not be debated during a race.


7.5 Driver Ejections - Officials reserve the right to eject any driver at any time for any reason, including foul language, jumping restarts, reckless driving, and/or other similar activities.


7.6 Penalty Discussion – Drivers may discuss penalties with an administrator AFTER the race if drivers wish, however penalty discussion during the race is not permitted. Drivers may also be asked to meet with race officials after the race to discuss issues during a race.


7.7 Post-Race Penalties - Drivers may also face penalties after a race if it is determined that the driver was in violation of a rule during the last race. The statute of limitations applies whereas a race penalty can only be assessed for the most recent race. The statute of limitations does not apply to appealed penalties or ongoing investigations. 


7.8 File an Appeal – If you feel that you were wrongfully penalized, a driver may file an appeal. Drivers who appeal a penalty must provide evidence to back their claim. League administrators will then review the incident, the penalty and the outcome. If the penalty is overturned or reduced, the driver will be notified and the adjustment will be made immediately. If the penalty stands, the driver will be notified and no adjustment will be made. Appeals are welcome and a great way to ensure that the league and drivers are all operating at optimum levels. Appeals are a great time to review processes and procedures for the league as well.


7.9 Assurance of Fairness – If you feel that race officials have unfairly penalized you and feel there is a conflict of interest or evidence of favoritism or unfairness when or how penalties are being applied and your penalty appeal was denied, you may contact the league administrator via email at This email address is being protected from spambots. You need JavaScript enabled to view it. and explain the issue. We will review the issue and contact you with our findings. Again, we appreciate this opportunity to review policies and procedures at FTSR and welcome your feedback.





Note: FTSR Officials have the right to modify any and all rules in this rulebook and to interpret them in the best interest of the league. FTSR Officials have the right to make calls outside of the rulebook in the best interest of the league at any time. Some series may have special rules associated with them. All rules are subject to change.

© 2017 Full Throttle Sim Racing
All Rights Reserved.