FOREST, MS · Scott County
CITY OF FOREST Water System
Consumer Confidence Report status
CITY OF FOREST 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 FOREST.
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)
- MS0620002
- System type
- Community Water System
- Population served
- 5,430
- Service connections
- 2,433
- Ownership
- local government
- Water source
- groundwater (wells)
CITY OF FOREST is one of 161 community water systems in Mississippi in the 3,301 to 10,000 people size category, serving 5,430 people from groundwater.
As of August 1, 2026, its federal record holds 44 entries between 2007 and 2020, all of which EPA lists as closed. Nothing has been added since 2020.
All 44 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 1 Disinfectants and Disinfection Byproducts Rule.
Violation history
Monitoring and Reporting (DBP)
—Chlorine
July 1, 2020 – September 30, 2020
ResolvedMonitoring, Regular
—Radium-228
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Radium-228
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Radium-226
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Radium-226
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Radium-226
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Radium-226
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Radium-228
October 1, 2012 – December 31, 2012
ResolvedMonitoring, Regular
—Radium-226
July 1, 2012 – September 30, 2012
ResolvedMonitoring, Regular
—Radium-226
July 1, 2012 – September 30, 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
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-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
—Combined Uranium
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Radium-226
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Radium-228
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Radium-228
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Radium-228
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2011 – September 30, 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
—Combined Uranium
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Radium-228
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-228
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-228
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-226
October 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Radium-228
January 1, 2009 – March 31, 2009
ResolvedMonitoring, Regular
—Radium-228
October 1, 2008 – December 31, 2008
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
January 1, 2007 – March 31, 2007
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| July 1, 2020 – September 30, 2020 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2012 – September 30, 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-226 | — | Resolved |
| July 1, 2012 – September 30, 2012 | Monitoring, Regular | Radium-228 | — | 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-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 | Combined Uranium | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2011 – September 30, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2011 – September 30, 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 | 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 | Combined Uranium | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2010 – December 31, 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 |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2009 – December 31, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2009 – March 31, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2008 – December 31, 2008 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2007 – March 31, 2007 | Monitoring, Regular | Gross Alpha, Excl. Radon and U | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- February 7, 2014State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 31, 2012State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- June 8, 2012State Public Notification received87 linked violations
- March 20, 2012State Formal Notice of Violation issued159 linked violations
- March 11, 2010State Compliance achieved19 linked violations
- September 30, 2009State Compliance achieved72 linked violations
- September 30, 2009State Compliance achieved21 linked violations
- September 30, 2009State Compliance achieved21 linked violations
- September 30, 2009State Compliance achieved18 linked violations
- September 30, 2009State Compliance achieved82 linked violations
- September 30, 2009State Compliance achieved25 linked violations
- June 26, 2009State Public Notification received63 linked violations
- June 26, 2009State Public Notification received39 linked violations
- November 17, 2008State Formal Notice of Violation issued97 linked violations
- November 17, 2008State Public Notification requested33 linked violations
- November 17, 2008State Formal Notice of Violation issued210 linked violations
- November 17, 2008State Public Notification requested54 linked violations
Common questions
Is CITY OF FOREST required to publish a Consumer Confidence Report?
- Yes. CITY OF FOREST 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 FOREST’s next Consumer Confidence Report due?
- CITY OF FOREST’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does CITY OF FOREST have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for CITY OF FOREST.
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
CHAMBERS, NANCY N
601-469-2921
FOREST, MS 39074