MISSOULA, MT · Missoula County
WYE AREA WATER SYSTEM Water System
Consumer Confidence Report status
WYE AREA 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 WYE AREA 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 Montana’s official records. Always confirm current status with Montana before making decisions based on this information.
System facts
- System ID (PWSID)
- MT0004107
- System type
- Community Water System
- Population served
- 512
- Service connections
- 183
- Ownership
- privately owned
- Water source
- groundwater (wells)
WYE AREA WATER SYSTEM is one of 123 community water systems in Montana in the 501 to 3,300 people size category, serving 512 people from groundwater.
As of August 1, 2026, its federal record holds 1 entry in 2012, all of which EPA lists as closed. Nothing has been added since 2012.
All 1 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 Groundwater Rule.
Violation history
Monitoring, Source Water (GWR)
—E. COLI
September 1, 2012 – October 26, 2012
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| September 1, 2012 – October 26, 2012 | Monitoring, Source Water (GWR) | E. COLI | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- March 17, 2025State Compliance achieved1 linked violation
- February 4, 2025State Violation/Reminder Notice1 linked violation
- July 20, 2016State Public Notification requested1 linked violation
- July 20, 2016State Violation/Reminder Notice1 linked violation
- July 6, 2016State Compliance achieved1 linked violation
- August 21, 2013State Compliance achieved1 linked violation
- August 1, 2013State Public Notification received1 linked violation
- July 29, 2013State Public Notification requested1 linked violation
- July 29, 2013State Violation/Reminder Notice1 linked violation
- July 29, 2013State Violation/Reminder Notice1 linked violation
- December 13, 2012State Compliance achieved1 linked violation
- November 27, 2012State Public Notification received1 linked violation
- November 21, 2012State Violation/Reminder Notice1 linked violation
- November 21, 2012State Public Notification requested1 linked violation
- November 21, 2012State Violation/Reminder Notice1 linked violation
- October 26, 2012State Compliance achieved2 linked violations
- October 18, 2012State Violation/Reminder Notice1 linked violation
- October 18, 2012State Public Notification requested1 linked violation
- October 18, 2012State Violation/Reminder Notice1 linked violation
- October 18, 2012State Public Notification requested1 linked violation
- June 27, 2012State Compliance achieved1 linked violation
- June 15, 2012State Violation/Reminder Notice1 linked violation
- June 15, 2012State Public Notification requested1 linked violation
- January 23, 2012State Compliance achieved1 linked violation
- January 3, 2012State Public Notification requested1 linked violation
- January 3, 2012State Violation/Reminder Notice1 linked violation
- December 7, 2011State Compliance achieved1 linked violation
- November 25, 2011State Public Notification received1 linked violation
- November 17, 2011State Violation/Reminder Notice1 linked violation
- November 17, 2011State Public Notification requested1 linked violation
- November 17, 2011State Violation/Reminder Notice1 linked violation
- November 9, 2011State Compliance achieved1 linked violation
- October 31, 2011State Public Notification requested1 linked violation
- October 31, 2011State Violation/Reminder Notice1 linked violation
- December 7, 2010State Compliance achieved1 linked violation
- November 24, 2010State Public Notification requested1 linked violation
- November 24, 2010State Violation/Reminder Notice1 linked violation
- November 24, 2010State Public Notification requested1 linked violation
- November 24, 2010State Violation/Reminder Notice1 linked violation
- November 3, 2010State Compliance achieved1 linked violation
- October 28, 2010State Public Notification received1 linked violation
- October 12, 2010State Violation/Reminder Notice1 linked violation
- October 12, 2010State Public Notification requested1 linked violation
- October 12, 2010State Violation/Reminder Notice1 linked violation
- July 1, 2010State Violation/Reminder Notice1 linked violation
- July 1, 2010State Public Notification requested1 linked violation
- May 7, 2010State Compliance achieved1 linked violation
- November 25, 2009State Compliance achieved1 linked violation
- November 17, 2009State Violation/Reminder Notice1 linked violation
- November 17, 2009State Public Notification requested3 linked violations
- August 3, 2009State Public Notification requested1 linked violation
- August 14, 2008State Compliance achieved2 linked violations
- August 14, 2008State Public Notification requested1 linked violation
- August 5, 2008State Violation/Reminder Notice2 linked violations
- July 31, 2008State Compliance achieved1 linked violation
- February 15, 2007State Compliance achieved1 linked violation
- January 24, 2007State Compliance achieved1 linked violation
- January 14, 2007State Violation/Reminder Notice1 linked violation
- January 14, 2007State Public Notification requested1 linked violation
- September 21, 2006State Administrative/Compliance Order with penalty issued1 linked violation
- July 25, 2006State Other1 linked violation
- August 16, 2005State Violation/Reminder Notice1 linked violation
- April 14, 2005State Compliance achieved7 linked violations
- January 12, 2005State Public Notification received9 linked violations
- December 31, 2004State Public Notification requested2 linked violations
- December 31, 2004State Violation/Reminder Notice4 linked violations
- December 31, 2004State Violation/Reminder Notice4 linked violations
- April 4, 2003State Public Notification received3 linked violations
- April 4, 2003State Compliance achieved8 linked violations
- December 24, 2002State Violation/Reminder Notice3 linked violations
- May 19, 2001State Public Notification requested1 linked violation
- May 19, 2001State Violation/Reminder Notice1 linked violation
Common questions
Is WYE AREA WATER SYSTEM required to publish a Consumer Confidence Report?
- Yes. WYE AREA 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 WYE AREA WATER SYSTEM’s next Consumer Confidence Report due?
- WYE AREA WATER SYSTEM’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does WYE AREA WATER SYSTEM have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for WYE AREA 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
WILLIAMS, DENNIS
406-531-6472
MISSOULA, MT 59808