Edwards AFB provides ordnance disposal support to March ARB

Tech Sgt. James Bennett and Airman 1st Class David Lane, both from 812th Civil Engineer Squadron, Explosive Ordnance Disposal, was part of a team that responded to a call for assistance following an F-16 crash at March Air Reserve Base in Riverside, Calif., recently. (U.S. Air Force photo by Giancarlo Casem)

Tech Sgt. James Bennett and Airman 1st Class David Lane, both from 812th Civil Engineer Squadron, Explosive Ordnance Disposal, was part of a team that responded to a call for assistance following an F-16 crash at March Air Reserve Base in Riverside, Calif., recently. (U.S. Air Force photo by Giancarlo Casem)


An Explosive Ordnance Disposal team from Edwards Air Force Base, California, recently provided support to nearby March Air Reserve Base in Riverside, following an F-16 crash incident.

The three-man team from the 412th Test Wing’s 812th Civil Engineer Squadron were onsite within hours of the call for support and promptly rendered the site safe from unexploded ordnance dangers.

“When the flag goes up asking for EOD assistance, the team never knows what to expect,” said Maj. Brian Anderson, 812th CES Commander. “All they know is that their unique skillset is needed – there’s no one else that can cover down to fill this mission if they’re unable or unavailable.” 

The three-man, EOD stand-by team was led Tech Sgt. James Bennett, operations section chief. He said that despite his years of experience, this particular situation was new and unique.

“Having an aircraft crash just off-base and inside a civilian building, I’ve never seen that before,” Bennett said. “It was completely different for all the guys, for one of my guys, it was actually it was his first stand-by call.”

Bennett said that EOD responds to calls on Edwards during flights with hung ordnance. They also respond to local areas when old munitions are discovered and provide support to local authorities all over the Southern California region.

“We don’t normally get calls at three in the morning,” he said.

The F-16 crash outside of March caused impact to the surrounding communities due to the closure of a nearby freeway; after clearing the building of hazards, the freeway was reopened.

“Explosives often trump other hazards, and everything is basically shut down within the associated cordon,” Anderson said. “It is imperative to arrive on scene as quickly as possible. When responding on-base, this will help the Wing to get back on mission. When off-base, this will help businesses and roads to reopen, and for people to go back to their homes.”

Bennett and his team used the almost two-hour long drive from Edwards to March to review procedures and tasks to ensure the ordnance was disposed of properly.

“There’s a lot of training that goes into it before, we were talking about on the drive down,” Bennett said. “You have to know what to look for, we talked about hazards, what local agencies are going to be concerned about. All the training we’ve done before helps.”

Bennett also took the opportunity to train and mentor his team. He reminded his team to watch out for everybody and to be careful in an unknown environment with uncertain conditions of the munitions.

“Most definitely used as a real-world training opportunity,” Bennett said. “It was good for them to see how everybody works together, the different ways of communication, the different verbiage that they use. It is really rare for us to get to do a disposal like that off-base.”

Bennett said that the importance of training with other agencies showed its value during their mission to March.

“We had a really good pass off from the (EOD team) down there, there was really good communication,” Bennett said. “We’ve done some training operations with some of the March guys up here, we like to go in very prepared.”

Anderson attributed to the team’s safety and success to training and a whole team effort.

“I am extremely proud of my entire team, not just those few who directly participated in this response and their performance this one time,” Anderson said. “This was truly a team effort stemming back to countless hours in the shop, training and working to ensure the equipment is ready to go. The whole Flight has to pull their weight to ensure mission success. This was a team win.”

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.

News Search