FORT MILL, SC · Lexington County
BGWC DUTCHMAN ACRES (SC3250028) Water System
Consumer Confidence Report status
BGWC DUTCHMAN ACRES (SC3250028) 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 BGWC DUTCHMAN ACRES (SC3250028).
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 South Carolina’s official records. Always confirm current status with South Carolina before making decisions based on this information.
System facts
- System ID (PWSID)
- SC3250028
- System type
- Community Water System
- Population served
- 60
- Service connections
- 24
- Ownership
- privately owned
- Water source
- groundwater (wells)
BGWC DUTCHMAN ACRES (SC3250028) is one of 1,060 community water systems in South Carolina in the 500 or fewer people size category, serving 60 people from groundwater.
As of August 1, 2026, its federal record holds 16 entries between 2001 and 2009, all of which EPA lists as closed. Nothing has been added since 2009.
Of the 16, 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 the Radionuclides and Revised Rad Rule and inorganic chemicals.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2009 – December 31, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2009 – September 30, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2009 – June 30, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2009 – March 31, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2008 – December 31, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2008 – September 30, 2008
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)
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)
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
ResolvedMonitoring, Regular
—Nitrate
January 1, 2001 – December 31, 2001
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| October 1, 2009 – December 31, 2009 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2009 – September 30, 2009 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2009 – June 30, 2009 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2009 – March 31, 2009 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2008 – December 31, 2008 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2008 – September 30, 2008 | 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 |
| 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 |
| 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 |
| January 1, 2001 – December 31, 2001 | Monitoring, Regular | Nitrate | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- April 1, 2011State Public Notification received1 linked violation
- February 24, 2011State Compliance achieved15 linked violations
- July 1, 2010State Bilateral Compliance Agreement signed15 linked violations
- April 14, 2010State Violation/Reminder Notice1 linked violation
- April 14, 2010State Public Notification requested1 linked violation
- February 10, 2010State Public Notification received1 linked violation
- September 17, 2009State Violation/Reminder Notice1 linked violation
- September 17, 2009State Public Notification requested1 linked violation
- June 3, 2009State Public Notification requested1 linked violation
- June 3, 2009State Violation/Reminder Notice1 linked violation
- March 23, 2009State Public Notification received1 linked violation
- February 18, 2009State Public Notification received1 linked violation
- February 13, 2009State Public Notification requested1 linked violation
- February 13, 2009State Violation/Reminder Notice1 linked violation
- January 9, 2009State Public Notification requested1 linked violation
- January 9, 2009State Violation/Reminder Notice1 linked violation
- November 6, 2008State Violation/Reminder Notice1 linked violation
- November 6, 2008State Violation/Reminder Notice1 linked violation
- November 6, 2008State Public Notification requested1 linked violation
- November 6, 2008State Violation/Reminder Notice1 linked violation
- November 6, 2008State Public Notification requested1 linked violation
- November 6, 2008State Public Notification requested1 linked violation
- September 19, 2008State Public Notification received1 linked violation
- September 12, 2008State Public Notification received1 linked violation
- August 26, 2008State Administrative Penalty assessed7 linked violations
- August 26, 2008State Administrative/Compliance Order with penalty issued8 linked violations
- August 13, 2008State Violation/Reminder Notice1 linked violation
- August 13, 2008State Public Notification requested1 linked violation
- July 17, 2008State Public Notification received1 linked violation
- July 15, 2008State Show-Cause hearing11 linked violations
- July 1, 2008State Formal Notice of Violation issued7 linked violations
- June 11, 2008State Violation/Reminder Notice1 linked violation
- June 11, 2008State Public Notification requested1 linked violation
- March 18, 2008State Violation/Reminder Notice1 linked violation
- March 18, 2008State Violation/Reminder Notice1 linked violation
- March 18, 2008State Public Notification requested1 linked violation
- March 18, 2008State Public Notification requested1 linked violation
- March 18, 2008State Violation/Reminder Notice1 linked violation
- March 18, 2008State Public Notification requested1 linked violation
- July 13, 2007State Violation/Reminder Notice1 linked violation
- March 23, 2007State Public Notification received1 linked violation
- February 22, 2007State Violation/Reminder Notice1 linked violation
- November 20, 2002State Compliance achieved1 linked violation
- July 1, 2002State Administrative/Compliance Order with penalty issued1 linked violation
- July 1, 2002State Public Notification received1 linked violation
Common questions
Is BGWC DUTCHMAN ACRES (SC3250028) required to publish a Consumer Confidence Report?
- Yes. BGWC DUTCHMAN ACRES (SC3250028) 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 BGWC DUTCHMAN ACRES (SC3250028)’s next Consumer Confidence Report due?
- BGWC DUTCHMAN ACRES (SC3250028)’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does BGWC DUTCHMAN ACRES (SC3250028) have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for BGWC DUTCHMAN ACRES (SC3250028).
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
JAMES, ADAM
803-547-7158
FORT MILL, SC 29715