U.S. Route 730
U.S. Numbered Highway in Oregon and Washington in the United States
U.S. Route 730 (US 730) is an east–west United States Numbered Highway, of which all but 6.08 miles of its 41.78 miles (9.78 of 67.24 km) are within the state of Oregon. The highway starts in rural Morrow County in Eastern Oregon at an interchange with Interstate 84 (I-84) and US 30, located east of the city of Boardman. US 730 travels east along the Columbia River as a continuation of Columbia River Highway No. 2 into Umatilla County, intersecting I-82 and US 395 in the city of Umatilla. US 730 and US 395 form a short concurrency within the city before the highways part, and US 730 continues northeast into Washington. The highway travels through rural Walla Walla County and ends at an intersection with US 12 south of Wallula.
US 730 was created with the original US Highway System on November 11, 1926, traveling on the existing Columbia River Highway, established in 1917, from US 30 in Umatilla to US 410 south of Wallula. The Washington section of US 730 was added to the state highway system in 1923 as a branch of State Road 3, later becoming a branch of Primary State Highway 3 (PSH 3) in 1937. The highway was concurrent with US 395 from 1937 until 1985, traveling from Cold Springs Junction to US 410. US 30 was moved to a new route bypassing Umatilla and Irrigon in 1946, allowing for US 730 to be extended southwest to Boardman, later to an interchange with I-84.
Begin with the source’s own compact description: “U.S. Route 730” is u.S. Numbered Highway in Oregon and Washington in the United States. The dossier treats that line as a proposition to test through Route, Numbered and Highway, not as a finished interpretation.
Why this record matters
The phrase “u.S. Numbered Highway in Oregon and Washington in the United States” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Jan 19, 2026. The linked authority identifier is Q833230. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1926, 1917, 1923 and 1937.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. 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 730”, its source revision and the description used here.
- Expand the search: follow U.S. Route 730 primary sources, U.S. Route 730 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 730”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “U.S. Route 730” 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.