WAKONDA, SD · Union County
CLAY RWS/SOUTH UNION Water System
Consumer Confidence Report status
CLAY RWS/SOUTH UNION 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 CLAY RWS/SOUTH UNION.
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)
- SD4602185
- System type
- Community Water System
- Population served
- 1,447
- Service connections
- 579
- Ownership
- privately owned
- Water source
- groundwater (wells)
CLAY RWS/SOUTH UNION is one of 124 community water systems in South Dakota in the 501 to 3,300 people size category, serving 1,447 people from groundwater.
As of August 1, 2026, its federal record holds 26 entries between 1999 and 2004, all of which EPA lists as closed. Nothing has been added since 2004.
All 26 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 synthetic organic chemicals, volatile organic chemicals, and the Radionuclides and Revised Rad Rule.
Violation history
Monitoring, Regular
—Endothall
April 1, 2004 – June 30, 2004
ResolvedMonitoring, Regular
—Diquat
April 1, 2004 – June 30, 2004
ResolvedMonitoring, Regular
—Heptachlor
April 1, 2004 – June 30, 2004
ResolvedMonitoring, Regular
—Benzo(a)pyrene
April 1, 2004 – June 30, 2004
ResolvedMonitoring, Regular
—Carbofuran
April 1, 2004 – June 30, 2004
ResolvedMonitoring, Regular
—OXAMYL
April 1, 2004 – June 30, 2004
ResolvedMonitoring, Regular
—Dalapon
April 1, 2004 – June 30, 2004
ResolvedMonitoring, Regular
—2,4-D
April 1, 2004 – June 30, 2004
ResolvedMonitoring, Regular
—Picloram
January 1, 2004 – March 30, 2004
ResolvedMonitoring, Regular
—2,4-D
January 1, 2004 – March 30, 2004
ResolvedMonitoring, Regular
—Diquat
January 1, 2004 – March 30, 2004
ResolvedMonitoring, Regular
—Heptachlor
January 1, 2004 – March 30, 2004
ResolvedMonitoring, Regular
—Total Polychlorinated Biphenyls (PCB)
January 1, 2004 – March 30, 2004
ResolvedMonitoring, Regular
—Hexachlorocyclopentadiene
January 1, 2004 – March 30, 2004
ResolvedMonitoring, Regular
—BHC-GAMMA
January 1, 2004 – March 30, 2004
ResolvedMonitoring, Regular
—Simazine
January 1, 2004 – March 30, 2004
ResolvedMonitoring, Regular
—Dalapon
January 1, 2004 – March 30, 2004
ResolvedMonitoring, Regular
—CHLOROBENZENE
January 1, 2001 – December 31, 2001
ResolvedMonitoring, Regular
—Trichloroethylene
January 1, 2001 – December 31, 2001
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
January 1, 1999 – December 31, 1999
ResolvedMonitoring, Regular
—1,1-Dichloroethylene
January 1, 1999 – December 31, 1999
ResolvedMonitoring, Regular
—CHLOROBENZENE
January 1, 1999 – December 31, 1999
ResolvedMonitoring, Regular
—Toluene
January 1, 1999 – December 31, 1999
ResolvedMonitoring, Regular
—Endrin
January 1, 1999 – December 31, 1999
ResolvedMonitoring, Regular
—Diquat
January 1, 1999 – December 31, 1999
ResolvedMonitoring, Regular
—Nitrite
January 1, 1999 – December 31, 1999
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| April 1, 2004 – June 30, 2004 | Monitoring, Regular | Endothall | — | Resolved |
| April 1, 2004 – June 30, 2004 | Monitoring, Regular | Diquat | — | Resolved |
| April 1, 2004 – June 30, 2004 | Monitoring, Regular | Heptachlor | — | Resolved |
| April 1, 2004 – June 30, 2004 | Monitoring, Regular | Benzo(a)pyrene | — | Resolved |
| April 1, 2004 – June 30, 2004 | Monitoring, Regular | Carbofuran | — | Resolved |
| April 1, 2004 – June 30, 2004 | Monitoring, Regular | OXAMYL | — | Resolved |
| April 1, 2004 – June 30, 2004 | Monitoring, Regular | Dalapon | — | Resolved |
| April 1, 2004 – June 30, 2004 | Monitoring, Regular | 2,4-D | — | Resolved |
| January 1, 2004 – March 30, 2004 | Monitoring, Regular | Picloram | — | Resolved |
| January 1, 2004 – March 30, 2004 | Monitoring, Regular | 2,4-D | — | Resolved |
| January 1, 2004 – March 30, 2004 | Monitoring, Regular | Diquat | — | Resolved |
| January 1, 2004 – March 30, 2004 | Monitoring, Regular | Heptachlor | — | Resolved |
| January 1, 2004 – March 30, 2004 | Monitoring, Regular | Total Polychlorinated Biphenyls (PCB) | — | Resolved |
| January 1, 2004 – March 30, 2004 | Monitoring, Regular | Hexachlorocyclopentadiene | — | Resolved |
| January 1, 2004 – March 30, 2004 | Monitoring, Regular | BHC-GAMMA | — | Resolved |
| January 1, 2004 – March 30, 2004 | Monitoring, Regular | Simazine | — | Resolved |
| January 1, 2004 – March 30, 2004 | Monitoring, Regular | Dalapon | — | Resolved |
| January 1, 2001 – December 31, 2001 | Monitoring, Regular | CHLOROBENZENE | — | Resolved |
| January 1, 2001 – December 31, 2001 | Monitoring, Regular | Trichloroethylene | — | Resolved |
| January 1, 1999 – December 31, 1999 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| January 1, 1999 – December 31, 1999 | Monitoring, Regular | 1,1-Dichloroethylene | — | Resolved |
| January 1, 1999 – December 31, 1999 | Monitoring, Regular | CHLOROBENZENE | — | Resolved |
| January 1, 1999 – December 31, 1999 | Monitoring, Regular | Toluene | — | Resolved |
| January 1, 1999 – December 31, 1999 | Monitoring, Regular | Endrin | — | Resolved |
| January 1, 1999 – December 31, 1999 | Monitoring, Regular | Diquat | — | Resolved |
| January 1, 1999 – December 31, 1999 | Monitoring, Regular | Nitrite | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved2 linked violations
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved6 linked violations
- August 27, 2004State Compliance achieved3 linked violations
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved2 linked violations
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved2 linked violations
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved2 linked violations
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved2 linked violations
- August 27, 2004State Compliance achieved2 linked violations
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved4 linked violations
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved2 linked violations
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved2 linked violations
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- August 27, 2004State Compliance achieved1 linked violation
- July 21, 2004State Public Notification requested3 linked violations
- July 21, 2004State Public Notification requested3 linked violations
- July 21, 2004State Public Notification requested5 linked violations
- July 21, 2004State Public Notification requested2 linked violations
- July 21, 2004State Public Notification requested3 linked violations
- July 21, 2004State Public Notification requested2 linked violations
- July 21, 2004State Public Notification requested2 linked violations
- April 21, 2004State Public Notification requested3 linked violations
- April 21, 2004State Public Notification requested2 linked violations
- April 21, 2004State Public Notification requested4 linked violations
- April 21, 2004State Public Notification requested3 linked violations
- April 21, 2004State Public Notification requested3 linked violations
- April 21, 2004State Public Notification requested3 linked violations
- April 21, 2004State Public Notification requested5 linked violations
- April 21, 2004State Public Notification requested4 linked violations
- May 29, 2002State Compliance achieved2 linked violations
- May 29, 2002State Compliance achieved2 linked violations
- May 29, 2002State Compliance achieved2 linked violations
- May 29, 2002State Compliance achieved2 linked violations
- May 29, 2002State Compliance achieved41 linked violations
- May 29, 2002State Compliance achieved3 linked violations
- May 29, 2002State Compliance achieved3 linked violations
- May 29, 2002State Compliance achieved4 linked violations
- May 29, 2002State Compliance achieved3 linked violations
- May 29, 2002State Compliance achieved3 linked violations
- May 29, 2002State Compliance achieved2 linked violations
- May 13, 2002State Public Notification received2 linked violations
- May 13, 2002State Public Notification received2 linked violations
- May 13, 2002State Public Notification received2 linked violations
- May 13, 2002State Public Notification received2 linked violations
- May 13, 2002State Public Notification received2 linked violations
- May 13, 2002State Public Notification received2 linked violations
- May 13, 2002State Public Notification received2 linked violations
- May 13, 2002State Public Notification received2 linked violations
- May 13, 2002State Public Notification received4 linked violations
- May 13, 2002State Public Notification received2 linked violations
- April 17, 2002State Public Notification requested3 linked violations
- April 17, 2002State Public Notification requested1 linked violation
- April 17, 2002State Public Notification requested4 linked violations
- April 17, 2002State Public Notification requested3 linked violations
- April 17, 2002State Public Notification requested3 linked violations
- March 6, 2000State Compliance achieved70 linked violations
Common questions
Is CLAY RWS/SOUTH UNION required to publish a Consumer Confidence Report?
- Yes. CLAY RWS/SOUTH UNION 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 CLAY RWS/SOUTH UNION’s next Consumer Confidence Report due?
- CLAY RWS/SOUTH UNION’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does CLAY RWS/SOUTH UNION have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for CLAY RWS/SOUTH UNION.
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
CLAY RWS/SOUTH UNION
6052672088
WAKONDA, SD 57073