Connecticut Yankee Council
Scouting organization in Connecticut, US
The Connecticut Yankee Council of Scouting America is located in Milford, Connecticut. It is council #072 and serves 37 towns and cities in Connecticut, including Fairfield, New Haven, and parts of Hartford counties. The present council was formed in 1998 by the merger of Quinnipiac Council (#074) and Fairfield County Council (#068).Owaneco Lodge is the Order of the Arrow lodge that serves this council.
History
In 1998, the council was formed by the merger of Quinnipiac Council and Fairfield County Council.
Organization
Connecticut Yankee Council is divided into the following districts:
Pomperaug District serves Westport, Weston, Easton, Fairfield, Monroe, Trumbull, Bridgeport and Stratford.
Powahay District serves Stamford, New Canaan, Darien, Wilton and Norwalk.
Quinnipiac District serves New Haven, East Haven, West Haven, North Haven, Branford, North Branford, Guilford, Madison, Southington, Meriden, Wallingford, Hamden, Bethany, Woodbridge, Orange and Milford.
Scatacook District serves Sherman, New Fairfield, Brookfield, Danbury, Bethel, Newtown, Ridgefield and Redding.
Camps
Connecticut Yankee Council operates two camps: Camp Sequassen in New Hartford, Hoyt Scout Reservation in Redding
Camp Sequassen
Camp Sequassen is located in New Hartford, Connecticut. It is a Scouting camp operated by the Connecticut Yankee Council and is mainly used for summer camp.
This brief starts where responsible research should: with the source description of “Connecticut Yankee Council” as scouting organization in Connecticut, US. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the history & society register because the source frames it as scouting organization in Connecticut, US. Its deeper value depends on whether names, dates, institutions and citations support that framing.
The record creator and administrative purpose are central evidence, because official documentation reflects both action and institutional priorities. The source revision retrieved here is dated Aug 16, 2026. The linked authority identifier is Q5161650. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1998.
Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. 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
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Connecticut Yankee Council”, its source revision and the description used here.
- Expand the search: follow Connecticut Yankee Council primary sources, Connecticut Yankee Council 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 Yankee Council”?
- Who created the surviving record, and for what administrative purpose?
- Which voices are present, absent or mediated by the institution?
Search terms from this dossier
This entry incorporates text from “Connecticut Yankee Council” 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.