U.S. Route 13 in Virginia
highway in Virginia
U.S. Route 13 (US 13) is a north–south United States Numbered Highway established in 1926 that runs for 518 miles (834 km) from Interstate 95 (I-95) just north of Fayetteville, North Carolina, north to US 1 in Morrisville, Pennsylvania, a northeastern suburb of Philadelphia. In the U.S. state of Virginia, US 13 runs north–south through the Hampton Roads and Eastern Shore regions of the state, using the Chesapeake Bay Bridge–Tunnel to get between the two. In the Hampton Roads area, it uses Military Highway to bypass the city centers. It is most usually a four-lane highway, sometimes up to freeway or expressway standards with controlled access.
Route description
City of Suffolk
US 13 enters Virginia from North Carolina in the city of Suffolk in the Hampton Roads region, heading north on two-lane undivided Whaleyville Boulevard. The road passes through a mix of farmland and woodland with some residential and commercial development in the southern part of Suffolk, making a turn to the east in Somerton Historic District. The route curves northeast and reaches the community of Whaleyville, where it passes a mix of homes and businesses and crosses Mineral Spring Road. US 13 continues through wooded areas with some farm fields and residences, heading north before curving back to the northeast. Farther northeast, the road widens to a divided highway before it comes to an intersection with State Route 32 (SR 32). At this point, SR 32 joins US 13 for a concurrency on Carolina Road, a four-lane divided highway.
The public source identifies “U.S. Route 13 in Virginia” as highway in Virginia. This brief keeps that definition visible, then builds a research path around Route, Virginia and highway.
Why this record matters
A short description can identify a subject without explaining its stakes. For “U.S. Route 13 in Virginia”, the useful work is to connect “highway in Virginia” to the records capable of establishing context and consequence.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Mar 4, 2026. The linked authority identifier is Q4818361. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1926.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “U.S. Route 13 in Virginia”, its source revision and the description used here.
- Expand the search: follow U.S. Route 13 in Virginia primary sources, U.S. Route 13 in Virginia archive and Route research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “U.S. Route 13 in Virginia”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “U.S. Route 13 in Virginia” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.