Understanding 1,2,3-TCP in Martinsburg Berkeley County Water and Technical Treatment Options

Assembled 16x65 inch composite AIO filter with approved blue and white WaterSoftenerPlus Mylar on installed head

$1,450.00

Whole House 1,2,3-TCP Reduction Water Filter System - Trichloropropane Removal

View full details

✓ Free shipping in the USA  ·  ✓ 90-day returns  ·  ✓ Secure checkout

Whole House 1,2,3-TCP Reduction Water Filter System - Trichloropropane Removal

Whole House 1,2,3-TCP Reduction Water Filter System - Trichloropropane Removal

Buy Now

View full details

Water in Martinsburg, Berkeley County, is supplied through a public water system that serves over 16,000 residents using surface water sources. This water is treated and distributed to homes, including yours, through municipal connections. The federal EPA has monitored the City of Martinsburg’s water for contaminants including 1,2,3-trichloropropane, also known as 1,2,3-TCP or simply TCP, a chlorinated solvent sometimes detected in water supplies.

Why is the reporting level for 1,2,3-TCP set much lower than for common metals?

The reporting level established for 1,2,3-TCP in the EPA’s Unregulated Contaminant Monitoring Rule (UCMR) is 0.03 micrograms per liter, or parts per billion. This threshold is substantially lower than limits set for common metals due to differences in chemical properties and potential health considerations. A reporting level acts as a detection threshold for monitoring rather than a safety limit. It enables sensitive laboratory instruments to identify even trace concentrations that might warrant further study. For metals like iron or manganese, higher reporting or action levels apply given their typical occurrence and effects. Thus, the low reporting level for TCP reflects the need to track even minimal presence of this synthetic solvent in water systems.

How do aesthetic secondary standards differ from health-based limits for this contaminant?

Aesthetic secondary standards address factors like taste, odor, and staining rather than health risks. For 1,2,3-trichloropropane, there are no EPA-established aesthetic secondary standards because it does not commonly cause such effects at typical levels. Health-based considerations focus on potential toxicity rather than sensory impact. The Martinsburg public water system has no health-based violations recorded for TCP, meaning detected levels remain within ranges considered acceptable by federal health guidelines. This distinction clarifies that detection does not equal an adverse health effect.

How should I compare Martinsburg’s 1,2,3-TCP data with neighboring counties without overreading the information?

Data available from Martinsburg’s public water system indicate zero detections above the 0.03 µg/L reporting level for TCP in monitoring conducted during 2014. When comparing with nearby counties, it’s important to recognize that absence of detection in Martinsburg does not guarantee the same for other areas, nor does detection elsewhere imply a problem here. Each system’s monitoring methods, source waters, and chemical presence can vary. Avoid interpreting detected presence as a violation or assuming non-detection means absence in private wells. Use the data as context for whether further testing in your home is warranted.

What additional questions might a commercial or industrial water user consider compared to a household?

Commercial and industrial users may face higher water volume demands, regulatory compliance requirements, and process sensitivities that differ from household concerns. They often need detailed contaminant profiles affecting operations or product quality and might require specialized treatment designs or certifications. While households focus mainly on health and aesthetic impacts at the tap, businesses may also consider continuous monitoring, treatment scalability, and regulatory reporting. These factors can influence the choice between technical approaches to managing chemicals like TCP.

What do the terms ‘detected’, ‘median’, and ‘range’ mean in the public water system sampling record here?

  • Detected: Indicates a laboratory measurement identified the presence of a chemical at or above the reporting level. Detection does not equal a violation or unsafe condition.
  • Median: The middle value in a set of measurements, providing a typical concentration estimate when multiple samples are tested.
  • Range: The difference between the lowest and highest measured values in the sample set, showing variability.

For Martinsburg’s water, all eight samples for 1,2,3-TCP from 2014 were below the reporting level, so detection was zero. Thus, median and range values for TCP were not established above this threshold.

How do public water system records differ from private well testing in establishing 1,2,3-TCP levels?

Public water system records like those from Martinsburg reflect aggregate monitoring of water as treated and distributed to many consumers. They provide a broad overview of water quality but do not establish specific levels in individual homes or private wells. Private well water quality can differ substantially due to local geology, well construction, and lack of centralized treatment. Testing your own water supply is the only way to confirm the presence and concentration of TCP or other constituents at your taps.

For residential households weighing technical options to address 1,2,3-trichloropropane, the Autotrol 1,2,3-TCP Filter offers a direct-purchase solution. It ships ready to configure and is designed to reduce TCP levels based on the demand figures measured in your water. Evaluating your water test results alongside this documented technology can support an informed choice tailored to your home’s water quality needs.

Where this information comes from

Source: EPA SDWIS public water system record. Sampled 2014-11-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 City of Martinsburg (WV3300212), WV: 8 results across 1 listed contaminants, 0 detections above the reporting level; nothing detected above the method reporting level