I began taking pictures on I-95 northbound, after I had missed my exit for VA 10 (exit 61), where I had planned to hit I-64 further east via I-295. Instead, I just kept going towards Richmond.
I hope you like overhead signs. This entry has a lot of them.
Broken light fixture.
Approaching downtown Richmond.
Bleh.
On the James River Bridge.
The world's tiniest patch. It covers an 11, the pre-1992 exit number for I-64.
...I missed the exit for I-64, so I had to get off at the next one (US 1/301) and turn around, something that requires making several (well-posted) turns in downtown Richmond.
Now on I-64, heading for Hampton Roads.
For the most part, I did a pretty good job of not getting my car in the pictures, but this was an exception.
I-64 meets I-295 at exit 200. If you're waiting to see actual Norfolk, you're in the wrong blog entry.
US 60 is parallel to I-64 here, but the C/D road on I-295 south takes you there.
Now in New Kent County. I-64 is more rural here, but there was still lots of traffic.
Exit 211 is for VA 106.
I tried to get this combination I-64/VA 33 reassurance assembly after several exits, but kept waiting too long. This was the only one that actually got them.
Now in James City County, at the second of two consecutive exits I-64 has for VA 30.
We're in the Williamsburg area.
The eastern interchange with VA 199 actually has the road's names.
I like the way this photo turned out, despite the VA 199 overhead being cut off, because you can see I-64's undulation ahead.
Yellow-out is what happens when you need to make the arrow a different direction.
There's no greenout here. Just excess space.
They should have used some of the extra space from the previous overhead for this one. I-64 eastbound does not have a direct exit to VA 238, but it has an onramp from it, and I-64 westbound does have an offramp for it.
Now in the deceptively long City of Newport News, where traffic starts to get thicker.
As usual, my camera didn't pick up all the numbers on the VMS here. I-64 said 47 minutes, while I-664 said 68. Of course it's going to take longer to reach the oceanfront when you're going parallel to it on 664 as opposed to relatively closer to it via 664, but 664 is a much, much, much smoother ride and is less often congested than 64.
The times here for VA 168 (which is where I was headed) said 67 minutes via I-64 and 63 via I-664. Both were congested. My own fault for going this way in rush hour traffic, but if I took the World's Most Depressing Stretch of US 460 one more time...
Especially huge overhead.
There's 664. Upon turning onto it, I stared directly into the sun...
...until I hit the traffic jam. There was a stalled vehicle in the left lane of the Monitor-Merrimac Memorial Bridge-Tunnel, so traffic had to squeeze into the right lane.
The rarely-seen Y intersection advisory sign on the offramp.
I wish. It was more like 60 feet per minute. My clutch was sure enjoying that. [/sarcasm]
Vehicles are already stopped, regardless of whether or not they have hazmats.
Merging traffic didn't help.
I was hoping to clinch a route or two while I was down here. Nope.
The yellows were flashing. And look, a red light on an interstate.
The stalled vehicle is being attended to in the background.
Hooray, I can go again. Down into the tunnel I went.
Now out of the tunnel.
On the south side of the river now.
After that, the combination of bad drivers and darkness made me unable to get anymore pictures, but I retrieved the wheels and got home with no incidents. I-64 westbound has a bad bottleneck at exit 255, where it drops from 4 lanes to 2 and traffic enters at the same time, but other than that there were no other delays. The MMMBT is even nicer at night.
No comments:
Post a Comment