6.1. Emergency Race Procedures
The following paragraphs detail the emergency race procedures that will be taken if necessary.
They outline a number of situations, however is not an exhaustive list, due to it not being possible to consider all situations.
In any event, the series Organisers, Race Control and Race Stewards have equal responsibility for enacting any emergency race procedures either due to incidents with simulation or technical problems.
6.1.1.
The main potential reasons for the need to enact emergency procedures are:
- A massive disconnection, which is made more important as a consideration due to all participants being located in the same geographical area.
- Scheduled / Unscheduled maintenance to the iRacing service.
6.1.2.
In the event of a mass disconnection, this will be immediately noted by Race Control, who will take note of the standings at the end of the last completed lap. In situations such as this, participants may either disconnect simultaneously, or over a period of a few minutes.
This could be due to an:
A power failure in a geographic area
An ISP issue that may affect a section of participants.
A communications issue with iRacing’s servers.
6.1.3.
Race Control will only effect emergency procedures in the event that more than 30% of participants (e.g 9+ for a full grid) are simultaneously affected; in other circumstances, the race event will continue as normal. In the event of a mass disconnection, the following procedures will apply:
Disconnection During Practice Sessions
6.1.4.
If the disconnection is during practice, then in the first instance, all non affected drivers will be required to return to the pit lane. Affected drivers will be required to attempt to re-join the session, noting the fact that in some instances, it can take up to 5 minutes for iRacing to allow this to occur.
6.1.5.
Should drivers be unable to re-join the session, and time remaining in practice is due to expire, a
new session will be set up, with 20 minutes worth of additional practice time. This will allow
drivers a clean slate to join the session. Note that the weather conditions may vary from those in
the original session.
Disconnection During Qualifying Sessions
6.1.6.
In the event of qualifying taking place at the point of the mass disconnection, then that session will be cancelled, and a new session will be set up with 20 minutes worth of additional practice time, and a complete qualifying session.
All qualifying times set in the original qualifying session will be void, and the times used in the new session will be used. Note that weather conditions may vary from those in the original session.
Disconnection During Race Sessions
6.1.7.
In the event of the issue taking place in the race part of the event, the action taken will be dependent on when the issue occurs:
6.1.8.
Equal to or more than 15 minutes to go – The race will be cancelled and a new race server will be started with enough practice time to allow drivers to reconnect.
The results from the abandoned race will be void.
The grid will be set as the same grid from the abandoned race.
6.1.9.
Less than 15 minutes to go but more than 7 minutes to go – The race will be called as completed and half points will be awarded based on the position of the drivers at the end of the lap before the issue occurs.
6.1.10.
Less than or equal to 7 minutes to go – The race will be called as completed and full points will be awarded based on the position of the drivers at the end of the lap before the issue occurs.
Unresolvable Circumstances
6.1.11.
In the event issues occur that prevent the running or further running of any races on a given day, the decision may be made after discussions between Race Control, the series organisers, and other major organisation parties and sponsors, to cancel or postpone the event.
This decision will be relayed to the teams and drivers through official channels.