Household 1,2,3-TCP Concerns in Albany County: Evaluating Contact Time for Effective Treatment

Understanding the limits of area water-quality data for your household

Government sampling in Laramie's public water system found no 1,2,3-TCP detections above 0.03 micrograms per liter (ppb) from 2013 to 2015

This data represents monitoring results for the City of Laramie's surface water supply serving over 32,000 people, not individual home water conditions. Your home's water could differ and requires specific testing to determine 1,2,3-trichloropropane presence.

Granular activated carbon contact time: why bed depth matters more for TCP than for taste

Longer contact time boosts effectiveness against 1,2,3-trichloropropane

The chlorinated solvent 1,2,3-TCP, unlike compounds affecting taste or odor, requires sufficient residence time in a granular activated carbon (GAC) bed for optimal reduction. Bed depth directly correlates to this contact time, allowing the GAC to adsorb the chlorinated solvent more thoroughly.

How a soil fumigant impurity from the 1950s-1980s reached deep groundwater decades later

Legacy contamination sources explain 1,2,3-TCP's presence in groundwater

1,2,3-TCP historically appeared as an impurity in soil fumigants widely used in mid-20th century agriculture. Over time, infiltration has carried residual amounts into deep groundwater, creating a delayed pathway for this chlorinated solvent to enter water supplies.

How to compare this area's record with a neighbouring county's without overreading it

Regional monitoring results are not proxies for individual household water quality

Differences in local geology and water source types mean nearby counties' 1,2,3-trichloropropane data cannot be directly applied to Laramie homes. Each area’s public water system records reflect collective results rather than individual well or tap water conditions.

What happens when this problem is left untreated for years, stated without exaggeration

Persistent 1,2,3-TCP in a household water supply can lead to long-term exposure

While no health-based violations exist for Laramie's municipal water, untreated 1,2,3-trichloropropane at households with private wells or different sources could result in ongoing exposure to this chlorinated solvent. This reinforces the value of accurate testing and effective treatment if presence is confirmed.

A worked example: reading the record's median and range as a homeowner would

The City of Laramie's 1,2,3-TCP monitoring reported zero detections above 0.03 micrograms per liter

This indicates a median concentration at or below this detection limit over multiple tests. Homeowners without individual well testing should not infer absence or presence but recognize the importance of private water analysis to clarify their water's condition.

How the documented treatment technology removes or neutralises the constituent

The C-Series 1,2,3-TCP Filter uses granular activated carbon designed for extended contact time with chlorinated solvents

This configuration allows the carbon media to adsorb 1,2,3-trichloropropane effectively, lowering its concentration within residential water supplies. The equipment ships ready to configure, enabling homeowners to address 1,2,3-TCP if testing indicates its presence in their water.

Closing considerations

The EPA monitoring data for Laramie's public water supply covers thousands of connections and is based on surface water sources; it reflects overall system performance, not individual household water. Homeowners should obtain their own water tests to determine specific 1,2,3-trichloropropane levels. The official EPA database is the authoritative source for public water system monitoring results in Albany County.

Where this information comes from

Source: EPA SDWIS public water system record. Sampled 2013-11-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 City of Laramie (WY5600029), WY: 10 results across 1 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level