A laboratory test report measuring volatile organic compounds (VOCs) in water usually lists individual compound names alongside their concentrations in micrograms per liter (µg/L). These values indicate what was detected, if anything, above specific reporting levels but do not alone establish safety or compliance. For example, in the Belcourt-Turtle Mtn. Rural Water system serving Area 08, no VOC was detected above its reporting level during federal testing from 2013 to 2015.
Why do aesthetic secondary standards differ from health-based limits when applied to VOCs?
Aesthetic secondary standards for water quality address factors like taste, odor, and appearance rather than health risks. VOCs monitored under federal unregulated contaminant rules often lack enforceable health-based maximum contaminant levels (MCLs). This means detections are not health violations but measurements to inform water systems and customers. Detected VOCs below levels of concern may affect water characteristics but do not necessarily indicate unsafe conditions.
How do VOCs enter groundwater or the distribution system in this region?
VOCs can originate from various sources including industrial solvents, gasoline components, or household products that seep into groundwater or enter distribution systems through cross-connections or infrastructure leaks. In Area 08’s Belcourt-Turtle Mtn. Rural Water system, federal occurrence monitoring detected none of the tested VOCs above reporting thresholds, indicating limited or controlled presence of these compounds at the source or during distribution.
What changes for a large household, a second home, or a seasonal property?
Water usage patterns affect the residence-time and stagnation of water within household plumbing, which can influence VOC levels from materials or environmental exposure inside the property. Larger households or seasonal homes may experience different water quality appearances or require tailored water treatment considerations due to varied usage frequency and volume. Testing the household supply specifically is the only way to confirm VOC presence where existing equipment is no longer operational.
What distinguishes this problem from the two problems most often confused with it?
VOCs are often confused with issues like microbial contamination or inorganic chemical problems. Unlike microbes that present health risks with known standards or metals that cause staining and taste issues, VOCs represent a class of organic chemicals with diverse sources and health effects. Their detection in water without health-based violations, as confirmed in the Area 08 system record, differentiates them from clear regulatory noncompliance or acute contamination scenarios.
What is the role of plumbing material and age, separate from the source water?
Plumbing material and infrastructure age can contribute VOCs through chemical leaching or degradation of pipe components. This means VOCs detected in household water may originate within the property’s plumbing system rather than the public water source. A household water test is necessary to identify whether plumbing contributes to current VOC levels, especially when existing filtration or treatment equipment fails to reduce these compounds effectively.
In summary, Area 08’s public water system has no recorded health-based violations for VOCs, with federal monitoring showing no detections above reporting levels. Since existing equipment is no longer functioning, the next step involves laboratory testing of household water to identify current VOC conditions. The C-Series VOCs & Industrial Chemicals Filter then offers a documented solution to effectively address VOC presence when needed.
Where this information comes from
Source: EPA SDWIS public water system record. Sampled 2015-09-01. These figures describe the public water system's record, not the plumbing inside any individual building.
On record: EPA UCMR3 monitoring (2013-2015) for Belcourt-Turtle Mtn. Rural Water (083890023), 08: 12 results across 6 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level