Water Safety

Lethal pesticides poison the water supply

A cross-connection incident drew widespread attention. Here's what happened and what utilities can do to prevent it.

Cross-connection incidents are rare, and that is exactly what makes them dangerous — programs get built around risks people see regularly. When contamination does reach a distribution system, the cause is almost never exotic. It is an unprotected connection nobody had on a list.

How contamination reaches the main

Two mechanisms account for nearly all of it. Backsiphonage happens when pressure in the main drops below pressure on the customer side — a break, heavy hydrant draw during firefighting, or a shutdown for repairs — and the system draws water backward. Backpressure happens when a customer's system operates at higher pressure than the main, such as a booster pump, an elevated tank, or a chemical injection loop, and pushes fluid into the service line.

Either way, whatever is connected on the customer side can enter the public supply: irrigation water carrying applied pesticides or fertilizer, boiler treatment chemicals, process fluid, or wastewater.

Why irrigation connections deserve particular attention

Irrigation systems combine several risk factors. They are directly connected to potable service, they sit at or below grade where standing water pools, and the water in them may contain applied lawn and agricultural chemicals. Many were installed by landscape contractors rather than plumbers, and some were never registered with the utility at all. An assembly that was correct at installation may since have been bypassed during a repair.

What utilities can actually do

  • Survey premises, don't assume. Hazard classification based on business type alone misses the property that added an irrigation loop or a chemical feed after its last survey.
  • Close the inventory gaps. Unregistered devices and unregistered connections are the same exposure; both need a field pass to resolve.
  • Enforce the test cycle. A required assembly that has not been tested in years is documentation, not protection.
  • Respond to failures on a clock. Repair-and-retest windows only work when someone is tracking them.
  • Coordinate with operations. Planned shutdowns and main work are the exact conditions that create backsiphonage; high-hazard connections in the affected zone should be known before valves move.

What property owners can do

Have your assemblies tested on schedule by a certified tester, keep the enclosure accessible, and never bypass a device during a repair — even temporarily. If you add irrigation, a booster pump, or any chemical feed, tell your water utility. The device that protects the neighborhood also protects your own building's plumbing.

The underlying lesson

Cross-connection control is unglamorous work: maintaining a list, sending notices, chasing overdue tests, and following up on failures. It gets attention after an incident and competes for resources before one. The utilities that stay ahead of it are usually the ones that stopped running the program manually — because the failure mode isn't a lack of intent, it's a due date nobody saw.

VEPO CrossConnex was built to remove that failure mode: a live device inventory, automatic notification of owners and testers, direct mobile test submission, and compliance reporting that is ready before an inspector asks. If you're reviewing your own program's exposure, we're glad to talk it through.

Talk to our team

Questions on this topic, or planning something similar at your utility? Send us a note.

Contact VEPO Solutions

More insights from the VEPO team

Browse the rest of the VEPO blog for practical thinking on backflow, AMI, and work order management.

Back to Blog