Director's Note

Apparently the policeman that was managing the turnaround thought the turnaround was farther down the road, so he took the cones off the turnaround point after the first 4 runners went past. The next 30-35 runners ran past the turnaround to the traffic control person at the end of the street. Most ran different distances on this segment. When I approached the turnaround in one of my slowest 5K's of my life, I instructed the officer to turn everyone else at the X that was clearly marked on the road. From this point on everyone apparently ran the correct distance.

I spent 5 hours (til 3am) studying the data and making adjustments. What I found was that almost everyone slowed down as the race progressed. It was a very warm night and we all suffered. I looked at all the first mile and last mile splits of all runners who showed a 2nd mile split of being way too slow. I averaged the first mile time and the 3rd mile time and used that time as the predicted 2nd mile time.

For instance, if your first mile was 6:00, and your second mile showed 7:30 (ran too far) and your third mile split was 7:00, I hypothesized that you actually slowed down about 30 seconds per mile (6:00, 6:30, and 7:00). So I manually adjusted your second mile cumulative time, your third mile cumulative time and your raw finish time by 1:00 to give you a time 1:00 faster than what you ran, but more accurate for the 5K.

This will be the time that I plug into the QUAD results. I'm not going to spend much more time compiling and editing the times. It is what it is. It was a lot of work, and I did the best I could to make it fair. I apologize for the volunteer's error.

Fortunately, it didn't rain or storm and no one got hurt.

See you at the DAM RACE on July 27th

S. Mark Courtney