ETOILE, TX · Nacogdoches County
ETOILE WSC Water System
Consumer Confidence Report status
ETOILE 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 ETOILE 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)
- TX1740011
- System type
- Community Water System
- Population served
- 2,136
- Service connections
- 894
- Ownership
- local government
- Water source
- groundwater (wells)
ETOILE WSC is one of 1,859 community water systems in Texas in the 501 to 3,300 people size category, serving 2,136 people from groundwater.
As of August 1, 2026, its federal record holds 10 entries between 2008 and 2016, all of which EPA lists as closed. Nothing has been added since 2016.
Of the 10, 3 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 Public Notice Rule and Revised PN Rule.
Violation history
Public Notification Violation for NPDWR Violation
—Public Notice
October 13, 2016 – February 10, 2017
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2016 – March 31, 2016
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
January 22, 2015 – March 3, 2015
ResolvedMonitoring and Reporting (DBP)
—Chlorine
October 1, 2012 – December 31, 2012
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2012 – March 31, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
April 1, 2011 – June 30, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
October 1, 2009 – December 31, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
July 1, 2009 – September 30, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
October 1, 2008 – December 31, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
July 1, 2008 – September 30, 2008
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| October 13, 2016 – February 10, 2017 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| January 1, 2016 – March 31, 2016 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 22, 2015 – March 3, 2015 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| October 1, 2012 – December 31, 2012 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| April 1, 2011 – June 30, 2011 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| October 1, 2009 – December 31, 2009 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| July 1, 2009 – September 30, 2009 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| October 1, 2008 – December 31, 2008 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| July 1, 2008 – September 30, 2008 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- October 1, 2018State Compliance achieved7 linked violations
- February 10, 2017State Compliance achieved6 linked violations
- December 12, 2016State Public Notification requested5 linked violations
- October 31, 2016State Public Notification requested7 linked violations
- February 22, 2016State Public Notification received5 linked violations
- April 8, 2015State Public Notification requested18 linked violations
- March 3, 2015State Compliance achieved7 linked violations
- March 3, 2015State Public Notification received7 linked violations
- January 14, 2015State Public Notification requested6 linked violations
- September 14, 2011State Violation/Reminder Notice5 linked violations
- January 8, 2010State Public Notification requested1 linked violation
- October 23, 2009State Public Notification requested3 linked violations
- October 23, 2009State Violation/Reminder Notice4 linked violations
- June 22, 2009State Public Notification received4 linked violations
- June 11, 2009State Violation/Reminder Notice2 linked violations
- March 30, 2009State Violation/Reminder Notice2 linked violations
- March 30, 2009State Public Notification requested1 linked violation
- March 13, 2009State Public Notification received1 linked violation
- January 23, 2009State Violation/Reminder Notice1 linked violation
- January 23, 2009State Public Notification requested1 linked violation
- December 12, 2008State Public Notification received1 linked violation
- November 3, 2008State Public Notification requested1 linked violation
- November 3, 2008State Violation/Reminder Notice1 linked violation
- August 1, 2003State Compliance achieved5 linked violations
- November 1, 1986State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- March 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- January 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- October 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- April 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- October 1, 1980State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- June 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
Common questions
Is ETOILE WSC required to publish a Consumer Confidence Report?
- Yes. ETOILE 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 ETOILE WSC’s next Consumer Confidence Report due?
- ETOILE WSC’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does ETOILE WSC have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for ETOILE 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
FRANKLIN, TANNER
936-854-2215
ETOILE, TX 75944-0067