ESCALANTE, UT · Garfield County
ESCALANTE TOWN WATER SYSTEM Water System
Consumer Confidence Report status
ESCALANTE TOWN WATER SYSTEM 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 ESCALANTE TOWN WATER SYSTEM.
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 Utah’s official records. Always confirm current status with Utah before making decisions based on this information.
System facts
- System ID (PWSID)
- UTAH09004
- System type
- Community Water System
- Population served
- 800
- Service connections
- 732
- Ownership
- local government
- Water source
- groundwater (wells)
ESCALANTE TOWN WATER SYSTEM is one of 141 community water systems in Utah in the 501 to 3,300 people size category, serving 800 people from groundwater.
As of August 1, 2026, its federal record holds 23 entries between 1984 and 2023, all of which EPA lists as closed. Nothing has been added since 2023.
Of the 23, 21 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 Total Coliform Rules, and the Radionuclides and Revised Rad Rule.
Violation history
Monitoring, Regular
—1,1,2-Trichloroethane
January 1, 2023 – December 31, 2023
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
June 1, 2021 – June 30, 2021
ResolvedMonitoring and Reporting (DBP)
—TTHM
July 1, 2015 – September 30, 2015
ResolvedMonitoring, Regular
—Radium-228
January 1, 2012 – March 31, 2012
ResolvedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
January 1, 2011 – September 25, 2015
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Ethylbenzene
January 1, 2011 – May 24, 2011
ResolvedMonitoring, Regular
—Styrene
January 1, 2011 – May 24, 2011
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
July 1, 2010 – July 26, 2010
ResolvedMonitoring, Regular
—Nitrate
January 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Antimony, Total
January 1, 2008 – June 23, 2010
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
May 1, 2000 – May 31, 2000
ArchivedMonitoring, Routine Minor (TCR)
—Coliform (TCR)
August 1, 1998 – August 31, 1998
ArchivedMonitoring, Routine Major (TCR)
—Coliform (TCR)
August 1, 1997 – August 31, 1997
ArchivedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
September 1, 1991 – September 30, 1991
ArchivedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
June 1, 1991 – June 30, 1991
ArchivedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
January 1, 1987 – January 31, 1987
ResolvedMonitoring, Regular
—Mercury
January 1, 1984 – January 31, 1984
ArchivedMonitoring, Regular
—Fluoride
January 1, 1984 – January 31, 1984
ArchivedMonitoring, Regular
—Nitrate
January 1, 1984 – January 31, 1984
ArchivedMonitoring, Regular
—Chromium
January 1, 1984 – January 31, 1984
ArchivedMonitoring, Regular
—Cadmium
January 1, 1984 – January 31, 1984
ArchivedMonitoring, Regular
—Selenium
January 1, 1984 – January 31, 1984
Archived
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2023 – December 31, 2023 | Monitoring, Regular | 1,1,2-Trichloroethane | — | Resolved |
| June 1, 2021 – June 30, 2021 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| July 1, 2015 – September 30, 2015 | Monitoring and Reporting (DBP) | TTHM | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2011 – September 25, 2015 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2011 – May 24, 2011 | Monitoring, Regular | Ethylbenzene | — | Resolved |
| January 1, 2011 – May 24, 2011 | Monitoring, Regular | Styrene | — | Resolved |
| July 1, 2010 – July 26, 2010 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| January 1, 2009 – December 31, 2009 | Monitoring, Regular | Nitrate | — | Resolved |
| January 1, 2008 – June 23, 2010 | Monitoring, Regular | Antimony, Total | — | Resolved |
| May 1, 2000 – May 31, 2000 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Archived |
| August 1, 1998 – August 31, 1998 | Monitoring, Routine Minor (TCR) | Coliform (TCR) | — | Archived |
| August 1, 1997 – August 31, 1997 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Archived |
| September 1, 1991 – September 30, 1991 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
| June 1, 1991 – June 30, 1991 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
| January 1, 1987 – January 31, 1987 | Monitoring, Regular | Gross Alpha, Excl. Radon and U | — | Resolved |
| January 1, 1984 – January 31, 1984 | Monitoring, Regular | Mercury | — | Archived |
| January 1, 1984 – January 31, 1984 | Monitoring, Regular | Fluoride | — | Archived |
| January 1, 1984 – January 31, 1984 | Monitoring, Regular | Nitrate | — | Archived |
| January 1, 1984 – January 31, 1984 | Monitoring, Regular | Chromium | — | Archived |
| January 1, 1984 – January 31, 1984 | Monitoring, Regular | Cadmium | — | Archived |
| January 1, 1984 – January 31, 1984 | Monitoring, Regular | Selenium | — | Archived |
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- April 19, 2024State Compliance achieved1 linked violation
- February 28, 2024State Compliance achieved1 linked violation
- February 28, 2024State Compliance achieved21 linked violations
- January 26, 2024State Formal Notice of Violation issued1 linked violation
- January 26, 2024State Formal Notice of Violation issued21 linked violations
- January 23, 2024State Public Notification requested1 linked violation
- January 23, 2024State Public Notification requested21 linked violations
- February 22, 2023State Compliance achieved1 linked violation
- December 3, 2022State Formal Notice of Violation issued1 linked violation
- December 3, 2022State Public Notification requested1 linked violation
- February 20, 2022State Public Notification requested1 linked violation
- February 20, 2022State Formal Notice of Violation issued1 linked violation
- August 31, 2021State Compliance achieved1 linked violation
- August 26, 2021State Formal Notice of Violation issued1 linked violation
- August 26, 2021State Public Notification requested1 linked violation
- August 26, 2021State Formal Notice of Violation issued1 linked violation
- August 26, 2021State Public Notification requested1 linked violation
- May 25, 2021State Compliance achieved1 linked violation
- May 25, 2021State Compliance achieved1 linked violation
- May 25, 2021State Compliance achieved1 linked violation
- December 22, 2017State Formal Notice of Violation issued1 linked violation
- December 22, 2017State Compliance achieved1 linked violation
- December 22, 2017State Public Notification requested1 linked violation
- February 28, 2017State Compliance achieved1 linked violation
- July 12, 2016State Compliance achieved2 linked violations
- June 18, 2016State Formal Notice of Violation issued2 linked violations
- June 18, 2016State Public Notification requested1 linked violation
- June 18, 2016State Formal Notice of Violation issued1 linked violation
- June 18, 2016State Public Notification requested1 linked violation
- June 18, 2016State Formal Notice of Violation issued1 linked violation
- June 18, 2016State Public Notification requested1 linked violation
- June 18, 2016State Formal Notice of Violation issued1 linked violation
- June 18, 2016State Public Notification requested1 linked violation
- June 18, 2016State Formal Notice of Violation issued1 linked violation
- June 18, 2016State Public Notification requested2 linked violations
- June 15, 2016State Compliance achieved4 linked violations
- September 30, 2015State Compliance achieved5 linked violations
- September 25, 2015State Compliance achieved1 linked violation
- November 8, 2013State Formal Notice of Violation issued1 linked violation
- November 8, 2013State Public Notification requested1 linked violation
- December 17, 2012State Public Notification requested1 linked violation
- December 17, 2012State Formal Notice of Violation issued1 linked violation
- October 1, 2012State Compliance achieved5 linked violations
- October 1, 2012State Compliance achieved5 linked violations
- October 1, 2012State Compliance achieved1 linked violation
- October 1, 2012State Compliance achieved1 linked violation
- October 1, 2012State Compliance achieved1 linked violation
- May 17, 2012State Public Notification requested1 linked violation
- May 17, 2012State Formal Notice of Violation issued1 linked violation
- May 17, 2012State Public Notification requested1 linked violation
- May 17, 2012State Formal Notice of Violation issued1 linked violation
- May 17, 2012State Public Notification requested1 linked violation
- May 17, 2012State Formal Notice of Violation issued1 linked violation
- April 2, 2012State Compliance achieved1 linked violation
- April 2, 2012State Compliance achieved1 linked violation
- April 2, 2012State Compliance achieved1 linked violation
- January 20, 2012State Formal Notice of Violation issued1 linked violation
- January 20, 2012State Public Notification requested1 linked violation
- January 20, 2012State Public Notification requested1 linked violation
- January 20, 2012State Formal Notice of Violation issued1 linked violation
- January 20, 2012State Public Notification requested21 linked violations
- January 20, 2012State Formal Notice of Violation issued21 linked violations
- January 20, 2012State Public Notification requested1 linked violation
- January 20, 2012State Formal Notice of Violation issued1 linked violation
- November 4, 2011State Formal Notice of Violation issued5 linked violations
- November 4, 2011State Public Notification requested5 linked violations
- August 6, 2011State Formal Notice of Violation issued1 linked violation
- August 6, 2011State Public Notification requested1 linked violation
- May 24, 2011State Compliance achieved21 linked violations
- May 6, 2011State Formal Notice of Violation issued5 linked violations
- May 6, 2011State Public Notification requested5 linked violations
- April 7, 2011State Compliance achieved3 linked violations
- February 16, 2011State Compliance achieved1 linked violation
- February 13, 2011State Formal Notice of Violation issued1 linked violation
- February 13, 2011State Public Notification requested1 linked violation
- January 17, 2011State Public Notification requested12 linked violations
- January 17, 2011State Public Notification requested5 linked violations
- January 17, 2011State Formal Notice of Violation issued5 linked violations
- January 17, 2011State Formal Notice of Violation issued12 linked violations
- November 13, 2010State Public Notification requested5 linked violations
- November 13, 2010State Formal Notice of Violation issued5 linked violations
- July 26, 2010State Compliance achieved5 linked violations
- June 23, 2010State Compliance achieved12 linked violations
- August 30, 2006State Compliance achieved104 linked violations
- November 9, 2005State Compliance achieved8 linked violations
- June 30, 2000State Formal Notice of Violation issued3 linked violations
- September 29, 1997State Public Notification requested1 linked violation
- September 29, 1997State Formal Notice of Violation issued1 linked violation
- February 1, 1990State Technical Assistance Visit2 linked violations
- November 30, 1989State Technical Assistance Visitgeneral compliance action — not tied to a specific violation on record
Common questions
Is ESCALANTE TOWN WATER SYSTEM required to publish a Consumer Confidence Report?
- Yes. ESCALANTE TOWN WATER SYSTEM 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 ESCALANTE TOWN WATER SYSTEM’s next Consumer Confidence Report due?
- ESCALANTE TOWN WATER SYSTEM’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does ESCALANTE TOWN WATER SYSTEM have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for ESCALANTE TOWN WATER SYSTEM.
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
STEED, STEPHANIE
435-826-4644
ESCALANTE, UT 84726