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

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

CENTRAL 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 · Webster County

CENTRAL WATER WORKS Water System

Consumer Confidence Report status

CENTRAL 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 CENTRAL 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): IA9400801
System type: Community Water System
Population served: 27
Service connections: 17
Ownership: privately owned
Water source: groundwater (wells)

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

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

All 32 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 volatile organic chemicals, synthetic organic chemicals, and inorganic chemicals.

Violation history

Monitoring, Routine (RTCR)
—
Revised Total Coliform Rule
February 1, 2026 – February 28, 2026
Archived
Monitoring, Regular
—
Fluoride
April 1, 2009 – March 31, 2012
Resolved
Monitoring, Regular
—
o-Dichlorobenzene
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
p-Dichlorobenzene
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
1,2-Dichloroethane
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
cis-1,2-Dichloroethylene
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
1,1-Dichloroethylene
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
trans-1,2-Dichloroethylene
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
DICHLOROMETHANE
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
1,2-Dichloropropane
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Ethylbenzene
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
CHLOROBENZENE
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Styrene
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
1,2,4-Trichlorobenzene
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
1,1,1-Trichloroethane
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
1,1,2-Trichloroethane
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Trichloroethylene
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Vinyl chloride
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Xylenes, Total
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Atrazine
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Benzo(a)pyrene
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Dalapon
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Di(2-ethylhexyl) adipate
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Di(2-ethylhexyl) phthalate
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Pentachlorophenol
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Picloram
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Simazine
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
2,4,5-TP
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Benzene
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Carbon tetrachloride
April 1, 2006 – March 31, 2012
Resolved
Monitoring, Regular
—
Fluoride
March 1, 2006 – March 31, 2009
Resolved
Monitoring, Regular
—
Arsenic
April 1, 2001 – March 31, 2002
Resolved

Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
February 1, 2026 – February 28, 2026	Monitoring, Routine (RTCR)	Revised Total Coliform Rule	—	Archived
April 1, 2009 – March 31, 2012	Monitoring, Regular	Fluoride	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	o-Dichlorobenzene	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	p-Dichlorobenzene	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	1,2-Dichloroethane	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	cis-1,2-Dichloroethylene	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	1,1-Dichloroethylene	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	trans-1,2-Dichloroethylene	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	DICHLOROMETHANE	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	1,2-Dichloropropane	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Ethylbenzene	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	CHLOROBENZENE	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Styrene	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	1,2,4-Trichlorobenzene	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	1,1,1-Trichloroethane	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	1,1,2-Trichloroethane	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Trichloroethylene	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Vinyl chloride	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Xylenes, Total	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Atrazine	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Benzo(a)pyrene	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Dalapon	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Di(2-ethylhexyl) adipate	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Di(2-ethylhexyl) phthalate	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Pentachlorophenol	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Picloram	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Simazine	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	2,4,5-TP	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Benzene	—	Resolved
April 1, 2006 – March 31, 2012	Monitoring, Regular	Carbon tetrachloride	—	Resolved
March 1, 2006 – March 31, 2009	Monitoring, Regular	Fluoride	—	Resolved
April 1, 2001 – March 31, 2002	Monitoring, Regular	Arsenic	—	Resolved

Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state

Enforcement actions

March 26, 2026State Formal Notice of Violation issued1 linked violation
March 26, 2026State Public Notification requested1 linked violation
June 16, 2020State Compliance achieved1 linked violation
September 30, 2019State Public Notification received1 linked violation
September 30, 2019State Compliance achieved1 linked violation
September 17, 2019State Formal Notice of Violation issued1 linked violation
September 17, 2019State Public Notification requested1 linked violation
August 2, 2019State Formal Notice of Violation issued1 linked violation
July 5, 2019State Violation/Reminder Notice1 linked violation
September 25, 2013State Public Notification received2 linked violations
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received2 linked violations
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
May 20, 2013State Public Notification received1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved2 linked violations
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved2 linked violations
June 5, 2012State Compliance achieved4 linked violations
June 5, 2012State Compliance achieved3 linked violations
June 5, 2012State Compliance achieved2 linked violations
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
June 5, 2012State Compliance achieved1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Formal Notice of Violation issued2 linked violations
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued1 linked violation
May 18, 2012State Public Notification requested1 linked violation
May 18, 2012State Formal Notice of Violation issued4 linked violations
July 6, 2007State Public Notification requested6 linked violations
June 14, 2002State Public Notification received4 linked violations
January 28, 1998State Formal Notice of Violation issued1 linked violation
January 28, 1998State Formal Notice of Violation issued1 linked violation
January 28, 1998State Public Notification requested1 linked violation
January 28, 1998State Public Notification requested1 linked violation
June 6, 1996State Compliance achieved2 linked violations
June 6, 1996State Compliance achieved3 linked violations
December 17, 1993State Formal Notice of Violation issued3 linked violations
December 17, 1993State Public Notification requested4 linked violations
September 29, 1993State Formal Notice of Violation issued8 linked violations
June 18, 1993State Formal Notice of Violation issued7 linked violations
August 31, 1992State Public Notification requested3 linked violations
June 15, 1989State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
June 15, 1989State Formal Notice of Violation issued2 linked violations
June 15, 1989State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
September 30, 1984Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
March 1, 1982State Unresolvedgeneral compliance action — not tied to a specific violation on record
February 18, 1982State Unresolvedgeneral compliance action — not tied to a specific violation on record
February 16, 1982State Unresolvedgeneral compliance action — not tied to a specific violation on record
January 21, 1982State Unresolvedgeneral compliance action — not tied to a specific violation on record

Common questions

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

CENTRAL WATER WORKS OP

515-571-5070

FORT DODGE, IA 50501