Connecticut Route 112
State highway in Litchfield County, Connecticut, US

Route 112 is a state highway in northwestern Connecticut, running entirely within the town of Salisbury. The route serves the village of Lime Rock.
Route description
Route 112 begins at an intersection with US 44 in western part of the town of Salisbury as Interlaken Road. It heads southeast in between Lake Wononskopomuc and Lake Wononpakuk, passing by the Hotchkiss School and its associated golf course, to an intersection with Route 41 (for Salisbury center and Sharon) about 2 miles (3.2 km) later. Route 112 then continues southeast and east past Route 41 as Lime Rock Road through the village of Lime Rock and Lime Rock Park (an auto race track), crossing Salmon Creek, and eventually ending at an intersection with US 7 near the Housatonic River. The eastern terminus is a wye-junction, with Route 112 officially designated on the northern leg. The southern leg splits off from the main route about 0.1 miles (0.16 km) from the end, connecting to southbound US 7. Lime Rock Road continues north along US 7 towards Falls Village. Route 112 is a two-lane rural collector road and carries average daily traffic volumes of up to 2,900 in the Lime Rock Park area.
History
Route 112 was established as part of the 1932 state highway renumbering over an old mining road (Lime Rock Road) and remains unchanged since then.
The public source identifies “Connecticut Route 112” as state highway in Litchfield County, Connecticut, US. This brief keeps that definition visible, then builds a research path around Connecticut, Route and State.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Connecticut Route 112”, the useful work is to connect “state highway in Litchfield County, Connecticut, US” to the records capable of establishing context and consequence.
Place names and jurisdictional language are key evidence: both can reveal earlier catalogue descriptions and overlooked record series. The source revision retrieved here is dated Jul 19, 2026. The linked authority identifier is Q2248364. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1932.
Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. 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
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Connecticut Route 112”, its source revision and the description used here.
- Expand the search: follow Connecticut Route 112 primary sources, Connecticut Route 112 archive and Connecticut 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 “Connecticut Route 112”?
- What physical evidence or contemporary plan supports the description?
- Which earlier names or jurisdictions may reveal additional records?
Search terms from this dossier
This entry incorporates text from “Connecticut Route 112” 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.