Is SANBORN WATER SUPPLY required to publish a Consumer Confidence Report?

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

SANBORN WATER SUPPLY’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.

SANBORN, IA · O'Brien County

SANBORN WATER SUPPLY Water System

Consumer Confidence Report status

SANBORN WATER SUPPLY 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 SANBORN WATER SUPPLY.

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): IA7165025
System type: Community Water System
Population served: 1,392
Service connections: 699
Ownership: local government
Water source: groundwater (wells)

SANBORN WATER SUPPLY is one of 403 community water systems in Iowa in the 501 to 3,300 people size category, serving 1,392 people from groundwater.

As of August 1, 2026, its federal record holds 17 entries in 2013, all of which EPA lists as closed. Nothing has been added since 2013.

All 17 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 and synthetic organic chemicals.

Violation history

Monitoring, Regular
—
Diquat
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
LASSO
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
Atrazine
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
2,4-D
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
Di(2-ethylhexyl) phthalate
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
Pentachlorophenol
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
Picloram
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
Simazine
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
Carbon tetrachloride
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
1,2-Dichloroethane
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
cis-1,2-Dichloroethylene
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
DICHLOROMETHANE
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
CHLOROBENZENE
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
Tetrachloroethylene
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
1,2,4-Trichlorobenzene
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
Trichloroethylene
January 1, 2013 – December 31, 2018
Resolved
Monitoring, Regular
—
Xylenes, Total
January 1, 2013 – December 31, 2018
Resolved

Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
January 1, 2013 – December 31, 2018	Monitoring, Regular	Diquat	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	LASSO	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	Atrazine	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	2,4-D	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	Di(2-ethylhexyl) phthalate	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	Pentachlorophenol	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	Picloram	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	Simazine	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	Carbon tetrachloride	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	1,2-Dichloroethane	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	cis-1,2-Dichloroethylene	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	DICHLOROMETHANE	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	CHLOROBENZENE	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	Tetrachloroethylene	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	1,2,4-Trichlorobenzene	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	Trichloroethylene	—	Resolved
January 1, 2013 – December 31, 2018	Monitoring, Regular	Xylenes, Total	—	Resolved

Resolved addressed and confirmed by the state

Enforcement actions

May 31, 2019State Public Notification received1 linked violation
May 31, 2019State Public Notification received1 linked violation
May 31, 2019State Public Notification received1 linked violation
May 31, 2019State Public Notification received1 linked violation
May 31, 2019State Public Notification received1 linked violation
May 31, 2019State Public Notification received1 linked violation
May 31, 2019State Public Notification received1 linked violation
May 31, 2019State Public Notification received1 linked violation
May 31, 2019State Public Notification received1 linked violation
May 31, 2019State Public Notification received1 linked violation
May 31, 2019State Public Notification received1 linked violation
May 31, 2019State Public Notification received1 linked violation
March 12, 2019State Compliance achieved1 linked violation
March 12, 2019State Compliance achieved1 linked violation
March 12, 2019State Compliance achieved3 linked violations
March 12, 2019State Compliance achieved5 linked violations
March 12, 2019State Compliance achieved3 linked violations
March 12, 2019State Compliance achieved3 linked violations
March 12, 2019State Compliance achieved5 linked violations
March 12, 2019State Compliance achieved1 linked violation
March 12, 2019State Compliance achieved1 linked violation
March 12, 2019State Compliance achieved1 linked violation
March 12, 2019State Compliance achieved1 linked violation
March 12, 2019State Compliance achieved1 linked violation
March 12, 2019State Compliance achieved1 linked violation
March 12, 2019State Compliance achieved1 linked violation
March 12, 2019State Compliance achieved1 linked violation
March 12, 2019State Compliance achieved1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested4 linked violations
February 21, 2019State Public Notification requested2 linked violations
February 21, 2019State Formal Notice of Violation issued2 linked violations
February 21, 2019State Formal Notice of Violation issued3 linked violations
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Formal Notice of Violation issued2 linked violations
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested2 linked violations
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested2 linked violations
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Formal Notice of Violation issued1 linked violation
February 21, 2019State Public Notification requested1 linked violation
February 21, 2019State Public Notification requested1 linked violation
March 26, 1998State Public Notification received3 linked violations
February 17, 1998State Compliance achieved1 linked violation
February 11, 1998State Public Notification requested2 linked violations

Common questions

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

SANBORN WATER SUPPLY

712-930-3842

SANBORN, IA 51248