CMS iRTES Sporting Regulations — 2026 Winter Season 7

Version: 3.1   •   Date: October 25, 2026   •   CMSRacing.com

1. Changes from Last Version

Version 3.1 adds a public-facing, high-level race weather outlook with in-simulator start times. All sporting provisions from version 3.0 remain in effect, including the following Season 7 updates:

• Renamed the registration section to 2026 Winter Season 7 Timeline and opened registration to both returning and new teams through the Season 7 start, subject to available class capacity and CMS approval.
• Replaced the Season 6 three-round calendar with the new six-round Season 7 championship schedule, plus the November 15 preseason Shakedown at Okayama.
• Updated the Series Overview from the compact Season 6 format to the expanded Season 7 championship running December 2026 through April 2027.
• Added the standardized Season 7 practice rhythm: FP1 on the Sunday before each feature, followed by FP2 and a Sprint on the Saturday before the feature race.
• Updated season-specific references throughout the regulations from Season 6 to Season 7 while retaining the existing sporting framework unless otherwise noted.
• Corrected the Iron Man award language to reflect that it is a car/team mileage award within each class, with drivers becoming eligible if they drive the winning car in at least two championship rounds.

2. Series Overview

Welcome to Season 7 of the Champion Motorsports iRacing Team Endurance Series (iRTES). iRTES is loosely modeled after the spirit of major real-world endurance championships and combines GTP and GT3 machinery in multi-driver team competition.

Season 7 expands iRTES to six points-paying championship rounds running from December 2026 through April 2027, preceded by a non-points preseason Shakedown at Okayama. Each championship round will feature teams of two to three drivers, solo qualifying, active Race Control, multiclass traffic, dynamic weather and track conditions, and race lengths ranging from 3 hours 20 minutes to 5 hours.

The grid remains limited to 30 total entries: 12 GTP and 18 GT3. The goal remains serious endurance racing in the long-standing CMS spirit of competitive, respectful community racing.

3. 2026 Winter Season 7 Timeline

Season 7 will be limited to a total racing grid of 30 entries — 18 GT3 and 12 GTP. Once either class reaches capacity, approved additional entries may be placed on a reserve list.

• Now through Season Start: Registration open to returning teams, CMS community teams, and new/public teams.
• Rolling Approval: CMS Admins will review entries as they are submitted. Returning teams are encouraged to reserve their places early, but registration is open to both returning and new organizations during this period.
• December 6, 2026: Season 7 championship begins at Daytona. Registration closes at season start unless CMS Admins elect to fill an available vacancy or reserve position.

All entries are subject to approval by CMS Admins and may be refused if deemed appropriate and in the best interest of the community and the series.

4. Entry Fees and Charters

The Season 7 entry fee remains $15 USD per car, payable to CMS via PayPal at donate@cmsracing.com. Upon approval of a grid entry, the team will be cleared to make payment. If payment is not made within a reasonable time, the position may be passed to the next eligible team. Special payment arrangements may be made with CMS Admins when needed.

Teams holding a permanent iRTES charter remain protected on the grid so long as they remain in good standing with the CMS community. The existing charter structure remains a one-time $100 USD per car commitment in addition to the normal seasonal entry fee.

5. Eligible Cars

GTP / LMDh Class

All currently available non-legacy iRacing cars.

GT3 Class

All currently available non-legacy iRacing cars.

Note: If multiple versions of a car exist from the same manufacturer, the most recently released version will be used.

Additional Information

All participants must be familiar with the CMS General Competition Rules & Regulations.

6. Series Schedule

Season 7 begins with a non-points Shakedown at Okayama before six championship rounds. The standard championship-weekend rhythm uses FP1 on the Sunday before the feature, followed by FP2 and the Sprint on Saturday, then the endurance feature on Sunday.

6A. Season 7 Race Weather Outlook

7. Server Schedule

• Practice: 75 minutes — 1530 GMT
• Mandatory Drivers Meeting: 1630 GMT
• Solo Qualifying: 15 minutes / 3 laps — 1645 GMT
• Race: 3 hours 20 minutes up to 5 hours — 1700 GMT

Any event-specific change to the standard server schedule will be communicated in advance in the official race briefing.

8. Official Practice Sessions

Each championship round will have designated official practice sessions. Unless otherwise announced, FP1 will take place on the Sunday before the feature race, and FP2 will take place on the Saturday immediately before the feature. The Saturday program will also include the corresponding Sprint Race.

All members are strongly encouraged to attend official practice whenever possible to gain track time with the group, verify paints and driver registrations, identify technical issues, and rehearse multiclass traffic procedures before race day. Sessions will be announced on the CMS Discord server and in race briefings.

9. Championship Points

GTP & GT3 Classes — Positions 1st–10th

Positions 11th–20th

Positions 21st–30th

10. Tie Breakers

In the event of a tie at the conclusion of the series, a countback of class finishing positions will be used. The first tiebreaker is the number of first-place finishes; if a tie remains, second-place finishes will be compared, followed by third-place finishes, and so on until the tie is broken.

11. Server Settings

• Dynamic Weather, with a general forecast provided in each race briefing for planning purposes.
• Dynamic Track.
• 1 Fast Repair.

Season 7 is intended to feature meaningful weather variety without turning weather into randomness. Event-specific conditions will be published with the race briefing.

12. Tire and Fuel Limits

The series may use race-specific tire and fuel limitations. Teams may be allocated a limited number of tire sets, and/or fuel capacity may be configured below 100%. Any such limits will be communicated in advance in the pre-race briefing.

No additional Balance of Performance adjustment, such as weight or power changes, will be used unless CMS Admins determine an adjustment is necessary after observing a significant impact on event quality.

13. Starts

All events will use a rolling start. The GTP pole sitter will hold the GTP field at the track's posted pacing speed until the pole sitter begins acceleration in the designated acceleration zone or the green lights/flag are displayed, whichever occurs first.

The GT3 pole sitter will hold the GT3 field at the track's posted pacing speed until the pole sitter begins acceleration in the designated acceleration zone or the green lights/flag are displayed, whichever occurs first.

All drivers must maintain position until the start. Laying back, gaming the start, jumping the start, tire warming, and weaving are prohibited. Dragging the brakes is permitted. The acceleration zone and point at which passing may commence will be defined in each event briefing.

14. Orange Zone

Each race will use an Orange Zone. Orange Zones will be posted in the specific event thread on Discord. All drivers are expected to exercise heightened caution to reduce the risk of early, high-consequence incidents.

15. Safety Cars and Code 60

Instead of a traditional full-course yellow, iRTES uses a Code 60 procedure to slow the field, neutralize the course, and allow Race Control to manage unsafe conditions.

All cars capable of proceeding must remain moving throughout a Code 60. Unless Race Control specifically directs otherwise, there will be no stopping or on-track queuing.

1. Initial Code 60 Call

When a Code 60 is called, Race Control will announce over the radio: “Attention drivers, Code 60 in 5-4-3-2-1.”

The countdown will be given over the radio only. As soon as the countdown begins, all drivers must immediately lift off the accelerator and begin slowing in a safe and controlled manner. By the end of the five-second countdown, every car must be traveling at the designated Code 60 speed with the pit speed limiter engaged.

Unless Race Control announces otherwise, the designated Code 60 speed will be the pit-lane speed configured for that track.

2. Pit Lane

The pits will remain open throughout the Code 60 unless an incident blocks or interferes with pit entry or pit exit. Any pit-lane closure will be announced by Race Control.

Teams may elect to pit during a Code 60 but may lose positions as a result of taking service. Cars rejoining from pit lane must yield to cars already on track and may merge only when a safe gap is available.

3. Passing During Code 60

Except for Race Control-directed field-formation procedures, passing is not permitted for cars remaining on track during a Code 60. Passing a damaged, stationary, or clearly disabled car is permitted only when necessary to proceed safely.

4. Forming the GTP Field

Once Race Control confirms that all cars are safely on the limiter, GTP cars positioned behind the overall GTP leader may be instructed to carefully leave the limiter and move through GT3 traffic ahead of them. Those GTP cars will form behind the overall leader while maintaining their exact GTP order. GTP cars may not pass one another during this process.

The overall GTP leader will serve as the pace car throughout the Code 60 and will maintain the pace directed by Race Control.

5. Forming the GT3 Field

Once the GTP field is organized, Race Control will instruct GT3 cars to safely leave the limiter and catch the rear of the GTP field. The first GT3 car in the restart line must maintain approximately a five-to-seven-second gap behind the final GTP car.

GT3 cars must maintain their existing GT3 order while catching the field and may not pass one another unless specifically directed by Race Control.

6. Return to Green

Once the field is organized, Race Control will return the race to green as the field approaches the defined race-start or acceleration zone. The overall GTP leader controls the GTP restart. The first GT3 car in the restart line controls the GT3 restart while maintaining the prescribed class gap.

No driver may accelerate early, lay back, jump the restart, or begin passing before permitted by the event's start procedure and Race Control instructions.

Additional Code 60 Rules

• Drivers may not serve penalties during a Code 60 period.
• Race Control may announce a sector caution for a slow or damaged car. Drivers must respond appropriately and follow all Race Control instructions.
• Teams found speeding, passing improperly, or failing to follow Race Control instructions may be subject to post-race review.

16. Request to Tow in iRTES

If a car is involved in an accident and cannot safely return to the pits in a controlled manner while remaining off the preferred racing line, it may need to tow. In iRTES, towing is permitted only when approved by Race Control.

A team that cannot safely resume rolling must contact Race Control by voice and/or text and request permission to tow. Once approved, the team may tow or follow any additional instructions issued by Race Control.

Automatic iRacing Tow Exception: The only exception is an automatic iRacing tow caused by a computer, network, or connection failure. If this occurs, the team must notify Race Control after the race.

17. Race Control & Communications

Race Control instructions, communications, penalties, and the pre-race briefing will be conducted using iRacing voice and text chat through the @RACECONTROL channel. In-race voice communications and text macros should be kept to a minimum. Abusive and/or profane language in iRacing or CMS Discord channels may lead to probation, suspension, or removal from the league.

18. Blue Flags

In accordance with the CMS General Competition Rules, blue flags are advisory. All drivers and teams must understand and comply with CMS rules regarding lapped traffic and multiclass passing. See the CMS General Competition Rules & Regulations.

19. Team Rules

To be eligible to race, a team's drivers must be registered to that team within iRacing. All drivers must be approved members of the iRTES Endurance league on iRacing. Teams may register up to four drivers per entry.

Points cannot be transferred from an existing entry to a new entry. If an entry changes to a different car mid-season, all previous championship points will be forfeited unless CMS Admins approve an exception.

20. Class and Driver Requirements

• All drivers must hold a Class C license with a minimum 4.0 Safety Rating to compete in iRTES.
• Drivers in the GTP class must have a minimum iRating of 1800 before the start of the season.
• Drivers in the GT3 class do not have an iRating minimum, but all entries remain subject to approval by CMS Admins.

21. Numbers and Templates

Official iRTES templates will be provided with required number plates and windshield banners. Teams racing without required templates may receive a DSQ. Templates will be distributed through Discord, and teams will be required to upload paints to the CMS Admins share. Trading Paints is also strongly encouraged.

• GTP cars may reserve a car number between 2 and 99 at registration.
• GT3 cars may reserve a car number between 100 and 199 at registration.

22. Race Registration Requirements

For each championship round, CMS intends to field the strongest available grid up to the 30-car limit. Team Managers must inform CMS Admins approximately one week before each race whether their team intends to participate.

If a team does not communicate its status or cannot demonstrate confidence in fielding its car, CMS may move that team to reserve status and promote another approved entry at its discretion.

Qualifying Driver

The driver who qualifies the car must start the race.

Drive Times

All teams must comply with iRacing Fair Share requirements. Teams must use at least two and no more than three drivers per championship feature.

Incident Count

After 25 incident points, the offending team will automatically receive a drive-through penalty from iRacing Race Control. After 40 incidents, the team will be disqualified from the event by iRacing Race Control.

23. Red Flag Conditions

If a race must be stopped for any reason, including a significant mass disconnect, Race Control may apply the following procedures at its discretion.

Less Than 50% of Race Duration Completed

If less than half of the scheduled duration has been covered, Race Control may restart the race using a new server. The race length may be reduced at Race Control's discretion. A race completing more than 25% but less than 50% of the scheduled duration may award half points.

More Than 50% of Race Duration Completed

If more than half of the scheduled duration has been completed, Race Control may direct remaining cars to return to pit lane and line up in the order entered. If the race cannot be restarted, finishing order will be determined using the last good lap before the race-stopping circumstance and full points will be awarded.

24. Penalties

Penalties can be applied in two ways:

1. iRacing automated Race Control penalties, including slow-downs, black flags, incident limits, and similar automated sanctions.
2. Post-race Incident Review Requests submitted by teams or CMS Admins and ruled upon by the independent steward team.

Any penalty arising from a post-race steward decision will be applied to the race results. Results are not final until all open investigations are closed.

For the final round of the season, any sanction that would normally be carried into a future event will be converted to an appropriate time or lap penalty so the final championship results can be resolved.

25. Reporting of Incidents

Following an event, competitors may submit incidents through the normal CMS Incident Review Request process. Teams will have between 12 and 60 hours from the time the official race replay is posted to submit an Incident Report to the CMS Race Review Team at CMS Incident Review Request.

All incident decisions, whether in-race or post-race, are final.

26. Sample Penalty Matrix

Penalties assigned will generally follow the table below. Stewards may increase or reduce a penalty based on the circumstances of the incident.

27. CMS Sporting Conduct

Golden Rule: Treat others as you would like to be treated. If you cause another competitor difficulty and gain unfairly as a result, give the position back.

Notes on the Golden Rule

Observing the Golden Rule is entirely up to the drivers and does not guarantee a reduction in any penalty. Stewards may exercise leniency when:

• The position is returned immediately at the scene of contact.
• It is done safely and without impeding other competitors.
• Damage to the other driver is minimal and the competitor did not suffer significant position loss or heavy damage.

28. Prizes and Awards

Season 7 will continue the iRTES emphasis on recognizing championship performance, consistency, endurance, clean racing, participation, and sportsmanship. Personalized championship awards and the core side competitions will return for the expanded six-round season.

1. Series Champion Personalized Awards — Personalized championship awards will be presented to the highest-finishing GTP and GT3 teams. Final Season 7 award design, recipient eligibility, and shipping details will be communicated by CMS before the championship opener.
2. Monster 50+ Awards — The Monster 50+ competition is a driver award for participants aged 50 and older. One winner will be recognized in GTP and one in GT3. Drivers must participate in a minimum of two championship events to be eligible. In the event of a tie, the final championship standing of the team for which the driver competed will be used as the tiebreaker.
3. Clean Team Awards — One GTP team and one GT3 team that participate in all six championship rounds will be recognized for recording the fewest iRacing incident points over the season. In the event of a tie, final championship position will be used as the tiebreaker.
4. Iron Man Awards — Iron Man is a car/team mileage award within each class. One GTP car and one GT3 car will be ranked by total championship laps completed across the season. The car with the greatest total in each class wins the Iron Man award. Any driver who drove the winning car in at least two championship rounds is eligible to receive the corresponding Iron Man recognition.
5. Sportsmanship and Leadership Recognition — Two drivers will receive special recognition as selected by the iRTES Admins at the conclusion of the season. These awards recognize sportsmanship, integrity, racecraft, participation, leadership, and positive representation of the CMS community.

Back to top ↑