BETHEL, CT · Fairfield County
SANDY LANE VILLAGE CONDO. ASSN., INC. Water System
Inactive system
This water system is marked inactive in EPA’s federal records as of July 3, 2014. It is no longer an operating public water system under this PWSID, and no compliance deadlines — including the 2027 Consumer Confidence Report rule — apply to it.
If you are a resident looking for your current water provider, see water systems in Fairfield County, CT.
Data sourced from the EPA ECHO database (SDWA bulk download), last refreshed August 1, 2026. This is a record-keeping and public-information tool — it does not replace Connecticut’s official records. Always confirm current status with Connecticut before making decisions based on this information.
System facts
- System ID (PWSID)
- CT0180211
- System type
- Community Water System
- Population served
- 318
- Service connections
- 106
- Ownership
- privately owned
- Water source
- groundwater (wells)
SANDY LANE VILLAGE CONDO. ASSN., INC. is one of 799 community water systems in Connecticut in the 500 or fewer people size category, formerly serving 318 people from groundwater.
EPA's federal records list this system as inactive in 2014; the record below is historical.
As of August 1, 2026, its federal record holds 9 entries between 2010 and 2013, all of which EPA lists as closed. Nothing has been added since 2013.
Of the 9, 2 are monitoring and reporting requirements — the category that accounts for about four in five of all violations in EPA's national dataset — rather than findings about the water itself. The record involves the Radionuclides and Revised Rad Rule, the Public Notice Rule and Revised PN Rule, and inorganic chemicals.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedCombined Uranium
January 1, 2013 – March 31, 2013
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Uranium
October 1, 2012 – December 31, 2012
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
September 9, 2012 – September 17, 2012
ResolvedMonitoring, Regular
—Nitrate
July 1, 2012 – September 30, 2012
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
April 1, 2012 – June 30, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Uranium
October 1, 2011 – December 31, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
April 1, 2011 – June 30, 2011
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
February 27, 2011 – January 3, 2013
ResolvedConsumer Confidence Report Inadequate Reporting
—Consumer Confidence Rule
October 1, 2010 – November 17, 2010
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2013 – March 31, 2013 | Maximum Contaminant Level Violation, Average | Combined Uranium | Health-based | Resolved |
| October 1, 2012 – December 31, 2012 | Maximum Contaminant Level Violation, Average | Combined Uranium | Health-based | Resolved |
| September 9, 2012 – September 17, 2012 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| July 1, 2012 – September 30, 2012 | Monitoring, Regular | Nitrate | — | Resolved |
| April 1, 2012 – June 30, 2012 | Monitoring, Regular | Gross Alpha, Excl. Radon and U | — | Resolved |
| October 1, 2011 – December 31, 2011 | Maximum Contaminant Level Violation, Average | Combined Uranium | Health-based | Resolved |
| April 1, 2011 – June 30, 2011 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| February 27, 2011 – January 3, 2013 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| October 1, 2010 – November 17, 2010 | Consumer Confidence Report Inadequate Reporting | Consumer Confidence Rule | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- July 24, 2014State Public Notification received1 linked violation
- July 1, 2014State Violation/Reminder Notice1 linked violation
- July 1, 2014State Public Notification requested1 linked violation
- June 25, 2014State Compliance achieved40 linked violations
- May 27, 2014State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- April 30, 2014State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- April 30, 2014State Compliance achieved1 linked violation
- April 30, 2014State Public Notification received1 linked violation
- April 22, 2014State Public Notification requested1 linked violation
- April 22, 2014State Violation/Reminder Notice1 linked violation
- April 9, 2014State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- April 9, 2014State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- December 27, 2013State Violation/Reminder Notice1 linked violation
- December 27, 2013State Public Notification requested1 linked violation
- December 19, 2013State Violation/Reminder Notice1 linked violation
- November 25, 2013State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- October 29, 2013State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- October 29, 2013State Public Notification requested1 linked violation
- September 25, 2013State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- August 20, 2013State Public Notification received1 linked violation
- August 20, 2013State Public Notification received1 linked violation
- August 16, 2013State Compliance achieved1 linked violation
- August 5, 2013State Public Notification requested1 linked violation
- August 5, 2013State Violation/Reminder Notice1 linked violation
- July 22, 2013State Violation/Reminder Notice2 linked violations
- June 18, 2013State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- April 15, 2013State Violation/Reminder Notice1 linked violation
- April 15, 2013State Public Notification requested1 linked violation
- January 10, 2013State Public Notification requested5 linked violations
- January 3, 2013State Public Notification received1 linked violation
- January 3, 2013State Public Notification received2 linked violations
- January 3, 2013State Compliance achieved1 linked violation
- January 3, 2013State Compliance achieved1 linked violation
- January 3, 2013State Compliance achieved2 linked violations
- January 3, 2013State Public Notification received2 linked violations
- January 3, 2013State Compliance achieved2 linked violations
- January 3, 2013State Compliance achieved2 linked violations
- December 5, 2012State Compliance achieved5 linked violations
- September 30, 2012State Public Notification received2 linked violations
- August 9, 2012State Public Notification requested3 linked violations
- May 11, 2012State Public Notification received4 linked violations
- April 13, 2012State Bilateral Compliance Agreement signed65 linked violations
- March 6, 2012State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- January 9, 2012State Public Notification requested1 linked violation
- January 9, 2012State Violation/Reminder Notice1 linked violation
- January 9, 2012State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- November 14, 2011State Public Notification received1 linked violation
- October 26, 2011State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- October 26, 2011State Public Notification requested1 linked violation
- September 22, 2011State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- August 24, 2011State Public Notification received1 linked violation
- August 16, 2011State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- August 16, 2011State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- June 29, 2011State Violation/Reminder Notice1 linked violation
- June 29, 2011State Public Notification requested1 linked violation
- June 29, 2011State Public Notification requested1 linked violation
- June 29, 2011State Violation/Reminder Notice1 linked violation
- April 28, 2011State Public Notification received1 linked violation
- April 26, 2011State Public Notification received1 linked violation
- April 13, 2011State Public Notification requested1 linked violation
- April 13, 2011State Violation/Reminder Notice1 linked violation
- April 13, 2011State Public Notification requested1 linked violation
- April 13, 2011State Violation/Reminder Notice1 linked violation
- March 16, 2011State Public Notification received1 linked violation
- March 16, 2011State Compliance achieved1 linked violation
- March 8, 2011State Compliance achieved1 linked violation
- March 8, 2011State Public Notification received1 linked violation
- March 4, 2011State Violation/Reminder Notice3 linked violations
- March 4, 2011State Violation/Reminder Notice1 linked violation
- January 27, 2011State Violation/Reminder Notice1 linked violation
- January 27, 2011State Violation/Reminder Notice1 linked violation
- January 27, 2011State Public Notification requested1 linked violation
- January 27, 2011State Public Notification requested1 linked violation
- December 2, 2010State Compliance achieved2 linked violations
- December 2, 2010State Compliance achieved3 linked violations
- November 17, 2010State Compliance achieved6 linked violations
- October 28, 2010State Violation/Reminder Notice2 linked violations
- September 30, 2010State Compliance achieved1 linked violation
- September 22, 2010State Public Notification received1 linked violation
- September 21, 2010State Violation/Reminder Notice2 linked violations
- September 21, 2010State Violation/Reminder Notice2 linked violations
- September 13, 2010State Violation/Reminder Notice2 linked violations
- March 31, 2010State Compliance achieved5 linked violations
- March 30, 2010State Public Notification requested2 linked violations
- March 30, 2010State Violation/Reminder Notice1 linked violation
- February 7, 2010State Public Notification received2 linked violations
- January 11, 2010State Violation/Reminder Notice3 linked violations
- January 11, 2010State Violation/Reminder Notice2 linked violations
- December 28, 2009State Public Notification received4 linked violations
- December 24, 2009State Public Notification received1 linked violation
- October 14, 2009State Public Notification requested3 linked violations
- October 14, 2009State Violation/Reminder Notice3 linked violations
- July 14, 2009State Public Notification requested3 linked violations
- July 14, 2009State Violation/Reminder Notice2 linked violations
- March 16, 2009State Public Notification received3 linked violations
- February 9, 2009State Public Notification received3 linked violations
- January 16, 2009State Administrative/Compliance Order without penalty issued39 linked violations
- October 16, 2008State Public Notification requested6 linked violations
- October 16, 2008State Violation/Reminder Notice5 linked violations
- September 3, 2008State Compliance achieved7 linked violations
- September 3, 2008State Public Notification requested5 linked violations
- August 12, 2008State Violation/Reminder Notice5 linked violations
- April 9, 2008State Public Notification requested3 linked violations
- February 13, 2008State Public Notification received5 linked violations
- January 29, 2008State Violation/Reminder Notice2 linked violations
- January 18, 2008State Public Notification received6 linked violations
- January 18, 2008State Compliance achieved5 linked violations
- August 14, 2007State Compliance achieved6 linked violations
- July 12, 2007State Public Notification requested4 linked violations
- July 12, 2007State Violation/Reminder Notice5 linked violations
- June 20, 2007State Violation/Reminder Notice2 linked violations
- March 31, 2007State Compliance achieved4 linked violations
- January 19, 2007State Public Notification received11 linked violations
- January 19, 2007State Public Notification received1 linked violation
- January 9, 2007State Violation/Reminder Notice4 linked violations
- January 9, 2007State Public Notification requested2 linked violations
- January 9, 2007State Public Notification requested3 linked violations
- January 9, 2007State Violation/Reminder Notice3 linked violations
- December 28, 2006State Compliance achieved4 linked violations
- June 29, 2006State Compliance achieved2 linked violations
- June 29, 2006State Public Notification received2 linked violations
- June 29, 2006State Violation/Reminder Notice3 linked violations
- June 8, 2006State Public Notification requested3 linked violations
- January 9, 2006State Public Notification requested13 linked violations
- January 9, 2006State Violation/Reminder Notice2 linked violations
- December 1, 2005State Public Notification received2 linked violations
- November 15, 2005State Public Notification requested6 linked violations
- June 3, 2005State Violation/Reminder Notice27 linked violations
- November 1, 2004State Violation/Reminder Notice2 linked violations
- December 23, 2003State Public Notification received2 linked violations
- January 24, 2002State Violation/Reminder Notice5 linked violations
Last known contact on file (system is inactive)
HYATT, TRAVIS
203-790-6888
BETHEL, CT 06801