Is MORLEY MUNICIPAL WATER SUPPLY required to publish a Consumer Confidence Report?

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

MORLEY MUNICIPAL 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.

ANAMOSA, IA · Jones County

MORLEY MUNICIPAL WATER SUPPLY Water System

Consumer Confidence Report status

MORLEY MUNICIPAL 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 MORLEY MUNICIPAL 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): IA5349001
System type: Community Water System
Population served: 98
Service connections: 52
Ownership: local government
Water source: groundwater (wells)

MORLEY MUNICIPAL WATER SUPPLY is one of 1,221 community water systems in Iowa in the 500 or fewer people size category, serving 98 people from groundwater.

As of August 1, 2026, its federal record holds 18 entries between 2004 and 2007, all of which EPA lists as closed. Nothing has been added since 2007.

All 18 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, Regular
—
Xylenes, Total
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
Benzo(a)pyrene
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
Dalapon
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
Dinoseb
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
Picloram
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
Simazine
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
2,4,5-TP
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
Benzene
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
o-Dichlorobenzene
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
1,2-Dichloroethane
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
trans-1,2-Dichloroethylene
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
DICHLOROMETHANE
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
1,2-Dichloropropane
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
Ethylbenzene
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
CHLOROBENZENE
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
1,2,4-Trichlorobenzene
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
Trichloroethylene
January 1, 2007 – December 31, 2012
Resolved
Monitoring, Regular
—
Thallium, Total
January 1, 2004 – December 31, 2012
Resolved

Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
January 1, 2007 – December 31, 2012	Monitoring, Regular	Xylenes, Total	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	Benzo(a)pyrene	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	Dalapon	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	Dinoseb	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	Picloram	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	Simazine	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	2,4,5-TP	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	Benzene	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	o-Dichlorobenzene	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	1,2-Dichloroethane	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	trans-1,2-Dichloroethylene	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	DICHLOROMETHANE	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	1,2-Dichloropropane	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	Ethylbenzene	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	CHLOROBENZENE	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	1,2,4-Trichlorobenzene	—	Resolved
January 1, 2007 – December 31, 2012	Monitoring, Regular	Trichloroethylene	—	Resolved
January 1, 2004 – December 31, 2012	Monitoring, Regular	Thallium, Total	—	Resolved

Resolved addressed and confirmed by the state

Enforcement actions

January 21, 2026State Formal Notice of Violation issued2 linked violations
January 4, 2026State Compliance achieved22 linked violations
October 15, 2025State Compliance achieved2 linked violations
October 7, 2025State Public Notification received2 linked violations
July 25, 2025State Public Notification requested3 linked violations
September 16, 2022State Compliance achieved2 linked violations
August 18, 2022State Formal Notice of Violation issued3 linked violations
October 7, 2021State Compliance achieved1 linked violation
August 26, 2021State Formal Notice of Violation issued1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received2 linked violations
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received2 linked violations
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
July 1, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received2 linked violations
June 10, 2013State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received4 linked violations
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
June 10, 2013State Public Notification received1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved2 linked violations
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved3 linked violations
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved2 linked violations
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved4 linked violations
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved3 linked violations
March 11, 2013State Compliance achieved3 linked violations
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved1 linked violation
March 11, 2013State Compliance achieved2 linked violations
March 11, 2013State Compliance achieved5 linked violations
March 11, 2013State Compliance achieved3 linked violations
March 11, 2013State Compliance achieved2 linked violations
February 18, 2013State Formal Notice of Violation issued2 linked violations
February 18, 2013State Public Notification requested2 linked violations
February 18, 2013State Public Notification requested2 linked violations
February 18, 2013State Formal Notice of Violation issued2 linked violations
February 18, 2013State Public Notification requested2 linked violations
February 18, 2013State Public Notification requested2 linked violations
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued2 linked violations
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued1 linked violation
February 18, 2013State Formal Notice of Violation issued2 linked violations
February 18, 2013State Formal Notice of Violation issued2 linked violations
February 18, 2013State Public Notification requested2 linked violations
February 18, 2013State Formal Notice of Violation issued2 linked violations
February 18, 2013State Formal Notice of Violation issued4 linked violations
February 18, 2013State Public Notification requested5 linked violations
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Formal Notice of Violation issued2 linked violations
February 18, 2013State Public Notification requested2 linked violations
February 18, 2013State Public Notification requested1 linked violation
February 18, 2013State Public Notification requested2 linked violations
February 18, 2013State Formal Notice of Violation issued1 linked violation
September 3, 2004State Formal Notice of Violation issued8 linked violations
January 22, 1996State Public Notification requested2 linked violations
January 22, 1996State Formal Notice of Violation issued2 linked violations
November 28, 1995State Bilateral Compliance Agreement signed3 linked violations

Common questions

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

MORLEY MUNI WATER SUPPLY

319-480-2517

ANAMOSA, IA 52205