GOODMAN, MS · Holmes County
TOWN OF GOODMAN Water System
Consumer Confidence Report status
TOWN OF GOODMAN 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 TOWN OF GOODMAN.
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)
- MS0260008
- System type
- Community Water System
- Population served
- 1,188
- Service connections
- 450
- Ownership
- local government
- Water source
- groundwater (wells)
TOWN OF GOODMAN is one of 794 community water systems in Mississippi in the 501 to 3,300 people size category, serving 1,188 people from groundwater.
As of August 1, 2026, its federal record holds 28 entries between 2008 and 2023, all of which EPA lists as closed. Nothing has been added since 2023.
Of the 28, 27 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)
—TTHM
January 1, 2023 – December 31, 2023
ArchivedPublic Notification Violation for NPDWR Violation
—Public Notice
June 27, 2022 – June 30, 2022
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
May 1, 2022 – May 31, 2022
ResolvedMonitoring and Reporting (DBP)
—Total Haloacetic Acids (HAA5)
January 1, 2022 – December 31, 2022
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
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Radium-226
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Radium-226
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Radium-226
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-228
July 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Radium-228
July 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-228
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Radium-228
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Radium-226
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Radium-226
October 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Radium-228
January 1, 2009 – March 31, 2009
ResolvedMonitoring, Regular
—Radium-228
January 1, 2009 – March 31, 2009
ResolvedMonitoring, Regular
—Radium-226
January 1, 2009 – March 31, 2009
ResolvedMonitoring, Regular
—Radium-226
October 1, 2008 – December 31, 2008
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2008 – September 30, 2008
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 |
|---|---|---|---|---|
| January 1, 2023 – December 31, 2023 | Monitoring and Reporting (DBP) | TTHM | — | Archived |
| June 27, 2022 – June 30, 2022 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| May 1, 2022 – May 31, 2022 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| January 1, 2022 – December 31, 2022 | Monitoring and Reporting (DBP) | Total Haloacetic Acids (HAA5) | — | 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 |
| January 1, 2012 – March 31, 2012 | 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 |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2010 – September 30, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2010 – September 30, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2010 – June 30, 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 | Combined Uranium | — | Resolved |
| January 1, 2010 – March 31, 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-226 | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2009 – March 31, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2009 – March 31, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2009 – March 31, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2008 – December 31, 2008 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2008 – September 30, 2008 | Monitoring, Regular | Combined Uranium | — | Resolved |
Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state
Enforcement actions
- April 4, 2025State Compliance achieved1 linked violation
- March 19, 2025State no additional Formal Action needed2 linked violations
- February 5, 2025State no additional Formal Action needed1 linked violation
- January 28, 2025State no additional Formal Action neededgeneral compliance action — not tied to a specific violation on record
- January 27, 2025State no additional Formal Action needed1 linked violation
- January 22, 2025State no additional Formal Action neededgeneral compliance action — not tied to a specific violation on record
- January 17, 2025State no additional Formal Action needed1 linked violation
- January 16, 2025State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- January 3, 2025State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- March 18, 2024State Compliance achieved2 linked violations
- March 6, 2024State no additional Formal Action needed2 linked violations
- February 1, 2024State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- February 1, 2024State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- February 1, 2024State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- September 7, 2023State Formal Notice of Violation issued1 linked violation
- September 7, 2023State Public Notification requested1 linked violation
- September 5, 2023State Compliance achieved1 linked violation
- April 28, 2023State Public Notification received2 linked violations
- April 28, 2023State Compliance achieved1 linked violation
- March 14, 2023State Public Notification requested2 linked violations
- March 14, 2023State Formal Notice of Violation issued2 linked violations
- January 24, 2023State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2022State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- December 31, 2022State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- September 30, 2022State Formal Notice of Violation issued1 linked violation
- September 30, 2022State Compliance achieved1 linked violation
- September 30, 2022State Public Notification requested1 linked violation
- September 1, 2022State Compliance achieved1 linked violation
- June 30, 2022State Compliance achieved1 linked violation
- June 23, 2022State Public Notification received2 linked violations
- June 20, 2022State Compliance achieved1 linked violation
- June 9, 2022State Public Notification requested1 linked violation
- June 9, 2022State Public Notification requested1 linked violation
- June 9, 2022State Formal Notice of Violation issued1 linked violation
- June 9, 2022State Formal Notice of Violation issued1 linked violation
- May 11, 2022State Show-Cause hearing2 linked violations
- April 6, 2021State Formal Notice of Violation issued2 linked violations
- May 21, 2013State Public Notification received15 linked violations
- November 17, 2008State Formal Notice of Violation issued114 linked violations
- March 14, 1988State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- February 16, 1987State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- January 19, 1987State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
Common questions
Is TOWN OF GOODMAN required to publish a Consumer Confidence Report?
- Yes. TOWN OF GOODMAN 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 TOWN OF GOODMAN’s next Consumer Confidence Report due?
- TOWN OF GOODMAN’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does TOWN OF GOODMAN have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for TOWN OF GOODMAN.
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
HOWARD, MICHAEL
662-472-9800
GOODMAN, MS 39079