YORKVILLE, IL · Kendall County
MORGAN CREEK Water System
Consumer Confidence Report status
MORGAN CREEK 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 1 item for MORGAN CREEK that is 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)
- IL0935140
- System type
- Community Water System
- Population served
- 66
- Service connections
- 25
- Ownership
- privately owned
- Water source
- groundwater (wells)
MORGAN CREEK is one of 1,572 community water systems in Illinois in the 500 or fewer people size category, serving 66 people from groundwater.
As of August 1, 2026, its federal record holds 25 entries between 1977 and 2025, of which 1 remains open; none are health-based.
Of the 25, 6 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 Total Coliform Rules, and the Lead and Copper Rule.
Violation history
Notification, Known or Potential LSL
—LEAD AND COPPER RULE REVISIONS
July 2, 2025
UnaddressedMonitoring, Regular
—Combined Radium (-226 and -228)
January 1, 2022 – December 31, 2022
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2007 – March 31, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2006 – December 31, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2006 – September 30, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2006 – June 30, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2006 – February 24, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2005 – September 30, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2005 – June 30, 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)
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, Monthly (TCR)
Health-basedColiform (TCR)
June 1, 1999 – June 30, 1999
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 1998 – June 30, 1999
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
May 20, 1996 – July 28, 1997
ResolvedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 1995 – January 27, 1997
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
December 1, 1993 – March 25, 1994
ResolvedMonitoring, Routine Minor (TCR)
—Coliform (TCR)
August 1, 1992 – August 31, 1992
ArchivedMonitoring, Repeat Minor (TCR)
—Coliform (TCR)
July 1, 1992 – July 31, 1992
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
December 9, 1985 – December 8, 1989
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
June 30, 1977 – June 29, 1981
Resolved
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 |
|---|---|---|---|---|
| July 2, 2025 | Notification, Known or Potential LSL | LEAD AND COPPER RULE REVISIONS | — | Unaddressed |
| January 1, 2022 – December 31, 2022 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| January 1, 2007 – March 31, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2006 – December 31, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2006 – September 30, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2006 – June 30, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2006 – February 24, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2005 – September 30, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2005 – June 30, 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 |
| 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 |
| June 1, 1999 – June 30, 1999 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
| April 1, 1998 – June 30, 1999 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| May 20, 1996 – July 28, 1997 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 1995 – January 27, 1997 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| December 1, 1993 – March 25, 1994 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| August 1, 1992 – August 31, 1992 | Monitoring, Routine Minor (TCR) | Coliform (TCR) | — | Archived |
| July 1, 1992 – July 31, 1992 | Monitoring, Repeat Minor (TCR) | Coliform (TCR) | — | Archived |
| December 9, 1985 – December 8, 1989 | 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 | — | Resolved |
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
- July 3, 2025State Violation/Reminder Notice1 linked violation
- July 3, 2025State Public Notification requested1 linked violation
- April 17, 2023State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- February 10, 2023State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- February 10, 2023State Violation/Reminder Notice1 linked violation
- July 2, 2007State Public Notification received1 linked violation
- June 19, 2007State Compliance achieved4 linked violations
- April 24, 2007State Public Notification requested1 linked violation
- April 4, 2007State Public Notification received1 linked violation
- October 12, 2006State Violation/Reminder Notice1 linked violation
- September 15, 2006State Public Notification received1 linked violation
- July 10, 2006State Violation/Reminder Notice2 linked violations
- June 23, 2006State Public Notification received1 linked violation
- May 16, 2006State Public Notification requested1 linked violation
- May 16, 2006State Violation/Reminder Notice1 linked violation
- April 3, 2006State Public Notification received1 linked violation
- February 24, 2006State Compliance achieved14 linked violations
- January 10, 2006State Violation/Reminder Notice1 linked violation
- January 10, 2006State Public Notification requested1 linked violation
- December 30, 2005State Public Notification received1 linked violation
- October 7, 2005State Violation/Reminder Notice1 linked violation
- October 7, 2005State Public Notification requested1 linked violation
- September 30, 2005State Public Notification received1 linked violation
- July 8, 2005State Violation/Reminder Notice1 linked violation
- June 27, 2005State Public Notification received2 linked violations
- April 8, 2005State Public Notification requested1 linked violation
- January 5, 2005State Public Notification received1 linked violation
- October 19, 2004State Public Notification requested1 linked violation
- July 10, 2004State Violation/Reminder Notice1 linked violation
- July 10, 2004State Public Notification requested1 linked violation
- July 2, 2004State Public Notification received1 linked violation
- June 1, 2004State Bilateral Compliance Agreement signed16 linked violations
- April 10, 2004State Public Notification requested1 linked violation
- January 10, 2004State Public Notification requested1 linked violation
- May 12, 2003State Public Notification received1 linked violation
- April 10, 2003State Violation/Reminder Notice1 linked violation
- March 25, 2003State Public Notification requested1 linked violation
- February 9, 2001State Compliance achieved3 linked violations
- June 30, 1999State Compliance achieved1 linked violation
- July 28, 1997State Compliance achieved1 linked violation
- January 27, 1997State Compliance achieved1 linked violation
- March 25, 1994State Compliance achieved2 linked violations
- March 25, 1994State Compliance achieved2 linked violations
- April 28, 1993State Public Notification received1 linked violation
- December 14, 1992State Public Notification received1 linked violation
- October 11, 1992State Public Notification requested1 linked violation
- October 11, 1992State Violation/Reminder Notice1 linked violation
- October 1, 1992State Public Notification received1 linked violation
- September 12, 1992State Public Notification requested2 linked violations
- September 12, 1992State Violation/Reminder Notice2 linked violations
- September 9, 1992State Public Notification received1 linked violation
- September 7, 1992State Public Notification received2 linked violations
- August 24, 1992State Public Notification requested1 linked violation
- April 1, 1992State Public Notification received1 linked violation
- October 15, 1991State Public Notification received1 linked violation
- July 1, 1991State Public Notification received1 linked violation
- April 1, 1991State Public Notification received1 linked violation
- January 1, 1991State Public Notification received1 linked violation
- September 30, 1990State Public Notification received1 linked violation
- August 17, 1990State Public Notification requested1 linked violation
- July 31, 1990State Public Notification received1 linked violation
- January 27, 1990State Public Notification received1 linked violation
- November 27, 1989State Public Notification received1 linked violation
- September 20, 1989State Public Notification received1 linked violation
- September 12, 1989State Public Notification requested1 linked violation
- May 30, 1989State Public Notification received1 linked violation
Common questions
Is MORGAN CREEK required to publish a Consumer Confidence Report?
- Yes. MORGAN CREEK 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 MORGAN CREEK’s next Consumer Confidence Report due?
- MORGAN CREEK’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does MORGAN CREEK have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show 1 item for MORGAN CREEK that is 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
EGIZIO, MICHAEL
630-553-3554
YORKVILLE, IL 60560-8312