Is Brandy Lake Estates required to publish a Consumer Confidence Report?

Yes. Brandy Lake Estates 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 Brandy Lake Estates’s next Consumer Confidence Report due?

Brandy Lake Estates’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.

Detroit Lakes, MN · Becker County

Brandy Lake Estates Water System

Consumer Confidence Report status

Brandy Lake Estates 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 Brandy Lake Estates.

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

System facts

System ID (PWSID): MN1030022
System type: Community Water System
Population served: 40
Service connections: 21
Ownership: privately owned
Water source: groundwater (wells)

Brandy Lake Estates is one of 739 community water systems in Minnesota in the 500 or fewer people size category, serving 40 people from groundwater.

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

Of the 25, 11 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 inorganic chemicals, the Total Coliform Rules, and the Lead and Copper Rule.

Violation history

Monitoring, Routine (RTCR)
—
Revised Total Coliform Rule
January 1, 2025 – March 31, 2025
Resolved
Monitoring, Routine (RTCR)
—
Revised Total Coliform Rule
July 1, 2024 – September 30, 2024
Resolved
Monitoring, Routine (RTCR)
—
Revised Total Coliform Rule
April 1, 2024 – June 30, 2024
Resolved
Monitoring, Routine (RTCR)
—
Revised Total Coliform Rule
January 1, 2024 – March 31, 2024
Resolved
Monitoring, Routine (RTCR)
—
Revised Total Coliform Rule
January 1, 2023 – March 31, 2023
Resolved
Monitoring, Routine (RTCR)
—
Revised Total Coliform Rule
July 1, 2021 – September 30, 2021
Resolved
Monitoring, Routine (RTCR)
—
Revised Total Coliform Rule
October 1, 2020 – December 31, 2020
Resolved
Monitoring, Routine (RTCR)
—
Revised Total Coliform Rule
April 1, 2018 – June 30, 2018
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2017 – March 31, 2017
Resolved
Monitoring, Routine (RTCR)
—
Revised Total Coliform Rule
October 1, 2016 – December 31, 2016
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2015 – June 30, 2015
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2015 – March 31, 2015
Resolved
Lead Consumer Notice
—
Lead and Copper Rule
January 1, 2015 – July 22, 2015
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
October 1, 2014 – December 31, 2014
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2014 – March 31, 2014
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2013 – September 30, 2013
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2013 – June 30, 2013
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
October 1, 2012 – December 31, 2012
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
October 1, 2010 – December 31, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2010 – September 30, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2010 – June 30, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2010 – March 31, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2009 – September 30, 2009
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
June 16, 2009 – September 30, 2014
Archived
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
October 1, 2007 – December 31, 2007
Resolved

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

Period	Violation	Contaminant / rule	Health-based	Status
January 1, 2025 – March 31, 2025	Monitoring, Routine (RTCR)	Revised Total Coliform Rule	—	Resolved
July 1, 2024 – September 30, 2024	Monitoring, Routine (RTCR)	Revised Total Coliform Rule	—	Resolved
April 1, 2024 – June 30, 2024	Monitoring, Routine (RTCR)	Revised Total Coliform Rule	—	Resolved
January 1, 2024 – March 31, 2024	Monitoring, Routine (RTCR)	Revised Total Coliform Rule	—	Resolved
January 1, 2023 – March 31, 2023	Monitoring, Routine (RTCR)	Revised Total Coliform Rule	—	Resolved
July 1, 2021 – September 30, 2021	Monitoring, Routine (RTCR)	Revised Total Coliform Rule	—	Resolved
October 1, 2020 – December 31, 2020	Monitoring, Routine (RTCR)	Revised Total Coliform Rule	—	Resolved
April 1, 2018 – June 30, 2018	Monitoring, Routine (RTCR)	Revised Total Coliform Rule	—	Resolved
January 1, 2017 – March 31, 2017	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
October 1, 2016 – December 31, 2016	Monitoring, Routine (RTCR)	Revised Total Coliform Rule	—	Resolved
April 1, 2015 – June 30, 2015	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 2015 – March 31, 2015	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 2015 – July 22, 2015	Lead Consumer Notice	Lead and Copper Rule	—	Resolved
October 1, 2014 – December 31, 2014	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 2014 – March 31, 2014	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2013 – September 30, 2013	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
April 1, 2013 – June 30, 2013	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
October 1, 2012 – December 31, 2012	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
October 1, 2010 – December 31, 2010	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2010 – September 30, 2010	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
April 1, 2010 – June 30, 2010	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 2010 – March 31, 2010	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2009 – September 30, 2009	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
June 16, 2009 – September 30, 2014	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Archived
October 1, 2007 – December 31, 2007	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved

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

Enforcement actions

June 30, 2025State Compliance achieved1 linked violation
April 18, 2025State Public Notification requested1 linked violation
April 18, 2025State Formal Notice of Violation issued1 linked violation
March 5, 2025State Violation/Reminder Notice1 linked violation
December 11, 2024State Public Notification requested1 linked violation
December 11, 2024State Public Notification requested1 linked violation
December 11, 2024State Formal Notice of Violation issued1 linked violation
December 11, 2024State Formal Notice of Violation issued1 linked violation
December 11, 2024State Public Notification requested1 linked violation
December 11, 2024State Formal Notice of Violation issued1 linked violation
October 9, 2024State Compliance achieved1 linked violation
October 9, 2024State Compliance achieved1 linked violation
October 9, 2024State Compliance achieved1 linked violation
September 5, 2024State Violation/Reminder Notice1 linked violation
June 5, 2024State Violation/Reminder Notice1 linked violation
March 5, 2024State Violation/Reminder Notice1 linked violation
May 23, 2023State Compliance achieved1 linked violation
May 17, 2023State Formal Notice of Violation issued1 linked violation
May 17, 2023State Public Notification requested1 linked violation
March 5, 2023State Violation/Reminder Notice1 linked violation
March 11, 2022State Public Notification requested1 linked violation
March 11, 2022State Formal Notice of Violation issued1 linked violation
January 26, 2022State Compliance achieved1 linked violation
January 26, 2022State Compliance achieved1 linked violation
October 29, 2021State Formal Notice of Violation issued1 linked violation
October 29, 2021State Public Notification requested1 linked violation
September 5, 2021State Violation/Reminder Notice1 linked violation
March 31, 2021State Compliance achieved1 linked violation
March 11, 2021State Public Notification requested1 linked violation
March 11, 2021State Formal Notice of Violation issued1 linked violation
December 5, 2020State Violation/Reminder Notice1 linked violation
November 5, 2019State Compliance achieved1 linked violation
November 5, 2019State Compliance achieved11 linked violations
November 5, 2019State Compliance achieved1 linked violation
November 5, 2019State Compliance achieved1 linked violation
November 5, 2019State Compliance achieved1 linked violation
November 5, 2019State Compliance achieved1 linked violation
November 5, 2019State Compliance achieved1 linked violation
November 5, 2019State Compliance achieved1 linked violation
November 5, 2019State Compliance achieved1 linked violation
November 5, 2019State Compliance achieved1 linked violation
November 5, 2019State Compliance achieved1 linked violation
November 5, 2019State Compliance achieved1 linked violation
November 5, 2019State Compliance achieved1 linked violation
October 28, 2019State Compliance achieved1 linked violation
October 15, 2019State Formal Notice of Violation issued1 linked violation
October 15, 2019State Public Notification requested1 linked violation
September 17, 2019State Violation/Reminder Notice1 linked violation
January 8, 2019State Violation/Reminder Notice1 linked violation
January 8, 2019State Public Notification requested1 linked violation
January 8, 2019State Compliance Meeting conducted1 linked violation
August 27, 2018State Public Notification received1 linked violation
August 14, 2018State Compliance Meeting conducted3 linked violations
July 24, 2018State Public Notification requested2 linked violations
July 23, 2018State Compliance achieved2 linked violations
June 27, 2018State Compliance Meeting conducted3 linked violations
April 4, 2018State Violation/Reminder Notice1 linked violation
April 4, 2018State Public Notification requested1 linked violation
April 4, 2018State Compliance Meeting conducted1 linked violation
January 8, 2018State Public Notification received2 linked violations
December 22, 2017State Compliance Meeting conducted1 linked violation
December 22, 2017State Public Notification requested1 linked violation
December 22, 2017State Violation/Reminder Notice1 linked violation
October 17, 2017State Compliance Meeting conducted1 linked violation
October 17, 2017State Violation/Reminder Notice1 linked violation
October 17, 2017State Public Notification requested1 linked violation
March 27, 2017State Intentional no-action1 linked violation
February 15, 2017State Public Notification requested2 linked violations
February 15, 2017State Compliance Meeting conducted3 linked violations
January 23, 2017State Formal Notice of Violation issued1 linked violation
January 23, 2017State Public Notification requested1 linked violation
January 19, 2017State Compliance achieved1 linked violation
December 12, 2016State Public Notification received5 linked violations
November 14, 2016State Public Notification requested5 linked violations
November 14, 2016State Compliance Meeting conducted2 linked violations
November 14, 2016State Formal Notice of Violation issued1 linked violation
June 2, 2016State Administrative/Compliance Order without penalty issued8 linked violations
March 7, 2016State Compliance achieved1 linked violation
December 11, 2015State Violation/Reminder Notice2 linked violations
August 20, 2015State Public Notification requested2 linked violations
August 20, 2015State Formal Notice of Violation issued2 linked violations
May 20, 2015State Public Notification requested1 linked violation
May 20, 2015State Compliance Meeting conducted1 linked violation
May 20, 2015State Formal Notice of Violation issued1 linked violation
January 30, 2015State Public Notification requested1 linked violation
January 30, 2015State Formal Notice of Violation issued6 linked violations
December 3, 2014State Violation/Reminder Notice2 linked violations
June 10, 2014State Administrative/Compliance Order without penalty issued1 linked violation
May 15, 2014State Public Notification received1 linked violation
April 17, 2014State Public Notification requested1 linked violation
April 17, 2014State Formal Notice of Violation issued1 linked violation
April 16, 2014State Violation/Reminder Notice1 linked violation
April 2, 2014State Compliance achieved1 linked violation
March 31, 2014State Public Notification received2 linked violations
March 7, 2014State Violation/Reminder Notice1 linked violation
February 11, 2014State Violation/Reminder Notice1 linked violation
January 10, 2014State Administrative/Compliance Order without penalty issued1 linked violation
November 13, 2013State Violation/Reminder Notice1 linked violation
July 18, 2013State Violation/Reminder Notice1 linked violation
July 18, 2013State Formal Notice of Violation issued2 linked violations
December 10, 2012State Violation/Reminder Notice1 linked violation
February 18, 2011State Violation/Reminder Notice1 linked violation
November 10, 2010State Public Notification requested1 linked violation
November 10, 2010State Violation/Reminder Notice1 linked violation
June 21, 2010State Violation/Reminder Notice1 linked violation
April 6, 2010State Violation/Reminder Notice1 linked violation
January 11, 2010State Violation/Reminder Notice3 linked violations
December 17, 2009State Public Notification received1 linked violation
November 13, 2009State Public Notification requested3 linked violations
November 13, 2009State Violation/Reminder Notice1 linked violation
July 16, 2009State Formal Notice of Violation issued1 linked violation
July 16, 2009State Compliance Meeting conducted3 linked violations
July 16, 2009State Public Notification requested1 linked violation
August 12, 2008State Compliance achieved1 linked violation
February 27, 2008State Compliance achieved2 linked violations
February 11, 2008State Public Notification received1 linked violation
January 17, 2008State Formal Notice of Violation issued1 linked violation
January 17, 2008State Public Notification requested1 linked violation
December 18, 2007State Violation/Reminder Notice1 linked violation
December 4, 2007State Violation/Reminder Notice1 linked violation
November 5, 2007State Public Notification received1 linked violation
November 1, 2007State Formal Notice of Violation issued5 linked violations
November 1, 2007State Public Notification requested2 linked violations
October 11, 2007State Formal Notice of Violation issued1 linked violation
October 11, 2007State Public Notification requested1 linked violation
September 19, 2007State Violation/Reminder Notice1 linked violation
September 13, 2007State Violation/Reminder Notice1 linked violation
September 5, 2007State Violation/Reminder Notice2 linked violations
August 29, 2007State Violation/Reminder Notice1 linked violation
December 7, 2005State Compliance achieved2 linked violations
November 22, 2005State Public Notification received1 linked violation
October 12, 2005State Public Notification requested1 linked violation
October 12, 2005State Formal Notice of Violation issued1 linked violation
September 14, 2005State Violation/Reminder Notice1 linked violation
April 10, 2001State Formal Notice of Violation issued2 linked violations
April 10, 2001State Public Notification requested1 linked violation
February 27, 2001State Public Notification requested1 linked violation
January 10, 2001State Violation/Reminder Notice1 linked violation
January 10, 2001State Formal Notice of Violation issued1 linked violation
January 10, 2001State Public Notification requested1 linked violation
January 15, 2000State Formal Notice of Violation issued1 linked violation
July 15, 1999State Formal Notice of Violation issued2 linked violations
April 1, 1999State Public Notification received1 linked violation
January 15, 1999State Violation/Reminder Notice1 linked violation
January 15, 1999State Formal Notice of Violation issued1 linked violation
January 15, 1999State Public Notification requested1 linked violation
July 15, 1996State Administrative/Compliance Order with penalty issued6 linked violations
July 9, 1996State Public Notification requested11 linked violations
January 17, 1996State Violation/Reminder Notice7 linked violations
October 15, 1993State Public Notification requested3 linked violations
January 15, 1992State Public Notification requested1 linked violation
July 1, 1990State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
July 1, 1990State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
December 15, 1989State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
September 30, 1989State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
September 30, 1988State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
September 30, 1988State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
September 30, 1988State Technical Assistance Visitgeneral compliance action — not tied to a specific violation on record
September 30, 1987State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
September 30, 1986State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
September 30, 1985State Compliance achievedgeneral compliance action — not tied to a specific violation on record
September 30, 1985State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
September 30, 1984State Compliance achievedgeneral compliance action — not tied to a specific violation on record
September 30, 1984State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
September 30, 1983State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record

Common questions

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

Brandy Lake Estates

2188499201

Detroit Lakes, MN 56501