AARoads Forum

Regional Boards => Mid-Atlantic => Topic started by: roadman65 on May 11, 2015, 07:34:07 PM

Title: Why was VA 168 truncated to Norfolk?
Post by: roadman65 on May 11, 2015, 07:34:07 PM
I was always wondering why VA 168 was renumbered to VA 143 on the VA Peninsula to become co-signed with I-64 when the interstate got built to later get unsigned? 

To me if it makes no sense as they had to go through the trouble of renumbering all of VA 168 west of the HRBT, then resign it with I-64 at the same time which then later had to take down the 168 shields along I-64.

For all of this they should have kept VA 168 all along Victoria Blvd, Jefferson Avenue, and the Merrimack Trail and maybe just truncated it to Camp Peary as the sign changes west of there were being done with the freeway construction as that is the only original part of VA 168 that was altered.  The the VA 30 is only a short distance where a change in route number only effected a couple of signs considering that the current VA 30/ US 60 intersection was redone anyway (remember VA 168Y, connected former VA 168 with US 60 with VA 168 not even touching US 60 there).
Title: Re: Why was VA 168 truncated to Norfolk?
Post by: froggie on May 11, 2015, 09:55:48 PM
With the coming of I-64, the two sides functionally and effectively became different routes, so there was really no need to keep the same route number.
Title: Re: Why was VA 168 truncated to Norfolk?
Post by: wdcrft63 on May 11, 2015, 11:13:32 PM
The weird thing is that 168 was extended across Hampton Roads to incorporate the former VA 170, and this led NC to renumber NC 170 to NC 168. Then the original 168 was renumbered to 143. They could have put the 170 shields back south of Hampton Roads and left 168 on the Peninsula side!
Title: Re: Why was VA 168 truncated to Norfolk?
Post by: Mapmikey on May 12, 2015, 06:59:47 AM
Although VA 168 could certainly have been removed from I-64 sections sooner than it actually was, there was a time when the designation might have been needed, as the FHWA tried to get Virginia to drop I-64 between I-664 and I-564 from the interstate system in 1968.

It appears the CTB briefly had VA 168 only intending to end in South Norfolk but decided to collaborate with NC (who actually renumbered their side first) as a natural extension of 168.  There are no other CTB references I can find that show this interim extension actually happened in the field prior to extension to NC.  Also note that VA 168 had already been extended over Hampton Roads in 1945 via the Newport News ferry.

From pg. 4 of http://www.ctb.virginia.gov/meetings/minutes_pdf/CTB-11-1957-02.pdf -
ROUTE 168 is designated via the Bridge-Tunnel crossing Hampton Roads and through Norfolk and South Norfolk replacing present Route 170, and whereas due to this routing of Route 168 through the cities it is also practicable to continue Route 168 over present ROUTE 170 in Norfolk County to the North Carolina Line, and whereas present ROUTE 170 continuing from Virginia into North Carolina has been approved by the North .Carolina Highway Commission on November 4, 1957 for its designation as Route 168; NOW, THEREFORE, BE IT RESOLVED, that present Route 170 in Norfolk County be renumbered to carry Route number 168, from the south corporate limits of south Norfolk south to the NORTH CAROLINA STATE Line; also the portion of present Route 168 leading from the east corpor ate limits of Norfolk east to an intersection with Route 60. in Princess Anne County be renumbered to carry Route 170. Motion carried.

Mapmikey