News:

Thanks to everyone for the feedback on what errors you encountered from the forum database changes made in Fall 2023. Let us know if you discover anymore.

Main Menu

State route concurrencies that cross state lines

Started by hbelkins, July 11, 2018, 02:11:32 PM

Previous topic - Next topic

hbelkins



Government would be tolerable if not for politicians and bureaucrats.


Sctvhound

SC/NC 41. Goes from US 17 in Mt. Pleasant well up into North Carolina.

hotdogPi

Quote from: Sctvhound on July 11, 2018, 05:17:54 PM
SC/NC 41. Goes from US 17 in Mt. Pleasant well up into North Carolina.

Not a concurrency.
Clinched, minus I-93 (I'm missing a few miles and my file is incorrect)

Traveled, plus US 13, 44, and 50, and several state routes

I will be in Burlington VT for the eclipse.

ilpt4u

Quote from: hbelkins on July 11, 2018, 02:11:32 PM
Any others besides NC/VA 49/96?
I'm assuming that both must be State Routes?

IL/MO 110 crosses the Mississippi, concurrent with I-72 and US 36, but not any other IL/MO Routes (that I am aware of)

Eth

So close but not quite: GA 23/121 continues as only FL 121*, which then has an intersection with County Road 23D about a half-mile later. The beginning of FL 23 is about 15 miles east of there at an interchange with I-10.

(* sidenote: I believe this is the only case of a Florida state road continuing in another state with the same number.)

MNHighwayMan

#5
MN-16 continues into Wisconsin as WI-16 concurrent with US-14/61. But this one's cheating just a little bit since it used to be US-16.

Super Mateo

Quote from: ilpt4u on July 11, 2018, 09:29:28 PM
Quote from: hbelkins on July 11, 2018, 02:11:32 PM
Any others besides NC/VA 49/96?
I'm assuming that both must be State Routes?

IL/MO 110 crosses the Mississippi, concurrent with I-72 and US 36, but not any other IL/MO Routes (that I am aware of)

I think so, so that would rule out something like US 52/IL 64/IA 64 further north on the Mississippi.

hbelkins

Yes, I'm thinking about two state routes that carry the same numbers concurrently across a state line.


Government would be tolerable if not for politicians and bureaucrats.

NE2

Quote from: Eth on July 11, 2018, 10:04:44 PM
So close but not quite: GA 23/121 continues as only FL 121*, which then has an intersection with County Road 23D about a half-mile later. The beginning of FL 23 is about 15 miles east of there at an interchange with I-10.

(* sidenote: I believe this is the only case of a Florida state road continuing in another state with the same number.)
FL 121 is former FL 23.
pre-1945 Florida route log

I accept and respect your identity as long as it's not dumb shit like "identifying as a vaccinated attack helicopter".

roadman65

NE2 stated it, but yes FL 23 was relocated to be the First Coast Expressway.  It did continue into FL as a FL route years ago.
Every day is a winding road, you just got to get used to it.

Sheryl Crowe

vdeane

If overlaps with US and interstate routes are fine, NJ/NY 17 overlaps I-287 when crossing the border.
Please note: All comments here represent my own personal opinion and do not reflect the official position of NYSDOT or its affiliates.

DrSmith

Another US/state route combo is 202 & 10 crossing from CT into Mass.

ErmineNotyours

Could we count US 97 continuing as BC 97?  I-5 to BC 99 no longer qualifies.

TheHighwayMan3561

Quote from: ErmineNotyours on July 13, 2018, 12:12:50 AM
Could we count US 97 continuing as BC 97?  I-5 to BC 99 no longer qualifies.

That example isn't what the thread is looking for, as that's a US route keeping a number crossing a border.

What the OP is looking for would be two state routes crossing a border and both keeping the same number, like if cpncurrent MN 1 and MN 2 become WIS 1 and WIS 2 crossing between Minnesota and Wisconsin. (There is no need to point out all the problems with my example; it's just an example).
self-certified as the dumbest person on this board for 5 years running

corco

I'm 97% sure there are no examples of this west of the Mississippi River

jp the roadgeek

Interstates I've clinched: 97, 290 (MA), 291 (CT), 291 (MA), 293, 295 (DE-NJ-PA), 295 (RI-MA), 384, 391, 395 (CT-MA), 395 (MD), 495 (DE), 610 (LA), 684, 691, 695 (MD), 695 (NY), 795 (MD)

hotdogPi

Clinched, minus I-93 (I'm missing a few miles and my file is incorrect)

Traveled, plus US 13, 44, and 50, and several state routes

I will be in Burlington VT for the eclipse.

SSOWorld

Quote from: corco on July 13, 2018, 01:54:51 AM
I'm 97% sure there are no examples of this west of the Mississippi River
MN-ND-MT-ID 200
ND-SD 1804 and
ND-SD 1806
IL-IA 64 (Crosses the Mississippi River)
CA-NV 28
Scott O.

Not all who wander are lost...
Ah, the open skies, wind at my back, warm sun on my... wait, where the hell am I?!
As a matter of fact, I do own the road.
Raise your what?

Wisconsin - out-multiplexing your state since 1918.

MNHighwayMan

Quote from: SSOWorld on July 13, 2018, 07:08:16 AM
Quote from: corco on July 13, 2018, 01:54:51 AM
I'm 97% sure there are no examples of this west of the Mississippi River
MN-ND-MT-ID 200
ND-SD 1804 and
ND-SD 1806
IL-IA 64 (Crosses the Mississippi River)
CA-NV 28

I am 99.9% sure none of those are concurrencies that cross state lines, but rather singular designations that are maintained over them.

hotdogPi

Another "almost, but not quite": NH/ME 9 and NH/ME 236. Both 236s are separate, and neither reaches the state border, but it's pretty close.
Clinched, minus I-93 (I'm missing a few miles and my file is incorrect)

Traveled, plus US 13, 44, and 50, and several state routes

I will be in Burlington VT for the eclipse.

sparker

Up until the 1964 renumbering, both SSR 4 and SSR 88 reached the NV state line as a multiplex, but only the 88 number actually "crossed the border" and was signed as a NV route.  After the renumbering, the new CA 4 actually multiplexed up CA 89 to the present east 88/89 junction but terminated there; it was later truncated back to its present terminus at CA 89. 

pianocello

I might have a historic example: According to Jeff Morrison's site, there could have been a brief period when IA/NE 64 and 92 both crossed the Missouri River in Omaha at the location of the I-480 bridge now. (Link)

IA/NE 92 was on that bridge from the late 30s until it was moved to its current bridge in 1959. IA 64 had gone at least as far as downtown Council Bluffs in the late 30s, and NE 64 was extended east to Omaha in the late 50s, Jeff says 1957ish. It's unclear if NE 64 and IA 64 ever were signed concurrently with US 6 to meet each other at the bridge, but if they did, then it counts for this thread.
Davenport, IA -> Valparaiso, IN -> Ames, IA -> Orlando, FL -> Gainesville, FL -> Evansville, IN

Bickendan

Quote from: MNHighwayMan on July 12, 2018, 06:33:35 AM
MN-16 continues into Wisconsin as WI-16 concurrent with US-14/61. But this one's cheating just a little bit since it used to be US-16.
Also, according to Froggie, MNDot doesn't consider MN 16 to exist on the US 14/61 facility between the US 14/61/MN 16 split and the MN/WI border... despite it being signed in the field.
(Froggie, correct any inaccuracies please!)

MNHighwayMan

Quote from: Bickendan on July 17, 2018, 08:41:33 PM
Quote from: MNHighwayMan on July 12, 2018, 06:33:35 AM
MN-16 continues into Wisconsin as WI-16 concurrent with US-14/61. But this one's cheating just a little bit since it used to be US-16.
Also, according to Froggie, MNDot doesn't consider MN 16 to exist on the US 14/61 facility between the US 14/61/MN 16 split and the MN/WI border... despite it being signed in the field.
(Froggie, correct any inaccuracies please!)

Not him, but that is what the last available route log states, correct. But since it is signed it effectively exists, from a practical perspective.



Opinions expressed here on belong solely to the poster and do not represent or reflect the opinions or beliefs of AARoads, its creators and/or associates.