US routes that multiplex before terminating

[Mapmikey]

More:

US 17 north ends concurrent with US 11-50-522

US 221 north ends concurrent with US 460-501 Bus

US 701 south used to end after a 60-mile concurrency with US 17

US 601 south used to end after a concurrency with US 321 (and vice-versa)

US 13 south used to end in Bowers Hill, VA while concurrent with US 460

US 33 east ends after concurrency with US 250

US 24 west used to end after a long US 6 concurrency

US 117 south used to end after a US 421 concurrency

US 411 north used to end after a US 11E-19 concurrency

US 26 west used to end after a US 101 concurrency

US 311 south used to end in Asheboro after a US 220 concurrency

Mapmikey

[oscar]

US 223's south end multiplexes with US 23, before 223 quietly disappears just south of the Ohio border.  I wonder if that multiplex (with that tiny segment in Ohio) is there to evade AASHTO's rule against short intrastate US routes.

[bulldog1979]

There is US 223, which pairs up with US 23 for about 6 miles from near Blissfield, MI south to SR 51 in Sylvania (Toledo), OH. As mentioned previously, 223 was truncated in 1986 during the "Great Toledo Route Switch" when SR 51 followed much of US 223's old Ohio alignment from Downtown Toledo to US 23.

The question remains why Michigan and especially Ohio (for less than 1 stinkin' mile) continue to recognize US 223 along US 23.

ODOT doesn't sign US 223. They only list it in their straight-line diagram. MDOT on the other hand fully signs it where it exists, because until the two of them decide to petition AASHTO to truncate it further, it does exist on the southernmost part of the US 23 freeway in Michigan.

[elsmere241]

Close to home.  US 43 ends north of Columbia, TN @ US 31 while multiplexed with US 412.

And, to the best of my knowledge, US 31A and US 41A are multiplexed when US 31A ends at US 31 in Nashville.

Lafayette Street at that point is US 31A-41A-41-70S.

[agentsteel53]

Actually, I was noting that 6 was concurrent with Alt 101 at its end, and 91 was concurrent with Alt 101 coming in from the other direction.

ah okay; I did not notice that 6 and Alt 101 had shared some mileage there at the end.

[mightyace]

And, to the best of my knowledge, US 31A and US 41A are multiplexed when US 31A ends at US 31 in Nashville.

Lafayette Street at that point is US 31A-41A-41-70S.

I think you're right, I had forgotten about everything and it's been awhile since I've actually been past there.  And, in the field, it's hard to tell as arterials in Nashville are poorly signed, at best.

[RustyK]

US 40 and 322 share pavement from Hamilton, NJ into Atlantic City, where they both end right near the water. 

[bugo]

US 169 and 64.

[InterstateNG]

There is US 223, which pairs up with US 23 for about 6 miles from near Blissfield, MI south to SR 51 in Sylvania (Toledo), OH. As mentioned previously, 223 was truncated in 1986 during the "Great Toledo Route Switch" when SR 51 followed much of US 223's old Ohio alignment from Downtown Toledo to US 23.

The question remains why Michigan and especially Ohio (for less than 1 stinkin' mile) continue to recognize US 223 along US 23.

ODOT doesn't sign US 223. They only list it in their straight-line diagram. MDOT on the other hand fully signs it where it exists, because until the two of them decide to petition AASHTO to truncate it further, it does exist on the southernmost part of the US 23 freeway in Michigan.

http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Toledo,+OH&sll=37.0625,-95.677068&sspn=49.043149,79.013672&ie=UTF8&hq=&hnear=Toledo,+Lucas,+Ohio&ll=41.714379,-83.68475&spn=0.022873,0.038581&z=15&layer=c&cbll=41.714719,-83.685305&panoid=Vphp_iXFvktCjPmNRnp6rQ&cbp=12,333.52,,0,4.5

http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Toledo,+OH&sll=37.0625,-95.677068&sspn=49.043149,79.013672&ie=UTF8&hq=&hnear=Toledo,+Lucas,+Ohio&ll=41.715019,-83.6902&spn=0.022873,0.038581&z=15&layer=c&cbll=41.714949,-83.690282&panoid=_fbWN-B0N_S-f72Pb5ow2A&cbp=12,50.51,,0,2.9

Nothing on mainline 23, however.

[bugo]

ODOT doesn't sign US 223. They only list it in their straight-line diagram. MDOT on the other hand fully signs it where it exists, because until the two of them decide to petition AASHTO to truncate it further, it does exist on the southernmost part of the US 23 freeway in Michigan.

I thought I remember seeing an assembly with a large 23 shield with a small 223 shield.  I always assumed it was in Ohio.  Was it in Michigan?

[prenatt1166]

US 40 and 50 began concurrent with each other in San Francisco for years - originally, along Market Street until the Bay Bridge was opened, then on Harrison and Bryant Streets to 9th/10th Street when the Bay Bridge was first opened, and finally at the Bayshore/Central/James Lick Skyway split with 101 when the skyway (today's I-80, which was co-signed with 40/50 for a few years) was finished.

US 40 and 322 share pavement from Hamilton, NJ into Atlantic City, where they both end right near the water. 

This is interesting.  How long did the US 40/US 50 multiplex exist after US 322 was routed along US 40 in NJ?

[TheStranger]

This is interesting.  How long did the US 40/US 50 multiplex exist after US 322 was routed along US 40 in NJ?

The 40/50 concurrency lasted until at least 1964; this 1967 map shows only 50 and 80 concurrent to SF on the Bay Bridge:
http://teczno.com/old-oakland/

According to Wikipedia, the 40/322 concurrency was first created in 1936.

[Scott5114]

US 400 ends going westbound while duplexed with US 50 at Granada, CO, and ends going eastbound while duplexed with US 166 at Joplin, MO (which also ends while duplexed with US 400 at that I-44 interchange - did they have a fight over which route would end at the US 400/US 166 intersection near Baxter Springs so they just kept both?      )

It was 166 first. AASHTO has a policy regarding the number of states a US highway has to go through, so when Kansas was creating US 400, they ran it up to the state line on either side. Colorado and Missouri didn't really know what the hell to do with it, so they both just ended it at the first available opportunity.

[Hot Rod Hootenanny]

It's not much but US 42 and US 322 each multiplex with US 6 (and 20) for several blocks before ending at Public Square in Cleveland.

[yakra]

US270 ends on a useless duplex with US83 at US54 in Liberal, KS.
US275 ends on a useless duplex with US20 at US281 in O'Neill, NE.

[ctsignguy]

Back in the day, US 68 hooked up with US 25 in Findlay OH, and was concurrent all the way up to Toledo....

[national highway 1]

US 164 (II) was concurrent with US 89 from Tuba City AZ, to US 66 in Flagstaff from 1966-70
The same happened at the other end with US 666 into Cortez, CO.

[TheStranger]

US270 ends on a useless duplex with US83 at US54 in Liberal, KS.

270 is probably one of several examples of a US route whose entire run in a state (Kansas, in this case) is concurrent with another US route; US 70 in California and US 56/412 in New Mexico also fit this, as does US 62 in New Mexico (though it doesn't terminate there).

---

Forgot to mention one I just thought of - US 62 and US 85 in El Paso.

[US71]

US270 ends on a useless duplex with US83 at US54 in Liberal, KS.
US275 ends on a useless duplex with US20 at US281 in O'Neill, NE.

Also (formerly) US 65 in Pine Bluff

[sandiaman]

The  Stranger is right,  US 62 mulitplexes  with US  180  all the way thru NM  and terminates in El Paso.  US 180  starts (or ends)  in  Texas, leaves Texas  and re-enters Texas.  It also  leaves  NM  and re-enters  NM  and terminates in AZ.  US 180 is unique    in that respect, I believe.

[TheStranger]

The  Stranger is right,  US 62 mulitplexes  with US  180  all the way thru NM  and terminates in El Paso.  US 180  starts (or ends)  in  Texas, leaves Texas  and re-enters Texas.  It also  leaves  NM  and re-enters  NM  and terminates in AZ.  US 180 is unique    in that respect, I believe.

62 starts in Texas, leaves it, then re-enters - similar to US 395 starting in California, going through Nevada, then reappearing in California.

180 actually continues for a while west to the Grand Canyon.

[agentsteel53]

I believe the 2-141 multiplex weaves between Michigan and Wisconsin four times.  MI-WI-MI-WI

[bugo]

270 is probably one of several examples of a US route whose entire run in a state (Kansas, in this case) is concurrent with another US route; US 70 in California and US 56/412 in New Mexico also fit this, as does US 62 in New Mexico (though it doesn't terminate there).

US 59 is duplexed with either US 71 or US 270 on its entire route through Arkansas.

[TheStranger]

270 is probably one of several examples of a US route whose entire run in a state (Kansas, in this case) is concurrent with another US route; US 70 in California and US 56/412 in New Mexico also fit this, as does US 62 in New Mexico (though it doesn't terminate there).

US 59 is duplexed with either US 71 or US 270 on its entire route through Arkansas.

For that matter, US 71's short (Texarkana-area) run in Texas is along its concurrency with US 59!

[rawmustard]

I believe the 2-141 multiplex weaves between Michigan and Wisconsin four times.  MI-WI-MI-WI

The 2-141 plex merely dips once into Florence County, WI, between Crystal Falls and Iron Mountain.