SURPRISE, TX · Ector County
GARDENDALE MOBILE HOME AND RV PARK Water System
Consumer Confidence Report status
GARDENDALE MOBILE HOME AND RV 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 GARDENDALE MOBILE HOME AND RV 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)
- TX0680148
- System type
- Community Water System
- Population served
- 93
- Service connections
- 31
- Ownership
- privately owned
- Water source
- groundwater (wells)
GARDENDALE MOBILE HOME AND RV PARK is one of 4,188 community water systems in Texas in the 500 or fewer people size category, serving 93 people from groundwater.
As of August 1, 2026, its federal record holds 10 entries between 2012 and 2017, all of which EPA lists as closed. Nothing has been added since 2017.
Of the 10, 2 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 Public Notice Rule and Revised PN Rule, inorganic chemicals, and the Total Coliform Rules.
Violation history
Maximum Contaminant Level Violation, Single Sample
Health-basedNitrate
April 1, 2017 – June 30, 2017
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2017 – March 31, 2017
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
November 1, 2016 – November 30, 2016
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
October 13, 2016 – April 10, 2017
ResolvedMonitoring and Reporting (DBP)
—Chlorine
October 1, 2016 – December 31, 2016
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
April 11, 2016 – July 10, 2017
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
November 10, 2015 – February 21, 2016
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
September 10, 2015 – February 21, 2016
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
July 8, 2015 – April 10, 2017
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
May 13, 2012 – August 2, 2012
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| April 1, 2017 – June 30, 2017 | Maximum Contaminant Level Violation, Single Sample | Nitrate | Health-based | Resolved |
| January 1, 2017 – March 31, 2017 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| November 1, 2016 – November 30, 2016 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| October 13, 2016 – April 10, 2017 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| October 1, 2016 – December 31, 2016 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| April 11, 2016 – July 10, 2017 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| November 10, 2015 – February 21, 2016 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| September 10, 2015 – February 21, 2016 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| July 8, 2015 – April 10, 2017 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| May 13, 2012 – August 2, 2012 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- April 7, 2026State Public Notification received31 linked violations
- January 19, 2018State no longer subject to Rule17 linked violations
- August 21, 2017State Public Notification requested3 linked violations
- August 21, 2017State Violation/Reminder Notice2 linked violations
- August 16, 2017State Public Notification requested4 linked violations
- July 17, 2017State Violation/Reminder Notice2 linked violations
- July 13, 2017State Violation/Reminder Notice2 linked violations
- July 13, 2017State Public Notification requested8 linked violations
- July 12, 2017State Compliance achieved5 linked violations
- July 12, 2017State Administrative/Compliance Order with penalty issued21 linked violations
- June 26, 2017State Public Notification requested3 linked violations
- June 21, 2017State Compliance achieved5 linked violations
- June 12, 2017State Public Notification received4 linked violations
- June 12, 2017State Compliance achieved21 linked violations
- April 24, 2017State Violation/Reminder Notice4 linked violations
- April 10, 2017State Public Notification received4 linked violations
- April 10, 2017State Violation/Reminder Notice2 linked violations
- April 10, 2017State Public Notification requested3 linked violations
- April 10, 2017State Public Notification received3 linked violations
- April 7, 2017State Violation/Reminder Notice2 linked violations
- April 7, 2017State Violation/Reminder Notice4 linked violations
- March 6, 2017State Violation/Reminder Notice4 linked violations
- February 21, 2017State Violation/Reminder Notice3 linked violations
- January 10, 2017State Violation/Reminder Notice4 linked violations
- November 21, 2016State Violation/Reminder Notice4 linked violations
- October 31, 2016State Violation/Reminder Notice7 linked violations
- August 19, 2016State Formal Notice of Violation issued17 linked violations
- August 16, 2016State Violation/Reminder Notice11 linked violations
- May 17, 2016State Violation/Reminder Notice5 linked violations
- March 30, 2016State Violation/Reminder Notice5 linked violations
- March 23, 2016State Public Notification requested10 linked violations
- March 11, 2016State Public Notification requested4 linked violations
- March 4, 2016State Public Notification requested18 linked violations
- February 23, 2016State Violation/Reminder Notice3 linked violations
- February 21, 2016State Compliance achieved4 linked violations
- January 21, 2016State Compliance achieved4 linked violations
- January 14, 2016State Public Notification requested4 linked violations
- December 15, 2015State Compliance achieved31 linked violations
- December 14, 2015State Compliance achieved3 linked violations
- November 5, 2015State Violation/Reminder Notice2 linked violations
- October 13, 2015State Violation/Reminder Notice3 linked violations
- October 9, 2015State Public Notification requested3 linked violations
- September 16, 2015State Violation/Reminder Notice3 linked violations
- July 31, 2015State Violation/Reminder Notice3 linked violations
- June 26, 2015State Public Notification requested3 linked violations
- May 11, 2015State Compliance achieved3 linked violations
- May 11, 2015State Compliance achieved3 linked violations
- April 8, 2015State Public Notification requested3 linked violations
- April 7, 2015State Compliance achieved3 linked violations
- March 30, 2015State Violation/Reminder Notice3 linked violations
- March 6, 2015State Violation/Reminder Notice20 linked violations
- January 15, 2015State Violation/Reminder Notice4 linked violations
- July 1, 2012State Compliance achieved4 linked violations
- May 21, 2012State Violation/Reminder Notice3 linked violations
- March 26, 2012State Public Notification requested2 linked violations
- March 8, 2012State Public Notification requested2 linked violations
- February 6, 2012State Violation/Reminder Notice3 linked violations
- February 6, 2012State Public Notification requested2 linked violations
- August 2, 2011State Compliance achieved4 linked violations
- May 31, 2011State Public Notification requested3 linked violations
- May 31, 2011State Public Notification requested2 linked violations
- April 14, 2009State Public Notification received1 linked violation
- March 27, 2009State Violation/Reminder Notice1 linked violation
- September 1, 1984State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- July 1, 1983State Public Notification received1 linked violation
- July 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
Common questions
Is GARDENDALE MOBILE HOME AND RV PARK required to publish a Consumer Confidence Report?
- Yes. GARDENDALE MOBILE HOME AND RV 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 GARDENDALE MOBILE HOME AND RV PARK’s next Consumer Confidence Report due?
- GARDENDALE MOBILE HOME AND RV PARK’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does GARDENDALE MOBILE HOME AND RV PARK have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for GARDENDALE MOBILE HOME AND RV 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
HETLAND, WILLIAM
360-918-2200
SURPRISE, AZ 85387-6947