DALLAS, TX · Tarrant County
COUNTRY OAKS MOBILE HOME PARK Water System
Consumer Confidence Report status
COUNTRY OAKS MOBILE HOME 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 COUNTRY OAKS MOBILE HOME 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)
- TX2200139
- System type
- Community Water System
- Population served
- 146
- Service connections
- 59
- Ownership
- privately owned
- Water source
- groundwater (wells)
COUNTRY OAKS MOBILE HOME PARK is one of 4,188 community water systems in Texas in the 500 or fewer people size category, serving 146 people from groundwater.
As of August 1, 2026, its federal record holds 2 entries in 2008, all of which EPA lists as closed. Nothing has been added since 2008.
All 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 inorganic chemicals.
Violation history
Monitoring, Regular
—Fluoride
January 1, 2008 – December 31, 2008
ResolvedMonitoring, Regular
—Nitrate
January 1, 2008 – December 31, 2008
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2008 – December 31, 2008 | Monitoring, Regular | Fluoride | — | Resolved |
| January 1, 2008 – December 31, 2008 | Monitoring, Regular | Nitrate | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- January 21, 2026State Violation/Reminder Notice3 linked violations
- May 12, 2025State Public Notification received2 linked violations
- May 12, 2025State Public Notification received22 linked violations
- September 5, 2024State Violation/Reminder Notice3 linked violations
- November 16, 2023State Compliance achieved3 linked violations
- October 30, 2023State Violation/Reminder Notice3 linked violations
- July 18, 2023State Public Notification received24 linked violations
- July 18, 2023State Public Notification received4 linked violations
- July 18, 2023State Public Notification received3 linked violations
- March 9, 2023State Compliance achieved2 linked violations
- March 7, 2023State Violation/Reminder Notice2 linked violations
- January 28, 2019State Violation/Reminder Notice3 linked violations
- December 11, 2018State Public Notification requested2 linked violations
- October 16, 2018State Violation/Reminder Notice4 linked violations
- September 13, 2018State Compliance achieved3 linked violations
- April 16, 2018State Public Notification received3 linked violations
- March 27, 2018State Public Notification requested4 linked violations
- March 15, 2018State no longer subject to Rule3 linked violations
- March 15, 2018State no longer subject to Rule3 linked violations
- March 12, 2018State Compliance achieved5 linked violations
- February 6, 2018State Public Notification requested2 linked violations
- February 6, 2018State Violation/Reminder Notice2 linked violations
- January 31, 2018State Public Notification requested3 linked violations
- October 24, 2017State Public Notification requested3 linked violations
- October 24, 2017State Violation/Reminder Notice4 linked violations
- January 13, 2017State Violation/Reminder Notice4 linked violations
- October 17, 2016State Public Notification requested5 linked violations
- September 16, 2016State Compliance achieved19 linked violations
- September 16, 2016State Compliance achieved4 linked violations
- September 16, 2016State Compliance achieved8 linked violations
- July 14, 2016State Public Notification requested5 linked violations
- October 30, 2015State Compliance achieved3 linked violations
- October 30, 2015State Compliance achieved1 linked violation
- October 30, 2015State Compliance achieved2 linked violations
- October 30, 2015State Compliance achieved3 linked violations
- October 30, 2015State Compliance achieved2 linked violations
- October 30, 2015State Compliance achieved1 linked violation
- October 30, 2015State Compliance achieved2 linked violations
- January 7, 2015State Compliance achieved5 linked violations
- January 7, 2015State Public Notification received4 linked violations
- November 3, 2014State Violation/Reminder Notice4 linked violations
- September 11, 2014State Violation/Reminder Notice5 linked violations
- July 22, 2014State Public Notification requested9 linked violations
- June 8, 2014State Administrative/Compliance Order with penalty issued64 linked violations
- December 6, 2013State Compliance achieved8 linked violations
- October 1, 2009State Violation/Reminder Notice1 linked violation
- April 6, 2009State Public Notification received1 linked violation
- March 27, 2009State Violation/Reminder Notice1 linked violation
- January 28, 2009State Formal Notice of Violation issued3 linked violations
- August 1, 1987State Formal Notice of Violation issued1 linked violation
- July 1, 1985State Formal Notice of Violation issued1 linked violation
- June 1, 1985State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- November 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
- December 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- November 1, 1983State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- October 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
- 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
- April 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 received1 linked violation
- October 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
- March 1, 1981State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- February 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
- October 1, 1980State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- September 1, 1980Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- December 1, 1979Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- November 1, 1979Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
- October 1, 1979Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
Common questions
Is COUNTRY OAKS MOBILE HOME PARK required to publish a Consumer Confidence Report?
- Yes. COUNTRY OAKS MOBILE HOME 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 COUNTRY OAKS MOBILE HOME PARK’s next Consumer Confidence Report due?
- COUNTRY OAKS MOBILE HOME PARK’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does COUNTRY OAKS MOBILE HOME PARK have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for COUNTRY OAKS MOBILE HOME 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
WATSON, GEORGE
214-536-7000
DALLAS, TX 75225-6063