BOLTON, MS · Hinds County
ST THOMAS WATER ASSOCIATION Water System
Consumer Confidence Report status
ST THOMAS WATER ASSOCIATION 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 ST THOMAS WATER ASSOCIATION.
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)
- MS0250024
- System type
- Community Water System
- Population served
- 500
- Service connections
- 182
- Ownership
- public/private mix
- Water source
- groundwater (wells)
ST THOMAS WATER ASSOCIATION is one of 879 community water systems in Mississippi in the 500 or fewer people size category, serving 500 people from groundwater.
As of August 1, 2026, its federal record holds 41 entries between 2006 and 2025, all of which EPA lists as closed.
Of the 41, 35 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 Public Notice Rule and Revised PN Rule.
Violation history
Monitoring and Reporting (DBP)
—Total Haloacetic Acids (HAA5)
April 1, 2025 – June 30, 2025
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
June 4, 2023 – June 30, 2024
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
December 13, 2022 – June 30, 2023
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
July 1, 2022 – September 30, 2022
ResolvedMonitoring, Regular
—Radium-228
July 1, 2012 – September 30, 2012
ResolvedMonitoring, Regular
—Radium-226
July 1, 2012 – September 30, 2012
ResolvedMonitoring, Regular
—Radium-226
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Radium-228
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Radium-226
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-226
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Radium-228
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Radium-228
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-228
October 1, 2010 – December 31, 2010
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
September 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Radium-226
July 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Radium-228
July 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Radium-226
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-228
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-226
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Radium-228
October 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Radium-226
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Radium-228
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Radium-226
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Radium-228
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Radium-226
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Radium-228
January 1, 2009 – March 31, 2009
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2008 – December 31, 2008
ResolvedMonitoring, Regular
—Radium-228
October 1, 2008 – December 31, 2008
ResolvedMonitoring, Regular
—Radium-226
October 1, 2008 – December 31, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
October 1, 2008 – December 31, 2008
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
January 1, 2008 – March 31, 2008
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
January 1, 2008 – March 31, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
January 1, 2006 – March 31, 2006
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| April 1, 2025 – June 30, 2025 | Monitoring and Reporting (DBP) | Total Haloacetic Acids (HAA5) | — | Resolved |
| June 4, 2023 – June 30, 2024 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| December 13, 2022 – June 30, 2023 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| July 1, 2022 – September 30, 2022 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| July 1, 2012 – September 30, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2012 – September 30, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2011 – December 31, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2011 – December 31, 2011 | Monitoring, Regular | Radium-226 | — | 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-226 | — | Resolved |
| April 1, 2011 – June 30, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| September 1, 2010 – September 30, 2010 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| July 1, 2010 – September 30, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2010 – September 30, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2010 – September 30, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2010 – March 31, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2009 – December 31, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2009 – March 31, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2008 – December 31, 2008 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2008 – December 31, 2008 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2008 – December 31, 2008 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2008 – December 31, 2008 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| January 1, 2008 – March 31, 2008 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| January 1, 2008 – March 31, 2008 | Monitoring, Regular | Gross Alpha, Excl. Radon and U | — | Resolved |
| January 1, 2006 – March 31, 2006 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- June 7, 2012State Compliance achieved1 linked violation
- June 7, 2012State Public Notification received78 linked violations
- March 20, 2012State Public Notification requested78 linked violations
- March 20, 2012State Formal Notice of Violation issued78 linked violations
- October 14, 2010State Public Notification received1 linked violation
- October 12, 2010State Compliance achieved4 linked violations
- September 24, 2010State Public Notification requested4 linked violations
- July 1, 2009State Public Notification received134 linked violations
- September 18, 2008State Formal Notice of Violation issued45 linked violations
- July 1, 2008State Compliance achieved116 linked violations
- October 3, 2007State Public Notification requested5 linked violations
- October 3, 2007State Violation/Reminder Notice46 linked violations
- July 23, 2007State Public Notification requested35 linked violations
- July 27, 2006State Violation/Reminder Notice5 linked violations
- December 31, 2005State Compliance achieved1 linked violation
- October 14, 2005State Public Notification requested49 linked violations
- June 30, 2005State Compliance achieved1 linked violation
- July 17, 1987State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
Common questions
Is ST THOMAS WATER ASSOCIATION required to publish a Consumer Confidence Report?
- Yes. ST THOMAS WATER ASSOCIATION 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 ST THOMAS WATER ASSOCIATION’s next Consumer Confidence Report due?
- ST THOMAS WATER ASSOCIATION’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does ST THOMAS WATER ASSOCIATION have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for ST THOMAS WATER ASSOCIATION.
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
FRANKLIN, VERONICA
601-866-4105
BOLTON, MS 39041