OHIO, IL · Bureau County
OHIO Water System
Consumer Confidence Report status
OHIO 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 OHIO.
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)
- IL0110800
- System type
- Community Water System
- Population served
- 465
- Service connections
- 246
- Ownership
- local government
- Water source
- groundwater (wells)
OHIO is one of 1,572 community water systems in Illinois in the 500 or fewer people size category, serving 465 people from groundwater.
As of August 1, 2026, its federal record holds 9 entries between 1977 and 2009, all of which EPA lists as closed. Nothing has been added since 2009.
Of the 9, 2 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 inorganic chemicals, volatile organic chemicals, and the Radionuclides and Revised Rad Rule.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2009 – December 31, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2009 – June 30, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2008 – December 31, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
July 1, 2008 – September 30, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2007 – December 31, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2006 – December 31, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2006 – June 30, 2006
ResolvedMonitoring, Regular
—Carbon tetrachloride
October 1, 1991 – December 31, 1991
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 |
|---|---|---|---|---|
| October 1, 2009 – December 31, 2009 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| April 1, 2009 – June 30, 2009 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| October 1, 2008 – December 31, 2008 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| July 1, 2008 – September 30, 2008 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| October 1, 2007 – December 31, 2007 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| October 1, 2006 – December 31, 2006 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| April 1, 2006 – June 30, 2006 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| October 1, 1991 – December 31, 1991 | Monitoring, Regular | Carbon tetrachloride | — | 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 30, 2010State Compliance achieved1 linked violation
- March 5, 2010State Compliance achieved16 linked violations
- January 20, 2010State Violation/Reminder Notice1 linked violation
- November 9, 2009State Public Notification received1 linked violation
- October 30, 2009State Violation/Reminder Notice1 linked violation
- October 20, 2009State Violation/Reminder Notice1 linked violation
- October 20, 2009State Public Notification requested1 linked violation
- August 2, 2009State Public Notification received1 linked violation
- July 15, 2009State Violation/Reminder Notice1 linked violation
- July 15, 2009State Public Notification requested1 linked violation
- May 4, 2009State Public Notification received1 linked violation
- April 21, 2009State Violation/Reminder Notice1 linked violation
- April 21, 2009State Public Notification requested1 linked violation
- January 31, 2009State Public Notification received1 linked violation
- January 15, 2009State Violation/Reminder Notice1 linked violation
- January 15, 2009State Public Notification requested1 linked violation
- November 3, 2008State Public Notification received1 linked violation
- October 27, 2008State Violation/Reminder Notice1 linked violation
- October 27, 2008State Public Notification requested1 linked violation
- August 5, 2008State Public Notification received1 linked violation
- July 16, 2008State Violation/Reminder Notice1 linked violation
- July 16, 2008State Public Notification requested1 linked violation
- May 1, 2008State Public Notification received1 linked violation
- April 16, 2008State Violation/Reminder Notice1 linked violation
- April 16, 2008State Public Notification requested1 linked violation
- April 2, 2008State Bilateral Compliance Agreement signed1 linked violation
- March 25, 2008State Compliance achieved1 linked violation
- March 11, 2008State Public Notification received1 linked violation
- March 3, 2008State Formal Notice of Violation issued1 linked violation
- February 13, 2008State Violation/Reminder Notice1 linked violation
- February 13, 2008State Public Notification requested1 linked violation
- January 29, 2008State Public Notification received1 linked violation
- January 16, 2008State Violation/Reminder Notice1 linked violation
- January 16, 2008State Public Notification requested1 linked violation
- October 30, 2007State Public Notification received1 linked violation
- October 15, 2007State Public Notification requested1 linked violation
- October 15, 2007State Violation/Reminder Notice1 linked violation
- August 2, 2007State Public Notification received1 linked violation
- July 17, 2007State Public Notification requested1 linked violation
- July 17, 2007State Violation/Reminder Notice1 linked violation
- May 5, 2007State Public Notification received1 linked violation
- April 12, 2007State Violation/Reminder Notice1 linked violation
- April 12, 2007State Public Notification requested1 linked violation
- February 3, 2007State Public Notification received1 linked violation
- January 3, 2007State Violation/Reminder Notice1 linked violation
- January 3, 2007State Public Notification requested1 linked violation
- November 8, 2006State Public Notification received1 linked violation
- October 11, 2006State Violation/Reminder Notice1 linked violation
- October 11, 2006State Public Notification requested1 linked violation
- August 11, 2006State Public Notification received1 linked violation
- July 31, 2006State Violation/Reminder Notice1 linked violation
- July 31, 2006State Public Notification requested1 linked violation
- June 22, 2006State Bilateral Compliance Agreement signed16 linked violations
- May 15, 2006State Public Notification received1 linked violation
- April 13, 2006State Formal Notice of Violation issued16 linked violations
- April 10, 2006State Violation/Reminder Notice1 linked violation
- April 10, 2006State Public Notification requested1 linked violation
- February 19, 1993State Compliance achieved7 linked violations
- August 29, 1992State Violation/Reminder Notice1 linked violation
- August 29, 1992State Public Notification requested1 linked violation
- August 24, 1992State Public Notification received1 linked violation
- March 11, 1992State Public Notification requested7 linked violations
- October 1, 1991State Public Notification requested7 linked violations
- October 1, 1991State Violation/Reminder Notice7 linked violations
- September 29, 1991State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- September 9, 1991State Public Notification received1 linked violation
- August 31, 1991State Violation/Reminder Notice1 linked violation
- August 31, 1991State Public Notification requested1 linked violation
Common questions
Is OHIO required to publish a Consumer Confidence Report?
- Yes. OHIO 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 OHIO’s next Consumer Confidence Report due?
- OHIO’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does OHIO have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for OHIO.
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
THOMAS, CHARLES L.
815-376-6446
OHIO, IL 61349