October 26, 2007 By Chandler Harris
Feb. 5, 1957, began like every other day for Jerry Fenwick, who worked at his family's paint and art supply store in downtown Reno, Nev. Yet on this day, Fenwick decided not to check on his prize 1957 Dodge Custom Royal Lancer, which was being modified at the local repair shop a few blocks away, as he usually did on his lunch break.
The decision most likely saved his life. Fenwick's usual stroll would have put him at the corner of First and Sierra streets right around the time of a deadly blast.
Alerted by complaints of strong gas odor, a crew of five firefighters had converged on to the intersection, evacuating surrounding buildings. Moments later, at 1:03 p.m., two gas-fueled explosions 30 seconds apart shook downtown Reno, completely destroying two buildings, killing two people and injuring dozens. Fenwick, still at work two blocks away, said he had no injuries, and that most of those harmed were on the same block as the blast.
Though the explosions were at ground level, they were strong enough to register seismic reverberations equivalent to a 1.5-magnitude earthquake, according to the University of Nevada's Mackay School of Mines.
"I felt a terrible loud thump like something had been dropped," Fenwick said. "I turned around and saw the old-fashioned door jam lifted off the post three inches. That's when I knew something radically was wrong. I looked down the street and saw huge pieces of roof drifting down."
The blast was so strong it shattered windows in a block-and-a-half radius, said Jim Paterson, who at the time of the blast worked at Paterson's - one of the buildings that was completely demolished.
"The blast took the roof off the building where I worked and dumped it on the street," Paterson said.
Reno firefighter Bill Shinners was outside Paterson's when the blast hit; when he looked up, the sky was red. Shinners and other firefighters fought the fire for about 36 hours without any sleep. After the first seven hours, Shinners stole a needed break on top of the aerial fire ladder.
"I got up there to relax and started to shake uncontrollably," Shinners said. "I think I was in a state of shock."
The explosion was caused by a ruptured gas main that filled an undetermined area with gas before igniting. Damage from the blast was estimated to be more than $7 million, according to the Reno Gazette-Journal.
Fifty years later, new technologies, added safety precautions for emergency responders, more stringent building codes and stricter gas line controls imposed by energy companies have lessened the chances for another gas-fueled explosion in Reno, said Marty Scheuerman, division chief of the Reno Fire Department and emergency manager of the city.
Today, firefighters' technological arsenal includes devices that detect the presence of flammable vapor in the air and lower and upper explosion limit of gases, which determine if a structure or area is safe from potential explosions, Scheuerman said. Firefighters also carry an assortment of equipment for plugging gas line leaks, and are trained on how to approach and contain pressure leaks.
Gas line maps and computerized building schematics have improved firefighters' ability to shut off potentially deadly gas lines if a leak is detected or before approaching a fire, Scheuerman said. Sierra Pacific Power, the local gas and electric company, also has extensive mapping systems of gas lines and excess flow valves that automatically shut gas flow off when a leak is detected.
Reno now has a large natural gas pipeline that flows from Canada and is equipped with infrared monitors that detect the presence or leakage of flammable vapor.
Even with more advanced technology and mapping, however, another gas-fueled explosion isn't entirely improbable, especially in
This Digital Communities white paper highlights discussions with IT officials in four counties that have adopted shared services models. Our aim was to learn about the obstacles these governments have faced when it comes to shared services and what it takes to overcome those roadblocks. We also spoke with several members of the IT industry who have thought long and hard about these issues. The paper offers some best practices for shared government-to-government services, but also points out challenges that government and industry still must overcome before this model gains widespread adoption.