Is LANESBORO WATER WORKS required to publish a Consumer Confidence Report?

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

LANESBORO WATER WORKS’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.

FORT DODGE, IA · Carroll County

LANESBORO WATER WORKS Water System

Consumer Confidence Report status

LANESBORO WATER WORKS 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 LANESBORO WATER WORKS.

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 Iowa’s official records. Always confirm current status with Iowa before making decisions based on this information.

System facts

System ID (PWSID): IA1449053
System type: Community Water System
Population served: 119
Service connections: 70
Ownership: local government
Water source: groundwater (wells)

LANESBORO WATER WORKS is one of 1,221 community water systems in Iowa in the 500 or fewer people size category, serving 119 people from groundwater.

As of August 1, 2026, its federal record holds 10 entries between 2002 and 2024, all of which EPA lists as closed.

None of the 10 are monitoring or reporting requirements — the category that accounts for about four in five of all violations in EPA's national dataset; these involve water-quality, treatment, or public-notice findings instead. The record involves inorganic chemicals and the Consumer Confidence Rule.

Violation history

Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2024 – June 30, 2024
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2023 – September 30, 2023
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2023 – June 30, 2023
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2022 – March 31, 2022
Resolved
Consumer Confidence Report Complete Failure to Report
—
Consumer Confidence Rule
July 1, 2021 – September 15, 2021
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2012 – June 30, 2012
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
October 1, 2011 – December 31, 2011
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2011 – September 30, 2011
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2011 – June 30, 2011
Resolved
Consumer Confidence Report Complete Failure to Report
—
Consumer Confidence Rule
July 1, 2002 – June 6, 2003
Resolved

Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
April 1, 2024 – June 30, 2024	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2023 – September 30, 2023	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
April 1, 2023 – June 30, 2023	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 2022 – March 31, 2022	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2021 – September 15, 2021	Consumer Confidence Report Complete Failure to Report	Consumer Confidence Rule	—	Resolved
April 1, 2012 – June 30, 2012	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
October 1, 2011 – December 31, 2011	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2011 – September 30, 2011	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
April 1, 2011 – June 30, 2011	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2002 – June 6, 2003	Consumer Confidence Report Complete Failure to Report	Consumer Confidence Rule	—	Resolved

Resolved addressed and confirmed by the state

Enforcement actions

July 1, 2025State Public Notification received3 linked violations
July 1, 2025State Compliance achieved3 linked violations
September 27, 2024State Formal Notice of Violation issued1 linked violation
September 27, 2024State Intentional no-action1 linked violation
August 8, 2024State Compliance achieved1 linked violation
August 8, 2024State Compliance achieved1 linked violation
August 8, 2024State Compliance achieved1 linked violation
August 8, 2024State Compliance achieved1 linked violation
August 8, 2024State Compliance achieved1 linked violation
August 8, 2024State Compliance achieved1 linked violation
August 8, 2024State Compliance achieved1 linked violation
August 8, 2024State Compliance achieved1 linked violation
August 8, 2024State Compliance achieved1 linked violation
August 8, 2024State Compliance achieved1 linked violation
August 8, 2024State Compliance achieved1 linked violation
August 8, 2024State Compliance achieved1 linked violation
July 19, 2024State Public Notification received1 linked violation
July 9, 2024State Public Notification requested1 linked violation
June 21, 2024State Public Notification requested1 linked violation
June 21, 2024State Formal Notice of Violation issued1 linked violation
March 10, 2024State Public Notification received1 linked violation
February 6, 2024State Formal Notice of Violation issued1 linked violation
February 6, 2024State Public Notification requested1 linked violation
January 1, 2024State Public Notification received1 linked violation
October 25, 2023State Administrative/Compliance Order without penalty issued1 linked violation
October 25, 2023State Administrative/Compliance Order without penalty issued1 linked violation
October 25, 2023State Administrative/Compliance Order without penalty issued1 linked violation
October 25, 2023State Administrative/Compliance Order without penalty issued1 linked violation
October 25, 2023State Administrative/Compliance Order without penalty issued1 linked violation
October 25, 2023State Administrative/Compliance Order without penalty issued1 linked violation
October 25, 2023State Administrative/Compliance Order without penalty issued1 linked violation
October 6, 2023State Formal Notice of Violation issued1 linked violation
October 6, 2023State Public Notification requested1 linked violation
September 28, 2023State Public Notification received1 linked violation
August 2, 2023State Formal Notice of Violation issued1 linked violation
August 2, 2023State Public Notification requested1 linked violation
May 16, 2023State Public Notification received1 linked violation
April 24, 2023State Public Notification requested1 linked violation
April 24, 2023State Formal Notice of Violation issued1 linked violation
July 5, 2022State Compliance achieved1 linked violation
June 28, 2022State Administrative/Compliance Order without penalty issued1 linked violation
June 28, 2022State Administrative/Compliance Order without penalty issued1 linked violation
June 28, 2022State Administrative/Compliance Order without penalty issued1 linked violation
June 28, 2022State Administrative/Compliance Order without penalty issued1 linked violation
June 28, 2022State Administrative/Compliance Order without penalty issued1 linked violation
June 28, 2022State Administrative/Compliance Order without penalty issued1 linked violation
June 28, 2022State Administrative/Compliance Order without penalty issued1 linked violation
February 24, 2022State Public Notification received1 linked violation
February 24, 2022State Public Notification received1 linked violation
January 18, 2022State Formal Notice of Violation issued1 linked violation
January 18, 2022State Public Notification requested1 linked violation
September 15, 2021State Compliance achieved1 linked violation
August 26, 2021State Formal Notice of Violation issued1 linked violation
April 6, 2021State Compliance achieved1 linked violation
January 19, 2021State Public Notification received1 linked violation
January 14, 2021State Formal Notice of Violation issued1 linked violation
January 14, 2021State Public Notification requested1 linked violation
October 24, 2012State Public Notification received1 linked violation
October 23, 2012State Compliance achieved1 linked violation
October 23, 2012State Compliance achieved1 linked violation
October 23, 2012State Compliance achieved1 linked violation
October 23, 2012State Compliance achieved1 linked violation
October 23, 2012State Compliance achieved1 linked violation
October 23, 2012State Compliance achieved1 linked violation
October 12, 2012State Public Notification requested1 linked violation
October 12, 2012State Formal Notice of Violation issued1 linked violation
August 1, 2012State Public Notification received1 linked violation
August 1, 2012State Public Notification received1 linked violation
May 31, 2012State Public Notification requested1 linked violation
May 31, 2012State Formal Notice of Violation issued1 linked violation
April 23, 2012State Formal Notice of Violation issued1 linked violation
April 23, 2012State Public Notification requested1 linked violation
April 20, 2012State Bilateral Compliance Agreement signed1 linked violation
April 20, 2012State Bilateral Compliance Agreement signed1 linked violation
April 20, 2012State Bilateral Compliance Agreement signed1 linked violation
April 20, 2012State Bilateral Compliance Agreement signed1 linked violation
April 20, 2012State Bilateral Compliance Agreement signed1 linked violation
April 20, 2012State Bilateral Compliance Agreement signed1 linked violation
February 10, 2012State Public Notification received1 linked violation
January 11, 2012State Bilateral Compliance Agreement signed1 linked violation
January 11, 2012State Bilateral Compliance Agreement signed1 linked violation
January 11, 2012State Bilateral Compliance Agreement signed1 linked violation
January 11, 2012State Bilateral Compliance Agreement signed1 linked violation
January 11, 2012State Public Notification requested1 linked violation
January 11, 2012State Bilateral Compliance Agreement signed2 linked violations
January 11, 2012State Bilateral Compliance Agreement signed2 linked violations
June 6, 2003State Compliance achieved2 linked violations
February 19, 2003State Public Notification requested1 linked violation
May 21, 1999State Formal Notice of Violation issued3 linked violations
September 23, 1998State Compliance achieved1 linked violation
September 23, 1998State Compliance achieved2 linked violations
September 15, 1998State Public Notification requested1 linked violation
September 15, 1998State Formal Notice of Violation issued1 linked violation
July 20, 1998State Formal Notice of Violation issued1 linked violation
June 4, 1998State Public Notification received32 linked violations
October 19, 1996State Formal Notice of Violation issued16 linked violations
October 9, 1996State Compliance achieved38 linked violations
July 26, 1996State Compliance achieved1 linked violation
June 24, 1996State Formal Notice of Violation issued5 linked violations
June 16, 1995State Formal Notice of Violation issued4 linked violations
May 8, 1995State Compliance achieved3 linked violations
August 26, 1994State Public Notification requested3 linked violations
October 31, 1989State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
September 19, 1989State Compliance achievedgeneral compliance action — not tied to a specific violation on record
September 30, 1984Federal issued Formal Notice of Violation1 linked violation

Common questions

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

LANESBORO WATER WORKS

Phone not on record

FORT DODGE, IA 50501