HOUSTON, TX · Victoria County
ARENOSA CREEK ESTATES Water System
Consumer Confidence Report status
ARENOSA CREEK ESTATES 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 ARENOSA CREEK ESTATES.
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)
- TX2350042
- System type
- Community Water System
- Population served
- 75
- Service connections
- 33
- Ownership
- privately owned
- Water source
- groundwater (wells)
ARENOSA CREEK ESTATES is one of 4,188 community water systems in Texas in the 500 or fewer people size category, serving 75 people from groundwater.
As of August 1, 2026, its federal record holds 23 entries between 2008 and 2021, all of which EPA lists as closed. Nothing has been added since 2021.
Of the 23, 7 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, the Public Notice Rule and Revised PN Rule, and the Stage 1 Disinfectants and Disinfection Byproducts Rule.
Violation history
Monitoring and Reporting (DBP)
—Chlorine
January 1, 2021 – March 31, 2021
ResolvedLead Consumer Notice
—Lead and Copper Rule
December 30, 2020 – December 27, 2022
ResolvedLead Consumer Notice
—Lead and Copper Rule
December 30, 2019 – March 13, 2020
ResolvedMonitoring and Reporting (DBP)
—Chlorine
April 1, 2018 – June 30, 2018
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2018 – March 31, 2018
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
March 13, 2017 – May 30, 2017
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
September 1, 2016 – September 30, 2016
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
April 1, 2013 – June 30, 2013
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2013 – June 30, 2013
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
January 10, 2013 – May 7, 2013
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
January 1, 2013 – March 31, 2013
ResolvedMonitoring, Routine Minor (TCR)
—Coliform (TCR)
September 1, 2012 – September 30, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2012 – September 30, 2012
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
June 27, 2012 – September 11, 2013
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
June 27, 2012 – September 11, 2013
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
April 1, 2012 – June 30, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2011 – September 30, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
July 1, 2011 – September 30, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2011 – June 30, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2009 – December 31, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
October 1, 2009 – December 31, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
January 1, 2008 – December 31, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2008 – December 31, 2008
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2021 – March 31, 2021 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| December 30, 2020 – December 27, 2022 | Lead Consumer Notice | Lead and Copper Rule | — | Resolved |
| December 30, 2019 – March 13, 2020 | Lead Consumer Notice | Lead and Copper Rule | — | Resolved |
| April 1, 2018 – June 30, 2018 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 1, 2018 – March 31, 2018 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| March 13, 2017 – May 30, 2017 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| September 1, 2016 – September 30, 2016 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| April 1, 2013 – June 30, 2013 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| April 1, 2013 – June 30, 2013 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 10, 2013 – May 7, 2013 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| January 1, 2013 – March 31, 2013 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| September 1, 2012 – September 30, 2012 | Monitoring, Routine Minor (TCR) | Coliform (TCR) | — | Resolved |
| July 1, 2012 – September 30, 2012 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| June 27, 2012 – September 11, 2013 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| June 27, 2012 – September 11, 2013 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| April 1, 2012 – June 30, 2012 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| July 1, 2011 – September 30, 2011 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2011 – September 30, 2011 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| April 1, 2011 – June 30, 2011 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2009 – December 31, 2009 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2009 – December 31, 2009 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| January 1, 2008 – December 31, 2008 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| January 1, 2008 – December 31, 2008 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- December 31, 2025State Violation/Reminder Notice6 linked violations
- September 3, 2025State Public Notification requested3 linked violations
- March 10, 2025State Public Notification received10 linked violations
- January 16, 2025State Violation/Reminder Notice5 linked violations
- December 23, 2024State Public Notification received25 linked violations
- April 25, 2024State Compliance achieved22 linked violations
- September 18, 2023State Public Notification requested5 linked violations
- November 22, 2022State Compliance achieved12 linked violations
- October 21, 2022State Compliance achieved5 linked violations
- July 28, 2021State Violation/Reminder Notice4 linked violations
- June 23, 2021State Public Notification requested4 linked violations
- March 13, 2020State Compliance achieved7 linked violations
- February 16, 2020State Compliance achieved5 linked violations
- December 2, 2019State Compliance achieved6 linked violations
- December 2, 2019State Public Notification received10 linked violations
- July 25, 2019State Violation/Reminder Notice5 linked violations
- March 22, 2019State Public Notification requested5 linked violations
- March 11, 2019State Violation/Reminder Notice5 linked violations
- January 7, 2019State Public Notification requested4 linked violations
- June 25, 2018State Public Notification requested4 linked violations
- January 22, 2018State Public Notification requested4 linked violations
- January 11, 2018State Compliance achieved5 linked violations
- December 11, 2017State Public Notification requested5 linked violations
- October 24, 2017State Public Notification requested4 linked violations
- October 24, 2017State Violation/Reminder Notice2 linked violations
- July 5, 2017State Public Notification received3 linked violations
- April 10, 2017State Violation/Reminder Notice4 linked violations
- April 6, 2017State Violation/Reminder Notice46 linked violations
- November 22, 2016State Public Notification received5 linked violations
- October 17, 2016State Violation/Reminder Notice5 linked violations
- October 8, 2015Federal Compliance achieved34 linked violations
- October 6, 2015State Violation/Reminder Notice3 linked violations
- March 23, 2015State Compliance achieved41 linked violations
- July 8, 2014State Public Notification received4 linked violations
- July 7, 2014State Compliance achieved5 linked violations
- July 7, 2014State Compliance achieved4 linked violations
- June 20, 2014State Violation/Reminder Notice5 linked violations
- March 11, 2014State Violation/Reminder Notice5 linked violations
- January 22, 2014State Compliance achieved7 linked violations
- January 2, 2014State Public Notification requested4 linked violations
- November 26, 2013State Compliance achieved2 linked violations
- November 14, 2013State Public Notification requested3 linked violations
- November 14, 2013State Public Notification requested3 linked violations
- September 11, 2013State Compliance achieved4 linked violations
- September 10, 2013State Public Notification received3 linked violations
- September 9, 2013State Violation/Reminder Notice4 linked violations
- May 7, 2013State Violation/Reminder Notice3 linked violations
- May 7, 2013State Public Notification requested2 linked violations
- March 26, 2013State Violation/Reminder Notice1 linked violation
- March 26, 2013State Violation/Reminder Notice2 linked violations
- March 5, 2013State Violation/Reminder Notice1 linked violation
- March 5, 2013State Violation/Reminder Notice2 linked violations
- March 5, 2013State Violation/Reminder Notice4 linked violations
- January 10, 2013State Public Notification received5 linked violations
- January 10, 2013State Compliance achieved5 linked violations
- December 14, 2012State Violation/Reminder Notice4 linked violations
- November 27, 2012State Public Notification requested4 linked violations
- November 13, 2012State Public Notification requested4 linked violations
- November 13, 2012State Public Notification requested3 linked violations
- November 1, 2012State Compliance achieved23 linked violations
- September 11, 2012State Violation/Reminder Notice4 linked violations
- June 8, 2012Federal Final Administrative Order issued34 linked violations
- June 4, 2012State Public Notification requested3 linked violations
- June 4, 2012State Violation/Reminder Notice18 linked violations
- June 4, 2012State Violation/Reminder Notice4 linked violations
- April 10, 2012State Public Notification received5 linked violations
- March 6, 2012State Public Notification requested3 linked violations
- March 6, 2012State Public Notification requested3 linked violations
- March 6, 2012State Public Notification requested3 linked violations
- March 6, 2012State Violation/Reminder Notice3 linked violations
- March 6, 2012State Public Notification requested3 linked violations
- November 18, 2011State Public Notification requested4 linked violations
- October 6, 2011State Public Notification requested15 linked violations
- August 1, 2010State Compliance achieved3 linked violations
- December 16, 2009State Public Notification requested3 linked violations
- December 7, 2009State Public Notification received1 linked violation
- December 7, 2009State Public Notification received1 linked violation
- November 20, 2009State Violation/Reminder Notice1 linked violation
- November 20, 2009State Public Notification requested1 linked violation
- November 20, 2009State Violation/Reminder Notice1 linked violation
- November 20, 2009State Public Notification requested1 linked violation
- September 8, 2009State Public Notification received1 linked violation
- September 8, 2009State Public Notification received3 linked violations
- September 8, 2009State Public Notification received1 linked violation
- November 13, 2008State Public Notification received1 linked violation
- November 13, 2008State Public Notification received1 linked violation
- November 13, 2008State Public Notification received1 linked violation
- June 18, 2008State Public Notification received1 linked violation
- January 13, 2008State Public Notification received1 linked violation
- August 17, 2007State Bilateral Compliance Agreement signed23 linked violations
Common questions
Is ARENOSA CREEK ESTATES required to publish a Consumer Confidence Report?
- Yes. ARENOSA CREEK ESTATES 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 ARENOSA CREEK ESTATES’s next Consumer Confidence Report due?
- ARENOSA CREEK ESTATES’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does ARENOSA CREEK ESTATES have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for ARENOSA CREEK ESTATES.
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
HOLZHEAUSER, KENNETH
281-743-1255
HOUSTON, TX 77082-2624