WASCO, IL · Kane County
WASCO SD Water System
Consumer Confidence Report status
WASCO SD 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 WASCO SD.
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 Illinois’s official records. Always confirm current status with Illinois before making decisions based on this information.
System facts
- System ID (PWSID)
- IL0890110
- System type
- Community Water System
- Population served
- 4,000
- Service connections
- 1,195
- Ownership
- local government
- Water source
- groundwater (wells)
WASCO SD is one of 248 community water systems in Illinois in the 3,301 to 10,000 people size category, serving 4,000 people from groundwater.
As of August 1, 2026, its federal record holds 16 entries between 1995 and 2022, all of which EPA lists as closed. Nothing has been added since 2022.
Of the 16, 5 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 Radionuclides and Revised Rad Rule and the Total Coliform Rules.
Violation history
Monitoring, Regular
—Combined Radium (-226 and -228)
July 1, 2022 – September 30, 2022
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2022 – September 30, 2022
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2005 – May 11, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2005 – March 31, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2004 – September 30, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2004 – June 30, 2004
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
January 1, 2004 – March 31, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2004 – March 31, 2004
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2004 – March 31, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2003 – December 31, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2003 – September 30, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2002 – December 31, 2002
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
August 1, 2001 – September 30, 2002
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
September 26, 2000 – February 20, 2001
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 1999 – September 30, 2002
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
July 1, 1995 – July 31, 1995
Archived
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| July 1, 2022 – September 30, 2022 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| July 1, 2022 – September 30, 2022 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2005 – May 11, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2005 – March 31, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2004 – September 30, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2004 – June 30, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2004 – March 31, 2004 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| January 1, 2004 – March 31, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2004 – March 31, 2004 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2003 – December 31, 2003 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2003 – September 30, 2003 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2002 – December 31, 2002 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| August 1, 2001 – September 30, 2002 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| September 26, 2000 – February 20, 2001 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| October 1, 1999 – September 30, 2002 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 1995 – July 31, 1995 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Archived |
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- October 25, 2022State Compliance achieved2 linked violations
- October 18, 2022State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- October 18, 2022State Violation/Reminder Notice1 linked violation
- October 18, 2022State Violation/Reminder Notice1 linked violation
- January 24, 2022State Compliance achieved1 linked violation
- January 19, 2022State Violation/Reminder Notice1 linked violation
- January 19, 2022State Violation/Reminder Notice1 linked violation
- August 29, 2005State Public Notification received1 linked violation
- August 22, 2005State Public Notification received1 linked violation
- May 26, 2005State Public Notification received2 linked violations
- May 11, 2005State Violation/Reminder Notice1 linked violation
- May 11, 2005State Public Notification requested1 linked violation
- May 11, 2005State Compliance achieved12 linked violations
- April 8, 2005State Public Notification requested1 linked violation
- April 8, 2005State Violation/Reminder Notice1 linked violation
- January 7, 2005State Violation/Reminder Notice1 linked violation
- January 7, 2005State Public Notification requested1 linked violation
- December 16, 2004State Public Notification received1 linked violation
- October 19, 2004State Violation/Reminder Notice1 linked violation
- October 19, 2004State Public Notification requested1 linked violation
- September 9, 2004State Public Notification received1 linked violation
- July 10, 2004State Public Notification requested1 linked violation
- July 10, 2004State Violation/Reminder Notice1 linked violation
- June 3, 2004State Public Notification received1 linked violation
- June 3, 2004State Public Notification received1 linked violation
- June 3, 2004State Public Notification received1 linked violation
- May 21, 2004State Violation/Reminder Notice1 linked violation
- May 21, 2004State Public Notification requested1 linked violation
- May 21, 2004State Public Notification requested1 linked violation
- May 21, 2004State Violation/Reminder Notice1 linked violation
- May 21, 2004State Public Notification requested1 linked violation
- April 10, 2004State Public Notification requested1 linked violation
- April 10, 2004State Violation/Reminder Notice1 linked violation
- April 5, 2004State Compliance achieved3 linked violations
- February 11, 2004State Public Notification received1 linked violation
- February 10, 2004State Bilateral Compliance Agreement signed12 linked violations
- January 27, 2004State Formal Notice of Violation issued12 linked violations
- January 10, 2004State Public Notification requested1 linked violation
- January 10, 2004State Violation/Reminder Notice1 linked violation
- December 1, 2003State Public Notification received1 linked violation
- December 1, 2003State Public Notification received1 linked violation
- December 1, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- July 10, 2003State Violation/Reminder Notice1 linked violation
- July 10, 2003State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- July 10, 2003State Public Notification requested1 linked violation
- July 10, 2003State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- May 5, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- May 5, 2003State Public Notification received2 linked violations
- May 5, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- May 5, 2003State Public Notification received2 linked violations
- April 14, 2003State Compliance achieved1 linked violation
- April 10, 2003State Public Notification requested1 linked violation
- April 10, 2003State Violation/Reminder Notice1 linked violation
- April 10, 2003State Violation/Reminder Notice1 linked violation
- January 10, 2003State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- January 10, 2003State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- January 10, 2003State Public Notification requested1 linked violation
- January 10, 2003State Violation/Reminder Notice1 linked violation
- December 20, 2001State Bilateral Compliance Agreement signed4 linked violations
- September 24, 1995State Public Notification requested1 linked violation
- September 24, 1995State Violation/Reminder Notice1 linked violation
- August 26, 1995State Violation/Reminder Notice1 linked violation
- August 26, 1995State Public Notification requested1 linked violation
- August 21, 1995State Public Notification received2 linked violations
Common questions
Is WASCO SD required to publish a Consumer Confidence Report?
- Yes. WASCO SD 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 WASCO SD’s next Consumer Confidence Report due?
- WASCO SD’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does WASCO SD have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for WASCO SD.
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
MILOSAVLJEVIC, DANIELLE
630-443-0111
WASCO, IL 60183