Is LOSTANT required to publish a Consumer Confidence Report?

Yes. LOSTANT 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 LOSTANT’s next Consumer Confidence Report due?

LOSTANT’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.

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.

LOSTANT, IL · LaSalle County

LOSTANT Water System

Consumer Confidence Report status

LOSTANT 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 open health-based violation for LOSTANT, alongside 2 other open items.

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): IL0990450
System type: Community Water System
Population served: 463
Service connections: 210
Ownership: local government
Water source: groundwater (wells)

LOSTANT is one of 1,572 community water systems in Illinois in the 500 or fewer people size category, serving 463 people from groundwater.

As of August 1, 2026, its federal record holds 22 entries between 1977 and 2025, of which 1 health-based item remains open, alongside 2 other open entries.

Of the 22, 4 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 Lead and Copper Rule, and the Consumer Confidence Rule.

Violation history

Notification, Known or Potential LSL
—
LEAD AND COPPER RULE REVISIONS
July 2, 2025
Unaddressed
Consumer Confidence Report Inadequate Reporting
—
Consumer Confidence Rule
July 1, 2025
Unaddressed
LSL Inventory
Health-based
LEAD AND COPPER RULE REVISIONS
October 17, 2024
Unaddressed
Monitoring, Regular
—
Combined Radium (-226 and -228)
January 1, 2021 – December 31, 2021
Resolved
Consumer Confidence Report Complete Failure to Report
—
Consumer Confidence Rule
July 1, 2011 – July 12, 2011
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2004 – December 31, 2004
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2004 – June 30, 2004
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2003 – December 31, 2003
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2003 – September 30, 2003
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2003 – June 30, 2003
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2003 – March 31, 2003
Resolved
Monitoring, Regular
—
Nitrate
January 1, 2003 – December 31, 2003
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2002 – December 31, 2002
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
April 1, 1999 – September 30, 2002
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
September 1, 1996 – August 31, 2000
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
March 22, 1995 – March 21, 1999
Resolved
OCCT/SOWT Study/Recommendation
Health-based
Lead and Copper Rule
January 12, 1995 – May 21, 1997
Resolved
Public Education
Health-based
Lead and Copper Rule
January 1, 1995 – February 8, 2001
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
May 18, 1990 – March 2, 1993
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 1988 – August 31, 1992
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
September 1, 1988 – August 31, 1992
Resolved
Monitoring, 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
July 2, 2025	Notification, Known or Potential LSL	LEAD AND COPPER RULE REVISIONS	—	Unaddressed
July 1, 2025	Consumer Confidence Report Inadequate Reporting	Consumer Confidence Rule	—	Unaddressed
October 17, 2024	LSL Inventory	LEAD AND COPPER RULE REVISIONS	Health-based	Unaddressed
January 1, 2021 – December 31, 2021	Monitoring, Regular	Combined Radium (-226 and -228)	—	Resolved
July 1, 2011 – July 12, 2011	Consumer Confidence Report Complete Failure to Report	Consumer Confidence Rule	—	Resolved
October 1, 2004 – December 31, 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
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
January 1, 2003 – December 31, 2003	Monitoring, Regular	Nitrate	—	Resolved
October 1, 2002 – December 31, 2002	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
April 1, 1999 – September 30, 2002	Maximum Contaminant Level Violation, Average	Gross Alpha, Excl. Radon and U	Health-based	Resolved
September 1, 1996 – August 31, 2000	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
March 22, 1995 – March 21, 1999	Maximum Contaminant Level Violation, Average	Gross Alpha, Excl. Radon and U	Health-based	Resolved
January 12, 1995 – May 21, 1997	OCCT/SOWT Study/Recommendation	Lead and Copper Rule	Health-based	Resolved
January 1, 1995 – February 8, 2001	Public Education	Lead and Copper Rule	Health-based	Resolved
May 18, 1990 – March 2, 1993	Maximum Contaminant Level Violation, Average	Gross Alpha, Excl. Radon and U	Health-based	Resolved
October 1, 1988 – August 31, 1992	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
September 1, 1988 – August 31, 1992	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

August 27, 2025State Public Notification received1 linked violation
August 5, 2025State Violation/Reminder Notice1 linked violation
July 22, 2025State Violation/Reminder Notice1 linked violation
July 22, 2025State Public Notification requested1 linked violation
July 3, 2025State Public Notification requested1 linked violation
July 3, 2025State Violation/Reminder Notice1 linked violation
January 25, 2022State Compliance achieved1 linked violation
January 19, 2022State Violation/Reminder Notice1 linked violation
January 19, 2022State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
August 9, 2011State Violation/Reminder Notice1 linked violation
July 12, 2011State Compliance achieved1 linked violation
March 29, 2005State Bilateral Compliance Agreement signed2 linked violations
February 23, 2005State Formal Notice of Violation issued2 linked violations
February 4, 2005State Compliance achieved15 linked violations
January 27, 2005State Public Notification received2 linked violations
January 27, 2005State Compliance achieved2 linked violations
January 7, 2005State Public Notification requested1 linked violation
January 7, 2005State Violation/Reminder Notice1 linked violation
December 27, 2004State Public Notification received1 linked violation
December 22, 2004State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
December 22, 2004State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
November 17, 2004State Compliance achieved1 linked violation
November 8, 2004State Compliance achieved2 linked violations
October 19, 2004State Violation/Reminder Notice1 linked violation
October 19, 2004State Public Notification requested1 linked violation
October 5, 2004State Violation/Reminder Notice2 linked violations
September 14, 2004State Public Notification received1 linked violation
September 14, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
August 13, 2004State Compliance achieved2 linked violations
August 13, 2004State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
August 13, 2004State Public Notification received1 linked violation
July 10, 2004State Violation/Reminder Notice9 linked violations
October 16, 2003State Public Notification received1 linked violation
July 21, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
July 21, 2003State Public Notification received1 linked violation
April 15, 2003State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
April 15, 2003State Public Notification received1 linked violation
April 10, 2003State Public Notification requested1 linked violation
April 10, 2003State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
April 10, 2003State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
April 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 requested1 linked violation
January 10, 2003State Violation/Reminder Notice1 linked violation
January 10, 2003State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
November 13, 2001State Bilateral Compliance Agreement signed12 linked violations
February 8, 2001State Compliance achieved2 linked violations
June 1, 1998State Public Notification received1 linked violation
May 1, 1998State Public Notification received1 linked violation
April 1, 1998State Public Notification received1 linked violation
March 1, 1998State Public Notification received1 linked violation
February 1, 1998State Public Notification received1 linked violation
January 1, 1998State Public Notification received1 linked violation
December 1, 1997State Public Notification received1 linked violation
October 1, 1997State Public Notification received1 linked violation
September 1, 1997State Public Notification received1 linked violation
August 1, 1997State Public Notification received2 linked violations
July 1, 1997State Public Notification received1 linked violation
June 1, 1997State Public Notification received1 linked violation
May 21, 1997State Compliance achieved2 linked violations
May 1, 1997State Public Notification received1 linked violation
April 1, 1997State Public Notification received1 linked violation
February 1, 1997State Public Notification received1 linked violation
December 30, 1996State Public Notification received1 linked violation
December 1, 1996State Public Notification received1 linked violation
November 1, 1996State Public Notification received1 linked violation
October 1, 1996State Public Notification received1 linked violation
September 1, 1996State Public Notification received1 linked violation
August 1, 1996State Public Notification received1 linked violation
June 6, 1996State Public Notification received1 linked violation
May 1, 1996State Public Notification received1 linked violation
March 12, 1996State Violation/Reminder Notice1 linked violation
March 12, 1996State Public Notification requested6 linked violations
March 1, 1996State Public Notification received1 linked violation
February 1, 1996State Public Notification received1 linked violation
January 1, 1996State Public Notification received1 linked violation
September 1, 1995State Public Notification received1 linked violation
August 1, 1995State Public Notification received1 linked violation
July 1, 1995State Public Notification received1 linked violation
June 1, 1995State Public Notification received1 linked violation
April 1, 1995State Public Notification received1 linked violation
March 22, 1995State Bilateral Compliance Agreement signed1 linked violation
March 22, 1995State Public Notification received1 linked violation
March 1, 1995State Public Notification received1 linked violation
February 1, 1995State Public Notification received1 linked violation
January 1, 1995State Public Notification received1 linked violation
December 1, 1994State Public Notification received1 linked violation
November 1, 1994State Public Notification received1 linked violation
October 1, 1994State Public Notification received1 linked violation
August 1, 1994State Public Notification received2 linked violations
June 1, 1994State Public Notification received1 linked violation
May 1, 1994State Public Notification received1 linked violation
April 1, 1994State Public Notification received2 linked violations
April 1, 1994State Public Notification received1 linked violation
March 2, 1994State Public Notification received1 linked violation
February 1, 1994State Public Notification received1 linked violation
January 1, 1994State Public Notification received1 linked violation
December 1, 1993State Public Notification received1 linked violation
November 1, 1993State Public Notification received1 linked violation
October 1, 1993State Public Notification received2 linked violations
October 1, 1993State Public Notification received1 linked violation
July 5, 1993State Public Notification received1 linked violation
June 1, 1993State Public Notification received1 linked violation
May 1, 1993State Public Notification received1 linked violation
April 1, 1993State Public Notification received1 linked violation
March 2, 1993State Compliance achieved1 linked violation
February 1, 1993State Public Notification received2 linked violations
January 1, 1993State Public Notification received2 linked violations
November 1, 1992State Public Notification received3 linked violations
August 24, 1992State Public Notification received3 linked violations
June 26, 1992State Public Notification received3 linked violations
June 3, 1992State Public Notification received3 linked violations
April 1, 1992State Public Notification received3 linked violations
February 1, 1992State Public Notification received4 linked violations
November 1, 1991State Public Notification received3 linked violations
September 7, 1991State Public Notification received3 linked violations
August 1, 1991State Public Notification received3 linked violations
July 1, 1991State Public Notification received3 linked violations
June 20, 1991State Public Notification requested3 linked violations
January 18, 1991State Public Notification requested3 linked violations
October 14, 1990State Public Notification requested1 linked violation
September 10, 1990State Public Notification received3 linked violations
August 21, 1990State Public Notification issued3 linked violations
July 20, 1990State Public Notification requested3 linked violations
March 1, 1990State Public Notification received2 linked violations
December 26, 1989State Public Notification received2 linked violations
November 12, 1988State Violation/Reminder Notice1 linked violation
October 31, 1988State Public Notification received5 linked violations

Common questions

Is LOSTANT required to publish a Consumer Confidence Report?: Yes. LOSTANT 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 LOSTANT’s next Consumer Confidence Report due?: LOSTANT’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does LOSTANT have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show 1 open health-based violation for LOSTANT, alongside 2 other open items.
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

IMMEL, JOHN

815-488-9746

LOSTANT, IL 61334