HATTIESBURG, MS · Forrest County
GLENDALE UTILITY DISTRICT Water System
Consumer Confidence Report status
GLENDALE 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 1 item for GLENDALE UTILITY DISTRICT that is open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.
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)
- MS0180007
- System type
- Community Water System
- Population served
- 4,477
- Service connections
- 1,696
- Ownership
- local government
- Water source
- groundwater (wells)
GLENDALE UTILITY DISTRICT is one of 161 community water systems in Mississippi in the 3,301 to 10,000 people size category, serving 4,477 people from groundwater.
As of August 1, 2026, its federal record holds 43 entries between 2007 and 2020, of which 1 remains open; none are health-based.
Of the 43, 41 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 Lead and Copper Rule, and inorganic chemicals.
Violation history
Follow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
January 1, 2020
UnaddressedMonitoring, Regular
—Radium-226
April 1, 2012 – June 30, 2012
ResolvedMonitoring, Regular
—Radium-228
April 1, 2012 – June 30, 2012
ResolvedMonitoring, Regular
—Radium-228
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Radium-226
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Radium-226
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Radium-228
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Radium-228
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Radium-228
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
—Radium-228
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Radium-228
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
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Radium-228
January 1, 2011 – March 31, 2011
ResolvedMaximum Contaminant Level Violation, Single Sample
Health-basedFluoride
January 1, 2011 – April 5, 2012
ResolvedMonitoring, Regular
—Radium-228
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
ResolvedMonitoring, Regular
—Radium-226
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-226
July 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Radium-228
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-226
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-226
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-226
October 1, 2009 – December 31, 2009
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
—Radium-226
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Combined Uranium
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
October 1, 2008 – December 31, 2008
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
October 1, 2008 – May 8, 2012
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
July 1, 2008 – September 30, 2008
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
July 1, 2007 – September 30, 2007
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
April 1, 2007 – June 30, 2007
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2007 – March 31, 2007
Resolved
Unaddressed no corrective action on record yetResolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2020 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Unaddressed |
| April 1, 2012 – June 30, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2012 – June 30, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2012 – March 31, 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-228 | — | Resolved |
| October 1, 2011 – December 31, 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 | Radium-226 | — | Resolved |
| July 1, 2011 – September 30, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2011 – September 30, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2011 – June 30, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2011 – June 30, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2011 – June 30, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2011 – April 5, 2012 | Maximum Contaminant Level Violation, Single Sample | Fluoride | Health-based | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2010 – September 30, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2010 – June 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-226 | — | Resolved |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2009 – December 31, 2009 | 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 |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2009 – September 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 | Combined Uranium | — | Resolved |
| January 1, 2009 – March 31, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2008 – December 31, 2008 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2008 – December 31, 2008 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2008 – May 8, 2012 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| July 1, 2008 – September 30, 2008 | Monitoring, Regular | Gross Alpha, Excl. Radon and U | — | Resolved |
| July 1, 2007 – September 30, 2007 | Monitoring, Regular | Gross Alpha, Excl. Radon and U | — | Resolved |
| April 1, 2007 – June 30, 2007 | Monitoring, Regular | Gross Alpha, Excl. Radon and U | — | Resolved |
| January 1, 2007 – March 31, 2007 | Monitoring, Regular | Combined Uranium | — | Resolved |
Unaddressed no corrective action on record yetResolved addressed and confirmed by the state
Enforcement actions
- April 23, 2021State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- January 24, 2020State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- January 24, 2020State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- May 24, 2013State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- August 13, 2012State Compliance achieved135 linked violations
- May 8, 2012State Compliance achieved1 linked violation
- May 8, 2012State Public Notification received106 linked violations
- April 5, 2012State Compliance achieved2 linked violations
- March 30, 2012State Public Notification received112 linked violations
- March 20, 2012State Public Notification requested106 linked violations
- March 20, 2012State Formal Notice of Violation issued106 linked violations
- December 31, 2011State Compliance achieved2 linked violations
- October 3, 2011State Public Notification received1 linked violation
- September 9, 2011State Formal Notice of Violation issued1 linked violation
- September 9, 2011State Public Notification requested2 linked violations
- June 11, 2009State Public Notification received69 linked violations
- June 11, 2009State Public Notification received223 linked violations
- June 11, 2009State Public Notification received44 linked violations
- November 17, 2008State Public Notification requested89 linked violations
- January 24, 1996State Public Notification received1 linked violation
- May 18, 1987State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
Common questions
Is GLENDALE UTILITY DISTRICT required to publish a Consumer Confidence Report?
- Yes. GLENDALE 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 GLENDALE UTILITY DISTRICT’s next Consumer Confidence Report due?
- GLENDALE UTILITY DISTRICT’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does GLENDALE UTILITY DISTRICT have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show 1 item for GLENDALE UTILITY DISTRICT that is open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.
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
MCMAHAN, CHARLES
601-583-0647
HATTIESBURG, MS 39401