CLARKSBURG, WV · Harrison County
EAST VIEW PSD 172 Water System
Consumer Confidence Report status
EAST VIEW PSD 172 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 EAST VIEW PSD 172.
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 West Virginia’s official records. Always confirm current status with West Virginia before making decisions based on this information.
System facts
- System ID (PWSID)
- WV3301737
- System type
- Community Water System
- Population served
- 164
- Service connections
- 67
- Ownership
- privately owned
- Water source
- surface water (rivers, lakes, or reservoirs)
EAST VIEW PSD 172 is one of 760 community water systems in West Virginia in the 500 or fewer people size category, serving 164 people from surface water.
As of August 1, 2026, EPA's published records contain no violations for this system.
Violation history
No violations on record for this system.
Enforcement actions
- November 11, 2025State Formal Notice of Violation issued1 linked violation
- November 10, 2025State Compliance achieved1 linked violation
- November 15, 2024State Formal Notice of Violation issued1 linked violation
- May 16, 2024State Formal Notice of Violation issued1 linked violation
- December 28, 2022State Formal Notice of Violation issued1 linked violation
- March 15, 2022State Public Notification received1 linked violation
- March 15, 2022State Public Notification received1 linked violation
- February 16, 2022State Public Notification requested1 linked violation
- February 16, 2022State Public Notification requested1 linked violation
- February 16, 2022State Formal Notice of Violation issued1 linked violation
- February 16, 2022State Formal Notice of Violation issued1 linked violation
- February 15, 2022State Formal Notice of Violation issued1 linked violation
- January 5, 2022State Public Notification received1 linked violation
- November 16, 2021State Public Notification requested1 linked violation
- November 16, 2021State Formal Notice of Violation issued1 linked violation
- September 16, 2021State Formal Notice of Violation issued1 linked violation
- September 16, 2021State Formal Notice of Violation issued1 linked violation
- August 31, 2021State Intentional no-action2 linked violations
- August 13, 2021State Formal Notice of Violation issued1 linked violation
- August 13, 2021State Formal Notice of Violation issued1 linked violation
- August 15, 2020State Public Notification requested1 linked violation
- August 15, 2020State Formal Notice of Violation issued1 linked violation
- August 15, 2020State Public Notification requested1 linked violation
- August 15, 2020State Formal Notice of Violation issued1 linked violation
- August 12, 2020State Compliance achieved2 linked violations
- August 19, 2019State Compliance achieved1 linked violation
- August 15, 2019State Formal Notice of Violation issued1 linked violation
- March 26, 2019State Compliance achieved1 linked violation
- March 6, 2019State Formal Notice of Violation issued1 linked violation
- January 8, 2019State Compliance achieved1 linked violation
- November 13, 2018State Formal Notice of Violation issued1 linked violation
- December 9, 2017State Formal Notice of Violation issued1 linked violation
- August 23, 2017State Public Notification received1 linked violation
- August 23, 2017State Public Notification received1 linked violation
- August 9, 2017State Public Notification requested1 linked violation
- August 9, 2017State Formal Notice of Violation issued1 linked violation
- August 9, 2017State Public Notification requested1 linked violation
- August 9, 2017State Formal Notice of Violation issued1 linked violation
- August 1, 2017State Compliance achieved2 linked violations
- December 5, 2016State Public Notification received1 linked violation
- November 15, 2016State Public Notification requested1 linked violation
- November 15, 2016State Formal Notice of Violation issued1 linked violation
- November 15, 2016State Formal Notice of Violation issued1 linked violation
- November 15, 2016State Public Notification requested1 linked violation
- November 2, 2016State Compliance achieved4 linked violations
- October 17, 2016State Public Notification received1 linked violation
- October 17, 2016State Public Notification received1 linked violation
- October 13, 2016State Compliance achieved1 linked violation
- October 13, 2016State Compliance achieved1 linked violation
- September 29, 2016State Public Notification received1 linked violation
- September 29, 2016State Public Notification received1 linked violation
- September 10, 2016State Formal Notice of Violation issued1 linked violation
- September 10, 2016State Formal Notice of Violation issued1 linked violation
- September 10, 2016State Public Notification requested1 linked violation
- September 10, 2016State Public Notification requested1 linked violation
- September 6, 2016State Public Notification received1 linked violation
- September 6, 2016State Public Notification received1 linked violation
- August 23, 2016State Compliance achieved2 linked violations
- August 12, 2016State Public Notification requested1 linked violation
- August 12, 2016State Public Notification requested1 linked violation
- August 12, 2016State Formal Notice of Violation issued1 linked violation
- August 12, 2016State Formal Notice of Violation issued1 linked violation
- May 4, 2016State Formal Notice of Violation issued1 linked violation
- May 4, 2016State Formal Notice of Violation issued1 linked violation
- March 4, 2016State Compliance achieved2 linked violations
- February 16, 2016State Formal Notice of Violation issued1 linked violation
- February 16, 2016State Formal Notice of Violation issued1 linked violation
- August 3, 2015State Compliance achieved2 linked violations
- April 4, 2015State Public Notification requested1 linked violation
- April 4, 2015State Public Notification requested1 linked violation
- April 4, 2015State Formal Notice of Violation issued1 linked violation
- April 9, 2008State Boil Water Ordergeneral compliance action — not tied to a specific violation on record
- April 6, 2005State Public Notification received1 linked violation
- March 26, 2005State Public Notification requested1 linked violation
- March 26, 2005State Formal Notice of Violation issued1 linked violation
- March 14, 2005State Compliance achieved1 linked violation
- March 31, 1994State Compliance achieved1 linked violation
- January 11, 1994State Public Notification requested1 linked violation
- January 11, 1994State Formal Notice of Violation issued1 linked violation
Common questions
Is EAST VIEW PSD 172 required to publish a Consumer Confidence Report?
- Yes. EAST VIEW PSD 172 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 EAST VIEW PSD 172’s next Consumer Confidence Report due?
- EAST VIEW PSD 172’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does EAST VIEW PSD 172 have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for EAST VIEW PSD 172.
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
BLAKE, MICHAEL E.
304-624-2502
CLARKSBURG, WV 26301