As an Amazon Associate I earn from qualifying purchases. Some links on this page may earn RealIRacing a commission at no extra cost to you. Gear I personally race on is called out as such; other picks are researched recommendations.

Your safety rating in iRacing is built on one currency: incident points. They're the invisible cost of every spin, wall-kiss, contact, or corner-cutting lap. But most drivers don't really understand what causes incidents; they just see the numbers tick up after a lap and feel frustrated. Whether you race on a MOZA R9 or any other wheel, it's easy to spend months chasing a higher SR only to realize you were penalizing yourself for things that weren't actually your fault, and missing penalties you should have received because you didn't understand the system. This post breaks down how incident points actually work and what driving mistakes, or rules violations, actually trigger them.

The Two Categories of Incident Points

iRacing groups incident points into two broad categories: contact with other drivers and track limits violations. They're scored differently, penalize different behaviors, and understanding which is which is the first step toward building a durable safety rating.

Contact Incidents

When your car hits another driver's car, iRacing assigns incident points based on the severity and fault determination. A light tap in the run-off zone might be 1–2 points. A hard hit under braking is often 4–8 points. A spinout-inducing rear-end at the apex can be 8–15 points. The system assigns fault: if you make the unsafe move, you receive most or all of the points. If contact is mutual or ambiguous, points can split.

Here's the part most drivers miss: contact only triggers points if the sim detects actual physical collision. Bumper-to-bumper at a restart, both cars touching a wall, or a light graze on exit; all of these register. But driving defensively by moving offline to hold position, or simply being close to another car without touching, does not. Don't brake way too early thinking proximity alone is penalized; it isn't.

Track Limits Violations

Track limits are enforced by the sim's boundary detection. In most series, cutting a corner (all four wheels off track), running wide at exit, or even just touching the grass triggers incident points, usually 1–2 points per violation. Some tracks have stricter zones than others. Road America's Carousel, for example, is tighter than Watkins Glen's wider run-off areas.

What surprises newer drivers: the penalty applies instantly to that lap, regardless of whether you gained time or not. If you brush the rumble strip and one wheel goes slightly off, you get an incident point. If you clip the grass on a slow corner and lose 0.3 seconds, you still get the incident point. The system is binary: wheels off, points added, not outcome-based.

What Actually Causes Incidents: The Real Scenarios

The Safety Rating Math: How Points Convert to SR Loss

iRacing's safety rating is a running average. You don't lose a fixed number of SR points per incident; instead, each session your SR is recalculated based on your last ~10 complete sessions. One bad race can hurt, but a single incident won't tank you. However, repeated incidents compound quickly.

The conversion is roughly: ~4 incident points per race ≈ -0.1 to -0.2 SR (this varies by your current rating and the weighting system, which iRacing adjusts seasonally). A 10-point incident in a single race is serious; that's almost -0.5 SR depending on context. But if your last 10 sessions are clean, one bad lap won't bury you.

This is why consistency matters more than perfection. A driver with 3-point incidents across 10 races will have a higher SR than a driver with one 20-point crash, even if their raw incident totals are the same.

Track Your Incidents

Track your incident total per session, not just your final SR. If you see yourself hitting 8+ points in a race, you're likely looking at -0.1 to -0.2 SR that week. Clean sessions (0–2 points) are how you rebuild.

How to Avoid Incidents: The Practical Checklist

Reducing incidents is about being intentional. Here's a practical checklist for racing in high-traffic splits:

  1. Learn the track limits before racing. In practice, deliberately hit the boundary so you know where the penalty zone is. On some ovals, the white line is in-bounds; on others, it's out.
  2. Use smooth throttle and brake inputs. Good pedal modulation makes it much easier to avoid lockups and off-track incidents.
  3. Plan your overtakes 2–3 corners ahead. A defensive move you see coming is easier to avoid than a reactive block. If someone is faster, let them by in a safe zone (high-speed, wide track).
  4. Respect traffic at rolling starts. The first lap is chaotic. Stay offline, don't be aggressive, and wait until lap 2 to settle into racing.
  5. Know your car's limit. Strong force feedback, such as from a ~9 N·m wheelbase, can help you feel the grip limit. Don't exceed it just because the car feels planted in that lap.

Common Misconceptions About Incidents

"Incident points reset each season." False. Your safety rating carries over. A new season starts fresh only if you choose to create a new account. Your SR from last season influences your placement in this season's races, so a low SR puts you in slower splits initially.

"Off-track is only penalized if I gain time." False. All four wheels off track = incident point, regardless of time gain or loss. Even if you lose 0.5 seconds, the point still applies.

"Light contact doesn't count as an incident." False. Any collision, no matter how light, is detected and penalized. A gentle nudge in the slipstream still costs you.

"My SR will bounce back immediately with one clean race." Partially true. One clean race helps, but it's weighted against your last ~10. It takes several consecutive clean sessions to rebuild significantly.

Reading Your Incident Report After a Race

After every race, iRacing shows you an incident summary: total points, when they occurred, and brief descriptions. Use this to identify patterns. If three of your five incidents happened in the same corner, that is a setup or technique problem, not bad luck. If all your incidents are contact, you're too aggressive. If all are off-track, you're overdriving the grip envelope.

On RealIRacing, I recommend reviewing your telemetry alongside your incident report. Where did your inputs become unstable? Did you lock the brakes? Did throttle application cause a slide? Data doesn't lie, and it helps you avoid repeat mistakes.

Safety Rating vs. iRating: They're Not the Same

One final clarity: safety rating (SR) and iRating (strength, skill) are separate. You can be a 3000+ iRating driver with a 3.5 SR if you drive aggressively. You can be a 1200 iRating driver with a 4.8 SR if you're smooth and patient. Both matter for race selection: some series have iRating caps, others have SR minimums. You need both to be a complete driver.

Protecting your SR is not about being slow; it is about being predictable. Clean, smooth inputs can help you improve your iRating while maintaining a strong SR, because you're not wasting energy fighting the car or battling other drivers.

The gear in this guide
PickWhy it made the listTested?
MOZA R9 Direct Drive Wheelbase9 N·m direct drive, the base bolted to my rig right nowRaced on
MOZA CRP2 Load Cell Pedalsload-cell brake, managed in the same Pit House softwareResearched pick

As an Amazon Associate I earn from qualifying purchases. Some links are affiliate links; I may earn a commission at no cost to you.

From the RealiRacing shop

Before your next session, free up your rig. NWM PitStop is the clean-up and stream-priority script set we run before every session; our own product, not a third-party pick. See NWM PitStop →

Watch it, don't just read about it

I stream and upload iRacing races on my MOZA R9 rig: real laps, real force feedback, real mistakes. See the gear from this guide working before you spend a cent.

▶ Subscribe on YouTube

Skip the trial and error

The force-feedback, pedal and baseline settings I actually race, written up as setup packs for MOZA, iRacing, ACC and Le Mans Ultimate. The opening section of each pack is free to read.

See the setup packs →

Free FFB tuning checklist

The order I tune force feedback in, from rig to wheelbase software to iRacing, plus the clipping check. Enter your email and the checklist opens right here. No spam, unsubscribe anytime.

See the privacy notice.

FAQ

Do incident points from practice sessions count toward my safety rating?

(FAQ) No. Only incidents from qualifying and the race itself are counted. You can spin and hit walls all day in practice without affecting your SR. This is why practice is the time to learn exactly where the track limits are without penalty.

If I get hit and spin into the wall, do I get points for both the contact and the off-track?

Yes. If another driver hits you and causes you to spin and hit a wall, you'll typically get incident points for both the wall contact and potentially the off-track. The other driver gets incident points for the initial contact (and fault). It's not fair in the moment, but that is how the system works; therefore, defensive positioning (staying away from the chaos) is as important as speed.

How many incident points do I need before I drop a safety rating division?

There's no hard threshold. iRacing recalculates your SR continuously based on your last ~10 complete sessions. Roughly, ~4 incident points per race reduces your SR by about -0.1 to -0.2 depending on your current rating. But one race with 15 points won't instantly drop you from 4.5 to 4.0; it's a slower erosion based on the rolling average.

Can I get incident points for aggressive but clean driving?

No, not unless there's actual contact or off-track. Defensive positioning, brake-checking (though unsportsmanlike), blocking moves, and aggressive lines are not penalized unless they result in contact. The system is binary: contact detected or off-track detected equals incident points. Reckless driving without those consequences is unpunished by the incident system.