HomeNewsArticle Display

Team Malmstrom assists with determining threat level of suspicious pacakage

Ryan Burke, 341st Civil Engineer Squadron fire department member, checks the vital signs of Senior Airman Zalman Kosofsky before he suits up and enters the incident site on the Blackfeet Indian Reservation in Browning, Mont., Jan. 24. Team Malmstrom personnel were responding to a report of a suspicious package found in the Tribal Offices there.

Ryan Burke, 341st Civil Engineer Squadron fire department member, checks the vital signs of Senior Airman Zalman Kosofsky before he suits up and enters the incident site on the Blackfeet Indian Reservation in Browning, Mont., Jan. 24. Team Malmstrom personnel were responding to a report of a suspicious package found in the Tribal Offices there.

MALMSTROM AIR FORCE BASE, MONT. -- A 13-person team from three organizations at Malmstrom were called out to assist officials of the Blackfeet Tribal community with determining the contents of a suspicious package found on the reservation in Browning, Mont., Jan. 24.

"We initially received the call from the command post about 2 p.m.," said Capt. Aaron Weaver, 341st Medical Operations Squadron bioenvironmental flight chief who also acted as the operations section chief for the response. "But it wasn't until 7 p.m. before we departed for Browning."

What transpired in those five hours was a large amount of coordination between agencies capable of responding to this type of situation to determine who was bringing what assets to properly handle the imposing threat.

Seven members of the fire department's hazmat decontamination team and four members each from bioenvironmental flight and the emergency management flight arrived in the northern Montana city about 9:30 p.m. They were met by members of the Fort Harrison Civil Support Team as well as local officials and the on-scene commander from the Federal Bureau of Investigation.

"Fort Harrison responded with their mobile lab and a chemist but were unable to support the response with anyone else because their certifications had expired," said Master Sgt. David Wheeler, 341st Civil Engineer Squadron readiness flight superintendent. "By law, the closest federal agency with full capabilities is required to support when all other means are exhausted. Malmstrom was that agency."

While Captain Weaver was updated by the incident commander, the remaining team members prepared for action. The decontamination team set up their stations and the site entry team prepared to enter the facility and assess the situation.

"The information they gave us about the incident sounded just like a scenario given to us by the EET [exercise evaluation team] during an exercise," said Senior Airman Zalman Kosofsky, 341st MDOS bioenvironmental engineering flight member and also one of those tasked for the site entry team. "I felt totally confident in my abilities to perform my role on the entry team."

The team spent nearly an hour using their various equipment to test the suspicious package's contents and eliminate each type of hazard it could possibly be, according to Sergeant Wheeler. The next step was to collect enough of the sample material to put through more stringent testing in the CST lab.

"Most training scenarios do not get 'played' all the way out," said Airman 1st Class Michael Addy, a site entry team member who aided in collection and removal of the evidence. "It was helpful to take a scenario from start to finish."

Third team member and the one responsible for opening the suspicious package Senior Airman Kyle Kidwell agreed with his teammate.

"I'm glad we have real calls because it lends legitimacy to my job," he said. "On the other hand, I worry about the people that were possibly infected with deadly materials."

The final task was to get everyone and everything out of the "hot zone."

"Each person and their equipment had to be decontaminated, as did the samples being brought out for testing," Captain Weaver explained. "The process took about 30 minutes and went very smoothly."

Once the site entry team was processed and the samples were delivered to the lab, the "response" portion of the incident was over.

"We responded exactly like we practiced," Airman Kosofsky said. "As an integrated team, communications flowed very efficiently."

Bioenvironmental engineer personnel alongside the CST chemist then conducted extensive tests on the sample.

"Our efforts were able to confirm the suspicious package did not pose a creditable radiological, biological or chemical threat to the Blackfoot Indian community at any time during this response," Captain Weaver said.

The Integrated Weapons of Mass Destruction Response Team, also known as I-WMDRT, worked cohesively, according to Captain Weaver. "This was the first real-world, off-base response for the I-WMDRT and they displayed excellent team work," he said. "I even received a compliment from Army Capt. Juan Stevens, the nuclear medicine science officer from Fort Harrison. He was very impressed with how well the team worked together - especially the entry team."

"Very often it's easy to get lax, especially here in Montana, so far away from the fight," Airman Kosofsky said. "But this was somewhat of a wake-up call. You never know when the fight is going to come to you. You always need to be prepared."
USAF Comments Policy
If you wish to comment, use the text box below. AF reserves the right to modify this policy at any time.

This is a moderated forum. That means all comments will be reviewed before posting. In addition, we expect that participants will treat each other, as well as our agency and our employees, with respect. We will not post comments that contain abusive or vulgar language, spam, hate speech, personal attacks, violate EEO policy, are offensive to other or similar content. We will not post comments that are spam, are clearly "off topic", promote services or products, infringe copyright protected material, or contain any links that don't contribute to the discussion. Comments that make unsupported accusations will also not be posted. The AF and the AF alone will make a determination as to which comments will be posted. Any references to commercial entities, products, services, or other non-governmental organizations or individuals that remain on the site are provided solely for the information of individuals using this page. These references are not intended to reflect the opinion of the AF, DoD, the United States, or its officers or employees concerning the significance, priority, or importance to be given the referenced entity, product, service, or organization. Such references are not an official or personal endorsement of any product, person, or service, and may not be quoted or reproduced for the purpose of stating or implying AF endorsement or approval of any product, person, or service.

Any comments that report criminal activity including: suicidal behaviour or sexual assault will be reported to appropriate authorities including OSI. This forum is not:

  • This forum is not to be used to report criminal activity. If you have information for law enforcement, please contact OSI or your local police agency.
  • Do not submit unsolicited proposals, or other business ideas or inquiries to this forum. This site is not to be used for contracting or commercial business.
  • This forum may not be used for the submission of any claim, demand, informal or formal complaint, or any other form of legal and/or administrative notice or process, or for the exhaustion of any legal and/or administrative remedy.

AF does not guarantee or warrant that any information posted by individuals on this forum is correct, and disclaims any liability for any loss or damage resulting from reliance on any such information. AF may not be able to verify, does not warrant or guarantee, and assumes no liability for anything posted on this website by any other person. AF does not endorse, support or otherwise promote any private or commercial entity or the information, products or services contained on those websites that may be reached through links on our website.

Members of the media are asked to send questions to the public affairs through their normal channels and to refrain from submitting questions here as comments. Reporter questions will not be posted. We recognize that the Web is a 24/7 medium, and your comments are welcome at any time. However, given the need to manage federal resources, moderating and posting of comments will occur during regular business hours Monday through Friday. Comments submitted after hours or on weekends will be read and posted as early as possible; in most cases, this means the next business day.

For the benefit of robust discussion, we ask that comments remain "on-topic." This means that comments will be posted only as it relates to the topic that is being discussed within the blog post. The views expressed on the site by non-federal commentators do not necessarily reflect the official views of the AF or the Federal Government.

To protect your own privacy and the privacy of others, please do not include personally identifiable information, such as name, Social Security number, DoD ID number, OSI Case number, phone numbers or email addresses in the body of your comment. If you do voluntarily include personally identifiable information in your comment, such as your name, that comment may or may not be posted on the page. If your comment is posted, your name will not be redacted or removed. In no circumstances will comments be posted that contain Social Security numbers, DoD ID numbers, OSI case numbers, addresses, email address or phone numbers. The default for the posting of comments is "anonymous", but if you opt not to, any information, including your login name, may be displayed on our site.

Thank you for taking the time to read this comment policy. We encourage your participation in our discussion and look forward to an active exchange of ideas.