Understanding Perchlorate in GU Area Water: Sampling Insights and Treatment Options
$1,757.00
✓ Free shipping in the USA · ✓ 90-day returns · ✓ Secure checkout
Overview of GU Northern Water System and Water Delivery
The GWA Northern Water System serves residents in the GU area through a network of wells and supply lines. Water is drawn from multiple sources and treated before distribution to homes. This system's water quality is monitored regularly by the EPA under federal guidelines.
Samples and Testing Coverage Behind Perchlorate Data
Number of Samples Taken
Between 2002 and 2003, 194 perchlorate samples were collected from the GWA Northern Water System as part of EPA's Unregulated Contaminant Monitoring Rule 1 (UCMR1). This represents data aggregated at the system level, not individual homes or taps.
Meaning of No Detections Above Reporting Level
None of these samples showed perchlorate concentrations exceeding the EPA reporting level of 4.0 micrograms per liter (µg/L). However, absence of detections above this threshold in system sampling does not guarantee any single household's water is free of perchlorate without direct testing.
Differences Between Aesthetic Standards and Health-Based Limits
Current Regulatory Status
Perchlorate has no established federal maximum contaminant level (MCL) in drinking water, so detected amounts do not constitute a violation or indicate unsafe water within the system. The system's EPA record shows zero health-based violations relating to perchlorate.
What Secondary Standards Mean
Aesthetic secondary standards focus on water taste, odor, or appearance and do not apply to perchlorate. Therefore, taste or staining is not a concern for this constituent, distinguishing it from other water quality factors.
How the Autotrol Perchlorate Filter Addresses Perchlorate
Technology Functionality
The Autotrol Perchlorate Filter employs specialized filtration technology designed to reduce perchlorate levels by adsorbing or removing it from water. This system ships ready to configure for residential use.
Benefits of Using the Filter
By using this filter, households can manage perchlorate presence in their water independently of system-wide data, gaining control over water quality at the tap.
Origin of Perchlorate in GU Groundwater and Distribution
Potential Sources
Perchlorate enters groundwater primarily through environmental releases related to industrial activity and natural sources. In GU, its presence is monitored as a precaution, reflecting possible but unconfirmed local inputs.
Distribution System Factors
Water treatment and blending in the distribution system can influence perchlorate levels reaching consumers, but system results indicate low detection overall.
Impact of Well and Sample Depth on Expected Levels
Variation by Source Depth
Perchlorate presence can vary by aquifer depth and well construction, with deeper wells often showing different profiles compared to shallower sources. Area data represent a blend of these conditions.
Consumer Considerations
Individual water tests reflecting well depth and location are necessary to understand a household’s specific perchlorate level.
What GU Area Perchlorate Data Do Not Indicate
- The absence of detections above reporting levels in system samples does not confirm that all household water is free of perchlorate.
- Perchlorate detections are not health violations or safety hazards as per current EPA records for the region.
- These data cannot replace direct water testing when specific household water quality assessment is required.
For households concerned about perchlorate, using the Autotrol Perchlorate Filter offers a documented method to address potential presence effectively.
Where this information comes from
Source: EPA SDWIS public water system record. Sampled 2003-09-21. These figures describe the public water system's record, not the plumbing inside any individual building.
On record: EPA UCMR1 monitoring (2001-2005) for GWA NORTHERN WATER SYSTEM (GU0000006), GU: 194 results across 1 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level