GLENWOOD, IA · Mills County
GLENWOOD MUNICIPAL UTILITIES Water System
Consumer Confidence Report status
GLENWOOD MUNICIPAL UTILITIES 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 GLENWOOD MUNICIPAL UTILITIES.
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 Iowa’s official records. Always confirm current status with Iowa before making decisions based on this information.
System facts
- System ID (PWSID)
- IA6525090
- System type
- Community Water System
- Population served
- 5,449
- Service connections
- 2,543
- Ownership
- local government
- Water source
- groundwater (wells)
GLENWOOD MUNICIPAL UTILITIES is one of 91 community water systems in Iowa in the 3,301 to 10,000 people size category, serving 5,449 people from groundwater.
As of August 1, 2026, its federal record holds 19 entries between 1991 and 2018, all of which EPA lists as closed. Nothing has been added since 2018.
Of the 19, 8 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 Stage 1 Disinfectants and Disinfection Byproducts Rule, volatile organic chemicals, and the Total Coliform Rules.
Violation history
Monitoring, Routine (RTCR)
—Revised Total Coliform Rule
April 1, 2018 – April 30, 2018
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
October 1, 2012 – December 31, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
July 1, 2012 – September 30, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
April 1, 2012 – June 30, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
October 1, 2011 – December 31, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
July 1, 2011 – September 30, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
January 1, 2011 – March 31, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
October 1, 2010 – December 31, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
July 1, 2010 – September 30, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedTTHM
April 1, 2010 – June 30, 2010
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
July 1, 1991 – July 31, 1991
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
June 1, 1991 – June 17, 1991
ResolvedMonitoring, Regular
—Toluene
January 1, 1991 – January 31, 1991
ResolvedMonitoring, Regular
—1,1,2-Trichloroethane
January 1, 1991 – January 31, 1991
ResolvedMonitoring, Regular
—Styrene
January 1, 1991 – January 31, 1991
ResolvedMonitoring, Regular
—o-Dichlorobenzene
January 1, 1991 – January 31, 1991
ResolvedMonitoring, Regular
—Ethylbenzene
January 1, 1991 – January 31, 1991
ResolvedMonitoring, Regular
—cis-1,2-Dichloroethylene
January 1, 1991 – January 31, 1991
ResolvedMonitoring, Regular
—CHLOROBENZENE
January 1, 1991 – January 31, 1991
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| April 1, 2018 – April 30, 2018 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| October 1, 2012 – December 31, 2012 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| July 1, 2012 – September 30, 2012 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| April 1, 2012 – June 30, 2012 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| October 1, 2011 – December 31, 2011 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| July 1, 2011 – September 30, 2011 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| January 1, 2011 – March 31, 2011 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| October 1, 2010 – December 31, 2010 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| July 1, 2010 – September 30, 2010 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| April 1, 2010 – June 30, 2010 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| July 1, 1991 – July 31, 1991 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| June 1, 1991 – June 17, 1991 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| January 1, 1991 – January 31, 1991 | Monitoring, Regular | Toluene | — | Resolved |
| January 1, 1991 – January 31, 1991 | Monitoring, Regular | 1,1,2-Trichloroethane | — | Resolved |
| January 1, 1991 – January 31, 1991 | Monitoring, Regular | Styrene | — | Resolved |
| January 1, 1991 – January 31, 1991 | Monitoring, Regular | o-Dichlorobenzene | — | Resolved |
| January 1, 1991 – January 31, 1991 | Monitoring, Regular | Ethylbenzene | — | Resolved |
| January 1, 1991 – January 31, 1991 | Monitoring, Regular | cis-1,2-Dichloroethylene | — | Resolved |
| January 1, 1991 – January 31, 1991 | Monitoring, Regular | CHLOROBENZENE | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- July 13, 2018State Public Notification received1 linked violation
- May 18, 2018State Formal Notice of Violation issued1 linked violation
- May 18, 2018State Public Notification requested1 linked violation
- May 14, 2018State Compliance achieved1 linked violation
- January 7, 2013State Compliance achieved1 linked violation
- January 7, 2013State Compliance achieved1 linked violation
- January 7, 2013State Compliance achieved1 linked violation
- January 7, 2013State Compliance achieved1 linked violation
- January 7, 2013State Compliance achieved1 linked violation
- January 7, 2013State Compliance achieved1 linked violation
- January 7, 2013State Compliance achieved1 linked violation
- January 7, 2013State Compliance achieved1 linked violation
- January 7, 2013State Compliance achieved1 linked violation
- January 7, 2013State Compliance achieved1 linked violation
- January 7, 2013State Compliance achieved1 linked violation
- December 13, 2012State Public Notification received3 linked violations
- October 12, 2012State Public Notification requested1 linked violation
- October 12, 2012State Formal Notice of Violation issued1 linked violation
- August 20, 2012State Public Notification received1 linked violation
- July 18, 2012State Formal Notice of Violation issued1 linked violation
- June 4, 2012State Public Notification received3 linked violations
- April 24, 2012State Public Notification requested3 linked violations
- April 5, 2012State Public Notification received4 linked violations
- March 19, 2012State Formal Notice of Violation issued2 linked violations
- December 9, 2011State Public Notification requested2 linked violations
- December 9, 2011State Formal Notice of Violation issued2 linked violations
- May 12, 2011State Bilateral Compliance Agreement signed1 linked violation
- May 12, 2011State Bilateral Compliance Agreement signed1 linked violation
- May 12, 2011State Bilateral Compliance Agreement signed1 linked violation
- January 11, 2011State Public Notification received3 linked violations
- October 1, 1995State Compliance achieved1 linked violation
- June 15, 1993State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- June 15, 1993State Public Notification received2 linked violations
- June 15, 1993State Public Notification received3 linked violations
- June 15, 1993State Public Notification received1 linked violation
- June 15, 1993State Public Notification received1 linked violation
- June 15, 1993State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- June 15, 1993State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- June 15, 1993State Public Notification received1 linked violation
- June 15, 1993State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- May 17, 1993State Compliance achieved2 linked violations
- May 17, 1993State Compliance achieved1 linked violation
- May 17, 1993State Compliance achieved4 linked violations
- May 17, 1993State Compliance achieved2 linked violations
- May 17, 1993State Compliance achieved1 linked violation
- May 17, 1993State Compliance achieved2 linked violations
- May 17, 1993State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- May 17, 1993State Compliance achieved1 linked violation
- May 17, 1993State Compliance achieved2 linked violations
- May 17, 1993State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- May 17, 1993State Compliance achieved1 linked violation
- May 17, 1993State Compliance achieved1 linked violation
- April 13, 1993State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- April 13, 1993State Public Notification requested2 linked violations
- April 13, 1993State Public Notification requested3 linked violations
- April 13, 1993State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- April 13, 1993State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- April 13, 1993State Public Notification requested1 linked violation
- April 13, 1993State Public Notification requested2 linked violations
- April 13, 1993State Public Notification requested2 linked violations
- April 13, 1993State Formal Notice of Violation issued1 linked violation
- April 13, 1993State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- April 13, 1993State Public Notification requested2 linked violations
- April 13, 1993State Formal Notice of Violation issued3 linked violations
- April 13, 1993State Public Notification requested1 linked violation
- April 13, 1993State Public Notification requested1 linked violation
- April 13, 1993State Formal Notice of Violation issued2 linked violations
- April 13, 1993State Formal Notice of Violation issued1 linked violation
- April 13, 1993State Public Notification requested1 linked violation
- April 13, 1993State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- April 13, 1993State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- April 13, 1993State Formal Notice of Violation issued2 linked violations
- April 13, 1993State Formal Notice of Violation issued1 linked violation
- April 13, 1993State Public Notification requested2 linked violations
- April 13, 1993State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- April 13, 1993State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- April 13, 1993State Formal Notice of Violation issued2 linked violations
- April 13, 1993State Formal Notice of Violation issued2 linked violations
- April 13, 1993State Formal Notice of Violation issued4 linked violations
- April 13, 1993State Public Notification requested1 linked violation
- April 13, 1993State Formal Notice of Violation issued3 linked violations
- April 13, 1993State Public Notification requested3 linked violations
- April 13, 1993State Public Notification requested2 linked violations
- April 13, 1993State Formal Notice of Violation issued1 linked violation
- August 19, 1991State Public Notification received1 linked violation
- July 15, 1991State Public Notification requested2 linked violations
- July 15, 1991State Formal Notice of Violation issued6 linked violations
- July 15, 1991State Formal Notice of Violation issued2 linked violations
- July 15, 1991State Public Notification requested1 linked violation
- July 5, 1991State Public Notification received1 linked violation
- June 18, 1991State Public Notification requested3 linked violations
- June 18, 1991State Formal Notice of Violation issued1 linked violation
- June 18, 1991State Public Notification requested1 linked violation
- June 17, 1991State Compliance achieved1 linked violation
Common questions
Is GLENWOOD MUNICIPAL UTILITIES required to publish a Consumer Confidence Report?
- Yes. GLENWOOD MUNICIPAL UTILITIES 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 GLENWOOD MUNICIPAL UTILITIES’s next Consumer Confidence Report due?
- GLENWOOD MUNICIPAL UTILITIES’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does GLENWOOD MUNICIPAL UTILITIES have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for GLENWOOD MUNICIPAL UTILITIES.
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
GLENWOOD MUNI UTILITIES
712-527-4868
GLENWOOD, IA 51534