SMITHFIELD, VA · Isle of Wight County

JAMES RIVER SHORES Water System

Inactive system

This water system is marked inactive in EPA’s federal records as of June 19, 2012. It is no longer an operating public water system under this PWSID, and no compliance deadlines — including the 2027 Consumer Confidence Report rule — apply to it.

If you are a resident looking for your current water provider, see water systems in Isle of Wight County, VA.

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): VA3093319
System type: Community Water System
Population served: 132
Service connections: 35
Ownership: privately owned
Water source: groundwater (wells)

JAMES RIVER SHORES is one of 2,163 community water systems in Virginia in the 500 or fewer people size category, formerly serving 132 people from groundwater.

EPA's federal records list this system as inactive in 2012; the record below is historical.

As of August 1, 2026, its federal record holds 17 entries between 1995 and 2011, all of which EPA lists as closed. Nothing has been added since 2011.

Of the 17, 1 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 and the Lead and Copper Rule.

Violation history

Maximum Contaminant Level Violation, Average
Health-based
Fluoride
April 1, 2011 – June 30, 2011
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
January 1, 2010 – March 31, 2010
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
October 1, 2009 – December 31, 2009
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
April 1, 2009 – June 30, 2009
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
January 1, 2009 – March 31, 2009
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
October 1, 2008 – December 31, 2008
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
April 1, 2008 – June 30, 2008
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
January 1, 2008 – March 31, 2008
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
July 1, 2007 – September 30, 2007
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
April 1, 2007 – June 30, 2007
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
January 1, 2007 – March 31, 2007
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
October 1, 2003 – December 31, 2003
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
October 1, 2002 – December 31, 2002
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
April 1, 2002 – June 30, 2002
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
January 1, 2002 – March 31, 2002
Archived
Maximum Contaminant Level Violation, Average
Health-based
Fluoride
January 1, 2001 – December 31, 2001
Archived
Follow-up Or Routine LCR Tap M/R
—
Lead and Copper Rule
October 1, 1995 – February 2, 1996
Resolved

Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
April 1, 2011 – June 30, 2011	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
January 1, 2010 – March 31, 2010	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
October 1, 2009 – December 31, 2009	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
April 1, 2009 – June 30, 2009	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
January 1, 2009 – March 31, 2009	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
October 1, 2008 – December 31, 2008	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
April 1, 2008 – June 30, 2008	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
January 1, 2008 – March 31, 2008	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
July 1, 2007 – September 30, 2007	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
April 1, 2007 – June 30, 2007	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
January 1, 2007 – March 31, 2007	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
October 1, 2003 – December 31, 2003	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
October 1, 2002 – December 31, 2002	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
April 1, 2002 – June 30, 2002	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
January 1, 2002 – March 31, 2002	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
January 1, 2001 – December 31, 2001	Maximum Contaminant Level Violation, Average	Fluoride	Health-based	Archived
October 1, 1995 – February 2, 1996	Follow-up Or Routine LCR Tap M/R	Lead and Copper Rule	—	Resolved

Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state

Enforcement actions

September 20, 2011State Public Notification received1 linked violation
August 18, 2011State Public Notification requested1 linked violation
August 18, 2011State Formal Notice of Violation issued1 linked violation
June 30, 2011State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
May 26, 2011State Public Notification requested1 linked violation
May 26, 2011State Formal Notice of Violation issued1 linked violation
May 10, 2011State Public Notification received1 linked violation
March 22, 2011State Formal Notice of Violation issued1 linked violation
March 22, 2011State Public Notification requested1 linked violation
March 7, 2011State Public Notification received1 linked violation
January 5, 2011State Public Notification received1 linked violation
December 21, 2010State Formal Notice of Violation issued1 linked violation
December 21, 2010State Formal Notice of Violation issued1 linked violation
December 21, 2010State Public Notification requested1 linked violation
December 21, 2010State Public Notification requested1 linked violation
November 3, 2010State Public Notification received1 linked violation
June 16, 2010State Public Notification received1 linked violation
June 10, 2010State Formal Notice of Violation issued1 linked violation
June 10, 2010State Public Notification requested1 linked violation
March 1, 2010State Public Notification received1 linked violation
February 16, 2010State Public Notification requested1 linked violation
February 16, 2010State Formal Notice of Violation issued1 linked violation
February 16, 2010State Public Notification requested1 linked violation
February 16, 2010State Formal Notice of Violation issued1 linked violation
February 16, 2010State Formal Notice of Violation issued1 linked violation
February 16, 2010State Public Notification requested1 linked violation
February 16, 2010State Formal Notice of Violation issued1 linked violation
February 16, 2010State Public Notification requested1 linked violation
September 1, 2009State Public Notification received1 linked violation
August 13, 2009State Public Notification requested1 linked violation
August 13, 2009State Formal Notice of Violation issued1 linked violation
May 4, 2009State Public Notification received1 linked violation
May 4, 2009State Public Notification requested1 linked violation
May 4, 2009State Formal Notice of Violation issued1 linked violation
March 3, 2009State Public Notification received1 linked violation
February 10, 2009State Formal Notice of Violation issued1 linked violation
February 10, 2009State Public Notification requested1 linked violation
January 1, 2009State Public Notification received1 linked violation
June 24, 2008State Public Notification received170 linked violations
April 18, 2008State Public Notification received3 linked violations
February 13, 2008State Public Notification requested42 linked violations
February 13, 2008State Formal Notice of Violation issued3 linked violations
March 12, 2007Federal Final Administrative Order issued22 linked violations
November 8, 2006Federal issued Formal Notice of Violation20 linked violations
April 14, 2006State Public Notification requested10 linked violations
February 10, 2005State Public Notification requested6 linked violations
August 31, 2004State Public Notification requested13 linked violations
July 19, 2004State Public Notification received6 linked violations
September 8, 2003State Formal Notice of Violation issued2 linked violations
May 1, 2002State Public Notification received4 linked violations
March 1, 2002State Public Notification received9 linked violations
February 27, 2001State Formal Notice of Violation issued3 linked violations
February 27, 2001State Public Notification requested2 linked violations
February 2, 1996State Violation/Reminder Notice2 linked violations
February 2, 1996State Compliance achieved2 linked violations
April 20, 1990State Public Notification requestedgeneral compliance action — not tied to a specific violation on record

Last known contact on file (system is inactive)

KELLOGG, C. RAY

757-357-4105

SMITHFIELD, VA 23430