COLUMBIA, SC · Lexington County
BGWC INDIAN PINES (SC3250051) Water System
Consumer Confidence Report status
BGWC INDIAN PINES (SC3250051) 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 INDIAN PINES (SC3250051).
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)
- SC3250051
- System type
- Community Water System
- Population served
- 43
- Service connections
- 17
- Ownership
- privately owned
- Water source
- surface water (rivers, lakes, or reservoirs)
BGWC INDIAN PINES (SC3250051) is one of 1,060 community water systems in South Carolina in the 500 or fewer people size category, serving 43 people from surface water.
As of August 1, 2026, its federal record holds 25 entries between 2003 and 2023, all of which EPA lists as closed. Nothing has been added since 2023.
Of the 25, 6 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, the Surface Water Treatment Rules, and the Total Coliform Rules.
Violation history
Monitoring of Treatment (SWTR-Filter)
—Surface Water Treatment Rule
March 1, 2023 – March 31, 2023
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
March 1, 2023 – March 31, 2023
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2023 – March 31, 2023
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
December 1, 2022 – December 31, 2022
ResolvedMonitoring of Treatment (SWTR-Filter)
—Surface Water Treatment Rule
December 1, 2022 – December 31, 2022
ResolvedMonitoring and Reporting (DBP)
—Chlorine
October 1, 2022 – December 31, 2022
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2013 – March 31, 2013
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2012 – December 31, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2012 – September 30, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2012 – June 30, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2012 – March 31, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2011 – December 31, 2011
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)
July 1, 2005 – September 30, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2005 – June 30, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2005 – March 31, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2004 – December 31, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2004 – September 30, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2004 – June 30, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2004 – June 30, 2004
ResolvedNotification, Public
—Combined Radium (-226 and -228)
April 1, 2004 – June 30, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2004 – March 31, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2004 – March 31, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2003 – December 31, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2003 – September 30, 2003
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| March 1, 2023 – March 31, 2023 | Monitoring of Treatment (SWTR-Filter) | Surface Water Treatment Rule | — | Resolved |
| March 1, 2023 – March 31, 2023 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| January 1, 2023 – March 31, 2023 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| December 1, 2022 – December 31, 2022 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| December 1, 2022 – December 31, 2022 | Monitoring of Treatment (SWTR-Filter) | Surface Water Treatment Rule | — | Resolved |
| October 1, 2022 – December 31, 2022 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 1, 2013 – March 31, 2013 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2012 – December 31, 2012 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2012 – September 30, 2012 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2012 – June 30, 2012 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2012 – March 31, 2012 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2011 – December 31, 2011 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2005 – December 31, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2005 – September 30, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2005 – June 30, 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 |
| October 1, 2004 – December 31, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2004 – September 30, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2004 – June 30, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2004 – June 30, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2004 – June 30, 2004 | Notification, Public | Combined Radium (-226 and -228) | — | Resolved |
| January 1, 2004 – March 31, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2004 – March 31, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2003 – December 31, 2003 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2003 – September 30, 2003 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- June 6, 2023State Public Notification received1 linked violation
- June 6, 2023State Public Notification received1 linked violation
- June 6, 2023State Public Notification received1 linked violation
- June 6, 2023State Public Notification received1 linked violation
- June 6, 2023State Public Notification received1 linked violation
- June 6, 2023State Public Notification received1 linked violation
- May 16, 2023State Violation/Reminder Notice1 linked violation
- May 16, 2023State Public Notification requested1 linked violation
- May 16, 2023State Public Notification requested1 linked violation
- May 16, 2023State Violation/Reminder Notice1 linked violation
- May 16, 2023State Public Notification requested1 linked violation
- May 16, 2023State Violation/Reminder Notice1 linked violation
- April 24, 2023State Compliance achieved1 linked violation
- April 24, 2023State Compliance achieved1 linked violation
- April 24, 2023State Compliance achieved1 linked violation
- January 20, 2023State Compliance achieved1 linked violation
- January 20, 2023State Compliance achieved1 linked violation
- January 20, 2023State Compliance achieved1 linked violation
- January 6, 2023State Violation/Reminder Notice1 linked violation
- January 6, 2023State Public Notification requested1 linked violation
- January 6, 2023State Violation/Reminder Notice1 linked violation
- January 6, 2023State Public Notification requested1 linked violation
- January 6, 2023State Violation/Reminder Notice1 linked violation
- January 6, 2023State Public Notification requested1 linked violation
- September 25, 2013State Compliance achieved7 linked violations
- June 18, 2013State Public Notification received1 linked violation
- June 18, 2013State Public Notification received1 linked violation
- May 14, 2013State Public Notification requested1 linked violation
- May 14, 2013State Violation/Reminder Notice1 linked violation
- May 14, 2013State Violation/Reminder Notice1 linked violation
- May 14, 2013State Public Notification requested1 linked violation
- March 9, 2013State Public Notification received1 linked violation
- January 28, 2013State Public Notification requested1 linked violation
- January 28, 2013State Violation/Reminder Notice1 linked violation
- October 18, 2012State Public Notification received1 linked violation
- October 17, 2012State Administrative Penalty assessed3 linked violations
- September 26, 2012State Violation/Reminder Notice1 linked violation
- September 26, 2012State Public Notification requested1 linked violation
- August 1, 2012State Administrative/Compliance Order with penalty issued6 linked violations
- July 2, 2012State Public Notification received1 linked violation
- July 2, 2012State Public Notification received1 linked violation
- June 28, 2012State Show-Cause hearing2 linked violations
- June 19, 2012State Formal Notice of Violation issued2 linked violations
- June 11, 2012State Violation/Reminder Notice1 linked violation
- June 11, 2012State Public Notification requested1 linked violation
- June 11, 2012State Violation/Reminder Notice1 linked violation
- June 11, 2012State Public Notification requested1 linked violation
- July 1, 2007State Compliance achieved4 linked violations
- May 22, 2006State Violation/Reminder Notice2 linked violations
- February 13, 2006State Compliance achieved11 linked violations
- November 24, 2004State Public Notification received1 linked violation
- September 8, 2004State Public Notification received1 linked violation
- September 8, 2004State Public Notification received2 linked violations
- June 15, 2004State Public Notification received4 linked violations
- May 13, 2004State Violation/Reminder Notice4 linked violations
- April 5, 2004State Public Notification received1 linked violation
- February 25, 2004State Violation/Reminder Notice1 linked violation
- February 2, 2004State Public Notification received1 linked violation
- January 20, 2004State Public Notification requested3 linked violations
- December 19, 2003State Violation/Reminder Notice1 linked violation
- September 29, 2003State Public Notification received1 linked violation
- August 21, 2003State Violation/Reminder Notice1 linked violation
Common questions
Is BGWC INDIAN PINES (SC3250051) required to publish a Consumer Confidence Report?
- Yes. BGWC INDIAN PINES (SC3250051) 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 INDIAN PINES (SC3250051)’s next Consumer Confidence Report due?
- BGWC INDIAN PINES (SC3250051)’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does BGWC INDIAN PINES (SC3250051) have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for BGWC INDIAN PINES (SC3250051).
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
BLUE GRANITE WATER COMPANY
864-483-4268
COLUMBIA, SC 29203