SOUTH WILMINGTON, IL · Grundy County
SOUTH WILMINGTON Water System
Consumer Confidence Report status
SOUTH WILMINGTON 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 2 items for SOUTH WILMINGTON that are open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.
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)
- IL0630650
- System type
- Community Water System
- Population served
- 700
- Service connections
- 340
- Ownership
- local government
- Water source
- groundwater (wells)
SOUTH WILMINGTON is one of 773 community water systems in Illinois in the 501 to 3,300 people size category, serving 700 people from groundwater.
As of August 1, 2026, its federal record holds 25 entries between 1977 and 2026, of which 2 remain open; none are health-based.
Of the 25, 9 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, the Public Notice Rule and Revised PN Rule, and the Lead and Copper Rule.
Violation history
Public Notification Violation for NPDWR Violation
—Public Notice
January 14, 2026
UnaddressedNotification, Known or Potential LSL
—LEAD AND COPPER RULE REVISIONS
July 2, 2025
UnaddressedMonitoring, Regular
—Combined Uranium
October 1, 2024 – December 31, 2024
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
July 1, 2024 – September 30, 2024
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
April 1, 2022 – June 30, 2022
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
January 1, 2020 – March 31, 2020
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
April 1, 2019 – June 30, 2019
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
January 1, 2016 – December 31, 2016
ResolvedMonitoring and Reporting (DBP)
—TTHM
September 1, 2015 – August 31, 2016
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2004 – June 30, 2004
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
January 9, 2004 – January 15, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
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)
January 1, 2003 – March 31, 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
January 1, 2002 – September 30, 2002
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
June 1, 2001 – June 30, 2001
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2000 – September 30, 2002
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
December 8, 1997 – December 7, 2001
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
November 1, 1996 – September 30, 2000
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 1996 – September 30, 2000
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 22, 1992 – October 21, 1996
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
June 30, 1977 – June 29, 1981
Archived
Unaddressed no corrective action on record yetResolved 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 |
|---|---|---|---|---|
| January 14, 2026 | Public Notification Violation for NPDWR Violation | Public Notice | — | Unaddressed |
| July 2, 2025 | Notification, Known or Potential LSL | LEAD AND COPPER RULE REVISIONS | — | Unaddressed |
| October 1, 2024 – December 31, 2024 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2024 – September 30, 2024 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| April 1, 2022 – June 30, 2022 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| January 1, 2020 – March 31, 2020 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| April 1, 2019 – June 30, 2019 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| January 1, 2016 – December 31, 2016 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| September 1, 2015 – August 31, 2016 | Monitoring and Reporting (DBP) | TTHM | — | Resolved |
| April 1, 2004 – June 30, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 9, 2004 – January 15, 2004 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| January 1, 2004 – March 31, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | 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 |
| January 1, 2003 – March 31, 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 |
| January 1, 2002 – September 30, 2002 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| June 1, 2001 – June 30, 2001 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
| October 1, 2000 – September 30, 2002 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| December 8, 1997 – December 7, 2001 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| November 1, 1996 – September 30, 2000 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 1996 – September 30, 2000 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 22, 1992 – October 21, 1996 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| June 30, 1977 – June 29, 1981 | Monitoring, Regular | Gross Alpha, Excl. Radon and U | — | Archived |
Unaddressed no corrective action on record yetResolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- February 13, 2026State Violation/Reminder Notice1 linked violation
- January 27, 2026State Public Notification requested1 linked violation
- January 27, 2026State Violation/Reminder Notice1 linked violation
- July 29, 2025State Public Notification requested1 linked violation
- July 29, 2025State Violation/Reminder Notice1 linked violation
- July 3, 2025State Violation/Reminder Notice1 linked violation
- July 3, 2025State Public Notification requested1 linked violation
- June 2, 2025State Public Notification received1 linked violation
- June 2, 2025State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- June 2, 2025State Public Notification received1 linked violation
- April 10, 2025State Compliance achieved1 linked violation
- April 10, 2025State Compliance achieved1 linked violation
- January 13, 2025State Public Notification requested1 linked violation
- January 13, 2025State Violation/Reminder Notice1 linked violation
- January 9, 2025State Compliance achieved1 linked violation
- October 11, 2024State Violation/Reminder Notice1 linked violation
- October 11, 2024State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- October 11, 2024State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- October 11, 2024State Public Notification requested1 linked violation
- October 11, 2024State Violation/Reminder Notice1 linked violation
- October 11, 2024State Public Notification requested1 linked violation
- June 26, 2023State Public Notification received1 linked violation
- December 15, 2022State Compliance achieved1 linked violation
- October 24, 2022State Compliance achieved1 linked violation
- October 18, 2022State Public Notification requested1 linked violation
- 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
- August 4, 2022State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 29, 2022State Compliance achieved2 linked violations
- July 13, 2022State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- July 13, 2022State Violation/Reminder Notice1 linked violation
- July 13, 2022State Violation/Reminder Notice1 linked violation
- June 30, 2021State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- March 22, 2021State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- January 14, 2021State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- January 14, 2021State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- April 23, 2020State Compliance achieved1 linked violation
- April 17, 2020State Violation/Reminder Notice1 linked violation
- July 17, 2019State Compliance achieved1 linked violation
- July 12, 2019State Violation/Reminder Notice1 linked violation
- September 7, 2017State Compliance achieved2 linked violations
- June 22, 2017State Public Notification received2 linked violations
- February 2, 2017State Compliance achieved1 linked violation
- January 12, 2017State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- January 12, 2017State Violation/Reminder Notice1 linked violation
- October 17, 2016State Public Notification requested2 linked violations
- October 17, 2016State Violation/Reminder Notice2 linked violations
- June 23, 2015State Compliance achieved1 linked violation
- September 24, 2014State Violation/Reminder Notice1 linked violation
- May 30, 2013State Public Notification received1 linked violation
- May 21, 2013State Compliance achieved1 linked violation
- May 17, 2013State Violation/Reminder Notice1 linked violation
- May 17, 2013State Public Notification requested1 linked violation
- April 13, 2005State Public Notification received1 linked violation
- March 4, 2005State Violation/Reminder Notice1 linked violation
- March 4, 2005State Public Notification requested1 linked violation
- February 7, 2005State Public Notification received1 linked violation
- January 11, 2005State Compliance achieved14 linked violations
- January 7, 2005State Violation/Reminder Notice1 linked violation
- January 7, 2005State Public Notification requested1 linked violation
- November 29, 2004State Public Notification received1 linked violation
- October 19, 2004State Violation/Reminder Notice1 linked violation
- October 19, 2004State Public Notification requested1 linked violation
- October 8, 2004State Compliance achieved2 linked violations
- September 27, 2004State Public Notification received1 linked violation
- August 21, 2004State Public Notification received1 linked violation
- July 10, 2004State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- July 10, 2004State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- July 10, 2004State Public Notification requested1 linked violation
- July 10, 2004State Violation/Reminder Notice1 linked violation
- April 10, 2004State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- April 10, 2004State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- April 10, 2004State Public Notification requested1 linked violation
- April 10, 2004State Violation/Reminder Notice1 linked violation
- March 19, 2004State Bilateral Compliance Agreement signed16 linked violations
- March 18, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- March 18, 2004State Public Notification received1 linked violation
- March 17, 2004State Violation/Reminder Notice1 linked violation
- January 26, 2004State Formal Notice of Violation issued16 linked violations
- January 20, 2004State Public Notification received1 linked violation
- January 20, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- January 15, 2004State Compliance achieved1 linked violation
- January 10, 2004State Violation/Reminder Notice1 linked violation
- January 10, 2004State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- January 10, 2004State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- January 10, 2004State Public Notification requested1 linked violation
- September 19, 2003State Public Notification received1 linked violation
- September 19, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- 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
- April 10, 2003State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- April 10, 2003State Public Notification requested1 linked violation
- April 10, 2003State Violation/Reminder Notice1 linked violation
- April 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
- January 10, 2003State Violation/Reminder Notice1 linked violation
- January 10, 2003State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- October 12, 2001State Bilateral Compliance Agreement signed9 linked violations
- August 15, 2001State Violation/Reminder Notice2 linked violations
- January 15, 1998State Public Notification received3 linked violations
- December 24, 1997State Public Notification received2 linked violations
- April 2, 1997State Compliance achieved1 linked violation
- January 7, 1997State Public Notification received1 linked violation
- December 28, 1995State Public Notification received2 linked violations
- October 1, 1995State Public Notification received1 linked violation
- June 21, 1995State Public Notification received2 linked violations
- June 21, 1994State Public Notification received1 linked violation
- June 15, 1993State Public Notification received1 linked violation
- November 16, 1992State Public Notification received1 linked violation
- October 22, 1992State Public Notification received1 linked violation
- September 8, 1990State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- September 8, 1990State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- July 23, 1990State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- June 23, 1986State Compliance achieved1 linked violation
Common questions
Is SOUTH WILMINGTON required to publish a Consumer Confidence Report?
- Yes. SOUTH WILMINGTON 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 SOUTH WILMINGTON’s next Consumer Confidence Report due?
- SOUTH WILMINGTON’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does SOUTH WILMINGTON have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show 2 items for SOUTH WILMINGTON that are open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.
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
LARDI JR., NORMAN
815-714-0138
SOUTH WILMINGTON, IL 60474