Is HOLIDAY TRAV L PARK required to publish a Consumer Confidence Report?

Yes. HOLIDAY TRAV L PARK 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 HOLIDAY TRAV L PARK’s next Consumer Confidence Report due?

HOLIDAY TRAV L PARK’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.

DEL RIO, TX · Val Verde County

HOLIDAY TRAV L PARK Water System

Consumer Confidence Report status

HOLIDAY TRAV L PARK 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 HOLIDAY TRAV L PARK.

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): TX2330022
System type: Community Water System
Population served: 660
Service connections: 228
Ownership: privately owned
Water source: groundwater (wells)

HOLIDAY TRAV L PARK is one of 1,859 community water systems in Texas in the 501 to 3,300 people size category, serving 660 people from groundwater.

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

Of the 5, 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 synthetic organic chemicals, the Lead and Copper Rule, and the Stage 1 Disinfectants and Disinfection Byproducts Rule.

Violation history

Follow-up Or Routine LCR Tap M/R
—
Lead and Copper Rule
July 1, 2017 – February 8, 2018
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
April 1, 2016 – June 30, 2016
Resolved
Public Notification Violation for NPDWR Violation
—
Public Notice
January 1, 2012 – July 6, 2018
Resolved
Monitoring, Regular
—
Toxaphene
January 1, 2010 – December 31, 2012
Resolved
Monitoring, Regular
—
2,4-D
January 1, 2010 – December 31, 2012
Resolved

Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
July 1, 2017 – February 8, 2018	Follow-up Or Routine LCR Tap M/R	Lead and Copper Rule	—	Resolved
April 1, 2016 – June 30, 2016	Monitoring and Reporting (DBP)	Chlorine	—	Resolved
January 1, 2012 – July 6, 2018	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
January 1, 2010 – December 31, 2012	Monitoring, Regular	Toxaphene	—	Resolved
January 1, 2010 – December 31, 2012	Monitoring, Regular	2,4-D	—	Resolved

Resolved addressed and confirmed by the state

Enforcement actions

November 1, 2023State Compliance achieved4 linked violations
November 3, 2020State Compliance achieved7 linked violations
March 8, 2019State Public Notification requested6 linked violations
July 6, 2018State Public Notification received8 linked violations
July 6, 2018State Public Notification received34 linked violations
July 6, 2018State Public Notification received7 linked violations
May 18, 2018State Public Notification received31 linked violations
May 18, 2018State Public Notification received6 linked violations
December 15, 2017State Formal Notice of Violation issued18 linked violations
November 28, 2017State Violation/Reminder Notice9 linked violations
October 31, 2016State Violation/Reminder Notice11 linked violations
September 16, 2016State Compliance achieved8 linked violations
March 11, 2016State Violation/Reminder Notice10 linked violations
June 4, 2015State Compliance achieved43 linked violations
November 10, 2014State Public Notification requested25 linked violations
February 26, 2014State Violation/Reminder Notice29 linked violations
July 24, 2013State Formal Notice of Violation issued77 linked violations
October 1, 2009State Violation/Reminder Notice1 linked violation
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
June 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
April 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
September 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
August 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
July 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
June 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
May 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
April 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
March 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
October 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
September 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
July 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
June 1, 1982State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
April 1, 1982State Public Notification receivedgeneral 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
February 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
November 1, 1981State 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
September 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
August 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
July 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
June 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
May 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
January 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
December 1, 1980State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
November 1, 1980State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
July 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
May 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
March 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record

Common questions

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

MCINTIRE, JAMES

830-775-7275

DEL RIO, TX 78840-3371