Trenchless solutions for aging Orangeburg sewer pipes

(UI) – Inexpensive pipes made of wood fiber and tar were installed in many homes built between 1945 and 1972. Orangeburg pipes, named after the town in New York that was the main manufacturing source, were expected to last 50 years or more, but often showed signs of serious deterioration after just 30 years.

Any existing Orangeburg systems are likely to be compromised by pressure and age and could pose a high risk of emergency failure. Some of the signs that Orangeburg home sewer pipes need immediate service or replacement include frequent clogs, reduced water pressure, damp spots or indentations on the lawn, noticeable odors, mold, or sudden increases in water usage or utility costs.

"Orangeburg pipes were popular throughout Tacoma and the surrounding area, and those original pipes are still in place in many older homes around here," said Richard Hart, co-owner of Harts Services. "We urge anyone whose home was built before 1980 to schedule an inspection to check the condition of the sewer pipes and determine the right course of action to prevent an emergency." 

Modern trenchless technology offers several solutions for aging or failed Orangeburg pipes, depending on the age and condition of your home's sewer system. Advanced pipe relining or pipe bursting services are available in many cases to reinforce or replace old pulp pipes with PVC while avoiding the expense and inconvenience of excavation.

"We're reaching the point with Orangeburg pipe systems where a lot of homeowners could be facing big decisions soon," Hart said. "The good news is that trenchless technology and video inspection offer incredible precision and efficiency that have transformed sewer service. We can diagnose all the issues that need to be addressed and, in most instances, deliver the right solution without digging up your front yard, which saves everyone time, effort and money."

Related News

From Archive

Comments

{{ error }}
{{ comment.comment.Name }} • {{ comment.timeAgo }}
{{ comment.comment.Text }}