Zone Challenge News

During the Zone Group Challenge Series, look here for news and file updates.

Saturday, March 6, 2021 – The official server replays are now available on this page in the “Schedule” section.

Friday, March 5, 2021 – Carpack 2 has been released. Instructions are inside the zip file.

Congratulations!

Congratulations to the drivers who will be representing their Zones in the upcoming 2021 Challenge Championship!

Zone Group Challenge

The Zone Group Challenge provides an opportunity for all classed PCA Sim Racing drivers to qualify for the Zone Group Challenge Championship.

The four races are open to all drivers who are registered and assigned a classification in one of the four PCA Sim Racing classes. The classes are PCA Challenge, PCA Sport, PCA Club, and PCA Pro.

Entry & Eligibility

Participating drivers in the Zone Group Challenge must have been assigned classification via the eDE onboarding process. For drivers who are not familiar with the eDE Driver Education program of PCA Sim Racing, click here. Drivers registering for PCA Sim Racing on or after August 1, 2020, must complete at least one eDE Monday Madness session, and at least one Interlude or Prelude practice race event and be approved for competition with a PCA Sim Racing eDE Instructor before participating in an event. An invitation has been made available to any driver registered in PCA Sim Racing before August 1, 2020, and who has been assigned a racing class based on their prior racing performance and safety.

Important Note! Drivers who are listed among the Zone winners listed above are welcome to run the Zone Group Challenge, but they will not receive any points since they have already been promoted to the Zone Group Challenge Championship. Those already qualified drivers should not join the Zone Group Challenge race servers until 30 minutes have elapsed in practice on race night. This is to provide other racers a fair opportunity to run for a grid spot in the Zone Group Challenge Championship. If any questions on this, please contact a Steering Committee member on Discord.

Invitation Acceptance

Acceptance of the invitation in iRacing is required. To accept your invite, click the notification in the browser-based user interface (UI). If a driver does not have an invite when he/she logs into iRacing, please contact a member of the Steering Committee via email or on Discord, and his/her status will be reviewed.

Schedule

Event 1 – Watkins Glen International
Friday, March 5, 2021

PCA Challenge  Replay  Broadcast
PCA Sport  Replay  Broadcast
PCA Club  Replay  Broadcast
PCA Pro  Replay  Broadcast

Event 2 – Sonoma Raceway
Friday, March 12, 2021
Layout: Cup

PCA Challenge  Replay  Broadcast
PCA Sport  Replay  Broadcast
PCA Club  Replay  Broadcast
PCA Pro  Replay  Broadcast

Event 3 – Road America
Friday, March 19, 2021
Layout: Full Course

PCA Challenge  Replay  Broadcast
PCA Sport  Replay  Broadcast
PCA Club  Replay  Broadcast
PCA Pro  Replay  Broadcast

Event 4 – Sebring International Raceway
Friday, March 26, 2021
Layout: International

PCA Challenge  Replay  Broadcast
PCA Sport  Replay  Broadcast
PCA Club  Replay  Broadcast
PCA Pro  Replay  Broadcast

Format

The Zone Group Challenge will use the following format for events.

Server Name: PCA Challenge – ZGC
7:00 PM Eastern – Practice (advance on the 60-minute clock)
8:00 PM Eastern – Closed, Private Qualifying (advance on the 10-minute clock)
8:15 PM Eastern – Race (30-minute race)
8:50 PM Eastern – Post-race Podium eSports interview of the race winner & switch servers

Server Name: PCA Sport – ZGC
8:00 PM Eastern – Practice (advance on the 60-minute clock)
9:00 PM Eastern – Closed, Private Qualifying (advance on the 10-minute clock)
9:15 PM Eastern – Race (30-minute race)
9:50 PM Eastern – Post-race Podium eSports interview of the race winner & switch servers

Server Name: PCA Club – ZGC
9:00 PM Eastern – Practice (advance on the 60-minute clock)
10:00 PM Eastern – Closed, Private Qualifying (advance on the 10-minute clock)
10:15 PM Eastern – Race (30-minute race)
10:50 PM Eastern – Post-race Podium eSports interview of the race winner & switch servers

Server Name: PCA Pro – ZGC
10:00 PM Eastern – Practice (advance on the 60-minute clock)
11:00 PM Eastern – Closed, Private Qualifying (advance on the 10-minute clock)
11:15 PM Eastern – Race (30-minute race)
11:50 PM Eastern – Post-race Podium eSports interview of the race winner & closeout event

Car

The Zone Group Challenge and Zone Group Challenge Championship will use the iRacing Porsche 911 RSR for all races.

Track & Weather Conditions

  • Dynamic Sky
  • Relative humidity set at 30%
  • Temperature is 65°F
  • The wind is 1 mph
  • The starting “track state” for practice will be 10% with track surface rubber building-up during the sessions
  • Marbles will be removed
  • iRacing in-sim conditions:
    The race date will always be the actual date of the event
    Start times – practice “8:00 AM”; qualifying “9:00 AM”; race “9:30 AM”

General Settings

The following common setting will be used for all races within Zone Group Challenge:

  • Local yellow flags only
  • No full course yellow flags
  • There will be one “Fast Repair” permitted in all 4 classes
  • Damaged cars can be “towed” to the pits and drivers may rejoin the race after their car is repaired
  • No scheduled pit stops
  • Starting fuel – open setting
  • Open setups

Custom Livery Painting

  • Custom paint schemes are permitted and encouraged but must comply with iRacing eSports Network broadcast criteria. Refer to: iRacing Custom Paint Policy and iRacing Terms of Use, and reference generally.
  • Broadcasts will not use Trading Paints due to potential technical issues. Thus, any paint schemes uploaded to Trading Paints will not be visible on broadcasts.
  • Custom painted driver suits, pit crew suits, and pit stall customization will not be accepted in Zone Group Challenge or Challenge Championship.
  • Drivers are welcome to use either their PCA Sim Racing Series 4 livery, their TeamRacing Series livery, or this template.
  • If you want to use your existing Series 4 car livery, you do not need to resubmit it.
  • If you want your new livery added to the race server, please send it to Doug Atkinson on Discord by Wednesday at 12:00 PM. Car skins received after that time will be added to the following carset for the following race.
  • An updated carset will be available each Wednesday around 5 PM Eastern time. It is not mandatory you use the carset, but if you want to see which cars are around you, and not a multitude of the Porsche Intelligent Design iRacing provided livery, download and install the carset updates.

Communications

  • As a condition of participating in the PCA Sim Racing Zone Group Challenge, drivers agree to the following items regarding communications:
  • Joining the PCA Sim Racing Discord server is now a requirement for participating in the PCA Sim Racing League.
  • The Race Stewards will communicate with drivers via the iRacing voice chat function during the event and never on Discord.
  • It is strongly recommended drivers setup multiple keys for race comms.
  • Drivers must use Push-to-talk (PTT). Tip: Don’t wait until race night to adjust this!
  • Use only the in-game voice function on iRacing during the race. Race control will not be monitoring driver channels on Discord.

Use of Discord in the Race

  • Do not use Discord during the race unless you have a private channel with your spotter. Instead please make sure that you are using the in-game voice function on iRacing.
  • No competing driver or the driver’s spotter may enter a competitor’s private Discord channel.

Post-race Interviews

  • The winner of each race will be interviewed by Podium eSports. Winners should join the PCA Sim Racing Discord server, the Podium eSports Category, and the Interview Waiting Room channel right away after the race.
  • Podium eSports will do a microphone check with you then you will be moved to the Broadcast channel.
  • Please make sure your equipment is working for post-race interviews.

Post-race Discussions

  • Should a driver request a post-race meeting with Race Control for any reason, please send a Discord direct message (DM) to Doug Atkinson.

Qualifying

  • Drivers have 10 minutes to complete up to 3 timed laps during the qualifying session, the quickest of which will be used to determine the qualifying position for the race.
  • Important Note! The server will be manually advanced at the end of 10 minutes of qualifying. e.g., when the server reaches 00:00 in qualifying, it advances to the race grid.

Race Starts

  • Races start when iRacing shows the green flag / green lights.
  • There are no League restrictions passing once the race has started.
  • iRacing AI’s race start restrictions are still in effect. Those can be found in iRacing’s FIRST Sporting Code.
  • A link is also available in iRacing under the “Help” > “Sporting Code”. They are reproduced below:
    • 5.6. Starting
    • 5.6.1.Road Course
    • 5.6.1.1. Road race starts may from a standing or rolling start depending on the series.
    • 5.6.1.4. If the start for the road course is a roiling start, oval rules apply as stated in Section 5.6.2.
    • 5.6.2.Oval
    • 5.6.3.1. Standard oval race starts will be in the form of a rolling start.
    • 5.6.3.2. Once all drivers are on the grid, the pace car will lead the field around the track and exit the course as late as possible to enter the pit lane.
    • 5.6.3.3. As the front row of cars approaches the start/finish line, the green flag will be shown, signifying the start of the race.

Tire & Brake Warming

  • Do not warm tires or brakes before the start of the race. e.g., weaving around, hard braking, hard accelerating, etc.
  • If a driver is seen by Race Control doing either, they will receive a drive-through penalty from Race Control after the start of the race.

First Lap Orange Zone

  • If Race Control sees a driver hit another driver’s car regardless if it is slight contact or an outright incident, the driver will be given a one-second stop-and-go for each infraction.
  • A driver may not service their car during the penalty fulfillment.
  • If a driver does try to service their car, iRacing AI will automatically apply an additional time penalty.
  • To avoid this, uncheck all tires, fuel, and tear-offs before stopping for the penalty.

Flags

Blue Flags

  • Blue flags are advisory that a faster competitor is following you, not a mandate or directive to pull over.
  • However, a driver who does not heed a blue flag for corner-after-corner is eligible for a blocking penalty applied by the Race Stewards.

Blocking

  • You can adjust your line one time if you have someone racing for a position trying to overtake.
  • After that, you must hold that line and allow the overtaking driver the opportunity to pass.
  • That does not mean you have to lift and let them pass, you just may not swerve back and forth to block them.
  • The penalty for blocking is a drive-through.

Rejoining the Track

  • After a spin or incident, drivers must rejoin the track safely and not affect an upcoming driver’s racing line. Be patient!
  • Do not pull back onto the track without a clear line of sight for the track behind.
  • If you cannot see far enough behind you, stay off-track in the grass and slowly drive until you get to a straight section of the track where you can see ample distance behind your car.
  • Drivers should not back their cars onto the track unless there is absolutely no option.
  • A one-second stop-and-go penalty will be applied if a driver is deemed negligent in unsafe track re-entry.

Passing

  • The overtaking driver has the primary responsibility for the completion of a clean, safe pass but…
    • the driver being overtaken cannot alter his line to block the (faster) overtaking car.
    • the driver being overtaken cannot alter his line to impede the (faster) overtaking car.
    • the overtaken driver cannot brake-check the faster overtaking car.
  • The overtaking driver cannot turn in and squeeze the overtaken driver that’s on the inside of a corner and force them off track.
  • PCA Sim Racing uses Section 5 of the F1Metrics article, The Rules of Racing to address who owns the racing line.

Errant Penalties

  • Race Stewards will clear an errant penalty if a driver receives the penalty from iRacing AI for driving in an off-limits area to avoid an incident.
  • Drivers should ask the Race Stewards over the iRacing voice chat to please clear their penalty received and what the circumstances were when they got the penalty. For example, “Race Control this is car #15. I received an errant penalty for avoiding a crashing car when I drove on the infield.” An explanation of, “Race Control this is car #15. I’m not sure why I got a penalty. Can you clear it please.” will not suffice.
  • After a live review of the circumstance, Race Stewards will cancel or validate the penalty.
  • Drivers should be aware that iRacing AI may apply a penalty to a driver that Race Control has no idea the penalty was applied until after the iRacing race log is completed post-race. All Race Control will see is the log with the penalty calculation (1x, 2x, etc.).

Technical Issues

  • Any driver who has a bad connection will be alerted by the Race Stewards and may be asked to park their car in the pits until the problem is resolved.
  • If there is an additional problem or their connection remains unstable, they will, unfortunately, need to leave the server so it does not affect the race quality for other competitors.
  • Any driver leaving the server because of connection issues is welcome to rejoin the race once they have resolved their Internet problem by rebooting their computer, their router, or reducing the load on their home connection.
  • Drivers with a poor internet connection may be removed from the race.
  • Do not connect to a PCA Sim Racing event via a wireless connection and use only Ethernet cabled connections.

Race Incident Overview

  • Incidents may be reviewed IN-RACE, POST-RACE, or both IN-RACE and POST-RACE.
  • Race Stewards reserve the right to discuss and seek counsel about an incident with drivers not participating in the Series.
  • No intentional wrecking or spinning of another car will be allowed regardless if it is horseplay or serious during any event session. This applies during practice, qualifying, race, and post-race sessions.
  • Drivers are welcome to celebrate their accomplishments post-race (e.g., spinning donuts) but the celebration should never impede drivers still on-track who have not taken the checkered flag.

Incident Points

  • Drivers will be allowed up to 15 incident points during each race.
  • After 15+ points (e.g., 16), each driver will receive a drive-through penalty.
  • A drive-through penalty will be applied for each additional 5 incident points thereafter (e.g., at 21 and 26 incident points, etc.)
  • Once a driver receives 30+ incident points they will be retired from competition in the race by the iRacing AI official. This will be an automatic function and will trigger once a driver hits 31 points.
  • Because iRacing works on “no-fault”, both drivers involved in a contact incident will receive incident points.
  • All races in the Zone Group Challenge will use these same Incident Points settings.
  • The Steering Committee reserves the right to adjust the Incident Points on a per race basis.
  • Important! Incident Points are defined in iRacing’s Section 3.5 Incidents of the FIRST Sporting Code. A link is also available in iRacing under the “Help” > “Sporting Code”.
  • Race Stewards reserve the right to disqualify any driver who is driving intentionally recklessly or intentionally driving in a retaliatory manner.
  • A driver intentionally driving recklessly or intentionally driving in a retaliatory manner may be reviewed by the Race Stewards.
  • Race Stewards may apply a penalty up to and including being banned from the Series.
  • Regarding the severity and application of penalties, Race Stewards will apply punitive measures either IN-RACE, or POST-RACE, or both IN-RACE and POST-RACE commensurate with the infraction.
  • Race Stewards will also consider the flagrancy and impact on other drivers involved in an incident.
  • IN-RACE penalties assigned by Race Stewards may include a loss of a finishing position — or finishing positions — in the current race results before results become official.
  • Race Stewards have the authority to DISQUALIFY (DQ) a driver, as noted.
  • If necessary, finishing positions will be changed and points altered to reflect a disqualification.

Penalties

The following penalties will be applied in the race by iRacing AI and/or Race Stewards.

A drive-through penalty

  • tire warming
  • brake warming
  • blocking
  • more than 15+ iRacing incident points during a race
  • each additional 5 iRacing incident points beyond 15+ points (e.g., 16) during a race

To clear a drive-through penalty, a driver must enter the pit lane under green track conditions with no other black flags, and pass through the whole pit lane without stopping in their pit stall. This action will clear the drive-through penalty as the driver passes the pit exit.

A drive-through penalty cannot be cleared if entering the pits while the track is under caution, but if a caution comes out while a driver is already in the pitlane trying to serve a drive-through penalty, the penalty will still clear successfully.

A one-second stop-and-go penalty

  • an Orange Zone penalty
  • unsafe re-entry onto the track

A one-second stop-and-go penalty requires the driver to enter their pit, stop at their pit for one-second then exit.

  • The penalized driver is prohibited from servicing the car at this time.
  • Drivers must uncheck all pitstop mechanics in the black box on iRacing, e.g., tires, fuel, etc.
  • Each penalty requiring a stop-and-go shall be considered as separate and distinct infractions and shall not be combined.

A ten-second stop-and-go penalty

  • causing an accident.

A ten-second stop-and-go penalty requires the driver to enter their pit, stop at their pit for ten-seconds then exit.

  • The penalized driver is prohibited from servicing the car at this time.
  • Drivers must uncheck all pitstop mechanics in the black box on iRacing, e.g., tires, fuel, etc.
  • Each penalty requiring a stop-and-go shall be considered as separate and distinct infractions and shall not be combined.

A thirty-second stop-and-go penalty

  • causing an accident where a competitor is forced to retire their car.

A thirty-second stop-and-go penalty requires the driver to enter their pit, stop at their pit for thirty-seconds then exit.

  • The penalized driver is prohibited from servicing the car at this time.
  • Drivers must uncheck all pitstop mechanics in the black box on iRacing, e.g., tires, fuel, etc.
  • Each penalty requiring a stop-and-go shall be considered as separate and distinct infractions and shall not be combined.

Retirement from the race

The following items will be justification for a driver’s retirement.

  • causing 3 accidents in a race
  • acquiring 30+ incident points
  • unsportsmanlike retaliation on voice comms or by driving directly into a competitor
  • a driver running so severely off the pace that it endangers other competitors
  • a major, unresolvable problem with a driver’s Internet connection

Probation

The following criteria will be justification for a driver’s probation from the series.

  • Causing 3 accidents in a single race
  • Unsportsmanlike conduct
  • Driving with disregard for the rules at the discretion of the Stewards

Probation would last 1 race.

  • If the driver causes another crash during the probation period, he will have his invitation to the league revoked for one week. During that week, the driver must complete at least one more eDE Monday Madness session and at least one Interlude or Prelude Wednesday night event (re-certify).
  • After completing the re-certification and being “signed off” by the eDE Manager or his surrogate, a new invitation to join the league will be extended to the driver. Note that during the interim period, a driver is strongly encouraged to attend additional Monday Madness and Wednesday Interlude and/or Prelude events or solicit additional help from the eDE team.

Serving & Clearing Penalties

  • The Steering Committee and eDE instructors recently conducted an extended testing session to simulate all possible scenarios that may incur a black flag penalty. We confirm that the method to which a penalty should be served is aligned with what is already stated in the series rules.
  • Given however the complexity of penalty mechanics by iRacing AI we provide additional context and directions for serving a penalty as follows.

To Serve a Penalty

A. Follow the penalty instructions iRacing tells you to do.

  • If iRacing tells you to “Drive-Through”, do exactly that.
  • If iRacing tells you to “Stop and Go” for x amount of time, do exactly that.
  • If you receive a Drive-Through penalty but decide to stop at your pit box, iRacing AI will NOT clear your penalty and it will force you to actually “drive-through” without stopping next time.
  • If you’re using Crew Chief, when in doubt – do what iRacing tells you to do, not Crew Chief.

B. DO NOT SERVICE YOUR CAR UNDER BLACK FLAG PENALTY.

  • By “NO SERVICE” we mean: “Uncheck” all the boxes in the service/fuel black box (F4 & F5 keys). Make sure you do not take tires in the “tires” black box. Taking service of any kind will add time to your penalty.
  • A driver may not receive service when the driver is serving a black flag penalty (all services unchecked meaning… fuel, tires, the windshield tear-off, and fast repair… are unchecked at the pit box).
  • Doing so may subject the driver to additional in-race or post-race penalties.
  • iRacing AI will assess additional time specific to the track and race conditions if a service is taken while serving a black flag penalty. This additional time is the same regardless of whether you’re just taking a tear-off or a full pitstop.
  • Example 1: You receive a 30-second penalty but as you enter the pits, the windshield tear-off box is checked – you’ll be held for an additional time (as assessed by iRacing AI). If that additional time was 50 seconds, you’d serve a total of 80 seconds.
  • Example 2: You receive a 30-second penalty but as you enter the pits, Crew Chief automatically activates your auto-refuel as you enter the pits. Unless you uncheck the fuel before you stop, you will refuel and iRacing AI will assess an additional time penalty against you.
  • Example 3: You receive a drive-through penalty, but decide to stop in your pit, and take fuel. iRacing AI will not clear the drive-through penalty because you’ve stopped and serviced your car. You will need to drive through the pits again to clear your drive-through penalty.
  • C. Do not assume that Race Control has any idea of the reason for your penalty if it was applied by the iRacing AI system. Race Control will see a penalty is applied by iRacing, but will not know the reason for it until after the race has completed.

Additional Reference

In the 2020 Season 3 update, iRacing added the italicized section below on complying with penalties.

  • Drive-Through Penalties are now in place!
  • The Incident Count Black Flag penalty has been changed from a Stop-and-Go to a Drive Through penalty.
  • Drive-Through Penalties may also be applied manually by an Admin.
  • The admin command to issue a Drive-Through Penalty is done via the usual, “!black” command, but is appended with a “D” parameter.
  • For example: “!black D”
  • To clear a Drive-Through Penalty, a driver must enter the pit lane under green track conditions with no other black flags, and pass through the whole pit lane without stopping in their pit stall.
  • This action will clear the Drive-Through Penalty Black Flag as the driver passes the pit exit.
  • A Drive-Through Penalty cannot be cleared if entering the pits while the track is under Caution, but if a Caution comes out while a driver is already in the pitlane trying to serve a Drive-Through Penalty, the penalty will still clear successfully.
  • Getting a pit speed or other pit lane penalty while serving a Drive-Through Penalty will still clear the Drive-Through Penalty, but now the driver will have the extra penalties that were incurred during the process and will need to clear those separately.
  • If the driver has other penalties in addition to a Drive-Through Penalty, the Drive-Through Penalty cannot be cleared via driving through the pitlane.
  • It adds to the other penalties with the usual 15-second increase per combined penalty and must now be cleared via the usual stop and hold.
  • The iRacing reference for all other admin commands is here.

Incident Race Reports

  • Race Stewards will be monitoring the event and may determine a POST-RACE Incident Race Report (IRR) is necessary for any IN-RACE penalties.
  • Drivers are encouraged to submit a POST-RACE IRR for review.
  • Race Stewards will not initiate a POST-RACE Incident Race Report or re-review an incident that has been addressed IN-RACE by the Race Stewards.
  • Drivers cannot submit an Incident Race Report unless they are involved in the incident. In other words, observing an incident is not grounds for submitting an incident.
  • The Incident Race Report must be completed in full or they will be discarded.
  • The Incident Race Report is the most appropriate way to address incidents between drivers.
  • Penalties may be in addition to any IN-RACE penalties assigned by Race Stewards.
  • In the case of any penalties applied to a driver post-race, a time penalty will be assessed that is roughly equivalent to the cumulative time spent had the driver served the penalty during the race.
  • For example, the time it takes a driver to enter and exit the pits at pit speed + full duration of the stop for the penalty.
  • This is an attempt to take into account the difference between durations transiting pit lanes. Spa, for instance, takes much longer to transit than Lime Rock.
  • Use only the “Current Time” shown in the iRacing tools below. IRRs submitted not using the Current Time will be rejected from reviewing.
  • Drivers have 24 hours from the time the replay has been posted to submit an Incident Race Report (IRR).

Use only the “Current Time” shown in the iRacing tools below. IRRs submitted not using the Current Time will be rejected from reviewing.

Official Results

  • Once the event has concluded on Friday nights, the server replay is downloaded then uploaded to the archive and made available for drivers to review.
  • At the deadline time for submission, IRRs are sent to the review group for processing. The IRR review group is comprised of multiple people who are not affiliated with PCA Sim Racing in any way but are long-time knowledgable racers and enthusiasts. No drivers or members of the PCA Sim Racing Steering Committee are in the review group.
  • The Chairperson for PCA Sim Racing acts in a conduit role for the IRR process and is not a voting member of the IRR review group.
  • That is why there is a delay before posting official points.

Championships

Driver Championship

  • Results from 4 of 4 races will be used to determine the Zone Group Challenge podium for each class.
  • The podium for each class in the Zone Group Challenge advances to the Zone Group Challenge Championship.

Ties & Tie-breakers

  • Championship points finishing positions are defined in the FIRST Sporting Code, Section 5.7, Individual and Team Championships, 5.7.2 Championship Points Tie Breaker
  • Read iRacing’s FIRST Sporting Code. A link is also available in iRacing under the “Help” > “Sporting Code”.

Awards

An official trophy will be provided to the winner in each of the four Zone Group Challenge classes.

Scoring

  • Results are unofficial until they are posted on this page.
  • Official results will typically be available by Wednesday afternoon following the Friday event but may be available earlier.

Driver Championship

Points within each class will be awarded according to the single points matrix below, i.e., points paid for positions 1 through 60.

Pos. Pts. Pos. Pts. Pos. Pts. Pos. Pts.
1 320 16 230 31 140 46 50
2 314 17 224 32 134 47 44
3 308 18 218 33 128 48 38
4 302 19 212 34 122 49 32
5 296 20 206 35 116 50 26
6 290 21 200 36 110 51 20
7 284 22 194 37 104 52 14
8 278 23 188 38 98 53 8
9 272 24 182 39 92 54 7
10 266 25 176 40 86 55 6
11 260 26 170 41 80 56 5
12 254 27 164 42 74 57 4
13 248 28 158 43 68 58 3
14 242 29 152 44 62 59 2
15 236 30 146 45 56 60 > 1

Approval for Competition

The PCA Sim Racing Steering Committee reserves the right to require any driver — new or already registered — to complete at least one 1:1 eDE or an eDE Monday Madness session, and be approved for competition with a PCA Sim Racing eDE Instructor before participating in an event.

Driver Conduct

PCA Sim Racing is dedicated to Sportsmanship and Comradery.

Verbal abuse, including the use of profanity and calling out others in a derogatory manner (passively or actively), is inconsistent with these concepts. Verbal abuse, whether of a fellow driver or a Race Steward, will not be tolerated.

Profanity is unacceptable and inconsistent with Sportsmanship and Comradery.

Neither is acceptable.

The first offense may/will result in a warning.

The second offense may/will result in disqualification from the race in which the verbal abuse occurs.

The third offense may/will result in disqualification from the league.

Any use of profanity may result in disqualification from the league – even on a first instance.