Is MOUNTAIN LAKES WATER COMPANY required to publish a Consumer Confidence Report?

Yes. MOUNTAIN LAKES WATER COMPANY 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 MOUNTAIN LAKES WATER COMPANY’s next Consumer Confidence Report due?

MOUNTAIN LAKES WATER COMPANY’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.

VA · Greene County

MOUNTAIN LAKES WATER COMPANY Water System

Consumer Confidence Report status

MOUNTAIN LAKES WATER COMPANY 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 MOUNTAIN LAKES WATER COMPANY.

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

System facts

System ID (PWSID): VA2079590
System type: Community Water System
Population served: 2,304
Service connections: 854
Ownership: privately owned
Water source: groundwater (wells)

MOUNTAIN LAKES WATER COMPANY is one of 391 community water systems in Virginia in the 501 to 3,300 people size category, serving 2,304 people from groundwater.

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

All 8 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, the Total Coliform Rules, and inorganic chemicals.

Violation history

Monitoring, Routine (RTCR)
—
Revised Total Coliform Rule
August 1, 2022 – August 31, 2022
Resolved
Monitoring, Regular
—
1,2,4-Trichlorobenzene
January 1, 2019 – December 31, 2019
Resolved
Monitoring, Regular
—
Vinyl chloride
January 1, 2019 – December 31, 2019
Resolved
Monitoring, Regular
—
Tetrachloroethylene
January 1, 2019 – December 31, 2019
Resolved
Monitoring, Regular
—
Ethylbenzene
October 1, 2009 – December 31, 2009
Resolved
Monitoring, Regular
—
p-Dichlorobenzene
July 1, 2009 – September 30, 2009
Resolved
Monitoring, Regular
—
Trichloroethylene
July 1, 2009 – September 30, 2009
Resolved
Monitoring, Regular
—
Cadmium
January 1, 2008 – December 31, 2010
Resolved

Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
August 1, 2022 – August 31, 2022	Monitoring, Routine (RTCR)	Revised Total Coliform Rule	—	Resolved
January 1, 2019 – December 31, 2019	Monitoring, Regular	1,2,4-Trichlorobenzene	—	Resolved
January 1, 2019 – December 31, 2019	Monitoring, Regular	Vinyl chloride	—	Resolved
January 1, 2019 – December 31, 2019	Monitoring, Regular	Tetrachloroethylene	—	Resolved
October 1, 2009 – December 31, 2009	Monitoring, Regular	Ethylbenzene	—	Resolved
July 1, 2009 – September 30, 2009	Monitoring, Regular	p-Dichlorobenzene	—	Resolved
July 1, 2009 – September 30, 2009	Monitoring, Regular	Trichloroethylene	—	Resolved
January 1, 2008 – December 31, 2010	Monitoring, Regular	Cadmium	—	Resolved

Resolved addressed and confirmed by the state

Enforcement actions

February 13, 2026State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
February 13, 2026State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
October 7, 2025State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
September 25, 2025State Compliance achievedgeneral compliance action — not tied to a specific violation on record
September 9, 2025State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
September 9, 2025State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
August 26, 2025State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
April 3, 2025State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
April 3, 2025State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
December 15, 2024State Compliance achieved6 linked violations
July 24, 2024State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
July 22, 2024State Compliance achievedgeneral compliance action — not tied to a specific violation on record
March 18, 2024State Compliance achieved1 linked violation
March 18, 2024State Compliance achieved2 linked violations
March 18, 2024State Compliance achieved1 linked violation
March 18, 2024State Compliance achieved1 linked violation
March 18, 2024State Compliance achievedgeneral compliance action — not tied to a specific violation on record
March 18, 2024State Compliance achieved1 linked violation
March 18, 2024State Compliance achieved1 linked violation
March 18, 2024State Compliance achieved2 linked violations
March 18, 2024State Compliance achievedgeneral compliance action — not tied to a specific violation on record
March 18, 2024State Compliance achievedgeneral compliance action — not tied to a specific violation on record
March 18, 2024State Compliance achieved1 linked violation
January 2, 2024State Public Notification received2 linked violations
September 6, 2023State Public Notification requested4 linked violations
July 19, 2023State Compliance achieved4 linked violations
July 3, 2023State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
July 3, 2023State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
July 3, 2023State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
February 15, 2023State Public Notification requested3 linked violations
February 15, 2023State Public Notification requested1 linked violation
February 15, 2023State Formal Notice of Violation issued1 linked violation
February 15, 2023State Public Notification requested1 linked violation
February 15, 2023State Formal Notice of Violation issued3 linked violations
February 15, 2023State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
February 15, 2023State Public Notification requested1 linked violation
February 15, 2023State Formal Notice of Violation issued1 linked violation
February 15, 2023State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
February 15, 2023State Public Notification requested1 linked violation
February 15, 2023State Formal Notice of Violation issued1 linked violation
February 15, 2023State Public Notification requested1 linked violation
February 15, 2023State Public Notification requested1 linked violation
February 15, 2023State Formal Notice of Violation issued1 linked violation
February 15, 2023State Public Notification requested2 linked violations
February 15, 2023State Public Notification requested1 linked violation
February 15, 2023State Formal Notice of Violation issued1 linked violation
February 15, 2023State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
February 15, 2023State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
February 15, 2023State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
February 15, 2023State Public Notification requested2 linked violations
September 26, 2022State Public Notification requested3 linked violations
September 7, 2022State Compliance achieved2 linked violations
May 21, 2020State Public Notification received1 linked violation
March 25, 2020State Compliance achieved22 linked violations
March 25, 2020State Compliance achieved1 linked violation
March 25, 2020State Compliance achieved2 linked violations
March 25, 2020State Compliance achieved3 linked violations
January 30, 2020State Public Notification requested1 linked violation
January 23, 2020State Public Notification requested22 linked violations
January 23, 2020State Public Notification requested1 linked violation
January 23, 2020State Formal Notice of Violation issued1 linked violation
January 23, 2020State Formal Notice of Violation issued2 linked violations
January 23, 2020State Formal Notice of Violation issued22 linked violations
February 27, 2019State Public Notification requested2 linked violations
October 29, 2018State Public Notification received1 linked violation
October 23, 2018State Public Notification requested3 linked violations
October 23, 2018State Formal Notice of Violation issued1 linked violation
May 8, 2018State Public Notification requested1 linked violation
May 8, 2018State Formal Notice of Violation issued1 linked violation
April 18, 2018State Compliance achieved1 linked violation
July 13, 2017State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
March 26, 2014State Compliance achieved3 linked violations
March 24, 2014State Formal Notice of Violation issued4 linked violations
March 24, 2014State Public Notification requested12 linked violations
October 29, 2013State Compliance achieved1 linked violation
October 25, 2013State Formal Notice of Violation issued1 linked violation
October 21, 2013State Formal Notice of Violation issued1 linked violation
October 21, 2013State Public Notification requested1 linked violation
August 26, 2013State Compliance achieved1 linked violation
August 12, 2013State Public Notification requested1 linked violation
February 27, 2012State Compliance achieved1 linked violation
February 24, 2012State Public Notification received1 linked violation
January 24, 2012State Public Notification requested1 linked violation
January 24, 2012State Formal Notice of Violation issued1 linked violation
March 11, 2011Federal Compliance achieved3 linked violations
March 11, 2011Federal Compliance achieved385 linked violations
March 7, 2011State Compliance achieved10 linked violations
March 7, 2011State Compliance achieved1 linked violation
March 7, 2011State Compliance achieved10 linked violations
March 7, 2011State Compliance achieved1 linked violation
January 24, 2011State Public Notification requested10 linked violations
January 24, 2011State Formal Notice of Violation issued10 linked violations
January 24, 2011State Public Notification requested1 linked violation
January 24, 2011State Formal Notice of Violation issued1 linked violation
June 30, 2010State Compliance achieved1 linked violation
June 30, 2010State Compliance achieved1 linked violation
June 30, 2010State Compliance achieved2 linked violations
June 22, 2010State Compliance achieved21 linked violations
March 29, 2010State Compliance achieved1 linked violation
March 29, 2010State Compliance achieved1 linked violation
March 29, 2010State Compliance achieved1 linked violation
March 29, 2010State Compliance achieved23 linked violations
March 29, 2010State Compliance achieved1 linked violation
March 29, 2010State Compliance achieved21 linked violations
March 29, 2010State Compliance achieved1 linked violation
March 29, 2010State Compliance achieved3 linked violations
March 29, 2010State Compliance achieved21 linked violations
January 20, 2010State Formal Notice of Violation issued21 linked violations
January 20, 2010State Formal Notice of Violation issued2 linked violations
January 20, 2010State Public Notification requested1 linked violation
January 20, 2010State Formal Notice of Violation issued1 linked violation
January 20, 2010State Public Notification requested1 linked violation
January 20, 2010State Formal Notice of Violation issued1 linked violation
January 20, 2010State Public Notification requested21 linked violations
October 13, 2009State Formal Notice of Violation issued1 linked violation
October 13, 2009State Formal Notice of Violation issued1 linked violation
October 13, 2009State Public Notification requested1 linked violation
October 13, 2009State Public Notification requested1 linked violation
October 13, 2009State Public Notification requested21 linked violations
October 13, 2009State Formal Notice of Violation issued21 linked violations
July 24, 2009State Public Notification requested21 linked violations
July 24, 2009State Formal Notice of Violation issued21 linked violations
July 24, 2009State Public Notification requested1 linked violation
July 24, 2009State Formal Notice of Violation issued1 linked violation
July 24, 2009State Public Notification requested1 linked violation
July 24, 2009State Formal Notice of Violation issued1 linked violation
June 24, 2009State Compliance achieved1 linked violation
June 24, 2009State Compliance achieved1 linked violation
June 23, 2009State Public Notification received1 linked violation
February 17, 2009Federal issued Formal Notice of Violation37 linked violations
January 28, 2009State Formal Notice of Violation issued1 linked violation
January 28, 2009State Public Notification requested1 linked violation
October 27, 2008State Formal Notice of Violation issued2 linked violations
October 27, 2008State Public Notification requested2 linked violations
October 27, 2008State Formal Notice of Violation issued3 linked violations
July 1, 2008State Public Notification received33 linked violations
February 6, 2008State Public Notification requested5 linked violations
February 6, 2008State Public Notification requested3 linked violations
January 30, 2008State Public Notification requested2 linked violations
January 30, 2008State Formal Notice of Violation issued1 linked violation
January 30, 2008State Public Notification requested6 linked violations
January 30, 2008State Public Notification requested22 linked violations
July 23, 2007State Compliance achieved3 linked violations
July 5, 2007State Formal Notice of Violation issued4 linked violations
July 5, 2007State Formal Notice of Violation issued2 linked violations
June 19, 2007State Compliance achieved3 linked violations
April 19, 2007State Public Notification requested3 linked violations
February 14, 2007State Formal Notice of Violation issued4 linked violations
September 28, 2004State Compliance achieved2 linked violations
August 27, 2004State Compliance achieved1 linked violation
August 17, 2004State Formal Notice of Violation issued5 linked violations
July 1, 2004State Public Notification received3 linked violations
April 30, 2003State Public Notification received7 linked violations
March 19, 2003State Compliance achieved1 linked violation
August 29, 2000State Compliance achieved1 linked violation

Common questions

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

Not on record

Phone not on record