HUNTSVILLE, TX · Walker County
WATSON LAKES WSC Water System
Consumer Confidence Report status
WATSON LAKES 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 no open violations for WATSON LAKES WSC.
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)
- TX2360024
- System type
- Community Water System
- Population served
- 330
- Service connections
- 126
- Ownership
- local government
- Water source
- groundwater (wells)
WATSON LAKES WSC is one of 4,188 community water systems in Texas in the 500 or fewer people size category, serving 330 people from groundwater.
As of August 1, 2026, its federal record holds 9 entries between 2004 and 2010, all of which EPA lists as closed. Nothing has been added since 2010.
Of the 9, 6 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 and the Radionuclides and Revised Rad Rule.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2010 – March 31, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2009 – September 30, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
July 1, 2009 – September 30, 2009
ResolvedMonitoring and Reporting (DBP)
—Chlorine
October 1, 2008 – December 31, 2008
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2006 – March 31, 2006
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2005 – March 31, 2005
ResolvedMonitoring and Reporting (DBP)
—Chlorine
July 1, 2004 – September 30, 2004
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 state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2010 – March 31, 2010 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2009 – September 30, 2009 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2009 – September 30, 2009 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| October 1, 2008 – December 31, 2008 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 1, 2006 – March 31, 2006 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 1, 2005 – March 31, 2005 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| July 1, 2004 – September 30, 2004 | 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 state
Enforcement actions
- January 10, 2012State Compliance achieved23 linked violations
- November 18, 2011State Public Notification requested12 linked violations
- September 14, 2011State Violation/Reminder Notice10 linked violations
- September 20, 2010State Public Notification requested1 linked violation
- September 20, 2010State Violation/Reminder Notice1 linked violation
- September 20, 2010State Public Notification requested1 linked violation
- September 20, 2010State Violation/Reminder Notice1 linked violation
- February 19, 2010State Violation/Reminder Notice1 linked violation
- February 19, 2010State Public Notification requested2 linked violations
- February 19, 2010State Public Notification requested1 linked violation
- June 30, 2009State Public Notification received1 linked violation
- March 27, 2009State 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 requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 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
- December 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- April 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- December 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- August 1, 1981State Public Notification receivedgeneral 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
- February 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- January 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
Common questions
Is WATSON LAKES WSC required to publish a Consumer Confidence Report?
- Yes. WATSON LAKES 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 WATSON LAKES WSC’s next Consumer Confidence Report due?
- WATSON LAKES WSC’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does WATSON LAKES WSC have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for WATSON LAKES WSC.
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
COOK, JOHN
936-295-0467
HUNTSVILLE, TX 77342-5050