HATTIESBURG, MS · Lamar County
WEST LAMAR WATER ASSN #1 Water System
Consumer Confidence Report status
WEST LAMAR WATER ASSN #1 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 WEST LAMAR WATER ASSN #1.
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)
- MS0370011
- System type
- Community Water System
- Population served
- 18,491
- Service connections
- 7,075
- Ownership
- public/private mix
- Water source
- groundwater (wells)
WEST LAMAR WATER ASSN #1 is one of 56 community water systems in Mississippi in the 10,001 to 100,000 people size category, serving 18,491 people from groundwater.
As of August 1, 2026, its federal record holds 15 entries between 2007 and 2012, all of which EPA lists as closed. Nothing has been added since 2012.
Of the 15, 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 Public Notice Rule and Revised PN Rule.
Violation history
Monitoring, Regular
—Radium-226
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Radium-226
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2011 – December 31, 2011
ResolvedMonitoring, Regular
—Radium-226
July 1, 2011 – September 30, 2011
ResolvedMonitoring, Regular
—Radium-228
July 1, 2011 – September 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-226
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2009 – September 30, 2009
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
October 1, 2008 – May 15, 2012
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2008 – September 30, 2008
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
April 1, 2008 – June 30, 2008
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
January 1, 2008 – March 31, 2008
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
January 1, 2008 – March 31, 2008
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
January 1, 2007 – March 31, 2007
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| 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 | Combined Uranium | — | Resolved |
| July 1, 2011 – September 30, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2011 – September 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, 2010 – March 31, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2008 – May 15, 2012 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| July 1, 2008 – September 30, 2008 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2008 – June 30, 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, 2008 – March 31, 2008 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| January 1, 2007 – March 31, 2007 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- April 14, 2025State Public Notification received1 linked violation
- July 10, 2015State Public Notification requested1 linked violation
- July 10, 2015State Formal Notice of Violation issued4 linked violations
- May 15, 2013State Public Notification received22 linked violations
- December 31, 2012State Compliance achieved1 linked violation
- December 31, 2012State Compliance achieved2 linked violations
- December 31, 2012State Compliance achieved1 linked violation
- December 31, 2012State Compliance achieved1 linked violation
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved5 linked violations
- December 31, 2012State Compliance achieved3 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved5 linked violations
- December 31, 2012State Compliance achieved7 linked violations
- December 31, 2012State Compliance achieved5 linked violations
- December 31, 2012State Compliance achieved2 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- December 31, 2012State Compliance achieved1 linked violation
- December 31, 2012State Compliance achieved2 linked violations
- December 31, 2012State Compliance achieved4 linked violations
- September 5, 2012State Public Notification received5 linked violations
- August 8, 2012State Public Notification requested4 linked violations
- May 15, 2012State Compliance achieved4 linked violations
- March 10, 2010State Compliance achieved6 linked violations
- September 30, 2009State Compliance achieved39 linked violations
- June 24, 2009State Public Notification received72 linked violations
- June 24, 2009State Public Notification received28 linked violations
- June 24, 2009State Public Notification received28 linked violations
- December 30, 2008State Compliance achieved49 linked violations
- November 17, 2008State Public Notification requested56 linked violations
Common questions
Is WEST LAMAR WATER ASSN #1 required to publish a Consumer Confidence Report?
- Yes. WEST LAMAR WATER ASSN #1 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 WEST LAMAR WATER ASSN #1’s next Consumer Confidence Report due?
- WEST LAMAR WATER ASSN #1’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does WEST LAMAR WATER ASSN #1 have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for WEST LAMAR WATER ASSN #1.
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
RIDGWAY, REGGIE
601-264-6305
HATTIESBURG, MS 39402