LIBERTY, TX · Liberty County
AMES MINGLEWOOD WSC Water System
Consumer Confidence Report status
AMES MINGLEWOOD WSC 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 AMES MINGLEWOOD WSC 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 Texas’s official records. Always confirm current status with Texas before making decisions based on this information.
System facts
- System ID (PWSID)
- TX1460005
- System type
- Community Water System
- Population served
- 1,174
- Service connections
- 601
- Ownership
- local government
- Water source
- groundwater (wells)
AMES MINGLEWOOD WSC is one of 1,859 community water systems in Texas in the 501 to 3,300 people size category, serving 1,174 people from groundwater.
As of August 1, 2026, its federal record holds 11 entries between 2004 and 2025, of which 1 remains open; none are health-based.
Of the 11, 10 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 Stage 1 Disinfectants and Disinfection Byproducts Rule, the Lead and Copper Rule, and the Public Notice Rule and Revised PN Rule.
Violation history
Notification, Known or Potential LSL
—LEAD AND COPPER RULE REVISIONS
July 2, 2025 – April 16, 2026
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
February 8, 2016
UnaddressedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 2015 – September 28, 2016
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2007 – March 31, 2007
ResolvedMonitoring and Reporting (DBP)
—Chlorine
October 1, 2006 – December 31, 2006
ResolvedMonitoring and Reporting (DBP)
—Chlorine
July 1, 2006 – September 30, 2006
ResolvedMonitoring and Reporting (DBP)
—Chlorine
October 1, 2005 – December 31, 2005
ResolvedMonitoring and Reporting (DBP)
—Chlorine
July 1, 2005 – September 30, 2005
ResolvedMonitoring and Reporting (DBP)
—Chlorine
April 1, 2005 – June 30, 2005
ResolvedMonitoring and Reporting (DBP)
—Chlorine
April 1, 2004 – June 30, 2004
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2004 – March 31, 2004
Resolved
Resolved addressed and confirmed by the stateUnaddressed no corrective action on record yet
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| July 2, 2025 – April 16, 2026 | Notification, Known or Potential LSL | LEAD AND COPPER RULE REVISIONS | — | Resolved |
| February 8, 2016 | Public Notification Violation for NPDWR Violation | Public Notice | — | Unaddressed |
| October 1, 2015 – September 28, 2016 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| January 1, 2007 – March 31, 2007 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| October 1, 2006 – December 31, 2006 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| July 1, 2006 – September 30, 2006 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| October 1, 2005 – December 31, 2005 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| July 1, 2005 – September 30, 2005 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| April 1, 2005 – June 30, 2005 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| April 1, 2004 – June 30, 2004 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 1, 2004 – March 31, 2004 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
Resolved addressed and confirmed by the stateUnaddressed no corrective action on record yet
Enforcement actions
- September 28, 2016State Compliance achieved3 linked violations
- November 5, 2015State Violation/Reminder Notice3 linked violations
- October 31, 2014State Compliance achieved4 linked violations
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Public Notification requested2 linked violations
- July 19, 2007State Public Notification requested6 linked violations
- July 19, 2007State Public Notification requested2 linked violations
- July 19, 2007State Public Notification requested2 linked violations
- July 19, 2007State Public Notification requested2 linked violations
- July 19, 2007State Violation/Reminder Notice1 linked violation
- May 1, 1985State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- September 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- June 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- April 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- June 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- February 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- December 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- November 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- September 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- July 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- March 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
Common questions
Is AMES MINGLEWOOD WSC required to publish a Consumer Confidence Report?
- Yes. AMES MINGLEWOOD WSC 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 AMES MINGLEWOOD WSC’s next Consumer Confidence Report due?
- AMES MINGLEWOOD WSC’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does AMES MINGLEWOOD WSC have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show 1 item for AMES MINGLEWOOD WSC 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
HARDY, EDWIN
936-336-5883
LIBERTY, TX 77575-1598