Quote from gaston_ar44 :

Session of Incident (Official Sessions for Round 5: Qualifying 1, Qualifying 2, Race): Race
Lap AND MPR timecode of incident (or session time or UTC Time of Day): lap 271, timecode 7:53:40
Car(s) involved: 69 & 53
Location of Incident (Track Map Here): Turn 8
Brief Description of Incident: #53 cant hold inside line

Contact caused the 69 to go into the gravel, 53 was taking normal line. The contact caused 53 to stay on the outside line to maintain control.

Racing Incident - No further action

Quote from gaston_ar44 :

Session of Incident (Official Sessions for Round 5: Qualifying 1, Qualifying 2, Race): Race
Lap AND MPR timecode of incident (or session time or UTC Time of Day): My lap 204, timecode 5:55:30
Car(s) involved: 69 & 01
Location of Incident (Track Map Here): Turn 9
Brief Description of Incident: #01 dive bomb

Car #01 - Stop & Go Penalty - Causing an avoidable incident with blue flags

GT1 Q2 complete, GT2 drivers may now join.

no/71/jonathon.provost

Last edited by dekojester, Sun 1 Dec 2013, 18:38. Reason : informed via TS prior to race that not attending

#71

71/jonathon.provost/Jonathon Provost/UK/Advantage Motorsport

Initiated by the stewards:

Session of Incident (Official Sessions for Round 2: Qualifying 1, Qualifying 2, Race): Race
Lap AND MPR timecode of incident (or session time or UTC Time of Day): Beginning Car 25's Lap 273, 5:31:15 into the race thru Car 25's Lap 276, 5:35:00 into race
Car(s) involved: 25, 52, 88
Location of Incident (Track Map Here): Starting on Rallycross BackStraight and lasting through Turns 6 & 7 / Chicane, each lap in the range
Brief Description of Incident: GT1 Car 25 is lingering around GT2 Car 52 which is in a battle with GT2 Car 88. At end of time range, Cars 52 and 88 have an incident.

Last edited by dekojester, Sun 24 Nov 2013, 21:57. Reason : added times for reference

Car 64 - Drive Through - Overtaking under full course yellow - 2nd offence

Quote from wody21 :

Session of Incident : Race
Lap AND MPR timecode of incident (or session time or UTC Time of Day): Lap 81, MPR timecode ~ 1h 43m
Car(s) involved: 55, 69
Location of Incident: Turn 7
Brief Description of Incident: Car #69 crashes into us (#55) and causing us a spin out and position lost.

Car 69 - Drive Through - Causing avoidable incident

Quote from Black the Ripper :

Session of Incident : Race
Lap AND MPR timecode of incident (or session time or UTC Time of Day): lap 33? time 42 minutes in race
Car(s) involved: 73, 64
Location of Incident: back straight
Brief Description of Incident: Car 64 overtook us (73) during safety car

Car #64 Drive Through - Overtaking during Full Course Yellow

Quote from Jni :

Session of Incident : Race
Lap AND MPR timecode of incident (or session time or UTC Time of Day): Lap 38, MPR timecode 49.00.00
Car(s) involved: 55, 88
Location of Incident: Turn 5
Brief Description of Incident: Car 55 dives into turn 5 and crashes into car 88. Car 88 lost 5 positions in that incident.

Car #55 - Drive Through - Causing avoidable incident

Car #04 - Drive Through - Causing an avoidable incident

Quote from Black the Ripper :

Session of Incident : Race
Lap AND MPR timecode of incident : 48 (1h21m)
Car(s) involved: 03
Location of Incident (Track Map Here): Turn 5
Due to too late breaking car 03 spins out car 73, car 03 had enough space on the inside line.

General remark or question.
Do GT2 drivers have to slam the breaks when they see a blue flag, because most GT1 drivers force their way trough. I already read a comment in IRC saying "blue flag means prepare for impact". It certainly felt like that today.

No action taken - Unofficial message by IRC to team

Quote from L3VO :

Session of Incident : Race
Lap AND MPR timecode of incident : 55
Car(s) involved: 19
Location of Incident (Track Map Here): Turn 1-2
19 returns to the track recklessly and causes #05 to goes off the track.

Warning Car #19 - Re-entry to racing surface

Quote from Bmxtwins :

Session of Incident : Race
Lap AND MPR timecode of incident (or session time or UTC Time of Day): 21 minutes
Car(s) involved: 49, 72
Location of Incident (Track Map Here): Turn 1
Brief Description of Incident: Car 49 is overtaking car 72 but understeers into 72 and spins it.

Racing Incident - No action taken - MARKED FOR POST-RACE AUDIT

Quote from Bmxtwins :

Session of Incident : Race
Lap AND MPR timecode of incident (or session time or UTC Time of Day): 41 minutes
Car(s) involved: 08, 72
Location of Incident (Track Map Here): Turn 14
Brief Description of Incident: car 72 is being lapped by car 08, but is taken off by car 08's lag. Car 08 should've been aware of lag...

Racing Incident - No action taken

we can't investigate all contact warnings. too many.

Quote from Bmxtwins :

So was the 51's contact when he illegally rejoined into the racing line and slammed into my door coming into the double 90 degree right handers in the first sector. Admins didn't do jack.

We don't have 30 eyes. We can see anything. If your really bothered then you will always have the right to protest it post race. Which seems like you express that right often.

It was contact and it was avoidable

What about FE. Awesome environment.

Hello everyone,

On the British Touring Car Championship weekend at Oulton Park I will be running a Aeon Simulator with iRacing.
The simulator will run on the 8th and 9th of June 2013.

You can find us at the Advantage-Motorsport store near the scrutiny bay. See map here

We will be running the D Series Aeon Sim with triples. Oulton Park will be the track but we are currently unsure of the car at the moment. (Kia maybe) Any suggestions? bearing in mind that there will be some people who cant drive.

We will hopefully getting BTCC and support race driver to do a shoot out. So come down and see where you stand with the professionals.

Thanks Guys

First and Surname: Jonathon Provost
LFSW Username: jonathon.provost
Team: SGP•Team
Carnumber: 72
Nationality: British
Can confirm to attend to event (Yes/No): Yes (hopefully)

Ye basically but for teams to view there own drivers like the simtools one. Not sure if that makes any sense.

Thats the default value on the tracker if it doesn't know what to do

Quote from Hahmo :

Session of Incident: Race
MPR Timecode -OR- UTC Time of Incident: 24:25:.54
Lap and Location of Incident: 15, Sector 3
Your Car Number: 02
Other Car(s) Involved: 10
Brief Description of Incident: Maddee goes to the outside entering the braking zone and turns in late leaving plenty of room. #10 outbrakes himself and Maddee has to take evasive action (eventually spinning himself) to avoid contact with 10 who is suddenly 3 car widths away from the apex.

Will be reviewed by another admin after the race

Quote from Eclipsed :

Session of Incident: Race
MPR Timecode -OR- UTC Time of Incident: 3h19m
Lap and Location of Incident: 123 (of car 66) pitlane exit at speed limit ending point
Your Car Number: 66
Other Car(s) Involved: 59
Brief Description of Incident: 59 didn't do anything to avoid first contact while turning off speed limiter,which resulted in retirement of 66

#59 Stop & Go - Causing Avoidable Incident
#59 Continues to accelerate, trying to go 2 wide out of pit exit.

Quote from Eclipsed :

Session of Incident: Race
MPR Timecode -OR- UTC Time of Incident: 1h52:40
Lap and Location of Incident: 71 (of car 66) CS-7
Your Car Number: 66
Other Car(s) Involved: 67
Brief Description of Incident: After incident caused by my mistake on lap 70,67 takes revenge and intentionally hits and spins 66

Car 67 Hits the gas coming out of turn 7, contact with #67 causes #67 to spin. Car #67 Drive Through Penalty - Causing an Avoidable Incident

Quote from vipex123 :

Session of Incident: Race
MPR Timecode -OR- UTC Time of Incident: 24:25:.54
Lap and Location of Incident: 15, Sector 3
Your Car Number: 02
Other Car(s) Involved: 10
Brief Description of Incident: Maddee goes to the outside entering the braking zone and turns in late leaving plenty of room. #10 outbrakes himself and Maddee has to take evasive action (eventually spinning himself) to avoid contact with 10 who is suddenly 3 car widths away from the apex.

02 car began to spin before contact, Racing Incident

Quote from vipex123 :

Session of Incident: Race
MPR Timecode -OR- UTC Time of Incident: 48:54:00
Lap and Location of Incident: End of lap 31 start of lap 32.
Your Car Number: 02
Other Car(s) Involved: 10
Brief Description of Incident: 10 again does not leave sufficient room and turns left into Maddee when he is fully alongside, causing a collision that sends Maddee into the wall and causing substantial enough damage to warrant a repair in the pitstop.

Incident partly down to lag, Racing Incident

PM AMENDMENT Take the LAST 3 characters off the password, sorry for this