MISSOULA, MT · Missoula County
BONNER HOUSING PWS SYSTEM Water System
Consumer Confidence Report status
BONNER HOUSING PWS 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 BONNER HOUSING PWS 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)
- MT0000467
- System type
- Community Water System
- Population served
- 128
- Service connections
- 48
- Ownership
- privately owned
- Water source
- groundwater (wells)
BONNER HOUSING PWS SYSTEM is one of 1,084 community water systems in Montana in the 500 or fewer people size category, serving 128 people from groundwater.
As of August 1, 2026, its federal record holds 17 entries between 1995 and 2017, all of which EPA lists as closed. Nothing has been added since 2017.
Of the 17, 11 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 the Groundwater Rule.
Violation history
Monitoring, Source Water (GWR)
—E. COLI
July 27, 2017 – August 22, 2017
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
April 1, 2012 – April 30, 2012
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
December 1, 2010 – December 2, 2010
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
July 1, 2010 – July 31, 2010
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
August 1, 2009 – August 31, 2009
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
March 1, 2007 – March 31, 2007
ResolvedMonitoring, Regular
—Picloram
January 1, 2005 – December 31, 2007
ResolvedMonitoring, Regular
—Dalapon
January 1, 2005 – December 31, 2007
ResolvedMonitoring, Regular
—Dinoseb
January 1, 2005 – December 31, 2007
ResolvedMonitoring, Regular
—2,4-D
January 1, 2005 – December 31, 2007
ResolvedMonitoring, Regular
—Pentachlorophenol
January 1, 2005 – December 31, 2007
ResolvedWater Quality Parameter M/R
—Lead and Copper Rule
July 1, 2003 – December 31, 2003
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
September 1, 2002 – September 30, 2002
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
August 1, 2001 – August 31, 2001
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
February 1, 1996 – February 29, 1996
ResolvedMonitoring, Repeat Major (TCR)
—Coliform (TCR)
February 1, 1996 – February 29, 1996
ResolvedMonitoring, Repeat Major (TCR)
—Coliform (TCR)
December 1, 1995 – December 31, 1995
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| July 27, 2017 – August 22, 2017 | Monitoring, Source Water (GWR) | E. COLI | — | Resolved |
| April 1, 2012 – April 30, 2012 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| December 1, 2010 – December 2, 2010 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Resolved |
| July 1, 2010 – July 31, 2010 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Resolved |
| August 1, 2009 – August 31, 2009 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| March 1, 2007 – March 31, 2007 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| January 1, 2005 – December 31, 2007 | Monitoring, Regular | Picloram | — | Resolved |
| January 1, 2005 – December 31, 2007 | Monitoring, Regular | Dalapon | — | Resolved |
| January 1, 2005 – December 31, 2007 | Monitoring, Regular | Dinoseb | — | Resolved |
| January 1, 2005 – December 31, 2007 | Monitoring, Regular | 2,4-D | — | Resolved |
| January 1, 2005 – December 31, 2007 | Monitoring, Regular | Pentachlorophenol | — | Resolved |
| July 1, 2003 – December 31, 2003 | Water Quality Parameter M/R | Lead and Copper Rule | — | Resolved |
| September 1, 2002 – September 30, 2002 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| August 1, 2001 – August 31, 2001 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| February 1, 1996 – February 29, 1996 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| February 1, 1996 – February 29, 1996 | Monitoring, Repeat Major (TCR) | Coliform (TCR) | — | Resolved |
| December 1, 1995 – December 31, 1995 | Monitoring, Repeat Major (TCR) | Coliform (TCR) | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- August 22, 2017State Compliance achieved1 linked violation
- August 18, 2017State Public Notification requested1 linked violation
- August 18, 2017State Violation/Reminder Notice1 linked violation
- May 29, 2012State Compliance achieved1 linked violation
- April 27, 2012State Public Notification received1 linked violation
- April 25, 2012State Violation/Reminder Notice1 linked violation
- April 25, 2012State Public Notification requested1 linked violation
- April 25, 2012State Violation/Reminder Notice1 linked violation
- January 18, 2011State Violation/Reminder Notice1 linked violation
- January 18, 2011State Public Notification requested1 linked violation
- December 2, 2010State Compliance achieved1 linked violation
- September 27, 2010State Compliance achieved1 linked violation
- August 19, 2010State Public Notification requested1 linked violation
- August 19, 2010State Violation/Reminder Notice1 linked violation
- August 19, 2010State Public Notification received1 linked violation
- May 7, 2010State Compliance achieved2 linked violations
- August 24, 2009State Public Notification received1 linked violation
- August 14, 2009State Violation/Reminder Notice1 linked violation
- August 14, 2009State Public Notification requested2 linked violations
- August 14, 2009State Compliance achieved1 linked violation
- August 14, 2009State Public Notification requested1 linked violation
- August 14, 2009State Violation/Reminder Notice1 linked violation
- November 28, 2008State Compliance achieved7 linked violations
- February 27, 2008State Compliance achieved1 linked violation
- February 7, 2008State Compliance achieved7 linked violations
- January 25, 2008State Violation/Reminder Notice6 linked violations
- January 25, 2008State Public Notification requested6 linked violations
- April 2, 2007State Public Notification received1 linked violation
- March 23, 2007State Violation/Reminder Notice1 linked violation
- March 23, 2007State Public Notification requested1 linked violation
- March 23, 2007State Violation/Reminder Notice1 linked violation
- June 23, 2005State Compliance achieved3 linked violations
- February 11, 2005State Compliance achieved1 linked violation
- January 4, 2005State Public Notification requested2 linked violations
- January 4, 2005State Violation/Reminder Notice1 linked violation
- January 3, 2005State Public Notification requested1 linked violation
- January 3, 2005State Violation/Reminder Notice3 linked violations
- January 3, 2005State Public Notification requested3 linked violations
- January 3, 2005State Violation/Reminder Notice1 linked violation
- January 27, 2003State Compliance achieved1 linked violation
- September 28, 2002State Violation/Reminder Notice2 linked violations
- September 28, 2002State Public Notification requested2 linked violations
- September 26, 2002State Violation/Reminder Notice2 linked violations
- September 26, 2002State Public Notification requested1 linked violation
- January 19, 2002State Public Notification requested1 linked violation
- November 2, 2001State Compliance achieved1 linked violation
- August 30, 2001State Public Notification requested1 linked violation
- August 30, 2001State Violation/Reminder Notice1 linked violation
- August 30, 2001State Violation/Reminder Notice1 linked violation
Common questions
Is BONNER HOUSING PWS SYSTEM required to publish a Consumer Confidence Report?
- Yes. BONNER HOUSING PWS 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 BONNER HOUSING PWS SYSTEM’s next Consumer Confidence Report due?
- BONNER HOUSING PWS SYSTEM’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does BONNER HOUSING PWS SYSTEM have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for BONNER HOUSING PWS 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
CRISP, KEN L
406-549-8868
MISSOULA, MT 59806