CEDAR CITY, UT · Iron County
MONTE VISTA COMMUNITY WATER CO Water System
Consumer Confidence Report status
MONTE VISTA COMMUNITY WATER CO 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 MONTE VISTA COMMUNITY WATER CO 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 Utah’s official records. Always confirm current status with Utah before making decisions based on this information.
System facts
- System ID (PWSID)
- UTAH11036
- System type
- Community Water System
- Population served
- 150
- Service connections
- 57
- Ownership
- privately owned
- Water source
- groundwater (wells)
MONTE VISTA COMMUNITY WATER CO is one of 338 community water systems in Utah in the 500 or fewer people size category, serving 150 people from groundwater.
As of August 1, 2026, its federal record holds 29 entries between 1991 and 2025, of which 1 remains open; none are health-based.
Of the 29, 20 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 Total Coliform Rules, synthetic organic chemicals, and inorganic chemicals.
Violation history
Consumer Confidence Report Inadequate Reporting
—Consumer Confidence Rule
October 2, 2025
UnaddressedMonitoring and Reporting (DBP)
—TTHM
January 1, 2025 – December 31, 2025
ArchivedMonitoring, Regular
—Nitrate
January 1, 2022 – December 31, 2022
ResolvedMonitoring, Regular
—Chlordane
January 1, 2020 – December 31, 2022
ResolvedMonitoring, Regular
—2,4-D
January 1, 2020 – December 31, 2022
ResolvedMonitoring, Regular
—Di(2-ethylhexyl) adipate
January 1, 2020 – December 31, 2022
ResolvedMonitoring, Regular
—Di(2-ethylhexyl) phthalate
January 1, 2020 – December 31, 2022
ResolvedMonitoring, Regular
—Dinoseb
January 1, 2020 – December 31, 2022
ResolvedMonitoring, Regular
—Atrazine
January 1, 2020 – December 31, 2022
ResolvedMonitoring, Regular
—Nitrate
January 1, 2018 – December 31, 2018
ResolvedMonitoring, Source Water (GWR)
—E. COLI
July 1, 2017 – November 21, 2019
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
August 1, 2016 – August 31, 2016
ResolvedConsumer Confidence Report Complete Failure to Report
—Consumer Confidence Rule
July 1, 2015 – March 18, 2016
ResolvedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 2014 – January 14, 2015
ResolvedMonitoring, Source Water (GWR)
—E. COLI
August 1, 2013 – October 4, 2013
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
September 1, 2005 – September 30, 2005
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
August 1, 2004 – August 31, 2004
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
April 1, 2004 – April 30, 2004
ResolvedMonitoring, Repeat Major (TCR)
—Coliform (TCR)
October 1, 2003 – October 31, 2003
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
September 1, 2003 – September 30, 2003
ResolvedMonitoring, Repeat Major (TCR)
—Coliform (TCR)
September 1, 2002 – September 30, 2002
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
June 1, 2002 – June 30, 2002
ResolvedMonitoring, Regular
—Beryllium, Total
January 1, 2002 – December 31, 2010
ResolvedMonitoring, Regular
—Antimony, Total
January 1, 2002 – December 31, 2010
ResolvedMonitoring, Repeat Major (TCR)
—Coliform (TCR)
October 1, 2000 – October 31, 2000
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
August 1, 1999 – August 31, 1999
ArchivedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
June 1, 1999 – June 30, 1999
ArchivedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
May 1, 1999 – May 31, 1999
ArchivedMonitoring, Repeat Major (TCR)
—Coliform (TCR)
August 1, 1991 – August 31, 1991
Resolved
Unaddressed no corrective action on record yetArchived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| October 2, 2025 | Consumer Confidence Report Inadequate Reporting | Consumer Confidence Rule | — | Unaddressed |
| January 1, 2025 – December 31, 2025 | Monitoring and Reporting (DBP) | TTHM | — | Archived |
| January 1, 2022 – December 31, 2022 | Monitoring, Regular | Nitrate | — | Resolved |
| January 1, 2020 – December 31, 2022 | Monitoring, Regular | Chlordane | — | Resolved |
| January 1, 2020 – December 31, 2022 | Monitoring, Regular | 2,4-D | — | Resolved |
| January 1, 2020 – December 31, 2022 | Monitoring, Regular | Di(2-ethylhexyl) adipate | — | Resolved |
| January 1, 2020 – December 31, 2022 | Monitoring, Regular | Di(2-ethylhexyl) phthalate | — | Resolved |
| January 1, 2020 – December 31, 2022 | Monitoring, Regular | Dinoseb | — | Resolved |
| January 1, 2020 – December 31, 2022 | Monitoring, Regular | Atrazine | — | Resolved |
| January 1, 2018 – December 31, 2018 | Monitoring, Regular | Nitrate | — | Resolved |
| July 1, 2017 – November 21, 2019 | Monitoring, Source Water (GWR) | E. COLI | — | Resolved |
| August 1, 2016 – August 31, 2016 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| July 1, 2015 – March 18, 2016 | Consumer Confidence Report Complete Failure to Report | Consumer Confidence Rule | — | Resolved |
| October 1, 2014 – January 14, 2015 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| August 1, 2013 – October 4, 2013 | Monitoring, Source Water (GWR) | E. COLI | — | Resolved |
| September 1, 2005 – September 30, 2005 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| August 1, 2004 – August 31, 2004 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| April 1, 2004 – April 30, 2004 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| October 1, 2003 – October 31, 2003 | Monitoring, Repeat Major (TCR) | Coliform (TCR) | — | Resolved |
| September 1, 2003 – September 30, 2003 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| September 1, 2002 – September 30, 2002 | Monitoring, Repeat Major (TCR) | Coliform (TCR) | — | Resolved |
| June 1, 2002 – June 30, 2002 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Resolved |
| January 1, 2002 – December 31, 2010 | Monitoring, Regular | Beryllium, Total | — | Resolved |
| January 1, 2002 – December 31, 2010 | Monitoring, Regular | Antimony, Total | — | Resolved |
| October 1, 2000 – October 31, 2000 | Monitoring, Repeat Major (TCR) | Coliform (TCR) | — | Resolved |
| August 1, 1999 – August 31, 1999 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
| June 1, 1999 – June 30, 1999 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
| May 1, 1999 – May 31, 1999 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
| August 1, 1991 – August 31, 1991 | Monitoring, Repeat Major (TCR) | Coliform (TCR) | — | Resolved |
Unaddressed no corrective action on record yetArchived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state
Enforcement actions
- November 13, 2025State Public Notification requested2 linked violations
- November 1, 2025State Public Notification requested3 linked violations
- October 10, 2025State Formal Notice of Violation issued2 linked violations
- July 10, 2025State Formal Notice of Violation issued2 linked violations
- November 7, 2024State Public Notification requested4 linked violations
- July 12, 2024State Formal Notice of Violation issued4 linked violations
- October 25, 2023State Compliance achieved2 linked violations
- February 3, 2023State Public Notification requested27 linked violations
- February 3, 2023State Formal Notice of Violation issued26 linked violations
- October 9, 2021State Formal Notice of Violation issued2 linked violations
- May 12, 2021State Compliance achieved1 linked violation
- March 18, 2021State Compliance achieved2 linked violations
- February 6, 2021State Public Notification requested2 linked violations
- February 6, 2021State Formal Notice of Violation issued1 linked violation
- January 22, 2021State Public Notification requested2 linked violations
- January 22, 2021State Formal Notice of Violation issued4 linked violations
- June 19, 2020State Formal Notice of Violation issued1 linked violation
- January 31, 2020State Compliance achieved1 linked violation
- December 15, 2019State Compliance achieved1 linked violation
- December 15, 2019State Public Notification requested1 linked violation
- December 15, 2019State Formal Notice of Violation issued1 linked violation
- December 7, 2019State Public Notification requested1 linked violation
- November 21, 2019State Compliance achieved1 linked violation
- November 21, 2019State Compliance achieved1 linked violation
- November 21, 2019State Compliance achieved1 linked violation
- November 10, 2019State Compliance achieved1 linked violation
- November 7, 2019State Compliance achieved1 linked violation
- September 15, 2019State Public Notification requested1 linked violation
- September 15, 2019State Formal Notice of Violation issued1 linked violation
- August 31, 2019State Public Notification requested1 linked violation
- August 31, 2019State Formal Notice of Violation issued1 linked violation
- March 27, 2019State Compliance achieved1 linked violation
- February 28, 2019State Compliance achieved1 linked violation
- February 3, 2019State Public Notification requested1 linked violation
- February 3, 2019State Formal Notice of Violation issued1 linked violation
- December 15, 2018State Public Notification requested1 linked violation
- December 15, 2018State Formal Notice of Violation issued1 linked violation
- September 13, 2018State Compliance achieved1 linked violation
- June 15, 2018State Public Notification requested1 linked violation
- June 15, 2018State Formal Notice of Violation issued1 linked violation
- September 15, 2017State Formal Notice of Violation issued1 linked violation
- September 15, 2017State Public Notification requested1 linked violation
- July 14, 2017State Formal Notice of Violation issued1 linked violation
- July 14, 2017State Public Notification requested1 linked violation
- March 23, 2017State Compliance achieved1 linked violation
- September 17, 2016State Public Notification requested1 linked violation
- September 17, 2016State Formal Notice of Violation issued1 linked violation
- June 18, 2016State Formal Notice of Violation issued1 linked violation
- June 18, 2016State Public Notification requested1 linked violation
- May 1, 2016State Public Notification requested1 linked violation
- May 1, 2016State Formal Notice of Violation issued1 linked violation
- March 18, 2016State Compliance achieved1 linked violation
- February 8, 2016State Compliance achieved1 linked violation
- January 12, 2016State Formal Notice of Violation issued1 linked violation
- January 12, 2016State Public Notification requested1 linked violation
- January 9, 2016State Formal Notice of Violation issued1 linked violation
- September 28, 2015State Compliance achieved1 linked violation
- January 14, 2015State Compliance achieved1 linked violation
- December 6, 2014State Formal Notice of Violation issued1 linked violation
- December 6, 2014State Public Notification requested1 linked violation
- March 7, 2014State Formal Notice of Violation issued1 linked violation
- March 7, 2014State Compliance achieved1 linked violation
- March 7, 2014State Public Notification requested1 linked violation
- January 2, 2014State Public Notification requested1 linked violation
- January 2, 2014State Formal Notice of Violation issued1 linked violation
- October 4, 2013State Compliance achieved1 linked violation
- October 4, 2013State Formal Notice of Violation issued1 linked violation
- October 4, 2013State Public Notification requested1 linked violation
- October 4, 2013State Compliance achieved1 linked violation
- October 4, 2013State Public Notification requested1 linked violation
- October 4, 2013State Formal Notice of Violation issued1 linked violation
- January 19, 2013State Public Notification requested1 linked violation
- June 25, 2012State Formal Notice of Violation issued1 linked violation
- June 25, 2012State Public Notification requested1 linked violation
- June 18, 2012State Compliance achieved2 linked violations
- December 11, 2011State Compliance achieved1 linked violation
- August 18, 2011State Compliance achieved12 linked violations
- January 8, 2011State Public Notification requested2 linked violations
- December 12, 2010State Formal Notice of Violation issued1 linked violation
- December 12, 2010State Public Notification requested1 linked violation
- May 31, 2010State Compliance achieved2 linked violations
- December 18, 2007State Violation/Reminder Notice1 linked violation
- August 30, 2006State Compliance achieved5 linked violations
- September 28, 2004State Formal Notice of Violation issued5 linked violations
- May 27, 2004State Formal Notice of Violation issued2 linked violations
- October 31, 2003State Formal Notice of Violation issued1 linked violation
- October 31, 2003State Public Notification requested1 linked violation
- September 25, 2003State Public Notification received4 linked violations
- August 22, 2002State Public Notification requested1 linked violation
- November 21, 2000State Public Notification received1 linked violation
- October 30, 2000State Public Notification requested1 linked violation
- December 24, 1990State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- June 29, 1990State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
Common questions
Is MONTE VISTA COMMUNITY WATER CO required to publish a Consumer Confidence Report?
- Yes. MONTE VISTA COMMUNITY WATER CO 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 MONTE VISTA COMMUNITY WATER CO’s next Consumer Confidence Report due?
- MONTE VISTA COMMUNITY WATER CO’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does MONTE VISTA COMMUNITY WATER CO have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show 1 item for MONTE VISTA COMMUNITY WATER CO 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
OVESON, SETH
435-650-6439
CEDAR CITY, UT 84720