U.S. Route 19W

U.S. Route 19W (US 19W) traverses approximately 63 miles (101 km) from Cane River, North Carolina to Bluff City, Tennessee.

This article is about the section of U.S. Route 19W. For the entire route, see U.S. Route 19.

U.S. Route 19W
Route information
Auxiliary route of US 19
Length63 mi[1] (101 km)
Existed1930–present
Major junctions
South end US 19 / US 19E in Cane River, NC
  I-26 / US 23 near Erwin, TN
North end US 11E / US 19 / US 19E near Bluff City, TN
Location
StatesNorth Carolina, Tennessee
CountiesNC: Yancey
TN: Unicoi, Carter, Washington, Sullivan
Highway system


← US 19ENCNC 20 →
← US 19ETNSR 20 →

Route description
A misspelled sign stating that trucks are "not recomended" on US 19W.

US 19W begins in western Yancey county in the community of Cane River, at the intersection of US 19/US 19E. Several signs at the beginning of the route strongly recommend truckers against using this route. The road then proceeds north through the Pisgah National Forest, connecting the communities of Elk Shoal, Ramseytown and Sioux, to the Tennessee state line (near Spivey Gap), a 22 miles (35 km) drive of frequent curves and elevation changes.

Once past the state line, the road enters the Cherokee National Forest, and is much the same for another 6.3 miles (10.1 km) to SR-352/Flag Pond Road. From Flag Pond Road, it is just 1 mile (1.6 km) to Interstate 26 (I-26), where US 19W merges with the interstate to Johnson City. US 19W overlaps with I-26/US 23 from exit 43 (Hill Road) to exit 20 (Roan Street). There it leaves I-26 and continues north on the Bristol Highway, overlapped with US 11E, for 9.4 miles (15.1 km), after which it reconnects with US 19E to reform US 19 near Bluff City.

History

Established in 1930, US 19 was split at Cane River into US 19E and US 19W. US 19E follows the original routing via Spruce Pine and Elizabethton to Bluff City. US 19W was rerouted with US 23 and NC 692 into Tennessee, then through the cities of Erwin and Johnson City, before rejoining US 19E in Bluff City. In late 1934, NC 692 was dropped along the route; then in 1952, US 23 abandoned US 19W in North Carolina by rerouting west through Faust and Wolf Laurel, meeting back at Ernestville. In 1984, US 19 was realigned on a straighter path in Yancey County; US 19W was thus extended .4 miles (0.64 km).[2][3]

North Carolina Highway 692

North Carolina Highway 692
LocationCane River, NC–TN state line
Length21.6 mi[4] (34.8 km)
Existed1923–1930

North Carolina Highway 692 (NC 692) was established in 1923 as new primary routing to Tennessee; NC 692 was the original highway number from Cane River to Spivey Gap. In 1929, NC 692 was truncated at Sioux, replaced by an extension of NC 19 from Bakersville. In 1930, US 19W and US 23 were overlapped on the remaining section of NC 692. In late 1934, NC 692 was decommissioned.[5]

Junction list
StateCountyLocationmi[1]kmDestinationsNotes
North CarolinaYanceyCane River0.00.0 US 19 south / US 19E north – Asheville, BurnsvilleUS 19 splits into US 19E and US 19W; southern terminus
​15.124.3Huntdale Road – Huntdale
 21.9
0.0		35.2
0.0		North Carolina–Tennessee state line
TennesseeUnicoiErnestville6.310.1 SR 352 west (Flag Pond Road) – Flag PondEastern terminus of SR 352
Temple Hill7.512.1 I-26 east / US 23 south – AshevilleEast end of I-26 and south end of US 23 overlap
See Interstate 26 (exits 43 to 20)
WashingtonJohnson City31.049.9 I-26 west / US 23 north / US 11E south (Roan Street / SR 34) – KingsportWest end of I-26, south end of US 11E/SR 34, north end of US 23 overlap
31.550.7 SR 36 north (North Roan Street) – Boones Creek, KingsportNorth end of SR 36 overlap
32.051.5 SR 381 south (State of Franklin Road) – KingsportNorthern terminus of SR 381
SullivanBluff City41.066.0 US 11E north / US 19 north (SR 34) / US 19E south (SR 37) – Bristol, Bluff City, ElizabethtonNorthern terminus of US 19E and 19W; 19E and 19W come together to form US 19
1.000 mi = 1.609 km; 1.000 km = 0.621 mi
gollark: ```-------------------- ----- ----- ----- -----sha1-id False False False Falsesha1-newline False False False Falsesha1-bad_newline False False False Falsesha256-id False False False Falsesha256-newline False False False Falsesha256-bad_newline False False False Falsesha3_256-id False False False Falsesha3_256-newline False False False Falsesha3_256-bad_newline False False False Falsesha3_512-id False False False Falsesha3_512-newline False False False Falsesha3_512-bad_newline False False False Falsesha224-id False False False Falsesha224-newline False False False Falsesha224-bad_newline False False False Falsesha512-id False False False Falsesha512-newline False False False Falsesha512-bad_newline False False False Falsesha3_384-id False False False Falsesha3_384-newline False False False Falsesha3_384-bad_newline False False False Falsesha3_224-id False False False Falsesha3_224-newline False False False Falsesha3_224-bad_newline False False False Falsesha384-id False False False Falsesha384-newline False False False Falsesha384-bad_newline False False False False-------------------- ----- ----- ----- -----```you.
gollark: Come to think of it, it might just be comparing *pairs* via some hashing thing and not be a total ordering, but I doubt it.
gollark: I used highly advanced coding and algorithms™ to try a bunch of algorithms to see if any of them put the list in the right order.
gollark: Maybe there could be multiple hashing algorithms in use, oh bεes.
gollark: Okay, not even weird variants of SHA2 with different lengths appear to work.

See also

References
  1. Google (2010-10-31). "US 19W" (Map). Google Maps. Google. Retrieved 2010-10-31.
  2. "NCRoads.com: US 19". Retrieved 2010-10-31.
  3. "NCRoads.com: US 19-W". Retrieved 2010-10-31.
  4. Google (July 14, 2013). "North Carolina Highway 692" (Map). Google Maps. Google. Retrieved July 14, 2013.
  5. "NCRoads.com: N.C. 692". Retrieved July 14, 2013.

KML is from Wikidata
Preceded by
North Carolina		 U.S. Route 19
US 19W
US 19E		 Succeeded by
Tennessee
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.