ISLE OF WIGHT, VA · Isle of Wight County
CARRSVILLE Water System
Consumer Confidence Report status
CARRSVILLE 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 1 item for CARRSVILLE that is 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 Virginia’s official records. Always confirm current status with Virginia before making decisions based on this information.
System facts
- System ID (PWSID)
- VA3093170
- System type
- Community Water System
- Population served
- 313
- Service connections
- 126
- Ownership
- privately owned
- Water source
- groundwater (wells)
CARRSVILLE is one of 2,163 community water systems in Virginia in the 500 or fewer people size category, serving 313 people from groundwater.
As of August 1, 2026, its federal record holds 25 entries between 1991 and 2025, of which 1 remains open; none are health-based.
Of the 25, 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 inorganic chemicals, the Total Coliform Rules, and the Lead and Copper Rule.
Violation history
Notification, Known or Potential LSL
—LEAD AND COPPER RULE REVISIONS
July 2, 2025
UnaddressedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
October 1, 2014 – October 31, 2014
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
August 1, 2013 – August 31, 2013
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
July 1, 2011 – July 31, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
October 1, 2007 – December 31, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
April 1, 2007 – June 30, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
January 1, 2007 – March 31, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
October 1, 2006 – December 31, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
April 1, 2006 – June 30, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
January 1, 2006 – March 31, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
October 1, 2005 – December 31, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
July 1, 2005 – September 30, 2005
ResolvedMonitoring, Regular
—Fluoride
April 1, 2005 – June 30, 2005
ResolvedMonitoring, Regular
—Fluoride
January 1, 2005 – March 31, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
October 1, 2004 – December 31, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
July 1, 2004 – September 30, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
April 1, 2004 – June 30, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
January 1, 2004 – March 31, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
October 1, 2003 – December 31, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
July 1, 2003 – September 30, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
January 1, 2003 – March 31, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
July 1, 2002 – September 30, 2002
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
January 1, 2002 – March 31, 2002
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
January 1, 2001 – December 31, 2001
ResolvedMonitoring, Routine Minor (TCR)
—Coliform (TCR)
November 1, 1991 – November 30, 1991
Archived
Unaddressed no corrective action on record yetResolved 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 |
|---|---|---|---|---|
| July 2, 2025 | Notification, Known or Potential LSL | LEAD AND COPPER RULE REVISIONS | — | Unaddressed |
| October 1, 2014 – October 31, 2014 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| August 1, 2013 – August 31, 2013 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| July 1, 2011 – July 31, 2011 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| October 1, 2007 – December 31, 2007 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| April 1, 2007 – June 30, 2007 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| January 1, 2007 – March 31, 2007 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| October 1, 2006 – December 31, 2006 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| April 1, 2006 – June 30, 2006 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| January 1, 2006 – March 31, 2006 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| October 1, 2005 – December 31, 2005 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| July 1, 2005 – September 30, 2005 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| April 1, 2005 – June 30, 2005 | Monitoring, Regular | Fluoride | — | Resolved |
| January 1, 2005 – March 31, 2005 | Monitoring, Regular | Fluoride | — | Resolved |
| October 1, 2004 – December 31, 2004 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| July 1, 2004 – September 30, 2004 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| April 1, 2004 – June 30, 2004 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| January 1, 2004 – March 31, 2004 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| October 1, 2003 – December 31, 2003 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| July 1, 2003 – September 30, 2003 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| January 1, 2003 – March 31, 2003 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| July 1, 2002 – September 30, 2002 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| January 1, 2002 – March 31, 2002 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| January 1, 2001 – December 31, 2001 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| November 1, 1991 – November 30, 1991 | Monitoring, Routine Minor (TCR) | Coliform (TCR) | — | Archived |
Unaddressed no corrective action on record yetResolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- January 16, 2026State Formal Notice of Violation issued2 linked violations
- December 1, 2014State Public Notification requested2 linked violations
- October 1, 2013State Public Notification received2 linked violations
- September 24, 2013State Compliance achieved2 linked violations
- September 23, 2013State Public Notification requested2 linked violations
- February 8, 2012State Public Notification received2 linked violations
- August 3, 2011State Public Notification requested2 linked violations
- January 1, 2009State Compliance achieved29 linked violations
- July 24, 2008State Formal Notice of Violation issued2 linked violations
- July 24, 2008State Public Notification requested2 linked violations
- February 13, 2008State Public Notification requested3 linked violations
- May 3, 2007State Public Notification requested4 linked violations
- May 3, 2007State Formal Notice of Violation issued3 linked violations
- May 3, 2006State Public Notification received2 linked violations
- January 26, 2006State Formal Notice of Violation issued1 linked violation
- December 29, 2005State Public Notification requested3 linked violations
- September 15, 2005State Public Notification received1 linked violation
- August 3, 2005State Formal Notice of Violation issued1 linked violation
- May 9, 2005State Public Notification requested1 linked violation
- April 12, 2005State Public Notification received2 linked violations
- February 10, 2005State Formal Notice of Violation issued31 linked violations
- October 1, 2004State Public Notification received4 linked violations
- August 31, 2004State Formal Notice of Violation issued23 linked violations
- March 31, 2004State Public Notification received3 linked violations
- February 26, 2004State Public Notification requested3 linked violations
- February 26, 2004State Formal Notice of Violation issued24 linked violations
- November 6, 2003State Formal Notice of Violation issued16 linked violations
- September 8, 2003State Formal Notice of Violation issued9 linked violations
- June 10, 2003State Public Notification requested7 linked violations
- April 1, 2003State Bilateral Compliance Agreement signed26 linked violations
- December 31, 2002State Public Notification received26 linked violations
- October 30, 2002State Public Notification requested2 linked violations
- August 28, 1990State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- August 28, 1990State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
Common questions
Is CARRSVILLE required to publish a Consumer Confidence Report?
- Yes. CARRSVILLE 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 CARRSVILLE’s next Consumer Confidence Report due?
- CARRSVILLE’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does CARRSVILLE have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show 1 item for CARRSVILLE that is 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
GWALTNEY, JONATHAN H.
757-357-4843
ISLE OF WIGHT, VA 23397