Is HACKBERRY CREEK SUBDIVISION required to publish a Consumer Confidence Report?

Yes. HACKBERRY CREEK 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 HACKBERRY CREEK SUBDIVISION’s next Consumer Confidence Report due?

HACKBERRY CREEK SUBDIVISION’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.

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.

AUSTIN, TX · Chambers County

HACKBERRY CREEK SUBDIVISION Water System

Consumer Confidence Report status

HACKBERRY CREEK 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 HACKBERRY CREEK 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): TX0360100
System type: Community Water System
Population served: 176
Service connections: 60
Ownership: privately owned
Water source: groundwater (wells)

HACKBERRY CREEK SUBDIVISION is one of 4,188 community water systems in Texas in the 500 or fewer people size category, serving 176 people from groundwater.

As of August 1, 2026, its federal record holds 19 entries between 2004 and 2010, all of which EPA lists as closed. Nothing has been added since 2010.

Of the 19, 13 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, inorganic chemicals, and the Consumer Confidence Rule.

Violation history

Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2010 – March 31, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2009 – June 30, 2009
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
October 1, 2008 – December 31, 2008
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2008 – September 30, 2008
Resolved
Consumer Confidence Report Complete Failure to Report
—
Consumer Confidence Rule
July 1, 2007 – December 22, 2010
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
January 1, 2007 – March 31, 2007
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
October 1, 2006 – December 31, 2006
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
July 1, 2006 – September 30, 2006
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
April 1, 2006 – June 30, 2006
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
January 1, 2006 – March 31, 2006
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
October 1, 2005 – December 31, 2005
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
July 1, 2005 – September 30, 2005
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
April 1, 2005 – June 30, 2005
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
January 1, 2005 – March 31, 2005
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
October 1, 2004 – December 31, 2004
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
July 1, 2004 – September 30, 2004
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
April 1, 2004 – June 30, 2004
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
January 1, 2004 – March 31, 2004
Resolved
Consumer Confidence Report Inadequate Reporting
—
Consumer Confidence Rule
January 1, 2004 – December 22, 2010
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	Arsenic	Health-based	Resolved
April 1, 2009 – June 30, 2009	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
October 1, 2008 – December 31, 2008	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2008 – September 30, 2008	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2007 – December 22, 2010	Consumer Confidence Report Complete Failure to Report	Consumer Confidence 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
April 1, 2006 – June 30, 2006	Monitoring and Reporting (DBP)	Chlorine	—	Resolved
January 1, 2006 – March 31, 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
January 1, 2005 – March 31, 2005	Monitoring and Reporting (DBP)	Chlorine	—	Resolved
October 1, 2004 – December 31, 2004	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
January 1, 2004 – December 22, 2010	Consumer Confidence Report Inadequate Reporting	Consumer Confidence Rule	—	Resolved

Resolved addressed and confirmed by the state

Enforcement actions

July 23, 2024State Administrative/Compliance Order without penalty issued5 linked violations
February 28, 2024State Compliance achieved10 linked violations
February 12, 2024State Violation/Reminder Notice3 linked violations
September 29, 2023State Compliance achieved6 linked violations
May 12, 2023State Formal Notice of Violation issued8 linked violations
April 28, 2023State Public Notification requested8 linked violations
December 20, 2022State Public Notification received3 linked violations
December 16, 2022State Violation/Reminder Notice4 linked violations
December 15, 2022State Violation/Reminder Notice3 linked violations
August 26, 2020State Compliance achieved6 linked violations
April 30, 2020State Violation/Reminder Notice4 linked violations
December 11, 2019State Public Notification requested4 linked violations
July 12, 2017State Administrative/Compliance Order with penalty issued7 linked violations
August 25, 2016State Compliance achieved9 linked violations
April 22, 2016State Public Notification received4 linked violations
January 25, 2016State Public Notification requested4 linked violations
June 20, 2014Federal Compliance achieved22 linked violations
April 21, 2014State Public Notification received4 linked violations
January 22, 2014State Violation/Reminder Notice25 linked violations
September 4, 2013State Public Notification received3 linked violations
July 17, 2013State Violation/Reminder Notice5 linked violations
April 30, 2013State Violation/Reminder Notice3 linked violations
December 14, 2012State Violation/Reminder Notice23 linked violations
September 17, 2012Federal Final Administrative Order issued22 linked violations
August 28, 2012State Public Notification requested3 linked violations
June 29, 2012State Compliance achieved3 linked violations
November 17, 2010State Public Notification requested4 linked violations
April 17, 2009State Violation/Reminder Notice1 linked violation
January 19, 2009State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
January 19, 2009State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
January 14, 2009State Public Notification received1 linked violation
October 27, 2008State Public Notification requested1 linked violation
October 27, 2008State Formal Notice of Violation issued1 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
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

Common questions

Is HACKBERRY CREEK SUBDIVISION required to publish a Consumer Confidence Report?: Yes. HACKBERRY CREEK 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 HACKBERRY CREEK SUBDIVISION’s next Consumer Confidence Report due?: HACKBERRY CREEK SUBDIVISION’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does HACKBERRY CREEK SUBDIVISION have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show no open violations for HACKBERRY CREEK 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

FOLTZ, SCOT, W

512-990-4400

AUSTIN, TX 78723-2476