For a town full of motorists locked into their driving patterns, where the closure of a Downtown bridge constitutes a major commuting catastrophe, Monday’s surprise announcement that the fire-ravaged Liberty Bridge would reopen by evening rush hour provided cause for celebration.

Detour-weary drivers wasted no time flocking to the 88-year-old span, a vital artery between Downtown and the South Hills, which had shut down 24 days earlier after a worker’s errant torch ignited plastic piping, then a tarp, and burned so hot that it warped a key structural steel support.

Questions arose after the fire: What will we do? How long will it last? How will we get there from here?

After grappling with the dilemma for weeks and solving it with a zigzag of detours and new, unfamiliar routes, commuters suddenly had answers that made as much sense to them as a straight line. The bridge was back in business, all thanks to a hydraulic jacking system employed last week. By shifting the damaged chord — as the distorted lower support of the bridge is called — by 1⅝ inches longitudinally and 1¼ inches laterally, engineers were able to give their blessing to the reopening of a bridge that carries 55,000 vehicles a day.

Advertise with us

But although many took to the roads Monday afternoon to display confidence in the repaired span by simply driving across it, others took to social media to question the safety of the Liberty Bridge or convey their unease at traveling on it.

“Still nope,” one person tweeted. “I wouldn’t step on that bridge let alone drive on it with other vehicles,” tweeted another. “You’d have to pay me to ride on the #LibertyBridge #ItsGonnaFall,” a third tweeted.

Nonsense, said Dan Cessna, local district executive for the state Department of Transportation.

“The reality is, if the bridge wasn’t safe, we wouldn’t reopen it,” Mr. Cessna said, during a Monday afternoon news conference on the South Side. Serving as a backdrop to Mr. Cessna’s announcement: the bridge that would be empty for only another 45 minutes or so before hosting the sweet sounds of traffic once again.

Not everyone will benefit right away from the long, hard hours put in to repair the bridge by PennDOT, its consultants and the Joseph B. Fay Co., the contractor for an ongoing $80 million renovation project that was the unhappy catalyst for the closure.

Advertise with us

For now, there will be a nine-ton weight limit on vehicles crossing the span. Cars, pickup trucks and ambulances are good to go. But firetrucks, school buses, Port Authority buses, tractor-trailers and empty tri-axle trucks will be forbidden. Mr. Cessna said the Pennsylvania State Police will conduct spot checks on vehicle weights.

If all goes according to plan, that weight limit will jump to 30 tons over the next few weeks, Mr. Cessna said. The side of the bridge opposite from where the fire occurred must be bolstered first, a task that can be accomplished without disrupting traffic. With the jacking of the bridge to rotate and realign the damaged chord, about 80 percent of the load was shifted back to the support. But the remaining 20 percent of the load has to be picked up by the chord opposite it.

“Basically we have to strengthen the other chord to carry that additional load that didn’t shift back. That’s going to require additional steel plates and angles. That’s currently being designed and will be installed very shortly,” Mr. Cessna said.

A permanent repair is still in the works, and once that is done, PennDOT anticipates the bridge will once again be able to accommodate a 40-ton weight limit.

During his news conference, Mr. Cessna could not resist teasing the media. He said that PennDOT knew Sunday that the bridge would reopen the next day, pending some final steel strengthening and the introduction of updated signage with the nine-ton weight limit.

Advertise with us

“All the placards have been changed this afternoon,” Mr. Cessna said. “We expected one of you would pick up on that. Nobody contacted us.”

Jonathan D. Silver: jsilver@post-gazette.com, 412-263-1962 or on Twitter @jsilverpg.