I had about 3 hours to kill before going to work, so I went for the around-the-lake loop I previously rode on September 18th, and the first time September 11th. I was going for speed this time again, primarily because I didn't want to get to work late. I finished at 2:23:21 (device stops when going less than 3mph -- at a few stops signs and lights; I didn't stop to take a break as on the 18th), translating into 16.5mph, the total distance being 39.4 mi. On September 18th I clocked in at 2:27:12, but I think my GPS started working about 1-2 minutes earlier because the signal caught on earlier. So I think I only finished about 2:30 minutes ahead of last week. That's pretty amazing for over 2 hours and it also means that I probably can't finish too much faster -- say below 2:15 -- for that run. I really think I can get 20mph for a 40-50 mile ride, but on a road with little traffic, pedestrians, and stop signs/lights. Even though my device stops below 3mph, I often have to slow down considerably before I reach a light or when I see pedestrains or slower bike traffic. That's OK, no big deal at all :-), I like that ride a lot, but I do want to find a route where there's little traffic and where I can get to 20mph. At this point the Baindbridge Island loop is the best candidate...

I'm having trouble with extrapolating GPS data again; to be posted later.

Here's a low-resolution sattelite picture - best for large areas and not very accurate for smaller ones (thus it appears as if I biked on water :-) - with the estimated slope. Unfortunately the GPS stopped reading signals when I was going up the steepest slope right after Lap 1 on Juanita Dr. on the east side of Lake Washington. I think parts of it may have been 6%+. Also,



Total: 39.4 mi Bike; 1482 calories; 140 lb.