CYPRESS, TX · San Jacinto County
TANGLEWOOD FOREST SUBDIVISION Water System
Consumer Confidence Report status
TANGLEWOOD FOREST SUBDIVISION 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 TANGLEWOOD FOREST SUBDIVISION.
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)
- TX2040054
- System type
- Community Water System
- Population served
- 118
- Service connections
- 43
- Ownership
- privately owned
- Water source
- groundwater (wells)
TANGLEWOOD FOREST SUBDIVISION is one of 4,188 community water systems in Texas in the 500 or fewer people size category, serving 118 people from groundwater.
As of August 1, 2026, its federal record holds 1 entry in 2009, all of which EPA lists as closed. Nothing has been added since 2009.
None of the 1 are monitoring or reporting requirements — the category that accounts for about four in five of all violations in EPA's national dataset; these involve water-quality, treatment, or public-notice findings instead. The record involves inorganic chemicals.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2009 – December 31, 2009
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| October 1, 2009 – December 31, 2009 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- June 18, 2024State Administrative/Compliance Order without penalty issued4 linked violations
- November 10, 2023State Compliance achieved4 linked violations
- June 15, 2022State Public Notification received3 linked violations
- November 11, 2021State Public Notification received5 linked violations
- October 7, 2021State Public Notification requested3 linked violations
- November 9, 2020State Compliance achieved4 linked violations
- December 21, 2016State Public Notification received4 linked violations
- July 15, 2016State Compliance achieved2 linked violations
- July 15, 2016State Compliance achieved2 linked violations
- July 15, 2016State Compliance achieved1 linked violation
- July 15, 2016State Compliance achieved1 linked violation
- July 15, 2016State Compliance achieved1 linked violation
- July 15, 2016State Compliance achieved3 linked violations
- July 15, 2016State Compliance achieved3 linked violations
- July 15, 2016State Compliance achieved2 linked violations
- July 15, 2016State Compliance achieved3 linked violations
- July 15, 2016State Compliance achieved3 linked violations
- July 15, 2016State Compliance achieved3 linked violations
- April 15, 2016State Compliance achieved1 linked violation
- April 5, 2016State Public Notification received1 linked violation
- April 5, 2016State Public Notification received1 linked violation
- April 5, 2016State Public Notification received1 linked violation
- April 5, 2016State Public Notification received2 linked violations
- March 29, 2016State Public Notification requested2 linked violations
- March 29, 2016State Public Notification requested2 linked violations
- March 29, 2016State Violation/Reminder Notice2 linked violations
- February 2, 2016State Public Notification requested2 linked violations
- February 2, 2016State Public Notification requested2 linked violations
- January 4, 2016State Public Notification received1 linked violation
- January 4, 2016State Public Notification received1 linked violation
- January 4, 2016State Compliance achieved1 linked violation
- December 7, 2015State Public Notification requested2 linked violations
- December 7, 2015State Public Notification requested2 linked violations
- December 7, 2015State Violation/Reminder Notice2 linked violations
- October 21, 2015State Violation/Reminder Notice2 linked violations
- July 23, 2015State Compliance achieved2 linked violations
- July 23, 2015State Public Notification received2 linked violations
- July 13, 2015State Violation/Reminder Notice2 linked violations
- July 10, 2015State Violation/Reminder Notice2 linked violations
- July 10, 2015State Public Notification requested2 linked violations
- March 16, 2015State Violation/Reminder Notice3 linked violations
- March 16, 2015State Public Notification requested5 linked violations
- January 15, 2015State Public Notification received2 linked violations
- January 15, 2015State Public Notification received2 linked violations
- October 14, 2014State Public Notification received3 linked violations
- August 26, 2014State Public Notification requested3 linked violations
- June 27, 2014State Public Notification requested3 linked violations
- June 27, 2014State Public Notification requested3 linked violations
- March 27, 2014State Public Notification received23 linked violations
- March 27, 2014State Public Notification received3 linked violations
- March 11, 2014State Public Notification requested3 linked violations
- March 11, 2014State Public Notification requested2 linked violations
- March 11, 2014State Public Notification requested3 linked violations
- March 11, 2014State Violation/Reminder Notice2 linked violations
- November 19, 2013State Public Notification received3 linked violations
- August 15, 2013State Violation/Reminder Notice3 linked violations
- August 7, 2013State Public Notification received1 linked violation
- August 7, 2013State Public Notification received10 linked violations
- June 4, 2013State Public Notification requested22 linked violations
- June 4, 2013State Public Notification requested2 linked violations
- May 15, 2013State Public Notification received4 linked violations
- May 15, 2013State Public Notification received2 linked violations
- May 15, 2013State Public Notification received2 linked violations
- May 15, 2013State Compliance achieved4 linked violations
- March 14, 2013State Violation/Reminder Notice2 linked violations
- March 14, 2013State Public Notification requested2 linked violations
- February 12, 2013State Public Notification received3 linked violations
- January 29, 2013State Public Notification requested22 linked violations
- January 29, 2013State Violation/Reminder Notice22 linked violations
- October 4, 2012State Public Notification requested18 linked violations
- October 4, 2012State Public Notification requested2 linked violations
- December 16, 2011State Compliance achieved4 linked violations
- December 10, 2009State Violation/Reminder Notice2 linked violations
- April 1, 1989State Formal Notice of Violation issued2 linked violations
- April 1, 1987State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- January 1, 1987State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- October 1, 1986State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- April 1, 1986State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- October 1, 1985State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- December 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- November 1, 1984State Public Notification receivedgeneral 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
- July 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- May 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- March 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- February 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- January 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
Common questions
Is TANGLEWOOD FOREST SUBDIVISION required to publish a Consumer Confidence Report?
- Yes. TANGLEWOOD FOREST SUBDIVISION 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 TANGLEWOOD FOREST SUBDIVISION’s next Consumer Confidence Report due?
- TANGLEWOOD FOREST SUBDIVISION’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does TANGLEWOOD FOREST SUBDIVISION have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for TANGLEWOOD FOREST SUBDIVISION.
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
THOMAS, CAREY, A
713-574-5953
CYPRESS, TX 77429-7080