ISLE OF WIGHT, VA · Isle of Wight County
SMITHFIELD HEIGHTS/SANDY MOUNT MANOR Water System
Consumer Confidence Report status
SMITHFIELD HEIGHTS/SANDY MOUNT MANOR 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 2 items for SMITHFIELD HEIGHTS/SANDY MOUNT MANOR 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 Virginia’s official records. Always confirm current status with Virginia before making decisions based on this information.
System facts
- System ID (PWSID)
- VA3093580
- System type
- Community Water System
- Population served
- 475
- Service connections
- 190
- Ownership
- privately owned
- Water source
- groundwater (wells)
SMITHFIELD HEIGHTS/SANDY MOUNT MANOR is one of 2,163 community water systems in Virginia in the 500 or fewer people size category, serving 475 people from groundwater.
As of August 1, 2026, its federal record holds 32 entries between 1979 and 2026, of which 2 remain open; none are health-based.
Of the 32, 7 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
Report Sample Result/Fail Monitor (RTCR)
—Revised Total Coliform Rule
January 1, 2026 – February 24, 2026
ResolvedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 2025
UnaddressedNotification, Known or Potential LSL
—LEAD AND COPPER RULE REVISIONS
July 2, 2025
UnaddressedMaximum Contaminant Level Violation, Average
Health-basedFluoride
April 1, 2009 – June 30, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
July 1, 2008 – September 30, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
January 1, 2008 – March 31, 2008
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
July 1, 2006 – September 30, 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
July 1, 2005 – September 30, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
April 1, 2005 – June 30, 2005
ResolvedMonitoring, Regular
—Fluoride
April 1, 2005 – June 30, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
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
April 1, 2003 – June 30, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
January 1, 2003 – March 31, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
October 1, 2002 – December 31, 2002
ResolvedMonitoring, Routine Minor (TCR)
—Coliform (TCR)
September 1, 2002 – September 30, 2002
ArchivedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
August 1, 2002 – August 31, 2002
ArchivedMaximum Contaminant Level Violation, Average
Health-basedFluoride
July 1, 2002 – September 30, 2002
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
April 1, 2002 – June 30, 2002
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
January 1, 2002 – March 31, 2002
ResolvedMonitoring, Routine Minor (TCR)
—Coliform (TCR)
June 1, 1997 – June 30, 1997
ArchivedMaximum Contaminant Level Violation, Single Sample
Health-basedFluoride
March 11, 1981 – May 10, 1981
ArchivedMonitoring, Check/Repeat/Confirmation
—Fluoride
June 24, 1979 – July 23, 1979
Archived
Resolved addressed and confirmed by the stateUnaddressed no corrective action on record yetArchived closed in EPA's records (typically due to age or a data correction)
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2026 – February 24, 2026 | Report Sample Result/Fail Monitor (RTCR) | Revised Total Coliform Rule | — | Resolved |
| October 1, 2025 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Unaddressed |
| July 2, 2025 | Notification, Known or Potential LSL | LEAD AND COPPER RULE REVISIONS | — | Unaddressed |
| April 1, 2009 – June 30, 2009 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| July 1, 2008 – September 30, 2008 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| January 1, 2008 – March 31, 2008 | Maximum Contaminant Level Violation, Average | Fluoride | 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 |
| July 1, 2006 – September 30, 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 |
| July 1, 2005 – September 30, 2005 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| April 1, 2005 – June 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 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | 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 |
| April 1, 2003 – June 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 |
| October 1, 2002 – December 31, 2002 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| September 1, 2002 – September 30, 2002 | Monitoring, Routine Minor (TCR) | Coliform (TCR) | — | Archived |
| August 1, 2002 – August 31, 2002 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
| July 1, 2002 – September 30, 2002 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| April 1, 2002 – June 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 |
| June 1, 1997 – June 30, 1997 | Monitoring, Routine Minor (TCR) | Coliform (TCR) | — | Archived |
| March 11, 1981 – May 10, 1981 | Maximum Contaminant Level Violation, Single Sample | Fluoride | Health-based | Archived |
| June 24, 1979 – July 23, 1979 | Monitoring, Check/Repeat/Confirmation | Fluoride | — | Archived |
Resolved addressed and confirmed by the stateUnaddressed no corrective action on record yetArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- March 17, 2026State Public Notification requested1 linked violation
- March 17, 2026State Formal Notice of Violation issued1 linked violation
- March 5, 2026State Public Notification requested1 linked violation
- March 5, 2026State Formal Notice of Violation issued1 linked violation
- February 24, 2026State Compliance achieved1 linked violation
- January 16, 2026State Formal Notice of Violation issued1 linked violation
- January 16, 2026State Public Notification requested1 linked violation
- November 15, 2009State Compliance achieved1 linked violation
- September 15, 2009State Public Notification received1 linked violation
- June 5, 2009State Public Notification received1 linked violation
- May 24, 2009State Compliance achieved1 linked violation
- May 19, 2009State Public Notification requested1 linked violation
- May 19, 2009State Formal Notice of Violation issued1 linked violation
- January 1, 2009State Compliance achieved27 linked violations
- November 25, 2008State Formal Notice of Violation issued1 linked violation
- November 25, 2008State Public Notification requested1 linked violation
- September 30, 2008State Public Notification received1 linked violation
- July 24, 2008State Public Notification requested1 linked violation
- February 13, 2008State Formal Notice of Violation issued1 linked violation
- February 13, 2008State Public Notification requested1 linked violation
- September 4, 2007State Formal Notice of Violation issued4 linked violations
- May 3, 2007State Public Notification requested2 linked violations
- February 1, 2007State Public Notification requested2 linked violations
- November 20, 2006State Public Notification received3 linked violations
- November 2, 2006State Formal Notice of Violation issued1 linked violation
- November 2, 2006State Public Notification requested2 linked violations
- September 5, 2006State Public Notification received3 linked violations
- March 2, 2006State Public Notification received3 linked violations
- October 31, 2005State Public Notification requested1 linked violation
- August 3, 2005State Public Notification requested4 linked violations
- May 9, 2005State Formal Notice of Violation issued3 linked violations
- May 9, 2005State Public Notification requested2 linked violations
- February 10, 2005State Formal Notice of Violation issued2 linked violations
- February 10, 2005State Public Notification requested4 linked violations
- December 2, 2004State Formal Notice of Violation issued4 linked violations
- September 13, 2004State Public Notification received2 linked violations
- July 2, 2004State Public Notification received2 linked violations
- May 10, 2004State Public Notification received2 linked violations
- May 10, 2004State Public Notification received2 linked violations
- March 8, 2004State Public Notification received3 linked violations
- November 6, 2003State Public Notification requested2 linked violations
- September 8, 2003State Formal Notice of Violation issued3 linked violations
- June 10, 2003State Public Notification requested6 linked violations
- March 6, 2003State Public Notification requested7 linked violations
- March 6, 2003State Formal Notice of Violation issued4 linked violations
- January 6, 2003State Public Notification received3 linked violations
- October 30, 2002State Public Notification requested2 linked violations
- August 7, 2002State Public Notification requested8 linked violations
- February 27, 2001State Formal Notice of Violation issued8 linked violations
- March 7, 1990State Formal Notice of Violation issued1 linked violation
Common questions
Is SMITHFIELD HEIGHTS/SANDY MOUNT MANOR required to publish a Consumer Confidence Report?
- Yes. SMITHFIELD HEIGHTS/SANDY MOUNT MANOR 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 SMITHFIELD HEIGHTS/SANDY MOUNT MANOR’s next Consumer Confidence Report due?
- SMITHFIELD HEIGHTS/SANDY MOUNT MANOR’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does SMITHFIELD HEIGHTS/SANDY MOUNT MANOR have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show 2 items for SMITHFIELD HEIGHTS/SANDY MOUNT MANOR 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
GWALTNEY, JONATHAN H.
757-357-4843
ISLE OF WIGHT, VA 23397