Understanding What Area Data Say—and Don’t Say—About Your Water
The Environmental Protection Agency's public water system records for Prattville, Autauga County, report no detections of 1,2,3-trichloropropane (TCP) above the federal reporting level of 0.03 micrograms per liter (µg/L) in Waterworks Board of Prattville’s surface water supply from mid-2014. This absence of detection in tested system samples indicates the municipal source water meets current federal criteria concerning TCP levels—but it does not establish the TCP concentration in your household water. Your home’s plumbing, private well, treatment condition, or equipment status may influence your water quality differently. Since your existing water equipment has failed, verifying your household water through a laboratory test specifically for 1,2,3-TCP and other constituents is a recommended next step to understand what you are dealing with directly.
Why the Reporting Level for 1,2,3-Trichloropropane Is Thousands of Times Lower Than for Common Metals
The federal reporting level for TCP is set at 0.03 µg/L (or 0.03 parts per billion), which is considerably lower than typical thresholds for common metals found in drinking water. This low level reflects a precautionary stance due to TCP’s persistence and potential long-term effects, not because of frequent exceedance or acute risk in most public water systems. Since TCP is a chlorinated industrial solvent rarely present at high concentrations, the EPA’s monitoring emphasizes detection even at minute traces, serving as an early warning rather than reflecting common contamination.
The Agricultural Land-Use History of Prattville and Its Relation to 1,2,3-TCP Detections
Prattville and Autauga County have a historical landscape influenced by agriculture, which can involve the use of various soil fumigants and related chemicals. However, federal monitoring from 2013 to 2015 did not detect 1,2,3-TCP in the municipal surface water serving 46,614 people through over 15,000 connections. This suggests that either agricultural sources have not contributed measurable TCP to the surface water or that the system effectively manages or dilutes such inputs. The absence of detected TCP in this large community water system aligns with the current usage and runoff patterns documented for the area.
Why 1,2,3-TCP Resists Air Stripping and What That Means for Treatment Choice
1,2,3-Trichloropropane is known for resisting removal by air stripping methods commonly effective for volatile organics. This chlorinated solvent’s chemical properties make it less likely to volatilize in typical aeration processes, requiring specialized filtration or adsorption technologies to address its presence effectively. When existing equipment fails, relying on treatments that target TCP through adsorption or catalytic degradation becomes critical. The Fleck 1,2,3-TCP Filter is documented to address this resistance by employing a filtration approach designed specifically for chlorinated solvents like TCP.
What You Should Write Down Before Seeking Treatment Advice
Before looking into replacement solutions or further treatment recommendations, note the following details:
- Document your household water's source—public water system or private well.
- Record the dates and results of any recent water quality testing, focusing on organic contaminants and TCP if available.
- Describe symptoms or changes in water quality noticed since your equipment failure, such as taste, odor, or appearance changes.
- List any prior treatment equipment details, including type and last maintenance or replacement dates.
- Note any health advisories or communications received from your water supplier.
Household Symptoms That May or May Not Indicate 1,2,3-TCP Presence
Typical household symptoms linked to 1,2,3-trichloropropane exposure in water are subtle since TCP is colorless and typically odorless at the concentrations monitored by EPA. Unlike problems causing staining or visible particulate matter, TCP does not produce obvious signs such as discoloration or cloudiness. Taste changes may not be noticeable at low levels. Therefore, absence of sensory clues does not rule out the presence of TCP. Conversely, visible or taste changes alone often stem from other common water issues unrelated to TCP.
Distinguishing 1,2,3-TCP From Commonly Confused Water Concerns
1,2,3-Trichloropropane differs from many other water contaminants in its chemical behavior and treatment needs. It is not a metal, so it won’t cause typical metallic taste or staining. It does not behave like microbial contaminants, which are generally addressed differently in water treatment. Unlike volatile organic compounds that can be stripped by aeration, TCP resists such processes, requiring alternative technology. Understanding these distinctions helps avoid misidentifying water problems and ensures that solutions chosen target the actual issue.
Summary of the Public Water System Record and Where to Go for More Details
The Waterworks Board of Prattville’s federal monitoring results from 2013 to 2015 show no detections of 1,2,3-TCP above the 0.03 µg/L reporting level in the municipal surface water serving Autauga County residents. This record covers the system’s intake water and not individual household plumbing or post-treatment conditions. If your treatment equipment has failed and you suspect issues with 1,2,3-trichloropropane, testing your own water is essential. For treatment, the Fleck 1,2,3-TCP Filter ships ready to configure and is designed to address this chlorinated solvent effectively. For more detailed information on local water quality, refer to the EPA’s Safe Drinking Water Information System (SDWIS) public records for Waterworks Board of Prattville, AL0000017.
Where this information comes from
Source: EPA SDWIS public water system record. Sampled 2014-12-18. These figures describe the public water system's record, not the plumbing inside any individual building.
On record: EPA UCMR3 monitoring (2013-2015) for Waterworks Board of Prattville (AL0000017), AL: 25 results across 1 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level