CLINTON, MS · Hinds County
CITY OF CLINTON Water System
Consumer Confidence Report status
CITY OF CLINTON 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 CITY OF CLINTON.
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 Mississippi’s official records. Always confirm current status with Mississippi before making decisions based on this information.
System facts
- System ID (PWSID)
- MS0250003
- System type
- Community Water System
- Population served
- 25,000
- Service connections
- 10,854
- Ownership
- local government
- Water source
- groundwater (wells)
CITY OF CLINTON is among the 21 largest community water systems in Mississippi, serving 25,000 people from groundwater.
As of August 1, 2026, its federal record holds 35 entries between 2007 and 2025, all of which EPA lists as closed.
Of the 35, 30 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 Stage 2 Disinfectants and Disinfection Byproducts Rule, and the Stage 1 Disinfectants and Disinfection Byproducts Rule.
Violation history
Monitoring and Reporting (DBP)
—Chlorine
October 1, 2025 – December 31, 2025
ArchivedMaximum Contaminant Level Violation, Average
Health-basedTTHM
April 1, 2017 – June 30, 2017
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
July 1, 2016 – September 30, 2016
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
January 1, 2016 – March 31, 2016
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
October 1, 2015 – December 31, 2015
ResolvedMonitoring, Regular
—Radium-226
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Radium-226
July 1, 2012 – September 30, 2012
ResolvedMonitoring, Regular
—Radium-228
July 1, 2012 – September 30, 2012
ResolvedMonitoring, Regular
—Radium-226
April 1, 2012 – June 30, 2012
ResolvedMonitoring, Regular
—Radium-228
April 1, 2012 – June 30, 2012
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2012 – June 30, 2012
ResolvedMonitoring, Regular
—Radium-226
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Radium-228
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Radium-226
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Radium-228
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Radium-228
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Radium-226
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Radium-228
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Radium-226
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-228
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-226
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Radium-228
October 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Radium-226
October 1, 2009 – December 31, 2009
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
July 1, 2009 – June 29, 2012
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2008 – September 30, 2008
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
January 1, 2008 – March 31, 2008
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2007 – June 30, 2007
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
April 1, 2007 – June 30, 2007
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
January 1, 2007 – March 31, 2007
Resolved
Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| October 1, 2025 – December 31, 2025 | Monitoring and Reporting (DBP) | Chlorine | — | Archived |
| April 1, 2017 – June 30, 2017 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| July 1, 2016 – September 30, 2016 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| January 1, 2016 – March 31, 2016 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| October 1, 2015 – December 31, 2015 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2012 – September 30, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2012 – September 30, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2012 – June 30, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2012 – June 30, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2012 – June 30, 2012 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2011 – December 31, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2011 – December 31, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2011 – December 31, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2011 – September 30, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2011 – September 30, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2011 – September 30, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2011 – June 30, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2011 – June 30, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2010 – March 31, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2010 – March 31, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2009 – December 31, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2009 – December 31, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2009 – June 29, 2012 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| July 1, 2008 – September 30, 2008 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2008 – March 31, 2008 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| April 1, 2007 – June 30, 2007 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2007 – June 30, 2007 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| January 1, 2007 – March 31, 2007 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state
Enforcement actions
- June 29, 2012State Compliance achieved2 linked violations
- March 20, 2012State Formal Notice of Violation issued28 linked violations
- March 20, 2012State Public Notification requested28 linked violations
- September 14, 2010State Compliance achieved13 linked violations
- June 24, 2009State Public Notification received9 linked violations
- June 24, 2009State Public Notification received10 linked violations
- June 24, 2009State Public Notification received10 linked violations
- June 24, 2009State Public Notification received10 linked violations
- June 24, 2009State Public Notification received18 linked violations
- June 24, 2009State Public Notification received15 linked violations
- June 24, 2009State Public Notification received12 linked violations
- June 24, 2009State Public Notification received12 linked violations
- June 24, 2009State Public Notification received13 linked violations
- June 24, 2009State Public Notification received12 linked violations
- June 24, 2009State Public Notification received12 linked violations
- June 24, 2009State Public Notification received13 linked violations
- June 24, 2009State Public Notification received13 linked violations
- June 24, 2009State Public Notification received9 linked violations
- June 24, 2009State Public Notification received9 linked violations
- June 24, 2009State Public Notification received9 linked violations
- June 24, 2009State Public Notification received9 linked violations
- June 24, 2009State Public Notification received12 linked violations
- June 24, 2009State Public Notification received9 linked violations
- June 24, 2009State Public Notification received9 linked violations
- June 24, 2009State Public Notification received10 linked violations
- June 24, 2009State Public Notification received10 linked violations
- December 30, 2008State Compliance achieved15 linked violations
- December 30, 2008State Compliance achieved15 linked violations
- December 30, 2008State Compliance achieved16 linked violations
- November 17, 2008State Formal Notice of Violation issued215 linked violations
- November 17, 2008State Formal Notice of Violation issued94 linked violations
- November 17, 2008State Formal Notice of Violation issued45 linked violations
- November 17, 2008State Public Notification requested45 linked violations
- December 16, 1987State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
Common questions
Is CITY OF CLINTON required to publish a Consumer Confidence Report?
- Yes. CITY OF CLINTON 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 CITY OF CLINTON’s next Consumer Confidence Report due?
- CITY OF CLINTON’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does CITY OF CLINTON have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for CITY OF CLINTON.
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
PURDIE, WILLIAM
601-925-6103
CLINTON, MS 39056