Is RALEIGH COUNTY PSD ARNETT required to publish a Consumer Confidence Report?

Yes. RALEIGH COUNTY PSD ARNETT 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 RALEIGH COUNTY PSD ARNETT’s next Consumer Confidence Report due?

RALEIGH COUNTY PSD ARNETT’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.

WV · Raleigh County

RALEIGH COUNTY PSD ARNETT Water System

Consumer Confidence Report status

RALEIGH COUNTY PSD ARNETT 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 RALEIGH COUNTY PSD ARNETT.

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): WV3304140
System type: Community Water System
Population served: 6,663
Service connections: 2,964
Ownership: local government
Water source: surface water (rivers, lakes, or reservoirs)

RALEIGH COUNTY PSD ARNETT is one of 90 community water systems in West Virginia in the 3,301 to 10,000 people size category, serving 6,663 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

December 11, 2025State Formal Notice of Violation issued1 linked violation
October 27, 2025State Public Notification received1 linked violation
October 8, 2025State no longer subject to Rulegeneral compliance action — not tied to a specific violation on record
October 7, 2025State Public Notification requested1 linked violation
October 7, 2025State Public Notification requested1 linked violation
October 7, 2025State Formal Notice of Violation issued1 linked violation
October 7, 2025State Formal Notice of Violation issued1 linked violation
June 25, 2025State Public Notification received1 linked violation
June 25, 2025State Public Notification received1 linked violation
May 30, 2025State Public Notification requested1 linked violation
May 30, 2025State Public Notification requested1 linked violation
May 30, 2025State Formal Notice of Violation issued1 linked violation
May 30, 2025State Formal Notice of Violation issued1 linked violation
May 14, 2025State Formal Notice of Violation issued1 linked violation
May 14, 2025State Formal Notice of Violation issued1 linked violation
April 3, 2025State Public Notification received1 linked violation
April 3, 2025State Public Notification received1 linked violation
April 2, 2025State Compliance achieved1 linked violation
March 28, 2025State Formal Notice of Violation issued1 linked violation
March 28, 2025State Public Notification requested1 linked violation
March 14, 2025State no longer subject to Rulegeneral compliance action — not tied to a specific violation on record
February 21, 2025State Public Notification requested1 linked violation
February 21, 2025State Formal Notice of Violation issued1 linked violation
December 23, 2024State Public Notification received1 linked violation
December 23, 2024State Compliance achieved1 linked violation
December 23, 2024State Public Notification received1 linked violation
December 12, 2024State Formal Notice of Violation issued1 linked violation
December 12, 2024State Public Notification requested1 linked violation
December 12, 2024State Formal Notice of Violation issued1 linked violation
December 12, 2024State Public Notification requested1 linked violation
November 15, 2024State Formal Notice of Violation issued1 linked violation
September 23, 2024State Public Notification received1 linked violation
September 5, 2024State Formal Notice of Violation issued1 linked violation
September 5, 2024State Public Notification requested1 linked violation
August 19, 2024State Compliance achieved1 linked violation
August 16, 2024State Formal Notice of Violation issued1 linked violation
June 30, 2023State Public Notification received1 linked violation
June 9, 2023State Formal Notice of Violation issued1 linked violation
June 9, 2023State Public Notification requested1 linked violation
March 27, 2023State Public Notification received1 linked violation
March 16, 2023State Formal Notice of Violation issued1 linked violation
March 16, 2023State Public Notification requested1 linked violation
June 16, 2017State Formal Notice of Violation issued1 linked violation
June 16, 2017State Public Notification requested1 linked violation
February 9, 2016State Public Notification received1 linked violation
August 11, 2015State Public Notification received1 linked violation
August 3, 2015State Compliance achieved1 linked violation
July 9, 2015State Public Notification requested1 linked violation
July 9, 2015State Formal Notice of Violation issued1 linked violation
June 17, 2015State Compliance achieved1 linked violation
November 12, 2014State Public Notification requested1 linked violation
November 12, 2014State Formal Notice of Violation issued1 linked violation
July 21, 2014State Public Notification received1 linked violation
July 21, 2014State Public Notification received1 linked violation
July 16, 2014State Public Notification requested1 linked violation
July 16, 2014State Formal Notice of Violation issued1 linked violation
July 8, 2014State Formal Notice of Violation issued1 linked violation
July 8, 2014State Public Notification requested1 linked violation
June 1, 2014State Compliance achieved2 linked violations
April 7, 2008State Boil Water Ordergeneral compliance action — not tied to a specific violation on record
February 27, 2008State Boil Water Ordergeneral compliance action — not tied to a specific violation on record
May 31, 2007State Boil Water Ordergeneral compliance action — not tied to a specific violation on record
January 28, 2003State Boil Water Ordergeneral compliance action — not tied to a specific violation on record
April 15, 1997State Compliance achieved3 linked violations
April 18, 1995Federal Compliance achievedgeneral compliance action — not tied to a specific violation on record
April 5, 1995Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record

Common questions

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