WV · Logan County
LOGAN CO P S D - CRAWLEY CREEK Water System
Consumer Confidence Report status
LOGAN CO P S D - CRAWLEY CREEK 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 LOGAN CO P S D - CRAWLEY CREEK.
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)
- WV3302363
- System type
- Community Water System
- Population served
- 2,145
- Service connections
- 937
- Ownership
- local government
- Water source
- surface water (rivers, lakes, or reservoirs)
LOGAN CO P S D - CRAWLEY CREEK is one of 335 community water systems in West Virginia in the 501 to 3,300 people size category, serving 2,145 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
- January 21, 2026State Compliance achieved1 linked violation
- January 21, 2026State Compliance achieved2 linked violations
- January 21, 2026State Compliance achieved1 linked violation
- January 21, 2026State Compliance achieved2 linked violations
- January 21, 2026State Compliance achieved1 linked violation
- January 21, 2026State Compliance achieved1 linked violation
- September 13, 2025State Formal Notice of Violation issued1 linked violation
- August 13, 2025State Formal Notice of Violation issued1 linked violation
- August 13, 2025State Formal Notice of Violation issued1 linked violation
- August 13, 2025State Formal Notice of Violation issued1 linked violation
- July 12, 2025State Formal Notice of Violation issued1 linked violation
- July 12, 2025State Public Notification requested1 linked violation
- July 12, 2025State Formal Notice of Violation issued1 linked violation
- July 12, 2025State Public Notification requested1 linked violation
- June 12, 2025State Formal Notice of Violation issued1 linked violation
- June 12, 2025State Public Notification requested1 linked violation
- June 12, 2025State Formal Notice of Violation issued1 linked violation
- June 12, 2025State Formal Notice of Violation issued1 linked violation
- June 12, 2025State Public Notification requested1 linked violation
- June 12, 2025State Public Notification requested1 linked violation
- May 13, 2025State Public Notification requested1 linked violation
- May 13, 2025State Formal Notice of Violation issued1 linked violation
- May 1, 2025State Compliance achieved1 linked violation
- January 29, 2025State Compliance achieved1 linked violation
- November 15, 2024State Formal Notice of Violation issued1 linked violation
- October 1, 2024State Compliance achieved1 linked violation
- August 14, 2024State Formal Notice of Violation issued1 linked violation
- June 22, 2021State Compliance achieved1 linked violation
- January 7, 2021State Formal Notice of Violation issued1 linked violation
- November 14, 2020State Public Notification requested2 linked violations
- November 14, 2020State Formal Notice of Violation issued1 linked violation
- November 14, 2020State Formal Notice of Violation issued2 linked violations
- November 14, 2020State Public Notification requested1 linked violation
- October 7, 2020State Compliance achieved2 linked violations
- October 6, 2020State Compliance achieved1 linked violation
- February 15, 2020State Formal Notice of Violation issued1 linked violation
- November 27, 2019State Compliance achieved1 linked violation
- August 15, 2019State Formal Notice of Violation issued1 linked violation
- February 15, 2019State Formal Notice of Violation issued1 linked violation
- February 15, 2019State Formal Notice of Violation issued1 linked violation
- November 16, 2018State Formal Notice of Violation issued1 linked violation
- November 16, 2018State Formal Notice of Violation issued1 linked violation
- October 30, 2018State Compliance achieved1 linked violation
- September 27, 2018State Formal Notice of Violation issued1 linked violation
- September 27, 2018State Public Notification requested1 linked violation
- May 3, 2018State Formal Notice of Violation issued1 linked violation
- November 30, 2017State Compliance achieved1 linked violation
- October 4, 2017State Compliance achieved1 linked violation
- August 2, 2017State Formal Notice of Violation issued1 linked violation
- May 13, 2017State Formal Notice of Violation issued1 linked violation
- January 23, 2017State Public Notification received1 linked violation
- January 23, 2017State Public Notification received1 linked violation
- January 23, 2017State Public Notification received1 linked violation
- January 19, 2017State Compliance achieved1 linked violation
- January 19, 2017State Compliance achieved1 linked violation
- August 13, 2016State Formal Notice of Violation issued1 linked violation
- July 7, 2016State Compliance achieved1 linked violation
- June 18, 2016State Formal Notice of Violation issued1 linked violation
- March 4, 2016State Formal Notice of Violation issued1 linked violation
- November 30, 2015State Compliance achieved1 linked violation
- October 22, 2015State Formal Notice of Violation issued1 linked violation
- February 13, 2015State Formal Notice of Violation issued1 linked violation
- October 22, 2014State Compliance achieved1 linked violation
- October 18, 2014State Formal Notice of Violation issued1 linked violation
- October 5, 2013State Formal Notice of Violation issued1 linked violation
- October 4, 2013State Compliance achieved1 linked violation
- August 10, 2012State Formal Notice of Violation issued1 linked violation
- July 28, 2011State Public Notification requested1 linked violation
- July 28, 2011State Formal Notice of Violation issued1 linked violation
- July 11, 2011State Compliance achieved1 linked violation
- October 15, 2010State Formal Notice of Violation issued1 linked violation
- October 4, 2010State Compliance achieved4 linked violations
- May 6, 2009State Boil Water Ordergeneral compliance action — not tied to a specific violation on record
- June 17, 2003State Boil Water Order1 linked violation
Common questions
Is LOGAN CO P S D - CRAWLEY CREEK required to publish a Consumer Confidence Report?
- Yes. LOGAN CO P S D - CRAWLEY CREEK 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 LOGAN CO P S D - CRAWLEY CREEK’s next Consumer Confidence Report due?
- LOGAN CO P S D - CRAWLEY CREEK’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does LOGAN CO P S D - CRAWLEY CREEK have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for LOGAN CO P S D - CRAWLEY CREEK.
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