Connecticut Route 116
State highway in Fairfield County, Connecticut, US
Route 116 is a 4.24-mile-long (6.82 km) state highway entirely within Ridgefield, Connecticut that runs from the Ridgefield town center at Route 35 to the New York state line, where New York State Route 116 continues towards the hamlet of North Salem.
Route description
Route 116 begins in downtown Ridgefield, splitting off from Main Street (Route 35). While Route 35 heads northeast towards downtown Danbury, Route 116 heads northwest along North Salem Road towards the New York state line. North Salem Road travels through the more rural areas of Ridgefield. North Salem Road reaches Mamanasco Lake about 3.1 miles (5.0 km) later where it also intersects with Ridgebury Road, which leads to the Ridgebury section of town and to the old Union Carbide center in western Danbury. Route 116 then passes by the Ridgefield High School and Scotts Ridge Middle School after another 0.3 miles (0.48 km). Route 116 continues along North Salem Road for another 0.8 miles (1.3 km) where it crosses the state line and becomes New York State Route 116. For its entire length in Ridgefield, Route 116 is designated the Elizabeth M. Leonard Memorial Highway.
History
In the 1920s, the Ridgefield to North Salem route was a primary state highway designated as Highway 146. In the 1932 state highway renumbering, Highway 146 became incorporated into the newly established Route 33.
“Connecticut Route 116” enters the record as state highway in Fairfield County, Connecticut, US. Crown Archives preserves that source wording while asking what Connecticut, Route and State can confirm, complicate or overturn.
Why this record matters
“Connecticut Route 116” is worth following because a concise public description often conceals a longer documentary argument. Here, Connecticut, Route and State provides the most credible route into that argument.
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 Mar 2, 2026. The linked authority identifier is Q2248850. 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 116”, its source revision and the description used here.
- Expand the search: follow Connecticut Route 116 primary sources, Connecticut Route 116 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 116”?
- Which authority defined the place, boundary or structure at the relevant date?
- Which earlier names or jurisdictions may reveal additional records?
Search terms from this dossier
This entry incorporates text from “Connecticut Route 116” 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.