VOCs in Fremont County: What Riverton’s Public Water Record Reveals about Volatile Organic Compounds

$1,590.00
VOC Reduction System Water Filter
✓ Free shipping in the USA · ✓ 90-day returns · ✓ Secure checkout
How Seasonal Water-Table Changes Move a Solvent Plume Relative to a Well Screen
Surface water source dynamics
Riverton’s public water system relies on surface water, which varies seasonally. Changes in water tables and flow can shift any solvent or VOC plumes present in the environment, influencing the concentration and location of those compounds near intake points.
Plume movement versus household plumbing
Data on plume shifts applies to the public water source but does not predict VOC presence or concentration at individual taps. Household plumbing configurations and storage also modify what water arrives at fixtures.
Which volatile organic compounds appear in this record and which do not, named from the facts
No detected VOCs above reporting levels
EPA’s 2013-2015 monitoring of the City of Riverton’s system (serving 10,330 people) found no 1,1-dichloroethane, chloromethane, bromomethane, HCFC-22, Halon 1011, or 1,3-butadiene above respective reporting levels (ranging 0.03 to 0.2 µg/L or parts per billion). These compounds were measured but not observed in concentrations exceeding detection limits.
Absence of violations and health-based exceedances
Although the system has two EPA health-based violations on record unrelated to VOCs, no federal maximum contaminant levels apply specifically to the VOCs sampled here, so none of these detections indicate violations or unsafe conditions regarding VOCs.
Why volatility matters: showering, dishwashing and inhalation routes versus drinking
Volatile organics can enter the air from household water
Unlike many contaminants, solvent compounds evaporate easily, making inhalation a relevant exposure route during showering or dishwashing, not just ingestion through drinking water.
Health concerns depend on compound and exposure levels
Understanding which VOCs might be present and their concentrations is essential for assessing potential risks, but local public system data does not establish those levels at individual residences.
How public-system records differ from private-well testing in what they establish
Public system data represents multiple connections, not single homes
EPA records describe broad sampling across the public water system, not individual household water quality. Your well’s VOC content can differ significantly and requires specific testing to determine.
Sampling methods and detection limits shape what data shows
Monitoring with set detection levels identifies if VOCs are present above minimal thresholds, but no detection does not prove absolute absence, just below-reporting-level presence.
The household or facility symptoms that do and do not point to this problem
Symptoms possibly related to VOCs
Unusual chemical tastes or odors, persistent respiratory irritation when using water, or sudden changes in water quality may suggest solvent compounds.
Symptoms unlikely to be caused by VOCs
Hard water effects, mineral staining, or biological fouling are unrelated to VOCs and should be investigated separately.
Addressing VOC concerns with the Fleck VOCs & Industrial Chemicals Filter
If your household’s testing confirms volatile organic compounds in water at levels you find concerning, you can consider treatment options like the Fleck VOCs & Industrial Chemicals Filter. This Fleck system uses specialized filtration technology designed to reduce a range of solvent compounds and industrial chemicals, shipping ready to configure for residential water supplies. Matching treatment to the measured demand figure is important for effective removal.
Where this information comes from
Source: EPA SDWIS public water system record. Sampled 2013-08-26. These figures describe the public water system's record, not the plumbing inside any individual building.
On record: EPA UCMR3 monitoring (2013-2015) for City of Riverton (WY5600047), WY: 168 results across 6 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level
