DAVY, WV · McDowell County
DAVY MUNICIPAL WATER WORKS Water System
Consumer Confidence Report status
DAVY MUNICIPAL WATER WORKS 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 DAVY MUNICIPAL WATER WORKS.
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)
- WV3302425
- System type
- Community Water System
- Population served
- 332
- Service connections
- 157
- Ownership
- local government
- Water source
- groundwater (wells)
DAVY MUNICIPAL WATER WORKS is one of 760 community water systems in West Virginia in the 500 or fewer people size category, serving 332 people from groundwater.
As of August 1, 2026, its federal record holds 10 entries between 2016 and 2023, all of which EPA lists as closed. Nothing has been added since 2023.
Of the 10, 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 the Total Coliform Rules, the Public Notice Rule and Revised PN Rule, and inorganic chemicals.
Violation history
Public Notification Violation for NPDWR Violation
—Public Notice
October 15, 2023 – October 27, 2023
ResolvedMonitoring, Regular
—Chromium
January 1, 2023 – December 31, 2025
ArchivedMonitoring, Regular
—Antimony, Total
January 1, 2023 – December 31, 2025
ArchivedLead Consumer Notice
—Lead and Copper Rule
January 1, 2020 – September 30, 2020
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
September 1, 2019 – September 30, 2019
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
August 1, 2019 – August 31, 2019
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
May 1, 2019 – May 31, 2019
ResolvedMonitoring of Treatment (SWTR-Unfilt/GWR)
—Groundwater Rule
February 1, 2019 – February 28, 2019
ResolvedMonitoring and Reporting (DBP)
—Chlorine
July 1, 2018 – September 9, 2018
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
September 10, 2016 – July 14, 2017
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 |
|---|---|---|---|---|
| October 15, 2023 – October 27, 2023 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| January 1, 2023 – December 31, 2025 | Monitoring, Regular | Chromium | — | Archived |
| January 1, 2023 – December 31, 2025 | Monitoring, Regular | Antimony, Total | — | Archived |
| January 1, 2020 – September 30, 2020 | Lead Consumer Notice | Lead and Copper Rule | — | Resolved |
| September 1, 2019 – September 30, 2019 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| August 1, 2019 – August 31, 2019 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| May 1, 2019 – May 31, 2019 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| February 1, 2019 – February 28, 2019 | Monitoring of Treatment (SWTR-Unfilt/GWR) | Groundwater Rule | — | Resolved |
| July 1, 2018 – September 9, 2018 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| September 10, 2016 – July 14, 2017 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- February 12, 2026State Public Notification requested1 linked violation
- February 12, 2026State Formal Notice of Violation issued5 linked violations
- February 12, 2026State Public Notification requested2 linked violations
- February 12, 2026State Public Notification requested2 linked violations
- February 12, 2026State Public Notification requested5 linked violations
- February 12, 2026State Public Notification requested1 linked violation
- February 12, 2026State Formal Notice of Violation issued2 linked violations
- January 6, 2026State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- January 6, 2026State Public Notification received5 linked violations
- January 6, 2026State Public Notification received2 linked violations
- January 6, 2026State Public Notification received4 linked violations
- January 6, 2026State Public Notification received1 linked violation
- January 6, 2026State Public Notification received2 linked violations
- November 4, 2024State Public Notification received4 linked violations
- October 12, 2024State Public Notification requested1 linked violation
- October 12, 2024State Formal Notice of Violation issued1 linked violation
- August 16, 2024State Formal Notice of Violation issued1 linked violation
- August 7, 2024State Compliance achieved1 linked violation
- February 16, 2024State Formal Notice of Violation issued1 linked violation
- December 18, 2023State Compliance achieved1 linked violation
- December 18, 2023State Compliance achieved1 linked violation
- November 15, 2023State Formal Notice of Violation issued1 linked violation
- October 30, 2023State Public Notification received1 linked violation
- October 30, 2023State Public Notification received1 linked violation
- October 30, 2023State Compliance achieved1 linked violation
- October 30, 2023State Public Notification received1 linked violation
- October 30, 2023State Public Notification received1 linked violation
- October 27, 2023State Compliance achieved1 linked violation
- October 23, 2023State Compliance achieved1 linked violation
- October 23, 2023State Compliance achieved1 linked violation
- October 14, 2023State Public Notification requested1 linked violation
- October 14, 2023State Public Notification requested1 linked violation
- October 14, 2023State Formal Notice of Violation issued1 linked violation
- October 14, 2023State Public Notification requested1 linked violation
- October 14, 2023State Formal Notice of Violation issued1 linked violation
- October 14, 2023State Formal Notice of Violation issued1 linked violation
- September 30, 2023State Compliance achieved1 linked violation
- September 15, 2023State Formal Notice of Violation issued1 linked violation
- September 15, 2023State Public Notification requested1 linked violation
- June 1, 2023State Compliance achieved1 linked violation
- June 1, 2023State Compliance achieved1 linked violation
- December 22, 2022State Compliance achieved1 linked violation
- November 16, 2022State Formal Notice of Violation issued1 linked violation
- September 30, 2020State Compliance achieved1 linked violation
- July 31, 2020State Compliance achieved1 linked violation
- May 14, 2020State Compliance achieved1 linked violation
- May 14, 2020State Compliance achieved2 linked violations
- March 5, 2020State Public Notification received1 linked violation
- March 5, 2020State Public Notification received1 linked violation
- March 5, 2020State Public Notification received1 linked violation
- March 5, 2020State Public Notification received1 linked violation
- March 5, 2020State Public Notification received1 linked violation
- March 5, 2020State Public Notification received1 linked violation
- March 5, 2020State Public Notification received1 linked violation
- February 15, 2020State Formal Notice of Violation issued1 linked violation
- February 15, 2020State Formal Notice of Violation issued1 linked violation
- February 15, 2020State Public Notification requested1 linked violation
- February 15, 2020State Public Notification requested1 linked violation
- February 14, 2020State Formal Notice of Violation issued1 linked violation
- December 28, 2019State Formal Notice of Violation issued1 linked violation
- December 28, 2019State Public Notification requested1 linked violation
- November 20, 2019State Compliance achieved1 linked violation
- November 14, 2019State Formal Notice of Violation issued1 linked violation
- November 14, 2019State Public Notification requested1 linked violation
- November 13, 2019State Public Notification requested1 linked violation
- November 13, 2019State Formal Notice of Violation issued1 linked violation
- November 7, 2019State Compliance achieved3 linked violations
- October 11, 2019State Public Notification requested1 linked violation
- October 11, 2019State Formal Notice of Violation issued1 linked violation
- July 13, 2019State Formal Notice of Violation issued1 linked violation
- July 13, 2019State Public Notification requested1 linked violation
- June 19, 2019State Public Notification received1 linked violation
- June 18, 2019State Public Notification received1 linked violation
- June 18, 2019State Public Notification received1 linked violation
- June 18, 2019State Public Notification received1 linked violation
- June 18, 2019State Public Notification received1 linked violation
- June 18, 2019State Public Notification received1 linked violation
- June 11, 2019State Compliance achieved1 linked violation
- June 11, 2019State Compliance achieved1 linked violation
- May 14, 2019State Formal Notice of Violation issued1 linked violation
- May 14, 2019State Public Notification requested1 linked violation
- May 10, 2019State Compliance achieved2 linked violations
- April 11, 2019State Public Notification requested1 linked violation
- December 12, 2018State Formal Notice of Violation issued1 linked violation
- December 12, 2018State Formal Notice of Violation issued3 linked violations
- October 13, 2018State Formal Notice of Violation issued1 linked violation
- October 13, 2018State Formal Notice of Violation issued1 linked violation
- October 13, 2018State Public Notification requested2 linked violations
- October 13, 2018State Public Notification requested3 linked violations
- September 9, 2018State Compliance achieved4 linked violations
- August 28, 2018State Compliance achieved4 linked violations
- November 16, 2017State Formal Notice of Violation issued1 linked violation
- November 16, 2017State Public Notification requested2 linked violations
- November 16, 2017State Formal Notice of Violation issued1 linked violation
- November 16, 2017State Public Notification requested1 linked violation
- August 6, 2017State Compliance achieved1 linked violation
- July 18, 2017State Public Notification received1 linked violation
- July 18, 2017State Public Notification received1 linked violation
- July 18, 2017State Public Notification received1 linked violation
- July 18, 2017State Public Notification received1 linked violation
- July 18, 2017State Public Notification received1 linked violation
- July 14, 2017State Compliance achieved1 linked violation
- May 5, 2017State Public Notification requested1 linked violation
- May 5, 2017State Public Notification requested1 linked violation
- May 5, 2017State Formal Notice of Violation issued1 linked violation
- May 5, 2017State Formal Notice of Violation issued1 linked violation
- April 2, 2017State Compliance achieved2 linked violations
- February 11, 2017State Public Notification requested1 linked violation
- February 11, 2017State Formal Notice of Violation issued1 linked violation
- February 3, 2017State Formal Notice of Violation issued1 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 15, 2016State Public Notification requested1 linked violation
- October 8, 2016State Formal Notice of Violation issued1 linked violation
- May 31, 2016State Compliance achieved1 linked violation
- September 11, 2015State Public Notification requested1 linked violation
- September 11, 2015State Formal Notice of Violation issued1 linked violation
- August 31, 2015State Compliance achieved1 linked violation
- July 17, 2015State Formal Notice of Violation issued1 linked violation
- September 30, 2014State Compliance achieved2 linked violations
- May 15, 2014State Public Notification received1 linked violation
- May 15, 2014State Public Notification received1 linked violation
- May 15, 2014State Public Notification received1 linked violation
- May 15, 2014State Public Notification received1 linked violation
- May 15, 2014State Public Notification received1 linked violation
- May 15, 2014State Public Notification received1 linked violation
- May 1, 2014State Compliance achieved1 linked violation
- May 1, 2014State Compliance achieved1 linked violation
- April 2, 2014State Formal Notice of Violation issued1 linked violation
- March 10, 2014State Compliance achieved4 linked violations
- March 7, 2014State Formal Notice of Violation issued1 linked violation
- March 4, 2014State Formal Notice of Violation issued1 linked violation
- March 4, 2014State Formal Notice of Violation issued1 linked violation
- January 30, 2014State Public Notification requested1 linked violation
- January 30, 2014State Formal Notice of Violation issued1 linked violation
- January 15, 2014State Public Notification requested1 linked violation
- January 15, 2014State Formal Notice of Violation issued1 linked violation
- January 15, 2014State Public Notification requested1 linked violation
- January 15, 2014State Formal Notice of Violation issued1 linked violation
- January 1, 2014State Compliance achieved1 linked violation
- October 3, 2013State Formal Notice of Violation issued1 linked violation
- October 3, 2013State Formal Notice of Violation issued1 linked violation
- October 3, 2013State Public Notification requested1 linked violation
- September 27, 2013State Compliance achieved1 linked violation
- September 1, 2013State Compliance achieved1 linked violation
- April 3, 2013State Public Notification requested1 linked violation
- April 3, 2013State Formal Notice of Violation issued1 linked violation
- March 1, 2013State Compliance achieved1 linked violation
- February 7, 2013State Formal Notice of Violation issued1 linked violation
- February 7, 2013State Public Notification requested1 linked violation
- October 5, 2012State Formal Notice of Violation issued1 linked violation
- February 29, 2012State Compliance achieved1 linked violation
- February 9, 2012State Formal Notice of Violation issued1 linked violation
- October 15, 2008State Formal Notice of Violation issued2 linked violations
- October 7, 2008State Compliance achieved1 linked violation
- July 15, 2005State Compliance achieved3 linked violations
- May 4, 2002State Boil Water Order1 linked violation
Common questions
Is DAVY MUNICIPAL WATER WORKS required to publish a Consumer Confidence Report?
- Yes. DAVY MUNICIPAL WATER WORKS 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 DAVY MUNICIPAL WATER WORKS’s next Consumer Confidence Report due?
- DAVY MUNICIPAL WATER WORKS’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does DAVY MUNICIPAL WATER WORKS have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for DAVY MUNICIPAL WATER WORKS.
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
GENTRY, KENNETH M
304-656-7145
DAVY, WV 24828