Recent articles in the Star Tribune bring this question to mind. Part of our interstate highway system collapses after over a decade of reports pointing out defects, after our DFL representative in Congress funneled transportation dollars away from highway and bridge repair to fund his pet projects, and the current governor is to blame? How you get to this conclusion is by distorting some facts, ignoring others, and playing on emotions, prejudices and ignorance.
Last weekend's article Phone call put brakes on bridge repair is a good example. It starts off with the language of high drama which, like the Jaws theme music, is meant to warn readers of an impending accusation of some heinous crime:
The men and women whose job was to ensure the safety of Bridge 9340 were meeting once again. Just after noon on Dec. 6, they filed into a conference room in Roseville to divvy up the final prep work for a dangerous steel reinforcement project high above the Mississippi River.
The scene is set. The drama begins. You can hear the scary music in your head. You just know the authors are about to break the biggest story ever on the 35W bridge collapse, and they've telegraphed ahead of time that they've got the current administration in their sights. The story strains to create dramatic effect with language, but falls short of coming up with any facts to support its innuendo:
But five weeks later, all those preparations stopped. In a single conference call on Jan. 17, the same consultants who said reinforcement plates were needed to strengthen the bridge cautioned MnDOT that drilling for the retrofit could weaken it.
"That was the turning point. That's where we turned the ship 180 degrees," said state bridge engineer Dan Dorgan.
Well, think about this a minute. MnDOT hired outside experts, who told them that drilling for the reinforcement plates could weaken the bridge. The experts also told MnDOT that the three options it presented were all "equally viable." Then MnDOT chose the option that did not present the danger of weakening the bridge.
Undeterred, the Strib article persists in its innuendo that MnDOT cared more about money than about safety:
Internal MnDOT documents reviewed by the Star Tribune reveal that last year bridge officials talked openly about the possibility of the bridge collapsing -- and worried that it might have to be condemned.
After going on at some length about MnDOT's worries about a bridge collapse, the article buries on the next page the explanation of why MnDOT decided that a collapse was not likely:
Dorgan didn't want the consultant to mince words when it came to explaining what would happen if a fracture-critical beam in the superstructure failed.
"If the conclusion is the instability would likely lead to the collapse of the bridge, that should be stated clearly," Dorgan wrote.
So, MnDOT clearly asked the outside experts if a bridge collapse was likely, and Dorgan made sure to put this in writing so that there would be no question that he had asked the question. And the experts did not say that the bridge's defects were serious enough to replace the bridge at that time.
And never mind that, in 2001, a report by the University of Minnesota Department of Civil Engineering had concluded after a fatigue evaluation that this bridge did not need to be replaced prematurely.
Actually, the facts reported in this article support Governor Pawlenty's initial explanation: the San Francisco contractor MnDOT hired never told them that the bridge's condition was so bad they were looking at a collapse if a fracture-critical beam failed, and the contractor told MnDOT that the drilling necessary to reinforce the bridge might actually weaken it.
But of course, you have to read the whole article to get to these facts, and be willing to distinguish between the manipulative rhetoric and the facts. Once you do that, you end up asking, "where's the beef?"