Perchlorate in York County ME: What Sanford Water District Records Reveal
$2,150.00
✓ Free shipping in the USA · ✓ 90-day returns · ✓ Secure checkout
Government monitoring found no perchlorate detected above reporting levels in Sanford water
The EPA's Unregulated Contaminant Monitoring Rule (UCMR) sampled the Sanford Water District groundwater system between July 2002 and January 2003. In those 16 tests, none showed perchlorate above the reporting level of 4.0 micrograms per liter (µg/L). This federal sampling was not a compliance test but indicates perchlorate concentrations were below detection thresholds during that period. No health-based violations related to perchlorate appear in system records.
Perchlorate levels in groundwater can fluctuate over time and by sampling campaigns
Government perchlorate monitoring in Sanford covers only a limited time frame from early 2000s data. Seasonal changes and multi-year trends can affect groundwater quality near industrial or agricultural sources, but no later public records show perchlorate detections at levels above reporting limits. Residents should note that non-detections in past surveys do not guarantee current absence; testing your own water is the only way to confirm perchlorate presence or absence today.
Groundwater source and sampling depth affect perchlorate detection results
Sanford's public water comes from groundwater wells, where perchlorate may enter through environmental sources such as fertilizers or industrial runoff. The depth from which samples are drawn can influence detection since perchlorate concentrations may vary vertically in an aquifer. EPA monitoring samples public system sources but does not reflect individual household well depths or plumbing conditions, which can differ significantly.
Larger households, second homes, or seasonal residences may experience different treatment needs
Homes with higher daily water use might find perchlorate filtration more demanding, especially if private source testing indicates measurable perchlorate. Seasonal or secondary residences can have water quality varying with source conditions and system use patterns. Such properties may require different water treatment sizing or schedules aligned with usage patterns to maintain effective perchlorate reduction.
Commercial or industrial users need additional considerations beyond residential concerns
While this page focuses on residential water use, commercial and industrial operators typically assess perchlorate impacts on larger-scale water demands and potential regulatory reporting. They may have to consider cumulative chemical interactions, higher volume filtration, and compliance standards beyond what household users face. Residential water users should focus on testing and treatment options tailored to individual household consumption and system specifics.
Long-term lack of perchlorate treatment can allow buildup if contamination exists but does not show symptoms easily
If perchlorate contamination is present but untested, it can persist in water supplies without obvious signs such as taste or odor changes. Over time, perchlorate exposure through drinking water is a concern mainly due to its potential interference with thyroid function, which requires sensitive measurement rather than sensory detection. Regular testing and appropriate filtration reduce any risks from unnoticed perchlorate presence.
For households assessing perchlorate treatment needs, the C-Series Perchlorate Filter ships ready to configure and is designed to address perchlorate removal according to the demand figures each household determines through testing. Accurate knowledge of personal water perchlorate levels will guide proper system sizing and maintenance.
Where this information comes from
Source: EPA SDWIS public water system record. Sampled 2003-01-29. These figures describe the public water system's record, not the plumbing inside any individual building.
On record: EPA UCMR1 monitoring (2001-2005) for SANFORD WATER DISTRICT (ME0091410), ME: 16 results across 1 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level