LADD, IL · Bureau County
LADD Water System
Consumer Confidence Report status
LADD 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 LADD.
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)
- IL0110450
- System type
- Community Water System
- Population served
- 1,263
- Service connections
- 633
- Ownership
- local government
- Water source
- groundwater (wells)
LADD is one of 773 community water systems in Illinois in the 501 to 3,300 people size category, serving 1,263 people from groundwater.
As of August 1, 2026, its federal record holds 14 entries between 1977 and 2009, all of which EPA lists as closed. Nothing has been added since 2009.
Of the 14, 1 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 Stage 1 Disinfectants and Disinfection Byproducts Rule.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedTTHM
July 1, 2009 – September 30, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2004 – June 30, 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-basedCombined Radium (-226 and -228)
October 1, 2001 – September 30, 2002
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
August 6, 2001 – August 15, 2002
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 1997 – September 30, 2001
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 1993 – September 30, 1997
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
November 1, 1989 – September 30, 1993
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 1989 – September 30, 1993
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 4, 1985 – October 3, 1989
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
June 30, 1977 – June 29, 1981
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, 2009 – September 30, 2009 | Maximum Contaminant Level Violation, Average | TTHM | Health-based | Resolved |
| April 1, 2004 – June 30, 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 |
| October 1, 2002 – December 31, 2002 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2001 – September 30, 2002 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| August 6, 2001 – August 15, 2002 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| October 1, 1997 – September 30, 2001 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 1993 – September 30, 1997 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| November 1, 1989 – September 30, 1993 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 1989 – September 30, 1993 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 4, 1985 – October 3, 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 | — | Archived |
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- June 11, 2018State Public Notification received1 linked violation
- June 11, 2018State Public Notification received1 linked violation
- March 12, 2018State Violation/Reminder Notice1 linked violation
- March 12, 2018State Violation/Reminder Notice1 linked violation
- March 12, 2018State Public Notification requested1 linked violation
- March 12, 2018State Public Notification requested1 linked violation
- March 5, 2018State Compliance achieved2 linked violations
- August 7, 2012State Public Notification received1 linked violation
- July 13, 2012State Public Notification requested1 linked violation
- July 13, 2012State Violation/Reminder Notice1 linked violation
- July 12, 2012State Compliance achieved1 linked violation
- February 4, 2010State Public Notification received1 linked violation
- January 29, 2010State Compliance achieved2 linked violations
- January 13, 2010State Bilateral Compliance Agreement signed2 linked violations
- December 28, 2009State Public Notification requested1 linked violation
- December 28, 2009State Violation/Reminder Notice1 linked violation
- November 9, 2009State Public Notification received1 linked violation
- November 5, 2009State Formal Notice of Violation issued2 linked violations
- October 26, 2009State Violation/Reminder Notice1 linked violation
- October 26, 2009State Public Notification requested1 linked violation
- October 8, 2004State Compliance achieved13 linked violations
- July 10, 2004State Public Notification requested3 linked violations
- July 10, 2004State Violation/Reminder Notice1 linked violation
- April 10, 2004State Public Notification requested1 linked violation
- April 10, 2004State Violation/Reminder Notice1 linked violation
- February 26, 2004State Public Notification received1 linked violation
- January 27, 2004State Formal Notice of Violation issued15 linked violations
- November 6, 2003State Public Notification received2 linked violations
- September 9, 2003State Public Notification received1 linked violation
- July 10, 2003State Public Notification requested1 linked violation
- July 10, 2003State Violation/Reminder Notice1 linked violation
- May 8, 2003State Public Notification received1 linked violation
- April 10, 2003State Public Notification requested1 linked violation
- April 10, 2003State Violation/Reminder Notice1 linked violation
- March 13, 2003State Public Notification received2 linked violations
- January 10, 2003State Public Notification requested1 linked violation
- January 10, 2003State Violation/Reminder Notice1 linked violation
- August 15, 2002State Compliance achieved1 linked violation
- December 10, 2001State Bilateral Compliance Agreement signed4 linked violations
- January 27, 1998State Public Notification received1 linked violation
- May 7, 1997State Public Notification received1 linked violation
- January 8, 1997State Public Notification received1 linked violation
- May 8, 1996State Public Notification received1 linked violation
- January 9, 1996State Public Notification received1 linked violation
- November 8, 1995State Public Notification received1 linked violation
- July 7, 1995State Public Notification received1 linked violation
- April 17, 1995State Public Notification received1 linked violation
- March 3, 1995State Public Notification received1 linked violation
- November 4, 1994State Public Notification received1 linked violation
- March 4, 1994State Public Notification received1 linked violation
- January 10, 1994State Public Notification received1 linked violation
- November 8, 1993State Public Notification received1 linked violation
- November 8, 1993State Public Notification received1 linked violation
- June 1, 1993State Public Notification received2 linked violations
- December 14, 1992State Public Notification received2 linked violations
- October 1, 1992State Public Notification received2 linked violations
- August 24, 1992State Public Notification received2 linked violations
- June 26, 1992State Public Notification received2 linked violations
- April 17, 1992State Public Notification received2 linked violations
- February 18, 1992State Public Notification received2 linked violations
- December 18, 1991State Public Notification received2 linked violations
- August 19, 1991State Public Notification received2 linked violations
- June 14, 1991State Public Notification received2 linked violations
- April 15, 1991State Public Notification received2 linked violations
- February 22, 1991State Public Notification received3 linked violations
- December 18, 1990State Public Notification requested4 linked violations
- August 15, 1990State Public Notification received8 linked violations
- June 15, 1990State Public Notification received2 linked violations
- June 14, 1990State Public Notification requested2 linked violations
- October 18, 1989State Public Notification received4 linked violations
- June 5, 1989State Public Notification received1 linked violation
Common questions
Is LADD required to publish a Consumer Confidence Report?
- Yes. LADD 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 LADD’s next Consumer Confidence Report due?
- LADD’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does LADD have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for LADD.
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
ENGLEHAUPT, DOUG
815-894-2806
LADD, IL 61329