Virginia

[Plutonic Panda]

I love speeding probably more than anybody on this forum. I can't tell you how many times I've been cited for going more than 100 miles an hour, but I'm not saying it's right and I'm not advocating for people should abide by the speed limit. But that being said that makes no sense that there's a threshold of 12 miles an hour over the limit where they can't pull you over for driving below that. The speed limit is the speed limit. There's officer discretion.

I do remember something about their possibly being a 1 to 2 mile an hour discrepancy due to calibration issues with car speedometers. I'll notice sometimes when I'm driving and I see one of those digital "your speed xxx" but it's usually 5 to 8 miles an hour off of what my speedometer says, even when I have my digital speedometer on my dash.

Why even have speed limits if it's illegal to pull anybody over for going 11 miles an hour over the limit? That makes no sense. The law needs to be the law and it needs to be enforced. Some things there should be officer discretion for speed limits are one of them.

[Mapmikey]

B.2.C of the law here says tickets for speed cameras are issued at 10 mph over the limit - https://law.lis.virginia.gov/vacode/title46.2/chapter8/section46.2-882.1/

I spot checked other speed related ordinances and found no exceedence criteria for a cop pulling over a vehicle- https://law.lis.virginia.gov/vacode/title46.2/chapter8/

[Beltway]

B.2.C of the law here says tickets for speed cameras are issued at 10 mph over the limit - https://law.lis.virginia.gov/vacode/title46.2/chapter8/section46.2-882.1/
I spot checked other speed related ordinances and found no exceedence criteria for a cop pulling over a vehicle- https://law.lis.virginia.gov/vacode/title46.2/chapter8/

On police stops, there is no statutory exceedance requirement. Officers enforce based on clear, defensible violations, not a mandated number. Operational reality -- on rural Interstates, officers routinely ignore 80–82 mph in a 70 when the driver is stable, predictable, and not an outlier.

Review process -- every camera citation is reviewed by an officer before issuance; it's not an automated rubber‑stamp. In theory they could apply officer's discretion there as well, like use an exceedance of 12 or 15 mph before he approves it.

[FLAVORTOWN]

I submitted a request to have it fixed.

Good news, the 388 sign has been fixed.

Bad news, there is now a US-7 shield at Seven Corners. We've teleported to New England 

On a side note, VDOT has stopped using Clearview on LGS too. Only BGSes going forward. Rejoice! 

Also, why bother even signing 338 when its completely unsigned on the actual road? 

[Mapmikey]

I submitted a request to have it fixed.

Good news, the 388 sign has been fixed.

Bad news, there is now a US-7 shield at Seven Corners. We've teleported to New England 

On a side note, VDOT has stopped using Clearview on LGS too. Only BGSes going forward. Rejoice! 

Also, why bother even signing 338 when its completely unsigned on the actual road? 

That's the only location VDOT has jurisdiction to post a 338 marker. The rest of VA 338 is in the City of Falls Church.

[WillWeaverRVA]

I submitted a request to have it fixed.

Good news, the 388 sign has been fixed.

Bad news, there is now a US-7 shield at Seven Corners. We've teleported to New England 

On a side note, VDOT has stopped using Clearview on LGS too. Only BGSes going forward. Rejoice! 

Also, why bother even signing 338 when its completely unsigned on the actual road? 

What in the world, where's the US 7 shield at?

[FLAVORTOWN]

What in the world, where's the US 7 shield at?

[WillWeaverRVA]

What in the world, where's the US 7 shield at?

Holy crap, all of these new signs look awful. Submitted another request.

[Dirt Roads]

What in the world, where's the US 7 shield at?

Holy crap, all of these new signs look awful. Submitted another request.

Nah, it's just a US-501 sign in a 2dUS shield with the "1" whited out. 

[Thing 342]

Northern Virginia district has really been putting out some crap signage recently: https://maps.app.goo.gl/vdedqTE1ebuBbKKQ6

There are several other miscolored signs like this along I-95 through PWC and Fairfax County.

[WillWeaverRVA]

Northern Virginia district has really been putting out some crap signage recently: https://maps.app.goo.gl/vdedqTE1ebuBbKKQ6

There are several other miscolored signs like this along I-95 through PWC and Fairfax County.

Yuck!

Makes sense, given the enormous VA 1 shield they have up on Neabsco Mills Road

[Thing 342]

More examples:

• https://maps.app.goo.gl/ZKHt9Ng3sY2UY2DB9, late 2025 install
• https://maps.app.goo.gl/VpuUGvdSW1c1RioXA, 2024 install (many of this kind)

[Takumi]

I'm currently staying in Lexington and they've also got some oddball signs for US 11 (which is actually 11 Business but you'd never know it) and 60.

The 60 here has actually been replaced with one that says "E-W" above it.

I've yet to check on the infamous US 251 shield at the beginning of VA 251.

[1995hoo]

What in the world, where's the US 7 shield at?

On the US-50 sign, the "East" looks like the "st" part has been modified using some sort of sticker, but maybe it's a trick of the light.

[WillWeaverRVA]

On the US-50 sign, the "East" looks like the "st" part has been modified using some sort of sticker, but maybe it's a trick of the light.

You're not wrong, it definitely looks like the ST is a decal.

I'm currently staying in Lexington and they've also got some oddball signs for US 11 (which is actually 11 Business but you'd never know it) and 60.

The 60 here has actually been replaced with one that says "E-W" above it.

I've yet to check on the infamous US 251 shield at the beginning of VA 251.

Interesting to see the E-W trailblazers spreading out of the Staunton District, though this would be a city install.

Northern Virginia district has really been putting out some crap signage recently: https://maps.app.goo.gl/vdedqTE1ebuBbKKQ6

There are several other miscolored signs like this along I-95 through PWC and Fairfax County.

These look like VDOT bought them on Temu.

[Mapmikey]

I'm currently staying in Lexington and they've also got some oddball signs for US 11 (which is actually 11 Business but you'd never know it) and 60.

The 60 here has actually been replaced with one that says "E-W" above it.

I've yet to check on the infamous US 251 shield at the beginning of VA 251.

Be sure to approach from US 11 Bus southbound to see a 2nd US 251 shield.

[Takumi]

I'm currently staying in Lexington and they've also got some oddball signs for US 11 (which is actually 11 Business but you'd never know it) and 60.

The 60 here has actually been replaced with one that says "E-W" above it.

I've yet to check on the infamous US 251 shield at the beginning of VA 251.

Be sure to approach from US 11 Bus southbound to see a 2nd US 251 shield.

I did, and both are still there. Since they're outside city limits, it's on VDOT to fix them. (On US 11 northbound, the postings are correct.) And VA 251 really should be posted east-west.

edit: the one on 11 Business is actually in city limits. They potentially could fix that with a request. However, looking up close at some of their signage downtown, they appear to outsource their sign production to a company based out of Gainesville (not the Florida one).

[ElishaGOtis]

I just wonder why VDOT just downright refuses increasing the speed limit on I-264 between First Colonial and Witchduck Rd (VA 190). This section has a 70 mph design speed and the flow of traffic is consistently faster than the 55-mph speed limit. Practically all other 49 states would post a freeway with similar geometry at 60 or 65 mph. I wonder why does VDOT refuse? I know it was considered back in 2001, but this segment keeps getting skipped over each time there is a speed limit increase in the Hampton Roads area. Can the FHWA step in and order a traffic study?

You could ask

Half the time they won't do anything because nobody asked. All it takes is one!

Source: I requested I-10 in east Texas be increased from 65 and now it's 75.

[plain]

I just wonder why VDOT just downright refuses increasing the speed limit on I-264 between First Colonial and Witchduck Rd (VA 190). This section has a 70 mph design speed and the flow of traffic is consistently faster than the 55-mph speed limit. Practically all other 49 states would post a freeway with similar geometry at 60 or 65 mph. I wonder why does VDOT refuse? I know it was considered back in 2001, but this segment keeps getting skipped over each time there is a speed limit increase in the Hampton Roads area. Can the FHWA step in and order a traffic study?

You could ask

Half the time they won't do anything because nobody asked. All it takes is one!

Source: I requested I-10 in east Texas be increased from 65 and now it's 75.

I'm thinking the number of exits along that stretch of I-264 (most of which involves loop ramps) makes it less than ideal for a higher speed limit to be in place there.

[Pink Jazz]

I just wonder why VDOT just downright refuses increasing the speed limit on I-264 between First Colonial and Witchduck Rd (VA 190). This section has a 70 mph design speed and the flow of traffic is consistently faster than the 55-mph speed limit. Practically all other 49 states would post a freeway with similar geometry at 60 or 65 mph. I wonder why does VDOT refuse? I know it was considered back in 2001, but this segment keeps getting skipped over each time there is a speed limit increase in the Hampton Roads area. Can the FHWA step in and order a traffic study?

You could ask

Half the time they won't do anything because nobody asked. All it takes is one!

Source: I requested I-10 in east Texas be increased from 65 and now it's 75.

I'm thinking the number of exits along that stretch of I-264 (most of which involves loop ramps) makes it less than ideal for a higher speed limit to be in place there.

Still this doesn't change the fact that practically all other 49 states would post a freeway with identical geometry at 60 or 65 mph in full compliance with FHWA guidelines. I hope the FHWA intervenes to order a speed limit increase against the wishes of VDOT, with federal funding taken away from VDOT if VDOT fails to comply.

[Beltway]

I'm thinking the number of exits along that stretch of I-264 (most of which involves loop ramps) makes it less than ideal for a higher speed limit to be in place there.

Still this doesn't change the fact that practically all other 49 states would post a freeway with identical geometry at 60 or 65 mph in full compliance with FHWA guidelines. I hope the FHWA intervenes to order a speed limit increase against the wishes of VDOT.

The comparison to "49 other states" doesn't really hold. I‑264 in Virginia Beach isn't a rural or lightly‑suburban facility -- it's a high‑volume urban corridor with dense interchange spacing, short weaving sections, and continuous loop‑ramp activity.

Plenty of states post similar geometry at 55 mph when the context is urban: the I-495 Capital Beltway, I-695 Baltimore Beltway, I‑476, and long stretches of NJ I‑295 all run 55 under comparable interchange density and traffic load.

Parts of I‑64 in Chesapeake are posted at 60 mph, so VDOT clearly isn't opposed to higher limits on urban/suburban freeways when the operational profile supports it. I‑264's geometry is tighter -- short interchange spacing, multiple loop ramps, and heavy weaving -- which is why it stays at 55.

FHWA guidelines don't require 60–65 mph when the operational environment is urban and interchange spacing is tight. Geometry alone isn't the determinant; weaving demand, ramp frequency, and volume matter just as much.

[Pink Jazz]

I'm thinking the number of exits along that stretch of I-264 (most of which involves loop ramps) makes it less than ideal for a higher speed limit to be in place there.

Still this doesn't change the fact that practically all other 49 states would post a freeway with identical geometry at 60 or 65 mph in full compliance with FHWA guidelines. I hope the FHWA intervenes to order a speed limit increase against the wishes of VDOT.

The comparison to "49 other states" doesn't really hold. I‑264 in Virginia Beach isn't a rural or lightly‑suburban facility -- it's a high‑volume urban corridor with dense interchange spacing, short weaving sections, and continuous loop‑ramp activity.

Plenty of states post similar geometry at 55 mph when the context is urban: the I-495 Capital Beltway, I-695 Baltimore Beltway, I‑476, and long stretches of NJ I‑295 all run 55 under comparable interchange density and traffic load.

Parts of I‑64 in Chesapeake are posted at 60 mph, so VDOT clearly isn't opposed to higher limits on urban/suburban freeways when the operational profile supports it. I‑264's geometry is tighter -- short interchange spacing, multiple loop ramps, and heavy weaving -- which is why it stays at 55.

FHWA guidelines don't require 60–65 mph when the operational environment is urban and interchange spacing is tight. Geometry alone isn't the determinant; weaving demand, ramp frequency, and volume matter just as much.

I know most southern and western states would post them at 60 or 65 mph. I-264 in Virgina Beach has a 70 mph design speed and can safely handle 60 mph without any issues.

[Beltway]

I'm thinking the number of exits along that stretch of I-264 (most of which involves loop ramps) makes it less than ideal for a higher speed limit to be in place there.

Still this doesn't change the fact that practically all other 49 states would post a freeway with identical geometry at 60 or 65 mph in full compliance with FHWA guidelines. I hope the FHWA intervenes to order a speed limit increase against the wishes of VDOT.

The comparison to "49 other states" doesn't really hold. I‑264 in Virginia Beach isn't a rural or lightly‑suburban facility -- it's a high‑volume urban corridor with dense interchange spacing, short weaving sections, and continuous loop‑ramp activity.

Plenty of states post similar geometry at 55 mph when the context is urban: the I-495 Capital Beltway, I-695 Baltimore Beltway, I‑476, and long stretches of NJ I‑295 all run 55 under comparable interchange density and traffic load.

Parts of I‑64 in Chesapeake are posted at 60 mph, so VDOT clearly isn't opposed to higher limits on urban/suburban freeways when the operational profile supports it. I‑264's geometry is tighter -- short interchange spacing, multiple loop ramps, and heavy weaving -- which is why it stays at 55.

FHWA guidelines don't require 60–65 mph when the operational environment is urban and interchange spacing is tight. Geometry alone isn't the determinant; weaving demand, ramp frequency, and volume matter just as much.

I know most southern and western states would post them at 60 or 65 mph. I-264 in Virgina Beach has a 70 mph design speed and can safely handle 60 mph without any issues.

That's really only true in a few specific suburban corridors with long interchange spacing. Once you look at actual metro freeways in southern and western states, most of them are posted at 55 mph when the interchange density and weaving look like I‑264.

Atlanta, Houston, Dallas, Phoenix, San Diego, and Los Angeles all have major metro freeways posted no higher than 55. The 60–65 mph examples you're thinking of are almost always suburban segments with wide ramp spacing, not dense urban corridors like I‑264.

[Pink Jazz]

I'm thinking the number of exits along that stretch of I-264 (most of which involves loop ramps) makes it less than ideal for a higher speed limit to be in place there.

Still this doesn't change the fact that practically all other 49 states would post a freeway with identical geometry at 60 or 65 mph in full compliance with FHWA guidelines. I hope the FHWA intervenes to order a speed limit increase against the wishes of VDOT.

The comparison to "49 other states" doesn't really hold. I‑264 in Virginia Beach isn't a rural or lightly‑suburban facility -- it's a high‑volume urban corridor with dense interchange spacing, short weaving sections, and continuous loop‑ramp activity.

Plenty of states post similar geometry at 55 mph when the context is urban: the I-495 Capital Beltway, I-695 Baltimore Beltway, I‑476, and long stretches of NJ I‑295 all run 55 under comparable interchange density and traffic load.

Parts of I‑64 in Chesapeake are posted at 60 mph, so VDOT clearly isn't opposed to higher limits on urban/suburban freeways when the operational profile supports it. I‑264's geometry is tighter -- short interchange spacing, multiple loop ramps, and heavy weaving -- which is why it stays at 55.

FHWA guidelines don't require 60–65 mph when the operational environment is urban and interchange spacing is tight. Geometry alone isn't the determinant; weaving demand, ramp frequency, and volume matter just as much.

I know most southern and western states would post them at 60 or 65 mph. I-264 in Virgina Beach has a 70 mph design speed and can safely handle 60 mph without any issues.

That's really only true in a few specific suburban corridors with long interchange spacing. Once you look at actual metro freeways in southern and western states, most of them are posted at 55 mph when the interchange density and weaving look like I‑264.

Atlanta, Houston, Dallas, Phoenix, San Diego, and Los Angeles all have major metro freeways posted no higher than 55. The 60–65 mph examples you're thinking of are almost always suburban segments with wide ramp spacing, not dense urban corridors like I‑264.

Phoenix is almost entirely posted at 65 mph, with SR 143 and the southern portion SR 51 being the main exceptions. In fact, the Arizona legislature recently ordered ADOT to increase the southernmost portion of I-17 in Phoenix to 65 mph, despite the substandard lane and shoulder width that kept this portion at 55 mph for years.

[Rothman]

I just wonder why VDOT just downright refuses increasing the speed limit on I-264 between First Colonial and Witchduck Rd (VA 190). This section has a 70 mph design speed and the flow of traffic is consistently faster than the 55-mph speed limit. Practically all other 49 states would post a freeway with similar geometry at 60 or 65 mph. I wonder why does VDOT refuse? I know it was considered back in 2001, but this segment keeps getting skipped over each time there is a speed limit increase in the Hampton Roads area. Can the FHWA step in and order a traffic study?

You could ask

Half the time they won't do anything because nobody asked. All it takes is one!

Source: I requested I-10 in east Texas be increased from 65 and now it's 75.

I'm thinking the number of exits along that stretch of I-264 (most of which involves loop ramps) makes it less than ideal for a higher speed limit to be in place there.

Still this doesn't change the fact that practically all other 49 states would post a freeway with identical geometry at 60 or 65 mph in full compliance with FHWA guidelines. I hope the FHWA intervenes to order a speed limit increase against the wishes of VDOT, with federal funding taken away from VDOT if VDOT fails to comply.

Wut.