HILLSBORO, WV · Pocahontas County
HILLSBORO TOWN OF Water System
Consumer Confidence Report status
HILLSBORO TOWN OF 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 4 items for HILLSBORO TOWN OF that are open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.
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)
- WV3303815
- System type
- Community Water System
- Population served
- 262
- Service connections
- 105
- Ownership
- privately owned
- Water source
- groundwater (wells)
HILLSBORO TOWN OF is one of 760 community water systems in West Virginia in the 500 or fewer people size category, serving 262 people from groundwater.
As of August 1, 2026, its federal record holds 11 entries between 2008 and 2022, of which 4 remain open; none are health-based.
Of the 11, 4 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 Public Notice Rule and Revised PN Rule, the Consumer Confidence Rule, and the Lead and Copper Rule.
Violation history
Consumer Confidence Report Complete Failure to Report
—Consumer Confidence Rule
July 1, 2022
UnaddressedPublic Notification Violation for NPDWR Violation
—Public Notice
November 14, 2021
UnaddressedPublic Notification Violation for NPDWR Violation
—Public Notice
November 14, 2020 – November 1, 2020
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
November 13, 2020
UnaddressedPublic Notification Violation for NPDWR Violation
—Public Notice
October 10, 2020
UnaddressedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 2020 – July 21, 2021
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
November 15, 2018 – February 5, 2019
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
February 16, 2014 – July 1, 2014
ResolvedMonitoring, Regular
—Benzo(a)pyrene
January 1, 2011 – December 31, 2013
ResolvedMonitoring, Routine Major (TCR)
—Coliform (TCR)
September 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Thallium, Total
January 1, 2008 – December 31, 2010
Resolved
Unaddressed no corrective action on record yetResolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| July 1, 2022 | Consumer Confidence Report Complete Failure to Report | Consumer Confidence Rule | — | Unaddressed |
| November 14, 2021 | Public Notification Violation for NPDWR Violation | Public Notice | — | Unaddressed |
| November 14, 2020 – November 1, 2020 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| November 13, 2020 | Public Notification Violation for NPDWR Violation | Public Notice | — | Unaddressed |
| October 10, 2020 | Public Notification Violation for NPDWR Violation | Public Notice | — | Unaddressed |
| October 1, 2020 – July 21, 2021 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| November 15, 2018 – February 5, 2019 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| February 16, 2014 – July 1, 2014 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| January 1, 2011 – December 31, 2013 | Monitoring, Regular | Benzo(a)pyrene | — | Resolved |
| September 1, 2010 – September 30, 2010 | Monitoring, Routine Major (TCR) | Coliform (TCR) | — | Resolved |
| January 1, 2008 – December 31, 2010 | Monitoring, Regular | Thallium, Total | — | Resolved |
Unaddressed no corrective action on record yetResolved addressed and confirmed by the state
Enforcement actions
- March 22, 2024State Public Notification received1 linked violation
- August 16, 2023State Public Notification requested2 linked violations
- August 10, 2023State Compliance achieved1 linked violation
- February 10, 2022State Public Notification received1 linked violation
- February 10, 2022State Compliance achieved2 linked violations
- January 10, 2022State Public Notification received1 linked violation
- December 16, 2021State Formal Notice of Violation issued2 linked violations
- December 16, 2021State Formal Notice of Violation issued2 linked violations
- November 24, 2021State Compliance achieved2 linked violations
- November 24, 2021State Compliance achieved3 linked violations
- November 12, 2021State Public Notification requested2 linked violations
- November 12, 2021State Public Notification requested2 linked violations
- July 21, 2021State Compliance achieved27 linked violations
- May 14, 2021State Compliance achieved1 linked violation
- May 14, 2021State Public Notification received2 linked violations
- May 14, 2021State Public Notification received2 linked violations
- May 14, 2021State Formal Notice of Violation issued1 linked violation
- March 12, 2021State Formal Notice of Violation issued2 linked violations
- January 16, 2021State Public Notification requested22 linked violations
- January 10, 2021State Compliance achieved1 linked violation
- December 16, 2020State Formal Notice of Violation issued3 linked violations
- December 16, 2020State Formal Notice of Violation issued3 linked violations
- November 14, 2020State Public Notification requested2 linked violations
- November 14, 2020State Public Notification requested1 linked violation
- November 14, 2020State Formal Notice of Violation issued2 linked violations
- November 14, 2020State Formal Notice of Violation issued1 linked violation
- November 14, 2020State Formal Notice of Violation issued1 linked violation
- November 14, 2020State Public Notification requested2 linked violations
- November 3, 2020State Compliance achieved1 linked violation
- November 3, 2020State Compliance achieved1 linked violation
- November 1, 2020State Compliance achieved2 linked violations
- November 1, 2020State Compliance achieved2 linked violations
- November 1, 2020State Compliance achieved2 linked violations
- October 16, 2020State Formal Notice of Violation issued1 linked violation
- February 24, 2020State Compliance achieved1 linked violation
- February 15, 2020State Public Notification requested2 linked violations
- February 15, 2020State Formal Notice of Violation issued1 linked violation
- February 15, 2020State Public Notification requested2 linked violations
- February 14, 2020State Formal Notice of Violation issued1 linked violation
- January 15, 2020State Public Notification requested2 linked violations
- January 15, 2020State Public Notification requested2 linked violations
- January 15, 2020State Formal Notice of Violation issued1 linked violation
- December 3, 2019State Compliance achieved4 linked violations
- November 15, 2019State Formal Notice of Violation issued2 linked violations
- November 14, 2019State Public Notification requested3 linked violations
- November 14, 2019State Formal Notice of Violation issued2 linked violations
- November 14, 2019State Formal Notice of Violation issued1 linked violation
- October 11, 2019State Formal Notice of Violation issued1 linked violation
- October 11, 2019State Formal Notice of Violation issued1 linked violation
- October 11, 2019State Public Notification requested1 linked violation
- October 11, 2019State Public Notification requested1 linked violation
- September 13, 2019State Formal Notice of Violation issued1 linked violation
- September 13, 2019State Public Notification requested1 linked violation
- September 10, 2019State Compliance achieved27 linked violations
- June 7, 2019State Public Notification received1 linked violation
- April 5, 2019State Public Notification received1 linked violation
- April 5, 2019State Public Notification received1 linked violation
- March 6, 2019State Public Notification received1 linked violation
- March 6, 2019State Public Notification received1 linked violation
- February 8, 2019State Public Notification received1 linked violation
- February 8, 2019State Public Notification received1 linked violation
- February 7, 2019State Formal Notice of Violation issued1 linked violation
- February 5, 2019State Compliance achieved1 linked violation
- February 5, 2019State Compliance achieved1 linked violation
- January 10, 2019State Formal Notice of Violation issued1 linked violation
- January 10, 2019State Public Notification requested1 linked violation
- January 8, 2019State Formal Notice of Violation issued1 linked violation
- December 18, 2018State Public Notification requested1 linked violation
- December 18, 2018State Formal Notice of Violation issued1 linked violation
- December 14, 2018State Public Notification requested1 linked violation
- December 14, 2018State Formal Notice of Violation issued1 linked violation
- December 6, 2018State Compliance achieved3 linked violations
- November 26, 2018State Compliance achieved2 linked violations
- November 13, 2018State Formal Notice of Violation issued1 linked violation
- November 13, 2018State Public Notification requested1 linked violation
- November 13, 2018State Public Notification requested1 linked violation
- November 13, 2018State Formal Notice of Violation issued1 linked violation
- October 1, 2018State Public Notification received1 linked violation
- August 14, 2018State Public Notification requested1 linked violation
- August 14, 2018State Formal Notice of Violation issued1 linked violation
- August 7, 2018State Compliance achieved1 linked violation
- June 5, 2018State Compliance achieved1 linked violation
- April 2, 2018State Public Notification received1 linked violation
- April 1, 2018State Compliance achieved1 linked violation
- April 1, 2018State Compliance achieved1 linked violation
- March 30, 2018State Compliance achieved1 linked violation
- March 10, 2018State Formal Notice of Violation issued1 linked violation
- January 24, 2018State Formal Notice of Violation issued1 linked violation
- January 10, 2018State Public Notification requested1 linked violation
- January 10, 2018State Formal Notice of Violation issued1 linked violation
- December 9, 2017State Public Notification requested1 linked violation
- December 9, 2017State Formal Notice of Violation issued1 linked violation
- November 15, 2017State Public Notification requested1 linked violation
- November 15, 2017State Formal Notice of Violation issued1 linked violation
- November 13, 2017State Compliance achieved1 linked violation
- November 9, 2017State Formal Notice of Violation issued1 linked violation
- November 7, 2017State Compliance achieved1 linked violation
- February 3, 2017State Formal Notice of Violation issued1 linked violation
- August 29, 2016State Compliance achieved1 linked violation
- January 19, 2016State Compliance achieved1 linked violation
- January 9, 2016State Formal Notice of Violation issued1 linked violation
- January 7, 2016State Public Notification received1 linked violation
- December 28, 2015State Compliance achieved2 linked violations
- December 9, 2015State Formal Notice of Violation issued1 linked violation
- December 9, 2015State Formal Notice of Violation issued1 linked violation
- November 12, 2015State Public Notification requested1 linked violation
- November 12, 2015State Formal Notice of Violation issued1 linked violation
- September 14, 2015State Intentional no-action2 linked violations
- August 24, 2015State Compliance achieved1 linked violation
- August 13, 2015State Compliance achieved1 linked violation
- July 30, 2015State Formal Notice of Violation issued1 linked violation
- July 28, 2015State Compliance achieved1 linked violation
- July 16, 2015State Formal Notice of Violation issued1 linked violation
- November 6, 2014State Formal Notice of Violation issued1 linked violation
- July 1, 2014State Public Notification received1 linked violation
- July 1, 2014State Public Notification received2 linked violations
- July 1, 2014State Compliance achieved32 linked violations
- July 1, 2014State Public Notification received1 linked violation
- July 1, 2014State Public Notification received1 linked violation
- March 20, 2014State Compliance achieved17 linked violations
- March 14, 2014State Formal Notice of Violation issued1 linked violation
- March 11, 2014State Compliance achieved2 linked violations
- February 14, 2014State Formal Notice of Violation issued17 linked violations
- February 14, 2014State Formal Notice of Violation issued1 linked violation
- February 14, 2014State Public Notification requested1 linked violation
- February 14, 2014State Formal Notice of Violation issued1 linked violation
- February 14, 2014State Public Notification requested1 linked violation
- February 1, 2014State Formal Notice of Violation issued1 linked violation
- February 1, 2014State Public Notification requested1 linked violation
- January 7, 2014State Compliance achieved1 linked violation
- October 18, 2013State Formal Notice of Violation issued1 linked violation
- February 16, 2013State Formal Notice of Violation issued1 linked violation
- February 16, 2013State Public Notification requested1 linked violation
- September 5, 2012State Public Notification requested1 linked violation
- September 5, 2012State Formal Notice of Violation issued1 linked violation
- August 7, 2012State Compliance achieved1 linked violation
- July 1, 2012State Compliance achieved1 linked violation
- June 7, 2012State Public Notification received1 linked violation
- June 7, 2012State Public Notification received1 linked violation
- June 7, 2012State Compliance achieved1 linked violation
- May 30, 2012State Public Notification received1 linked violation
- April 11, 2012State Formal Notice of Violation issued1 linked violation
- February 21, 2012State Compliance achieved3 linked violations
- February 10, 2012State Formal Notice of Violation issued1 linked violation
- January 11, 2012State Formal Notice of Violation issued1 linked violation
- January 4, 2012State Formal Notice of Violation issued1 linked violation
- December 8, 2011State Public Notification requested1 linked violation
- December 8, 2011State Formal Notice of Violation issued1 linked violation
- November 28, 2011State Public Notification received5 linked violations
- November 28, 2011State Compliance achieved1 linked violation
- November 28, 2011State Public Notification received11 linked violations
- August 23, 2011State Compliance achieved1 linked violation
- August 16, 2011State Formal Notice of Violation issued1 linked violation
- August 5, 2011State Formal Notice of Violation issued1 linked violation
- May 3, 2011State Compliance achieved12 linked violations
- April 5, 2011State Compliance achieved1 linked violation
- March 23, 2011State Public Notification requested1 linked violation
- March 23, 2011State Formal Notice of Violation issued1 linked violation
- March 1, 2011State Compliance achieved1 linked violation
- February 2, 2011State Public Notification requested1 linked violation
- February 2, 2011State Public Notification requested11 linked violations
- February 2, 2011State Formal Notice of Violation issued11 linked violations
- February 2, 2011State Formal Notice of Violation issued1 linked violation
- January 27, 2011State Public Notification requested1 linked violation
- January 27, 2011State Formal Notice of Violation issued1 linked violation
- November 5, 2010State Public Notification requested1 linked violation
- November 5, 2010State Formal Notice of Violation issued1 linked violation
- October 26, 2010State Public Notification requested1 linked violation
- October 26, 2010State Formal Notice of Violation issued1 linked violation
- October 12, 2010State Compliance achieved1 linked violation
- October 1, 2010State Compliance achieved1 linked violation
- April 16, 2010State Public Notification requested1 linked violation
- April 16, 2010State Formal Notice of Violation issued1 linked violation
- January 15, 2010State Compliance achieved1 linked violation
- May 8, 2007State Public Notification received2 linked violations
- February 24, 2007State Public Notification requested1 linked violation
- February 24, 2007State Formal Notice of Violation issued22 linked violations
- February 6, 2007State Compliance achieved1 linked violation
- May 2, 2005State Compliance achieved5 linked violations
- June 8, 2004State Public Notification received2 linked violations
- March 4, 2004State Public Notification requested2 linked violations
- October 8, 2003State Formal Notice of Violation issued3 linked violations
- February 15, 2003State Public Notification requested1 linked violation
- February 15, 2003State Formal Notice of Violation issued1 linked violation
- February 1, 2003State Compliance achieved1 linked violation
- August 22, 2002State Public Notification requested1 linked violation
- August 22, 2002State Formal Notice of Violation issued1 linked violation
- July 19, 2001State Compliance achieved1 linked violation
- January 22, 2001State Formal Notice of Violation issued1 linked violation
- January 1, 2001State Compliance achieved2 linked violations
- June 21, 2000State Formal Notice of Violation issued2 linked violations
- June 15, 2000State Compliance achieved3 linked violations
Common questions
Is HILLSBORO TOWN OF required to publish a Consumer Confidence Report?
- Yes. HILLSBORO TOWN OF 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 HILLSBORO TOWN OF’s next Consumer Confidence Report due?
- HILLSBORO TOWN OF’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does HILLSBORO TOWN OF have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show 4 items for HILLSBORO TOWN OF that are open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.
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
SIERS, GAIL
304-653-4005
HILLSBORO, WV 24946