FORT DODGE, IA · Carroll County
LANESBORO WATER WORKS Water System
Current status
No open violations on record as of July 4, 2026.
This system's next federally required Consumer Confidence Report is due July 1, 2027, under the EPA's revised reporting rule.
Data sourced from the EPA ECHO database (SDWA bulk download), last refreshed July 4, 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)
Violation history
Maximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2024 – June 30, 2024
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
July 1, 2023 – September 30, 2023
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2023 – June 30, 2023
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2022 – March 31, 2022
ResolvedConsumer Confidence Report Complete Failure to Report
—Consumer Confidence Rule
July 1, 2021 – September 15, 2021
ResolvedMaximum Contaminant Level Violation, Single Sample
Health-basedArsenic
April 1, 2020 – March 31, 2021
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2012 – June 30, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
January 1, 2012 – March 31, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2011 – December 31, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
July 1, 2011 – September 30, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2011 – June 30, 2011
ResolvedConsumer Confidence Report Complete Failure to Report
—Consumer Confidence Rule
July 1, 2002 – June 6, 2003
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
July 1, 1998 – July 31, 1998
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, 2020 – March 31, 2021 | Maximum Contaminant Level Violation, Single Sample | Arsenic | Health-based | Resolved |
| April 1, 2012 – June 30, 2012 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| January 1, 2012 – March 31, 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 |
| July 1, 1998 – July 31, 1998 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- September 27, 2024State Intentional no-action1 linked violation
- September 27, 2024State Violation/Reminder Notice1 linked violation
- September 27, 2024State Formal Notice of Violation issued1 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 Formal Notice of Violation issued1 linked violation
- June 21, 2024State Public Notification requested1 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 Public Notification requested1 linked violation
- October 6, 2023State Formal Notice of Violation issued1 linked violation
- September 28, 2023State Public Notification received1 linked violation
- August 2, 2023State Public Notification requested1 linked violation
- August 2, 2023State Formal Notice of Violation issued1 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
- 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 Public Notification requested1 linked violation
- April 23, 2012State Formal Notice of Violation issued1 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
- March 4, 2003State Public Notification received5 linked violations
- February 19, 2003State Public Notification requested1 linked violation
- February 4, 2003State Compliance achieved3 linked violations
- July 23, 2002State Public Notification requested2 linked violations
- July 17, 2002State Public Notification requested1 linked violation
- May 21, 1999State Public Notification requested2 linked violations
- 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 Formal Notice of Violation issued1 linked violation
- September 15, 1998State Public Notification requested1 linked violation
- July 20, 1998State Formal Notice of Violation issued1 linked violation
- October 19, 1996State Formal Notice of Violation issued16 linked violations
- July 26, 1996State Compliance achieved1 linked violation
- June 4, 1996State Compliance achieved17 linked violations
- June 4, 1996State Compliance achieved3 linked violations
- June 16, 1995State Formal Notice of Violation issued4 linked violations
- June 16, 1995State Public Notification requested3 linked violations
- May 8, 1995State Compliance achieved3 linked violations
- August 26, 1994State Formal Notice of Violation issued2 linked violations
- August 26, 1994State Public Notification requested9 linked violations
- October 31, 1989State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- January 21, 1982State Unresolved1 linked violation
Contact
LANESBORO WATER WORKS
Phone not on record
FORT DODGE, IA 50501