WASCO, IL · Kane County
WASCO SD Water System
Current status
No open violations on record as of July 4, 2026.
This system's next federally required Consumer Confidence Report is due July 1, 2027, under the EPA's revised reporting rule.
Data sourced from the EPA ECHO database (SDWA bulk download), last refreshed July 4, 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)
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
—Gross Alpha, Excl. Radon and U
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 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)
April 1, 2003 – June 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
Resolved
Resolved addressed and confirmed by the state
| 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 | Gross Alpha, Excl. Radon and U | — | 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 Radium (-226 and -228) | — | 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 |
| April 1, 2003 – June 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 |
Resolved addressed and confirmed by the state
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 Violation/Reminder Notice3 linked violations
- 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
- March 31, 2004State Public Notification received2 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 Violation/Reminder Notice1 linked violation
- January 10, 2004State Public Notification requested1 linked violation
- December 1, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- December 1, 2003State Public Notification received1 linked violation
- December 1, 2003State Public Notification received1 linked violation
- July 10, 2003State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- July 10, 2003State Public Notification requested1 linked violation
- July 10, 2003State Violation/Reminder Notice1 linked violation
- July 10, 2003State Violation/Reminder Noticegeneral 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
- May 5, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- April 14, 2003State Compliance achieved1 linked violation
- April 10, 2003State Violation/Reminder Notice1 linked violation
- April 10, 2003State Public Notification requested1 linked violation
- April 10, 2003State Violation/Reminder Notice1 linked violation
- January 10, 2003State Violation/Reminder Notice1 linked violation
- January 10, 2003State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- January 10, 2003State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- January 10, 2003State Public Notification requested1 linked violation
- December 20, 2001State Bilateral Compliance Agreement signed4 linked violations
- September 24, 1995State Violation/Reminder Notice1 linked violation
- September 24, 1995State Public Notification requested1 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
Contact
MILOSAVLJEVIC, DANIELLE
630-443-0111
WASCO, IL 60183