Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[plain]

The easy solution would be just make VA 33 part of US 33.

That would be the easy solution, but VDOT never does things the easy way...

and even that's an understatement lol just like the whole US/VA 360 thing

[Takumi]

Digging this thread up with a photo from the Richmond Times-Dispatch from January 1952. This is West Broad and Lombardy, but doesn’t say which direction. Note the US 33 shield included.

[WillWeaverRVA]

Digging this thread up with a photo from the Richmond Times-Dispatch from January 1952. This is West Broad and Lombardy, but doesn’t say which direction. Note the US 33 shield included.

Looks like eastbound.

[The Ghostbuster]

I think VA 33 should have been US 33 from the get-go. I know VA 33 is an east-west route, but so is US 33 (more or less, with it being diagonal in a northwest-southeast trajectory). True, there is a VA 211 off the end of US 211, and a VA 360 along US 360’s old alignment. VA 311 doesn’t count since it was designated after US 311 became part of US 220.

[Mapmikey]

I think VA 33 should have been US 33 from the get-go. I know VA 33 is an east-west route, but so is US 33 (more or less, with it being diagonal in a northwest-southeast trajectory). True, there is a VA 211 off the end of US 211, and a VA 360 along US 360’s old alignment. VA 311 doesn’t count since it was designated after US 311 became part of US 220.

VA 311 absolutely existed while US 311 ended in Roanoke. Otherwise VA 311 would’ve been numbered something else.

Virginia has also had as extensions of US routes:
VA 13
VA 17
VA 121
VA 158
VA 258
VA 301
VA 501
VA 522

Plus there was a US/VA 29 setup similar to the current 360 setup, between Culpeper and Warrenton.