When running a tap in Rockford, you might notice nothing unusual about your water—clear, odorless, and unremarkable to the taste. Yet, decisions about treatment arise when considering invisible compounds like 1,2,3-trichloropropane (1,2,3-TCP) that sometimes appear in groundwater supplies here.
1. Commercial or Industrial Questions Beyond Residential Needs
While households focus mainly on water quality and daily volume needs, commercial or industrial operators add layers of complexity. They consider process water purity requirements, regulatory compliance for larger volumes, and impacts on equipment or product integrity. Households do not typically face these operational demands, making their treatment choices more centered on effective removal suited to daily consumption rates.
2. Distinguishing 1,2,3-TCP From Other Commonly Confused Substances
1,2,3-TCP is a synthetic organic compound once used as a solvent and in industrial applications. It differs from volatile organic compounds (VOCs) like trichloroethylene or from pesticides, which are sometimes confused with it due to their chemical naming similarities. Its presence in groundwater is separate from issues such as iron staining or hardness, which are mineral-based rather than synthetic chemicals.
3. Sources of 1,2,3-TCP in Rockford’s Water System
In Rockford, groundwater is the source of public water supply. 1,2,3-TCP can enter groundwater through historical industrial activities or agricultural chemical use in the surrounding area. The EPA’s public water system record indicates no detected 1,2,3-TCP above the reporting level of 0.03 micrograms per liter over multiple samples in recent years. This detection threshold confirms measurement sensitivity but does not imply contamination of any individual household tap.
4. Seasonal and Multi-Year Variation in Monitoring Results
The federal Unregulated Contaminant Monitoring Rule (UCMR3) sampling in Rockford extended from July 2014 to December 2015, covering multiple seasons and water use conditions. Across 52 test results in this period, 1,2,3-TCP was not detected above reporting limits. Such a record suggests that seasonal or annual fluctuations are minimal or below detection in the water system during those years.
5. Comparing Rockford’s Record with Neighboring Counties
When looking beyond Winnebago County, it is important not to overinterpret variations in 1,2,3-TCP detections reported elsewhere. Each county’s groundwater characteristics, industrial history, and agricultural practices differ. Rockford’s zero-detection pattern sets a regional baseline but does not guarantee identical conditions nearby. Individual well testing remains essential for specific household decisions.
6. Matching Treatment Capacity to Household Daily Demand
A household evaluating treatment should consider average daily water use, typically ranging from 50 to 100 gallons per person per day, multiplied by household size. Treatment devices like the Fleck 1,2,3-TCP Filter ship ready to configure for typical residential flow rates and volumes. Ensuring that filter capacity aligns with usage prevents unnecessary replacements and supports reliable water quality management.
In summary, Rockford’s public water system monitoring shows no detections of 1,2,3-TCP above reporting levels, indicating low likelihood of presence in the municipal supply. Households deciding on treatment should verify their own water through certified testing and select a technology like the Fleck 1,2,3-TCP Filter that fits their daily water demand.
This briefing walks through relevant water quality records, clarifies common confusions about 1,2,3-TCP, and illustrates considerations for residential treatment capacity, enabling informed decisions tailored to Rockford’s conditions.
Where this information comes from
Source: EPA SDWIS public water system record. Sampled 2015-12-09. These figures describe the public water system's record, not the plumbing inside any individual building.
On record: EPA UCMR3 monitoring (2013-2015) for Rockford (IL2010300), IL: 52 results across 1 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level