BOZEMAN, MT · Gallatin County
SPIRIT HILLS SUBDIVISION Water System
Consumer Confidence Report status
SPIRIT HILLS SUBDIVISION 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 SPIRIT HILLS SUBDIVISION.
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)
- MT0004208
- System type
- Community Water System
- Population served
- 230
- Service connections
- 90
- Ownership
- privately owned
- Water source
- groundwater (wells)
SPIRIT HILLS SUBDIVISION is one of 1,084 community water systems in Montana in the 500 or fewer people size category, serving 230 people from groundwater.
As of August 1, 2026, EPA's published records contain no violations for this system.
Violation history
No violations on record for this system.
Enforcement actions
- July 24, 2020State Compliance achieved1 linked violation
- July 20, 2020State Violation/Reminder Notice1 linked violation
- March 31, 2014State no additional Formal Action needed5 linked violations
- December 3, 2012State Compliance achieved2 linked violations
- November 14, 2012State Violation/Reminder Notice1 linked violation
- November 7, 2012State Compliance achieved1 linked violation
- October 22, 2012State Public Notification received1 linked violation
- October 22, 2012State Violation/Reminder Notice1 linked violation
- October 22, 2012State Violation/Reminder Notice1 linked violation
- October 22, 2012State Public Notification requested1 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
- October 18, 2012State Violation/Reminder Notice1 linked violation
- October 16, 2012State Public Notification requested1 linked violation
- October 16, 2012State Violation/Reminder Notice1 linked violation
- September 17, 2012State Compliance achieved1 linked violation
- September 17, 2012State Compliance achieved1 linked violation
- September 17, 2012State Compliance achieved2 linked violations
- July 12, 2012State Violation/Reminder Notice1 linked violation
- July 12, 2012State Public Notification requested1 linked violation
- December 20, 2011State Compliance achieved2 linked violations
- December 14, 2011State Violation/Reminder Notice1 linked violation
- December 14, 2011State Public Notification requested1 linked violation
- November 2, 2011State Compliance achieved1 linked violation
- October 19, 2011State Violation/Reminder Notice1 linked violation
- October 19, 2011State Public Notification requested1 linked violation
- October 19, 2011State Violation/Reminder Notice1 linked violation
- April 19, 2011State Violation/Reminder Notice1 linked violation
- April 19, 2011State Public Notification requested1 linked violation
- April 19, 2011State Violation/Reminder Notice1 linked violation
- April 19, 2011State Public Notification requested1 linked violation
- December 8, 2009State Compliance achieved1 linked violation
- September 16, 2009State Violation/Reminder Notice1 linked violation
- September 16, 2009State Public Notification requested1 linked violation
- March 16, 2009State Compliance achieved8 linked violations
- March 10, 2009State Public Notification received3 linked violations
- August 19, 2008State Other9 linked violations
- August 15, 2008State Public Notification requested1 linked violation
- August 15, 2008State Violation/Reminder Notice1 linked violation
- August 14, 2008State Violation/Reminder Notice1 linked violation
- August 14, 2008State Public Notification requested1 linked violation
- June 13, 2008State Violation/Reminder Notice2 linked violations
- June 13, 2008State Public Notification requested1 linked violation
- June 13, 2008State Violation/Reminder Notice1 linked violation
- May 16, 2008State Violation/Reminder Notice1 linked violation
- May 16, 2008State Public Notification requested1 linked violation
- May 16, 2008State Violation/Reminder Notice1 linked violation
- May 21, 2007State Compliance achieved1 linked violation
- January 29, 2007State Violation/Reminder Notice1 linked violation
- January 29, 2007State Public Notification requested1 linked violation
- September 5, 2006State Public Notification received2 linked violations
- May 12, 2006State Compliance achieved7 linked violations
- February 21, 2006State Compliance achieved1 linked violation
- December 2, 2005State Public Notification requested4 linked violations
- December 2, 2005State Violation/Reminder Notice7 linked violations
- August 19, 2005State Violation/Reminder Notice2 linked violations
- August 19, 2005State Public Notification requested12 linked violations
- August 15, 2005State Violation/Reminder Notice27 linked violations
- January 4, 2005State Public Notification requested2 linked violations
- July 1, 2004State Other4 linked violations
- August 7, 2003State Compliance achieved1 linked violation
- March 11, 2003State Compliance achieved1 linked violation
- March 11, 2003State Public Notification received1 linked violation
- February 19, 2003State Public Notification requested1 linked violation
- February 19, 2003State Violation/Reminder Notice1 linked violation
- November 26, 2002State Violation/Reminder Notice1 linked violation
- November 26, 2002State Public Notification requested1 linked violation
- November 26, 2002State Violation/Reminder Notice1 linked violation
- August 27, 2002State Compliance achieved1 linked violation
- August 26, 2002State Public Notification received1 linked violation
- April 20, 2002State Public Notification requested1 linked violation
- April 20, 2002State Violation/Reminder Notice1 linked violation
- April 20, 2002State Violation/Reminder Notice1 linked violation
Common questions
Is SPIRIT HILLS SUBDIVISION required to publish a Consumer Confidence Report?
- Yes. SPIRIT HILLS SUBDIVISION 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 SPIRIT HILLS SUBDIVISION’s next Consumer Confidence Report due?
- SPIRIT HILLS SUBDIVISION’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does SPIRIT HILLS SUBDIVISION have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for SPIRIT HILLS SUBDIVISION.
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
WALKER, KEN
406-586-6898
BOZEMAN, MT 59715