ROLLING FORK, MS · Issaquena County
TALLULA UTILITY DISTRICT Water System
Consumer Confidence Report status
TALLULA UTILITY DISTRICT 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 TALLULA UTILITY DISTRICT.
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)
- MS0280017
- System type
- Community Water System
- Population served
- 370
- Service connections
- 140
- Ownership
- local government
- Water source
- groundwater (wells)
TALLULA UTILITY DISTRICT is one of 879 community water systems in Mississippi in the 500 or fewer people size category, serving 370 people from groundwater.
As of August 1, 2026, its federal record holds 14 entries between 2009 and 2023, all of which EPA lists as closed. Nothing has been added since 2023.
All 14 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 and the Stage 2 Disinfectants and Disinfection Byproducts Rule.
Violation history
Monitoring and Reporting (DBP)
—TTHM
April 1, 2023 – June 30, 2023
ResolvedMonitoring, Regular
—Radium-226
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Radium-228
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Radium-226
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Radium-226
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-226
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Radium-228
October 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Radium-226
January 1, 2009 – March 31, 2009
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| April 1, 2023 – June 30, 2023 | Monitoring and Reporting (DBP) | TTHM | — | Resolved |
| October 1, 2011 – December 31, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2011 – December 31, 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 |
| July 1, 2011 – September 30, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2011 – June 30, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Combined Uranium | — | 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 | Combined Uranium | — | Resolved |
| January 1, 2009 – March 31, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- May 31, 2012State Public Notification received121 linked violations
- March 20, 2012State Public Notification requested65 linked violations
- June 30, 2007State Compliance achieved6 linked violations
- April 18, 1988State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- August 28, 1987State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- March 16, 1987State Public Notification requested1 linked violation
- 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
- December 8, 1986State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- October 14, 1986State Public Notification requested1 linked violation
- September 10, 1986State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- July 17, 1986State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- June 10, 1986State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- April 10, 1986State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- March 14, 1986State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- December 13, 1985State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- November 18, 1985State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- October 31, 1985State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- September 27, 1985State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- August 20, 1985State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
Common questions
Is TALLULA UTILITY DISTRICT required to publish a Consumer Confidence Report?
- Yes. TALLULA UTILITY DISTRICT 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 TALLULA UTILITY DISTRICT’s next Consumer Confidence Report due?
- TALLULA UTILITY DISTRICT’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does TALLULA UTILITY DISTRICT have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for TALLULA UTILITY DISTRICT.
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
HEIGLE, TODD
662-931-4896
ROLLING FORK, MS 39159