Is GLENDALE COLONY required to publish a Consumer Confidence Report?

Yes. GLENDALE COLONY 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 GLENDALE COLONY’s next Consumer Confidence Report due?

GLENDALE COLONY’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.

FRANKFORT, SD · Spink County

GLENDALE COLONY Water System

Consumer Confidence Report status

GLENDALE COLONY 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 GLENDALE COLONY.

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

System facts

System ID (PWSID): SD4602060
System type: Community Water System
Population served: 95
Service connections: 25
Ownership: privately owned
Water source: groundwater (wells)

GLENDALE COLONY is one of 583 community water systems in South Dakota in the 500 or fewer people size category, serving 95 people from groundwater.

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

Of the 53, 50 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

Maximum Contaminant Level Violation, E. coli (RTCR)
Health-based
Revised Total Coliform Rule
November 1, 2025 – November 30, 2025
Archived
Monitoring, Regular
—
Nickel
January 1, 2012 – December 31, 2012
Resolved
Monitoring, Regular
—
Beryllium, Total
January 1, 2012 – December 31, 2012
Resolved
Monitoring, Regular
—
Thallium, Total
January 1, 2012 – December 31, 2012
Resolved
Monitoring, Regular
—
Selenium
January 1, 2012 – December 31, 2012
Resolved
Monitoring, Regular
—
Mercury
January 1, 2012 – December 31, 2012
Resolved
Monitoring, Regular
—
Fluoride
January 1, 2012 – December 31, 2012
Resolved
Monitoring, Regular
—
Chromium
January 1, 2012 – December 31, 2012
Resolved
Monitoring, Regular
—
Arsenic
January 1, 2012 – December 31, 2012
Resolved
Monitoring, Regular
—
Cadmium
January 1, 2012 – December 31, 2012
Resolved
Monitoring, Regular
—
Vinyl chloride
April 1, 2004 – June 30, 2004
Resolved
Monitoring, Regular
—
Trichloroethylene
April 1, 2004 – June 30, 2004
Resolved
Monitoring, Regular
—
Benzene
April 1, 2004 – June 30, 2004
Resolved
Monitoring, Regular
—
o-Dichlorobenzene
April 1, 2004 – June 30, 2004
Resolved
Monitoring, Regular
—
Styrene
April 1, 2004 – June 30, 2004
Resolved
Monitoring, Regular
—
CHLOROBENZENE
April 1, 2004 – June 30, 2004
Resolved
Monitoring, Regular
—
Carbon tetrachloride
April 1, 2004 – June 30, 2004
Resolved
Monitoring, Regular
—
1,1,2-Trichloroethane
April 1, 2004 – June 30, 2004
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
February 1, 2004 – February 29, 2004
Resolved
Monitoring, Regular
—
ETHYLENE DIBROMIDE
January 1, 2004 – March 30, 2004
Resolved
Monitoring, Regular
—
Benzo(a)pyrene
January 1, 2004 – March 30, 2004
Resolved
Monitoring, Regular
—
Di(2-ethylhexyl) adipate
January 1, 2004 – March 30, 2004
Resolved
Monitoring, Regular
—
Hexachlorocyclopentadiene
January 1, 2004 – March 30, 2004
Resolved
Monitoring, Regular
—
Toxaphene
January 1, 2004 – March 30, 2004
Resolved
Monitoring, Regular
—
Carbofuran
January 1, 2004 – March 30, 2004
Resolved
Monitoring, Regular
—
Dalapon
January 1, 2004 – March 30, 2004
Resolved
Monitoring, Regular
—
2,4,5-TP
January 1, 2004 – March 30, 2004
Resolved
Monitoring, Regular
—
Picloram
January 1, 2004 – March 30, 2004
Resolved
Monitoring, Regular
—
2,4-D
January 1, 2004 – March 30, 2004
Resolved
Monitoring, Regular
—
1,2-DIBROMO-3-CHLOROPROPANE
January 1, 2004 – March 30, 2004
Resolved
Monitoring, Regular
—
Endothall
January 1, 2004 – March 30, 2004
Resolved
Monitoring, Regular
—
Heptachlor
January 1, 2004 – March 30, 2004
Resolved
Monitoring, Regular
—
Ethylbenzene
October 1, 2003 – December 31, 2003
Resolved
Monitoring, Regular
—
Tetrachloroethylene
October 1, 2003 – December 31, 2003
Resolved
Monitoring, Regular
—
Vinyl chloride
October 1, 2003 – December 31, 2003
Resolved
Monitoring, Regular
—
Xylenes, Total
October 1, 2003 – December 31, 2003
Resolved
Monitoring, Regular
—
cis-1,2-Dichloroethylene
October 1, 2003 – December 31, 2003
Resolved
Public Notification Violation for NPDWR Violation
—
Public Notice
June 15, 2003 – June 29, 2006
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
March 1, 2003 – March 31, 2003
Resolved
Monitoring, Regular
—
Xylenes, Total
January 1, 2003 – March 30, 2003
Resolved
Monitoring, Regular
—
1,2-Dichloropropane
January 1, 2003 – March 30, 2003
Resolved
Monitoring, Regular
—
Vinyl chloride
January 1, 2003 – March 30, 2003
Resolved
Monitoring, Regular
—
Tetrachloroethylene
January 1, 2003 – March 30, 2003
Resolved
Monitoring, Regular
—
1,1,1-Trichloroethane
January 1, 2003 – March 30, 2003
Resolved
Public Notification Violation for NPDWR Violation
—
Public Notice
March 11, 2002 – June 29, 2006
Resolved
Monitoring, Regular
—
DICHLOROMETHANE
January 1, 2002 – March 30, 2002
Resolved
Monitoring, Regular
—
Beryllium, Total
January 1, 2002 – December 31, 2002
Resolved
Monitoring, Regular
—
Cadmium
January 1, 2002 – December 31, 2002
Resolved
Monitoring, Regular
—
Arsenic
January 1, 2002 – December 31, 2002
Resolved
Monitoring, Regular
—
Trichloroethylene
January 1, 2002 – March 30, 2002
Resolved
Monitoring, Regular
—
p-Dichlorobenzene
January 1, 2002 – March 30, 2002
Resolved
Follow-up Or Routine LCR Tap M/R
—
Lead and Copper Rule
October 1, 2001 – June 13, 2002
Resolved
Monitoring, Regular
—
Aldicarb sulfoxide
January 1, 1993 – December 31, 1995
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
November 1, 2025 – November 30, 2025	Maximum Contaminant Level Violation, E. coli (RTCR)	Revised Total Coliform Rule	Health-based	Archived
January 1, 2012 – December 31, 2012	Monitoring, Regular	Nickel	—	Resolved
January 1, 2012 – December 31, 2012	Monitoring, Regular	Beryllium, Total	—	Resolved
January 1, 2012 – December 31, 2012	Monitoring, Regular	Thallium, Total	—	Resolved
January 1, 2012 – December 31, 2012	Monitoring, Regular	Selenium	—	Resolved
January 1, 2012 – December 31, 2012	Monitoring, Regular	Mercury	—	Resolved
January 1, 2012 – December 31, 2012	Monitoring, Regular	Fluoride	—	Resolved
January 1, 2012 – December 31, 2012	Monitoring, Regular	Chromium	—	Resolved
January 1, 2012 – December 31, 2012	Monitoring, Regular	Arsenic	—	Resolved
January 1, 2012 – December 31, 2012	Monitoring, Regular	Cadmium	—	Resolved
April 1, 2004 – June 30, 2004	Monitoring, Regular	Vinyl chloride	—	Resolved
April 1, 2004 – June 30, 2004	Monitoring, Regular	Trichloroethylene	—	Resolved
April 1, 2004 – June 30, 2004	Monitoring, Regular	Benzene	—	Resolved
April 1, 2004 – June 30, 2004	Monitoring, Regular	o-Dichlorobenzene	—	Resolved
April 1, 2004 – June 30, 2004	Monitoring, Regular	Styrene	—	Resolved
April 1, 2004 – June 30, 2004	Monitoring, Regular	CHLOROBENZENE	—	Resolved
April 1, 2004 – June 30, 2004	Monitoring, Regular	Carbon tetrachloride	—	Resolved
April 1, 2004 – June 30, 2004	Monitoring, Regular	1,1,2-Trichloroethane	—	Resolved
February 1, 2004 – February 29, 2004	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved
January 1, 2004 – March 30, 2004	Monitoring, Regular	ETHYLENE DIBROMIDE	—	Resolved
January 1, 2004 – March 30, 2004	Monitoring, Regular	Benzo(a)pyrene	—	Resolved
January 1, 2004 – March 30, 2004	Monitoring, Regular	Di(2-ethylhexyl) adipate	—	Resolved
January 1, 2004 – March 30, 2004	Monitoring, Regular	Hexachlorocyclopentadiene	—	Resolved
January 1, 2004 – March 30, 2004	Monitoring, Regular	Toxaphene	—	Resolved
January 1, 2004 – March 30, 2004	Monitoring, Regular	Carbofuran	—	Resolved
January 1, 2004 – March 30, 2004	Monitoring, Regular	Dalapon	—	Resolved
January 1, 2004 – March 30, 2004	Monitoring, Regular	2,4,5-TP	—	Resolved
January 1, 2004 – March 30, 2004	Monitoring, Regular	Picloram	—	Resolved
January 1, 2004 – March 30, 2004	Monitoring, Regular	2,4-D	—	Resolved
January 1, 2004 – March 30, 2004	Monitoring, Regular	1,2-DIBROMO-3-CHLOROPROPANE	—	Resolved
January 1, 2004 – March 30, 2004	Monitoring, Regular	Endothall	—	Resolved
January 1, 2004 – March 30, 2004	Monitoring, Regular	Heptachlor	—	Resolved
October 1, 2003 – December 31, 2003	Monitoring, Regular	Ethylbenzene	—	Resolved
October 1, 2003 – December 31, 2003	Monitoring, Regular	Tetrachloroethylene	—	Resolved
October 1, 2003 – December 31, 2003	Monitoring, Regular	Vinyl chloride	—	Resolved
October 1, 2003 – December 31, 2003	Monitoring, Regular	Xylenes, Total	—	Resolved
October 1, 2003 – December 31, 2003	Monitoring, Regular	cis-1,2-Dichloroethylene	—	Resolved
June 15, 2003 – June 29, 2006	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
March 1, 2003 – March 31, 2003	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved
January 1, 2003 – March 30, 2003	Monitoring, Regular	Xylenes, Total	—	Resolved
January 1, 2003 – March 30, 2003	Monitoring, Regular	1,2-Dichloropropane	—	Resolved
January 1, 2003 – March 30, 2003	Monitoring, Regular	Vinyl chloride	—	Resolved
January 1, 2003 – March 30, 2003	Monitoring, Regular	Tetrachloroethylene	—	Resolved
January 1, 2003 – March 30, 2003	Monitoring, Regular	1,1,1-Trichloroethane	—	Resolved
March 11, 2002 – June 29, 2006	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
January 1, 2002 – March 30, 2002	Monitoring, Regular	DICHLOROMETHANE	—	Resolved
January 1, 2002 – December 31, 2002	Monitoring, Regular	Beryllium, Total	—	Resolved
January 1, 2002 – December 31, 2002	Monitoring, Regular	Cadmium	—	Resolved
January 1, 2002 – December 31, 2002	Monitoring, Regular	Arsenic	—	Resolved
January 1, 2002 – March 30, 2002	Monitoring, Regular	Trichloroethylene	—	Resolved
January 1, 2002 – March 30, 2002	Monitoring, Regular	p-Dichlorobenzene	—	Resolved
October 1, 2001 – June 13, 2002	Follow-up Or Routine LCR Tap M/R	Lead and Copper Rule	—	Resolved
January 1, 1993 – December 31, 1995	Monitoring, Regular	Aldicarb sulfoxide	—	Resolved

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

Enforcement actions

November 19, 2025State Public Notification requested1 linked violation
December 1, 2024State Compliance achieved1 linked violation
November 13, 2024State Public Notification received1 linked violation
November 8, 2024State Public Notification requested1 linked violation
February 17, 2013State Compliance achieved1 linked violation
January 14, 2013State Public Notification received1 linked violation
January 14, 2013State Public Notification received1 linked violation
January 14, 2013State Public Notification received2 linked violations
January 14, 2013State Public Notification received2 linked violations
January 14, 2013State Public Notification received1 linked violation
January 14, 2013State Public Notification received2 linked violations
January 10, 2013State Compliance achieved1 linked violation
January 10, 2013State Compliance achieved1 linked violation
January 10, 2013State Compliance achieved1 linked violation
January 10, 2013State Compliance achieved1 linked violation
January 10, 2013State Compliance achieved1 linked violation
January 10, 2013State Compliance achieved1 linked violation
January 10, 2013State Compliance achieved2 linked violations
January 10, 2013State Compliance achieved1 linked violation
January 10, 2013State Compliance achieved1 linked violation
January 10, 2013State Compliance achieved1 linked violation
January 2, 2013State Public Notification requested2 linked violations
January 2, 2013State Public Notification requested2 linked violations
January 2, 2013State Public Notification requested2 linked violations
January 2, 2013State Public Notification requested4 linked violations
June 12, 2012State Public Notification received1 linked violation
June 1, 2012State Compliance achieved5 linked violations
June 29, 2006State Public Notification received1 linked violation
June 29, 2006State Public Notification received1 linked violation
June 29, 2006State Public Notification received1 linked violation
June 29, 2006State Compliance achieved1 linked violation
June 29, 2006State Compliance achieved1 linked violation
June 29, 2006State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved2 linked violations
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved2 linked violations
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved2 linked violations
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
November 22, 2004State Compliance achieved1 linked violation
September 1, 2004State Compliance achieved1 linked violation
August 4, 2004State Public Notification issued1 linked violation
August 3, 2004State Public Notification received1 linked violation
August 3, 2004State Public Notification received2 linked violations
August 3, 2004State Public Notification received1 linked violation
August 3, 2004State Public Notification received2 linked violations
August 3, 2004State Public Notification received1 linked violation
August 3, 2004State Public Notification received1 linked violation
August 3, 2004State Public Notification received1 linked violation
August 3, 2004State Public Notification received1 linked violation
August 3, 2004State Public Notification received1 linked violation
August 3, 2004State Public Notification received1 linked violation
August 3, 2004State Public Notification received1 linked violation
August 3, 2004State Public Notification received1 linked violation
August 3, 2004State Public Notification received2 linked violations
August 3, 2004State Public Notification received2 linked violations
August 3, 2004State Public Notification received1 linked violation
August 3, 2004State Public Notification received1 linked violation
August 3, 2004State Public Notification received1 linked violation
August 3, 2004State Public Notification received1 linked violation
August 3, 2004State Public Notification received1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested2 linked violations
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
July 15, 2004State Public Notification requested1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved2 linked violations
June 8, 2004State Compliance achieved2 linked violations
June 8, 2004State Compliance achieved2 linked violations
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved2 linked violations
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
June 8, 2004State Compliance achieved1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
April 21, 2004State Public Notification requested1 linked violation
March 4, 2004State Public Notification received1 linked violation
March 1, 2004State Public Notification requested1 linked violation
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received2 linked violations
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received2 linked violations
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received1 linked violation
February 20, 2004State Public Notification received1 linked violation
January 28, 2004State Public Notification requested1 linked violation
January 28, 2004State Public Notification requested1 linked violation
January 28, 2004State Public Notification requested1 linked violation
January 28, 2004State Public Notification requested1 linked violation
January 28, 2004State Public Notification requested1 linked violation
January 28, 2004State Public Notification requested2 linked violations
January 28, 2004State Public Notification requested2 linked violations
January 28, 2004State Public Notification requested1 linked violation
January 28, 2004State Public Notification requested1 linked violation
January 28, 2004State Public Notification requested2 linked violations
January 28, 2004State Public Notification requested2 linked violations
January 28, 2004State Public Notification requested2 linked violations
January 28, 2004State Public Notification requested1 linked violation
January 28, 2004State Public Notification requested1 linked violation
January 28, 2004State Public Notification requested1 linked violation
January 28, 2004State Public Notification requested1 linked violation
January 28, 2004State Public Notification requested1 linked violation
January 28, 2004State Public Notification requested1 linked violation
January 28, 2004State Public Notification requested1 linked violation
January 28, 2004State Public Notification requested1 linked violation
January 6, 2004State Public Notification requested2 linked violations
January 1, 2004State Compliance achieved1 linked violation
January 1, 2004State Compliance achieved2 linked violations
July 23, 2003State Compliance achieved1 linked violation
July 23, 2003State Compliance achieved1 linked violation
July 23, 2003State Compliance achieved1 linked violation
July 23, 2003State Compliance achieved2 linked violations
July 23, 2003State Compliance achieved1 linked violation
July 23, 2003State Compliance achieved2 linked violations
July 23, 2003State Compliance achieved1 linked violation
July 23, 2003State Compliance achieved1 linked violation
July 23, 2003State Compliance achieved1 linked violation
July 23, 2003State Compliance achieved1 linked violation
July 23, 2003State Compliance achieved1 linked violation
July 23, 2003State Compliance achieved1 linked violation
July 23, 2003State Compliance achieved2 linked violations
July 23, 2003State Compliance achieved1 linked violation
July 23, 2003State Compliance achieved1 linked violation
July 23, 2003State Compliance achieved1 linked violation
July 23, 2003State Compliance achieved2 linked violations
July 23, 2003State Compliance achieved3 linked violations
July 23, 2003State Compliance achieved2 linked violations
July 23, 2003State Compliance achieved2 linked violations
July 23, 2003State Compliance achieved2 linked violations
July 23, 2003State Compliance achieved2 linked violations
July 9, 2003State Public Notification requested5 linked violations
July 9, 2003State Public Notification requested5 linked violations
July 9, 2003State Public Notification requested4 linked violations
July 9, 2003State Public Notification requested2 linked violations
July 9, 2003State Public Notification requested6 linked violations
July 9, 2003State Public Notification requested5 linked violations
January 22, 2003State Compliance achieved2 linked violations
January 17, 2003State Public Notification received2 linked violations
January 17, 2003State Public Notification received1 linked violation
January 17, 2003State Public Notification received3 linked violations
January 17, 2003State Public Notification received1 linked violation
January 17, 2003State Public Notification received1 linked violation
January 17, 2003State Public Notification received3 linked violations
January 10, 2003State Public Notification requested1 linked violation
January 10, 2003State Public Notification requested2 linked violations
January 10, 2003State Public Notification requested2 linked violations
January 10, 2003State Public Notification requested2 linked violations
January 10, 2003State Public Notification requested1 linked violation
January 10, 2003State Public Notification requested1 linked violation
January 10, 2003State Public Notification requested3 linked violations
January 10, 2003State Public Notification requested1 linked violation
December 1, 2002State Compliance achieved1 linked violation
June 13, 2002State Compliance achieved3 linked violations
April 17, 2002State Public Notification requested3 linked violations
April 17, 2002State Public Notification requested2 linked violations
April 17, 2002State Public Notification requested2 linked violations
April 17, 2002State Public Notification requested5 linked violations
April 17, 2002State Public Notification requested2 linked violations
April 17, 2002State Public Notification requested2 linked violations
April 17, 2002State Public Notification requested3 linked violations
February 1, 2001State Compliance achieved1 linked violation
August 29, 2000State Public Notification received2 linked violations
January 13, 2000State Public Notification received1 linked violation
November 17, 1997State Administrative/Compliance Order without penalty issued36 linked violations
March 25, 1997State Public Notification received12 linked violations
May 1, 1995State Compliance achieved1 linked violation
September 12, 1994State Public Notification requested21 linked violations

Common questions

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

GLENDALE COLONY

6054721251

FRANKFORT, SD 57440