When considering water quality concerns in the Washington DC area, data from the Bolling Water System—a public water system serving homes in the region—provides informative background on the presence of volatile organic compounds (VOCs) in local water supplies. However, it's important to recognize that these figures represent system-wide sampling results and do not directly measure the VOC concentrations in any individual household's water.
How a Gasoline Release Differs from a Dry-Cleaning Release in Groundwater VOCs
VOCs, or volatile organic compounds, encompass a range of solvent compounds that can enter groundwater from different sources. For example, gasoline-related releases introduce compounds such as 1,1-dichloroethane and bromomethane, while dry-cleaning operations tend to release other solvent compounds. The specific VOCs detected vary based on the source of contamination, influencing the nature of the problem and potential treatment approaches.
Why Volatility Matters: Exposure through Showering, Dishwashing, and Inhalation Versus Drinking
The volatility of solvent compounds means that exposure routes include inhalation and dermal contact during household activities besides drinking. Showering or dishwashing with water containing VOCs can release these compounds into the air, where they are inhaled. This contrasts with the ingestion risk when drinking or cooking with the water. Understanding these different exposure routes helps households evaluate their overall VOC concern.
What Happens When VOCs in Water Go Untreated for Years, Stated Without Exaggeration
While the Bolling Water System's data shows no detections above reporting levels for listed VOCs like 1,1-dichloroethane, chloromethane, and HCFC-22, untreated solvent compounds can persist in groundwater if present. Long-term exposure to VOCs at elevated levels can potentially contribute to undesirable tastes, odors, or staining in home plumbing fixtures. Addressing solvent compounds early can reduce these impacts and prevent accumulation over time.
What Questions a Commercial or Industrial Operator Adds That a Household Does Not
Commercial or industrial water users often consider additional factors such as regulatory compliance for VOC discharge, process water quality standards, or the presence of industrial-specific compounds. Residential households typically focus on health, aesthetic concerns, and general safety, which simplifies the scope of water quality questions compared to commercial operations.
The Order in Which to Rule Things Out: From Cheapest Check to Laboratory Test
- Begin by reviewing any water quality reports from your local water supplier for VOC information.
- Observe any unusual tastes, odors, or staining appearing in your water supply.
- Conduct a basic home water test focusing on common water quality indicators.
- If concerns persist, arrange for laboratory testing specifically targeting VOCs and industrial chemicals to quantify the solvent compounds in your household water.
Based on these steps, if laboratory testing confirms the presence of VOCs at concerning levels in your home’s water, you can consider technologies designed to reduce volatile organic compounds and industrial chemicals. The C-Series VOCs & Industrial Chemicals Filter is one such system that ships ready to configure and is designed to address these contaminants effectively.
In conclusion, the key test to understand your household water’s VOC status is a laboratory analysis for volatile organic compounds tailored to your well or tap. This test provides definitive information to decide if treatment like the C-Series filter is needed, ensuring your water quality aligns with your household’s expectations and needs.
Where this information comes from
Source: EPA SDWIS public water system record. Sampled 2014-05-19. These figures describe the public water system's record, not the plumbing inside any individual building.
On record: EPA UCMR3 monitoring (2013-2015) for Bolling Water System - Jt. Base Anacostia-Bolling (DC0000007), DC: 24 results across 6 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level