CARY, NC · Guilford County
FOXBURY S/D Water System
Consumer Confidence Report status
FOXBURY S/D 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 FOXBURY S/D.
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 North Carolina’s official records. Always confirm current status with North Carolina before making decisions based on this information.
System facts
- System ID (PWSID)
- NC0241208
- System type
- Community Water System
- Population served
- 63
- Service connections
- 25
- Ownership
- privately owned
- Water source
- groundwater (wells)
FOXBURY S/D is one of 4,942 community water systems in North Carolina in the 500 or fewer people size category, serving 63 people from groundwater.
As of August 1, 2026, its federal record holds 15 entries between 2005 and 2024, all of which EPA lists as closed.
None of the 15 are monitoring or reporting requirements — the category that accounts for about four in five of all violations in EPA's national dataset; these involve water-quality, treatment, or public-notice findings instead. The record involves the Radionuclides and Revised Rad Rule, the Public Notice Rule and Revised PN Rule, and the Consumer Confidence Rule.
Violation history
Consumer Confidence Report Complete Failure to Report
—Consumer Confidence Rule
July 1, 2024 – December 3, 2024
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2013 – December 31, 2013
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2008 – June 30, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2008 – March 31, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2007 – December 31, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2007 – September 30, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2007 – June 30, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2007 – March 31, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2006 – December 31, 2006
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
July 21, 2006 – September 28, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2006 – September 30, 2006
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
March 30, 2006 – September 28, 2006
ResolvedPublic Notification Violation without NPDWR Violation
—Public Notice
October 4, 2005 – April 17, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2005 – December 31, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2005 – March 31, 2005
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| July 1, 2024 – December 3, 2024 | Consumer Confidence Report Complete Failure to Report | Consumer Confidence Rule | — | Resolved |
| October 1, 2013 – December 31, 2013 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2008 – June 30, 2008 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2008 – March 31, 2008 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2007 – December 31, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2007 – September 30, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2007 – June 30, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2007 – March 31, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2006 – December 31, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 21, 2006 – September 28, 2006 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| July 1, 2006 – September 30, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| March 30, 2006 – September 28, 2006 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| October 4, 2005 – April 17, 2010 | Public Notification Violation without NPDWR Violation | Public Notice | — | Resolved |
| October 1, 2005 – December 31, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2005 – March 31, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- December 3, 2024State Compliance achieved1 linked violation
- November 14, 2024State Administrative/Compliance Order without penalty issued1 linked violation
- November 14, 2024State Formal Notice of Violation issued1 linked violation
- October 13, 2014State Compliance achieved1 linked violation
- July 31, 2014State Administrative/Compliance Order without penalty issued1 linked violation
- July 31, 2014State Public Notification requested1 linked violation
- July 31, 2014State Formal Notice of Violation issued1 linked violation
- July 30, 2014State Public Notification received1 linked violation
- December 8, 2008State Public Notification requested1 linked violation
- December 8, 2008State Formal Notice of Violation issued1 linked violation
- October 30, 2008State Public Notification received1 linked violation
- July 21, 2008State Public Notification received1 linked violation
- July 11, 2008State Public Notification requested1 linked violation
- July 11, 2008State Formal Notice of Violation issued1 linked violation
- May 5, 2008State Public Notification received1 linked violation
- March 28, 2008State Formal Notice of Violation issued1 linked violation
- March 28, 2008State Public Notification requested1 linked violation
- January 7, 2008State Formal Notice of Violation issued1 linked violation
- January 7, 2008State Public Notification requested1 linked violation
- October 30, 2007State Public Notification received1 linked violation
- October 30, 2007State Public Notification received1 linked violation
- October 9, 2007State Formal Notice of Violation issued1 linked violation
- October 9, 2007State Public Notification requested1 linked violation
- May 1, 2007State Public Notification received1 linked violation
- April 26, 2007State Public Notification requested8 linked violations
- April 26, 2007State Formal Notice of Violation issued1 linked violation
- February 2, 2007State Public Notification requested3 linked violations
- February 1, 2007State Public Notification received1 linked violation
- September 28, 2006State Compliance achieved1 linked violation
- August 29, 2006State Administrative/Compliance Order without penalty issued2 linked violations
- June 27, 2006State Public Notification received12 linked violations
- May 18, 2006State Administrative/Compliance Order without penalty issued8 linked violations
- March 22, 2006State Public Notification requested3 linked violations
- December 30, 2005State Public Notification received4 linked violations
- September 22, 2005State Public Notification requested13 linked violations
Common questions
Is FOXBURY S/D required to publish a Consumer Confidence Report?
- Yes. FOXBURY S/D 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 FOXBURY S/D’s next Consumer Confidence Report due?
- FOXBURY S/D’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does FOXBURY S/D have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for FOXBURY S/D.
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
MILLIRON, BRENT
919-653-6999
CARY, NC 27511