Oceanic Endurance Championship (OEC) - GT Leagues Australia presents
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
GT Leagues Australia presents: Oceanic Endurance Championship (OEC)
Page |2
Contents:
Introduction 3
1 Entries 3
1.1 Drivers 3
1.2 Teams 3
2 Eligible Cars 4
2.1 Classes 4
2.2 Eligible Cars 4
3 Championship 4
3.1 Championship 4
3.2 Points Structure 5
3.3 Class Champions 5
3.4 Dead Heat 5
4 Events 6
4.1 Event Format 6
4.2 Official Hosting 6
4.3 Free Practice 6
4.4 Warm Up 6
4.5 Qualifying 7
4.6 Quick Repairs 7
4.7 Grid Procedure & Formation Lap 7
4.8 Pit Stops 7
4.9 Driving Time / Drivers Share 8
4.10 Safety Car Procedure 8
4.11 Red Flag 8
4.12 Checkered Flag 9
4.13 Classification 9
4.14 Results 9
5 Radio 9
5.1 General 9
5.2 Discord 10
6 Race Control 10
6.1 General 10
6.2 Incident Review 10
6.3 Race Penalties 11
6.4 Post Race Protest 11
7 Briefing 11
7.1 Forum Briefing 11
7.2 Pre Race Briefing 11
8 On Track Conduct 12
8.1 General 12
8.2 Passing 12
8.3 Blocking 12
8.4 Incidents 12
8.5 Unjustifiable Risk 13
8.6 Deliberate Contact 13
8.7 Track Limits 13
8.8 Blue Flags 13
8.9 Rejoining the Track 14
8.10 Incidents and Towing 14
9 Off Track Conduct 14Page |3
Introduction
Welcome to the Oceanic Endurance Championship Rules & Regulations document. The purpose of this
document is to outline the rules defined by the Oceanic Endurance Championship stewards. Rules in this
document will refer to ALL official test, qualifying, and race sessions.
By registering to Oceanic Endurance Championship, it is assumed that each driver has fully read, agree and
understand these rules & regulations.
Selected stewards may also race during each race, they shall act only as drivers whilst in their car, or outside of
the stewards’ room. Once that steward comes back to officiate the racing, they are to be 100% unbiased. If
stewards that are involved with any cars, that are involved in an incident, that steward will not have any say in
the judging of that incident. There will always be a steward that does not race throughout the entire
competition.
1 Entries
1.1 Drivers
1.1.1 All drivers are expected to have read and fully understands the rules & regulations stated in this
document.
1.1.2 Drivers may only change teams with Admin approval and only one change may be made per season.
This change must occur before the protest period of Rd6 is complete. Requests for Team changes
after this time will be rejected.
1.1.3 Drivers who have not participated in an event as a Driver may be removed from a pool without
penalty to either the Driver in question or the Team. Drivers who have participated in an event are
allowed one Team change per season as per rule 1.1.2.
1.2 Teams
1.2.1 Each team must supply a pool of drivers they intend to use for the season when requested at the
start of the season.
1.2.2 A team may enter a maximum of 3 cars per class (maximum of 3 Prototype (3 HPD???) and 3 GTE Pro
& 3 GTE AM).
1.2.3 A team must contact the Admins of the series if they wish to add or remove drivers from their
nominated driver lists or driver pool before Wednesday prior to an OEC race event weekend.
1.2.4 If a driver who is nominated to a car leaves a team, the team must nominate a new driver before
Free Practice 1 of the next round and notify the Admins of the series as soon as practicable. The
newly nominated driver will then be required to drive for that car for the remainder of the season.
Nominated Drivers are eligible to switch teams once per season however they will have to sit out the
following round. This change must occur before the protest period of Rd6 is complete. Requests for
Team changes after this time will be rejected.
1.2.5 If a team does not show up for 2 race events in a row, without notifying stewards with a valid reason,
then that team will be deemed to have withdrawn their entry.
1.2.6 The first team on the reserve list in that class can replace the withdrawn entry.Page |4
1.3 Cars
1.3.1 Each entry must have one nominated driver for the season.
1.3.2 The nominated driver must drive at least one stint for their nominated car for 4 rounds of the
season.
1.3.3 If a nominated driver leaves a car, they can make one switch and no longer eligible to be a
nominated driver for the new team, however may enter as a pool driver. They are unable to race in
the round immediately after leaving their previous entry.
1.3.4 The drivers from a team’s driver pool not nominated for a car may be used to complete the rest of
the stints at each round for ANY of the teams cars.
1.3.5 GTE AM cars must be driven primarily by drivers 2800iR or lower. Seeing as there’s a change to GTE
AM this season allowing a Pro driver to race with the AM drivers, a single Pro driver may drive for a
maximum of 40% of each round.
2 Eligible Cars
2.1 Classes
2.1.1 Oceanic Endurance Championship has two class choices, with 3 cars available.
LMP1 (P1) (Numbers 1 - 99)
HPD (P2) (Numbers 201 - 299)
Grand Touring Endurance Pro (GTE-Pro) (Numbers 401 - 499)
Grand Touring Endurance AM (GTE-AM) (Numbers 601 - 699)
2.1.2 The cut off for AM drivers is 2800 iRating as of the start of the OEC Season 2 Round 1 Free Practice 1.
2.1.3 Drivers in the Pro or AM class, if proving to be of a level performance outside their class, can be
adjusted to the correct Class at the admins discretion. The Admins will contact the team Manager
prior to this occurring.
2.2 Eligible Cars
2.1.1 Eligible cars are listed below:
P1: Audi R18 & Porsche 919
P2: HPD ARX01C
GTE: BMW M8 GTE, Ferrari 488 GTE, Ford GT 2017 & Porshe 911 RSR GTE
2.2.1 Stewards may balance the cars, if needed.
3 Championship
3.1 Championship
3.1.2 Oceanic Endurance Championship offers the following championship titles.
3.1.2.1 P1 Championship
P2 Championship
Grand Touring Endurance Pro Championship
Grand Touring Endurance AM ChampionshipPage |5
3.1.3 There are no drop rounds. Every race counts towards the championship.
3.1.4 The car is competing for the championship, not the drivers due to the driver pool system.
3.2 Points Structure
3.2.1 At the end of each round points are awarded to each class, as follows:
3.2.2 The Final round being an 8hr event will be a double points round. The points will be split between
the 4hr point and the finish of the race. The car list will be recorded on the lap post the 4hr mark and
points awarded as per the grid above.
3.2.3 For a team to score points, the car must be classified by the iRacing system. Further info is in (Article
6.12)
3.3 Class Champions
3.3.1 At the end of the season the car with the highest amount of points in each class will be declared the
winner of their class. They will also have their class number reserved if they register the same team
in the next season. (i.e. 1, 201, 401)
3.4 Dead Heat
3.4.1 If at the end of the season, two or more teams finish with the same number of points, the higher
result will go to the team with;
a) The highest number of wins.
b) If the number of first places is the same, the team with the highest number of second places
and so on until a winner emerges.
c) In case of a further tie the criterion for breaking the tie is by comparing the quickest race lap
time in all races for both teams. The team with the most fastest lap times emerges as winner.Page |6
4 Events
4.1 Event Format
4.1.1 Each event will have the following format. (AEST):
Friday - Free Practice 1 - 4-hour Server
Team Session Only - Rules (Article 4.3) apply.
Track Opens: 7:00pm - 11:00pm
Weather: Dynamic (Set Date and Time)
Password: TBA
Saturday - Free Practice 2 - 4-hour Server
Team Session Only - Rules (Article 4.3) apply.
Track Opens: 12:00pm - 4:00pm
Weather: Dynamic (Set Date and Time)
Password: TBA
Saturday - Free Practice 3 - 4-hour Server
Team Session Only - Rules (Article 4.3) apply.
Track Opens: 6:00pm - 10:00pm
Weather: Dynamic (Set Date and Time)
Password: TBA
Sunday - Race Day
Track Opens - 8:00am
Practice - 8:00am (70 minutes)
Qualifying - 9:10am - Qualifying Format (Article 4.5)
Race - 10:00am
Weather: Dynamic (Set Date and Time)
Password: TBA
4.2 Official Hosting
4.2.1 All official events will be hosted using the Australian server farm unless unforeseen circumstances
require use of the US server farm.
4.2.2 All sessions will be team only.
4.3 Free Practice
4.3.1 Each team must enter the practice session with the correct car and entry number. Warnings will be
applied for breaching this rule.
4.3.2 Incidents from Free Practice are able to be protested. Only protests breaching series rules will be
reviewed. A replay file will be required for these protests and must be sent to the RC team as quickly
as possible. Time is obviously needed to review these and if submitted too close to the Race session
will be discarded.
4.4 Warm Up
4.4.1 The practice within the race session is considered to be the events warm up.
4.4.2 All rules and penalties apply during this session.Page |7
4.4.3 Each team must enter the practice session with the correct car and entry number. Penalty is pit lane
start.
4.5 Qualifying
4.5.1 All qualifying will take place within the session.
4.5.2 The grid will be broken up into classes and sent out for 20 minutes at a time. In order of GTE then
Prototype.
4.5.3 Using any chat channel except @TEAM, will not be accepted. If done so in error a warning will be
issued. Further breaches will result in a pit lane start.
4.5.4 Being on track whilst it is not your classes allotted time is unacceptable. Penalty is pit lane start.
4.6 Quick Repairs
4.6.1 Damage can occur in iRacing for situations beyond peoples control at times. To cover this there is 1
quick repair available per race. The Quick Repairs may be used at any time throughout the race.
4.7 Grid Procedure & Formation Lap
4.7.1 All teams are expected to grid as soon as possible.
4.7.2 If any car grids that has a ‘Start from Pitlane’ penalty, a penalty of Stop & Hold will be applied.
4.7.3 Whilst under Safety Car control on the formation lap, every car should follow within 3-4 car lengths
of the car in front, at a steady and safe manner.
4.7.4 Excessive weaving or accelerating/braking to warm tires, is prohibited. This creates potential hazards
to other drivers.
4.7.5 When the safety car pulls off, the lead car maintains speed within 3kph of the safety car speed. The
class leader is considered as the green light for the respective class and must start within the start
box as per the briefing.
a) Any car of the same class behind the class leader who goes before the leader will be
penalised for a jump start.
b) If the leader goes before or after the start box the leader will be penalised for a jump
start.
4.7.6 The GTE class leader should leave a gap of 2 seconds or greater to the last car of the P class.
4.7.7 The GTE class leader DOES NOT start on the green flag. But start when they are coming to the
start/finish box as defined in the briefing.
4.7.8 Cars starting from Pit Lane for whatever reason must wait for the last car of the GTE Class to pass
before leaving the pit lane. Any car leaving before the final car passes the exit of pit lane (Green
Cones) will receive a Stop & Go penalty.
4.8 Pit Stops
4.8.1 Drivers should safely enter pit lane at all times in a manner that does not obstruct other drivers on
the normal racing line.Page |8
4.8.2 The beginning and end of the pit area will be defined precisely on each circuit by the yellow and
green cones.
4.8.3 Pit lane speed limit is set by iRacing and enforcing of the speed limit is done automatically by iRacing.
4.8.4 On exiting pit lane, drivers are required to follow the natural pit exit lane and join the track in a safe
manner after the pit exit merges with the main track.
4.8.5 On pit lane, contact through reckless or careless driving will be penalised one grade higher than on
track as there should never be contact in the pit lane.
4.9 Driving Time / Drivers Share
4.9.1 Driving time is calculated by the laps of each driver in each team. A driver may drive a maximum of
67% of the total laps of the team’s car in each race.
PENALTY: When the maximum driving time is exceeded by a driver, a number of laps equal to the
exceeded amount shall be subtracted from the completed number of laps of this team. The car shall
be classified as the last car on that lap.
4.10 Safety Car Procedure Section UPDATE PENDING
4.10.1 The safety car will only be called upon, when a driver or team call for a tow and RC deem a Safety Car
Period necessary. (see article 8.10)
4.10.2 Once the safety car has been called upon, it is the responsibility of each driver to slow down to a safe
pace, while catching the safety car.
4.10.3 Excessive weaving or accelerating/braking to warm ties, is prohibited. This creates potential hazards
to other drivers.
4.10.4 Pit lane is deemed to be closed at the time of safety car being called. This is regardless of any iRacing
instruction. Pit lane will open at discretion of Race Control.
Cars who enter pit lane while it is closed and take service will receive a Stop and Hold penalty on
restart.
Cars who enter pit lane while it is closed that don’t take service will receive an EOL Penalty after the
pit cycles have completed.
4.10.5 Whilst under safety car all cars in between of the overall race leader of their class and the safety car
will be waived by and able to make their way, safely, around to the rear of the field. Any incidents
during this time will be reviewed by Race Control after the race goes green again. SC will always pick
up the lead Prototype.
4.10.6 At the end of the safety car period, the race will go back to green racing. The leader of the field must
not go before the green flag waves.
4.10.7 When the safety car pulls off, the lead car should stay within 3kph of the safety car speed. The race
restarts with the Lead Car of the field being the Green Flag and following the same rules as the Start
procedure. There is no class split on restarts, the field is considered a single grid. The same penalties
apply for jumping the restart as jumping the start.
4.10.9 Drivers must maintain a reasonable distance (2-4 car lengths) with the car in front. Failure to do so
may result in a penalty.Page |9
4.11 Red Flag
4.11.1 A red flag scenario is for major situations such as mass disconnects and other arbitrary issues. If a
Red Flag is called by RC all cars will be required to hit the Pit Lane Speed Limiter and head to the
pitlane.
4.11.2 If the race has 40 minutes or less remaining then the race will be declared at the last fully completed
lap before the incident causing the red flag.
4.11.3 If there is more than 1hr remaining, when the relevant entrants have reconnected the safety car will
be called out and the field reordered to the positions on the lap prior to the incident as best as can
be accomplished. The race will then be restarted at RC’s discretion.
4.12 Chequered Flag
4.12.1 When the scheduled time for the race has elapsed or the full race distance has been covered, the
chequered flag will be shown to the car that is leading the general classification when it crosses the
finish line on the race track.
4.12.2 After each driver takes the chequered flag, they should exit their car in a manner that doesn't
impede the other drivers. We encourage drivers to finish the lap and stop in their pit stall.
4.12.3 The winners of each class are allowed to do burn-outs or donuts, as long they don’t impede other
drivers.
4.12.4 At no point on the cool down lap may drivers cause contact with others with the intention of
showing retaliation. Any driver found doing so will be penalised in the final results, at the discretion
of the stewards.
4.13 Classification
4.13.1 In order to be classified, a car must:
Completed at least 70% of the distance covered by the class leader’s car.
(Decimals will be rounded to the nearest whole number)
A minimum of two (2) drivers must have driven in the event.
All drivers must respect the maximum driving time (see article 4.9)
4.14 Results
4.14.1 All results are provisional until they are confirmed by the series admins.
5 Radio
5.1 General
5.1.1 Official announcements from race control will be done over iRacing over the @RACECONTROL radio
channel.
5.1.2 Using text or voice chat on the @drivers, @allteams and @club channels are prohibited during the
raceday warmup/practice, qualifying and race sessions. Failure to comply with this rule will result
first in a warning then in a penalty for further infractions.
5.1.3 The @allteams channel may only be used during the race to ask for tow permission when needed
due to severe or terminal damage to the car. Notification of Meatball Flags to Race Control is alsoP a g e | 10
allowed and now required. Race Control will delay any penalties in event of a Meatball Flag to allow
the flag to be cleared in the pits.
5.2 Discord
5.2.1 OEC has a Discord Server available for teams, drivers, broadcasters, as well as spectators and fans.
5.2.2 The OEC Discord Server can be joined at the following link: OEC Discord Server
5.2.3 All team members are expected to be in the OEC Discord Server during the race.
5.2.4 Race Control will contact teams directly through Discord.
5.2.5 Race Control may summon a team member(s) to the Stewards (Voice Channel).
Penalty: If Race Control does not get a response from the team, the car will receive a Stop & Go
penalty.
6 Race Control
6.1 General
6.1.1 All series events will have live race control, consisting of multiple stewards monitoring on track
activity.
6.1.2 Race Control has the ability to hand out penalties to drivers who fail to drive in a clean, fair manner,
act recklessly, or otherwise affect the spirit of competition within this championship.
6.1.3 Race control may remove drivers off the track if they pose a risk to other driver’s due to their driving
or internet connection. In this case, a driver will first be warned and given time to correct this. In the
event the issue persists, the driver shall be ordered to retire from the race and be replaced by
another driver from the team in the car.
6.1.4 Race control shall not reverse penalties generated by iRacing itself.
6.2 Incident Review
6.2.1 When a team would like race control to review an incident, they must fill out the protest form on the
website. Any incident a team wants race control to review must be submitted within 20 minutes of
the incident occurring.
6.2.2 Once race control has made a decision, the stewards will publish the outcome in Discord, that is
available for all teams, and issue the relevant penalty if required.
6.2.3 In case of a warning, race control will notify the team that receives the warning in addition to
publishing it in the outcome document.
6.2.4 In the event of an incident taking place in the last 30 minutes of the race, race control may choose to
review the incident after the conclusion of the race. In this instance, if a penalty is awarded, the
duration of the penalty will be added to the overall time of the driver being awarded the penalty.
6.2.5 Race Control has the right to estimate (using JRT) total time it takes to transit the pit lane, for every
track. This is so every post-race penalty is fair towards penalties taken during the race.
6.2.6 To appeal a protest the appeal must be made within 3 laps of the penalty being notified. The team
may present information in regards to the penalty to assist RC in the determination of the outcome.P a g e | 11
All information presented will be used to deliberate on the protest, however RC’s determination will
be final.
6.3 Race Penalties
6.3.1 All penalties must be served under green flag conditions. In the rare situation of a Black Flag clashing
with a Safety Car Period, the black flag will be removed and re-applied after the start/finish upon
commencement of green flag racing.
6.3.2 A penalty may not be combined with a pit stop.
6.3.3 When a penalty is served incorrectly, the penalty must be served again until it is served correctly.
6.3.4 Penalties must be served within three laps after being issued.
6.3.5 Warnings, Stop & Go or Stop & Hold penalties served during the race cannot be appealed during or
after the race.
6.4 Post Race Protest
6.4.1 A post-race protest not previously dealt with can be filed after chequered flag has been waved at
each racing event and before two whole days after. To file a post-race protest, fill in the protest form
on the Oceanic Racing website as normal.
6.4.2 The post-race protest must be filed within 24 hours of the race event race day. This means that if the
race is taking place on a Sunday, the deadline for the post-race protest is the following Monday
before 11:59pm AEST.
6.4.3 The stewards will review the incident and publish the decision on the GLA Discord Penalty Channel.
6.4.4 Post Race Penalty reviews may include contacting all parties involved to gain as much information
surrounding the events in the penalty. Teams must be prepared to be contacted by Race Control to
allow proper review of the penalties.
6.4.5 Post Race Protests are primarily for incidents which cause large damage or harm another cars race to
a large degree which were unable to be dealt with effectively during the event, occurred within the
last 30 minutes of the race or set to post race by Race Control for further deliberation.
7 Briefing
7.1 Forum Briefing
7.1.1 Otherwise known as ‘Race Information’ in the race thread on the AUS/NZ Road Discussion forum and
on the Oceanic Racing Discord. This post will have information series related, and specific event
related issues. Each driver and team are expected to read over this document, and fully understand
it.
7.2 Pre-Race Briefing
7.2.1 The final 10 minutes of Qualifying is not part of Qualifying. All cars will be notified to complete the
lap they are on and the teams will be requested to join the briefing room for the pre-race briefing.
7.2.2 If cars do not leave the track within a decent amount of time, a penalty may be given by Race
Control. Additionally, no cars should be on track during or post driver briefing until Gridding.P a g e | 12
7.2.3 This briefing will cover issues that relate to the race, and what track it is at. Covering issues such as
pit lane entry and cut off points. Any cars that have been given any penalties for a pit lane start, will
be notified for the last time.
8 On Track Conduct
8.1 General
8.1.1 It is expected that all drivers within the series race in a fair, honest manner, paying consideration to
other drivers on the race track, and do not commit any action that may bring the league into
disrepute.
8.1.2 All drivers, and team members, should treat other drivers, team members, and race control with
respect at all times. Not just on track, but also outside the race sessions. Any driver failing to observe
this may be penalised at the discretion of the stewards, which may go as far as exclusion of the
driver.
8.1.3 Drivers are expected to treat other members within the series in a courteous manner at all times.
Drivers using insulting, threatening, racist, sexist, homophobic, or any other form of derogatory
behaviour, either in written or spoken format, in the league race server or otherwise can and will
face severe penalties, up to and including exclusion from the league.
8.2 Passing
8.2.1 In all cases, it is the responsibility of the faster car to safely overtake the slower car. It is the
responsibility of the slower car to maintain a consistent line. It is strongly recommended that a
slower car being lapped makes every reasonable effort to facilitate a safe pass.
8.2.2 In case a car gains a position by an unfair manner, like exceeding track limits or car contact, a penalty
may be mitigated by giving back the position.
8.3 Blocking
8.3.1 A driver may not move in reaction, altering the line based on the actions of the pursuing car, or
select a defensive line and move back to the racing line in the braking zone.
8.3.2 Only a single defensive move is allowed. A second move in the same direction whether reacting to
another car or not is considered blocking. Returning to the racing line for the braking zone is not
considered blocking unless it impedes the progress of the following car.
8.4 Incidents
8.4.1 Any driver who, in the opinion of race control, is responsible for: an incident where a car spins, or
goes off-track, or suffers other mechanical difficulty requiring it to pit directly for repairs, or an
incident of contact resulting in a change of position, may be warned or penalised. Requiring to pit
may take up to 3 laps for the team to know, therefore RC will keep an eye on this.
8.4.2 ‘Netcode’ events will be taken into account in relation to incidents and may or may not affect the
outcome of RC’s decision.
8.4.3 Race Control are the determining factor in a penalty decision and any redress of a position will be
factored into that decision. A penalty may still be awarded even if a position is given back depending
on the circumstances of the incident.P a g e | 13
8.5 Unjustifiable Risk
8.5.1 Any driver who creates a dangerous situation, e.g. unsafe re-join of the track after a spin or incident,
may be warned or penalised.
8.6 Deliberate Contact
8.6.1 Making contact and collisions with another car on purpose will be penalised.
8.7 Track Limits
8.7.1 The track is defined within the white lines, including the white lines.
8.7.2 The racing surface may differ from the track with the inclusion of Kerbs and is track dependant.
Issues with racing surface definition will be pointed out in the Briefing document supplied by Race
Control the week before the event.
8.7.3 All cars must stay in contact with the racing surface with at least two wheels at all times. Drivers may
not leave the racing surface on a consistent basis in the same corners or different places on the
track. NOTE: Consistently going off track is at discretion of the stewards. 1-2 incidents per lap is
enough to get the attention of the stewards.
8.7.4 Going off the racing surface is only allowed when entering/leaving pit lane or to avoid an accident.
8.7.5 Drivers leaving the racing surface may not improve their position at any time over other running
cars. Drivers must also concede position if leaving the racing surface stops another car from
overtaking them in this short part of the track.
8.7.6 Teams can protest others for exceeding track limits. It must be very clear that the other car went
outside the racing surface with more than two wheels on a consistent basis. This means that over the
course of a few laps, off tracks occurred multiple times in the same corner or at other areas of the
track. NOTE: Consistently going off track is at discretion of the stewards.
8.7.7 Cars on the racetrack may use any portion of the pit exit that is part of the track surface.
8.7.8 While a portion of pit exit may be part of the track surface, cars on the racetrack must be aware of
cars re-joining while exiting the pits. Any contact that occurs as a result of a car exiting the pit may
be penalised and a penalty is at discretion of the stewards.
8.7.9 At the discretion of the organisation, exception zones may be added to certain areas of a track. At
these exception zones drivers may leave the normal track limits and treat them as part of the racing
surface.
8.7.10 In case exception zones are assigned, these will be documented and explained in the driver’s
briefings.
8.8 Blue Flags
8.8.1 It is the responsibility of both the overtaking driver and the driver being overtaken to assure safe
overtaking.
8.8.2 Blue flags while NOT authoritative are to be served as soon as it is safe if applicable. A car that is
unlapping and clearly faster than the car a lap or more up does not need to yield and can race
normally.P a g e | 14
8.9 Re-joining the Track
8.9.1 Any car that leaves the track must re-join the track in a safe manner as to not interfere with other
cars. The track and racing surface is described in Section 8.7 Track Limits. Penalties will apply for
dangerous rejoins.
8.10 Incidents and Towing
8.10.1 In the event of an incident, it is a driver’s, and its team’s, responsibility to assess if it is safe for them
to resume racing or not.
8.10.2 A driver who has sustained damage may drive back to pit lane under their own power if able to do
so. However, the following rules apply when driving back to the pit lane with damage:
The driver must be able to steer the car in both directions.
The driver must be able to control the car in such a way that he would not create a further incident.
The driver must be able to maintain a speed of at least 50% the racing pace.
Where the driver's speed is above 80% of the racing pace, the driver may directly follow the iRacing
procedure for dealing with damage (Meatball) flag. However, if the driver’s speed is below 80% of
the class racing pace, the driver must pit at the first possible opportunity (The next time the driver
can enter the pits).
8.10.3 In the event of a driver being unable to drive their car back to pit lane under their own power, it is
their responsibility to request a tow and wait for Race Control to give permission to tow. (This will
also bring out a Safety Car see article 4.10) Contact RC via Discord or in sim chat.
9 Off Track Conduct
9.1 Forum Etiquette
9.1 While it’s easy to get frustrated on track and incidents do happen, the forum threads and Discord
channels for the series is not the place to vent against or abuse any of the
Organisers/Sponsors/League Members or any other user. If there is a serious breach of etiquette
then the Series Administrators and Race Control will determine the punishment for the individual or
team involved up to and including exclusion from future races in the series and even possible future
series.
For any issues with respect to this series don’t hesitate to contact any of the named Administrators
and we’ll try to find a solution to the problem and hear any suggestions for improvements. We all
want to enjoy our racing and we want to extend that enjoyment to all Participants, Spectators and
Administrators for the series.
MOST IMPORTANTLY HAVE FUN AND RESPECT
EACH OTHERYou can also read
