Is BRAXTON HILLS/SIMMONS HEIGHTS required to publish a Consumer Confidence Report?

Yes. BRAXTON HILLS/SIMMONS HEIGHTS 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 BRAXTON HILLS/SIMMONS HEIGHTS’s next Consumer Confidence Report due?

BRAXTON HILLS/SIMMONS HEIGHTS’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.

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.

CARY, NC · Cumberland County

BRAXTON HILLS/SIMMONS HEIGHTS Water System

Consumer Confidence Report status

BRAXTON HILLS/SIMMONS HEIGHTS 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 BRAXTON HILLS/SIMMONS HEIGHTS.

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): NC0326124
System type: Community Water System
Population served: 680
Service connections: 272
Ownership: privately owned
Water source: groundwater (wells)

BRAXTON HILLS/SIMMONS HEIGHTS is one of 749 community water systems in North Carolina in the 501 to 3,300 people size category, serving 680 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.

Of the 15, 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 Public Notice Rule and Revised PN Rule, and the Lead and Copper Rule.

Violation history

Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2024 – December 31, 2024
Resolved
Public Notification Violation for NPDWR Violation
—
Public Notice
September 25, 2009 – September 16, 2010
Resolved
Public Notification Violation for NPDWR Violation
—
Public Notice
September 25, 2009 – September 16, 2010
Resolved
Monitoring, Regular
—
Combined Uranium
January 1, 2008 – March 31, 2008
Resolved
Monitoring, Regular
—
Gross Alpha, Excl. Radon and U
January 1, 2008 – March 31, 2008
Resolved
Monitoring, Regular
—
Gross Alpha, Excl. Radon and U
January 1, 2008 – March 31, 2008
Resolved
Monitoring, Regular
—
Combined Uranium
January 1, 2008 – March 31, 2008
Resolved
Public Notification Violation for NPDWR Violation
—
Public Notice
August 24, 2007 – September 10, 2007
Resolved
Follow-up Or Routine LCR Tap M/R
—
Lead and Copper Rule
July 1, 2006 – August 17, 2010
Resolved
OCCT/SOWT Study/Recommendation
Health-based
Lead and Copper Rule
July 1, 2006 – September 26, 2008
Resolved
Public Notification Violation for NPDWR Violation
—
Public Notice
April 3, 2006 – April 3, 2006
Resolved
Public Notification Violation for NPDWR Violation
—
Public Notice
April 3, 2006 – April 3, 2006
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2006 – March 31, 2006
Resolved
Monitoring, Regular
—
Heptachlor epoxide
January 1, 2006 – December 31, 2006
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2005 – September 30, 2005
Resolved

Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
October 1, 2024 – December 31, 2024	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
September 25, 2009 – September 16, 2010	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
September 25, 2009 – September 16, 2010	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
January 1, 2008 – March 31, 2008	Monitoring, Regular	Combined Uranium	—	Resolved
January 1, 2008 – March 31, 2008	Monitoring, Regular	Gross Alpha, Excl. Radon and U	—	Resolved
January 1, 2008 – March 31, 2008	Monitoring, Regular	Gross Alpha, Excl. Radon and U	—	Resolved
January 1, 2008 – March 31, 2008	Monitoring, Regular	Combined Uranium	—	Resolved
August 24, 2007 – September 10, 2007	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
July 1, 2006 – August 17, 2010	Follow-up Or Routine LCR Tap M/R	Lead and Copper Rule	—	Resolved
July 1, 2006 – September 26, 2008	OCCT/SOWT Study/Recommendation	Lead and Copper Rule	Health-based	Resolved
April 3, 2006 – April 3, 2006	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
April 3, 2006 – April 3, 2006	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
January 1, 2006 – March 31, 2006	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
January 1, 2006 – December 31, 2006	Monitoring, Regular	Heptachlor epoxide	—	Resolved
July 1, 2005 – September 30, 2005	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved

Resolved addressed and confirmed by the state

Enforcement actions

March 11, 2025State Public Notification received1 linked violation
February 7, 2025State Compliance achieved1 linked violation
January 14, 2025State Public Notification requested1 linked violation
January 14, 2025State Administrative/Compliance Order without penalty issued1 linked violation
January 14, 2025State Formal Notice of Violation issued1 linked violation
September 16, 2010State Intentional no-action2 linked violations
September 16, 2010State Compliance achieved2 linked violations
August 17, 2010State Compliance achieved1 linked violation
June 11, 2010State Intentional no-action1 linked violation
June 11, 2010State Compliance achieved1 linked violation
October 22, 2008State Administrative/Compliance Order with penalty issued2 linked violations
October 22, 2008State Administrative/Compliance Order with penalty issued2 linked violations
September 26, 2008State Compliance achieved1 linked violation
September 24, 2008State Formal Notice of Violation issued1 linked violation
September 24, 2008State Formal Notice of Violation issued1 linked violation
September 24, 2008State Public Notification requested1 linked violation
September 24, 2008State Public Notification requested1 linked violation
September 24, 2008State Formal Notice of Violation issued1 linked violation
September 24, 2008State Public Notification requested1 linked violation
September 24, 2008State Formal Notice of Violation issued1 linked violation
September 24, 2008State Public Notification requested1 linked violation
June 30, 2008State Compliance achieved4 linked violations
February 5, 2008State Public Notification received1 linked violation
September 18, 2007State Public Notification received1 linked violation
September 18, 2007State Public Notification received1 linked violation
September 10, 2007State Compliance achieved1 linked violation
July 24, 2007State Public Notification requested1 linked violation
July 24, 2007State Formal Notice of Violation issued1 linked violation
March 26, 2007State Formal Notice of Violation issued1 linked violation
March 26, 2007State Public Notification requested1 linked violation
November 29, 2006State Compliance achieved1 linked violation
October 30, 2006State Compliance achieved1 linked violation
October 30, 2006State Compliance achieved1 linked violation
October 30, 2006State Compliance achieved1 linked violation
October 11, 2006State Public Notification received2 linked violations
October 11, 2006State Public Notification received1 linked violation
September 25, 2006State Formal Notice of Violation issued1 linked violation
September 25, 2006State Public Notification requested1 linked violation
July 25, 2006State Public Notification received2 linked violations
April 3, 2006State Public Notification received1 linked violation
April 3, 2006State Compliance achieved1 linked violation
April 3, 2006State Compliance achieved1 linked violation
April 3, 2006State Public Notification received1 linked violation
April 3, 2006State Public Notification received2 linked violations
April 3, 2006State Public Notification received2 linked violations
April 3, 2006State Public Notification received1 linked violation
April 3, 2006State Public Notification received1 linked violation
April 2, 2006State Public Notification received1 linked violation
March 27, 2006State Public Notification requested1 linked violation
March 27, 2006State Formal Notice of Violation issued2 linked violations
March 27, 2006State Public Notification requested2 linked violations
March 23, 2006State Public Notification requested1 linked violation
March 23, 2006State Public Notification requested2 linked violations
March 23, 2006State Public Notification received2 linked violations
February 21, 2006State Formal Notice of Violation issued2 linked violations
February 21, 2006State Public Notification requested1 linked violation
February 21, 2006State Public Notification requested1 linked violation
November 15, 2005State Administrative/Compliance Order without penalty issued12 linked violations
November 15, 2005State Administrative/Compliance Order without penalty issued12 linked violations
May 6, 2003State Compliance achieved1 linked violation
May 6, 2003State Compliance achieved2 linked violations
May 6, 2003State Compliance achieved1 linked violation
May 6, 2003State Compliance achieved1 linked violation
May 6, 2003State Compliance achieved1 linked violation
May 6, 2003State Compliance achieved1 linked violation

Common questions

Is BRAXTON HILLS/SIMMONS HEIGHTS required to publish a Consumer Confidence Report?: Yes. BRAXTON HILLS/SIMMONS HEIGHTS 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 BRAXTON HILLS/SIMMONS HEIGHTS’s next Consumer Confidence Report due?: BRAXTON HILLS/SIMMONS HEIGHTS’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does BRAXTON HILLS/SIMMONS HEIGHTS have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show no open violations for BRAXTON HILLS/SIMMONS HEIGHTS.
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