When considering 1,2,3-trichloropropane (TCP) in your home's water, it's important to understand what regional public water system records tell you—and what they do not. The available government data covers broad monitoring results for Clarkstown, in Rockland County, NY, but cannot specify the level found in any individual household’s water. To know your home's water quality precisely, a direct test is needed.
Myth: 1,2,3-Trichloropropane Can Be Removed by Air Stripping Easily
1,2,3-TCP is a chlorinated solvent known for its persistence. Unlike volatile organic compounds that air stripping effectively treats, 1,2,3-TCP resists this process due to its chemical properties. This resistance means treatment methods relying on air stripping may not adequately reduce chlorinated solvent concentrations, guiding household equipment choices toward alternative technologies.
Myth: Federal Regulations Define Safe Levels of 1,2,3-TCP
While some states, like California, have established a stringent state limit for 1,2,3-trichloropropane at 5 nanograms per liter (ng/L), equivalent to 0.005 micrograms per liter (µg/L), no federal maximum contaminant level (MCL) currently exists. The publicly reported data for the local United Water New York system shows no detection above the reporting level of 0.03 µg/L (30 ng/L) in 73 samples from 2013 to 2015. Because there is no federal standard, detections do not imply noncompliance or unsafe water.
Myth: Regional Sample Data Represents Every Well or Household
The monitoring results cover multiple samples collected over several years for a surface water system serving over 270,000 people through more than 56,000 connections in Clarkstown. Although this provides a reliable overview of the public water system's status, it cannot specify conditions in individual households. Variability in private wells, plumbing materials, or local distribution network factors requires specific testing for accurate assessment.
Myth: Water Needs Are the Same for All Homes in the Area
Households vary in size and water demand. A large household uses more water daily, while a second home or seasonal property may have lower or intermittent use. These differences influence the capacity and configuration of treatment equipment required to address 1,2,3-trichloropropane at home, making it important to match the technology to your specific demand.
Myth: All Treatment Technologies Perform Equally Against 1,2,3-TCP
Not all filtration or treatment solutions are effective on chlorinated solvents like 1,2,3-TCP. Certain technologies, notably a Fleck system equipped to handle this contaminant, are documented for their ability to reduce TCP levels in household water. These systems work by adsorptive processes designed specifically for chlorinated solvents, providing an option tailored to this particular chemical challenge.
Myth: All Water Fixtures and Usage Points Are Equally Affected
The presence of 1,2,3-trichloropropane in home water affects drinking water and cooking uses first because these involve direct ingestion or food preparation. Appliances such as ice makers and coffee machines may also be impacted sooner. Uses like irrigation or cleaning are less sensitive but still benefit from treatment for overall water quality.
Understanding regional government data—such as that from the public water system serving Clarkstown in Rockland County—helps to frame the context for your water treatment decisions, but personal water testing is vital to determine actual household conditions. For homes measuring demand and seeking an effective solution to 1,2,3-TCP, a Fleck 1,2,3-TCP Filter ships ready to configure and is designed specifically to address the demands of this chlorinated solvent in residential water supplies.
Where this information comes from
Source: EPA SDWIS public water system record. Sampled 2015-10-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 United Water New York (NY4303673), NY: 73 results across 1 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level