HomeNewsArticle Display

Team Tinker unites to bring engine cells up

  • Published
  • By Brandice J. O'Brien
  • Staff Writer
TINKER AIR FORCE BASE, Okla. --  In late July, Team Tinker once again proved there's no "i" in teamwork.

Following an accidental fire suppression system dump on the industrial side of the base, several organizations came together to resolve the issue as soon as humanly possible. Their efforts proved successful and encouraging.

"Everyone went over and beyond to make sure we could continue the mission and operations. After determining what needed to be accomplished, all parties selflessly contributed to get it done. They understood the mission impact of the system remaining unserviceable for any length of time," said James Bradley, Tinker Fire and Emergency Services deputy fire chief. "It was a good barometer for how well agencies can work together in an urgent situation."

On the morning of July 25, a contractor in an engine test cell facility accidentally activated the carbon dioxide fire suppression system while training a coworker. The accident released 3,500 pounds of carbon dioxide into a test cell. Although the fire suppression system hadn't been used in several years and the carbon dioxide didn't cause damage to any of the other eight test cells, production was halted and the building's 50 personnel were evacuated. Officials brainstormed ways to keep the facility functional, as there were several engines in the facility which were very critical to get back online.

Firefighters used sound risk management practices to determine the accident compromised the safety of personnel. Without an operational fire suppression system in place there would be no effective measure for extinguishing an engine fire within a cell if there were a mishap. The 72nd Air Base Wing Civil Engineer Directorate's Tinker Support Services immediately went into action to replace the carbon dioxide agent, to their surprise there was simply no agent readily available in the state that could be delivered in time to get the 547th Propulsion Maintenance back in operation before the next shift.

Test-cell officials were told the refill would come from out-of-state and they would have to wait until the next week for the shipment arrival.

Chief Bradley said the fire department jumped at the opportunity to assist with removing any barriers or constraints that prevented an earlier delivery. Lt. Brian Maple, Tinker Fire Emergency Services logistics officer started making phone calls around the surrounding states to find a vendor that had enough agent on hand and was willing to make an emergency delivery to the base.

With a vendor located, payment and delivery details settled, the agent was in route from Louisiana that evening before close of business, fire officials offered to meet the truck at the gate and personally escorted the vehicle to the test cell facility and handed off to TSS personnel that were standing by on site ready for system servicing and reset after the agent was replaced.

"We just saw the need and helped where we could," the chief said.

In order to enable a smooth handoff, the chief said the 72nd Security Forces Squadron was informed about the situation prior to the truck's arrival. When the truck arrived, the handoff took just a matter of minutes.

"Security forces understood the importance," Chief Bradley said.

By 10 p.m., the refill had been completed and the test cell was functional again. Test-cell personnel had only missed a single shift.

"I don't know how it could have been controlled any better," said Steve Creek, 547th Propulsion Maintenance Squadron Test Cell Flight chief. "Everyone was evacuated; the fire department responded in a timely manner, TSS responded very quickly. Plus, 72nd ABW/CE, the fire department and TSS came up with a mitigation plan of things we could and could not do to get us back up and running and they got the tanks filled pretty quickly.

"I think the entire team did an outstanding job," Mr. Creek said. "It was excellently handled."

There are two engine test-cell facilities on base. On average, they test up to 40 engines a month for full functionality and the average test run takes three days, Mr. Creek said.