Is JIM HOGG COUNTY WCID 2 required to publish a Consumer Confidence Report?

Yes. JIM HOGG COUNTY WCID 2 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 JIM HOGG COUNTY WCID 2’s next Consumer Confidence Report due?

JIM HOGG COUNTY WCID 2’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.

HEBBRONVILLE, TX · Jim Hogg County

JIM HOGG COUNTY WCID 2 Water System

Consumer Confidence Report status

JIM HOGG COUNTY WCID 2 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 1 item for JIM HOGG COUNTY WCID 2 that is open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.

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): TX1240001
System type: Community Water System
Population served: 5,397
Service connections: 1,799
Ownership: local government
Water source: groundwater (wells)

JIM HOGG COUNTY WCID 2 is one of 817 community water systems in Texas in the 3,301 to 10,000 people size category, serving 5,397 people from groundwater.

As of August 1, 2026, its federal record holds 35 entries between 1980 and 2024, of which 1 remains open; none are health-based.

Of the 35, 4 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 inorganic chemicals, the Groundwater Rule, and the Consumer Confidence Rule.

Violation history

Public Notification Violation for NPDWR Violation
—
Public Notice
November 21, 2024 – November 25, 2024
Resolved
Monitoring, Source Water (GWR)
—
E. COLI
July 24, 2024
Unaddressed
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2024 – June 30, 2024
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2019 – June 30, 2019
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
October 1, 2017 – December 31, 2017
Resolved
Monitoring, Source Water (GWR)
—
E. COLI
July 1, 2017 – October 21, 2019
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2017 – June 30, 2017
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2017 – March 31, 2017
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
October 1, 2016 – December 31, 2016
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2016 – September 30, 2016
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2016 – March 31, 2016
Resolved
Consumer Confidence Report Inadequate Reporting
—
Consumer Confidence Rule
July 1, 2015 – November 16, 2015
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
October 1, 2014 – December 31, 2014
Resolved
Consumer Confidence Report Inadequate Reporting
—
Consumer Confidence Rule
July 1, 2014 – May 18, 2017
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2013 – June 30, 2013
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2013 – March 31, 2013
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
October 1, 2012 – December 31, 2012
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2012 – September 30, 2012
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2011 – September 30, 2011
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
April 1, 2011 – June 30, 2011
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2010 – June 30, 2010
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
July 1, 2009 – September 30, 2009
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2009 – September 30, 2009
Resolved
Notification, Public
—
Arsenic
April 1, 2001 – June 30, 2001
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2001 – December 31, 2001
Resolved
Maximum Contaminant Level Violation, Single Sample
Health-based
Arsenic
January 1, 1999 – December 31, 2001
Resolved
Maximum Contaminant Level Violation, Single Sample
Health-based
Arsenic
January 1, 1999 – December 31, 2001
Resolved
Maximum Contaminant Level Violation, Single Sample
Health-based
Arsenic
January 1, 1999 – December 31, 2001
Resolved
Maximum Contaminant Level Violation, Single Sample
Health-based
Arsenic
January 1, 1999 – December 31, 1999
Resolved
Maximum Contaminant Level Violation, Single Sample
Health-based
Arsenic
January 1, 1997 – December 31, 1997
Resolved
Maximum Contaminant Level Violation, Single Sample
Health-based
Arsenic
January 1, 1996 – December 31, 1996
Resolved
Maximum Contaminant Level Violation, Monthly (TCR)
Health-based
Coliform (TCR)
July 1, 1993 – July 31, 1993
Archived
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 1993 – December 31, 1995
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
December 11, 1984 – December 10, 1985
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
January 11, 1980 – February 10, 1980
Archived

Resolved addressed and confirmed by the stateUnaddressed no corrective action on record yetArchived closed in EPA's records (typically due to age or a data correction)

Period	Violation	Contaminant / rule	Health-based	Status
November 21, 2024 – November 25, 2024	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
July 24, 2024	Monitoring, Source Water (GWR)	E. COLI	—	Unaddressed
April 1, 2024 – June 30, 2024	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
April 1, 2019 – June 30, 2019	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
October 1, 2017 – December 31, 2017	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2017 – October 21, 2019	Monitoring, Source Water (GWR)	E. COLI	—	Resolved
April 1, 2017 – June 30, 2017	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 2017 – March 31, 2017	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
October 1, 2016 – December 31, 2016	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2016 – September 30, 2016	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 2016 – March 31, 2016	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2015 – November 16, 2015	Consumer Confidence Report Inadequate Reporting	Consumer Confidence Rule	—	Resolved
October 1, 2014 – December 31, 2014	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2014 – May 18, 2017	Consumer Confidence Report Inadequate Reporting	Consumer Confidence Rule	—	Resolved
April 1, 2013 – June 30, 2013	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 2013 – March 31, 2013	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
October 1, 2012 – December 31, 2012	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2012 – September 30, 2012	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2011 – September 30, 2011	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
April 1, 2011 – June 30, 2011	Monitoring and Reporting (DBP)	Chlorine	—	Resolved
April 1, 2010 – June 30, 2010	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2009 – September 30, 2009	Monitoring and Reporting (DBP)	Chlorine	—	Resolved
July 1, 2009 – September 30, 2009	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
April 1, 2001 – June 30, 2001	Notification, Public	Arsenic	—	Resolved
January 1, 2001 – December 31, 2001	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 1999 – December 31, 2001	Maximum Contaminant Level Violation, Single Sample	Arsenic	Health-based	Resolved
January 1, 1999 – December 31, 2001	Maximum Contaminant Level Violation, Single Sample	Arsenic	Health-based	Resolved
January 1, 1999 – December 31, 2001	Maximum Contaminant Level Violation, Single Sample	Arsenic	Health-based	Resolved
January 1, 1999 – December 31, 1999	Maximum Contaminant Level Violation, Single Sample	Arsenic	Health-based	Resolved
January 1, 1997 – December 31, 1997	Maximum Contaminant Level Violation, Single Sample	Arsenic	Health-based	Resolved
January 1, 1996 – December 31, 1996	Maximum Contaminant Level Violation, Single Sample	Arsenic	Health-based	Resolved
July 1, 1993 – July 31, 1993	Maximum Contaminant Level Violation, Monthly (TCR)	Coliform (TCR)	Health-based	Archived
January 1, 1993 – December 31, 1995	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
December 11, 1984 – December 10, 1985	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
January 11, 1980 – February 10, 1980	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived

Resolved addressed and confirmed by the stateUnaddressed no corrective action on record yetArchived closed in EPA's records (typically due to age or a data correction)

Enforcement actions

February 26, 2026State Violation/Reminder Notice5 linked violations
October 27, 2025State Public Notification received6 linked violations
October 27, 2025State Public Notification received4 linked violations
October 8, 2025State Public Notification requested5 linked violations
September 10, 2025State Public Notification requested5 linked violations
September 10, 2025State Public Notification requested3 linked violations
September 8, 2025State Violation/Reminder Notice4 linked violations
April 30, 2025State Public Notification requested7 linked violations
April 30, 2025State Public Notification requested6 linked violations
March 24, 2025State Public Notification received4 linked violations
March 11, 2025State Public Notification requested5 linked violations
November 25, 2024State Compliance achieved6 linked violations
October 28, 2024State Public Notification requested5 linked violations
October 11, 2024State Violation/Reminder Notice4 linked violations
August 22, 2024State Public Notification requested5 linked violations
August 22, 2024State Public Notification requested5 linked violations
August 14, 2024State Public Notification requested6 linked violations
May 1, 2024State Public Notification received5 linked violations
June 22, 2023State Public Notification received6 linked violations
March 27, 2023State Public Notification received7 linked violations
January 20, 2023State Public Notification requested8 linked violations
October 28, 2019State Compliance achieved18 linked violations
October 21, 2019State Compliance achieved6 linked violations
July 24, 2019State Public Notification received7 linked violations
June 25, 2019State Violation/Reminder Notice6 linked violations
June 25, 2019State Violation/Reminder Notice5 linked violations
April 25, 2019State Public Notification received9 linked violations
March 25, 2019State Public Notification received7 linked violations
March 21, 2019State Public Notification requested6 linked violations
October 24, 2018State Public Notification received5 linked violations
August 23, 2018State Public Notification received3 linked violations
August 17, 2018State Violation/Reminder Notice4 linked violations
August 17, 2018State Violation/Reminder Notice4 linked violations
July 2, 2018State Public Notification received4 linked violations
June 27, 2018State Violation/Reminder Notice4 linked violations
June 27, 2018State Violation/Reminder Notice4 linked violations
April 30, 2018State Violation/Reminder Notice41 linked violations
April 30, 2018State Public Notification requested2 linked violations
February 26, 2018State Public Notification requested3 linked violations
January 18, 2018State Public Notification requested3 linked violations
October 31, 2017State Public Notification received6 linked violations
May 24, 2017State Public Notification requested7 linked violations
May 18, 2017State Compliance achieved3 linked violations
April 7, 2017State Public Notification requested3 linked violations
February 27, 2017State Public Notification received2 linked violations
October 3, 2016State Public Notification requested7 linked violations
January 11, 2016State Public Notification requested3 linked violations
January 11, 2016State Violation/Reminder Notice3 linked violations
October 8, 2015State Public Notification requested3 linked violations
October 6, 2015State Violation/Reminder Notice4 linked violations
July 10, 2015State Violation/Reminder Notice3 linked violations
May 15, 2015State Compliance achieved2 linked violations
April 7, 2015State Compliance achieved2 linked violations
March 4, 2015State Public Notification received2 linked violations
February 6, 2015State Public Notification requested2 linked violations
January 27, 2015State Public Notification requested2 linked violations
January 27, 2015State Violation/Reminder Notice2 linked violations
October 16, 2014State Violation/Reminder Notice2 linked violations
September 30, 2014State Violation/Reminder Notice2 linked violations
September 30, 2014State Public Notification requested2 linked violations
July 30, 2014State Public Notification requested2 linked violations
March 31, 2014State Violation/Reminder Notice2 linked violations
February 5, 2014State Violation/Reminder Notice2 linked violations
December 4, 2013State Formal Notice of Violation issued18 linked violations
November 5, 2013State Public Notification received2 linked violations
September 25, 2013State Public Notification requested1 linked violation
September 25, 2013State Violation/Reminder Notice2 linked violations
July 17, 2013State Public Notification requested3 linked violations
July 11, 2013State Compliance achieved10 linked violations
June 11, 2013State Violation/Reminder Notice2 linked violations
March 8, 2013State Public Notification received2 linked violations
December 21, 2012State Violation/Reminder Notice2 linked violations
December 21, 2012State Violation/Reminder Notice2 linked violations
December 21, 2012State Public Notification requested3 linked violations
December 14, 2012State Violation/Reminder Notice2 linked violations
October 29, 2012State Violation/Reminder Notice2 linked violations
August 14, 2012State Violation/Reminder Notice2 linked violations
July 16, 2012State Public Notification requested3 linked violations
January 24, 2011State Compliance achieved3 linked violations
December 16, 2010State Public Notification received3 linked violations
September 17, 2010State Public Notification requested3 linked violations
July 12, 2010State Bilateral Compliance Agreement signed7 linked violations
October 21, 2009State Public Notification received5 linked violations
October 1, 2009State Violation/Reminder Notice1 linked violation
September 25, 2009State Public Notification received1 linked violation
April 15, 2009State Public Notification received1 linked violation
March 27, 2009State Violation/Reminder Notice1 linked violation
August 17, 2007State Bilateral Compliance Agreement signed10 linked violations
April 5, 2003State Compliance achieved1 linked violation
April 5, 2003State Compliance achieved1 linked violation
April 5, 2003State Compliance achieved1 linked violation
August 23, 2001State Public Notification received1 linked violation
January 17, 1997State Bilateral Compliance Agreement signed20 linked violations
December 21, 1995State Violation/Reminder Notice1 linked violation
December 21, 1995State Public Notification requested1 linked violation
December 21, 1995State Formal Notice of Violation issued2 linked violations
September 5, 1995State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
September 5, 1995State Public Notification requestedgeneral 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
January 11, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
January 11, 1980State Public Notification receivedgeneral compliance action — not tied to a specific violation on record

Common questions

Is JIM HOGG COUNTY WCID 2 required to publish a Consumer Confidence Report?: Yes. JIM HOGG COUNTY WCID 2 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 JIM HOGG COUNTY WCID 2’s next Consumer Confidence Report due?: JIM HOGG COUNTY WCID 2’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does JIM HOGG COUNTY WCID 2 have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show 1 item for JIM HOGG COUNTY WCID 2 that is open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.
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

CANTU, SANTOS

361-527-3287

HEBBRONVILLE, TX 78361-0148