Is SUNSET COLONY required to publish a Consumer Confidence Report?

Yes. SUNSET COLONY is a community water system, and federal rules (40 CFR 141 Subpart O) require every community water system to publish a Consumer Confidence Report each year.

When is SUNSET COLONY’s next Consumer Confidence Report due?

SUNSET COLONY’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.

What is a Consumer Confidence Report?

A Consumer Confidence Report (CCR) is the annual drinking water quality report that community water systems must provide to the people they serve. It lists the contaminants detected in the system’s water during the year, where the water comes from, and how the results compare with federal limits. EPA’s revised CCR rule takes effect January 1, 2027, and the first reports in the new format are due July 1, 2027.

BRITTON, SD · Marshall County

SUNSET COLONY Water System

Consumer Confidence Report status

SUNSET COLONY must publish a Consumer Confidence Report — the annual drinking water quality report covering calendar year 2026 — by July 1, 2027.

As of August 1, 2026, EPA's federal records show no open violations for SUNSET COLONY.

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 South Dakota’s official records. Always confirm current status with South Dakota before making decisions based on this information.

System facts

System ID (PWSID): SD4602025
System type: Community Water System
Population served: 140
Service connections: 24
Ownership: privately owned
Water source: groundwater (wells)

SUNSET COLONY is one of 583 community water systems in South Dakota in the 500 or fewer people size category, serving 140 people from groundwater.

As of August 1, 2026, its federal record holds 17 entries between 1993 and 2012, all of which EPA lists as closed. Nothing has been added since 2012.

Of the 17, 4 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 inorganic chemicals and synthetic organic chemicals.

Violation history

Maximum Contaminant Level Violation, Average
Health-based
Arsenic
October 1, 2012 – December 31, 2012
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2012 – September 30, 2012
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2012 – March 31, 2012
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2011 – March 31, 2011
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
October 1, 2010 – December 31, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2010 – September 30, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2010 – March 31, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2009 – September 30, 2009
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2008 – September 30, 2008
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
October 1, 2007 – December 31, 2007
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2007 – September 30, 2007
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2007 – June 30, 2007
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2007 – March 31, 2007
Resolved
Monitoring, Regular
—
Atrazine
January 1, 1993 – December 31, 1995
Resolved
Monitoring, Regular
—
Chlordane
January 1, 1993 – December 31, 1995
Resolved
Monitoring, Regular
—
Aldicarb
January 1, 1993 – December 31, 1995
Resolved
Monitoring, Regular
—
Picloram
January 1, 1993 – December 31, 1995
Resolved

Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
October 1, 2012 – December 31, 2012	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2012 – September 30, 2012	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 2012 – March 31, 2012	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 2011 – March 31, 2011	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
October 1, 2010 – December 31, 2010	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2010 – September 30, 2010	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 2010 – March 31, 2010	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2009 – September 30, 2009	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2008 – September 30, 2008	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
October 1, 2007 – December 31, 2007	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2007 – September 30, 2007	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
April 1, 2007 – June 30, 2007	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 2007 – March 31, 2007	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 1993 – December 31, 1995	Monitoring, Regular	Atrazine	—	Resolved
January 1, 1993 – December 31, 1995	Monitoring, Regular	Chlordane	—	Resolved
January 1, 1993 – December 31, 1995	Monitoring, Regular	Aldicarb	—	Resolved
January 1, 1993 – December 31, 1995	Monitoring, Regular	Picloram	—	Resolved

Resolved addressed and confirmed by the state

Enforcement actions

January 11, 2013State Compliance achieved1 linked violation
January 11, 2013State Compliance achieved2 linked violations
January 11, 2013State Compliance achieved3 linked violations
January 11, 2013State Compliance achieved2 linked violations
January 11, 2013State Compliance achieved1 linked violation
January 11, 2013State Compliance achieved1 linked violation
January 11, 2013State Compliance achieved7 linked violations
January 11, 2013State Compliance achieved2 linked violations
January 11, 2013State Compliance achieved5 linked violations
January 11, 2013State Compliance achieved2 linked violations
January 11, 2013State Compliance achieved2 linked violations
January 11, 2013State Compliance achieved2 linked violations
September 12, 2012State Public Notification requested7 linked violations
October 31, 2011State Public Notification received5 linked violations
July 7, 2011State Public Notification received2 linked violations
March 2, 2011State Public Notification received1 linked violation
May 27, 2009State Public Notification received4 linked violations
December 9, 2008State Public Notification received3 linked violations
December 4, 2008State Public Notification requested2 linked violations
September 24, 2008State Public Notification received2 linked violations
June 4, 2008State Public Notification requested2 linked violations
April 17, 2008State Public Notification received1 linked violation
April 8, 2008State Public Notification requested1 linked violation
March 5, 2008State Public Notification received1 linked violation
January 4, 2008State Public Notification received1 linked violation
December 27, 2007State Public Notification requested1 linked violation
December 21, 2007State Public Notification received1 linked violation
September 28, 2007State Public Notification received1 linked violation
September 18, 2007State Public Notification requested1 linked violation
September 7, 2007State Administrative/Compliance Order without penalty issued2 linked violations
September 7, 2007State Administrative/Compliance Order without penalty issued1 linked violation
September 7, 2007State Administrative/Compliance Order without penalty issued5 linked violations
September 7, 2007State Administrative/Compliance Order without penalty issued1 linked violation
September 7, 2007State Administrative/Compliance Order without penalty issued1 linked violation
September 7, 2007State Administrative/Compliance Order without penalty issued1 linked violation
September 7, 2007State Administrative/Compliance Order without penalty issued2 linked violations
September 7, 2007State Administrative/Compliance Order without penalty issued2 linked violations
September 7, 2007State Administrative/Compliance Order without penalty issued1 linked violation
September 7, 2007State Administrative/Compliance Order without penalty issued3 linked violations
September 7, 2007State Administrative/Compliance Order without penalty issued2 linked violations
September 7, 2007State Administrative/Compliance Order without penalty issued3 linked violations
September 7, 2007State Administrative/Compliance Order without penalty issued2 linked violations
September 7, 2007State Administrative/Compliance Order without penalty issued1 linked violation
September 7, 2007State Administrative/Compliance Order without penalty issued7 linked violations
July 18, 2007State Public Notification received2 linked violations
April 30, 2007State Public Notification received3 linked violations
April 23, 2007State Public Notification requested3 linked violations
November 14, 2006State Public Notification requested3 linked violations
November 9, 2005State Compliance achieved3 linked violations
January 1, 2001State Compliance achieved1 linked violation
January 1, 2001State Compliance achieved1 linked violation
July 18, 2000State Violation/Reminder Notice2 linked violations
March 13, 2000State Public Notification requested2 linked violations
October 15, 1998State Public Notification requested7 linked violations
May 18, 1998State Public Notification received5 linked violations
March 25, 1998State Compliance achieved114 linked violations
March 16, 1998State Public Notification received5 linked violations
October 9, 1996State Compliance achieved8 linked violations
April 24, 1996State Public Notification requested104 linked violations
March 28, 1996State Public Notification received6 linked violations
March 14, 1996State Compliance achieved24 linked violations
July 20, 1995State Public Notification received2 linked violations
July 14, 1994State Public Notification received30 linked violations

Common questions

Is SUNSET COLONY required to publish a Consumer Confidence Report?: Yes. SUNSET COLONY is a community water system, and federal rules (40 CFR 141 Subpart O) require every community water system to publish a Consumer Confidence Report each year.
When is SUNSET COLONY’s next Consumer Confidence Report due?: SUNSET COLONY’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does SUNSET COLONY have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show no open violations for SUNSET COLONY.
What is a Consumer Confidence Report?: A Consumer Confidence Report (CCR) is the annual drinking water quality report that community water systems must provide to the people they serve. It lists the contaminants detected in the system’s water during the year, where the water comes from, and how the results compare with federal limits. EPA’s revised CCR rule takes effect January 1, 2027, and the first reports in the new format are due July 1, 2027.

Contact

SUNSET COLONY

6054482980

BRITTON, SD 57430