Do any U.S. Highways exist that do not parallel any interstate highway throughout its entire course? Essentially, no interstate highway was ever built specifically to follow the same path of the U.S. Highway for more than 5-10 miles. That so-called U.S. Highway serves as the main route for thru traffic, and there's not an interstate paralleling it for thru traffic to use throughout its entire course.
If the U.S. Highway follows generally parallel to another interstate going the same direction, but is a significant distance (15-20 miles) away and that interstate would never compete to the U.S. Highway (I.E. they split off in both directions, and never cross or touch while being "parallel") that still counts as the interstate was never intended to parallel that particular road, it just happens to head the same direction for a portion of the route.
I can't think of any examples of the top of my head, but I'm just curious as to if any exist.
EDIT - Since most of the routes that follow no interstates whatsoever have been mentioned, if less than 15% of the entire route (take how much mileage the route parallels / overlaps an interstate then divide by the entire route's mileage) parallels or follows an interstate highway, it can qualify for this thread.
US 131, unless you count the few miles of concurrent unsigned I-296.
US 151 is not concurrent with any Interstate.
US 169 comes to mind.
Western US 2
Quote from: TheHighwayMan394 on June 08, 2019, 06:26:16 PM
US 169 comes to mind.
Close, but about 7 miles near St. Joseph run parallel to I-29, and there's a 14 mile concurrency with I-35 in Kansas City. From the looks of it, there's areas in other cities & urban areas as well that the highway parallel an interstate for at least 5-10 miles.
Quote from: TheHighwayMan394 on June 08, 2019, 06:26:16 PM
Western US 2
With the exception of a 3 mile overlap with I-90 in Spokane, that would work. Still within the criteria as it follows an interstate for less than 5-10 miles.
US 17 and US 64.
I'm gonna go with US 68. For running through a region with a lot of interstates, it stays away from most of them.
Quote from: NE2 on June 08, 2019, 07:01:31 PM
US 17
Briefly overlapping I-95?
. . . . .
US-360
Quote from: NE2 on June 08, 2019, 07:01:31 PM
US 17 and US 64.
US-17 has a concurrency with I-64, I-95 and I-140 and runs parallel to I-95 for a significant distance in Georgia and Florida, also parallel to I-4 in Florida. Once the Kinston Bypass is constructed and I-42 is brought over to New Bern, US-17 would also overlap 7 miles of that. Unless of course the northern portion of the US-17 relocation is ever built.
US-64 has a concurrency with I-87, I-440, I-40, I-55, I-35, and runs parallel to I-75 and I-40 in parts.
US 101 does not parallel I-5. By definition, parallel lines never meet but these two routes connect on 101's north end (Olympia WA) and south end (Los Angeles CA).
Rick
Quote from: sprjus4 on June 08, 2019, 07:37:54 PM
US-64 has a concurrency with I-87, I-440, I-40, I-55, I-35, and runs parallel to I-75 and I-40 in parts.
It also has a short concurrency with I-75 northeast of Chattanooga, with I-24 for about 25 miles northwest of Chattanooga, and with I-25 for a few miles in Raton NM.
Quote from: nexus73 on June 08, 2019, 07:49:05 PM
US 101 does not parallel I-5. By definition, parallel lines never meet but these two routes connect on 101's north end (Olympia WA) and south end (Los Angeles CA).
Rick
I think it's safe to say US-101 is an independent route. It does not really parallel any interstate highways directly and has no concurrencies as far as I'm aware.
US 163 and US 550 come to mind.
I'm sure that a lot of 3-di's will appear and it seems that most 2-di's do parallel an Interstate. Perhaps that's how the Interstate system was planned but I'm not sure on that.
US-127 and as mentioned earlier US-131 don't really parallel any Interstate's.
US-2 doesn't really parallel an Interstate either, it has no junctions with any east-west Interstate.
57
350
491
Concurrencies usually occur on routes that, in the big picture, head in different directions and serve different corridors. Thus, routes like US 64 that have many concurrencies are better examples than routes like US 101. The fact that a
variety of concurrencies exist
proves that there isn't a parallel interstate.
Personal opinion here, but 3dis do not count as parallel interstates, especially when looking at the entire length of the US route.
Quote from: nexus73 on June 08, 2019, 07:49:05 PM
US 101 does not parallel I-5. By definition, parallel lines never meet but these two routes connect on 101's north end (Olympia WA) and south end (Los Angeles CA).
Let's be realistic regarding our interpretations of "parallel". US 11 and I-81 cross each other many, many times, yet it cannot be argued that they aren't parallel - they are, full stop. Same with I-5 and US 101. For the most part, they run parallel to each other; whether US 101 counts for the thread is an open question only because of the
distance from I-5, not because it's unclear whether they're parallel.
Most 3-di US routes don't parallel Interstate routes, or at least were not supplanted by interstates. The ones that come to mind in my part of the country include 231, 280, 331, 411, and 431 in Alabama, 129, 319 and 341 in Georgia....
Quote from: Charles2 on June 08, 2019, 08:23:21 PM
Most 3-di US routes don't parallel Interstate routes, or at least were not supplanted by interstates. The ones that come to mind in my part of the country include 231, 280, 331, 411, and 431 in Alabama, 129, 319 and 341 in Georgia....
I-16 and US 280 in Georgia
I-65 and US 431 in Tennessee
I-75 and US 411 in Tennessee
Quote from: 1 on June 08, 2019, 08:34:52 PM
Quote from: Charles2 on June 08, 2019, 08:23:21 PM
Most 3-di US routes don't parallel Interstate routes, or at least were not supplanted by interstates. The ones that come to mind in my part of the country include 231, 280, 331, 411, and 431 in Alabama, 129, 319 and 341 in Georgia....
I-16 and US 280 in Georgia
I-65 and US 431 in Tennessee
I-75 and US 411 in Tennessee
Also I-95 and US 301.
Quote from: Charles2 on June 08, 2019, 08:23:21 PM
Most 3-di US routes don't parallel Interstate routes, or at least were not supplanted by interstates. The ones that come to mind in my part of the country include 231, 280, 331, 411, and 431 in Alabama, 129, 319 and 341 in Georgia....
VA US-211
Are we allowed to post highways that used to parallel one, but have had their paralleled segments removed?
Quote from: Kulerage on June 08, 2019, 09:51:41 PM
Are we allowed to post highways that used to parallel one, but have had their paralleled segments removed?
As long as it still does not follow it's parallel / concurrency path with an interstate highway today, then it's fine.
US 113, which might be the only US route that doesn't even get near an Interstate.
Quote from: sprjus4 on June 08, 2019, 09:53:23 PM
Quote from: Kulerage on June 08, 2019, 09:51:41 PM
Are we allowed to post highways that used to parallel one, but have had their paralleled segments removed?
As long as it still does not follow it's parallel / concurrency path with an interstate highway today, then it's fine.
In that case;
US 521 doesn't have any interstate that truly follows it's path.
US 701
US 73
US 400
US 199
Quote from: 1 on June 08, 2019, 09:56:36 PM
US 113, which might be the only US route that doesn't even get near an Interstate.
US 163 begs to differ.
US 65
US 75
US 79
US 165
US 167
US 175
Quote from: sprjus4 on June 08, 2019, 07:55:14 PM
Quote from: nexus73 on June 08, 2019, 07:49:05 PM
US 101 does not parallel I-5. By definition, parallel lines never meet but these two routes connect on 101's north end (Olympia WA) and south end (Los Angeles CA).
Rick
I think it's safe to say US-101 is an independent route. It does not really parallel any interstate highways directly and has no concurrencies as far as I'm aware.
It was supplanted by I-5 south of downtown Los Angeles.
Mike
US 8
US 53
US 58
US 141 south of metro Green Bay, WI was supplanted by I-43.
Mike
Quote from: mgk920 on June 08, 2019, 11:22:53 PM
Quote from: sprjus4 on June 08, 2019, 07:55:14 PM
Quote from: nexus73 on June 08, 2019, 07:49:05 PM
US 101 does not parallel I-5. By definition, parallel lines never meet but these two routes connect on 101's north end (Olympia WA) and south end (Los Angeles CA).
Rick
I think it's safe to say US-101 is an independent route. It does not really parallel any interstate highways directly and has no concurrencies as far as I'm aware.
It was supplanted by I-5 south of downtown Los Angeles.
Mike
Historically it was, though the southern terminus has been since truncated at the I-5 / I-10 / CA-60 / US-101 interchange south of Downtown.
US 98 comes to mind. I suppose you could quibble about a short parallel stretch with I-10 in Mobile, and a brief concurrency with I-59 near Jackson.
The I-10 segment could fall under the OP's allowance for a short stretch (and you can consider I-10 to be parallel with US 90 primarily).
The I-59 concurrency is very short between an east-west road and a north-south road, which nobody would consider I-59 and US 98 to "parallel" each other.
Quote from: dlsterner on June 08, 2019, 11:49:28 PM
The I-10 segment could fall under the OP's allowance for a short stretch (and you can consider I-10 to be parallel with US 90 primarily).
I'd say it works mainly because it's a water crossing, and that's really the only feasible place for both routes to cross. The divert from each other immediately after crossing.
Quote from: dlsterner on June 08, 2019, 11:49:28 PM
The I-59 concurrency is very short between an east-west road and a north-south road, which nobody would consider I-59 and US 98 to "parallel" each other.
It still is a concurrency nonetheless, but it is under 5-10 miles, so it would still work.
US-98 works.
Quote from: mgk920 on June 08, 2019, 11:26:05 PM
US 8
I-35 and I-35W replaced it into Minneapolis, with a concurrency for a number of years before truncation to the current Forest Lake terminus.
Quote
US 53
Could argue that I-94 parallels it for an 18-mile stretch from Eau Claire to Osseo.
US 44 really doesn't, thanks to the NIMBY's cancelling I-84 from Hartford to Providence. One can argue that it parallels I-84 between the Middletown, NY area and Manchester, CT, but it's far enough away during most of the trek, even jogging northeast away from I-84 between Poughkeepsie and Canaan, CT. US 6 is the true one that parallels 84. Even east of Providence, it loosely parallels I-195, but diverts away more due east while I-195 deflect southeast.
US 4 east of Whitehall, NY doesn't parallel any interstate, nor do US 2 or US 302 between Montpelier, VT and Fairfield and Portland, ME, respectively.
Quote from: TheHighwayMan394 on June 09, 2019, 12:28:43 AM
Quote from: mgk920 on June 08, 2019, 11:26:05 PM
US 53
Could argue that I-94 parallels it for an 18-mile stretch from Eau Claire to Osseo.
IMHO, I-94 was routed independently of US 53 and that 'parallel' part is just a co-incidence.
Mike
Quote from: sprjus4 on June 08, 2019, 06:32:31 PM
Quote from: TheHighwayMan394 on June 08, 2019, 06:26:16 PM
Western US 2
With the exception of a 3 mile overlap with I-90 in Spokane, that would work. Still within the criteria as it follows an interstate for less than 5-10 miles.
That works now, but I-75 runs along the pre-truncated route of US-2 from (roughly) St Ignace to Sault Ste Marie.
I saw US 58 mentioned, which was the one that immediately came to my mind. It has a short concurrency between Bristol and Abingdon with I-81, but other than that, it's an independent route.
How about US 23? Its concurrency with I-26 is a relatively new thing.
Wouldn't US 27's current incarnation (terminating at I-69 in Ft. Wayne) work? It's far enough away from I-75 in Ohio, Kentucky, Tennessee and Georgia to qualify.
Come to think of it, US 33 and US 35 work too, as does the current US 48.
The Devil's highway, now known as US 491.
Quote from: US 89 on June 08, 2019, 10:19:11 PM
Quote from: 1 on June 08, 2019, 09:56:36 PM
US 113, which might be the only US route that doesn't even get near an Interstate.
US 163 begs to differ.
As signed maybe, but officially it still runs all the way up to I-70 IIRC.
Quote from: TheHighwayMan394 on June 09, 2019, 12:28:43 AM
Quote from: mgk920 on June 08, 2019, 11:26:05 PM
US 8
I-35 and I-35W replaced it into Minneapolis, with a concurrency for a number of years before truncation to the current Forest Lake terminus.
OP allows highways that used to, but no longer have parallel segments.
Quote from: hbelkins on June 09, 2019, 04:21:27 PM
I saw US 58 mentioned, which was the one that immediately came to my mind. It has a short concurrency between Bristol and Abingdon with I-81, but other than that, it's an independent route.
Debatable. While most of the route is independent, the overlap with I-81 is 20 miles, which exceeds the 5-10 mile limit. Also, in the future there will be more interstates being concurrent with US-58. 7 miles of I-785 and US-58 will be overlapped in Danville, along with 7 miles of I-73 in Martinsville if an eastern route is selected, though that'll most likely end up going west. Even if you pushed that aside though, Hampton Roads is where it's not an independent route. I-264 parallels US-58 for 25 miles, and for that stretch, US-58 is a local road, and I-264 is the main thru route.
So approximately 45 miles of interstate highway currently concurrent with US-58, and at least another 9 or so miles in the future.
US 258 fits this.
US 199 also fits the criteria.
Quote from: sprjus4 on June 09, 2019, 05:38:24 PM
So approximately 45 miles of interstate highway currently concurrent with US-58, and at least another 9 or so miles in the future.
Why would that disqualify US 58, a 508 mile long route, as a whole? Most of it is independent and has not been supplanted by interstates. Totally opposite situation to I-81/ US 11; guess which one I'd pick as a contender if I had a choice?
Quote from: mgk920 on June 09, 2019, 03:28:23 PM
IMHO, I-94 was routed independently of US 53 and that 'parallel' part is just a co-incidence.
Thank you! This is what I've been saying. The I-94 example is irrelevant in the context of US 53 as a whole. How can you say US 53 from Duluth to Eau Claire doesn't qualify just because of a glitch south of Eau Claire?
Quote from: webny99 on June 09, 2019, 06:08:33 PM
Why would that disqualify US 58, a 508 mile long route, as a whole? Most of it is independent and has not been supplanted by interstates. Totally opposite situation to I-81/ US 11 - guess which one I'd pick as a contender if I had a choice?
The entire point was to identify U.S. Highways that do not parallel or have a concurrency with an interstate throughout it's entire duration -at all- or minimal such as a 3-5 mile overlap traversing through a town or something - like US-2 and I-90 through Spokane.
If the overlap with I-81 was only 5-10 miles long, and I-264 wasn't intentionally built parallel to US-58 for almost 30 miles to supplement it in Hampton Roads, then that'd be a different story.
I get that. All I'm saying is if you ranked all US highways based on the percentage that has been supplanted, US 58 is going to be near the bottom. You might only find 5-10 US highways that have fewer concurrencies or parallels than US 58.
So even if US 58 is not a technically correct answer, it is closer to being a correct answer than the vast, vast majority of other US highways. Unlike US 11, it still serves an important purpose for long distance traffic for much of its length. Thus, I think US 58 does fit the spirit of the thread (although obviously that isn't my call :)).
Quote from: webny99 on June 09, 2019, 06:24:55 PM
I get that. All I'm saying is if you ranked all US highways based on the percentage that has been supplanted, US 58 is going to be near the bottom. You might only find 5-10 US highways that have fewer concurrencies or parallels than US 58.
So even if US 58 is not a technically correct answer, it is closer to being a correct answer than the vast, vast majority of other US highways. Unlike US 11, it still serves an important purpose for long distance traffic for much of its length. Thus, I think US 58 does fit the spirit of the thread (although obviously that isn't my call :)).
I get what you're saying, and the thread may well evolve that way. I think we've hit most of the highways that follow the original topic, so I guess this is the direction it will go, or else the thread will die. But obviously, something like US-11 is out the door instantly.
Here are the ones that enter PA:
- US 219
- Western US 422
- US 222 (it parallels I-78 for the last 14 miles, but they go off in different directions)
- Arguably US 209 (It briefly parallels a few Interstates and even runs concurrent with I-80 through Stroudsburg, but quickly diverges on its own path each time.)
Quote from: sprjus4 on June 09, 2019, 06:12:43 PM
The entire point was to identify U.S. Highways that do not parallel or have a concurrency with an interstate throughout it's entire duration -at all- or minimal such as a 3-5 mile overlap traversing through a town or something - like US-2 and I-90 through Spokane.
If the overlap with I-81 was only 5-10 miles long, and I-264 wasn't intentionally built parallel to US-58 for almost 30 miles to supplement it in Hampton Roads, then that'd be a different story.
Alt. US-58 takes US-58 away from any I-81 concurrency at Abingdon and doesn't rejoin US-58 until Jonesville.
However, I argued elsewhere that Alt. US-58 is conceptually more like a US-458 or US-658 than any actual part of the US-58 route.
When I was considering US-58 for this thread, the obvious objection was I-264 between Bowers Hill and the VA Beach oceanfront.
Quote from: debragga on June 08, 2019, 10:44:40 PM
US 65
Overlaps I-530 from the Little Rock area down to Pine Bluff.
Quote from: debragga on June 08, 2019, 10:44:40 PMUS 75
Debatable given the proximity to I-29 between Nebraska City and Sioux City.
If we're going to be a little more flexible, then US-158 could work.
It's mostly an independent routing, and only encounters and follows a few interstates for a short distance -
- Parallels I-85 for about 12 miles near Henderson, NC
- Parallels I-40 for about 16 miles southwest of Winston-Salem.
In the future, the US-158 relocation & widening project currently underway near Roanoke Rapids will re-route US-158 and overlap I-95 for 3 miles. Also, once I-87 is completed in northeastern NC, there will be a 3 mile concurrency northwest of Elizabeth City.
In total, once I-87 is completed & the US-158 re-routing over I-95 is completed, the 347 mile route would only parallel & overlap 34 miles of interstate highway, or 9.7% of the total route.
Quote from: Beltway on June 09, 2019, 08:59:22 PM
Quote from: sprjus4 on June 09, 2019, 06:12:43 PM
The entire point was to identify U.S. Highways that do not parallel or have a concurrency with an interstate throughout it's entire duration -at all- or minimal such as a 3-5 mile overlap traversing through a town or something - like US-2 and I-90 through Spokane.
If the overlap with I-81 was only 5-10 miles long, and I-264 wasn't intentionally built parallel to US-58 for almost 30 miles to supplement it in Hampton Roads, then that'd be a different story.
Alt. US-58 takes US-58 away from any I-81 concurrency at Abingdon and doesn't rejoin US-58 until Jonesville.
However, I argued elsewhere that Alt. US-58 is conceptually more like a US-458 or US-658 than any actual part of the US-58 route.
When I was considering US-58 for this thread, the obvious objection was I-264 between Bowers Hill and the VA Beach oceanfront.
Since we're being a little more flexible now with the main no-interstate-whatsoever routes out of the way, it could work. Only 8.8% of the total routing follows or overlaps interstate highways.
See my new edit to the original post that now qualifies any route that follows less than 15% of interstate highways.
Has US-258 been mentioned? It could be argued that none of it was paralleled by an Interstate highway.
U.S. Route 258 (US 258) is a spur of US 58 in the U.S. states of North Carolina and Virginia. The U.S. Highway runs 220.15 miles from US 17 Business and NC 24 Business in Jacksonville, North Carolina north to Virginia State Route 143 (SR 143) at Fort Monroe in Hampton, Virginia.
. . . . .
Has US-13 been mentioned? Other than about 10 miles of I-64 and about 60 miles of I-95 the rest is not concurrent with any Interstate highway.
U.S. Route 13 (US 13) is a north—south U.S. highway established in 1926 that runs for 517 miles (832 km) from Interstate 95 just north of Fayetteville, North Carolina to the northeastern suburbs of Philadelphia, Pennsylvania, in Morrisville. In all, it traverses five states in the Atlantic coastal plain region.
Quote from: Beltway on June 10, 2019, 12:03:28 AM
Has US-258 been mentioned? It could be argued that none of it was paralleled by an Interstate highway.
U.S. Route 258 (US 258) is a spur of US 58 in the U.S. states of North Carolina and Virginia. The U.S. Highway runs 220.15 miles from US 17 Business and NC 24 Business in Jacksonville, North Carolina north to Virginia State Route 143 (SR 143) at Fort Monroe in Hampton, Virginia.
It was mentioned on the last page. It would work. About 5 miles in Hampton is paralleled by I-64, but that's it. That's only about 2% of the entire routing.
Quote from: Beltway on June 10, 2019, 12:03:28 AM
Has US-13 been mentioned? Other than about 10 miles of I-64 and about 60 miles of I-95 the rest is not concurrent with any Interstate highway.
U.S. Route 13 (US 13) is a north—south U.S. highway established in 1926 that runs for 517 miles (832 km) from Interstate 95 just north of Fayetteville, North Carolina to the northeastern suburbs of Philadelphia, Pennsylvania, in Morrisville. In all, it traverses five states in the Atlantic coastal plain region.
About 15% paralleled by interstates. That could barely fit, but debatable.
Once I-87 is completed in NC, it would be concurrent for about 34 miles between Windsor and Bethel. That would bring it up to about 22%, and by then, it wouldn't really count. If US-58 / US-13 / US-460 is ever upgraded into an I-X64 or I-264 extension between Bowers Hill and the east end of the Suffolk Bypass, that's another 15 miles, up to 25%.
I've always been a fan of the famous "Million Dollar Highway", US-550. As mentioned previously, it fits the bill quite well in weaving through a unique corridor. It shares south Durango with US-160 for about 4.5 miles
Quote from: hbelkins on June 09, 2019, 04:21:27 PM
How about US 23? Its concurrency with I-26 is a relatively new thing.
What about the long concurrency with I-75 (Flint to near Standish)?
Quote from: GaryV on June 10, 2019, 04:12:37 PM
Quote from: hbelkins on June 09, 2019, 04:21:27 PM
How about US 23? Its concurrency with I-26 is a relatively new thing.
What about the long concurrency with I-75 (Flint to near Standish)?
And US-23 is pretty parallel to I-75 until at least the Upper Sandusky, Ohio area. And then again from Atlanta to Macon.
Also I don't think I-26 should even be an Interstate north of Asheville. It even has to run concurrent with an 3-di to go between alignments.
Quote from: Flint1979 on June 10, 2019, 06:55:08 PM
Also I don't think I-26 should even be an Interstate north of Asheville. It even has to run concurrent with an 3-di to go between alignments.
I-26 originally ended at I-40 / I-240. Sometime in the 80s and 90s due to the push for an interstate in Johnson City and Kingsport, NCDOT & TDOT decided to come up with an extension of Interstate 26. That involved routing I-26 over a portion of I-240, over the existing US-23 freeway between Asheville and Mars Hill. From that point, it was all new construction. The NC portion of I-26 running north of Mars Hill opened in 2002. Once entering Tennessee, it then took over the existing US-23 freeway between North Carolina and Virginia.
All in all, the I-26 extension north of I-40 really overlays all existing freeways, and built a few new segments to form one continuous freeway. It connects the metro areas of Johnson City and Kingsport to the south, and Asheville and cities on the southerly I-26 corridor to I-81 north, and obviously the cities together. It's also a detour and alternate route to I-40 through the mountains - and frankly a much nicer drive - but out of the way unless I-40 is closed.
Ironically, I-26 between Asheville and Mars Hill is still designated as "Future I-26". It still has not been fully upgraded to interstate standards. But for continuity purposes, it has regular I-26 shields, but has an additional banner above the directional one indicating "Future".
For some reason, the first route I thought of in response to this is US385. I don't think the short jog it has along I-10 should implicate that the paths they take are similar in any significant way. And you could argue that it kind of parallels I-90 for its northern 20 miles or so.
US 58 and I-81 go to vastly different places, and if US 58 and its alternate were switched, there would only be a one-exit concurrency. And there's really no reason why US 58 was placed on the interstate alignment and US 11 and US 19, which also parallel I-81 between two towns in the same county, were not.
I-264 was originally VA 44, so the interstate designation came much later.
Quote from: hbelkins on June 10, 2019, 08:27:06 PM
US 58 and I-81 go to vastly different places, and if US 58 and its alternate were switched, there would only be a one-exit concurrency. And there's really no reason why US 58 was placed on the interstate alignment and US 11 and US 19, which also parallel I-81 between two towns in the same county, were not.
I-264 was originally VA 44, so the interstate designation came much later.
My guess is even back then VA wanted US 58 to be a major route, so they threw it on the interstate there. It's really the only reason that makes since to me.
As far as I-264 goes, that's only the case in Virginia Beach. I-264 "between the 64's" has always been I-264 as sections were completed.
Quote from: hbelkins on June 10, 2019, 08:27:06 PM
I-264 was originally VA 44, so the interstate designation came much later.
Only between I-64 in Norfolk and the Oceanfront. From I-64 in Norfolk to I-64 in Bowers Hill, it's always been I-264. Either way though, this is talking from current designations. As of today, I-264 stretches the entire length.
US-58 was likely routed over I-81 unlike US-11 because US-11 serves as a local route, while US-58 is a major thru route. The goal is really to keep it on 4-lane alignments as much as possible, whereas US-11 isn't a big deal.
Quote from: sprjus4 on June 10, 2019, 09:23:04 PM
Only between I-64 in Norfolk and the Oceanfront. From I-64 in Norfolk to I-64 in Bowers Hill, it's always been I-264. Either way though, this is talking from current designations. As of today, I-264 stretches the entire length.
I-264 was in two segments as authorized in 1956. It took a special authorization over 20 years later to fill the gap.
The originally designated I-264 from I-64 at Bowers Hill to I-64/I-264/VA-44 near Military Circle was completed in 1972, and did not include the Downtown Tunnel / Berkley Bridge complex (completed 1952, funded with toll revenue bonds). The tunnel (which crosses the Elizabeth River, South Branch) had a single 2-lane tube, and the bridge (which crosses the Elizabeth River, East Branch) had a single 4-lane span. For years, this road had to serve the I-264 corridor. Virginia got federal Interstate funding (90% FHWA funds) approval in 1978 to upgrade that facility and include it in I-264. The 2.2-mile-long project to build a parallel 2-lane tube, parallel 4-lane bridge, renovated existing 2-lane tube, redecked existing 4-lane bridge, and upgraded urban interchanges was completed in 1991. The dual Downtown Tunnel was finished in 1988.
Quote from: sprjus4 on June 10, 2019, 07:00:42 PM
Quote from: Flint1979 on June 10, 2019, 06:55:08 PM
Also I don't think I-26 should even be an Interstate north of Asheville. It even has to run concurrent with an 3-di to go between alignments.
I-26 originally ended at I-40 / I-240. Sometime in the 80s and 90s due to the push for an interstate in Johnson City and Kingsport, NCDOT & TDOT decided to come up with an extension of Interstate 26. That involved routing I-26 over a portion of I-240, over the existing US-23 freeway between Asheville and Mars Hill. From that point, it was all new construction. The NC portion of I-26 running north of Mars Hill opened in 2002. Once entering Tennessee, it then took over the existing US-23 freeway between North Carolina and Virginia.
All in all, the I-26 extension north of I-40 really overlays all existing freeways, and built a few new segments to form one continuous freeway. It connects the metro areas of Johnson City and Kingsport to the south, and Asheville and cities on the southerly I-26 corridor to I-81 north, and obviously the cities together. It's also a detour and alternate route to I-40 through the mountains - and frankly a much nicer drive - but out of the way unless I-40 is closed.
Ironically, I-26 between Asheville and Mars Hill is still designated as "Future I-26". It still has not been fully upgraded to interstate standards. But for continuity purposes, it has regular I-26 shields, but has an additional banner above the directional one indicating "Future".
I think it's just slapping a highway number IMO that's just how I see it. I guess my point is that I can't see why it can't just be called US-23 since I-26 seems to be a redundant route north of Asheville.
US 2
US 4
US 7*
US 13
US 44
US 50
US 119
US 202
US 219
US 302
*Part of original Interstate plan but idea later scrapped.
Doesn't US 7 briefly parallel I-89?
Quote from: Verlanka on June 11, 2019, 07:14:57 AM
Doesn't US 7 briefly parallel I-89?
Yes, and US 50 parallels I-66, and US 4 parallels I-89, and US 202 parallels I-287, and US 302 parallels I-93.
I would suggest US 285 as it currently exists. It serves as a shorter route from Denver to Santa Fe than I-25 and connects Denver to Buena Vista and Alamosa and Espanola, New Mexico along the way along the west side of the front range and through South Park and the San Luis Valley. South of Santa Fe it has a 7 mile wrong-way unmarked concurrency with I-25 through part of the P-trap, then continues as an independent corridor southeast to Sanderson, TX.
US 97, though the 40-ish mile concurrency with I-90 and I-82 from Ellensburg to Yakima is only about 6% of its length
US 195
US 197
US 730
Quote from: Verlanka on June 11, 2019, 07:14:57 AM
Doesn't US 7 briefly parallel I-89?
Yes but I dont believe it's for more than the 15% of total miles that would disqualify it. It's pretty clear that I-91 is complimentary to US 5 and I-87 to US 9. A lot of I-89 parallels US 4.
Quote from: sprjus4 on June 10, 2019, 09:23:04 PM
Quote from: hbelkins on June 10, 2019, 08:27:06 PM
I-264 was originally VA 44, so the interstate designation came much later.
Only between I-64 in Norfolk and the Oceanfront. From I-64 in Norfolk to I-64 in Bowers Hill, it's always been I-264. Either way though, this is talking from current designations. As of today, I-264 stretches the entire length.
US-58 was likely routed over I-81 unlike US-11 because US-11 serves as a local route, while US-58 is a major thru route. The goal is really to keep it on 4-lane alignments as much as possible, whereas US-11 isn't a big deal.
US 19 is also a major route, and it definitely could have gone on the interstate, following VA 381/I-381 to I-81, then VA 140 over to just south of where it departs US 11 for Bluefield.
I would submit the current iteration of US 460. Since it's truncation west of Frankfort, it really doesn't serve as a parallel route to any interstate (unlike US 60 and I-64). Yes, it parallels I-81 between Christiansburg and Roanoke, but this is much like the US 58 example, and it's an incidental occurrence between two roads with vastly different termini and destinations.
If the western US-2 counts as a separate route, then that should be on the list. There are short concurrences of I-35 near Duluth and I-90 near Spokane. Otherwise, it's entirely independent.
US 4 in both NY and VT does not as well as it east of Concord, NH. What always got me is the N-S portion in NY and E-W part in VT together do not form a straight line corridor and its endpoints is better served by NY 7 and VT/NH 9. However, that was adlibbed as most of US 4 in NY was old US 109 and the parts in VT and NH together did form an east- west corridor.
Being the road is a regional route serving locals it is only used, but with NY 149 connecting US 4 to I-87 I guess that continues Vermont's segment further west in a way.
US 171
US 371
US 380
US 425
iPhone
Except for a secton within the MStP metro area, nothing of what is left of US 10 parallels any interstate.
Mike
Quote from: mgk920 on June 12, 2019, 11:25:53 AM
Except for a secton within the MStP metro area, nothing of what is left of US 10 parallels any interstate.
Mike
Looking quickly on Google Maps, US 10 roughly parallels I-94 between Fargo, ND and Osseo, WI - basically all the way across MN
US-412 doesn't. In fact, I don't think any of the US 400 series does. Arguably, at least one segment of US-412 could eventually become an Interstate, but that would take some political and financial will that doesn't currently exist.
Quote from: ilpt4u on June 12, 2019, 11:32:30 AM
Quote from: mgk920 on June 12, 2019, 11:25:53 AM
Except for a secton within the MStP metro area, nothing of what is left of US 10 parallels any interstate.
Mike
Looking quickly on Google Maps, US 10 roughly parallels I-94 between Fargo, ND and Osseo, WI - basically all the way across MN
More like 'common points via widely differing routes', differing enough that US 10 warrants four lanes divided in its own right across Minnesota. I-94 is parallel to US 12 between Wisconsin Dells, WI and the MStP area and US 52 from MStP into North Dakota. Yes, I-94 and I-90 did supplant US 10 west of Fargo, ND, though.
Mike
How about US Highways 24, 54, and 56?
https://en.wikipedia.org/wiki/U.S._Route_199
US 199 in California and Oregon.
Quote from: Konza on June 14, 2019, 01:30:33 AM
How about US Highways 24, 54, and 56?
US 56 may count as there is only a 17-mile overlap w/I-35 in Kansas City.
US 54 has a 54-mile overlap with I-40 in New Mexico.
US 24 parallels I-75 from Toledo to Detroit. I-70 runs adjacent to or on top of it from Limon, CO to Colby KS. It also parallels or follows I-70 from Lawrence, KS through Kansas City.
A few running through Georgia that I don't think have been mentioned yet: 123, 221, and 378.
Quote from: zzcarp on June 14, 2019, 02:09:54 AM
Quote from: Konza on June 14, 2019, 01:30:33 AM
How about US Highways 24, 54, and 56?
US 56 may count as there is only a 17-mile overlap w/I-35 in Kansas City.
US 54 has a 54-mile overlap with I-40 in New Mexico.
US 24 parallels I-75 from Toledo to Detroit. I-70 runs adjacent to or on top of it from Limon, CO to Colby KS. It also parallels or follows I-70 from Lawrence, KS through Kansas City.
The standard is 15 percent. For US 54, that would be 180 miles, so according to the standard, it qualifies. Plus in the segment you mention, I-40 is headed from Amarillo to Albuquerque. Us 54 is headed from Wichita to El Paso. The routes are crossing, albeit very gradually.
For US 24, the concurrency with I-70 is about 135 miles from Limon to Colby. Rand McNally says it's 62 miles from Kansas City to Topeka. It's 59 miles from Detroit to Toledo, although the US 24 concurrency is not that long as US 24 heads up Telegraph Road. I-75 was actually concurrent with US 25 here before it was decommissioned. That totals about 255 miles, and the standard here would be 231, so it doesn't qualify. I would, however, also make the argument that the control cities for I-70 west of Topeka would be Topeka and Denver, while the control cities for US 24 would be Topeka and Colorado Springs. There are three pretty much parallel US highways in western Kansas and eastern Colorado; 24, 36 , and 40. I-70 could just as easily have followed one of the other two in this stretch, and does follow US 40 for most of it.
Speaking of US 36, it's 1414 miles long. It's concurrent with I-70 for 37 miles in and east of Denver, and with I-72 for 133 miles from the Mississippi River to the west edge of Decatur. That's less than 15% of the route. That may change, of course, if I-72 is extended very far into Missouri.
Quote from: Konza on June 14, 2019, 05:07:48 PM
Speaking of US 36, it's 1414 miles long. It's concurrent with I-70 for 37 miles in and east of Denver, and with I-72 for 133 miles from the Mississippi River to the west edge of Decatur. That's less than 15% of the route. That may change, of course, if I-72 is extended very far into Missouri.
Not much more length, but US 36 is concurrent with I-465 (and everything else) around Indy, then parallels I-69 from 465 to somewhere around Pendleton-Anderson, before US 36 continues east & I-69 turns more northward
Surprised that US 83 hasn't been mentioned. Only about 3% of its entire nearly 2000 mile route is concurrent with interstates, and even then those occurrences are incidental and not a true parallel (i.e. US 58 and I-81).
Quote from: Kulerage on June 18, 2019, 06:41:47 PM
Surprised that US 83 hasn't been mentioned. Only about 3% of its entire nearly 2000 mile route is concurrent with interstates, and even then those occurrences are incidental and not a true parallel (i.e. US 58 and I-81).
Although it's only 48 miles long, the entire length of I-2 is concurrent with US 83 in south Texas, which might be enough to disqualify it for this thread.
Quote from: US 89 on June 18, 2019, 07:25:32 PM
Quote from: Kulerage on June 18, 2019, 06:41:47 PM
Surprised that US 83 hasn't been mentioned. Only about 3% of its entire nearly 2000 mile route is concurrent with interstates, and even then those occurrences are incidental and not a true parallel (i.e. US 58 and I-81).
Although it's only 48 miles long, the entire length of I-2 is concurrent with US 83 in south Texas, which might be enough to disqualify it for this thread.
That's a significant overlap, though when you consider US-83 is nearly 2,000 miles long, only about 3% parallel / concurrent with interstate highways, which is well within the 15% maximum prescribed for this thread.
Quote from: US 89 on June 18, 2019, 07:25:32 PM
Quote from: Kulerage on June 18, 2019, 06:41:47 PM
Surprised that US 83 hasn't been mentioned. Only about 3% of its entire nearly 2000 mile route is concurrent with interstates, and even then those occurrences are incidental and not a true parallel (i.e. US 58 and I-81).
Although it's only 48 miles long, the entire length of I-2 is concurrent with US 83 in south Texas, which might be enough to disqualify it for this thread.
It qualifies, IMO. I-2 is what doesn't qualify; it's a bulls*** Interstate.
Quote from: wanderer2575 on June 18, 2019, 07:47:12 PM
I-2 is what doesn't qualify; it's a bulls*** Interstate.
Until I-69E is completed anyways, it is. Or I-2 is extended to Laredo connecting w/ I-35. I-2 works though, once connected to another interstate highway
(that connects to the system, connecting to I-69E or I-69C doesn't qualify it)I wondered how they even got that stretch signed to begin with. Did they take the fact in order to sign an interstate highway, it must connect to another interstate - then decide let's apply for all three of them at once so they'll connect to each other - essentially a loophole around the system?
Quote from: sprjus4 on June 18, 2019, 07:49:46 PM
Quote from: US 89 on June 18, 2019, 07:25:32 PM
I-2 is what doesn't qualify; it's a bulls*** Interstate.
It was
wanderer2575 that said that, not
US 89.
US 441 is one highway that goes where the interstates go, but only parallels I-75 for a short distance from Ocala to Lake City. Otherwise its it own independent highway. In Georgia it runs nowhere near any interstate, but I-75, I-95, and I-985 will get you from one end of the state to the other along it.
If anyone does use that road from end to end it most likely will be one of us just to say we clinched it. Although, when I clinch it someday it will be most likely in pieces as I have no desire to follow it from the FL line to the NC line as I have done large segments of it already.
If I do a route lengthwise in the Peach State it will be most likely US 27 as that one is far from any freeway and would create the ultimate challenge of going from end to end on a surface road.
Speaking of US 27, since it was truncated now pretty much of it is along no interstate. Some may argue in Florida it has I-75, but really nowhere near it except near Miami where I-75 comes near for about 20 miles of it from Andytown to Hialeah.
Quote from: roadman65 on June 18, 2019, 08:27:37 PM
I-75, I-95, and I-985 will get you from one end of the state to the other along it.
You mean I-85, right?
Quote from: zzcarp on June 14, 2019, 02:09:54 AM
Quote from: Konza on June 14, 2019, 01:30:33 AM
How about US Highways 24, 54, and 56?
US 56 may count as there is only a 17-mile overlap w/I-35 in Kansas City.
US 54 has a 54-mile overlap with I-40 in New Mexico.
US 24 parallels I-75 from Toledo to Detroit. I-70 runs adjacent to or on top of it from Limon, CO to Colby KS. It also parallels or follows I-70 from Lawrence, KS through Kansas City.
I think US-24 paralleling I-75 is just a coincident of where each highway is at that point. Long haul it doesn't as the two split and run different directions after Toledo. I always wondered why US-24 ran north and south, Michigan seems to love that kind of thing.
US 206.
And I would second US 209.
Quote from: Flint1979 on June 20, 2019, 12:56:08 PM
Quote from: zzcarp on June 14, 2019, 02:09:54 AM
Quote from: Konza on June 14, 2019, 01:30:33 AM
How about US Highways 24, 54, and 56?
I always wondered why US-24 ran north and south, Michigan seems to love that kind of thing.
Have you seen the direction of US-24 in Michigan?
That last line is mine. I screwed up the quote somehow.
I have US-24 clinched from Clarkston, MI to Fort Wayne, IN. It's just strange that it takes a north south route in Michigan. After Toledo it runs correctly.
Quote from: Flint1979 on June 21, 2019, 06:37:19 AM
I have US-24 clinched from Clarkston, MI to Fort Wayne, IN. It's just strange that it takes a north south route in Michigan. After Toledo it runs correctly.
It does the same at the west terminus in Colorado, geography doesn't help keep US 24 straight at either terminus.
Quote from: Max Rockatansky on June 21, 2019, 11:57:25 AM
Quote from: Flint1979 on June 21, 2019, 06:37:19 AM
I have US-24 clinched from Clarkston, MI to Fort Wayne, IN. It's just strange that it takes a north south route in Michigan. After Toledo it runs correctly.
Lol so in reality it has two northern terminus. For the most part I guess it does run right.
It does the same at the west terminus in Colorado, geography doesn't help keep US 24 straight at either terminus.
Believe it or not, US 50 is concurrent with several interstates, but for less than 15% of its total length of 3017 miles!
Quote from: US 89 on June 18, 2019, 07:25:32 PM
Quote from: Kulerage on June 18, 2019, 06:41:47 PM
Surprised that US 83 hasn't been mentioned. Only about 3% of its entire nearly 2000 mile route is concurrent with interstates, and even then those occurrences are incidental and not a true parallel (i.e. US 58 and I-81).
Although it's only 48 miles long, the entire length of I-2 is concurrent with US 83 in south Texas, which might be enough to disqualify it for this thread.
I... forgot about that
stupid interstate. Well, I redid the math and even with the addition of Interstate 2, US 83 is still well-within the 15% threshold.
Quote from: MikieTimT on June 12, 2019, 12:07:05 PM
US-412 doesn't. In fact, I don't think any of the US 400 series does. Arguably, at least one segment of US-412 could eventually become an Interstate, but that would take some political and financial will that doesn't currently exist.
I don't see US 412 having any traction in TN in updating to an interstate. A portion of it is on I-155 and I-40 anyway.
Would US 59 and 290 count? The former probably doesn't anymore cause of i-69.
There's also US 96
US 33
US 35
No mention so far of U.S. 15 (S.C., N.C., Va., Md., Pa. and N.Y.).
Yes, it has a short concurrency with I-95 near its southern terminus in South Carolina to cross Lake Marion, another relatively short concurrency with I-85 north of Durham, and north of Williamsport in Pennsylvania the road is signed FUTURE I-99, and it is signed I-99 in New York, but those are recent developments, and for the most part the road goes its own way (it once went to Rochester, N.Y. and I have been on the part of U.S. 15 in New York that is no more).
Quote from: cpzilliacus on October 29, 2020, 11:51:05 AM
No mention so far of U.S. 15 (S.C., N.C., Va., Md., Pa. and N.Y.).
Yes, it has a short concurrency with I-95 near its southern terminus in South Carolina to cross Lake Marion, another relatively concurrency with I-85 north of Durham, and north of Williamsport in Pennsylvania the road is signed FUTURE I-99, and it is signed I-99 in New York, but those are recent developments, and for the most part the road goes its own way (it once went to Rochester, N.Y. and I have been on the part of U.S. 15 in New York that is no more).
Back in the days of Interstates posted at 55 mph, I certainly used US-15 from Culpeper, Virginia to Sanford, North Carolina and beyond as a viable parallel route to I-95 to get from Washington, DC to Fayetteville and Florence. After dark, the trip was only about an hour longer and much more predictable. For some reason, I never tried this as a northbound alternative, preferring to stick to the east side of I-95 on those trips.
Quote from: Dirt Roads on October 29, 2020, 12:14:21 PM
Back in the days of Interstates posted at 55 mph, I certainly used US-15 from Culpeper, Virginia to Sanford, North Carolina and beyond as a viable parallel route to I-95 to get from Washington, DC to Fayetteville and Florence. After dark, the trip was only about an hour longer and much more predictable. For some reason, I never tried this as a northbound alternative, preferring to stick to the east side of I-95 on those trips.
The only issue to be aware of with U.S. 15 in Virginia is speed limit enforcement.
In particular the municipalities of Gordonsville, Orange and Leesburg - and overall, it's not a good idea to speed in Virginia.
Quote from: cabiness42 on October 29, 2020, 07:21:32 AM
US 33
US 35
I can't believe I didn't think about US 33 for this thread given the fact that I lived very close to this road TWICE and used to drive it everyday :banghead:
Routes that enter Kentucky that would qualify: US 23 (I don't count the late addition of I-26 as a disqualifying factor), US 27, US 62, US 68, US 79, US 119, US 127, US 150, US 231 (again, the new addition of I-165 into the system doesn't count), US 421, US 431, US 460 in its current iteration, US 641. Some of these have brief encounters, either in or out of the state, but overall they weren't supplanted by interstates.
Not qualifying: US 25, US 31, US 41, US 42, US 51, US 60. For each of these routes, much of the through-route function was replaced by interstates. For some, such as US 41 and US 51, that doesn't occur in Kentucky, but elsewhere in the state. (Again, not counting the late addition of I-69 and future I-169 into the system where US 41 is concerned).
I'm not sure where to include US 45 because I'm not familiar enough with its relationships to interstates in the Chicago area and Wisconsin. Through most of Illinois and on south, however, it does not parallel an interstate.
^ I would disqualify US 45 because it parallels I-57 between Effingham and Kankakee. That's about 150 miles of eastern Illinois.
I would say in TN US 641, US 51, US 45, US 129, US 412, US 441 and honorable mention goes to the segment of US 70S from Murfreesboro to Sparta. US 70S swings away from Interstate highways to serve cities not otherwise served by the Interstate system.
Wouldn't it be the other way around? Interstate highways that don't parallel any US highways. The US highways were there first.
Quote from: Flint1979 on November 04, 2020, 07:38:32 AM
Interstate highways that don't parallel any US highways.
You're going to have a hard time finding a mainline interstate highway that doesn't run parallel to any US highways.
Quote from: sprjus4 on November 04, 2020, 10:23:33 AM
Quote from: Flint1979 on November 04, 2020, 07:38:32 AM
Interstate highways that don't parallel any US highways.
You're going to have a hard time finding a mainline interstate highway that doesn't run parallel to any US highways.
In their entirety, perhaps. But even there, I-335 KS and the eastern versions of I-86 and I-88 all qualify. And a number of individual segments of other Interstates don't run parallel. Off the top of my head, most of I-5 between the Grapevine and Sacramento, and I-93 from Franconia Notch into Vermont.