CHARLOTTE, NC · Cumberland County
TANGLEWOOD SOUTH MHPFAYETTEVILLE PWC Water System
Consumer Confidence Report status
TANGLEWOOD SOUTH MHPFAYETTEVILLE PWC 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 TANGLEWOOD SOUTH MHPFAYETTEVILLE PWC.
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)
- NC0326367
- System type
- Community Water System
- Population served
- 259
- Service connections
- 102
- Ownership
- privately owned
- Water source
- surface water (rivers, lakes, or reservoirs)
TANGLEWOOD SOUTH MHPFAYETTEVILLE PWC is one of 4,942 community water systems in North Carolina in the 500 or fewer people size category, serving 259 people from surface water.
As of August 1, 2026, its federal record holds 21 entries between 2006 and 2008, all of which EPA lists as closed. Nothing has been added since 2008.
Of the 21, 4 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 Public Notice Rule and Revised PN Rule, and the Total Coliform Rules.
Violation history
Maximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
November 1, 2008 – November 30, 2008
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
August 11, 2008 – September 16, 2010
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
August 11, 2008 – September 16, 2010
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
ResolvedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 2007 – November 7, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2007 – December 31, 2007
ResolvedMonitoring and Reporting (DBP)
—Chlorine
July 1, 2007 – September 30, 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)
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)
April 1, 2007 – June 30, 2007
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
March 30, 2007 – March 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)
January 1, 2007 – March 31, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
October 1, 2006 – December 31, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2006 – December 31, 2006
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
October 1, 2006 – December 31, 2006
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2006 – December 31, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2006 – September 30, 2006
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| November 1, 2008 – November 30, 2008 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| August 11, 2008 – September 16, 2010 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| August 11, 2008 – September 16, 2010 | Public Notification Violation for NPDWR Violation | Public Notice | — | 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 |
| October 1, 2007 – November 7, 2008 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | 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 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| July 1, 2007 – September 30, 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 |
| April 1, 2007 – June 30, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| March 30, 2007 – March 30, 2007 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| January 1, 2007 – March 31, 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 | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| October 1, 2006 – December 31, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2006 – December 31, 2006 | Monitoring, Regular | Gross Alpha, Excl. Radon and U | — | Resolved |
| October 1, 2006 – December 31, 2006 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2006 – September 30, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- September 2, 2010State no longer subject to Rule11 linked violations
- August 30, 2010State Compliance achieved2 linked violations
- December 10, 2008State Public Notification received2 linked violations
- November 13, 2008State Formal Notice of Violation issued2 linked violations
- July 11, 2008State Formal Notice of Violation issued4 linked violations
- July 11, 2008State Formal Notice of Violation issued2 linked violations
- June 26, 2008State Administrative/Compliance Order with penalty issued5 linked violations
- May 29, 2008State Public Notification requested4 linked violations
- April 1, 2008State no longer subject to Rule2 linked violations
- April 1, 2008State no longer subject to Rule18 linked violations
- March 28, 2008State Public Notification requested1 linked violation
- March 28, 2008State Formal Notice of Violation issued2 linked violations
- March 28, 2008State Formal Notice of Violation issued1 linked violation
- March 17, 2008State Public Notification received2 linked violations
- February 19, 2008State Compliance achieved2 linked violations
- January 7, 2008State Formal Notice of Violation issued1 linked violation
- January 7, 2008State Public Notification requested3 linked violations
- January 7, 2008State Formal Notice of Violation issued1 linked violation
- January 7, 2008State Public Notification requested1 linked violation
- January 4, 2008State Public Notification received1 linked violation
- January 2, 2008State Public Notification requested1 linked violation
- October 9, 2007State Formal Notice of Violation issued1 linked violation
- October 9, 2007State Public Notification requested1 linked violation
- October 9, 2007State Public Notification requested5 linked violations
- September 28, 2007State Public Notification received1 linked violation
- April 26, 2007State Public Notification requested2 linked violations
- April 26, 2007State Public Notification requested2 linked violations
- April 26, 2007State Formal Notice of Violation issued2 linked violations
- April 3, 2007State Public Notification received2 linked violations
- April 3, 2007State Public Notification received2 linked violations
- March 30, 2007State Compliance achieved3 linked violations
- March 7, 2007State Formal Notice of Violation issued1 linked violation
- March 7, 2007State Public Notification requested1 linked violation
- February 27, 2007State Formal Notice of Violation issued1 linked violation
- December 22, 2006State Public Notification received4 linked violations
- December 22, 2006State Public Notification received1 linked violation
- December 22, 2006State Public Notification received1 linked violation
- December 22, 2006State Public Notification received1 linked violation
- December 13, 2006State Formal Notice of Violation issued1 linked violation
- December 13, 2006State Administrative/Compliance Order without penalty issued3 linked violations
- December 13, 2006State Public Notification requested6 linked violations
- December 13, 2006State Formal Notice of Violation issued1 linked violation
- December 13, 2006State Administrative/Compliance Order without penalty issued6 linked violations
- December 13, 2006State Administrative/Compliance Order without penalty issued4 linked violations
Common questions
Is TANGLEWOOD SOUTH MHPFAYETTEVILLE PWC required to publish a Consumer Confidence Report?
- Yes. TANGLEWOOD SOUTH MHPFAYETTEVILLE PWC 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 TANGLEWOOD SOUTH MHPFAYETTEVILLE PWC’s next Consumer Confidence Report due?
- TANGLEWOOD SOUTH MHPFAYETTEVILLE PWC’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does TANGLEWOOD SOUTH MHPFAYETTEVILLE PWC have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for TANGLEWOOD SOUTH MHPFAYETTEVILLE PWC.
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
PATEL, HARSHNA
800-525-7990
CHARLOTTE, NC 28224