Interpreting Perchlorate Results in Anoka County Water Testing
Laboratory reports for perchlorate in public water systems list quantified results based on federal monitoring protocols. In Anoka County, the Blaine water system, serving about 70,220 people, provided 16 test results from 2001 to 2005 showing no perchlorate detected above the reporting level of 4.0 micrograms per liter (µg/L). Because there is no federal maximum contaminant level (MCL) specifically for perchlorate, any detection above the reporting level does not equate to a violation or indicate unsafe water. These results reflect measurements taken at the system level, not at individual homes.
Pathways for Perchlorate in Local Groundwater and Water Systems
Perchlorate is an inorganic chemical that can enter groundwater through environmental sources such as agricultural fertilizers, industrial activities, or atmospheric deposition. In Anoka County, the Blaine public water system obtains its supply from groundwater sources, which can be susceptible to contamination by perchlorate due to these pathways. However, the absence of detections above the reporting threshold during the EPA occurrence monitoring indicates that perchlorate presence, if any, is minimal in the monitored system.
Aesthetic Versus Health-Based Standards for Perchlorate
It's important to distinguish between aesthetic secondary standards and health-based limits established for water constituents. For perchlorate, federal regulations have not established a mandatory MCL due to insufficient data at the time of rulemaking, although health-based guidelines are under consideration. Aesthetic standards generally pertain to taste, staining, or corrosivity, which do not apply to perchlorate as it is odorless and tasteless in drinking water at typical levels. Therefore, regulatory focus remains on health-based evaluations rather than aesthetic concerns for this constituent.
How the Fleck Perchlorate Filter Addresses Perchlorate in Residential Water
For residential users weighing treatment options, the Fleck Perchlorate Filter offers a documented technology designed to reduce perchlorate levels. This system operates by removing or neutralizing perchlorate ions from the water supply, typically employing ion exchange processes tailored for perchlorate reduction. It ships ready to configure for connection with existing water lines and can be selected as part of a comprehensive approach for water quality management when perchlorate testing indicates a need for treatment.
Sample Size and Its Implications for Interpreting Perchlorate Data
The reported perchlorate results for Blaine consist of 16 samples collected over several months during 2001 to 2005. While this number offers an initial indication of perchlorate occurrence in the public system, it represents a limited dataset relative to the number of wells and connections served. Variability in perchlorate concentrations can occur over time and location, so individual household testing is recommended to determine specific water conditions. These public records provide context but do not substitute for on-site analysis.
In summary, the Blaine public water system's perchlorate record in Anoka County shows no detections above the specified reporting level and no health-based violations on record. The data derive from groundwater sources serving a large population and cover a moderate number of samples collected in the early 2000s. For homeowners considering treatment solutions, options like the Fleck Perchlorate Filter provide adaptable technology for perchlorate reduction. For further details and updates, consult the official EPA Safe Drinking Water Information System (SDWIS) public records for this area.
Where this information comes from
Source: EPA SDWIS public water system record. Sampled 2001-10-23. These figures describe the public water system's record, not the plumbing inside any individual building.
On record: EPA UCMR1 monitoring (2001-2005) for Blaine (MN1020006), MN: 16 results across 1 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level