AARoads Forum

National Boards => General Highway Talk => Topic started by: Dirt Roads on January 22, 2023, 09:53:33 PM

Title: Route Numbering Coincidences
Post by: Dirt Roads on January 22, 2023, 09:53:33 PM
The 2004 rerouting of US-33 across the Ravenswood Bridge from Ohio into West Virginia has an unusual coincidence.  The route from Ravenswood -to- I-77 became a multiplex with WV-2, which replaced WV-56 on that segment after Gov. Rockefeller promised a four-lane road from Ravenswood -to- Parkersburg (and delivered on the promise by widening the two-mile segment of truncated WV-56.  But WV-56 was renumbered from WV-33 due to that same number being used closeby as part of the U.S. Highway System (along with the then State Road Commission having a rule against duplicate numbers).  It is total coincidence that this segment of US-33 was once-upon-a-time WV-33.

There have been several other threads on specific types of coincidences, but I couldn't find one like this.  I'm certainly open to a discussion of all sorts of numbering coincidences and oddities.
Title: Re: Route Numbering Coincidences
Post by: TheHighwayMan3561 on January 23, 2023, 02:29:29 PM
In part of Minnesota and all of Wisconsin, their original state routes 12 were replaced by US 12.

MN 317 has no relation to its connecting North Dakota route, ND 17.
Title: Re: Route Numbering Coincidences
Post by: Bruce on January 23, 2023, 03:27:45 PM
WA 9 and BC 9 are unrelated routes that are about 25 miles apart from eachother.

WA 31 and BC 31 occupy the same general slice of north-south territory despite the numbering systems not lining up elsewhere.

BC used to number their highways based on corresponding numbers in the U.S., but then Washington changed their numbering scheme. As a result, most state routes change to a different number at the border, so these are coincidences.
Title: Re: Route Numbering Coincidences
Post by: Flint1979 on January 23, 2023, 06:22:59 PM
In Michigan US-16 replaced M-16. US-16 has since been replaced by I-96.
Title: Re: Route Numbering Coincidences
Post by: Dirt Roads on January 23, 2023, 07:00:16 PM
Quote from: Bruce on January 23, 2023, 03:27:45 PM
WA 9 and BC 9 are unrelated routes that are about 25 miles apart from eachother.

WA 31 and BC 31 occupy the same general slice of north-south territory despite the numbering systems not lining up elsewhere.

BC used to number their highways based on corresponding numbers in the U.S., but then Washington changed their numbering scheme. As a result, most state routes change to a different number at the border, so these are coincidences.

Cool.  These two are closely related to this thread:  https://www.aaroads.com/forum/index.php?topic=27458.msg2525189#msg2525189
Title: Re: Route Numbering Coincidences
Post by: Max Rockatansky on January 23, 2023, 07:02:07 PM
AZ 95 south of Quartzsite became part of US 95.  I never found evidence in the AASHTO database that AZ was trying to establish a routing for US 95 before it was officially extended.
Title: Re: Route Numbering Coincidences
Post by: flan on January 23, 2023, 07:23:37 PM
Quote from: TheHighwayMan394 on January 23, 2023, 02:29:29 PM
MN 317 has no relation to its connecting North Dakota route, ND 17.

Wait really? I'd just assumed they chose legislative route no. 317 specifically for that connection.
Title: Re: Route Numbering Coincidences
Post by: kurumi on January 23, 2023, 07:57:45 PM
Main Street in East Hartford, CT near the Pratt & Whitney plant was originally part of New England Interstate Route 17; then later on was part of (unrelated) state route 17. In between, the designation was, at various times, CT 2, CT 2/15, and CT 2/17.

This stretch of road is now unposted, but state-maintained, SR 517. (CT loves to "rhyme" when a designation is changed, so the 17 -> 517 is likely more deliberate than coincidental.)
Title: Re: Route Numbering Coincidences
Post by: hbelkins on January 23, 2023, 08:23:12 PM
Before US 460 was commissioned in Kentucky, KY 40 ran west from Paintsville through Salyersville, West Liberty, Frenchburg, Mt. Sterling, Paris, and Georgetown, before meeting up with US 60 to continue on to Louisville. When US 460 was commissioned, KY 40 was truncated to Paintsville. When the new alignment of US 460 between Paintsville and Salyersville opened in the mid-1970s, Kentucky could have extended KY 30 east along the route to Paintsville. It instead brought back the KY 40 designation for the old segment from Paintsville through Oil Springs to Salyersville.
Title: Re: Route Numbering Coincidences
Post by: NWI_Irish96 on January 23, 2023, 08:23:52 PM
IN 6 was replaced by US 6
Title: Re: Route Numbering Coincidences
Post by: Max Rockatansky on January 23, 2023, 08:27:28 PM
When the California Sign State Routes were plotted during 1934, CA 6 was selected for the Olympic Boulevard corridor in the Los Angeles Area.  CA 6 was eliminated during 1937 to make way for US 6 being extended to Long Beach. US 6 would have touched CA 6 in downtown Los Angeles had both numbers remained.  CA 6 was renumbered to the second iteration of CA 26.  This likely set the precedent to avoid Sign Route duplications which became such a big deal later on with the 1964 Renumbering and I-238.  I does make one wonder what would have happened if US 6 went the Bay Area via Tioga Pass instead of Long Beach?  Both proposals were submitted at the same time to AASHO.
Title: Re: Route Numbering Coincidences
Post by: MATraveler128 on January 23, 2023, 08:28:31 PM
MA/NH 28 was once New England Route 28.
Title: Re: Route Numbering Coincidences
Post by: Rothman on January 23, 2023, 08:38:48 PM
Quote from: BlueOutback7 on January 23, 2023, 08:28:31 PM
MA/NH 28 was once New England Route 28.
So were a decent number of other routes that don't change across state lines in New England.
Title: Re: Route Numbering Coincidences
Post by: Dirt Roads on January 23, 2023, 08:48:01 PM
There's a short 1-mile concurrency of WV-5 and US-33 in Glenville, West Virginia.  Most of the original WV-5 became US-33 in 1937, but the next year the original WV-35 was renumbered to WV-5.  So this section in downtown Glenville was part of WV-5 before and after the renumbering.  (This may have not been coincidental, but it is certainly is an oddity).
Title: Re: Route Numbering Coincidences
Post by: mgk920 on January 24, 2023, 11:17:12 AM
Well, I-35 and WI 35 are right across the MN/WI state line from each other.

Mike
Title: Re: Route Numbering Coincidences
Post by: Flint1979 on January 24, 2023, 07:50:42 PM
Another one in Michigan is US-10 replaced M-10 in the beginning, then M-10 replaced US-10 on the Lodge Freeway when US-10 was routed on the Lodge. Historically US-10 ran on Woodward Avenue which is where M-10 was replaced with US-10.
Title: Re: Route Numbering Coincidences
Post by: zachary_amaryllis on January 25, 2023, 06:36:20 AM
US 6  is 6th Ave, for a good part of Denver.
Title: Re: Route Numbering Coincidences
Post by: Henry on January 26, 2023, 08:12:52 PM
MO 66, KS 66, OK 66, AZ 66 and CA 66 are all former alignments of US 66.
Title: Re: Route Numbering Coincidences
Post by: Max Rockatansky on January 26, 2023, 08:15:50 PM
Legislative Route Number 189 was renumbered to California State Route 189 as part of the 1964 State Highway Renumbering.
Title: Re: Route Numbering Coincidences
Post by: Mapmikey on January 26, 2023, 08:38:30 PM
Quote from: Dirt Roads on January 23, 2023, 08:48:01 PM
There's a short 1-mile concurrency of WV-5 and US-33 in Glenville, West Virginia.  Most of the original WV-5 became US-33 in 1937, but the next year the original WV-35 was renumbered to WV-5.  So this section in downtown Glenville was part of WV-5 before and after the renumbering.  (This may have not been coincidental, but it is certainly is an oddity).

South Carolina has one of these...

The SC 8-81 overlay northeast of Anderson.

SC 81 was the first routing of US 29.  Prior to 1927, US 29 was the original SC 8.  The current SC 8 was not a state highway.  In 1928, SC 8 was dropped from US 29 and a new SC 8 was christened which included its current overlay of the original SC 8.
Title: Re: Route Numbering Coincidences
Post by: Max Rockatansky on January 26, 2023, 08:42:59 PM
What had been planned as AZ 89 between Flagstaff and Prescott was renumbered to the the iteration of AZ 79.  This quickly became US Route 89A after the highway through Oak Creek Canyon was completed and is now AZ 89A. 

When the Arizona State Routes were being planned there was no US 66 as it was still US 60.  That being the case AZ 66 was planned to follow the Apache Trail.  US 60 ultimately became US 66 in the final version of the US Route System.  This spurred the state to change AZ 66 to AZ 88. 
Title: Re: Route Numbering Coincidences
Post by: Max Rockatansky on January 26, 2023, 08:44:40 PM
As the Sign State Routes were being plotted in California during 1934 there was a CA 95 and a CA 195.  Both routes before the end of the decade would become part of the US Route 95 family of highways.  CA 95 would become part of US 395 and CA 195 became part of US 95. 
Title: Re: Route Numbering Coincidences
Post by: Takumi on January 26, 2023, 08:53:35 PM
VA 13 used to be VA 13.
Title: Re: Route Numbering Coincidences
Post by: Dirt Roads on January 26, 2023, 09:20:26 PM
Quote from: Takumi on January 26, 2023, 08:53:35 PM
VA 13 used to be VA 13.

Having relatives there, I understood this completely.  Except that US-60 was only one year old when it bypassed Powhatan and Tobaccoville and VA-13 was restored over the old segment in 1934.  Back in those days, all the locals still called it "Root There-teen".   
Title: Re: Route Numbering Coincidences
Post by: Dirt Roads on January 26, 2023, 09:24:31 PM
Quote from: Max Rockatansky on January 26, 2023, 08:42:59 PM
What had been planned as AZ 89 between Flagstaff and Prescott was renumbered to the the iteration of AZ 79.  This quickly became US Route 89A after the highway through Oak Creek Canyon was completed and is now AZ 89A. 

I should have remembered this one.  That's one that I've driven over a large segment.  Plus, Jerome is pronounced like Durham.
Title: Re: Route Numbering Coincidences
Post by: Big John on January 26, 2023, 09:25:29 PM
In Ontario, roadway "Highway 7" coincides with a bannered route 7.
Title: Re: Route Numbering Coincidences
Post by: TheHighwayMan3561 on January 27, 2023, 03:23:53 AM
Quote from: Henry on January 26, 2023, 08:12:52 PM
MO 66, KS 66, OK 66, AZ 66 and CA 66 are all former alignments of US 66.

That's not really a coincidence, though, that was a deliberate choice by those states.
Title: Re: Route Numbering Coincidences
Post by: formulanone on January 29, 2023, 10:11:51 AM
Part of Iowa's Highway 78 is named for Jay Norwood "Ding" Darling...

(https://live.staticflickr.com/1869/44320338871_d0247bfe6c_b.jpg) (https://flic.kr/p/2awrjDD)

...since he was involved with the National Wildlife Federation, the "Ding" Darling National Wildlife Refuge on Sanibel Island was named for him.

It's almost off Florida State Road 78 (https://www.google.com/maps/@26.5585028,-82.1129791,11.88z), but too good to pass up.
Title: Re: Route Numbering Coincidences
Post by: KCRoadFan on February 01, 2023, 09:13:31 AM
This thread seems redundant - for me, it brings to mind one I created myself a year-and-a-half ago:

https://www.aaroads.com/forum/index.php?topic=29915.0

How do I merge two threads?
Title: Re: Route Numbering Coincidences
Post by: hotdogPi on February 01, 2023, 09:16:47 AM
Quote from: KCRoadFan on February 01, 2023, 09:13:31 AM
This thread seems redundant - for me, it brings to mind one I created myself a year-and-a-half ago:

https://www.aaroads.com/forum/index.php?topic=29915.0

How do I merge two threads?

This thread does not appear to be a duplicate. The OP's post was entirely in one state.
Title: Re: Route Numbering Coincidences
Post by: dantheman on February 05, 2023, 02:20:09 PM
Quote from: Rothman on January 23, 2023, 08:38:48 PM
Quote from: BlueOutback7 on January 23, 2023, 08:28:31 PM
MA/NH 28 was once New England Route 28.
So were a decent number of other routes that don't change across state lines in New England.

While most of these were directly converted from the old New England-wide route numbering system straight to state routes, the old New England Route 1 more-or-less became US 1. That was coincidental that a number from one grid system worked in a different grid system, especially because the New England system had odd numbers on E-W routes and the US system went with odd numbers on N-S routes. Good thing New England's shoreline goes NE-SW.

While not the same type of coincidence, it's funny to me that New England 3 mostly became US 6 and New England 6 mostly became US/MA 3.
Title: Re: Route Numbering Coincidences
Post by: sbeaver44 on February 05, 2023, 07:34:46 PM
As a kid, my only exposure to New York State was fall trips to Watkins Glen, and probably 90% otherwise was in PA.  Since Pennsylvania often has a parent-child relationship between state routes (eg, PA 74, PA 174, and PA 274 being "related" ), and NY 14 and NY 414 intersect in Watkins Glen, I assumed they were similar.  Only many years later did I realize NYS doesn't tend to do this in the same way (more using letter suffixes like NY 14A, NY 96B, etc). NY 414 is simply a renumbered NY 44 that happens to intersect NY 14.  I guess the renumbering was because of US 44?  New York doesn't seem to care about duplicate numbers usually.
Title: Re: Route Numbering Coincidences
Post by: Declan127 on February 05, 2023, 09:13:44 PM
Quote from: sbeaver44 on February 05, 2023, 07:34:46 PM
As a kid, my only exposure to New York State was fall trips to Watkins Glen, and probably 90% otherwise was in PA.  Since Pennsylvania often has a parent-child relationship between state routes (eg, PA 74, PA 174, and PA 274 being "related" ), and NY 14 and NY 414 intersect in Watkins Glen, I assumed they were similar.  Only many years later did I realize NYS doesn't tend to do this in the same way (more using letter suffixes like NY 14A, NY 96B, etc). NY 414 is simply a renumbered NY 44 that happens to intersect NY 14.  I guess the renumbering was because of US 44?  New York doesn't seem to care about duplicate numbers usually.

US Routes are referenced with SR numbers (i.e. US 44 is NY 44), however interstates are given an "I" at the end (e.g. I-95 is NY 95I), so duplication is only allowed between interstates and state highways.
Title: Re: Route Numbering Coincidences
Post by: fillup420 on February 05, 2023, 09:24:41 PM
US 221, US 321, and US 421 all converge in Boone NC. i dont know of any other place that three " related"  routes all meet in one town.
Title: Re: Route Numbering Coincidences
Post by: cwf1701 on February 05, 2023, 09:29:23 PM
Quote from: Flint1979 on January 24, 2023, 07:50:42 PM
Another one in Michigan is US-10 replaced M-10 in the beginning, then M-10 replaced US-10 on the Lodge Freeway when US-10 was routed on the Lodge. Historically US-10 ran on Woodward Avenue which is where M-10 was replaced with US-10.

And let not forget M-10 was signed in Flint in the 1930s before BUS-US-10 was created. M-10 in Flint was US-10 first route thru Flint and like M-10 on Woodward, was replaced by US-10 in 1926.
Title: Re: Route Numbering Coincidences
Post by: Fredddie on February 07, 2023, 01:42:58 AM
Before 1926, what's now US 18 through Iowa and Wisconsin was Highway 19 in both states.
Title: Re: Route Numbering Coincidences
Post by: roadman65 on February 07, 2023, 02:44:37 AM
FL A1A being close to US 1 May suggest its number from that, but in reality A1A was chosen to avoid having two Route 1's near each other.

A1A was supposed to be FL 1 to fit the grid.
Title: Re: Route Numbering Coincidences
Post by: hbelkins on February 07, 2023, 12:46:59 PM
Quote from: roadman65 on February 07, 2023, 02:44:37 AM
FL A1A being close to US 1 May suggest its number from that, but in reality A1A was chosen to avoid having two Route 1's near each other.

A1A was supposed to be FL 1 to fit the grid.

In my mind, I always pictured A1A meaning "Atlantic 1 Alternate" because it ran between US 1 and the ocean.
Title: Re: Route Numbering Coincidences
Post by: Quillz on March 25, 2023, 03:52:10 PM
Quote from: Max Rockatansky on January 26, 2023, 08:44:40 PM
As the Sign State Routes were being plotted in California during 1934 there was a CA 95 and a CA 195.  Both routes before the end of the decade would become part of the US Route 95 family of highways.  CA 95 would become part of US 395 and CA 195 became part of US 95. 
CA-195 seems to have been based on it being near the border, as similar numbers were chosen for border routes. (94, 96, 98). I'm not sure why CA-95 was numbered that way, though. Maybe the logic was to have a two-digit "border" number for the LA Area, although something similar was not done for the Bay Area, unless CA-89 was supposed to serve a similar purpose.
Title: Re: Route Numbering Coincidences
Post by: ilpt4u on March 26, 2023, 10:27:27 AM
I feel like IL 145 between Harrisburg and Metropolis, in Southern IL, having both endpoints on US 45 and essentially being a rural bypass of Vienna and also a more direct route between its endpoints vs US 45, just happens to be IL 145 by coincidence.

It crosses IL 146 in Dixon Springs, IL 147 in Glendale, and the other IL 14xs are in nearby areas, so this part of Southern IL is where a 14x route should be, geographically. It just happens to act as an Alt or Bypass US 45
Title: Re: Route Numbering Coincidences
Post by: Max Rockatansky on March 26, 2023, 10:45:43 AM
Quote from: Quillz on March 25, 2023, 03:52:10 PM
Quote from: Max Rockatansky on January 26, 2023, 08:44:40 PM
As the Sign State Routes were being plotted in California during 1934 there was a CA 95 and a CA 195.  Both routes before the end of the decade would become part of the US Route 95 family of highways.  CA 95 would become part of US 395 and CA 195 became part of US 95. 
CA-195 seems to have been based on it being near the border, as similar numbers were chosen for border routes. (94, 96, 98). I'm not sure why CA-95 was numbered that way, though. Maybe the logic was to have a two-digit "border" number for the LA Area, although something similar was not done for the Bay Area, unless CA-89 was supposed to serve a similar purpose.

Jumping from Route 127 to 195 in the 1934 Sign Route designations was quite the leap.  There is no way that there was going to bunch that much Sign Route infill between 127-195 out in the deserts, especially back during the 1930s.  Given there seemed to be a lot of desire around to get US 95 extended at the time it doesn't seem that surprising the DOH might try to plan for it in advance.  The ION Highway being modernized in Oregon is what held up US 95 being extended before US 395. 
Title: Re: Route Numbering Coincidences
Post by: webny99 on March 26, 2023, 06:29:10 PM
Would the numerous "404 errors" (US 404 shields) posted on NY 404 over the years count as coincidence?  :sombrero:
Title: Re: Route Numbering Coincidences
Post by: formulanone on March 28, 2023, 11:24:23 AM
Quote from: hbelkins on February 07, 2023, 12:46:59 PM
Quote from: roadman65 on February 07, 2023, 02:44:37 AM
FL A1A being close to US 1 May suggest its number from that, but in reality A1A was chosen to avoid having two Route 1’s near each other.

A1A was supposed to be FL 1 to fit the grid.

In my mind, I always pictured A1A meaning "Atlantic 1 Alternate" because it ran between US 1 and the ocean.

There was also once a G1A, which is a causeway that leads to the Gulf of Mexico (https://www.google.com/maps/@29.6977169,-84.8644941,13.02z) (now SR 300), but it was nowhere near as long as A1A.

A gulf counterpart to A1A (G41A?) would be an interesting Fictional exercise, but it require a lot more bridges to double back to Tamiami Trail, and that's not going to happen any time soon.
Title: Re: Route Numbering Coincidences
Post by: MATraveler128 on March 28, 2023, 11:51:03 AM
Massachusetts also has MA 228, which took the number from the fact that it used to be a part of MA 128 before it was cut back to the present day Braintree Split.
Title: Re: Route Numbering Coincidences
Post by: paulthemapguy on March 28, 2023, 08:11:25 PM
Quote from: ilpt4u on March 26, 2023, 10:27:27 AM
I feel like IL 145 between Harrisburg and Metropolis, in Southern IL, having both endpoints on US 45 and essentially being a rural bypass of Vienna and also a more direct route between its endpoints vs US 45, just happens to be IL 145 by coincidence.

It crosses IL 146 in Dixon Springs, IL 147 in Glendale, and the other IL 14xs are in nearby areas, so this part of Southern IL is where a 14x route should be, geographically. It just happens to act as an Alt or Bypass US 45

I get a similar impression too. I also wonder if IL-140 has a number that's coincidentally related to US40.
Title: Re: Route Numbering Coincidences
Post by: hbelkins on March 29, 2023, 12:10:42 PM
I've always thought some of Ohio's route numbers for bridges and approaches are intentionally coincidental. OH 527 is in the neighborhood of US 52 and OH 7, and OH 852 links US 52 and KY 8.
Title: Re: Route Numbering Coincidences
Post by: kphoger on March 29, 2023, 12:37:39 PM
Quote from: ilpt4u on March 26, 2023, 10:27:27 AM
I feel like IL 145 between Harrisburg and Metropolis, in Southern IL, having both endpoints on US 45 and essentially being a rural bypass of Vienna and also a more direct route between its endpoints vs US 45, just happens to be IL 145 by coincidence.

It crosses IL 146 in Dixon Springs, IL 147 in Glendale, and the other IL 14xs are in nearby areas, so this part of Southern IL is where a 14x route should be, geographically. It just happens to act as an Alt or Bypass US 45

Quote from: paulthemapguy on March 28, 2023, 08:11:25 PM
I get a similar impression too. I also wonder if IL-140 has a number that's coincidentally related to US40.

Oh wow, with route number clustering in Illinois, it had never even occurred to me that one of them might have been purposefully given its particular number within the cluster based on nearby routes.  An interesting thought exercise...

Do you know if 242's number was derived from 142?
Title: Re: Route Numbering Coincidences
Post by: paulthemapguy on March 30, 2023, 05:52:07 PM
Quote from: kphoger on March 29, 2023, 12:37:39 PM

Oh wow, with route number clustering in Illinois, it had never even occurred to me that one of them might have been purposefully given its particular number within the cluster based on nearby routes.  An interesting thought exercise...

Do you know if 242's number was derived from 142?

You clearly missed the word "coincidentally" in my original post.
Title: Re: Route Numbering Coincidences
Post by: wanderer2575 on March 31, 2023, 09:21:08 AM
In Michigan, M-137 existed long before the route about six miles east was redesignated as part of M-37.