Hagan Stone Park

PWSID: NC0241513

No active violations
This system has no unresolved violations. The most recent violation on record was 2011-05-15.

System Details

Population Served25
Service Connections7
Water SourceGroundwater
System TypeTransient Non-Community
OwnerLocal Government
StatusActive
CityPleasant Garden
EPA ZIP on File27313

Areas Served

  • Pleasant Garden, Guilford County

Violation History (5 total)

ContaminantViolationDateHealth-BasedStatus
7500Other2011-05-15Returned to Compliance
7500Other2007-08-17Returned to Compliance
7500Other2007-06-24Returned to Compliance
7500Other2007-03-17Returned to Compliance
7500Other2006-09-14Returned to Compliance

Understanding This Water System's Record

Hagan Stone Park is a transient non-community water system that draws from groundwater sources and serves a population of 25 in Pleasant Garden, North Carolina. This page shows its complete compliance history as reported to the EPA's Safe Drinking Water Information System (SDWIS), the federal database that tracks every public water system in the United States.

What Do These Violations Mean?

Health-based violations mean the system exceeded an EPA maximum contaminant level (MCL) or failed to provide required treatment. These indicate potential health risks from contaminants like lead, arsenic, bacteria, nitrates, or disinfection byproducts. Non-health-based violations involve monitoring, reporting, or procedural requirements — the system missed a testing deadline or failed to notify customers, but contaminant levels were not necessarily unsafe.

What Should You Do?

Your water utility is required to publish an annual Consumer Confidence Report (CCR) that details test results and any violations. If your system has active health-based violations, consider a certified water filter rated for the specific contaminants involved. The contaminant guides on this site explain health risks and filter options for common pollutants. For the most current results, contact your water utility directly — EPA data can lag weeks or months behind real-time testing.