Is GARRETSON required to publish a Consumer Confidence Report?

Yes. GARRETSON 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 GARRETSON’s next Consumer Confidence Report due?

GARRETSON’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.

GARRETSON, SD · Minnehaha County

GARRETSON Water System

Consumer Confidence Report status

GARRETSON 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 GARRETSON.

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): SD4600138
System type: Community Water System
Population served: 1,228
Service connections: 511
Ownership: local government
Water source: groundwater (wells)

GARRETSON is one of 124 community water systems in South Dakota in the 501 to 3,300 people size category, serving 1,228 people from groundwater.

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

Of the 6, 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.

Violation history

Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2000 – December 31, 2000
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 1989 – June 30, 1989
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 1989 – March 31, 1989
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 1985 – December 31, 1985
Resolved
Monitoring, Regular
—
Gross Alpha, Excl. Radon and U
July 1, 1976 – June 30, 1980
Archived
Monitoring, Regular
—
Combined Radium (-226 and -228)
July 1, 1976 – June 30, 1980
Archived

Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)

Period	Violation	Contaminant / rule	Health-based	Status
January 1, 2000 – December 31, 2000	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
April 1, 1989 – June 30, 1989	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
January 1, 1989 – March 31, 1989	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
October 1, 1985 – December 31, 1985	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
July 1, 1976 – June 30, 1980	Monitoring, Regular	Gross Alpha, Excl. Radon and U	—	Archived
July 1, 1976 – June 30, 1980	Monitoring, Regular	Combined Radium (-226 and -228)	—	Archived

Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)

Enforcement actions

March 17, 2014State Compliance achieved1 linked violation
March 6, 2014State Violation/Reminder Notice1 linked violation
July 7, 2006State Compliance achieved2 linked violations
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved3 linked violations
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved8 linked violations
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved2 linked violations
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved2 linked violations
April 23, 2003State Compliance achieved3 linked violations
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved9 linked violations
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved12 linked violations
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
April 23, 2003State Compliance achieved1 linked violation
October 12, 2001State Public Notification received2 linked violations
October 5, 2001State Administrative/Compliance Order without penalty issued4 linked violations
October 5, 2001State Administrative/Compliance Order without penalty issued1 linked violation
October 5, 2001State Administrative/Compliance Order without penalty issued2 linked violations
October 5, 2001State Administrative/Compliance Order without penalty issued2 linked violations
October 5, 2001State Administrative/Compliance Order without penalty issued1 linked violation
October 5, 2001State Administrative/Compliance Order without penalty issued3 linked violations
October 5, 2001State Administrative/Compliance Order without penalty issued5 linked violations
October 5, 2001State Administrative/Compliance Order without penalty issued4 linked violations
October 5, 2001State Administrative/Compliance Order without penalty issued3 linked violations
October 5, 2001State Administrative/Compliance Order without penalty issued5 linked violations
October 5, 2001State Administrative/Compliance Order without penalty issued6 linked violations
October 5, 2001State Administrative/Compliance Order without penalty issued4 linked violations
October 5, 2001State Administrative/Compliance Order without penalty issued3 linked violations
October 3, 2001State Public Notification requested2 linked violations
December 11, 2000State Public Notification received1 linked violation
September 14, 2000State Public Notification requested1 linked violation
December 24, 1998State Compliance achieved5 linked violations
October 3, 1997State Public Notification received1 linked violation
July 7, 1997State Public Notification received1 linked violation
March 31, 1997State Public Notification received2 linked violations
April 25, 1996State Public Notification requested2 linked violations
October 10, 1995State Public Notification requested1 linked violation
August 8, 1995State Public Notification requested1 linked violation
August 3, 1995State Public Notification requested1 linked violation
July 20, 1995State Public Notification received1 linked violation
April 13, 1995State Public Notification received1 linked violation
March 27, 1995State Public Notification requested6 linked violations
February 13, 1995State Public Notification requested1 linked violation
December 30, 1994State Public Notification received1 linked violation
September 26, 1994State Public Notification received2 linked violations
June 8, 1994State Public Notification received1 linked violation
February 11, 1994State Compliance achieved3 linked violations
February 9, 1994State Public Notification received2 linked violations
September 9, 1993State Public Notification received1 linked violation
January 15, 1993State Public Notification received6 linked violations
October 1, 1992State Public Notification requested3 linked violations
September 25, 1991State Public Notification requested33 linked violations
March 29, 1984State Public Notification requested4 linked violations
June 17, 1982State Public Notification received2 linked violations

Common questions

Is GARRETSON required to publish a Consumer Confidence Report?: Yes. GARRETSON 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 GARRETSON’s next Consumer Confidence Report due?: GARRETSON’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does GARRETSON have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show no open violations for GARRETSON.
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

GARRETSON

6055946723

GARRETSON, SD 57030