Pentair 1,2,3-TCP Filter

Buy Now

View full details

Balancing Treatment Capacity with Household Water Demand

This week, households in Ozark, Christian County, face the decision of choosing water treatment equipment to address 1,2,3-trichloropropane (TCP) concerns while matching their daily water usage. Since Ozark's public water system draws groundwater serving over 22,000 people through 10,375 connections, the volume and flow rate of your household’s water use will dictate the necessary capacity of any treatment equipment. Assessing your family's average and peak daily water consumption helps ensure the selected system can manage the demand without reducing water pressure or treatment effectiveness.

Distinguishing 1,2,3-TCP from Similar Water Issues

1,2,3-TCP differs significantly from common water concerns such as chlorides or total dissolved solids. Unlike these aesthetic secondary standards, which affect taste, staining, and corrosion potential, 1,2,3-TCP is a synthetic chemical that does not have a federal maximum contaminant level (MCL). The EPA’s Unregulated Contaminant Monitoring Rule (UCMR) data for the Ozark system from 2013 to 2015 show no detections above the reporting level for 1,2,3-TCP, indicating the substance was either not present or below measurement thresholds during testing. This contrasts with commonly tested water quality parameters that might fluctuate seasonally or geographically.

Water Quality After Treatment with the Documented Technology

Once water from Ozark’s public system passes through the Pentair 1,2,3-TCP Filter, the water delivered to household taps is treated specifically to reduce 1,2,3-TCP levels. This technology targets the removal of this compound, improving overall water quality related to this constituent without affecting other water properties. Treated water will maintain the same basic characteristics concerning hardness, pH, and other factors, preserving household water usability while addressing 1,2,3-TCP concerns.

Interpreting the UCMR Data and Federal Standards for 1,2,3-TCP

The federal UCMR monitoring for the Ozark system revealed 20 samples were taken with zero detections above the reporting limit of 0.03 micrograms per liter (µg/L) for 1,2,3-TCP. Because no federal MCL exists for this compound, these results cannot be interpreted as violations or health-based exceedances. Instead, these detections represent measurements made within regulatory surveillance efforts, not individual water safety assessments. For homeowners, this means the public water supply demonstrated no measurable presence of 1,2,3-TCP during the testing period, but individual well or home plumbing tests would be needed to confirm local water conditions.

Example: Using the System Record to Inform Household Treatment Choices

Imagine a household in Ozark reviewing the system’s record: with 20 samples all below detection, the median and range indicate undetectable levels in public supply water. However, if this household uses a private well, they must obtain a certified laboratory test targeting 1,2,3-TCP to understand their specific water quality. Knowing the household's water demand and local water conditions can guide selection of the Pentair 1,2,3-TCP Filter, which ships ready to configure and is designed to address this compound when present.

Deciding on water treatment for 1,2,3-TCP in Christian County involves matching system treatment capacity to your household's daily water use, understanding how this compound differs from other common concerns, and recognizing what public water monitoring indicates and does not indicate. Using the Pentair 1,2,3-TCP Filter provides a documented approach to reduce 1,2,3-TCP when it is detected in your water.

Where this information comes from

Source: EPA SDWIS public water system record. Sampled 2013-09-12. These figures describe the public water system's record, not the plumbing inside any individual building.

On record: EPA UCMR3 monitoring (2013-2015) for Ozark (MO5010619), MO: 20 results across 1 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level