Oregon engineers breach wire obstacle with drone-delivered Bangalore

ORCHARD COMBAT TRAINING CENTER, Idaho — A heavy-lift drone climbed into 25-mile-per-hour gusts above the high desert here June 22, 2026, carrying a live Bangalore torpedo toward a wire obstacle.

In combat, breaching that obstacle on foot would, on average, cost half the Soldiers ordered to do it. Army doctrine plans for it: a 50 percent casualty planning factor for the deliberate breach.

Oregon engineers breach a wire obstacle with a drone-delivered Bangalore. The drone released the charge. Shock tube unspooled cleanly behind it. Soldiers from Bravo Company, 741st Brigade Engineer Battalion, 41st Infantry Brigade Combat Team, took cover. The Bangalore detonated, opening a lane through the wire, a lane that, in this iteration, no Soldier had to sprint across to deliver.

The proof-of-concept on Range 22 marked the close of a months-long innovation effort by the 741st BEB's drone working group, established by battalion commander Lt. Col. Eric Zimmerman with a directive to defeat a wire obstacle using a commercial off-the-shelf or similar drone during the battalion's annual training. The working group's research found no precedent for the tactic in the U.S. Army.

"Mostly Ukraine," Zimmerman said when asked what drove the concept. "Watching what was going on in Ukraine, and how innovative they are, it inspires you to get better and think bigger." The doctrinal cost of the breach was the blunter argument.

"The most casualty-producing thing that Army engineers do is the breach," said 1st Lt. Andrew Lucas, who co-led the working group from the battalion S-3 section. "Expect 50 percent casualties. If you can deliver something to clear the breach with a $40,000 drone, instead of putting soldiers in harm's way, that's worth experimenting with."

Innovation surrounded by doctrine Zimmerman said his intent was to apply emerging technology to a problem engineers already know how to solve. "I want us to talk about drones around something we already do really well, which is defeating obstacles," he said. "So let's do this non-doctrinal thing, but surround it with doctrine."

The working group, led by Lucas and Capt. Samuel Cushing, the battalion's plans officer, with input from senior noncommissioned officers, including 1st Sgt. Joshua Martin first studied commercially available drones priced from $2,000 to $40,000. After funding for a commercial purchase did not come through, the team turned to the Oregon Army National Guard's 249th Regional Training Institute, whose existing drone-build program could not produce an airframe with the lift capacity the mission required. Lt. Col. Mark Timmons, the 249th RTI commander, told the working group his program could not meet the requirement in the available timeline.

Rather than abandoning the effort, the battalion's operations section continued pursuing alternatives. Working from the specifications developed by the drone working group, Maj. Harvey, the battalion S-3, and 1st Sgt. Martin, the battalion operations noncommissioned officer, vetted industry partners before determining that Lorica Technologies could meet the requirement.

When Lucas arrived for annual training, he believed the search had come up short.

"We'd been told no, it's not going to happen, we're not going to get a drone," he said. "And that's when Maj. Harvey said, 'Oh, we actually got a drone.' So, full speed ahead."

The Mule 28 Lorica's contribution was the Mule 28, a heavy-lift, multi-mission unmanned aerial system designed and built in-house at the company's Ashland facility.

The airframe weighs roughly 45 pounds, lifts approximately 200 pounds, and is powered by eight motors turning eight 28-inch bi-bladed propellers. It carries 128 trillion operations per second of onboard artificial intelligence processing, software-defined radios capable of listening and radio direction-finding across the 0-to-11-gigahertz spectrum, and a sensor package that supports facial, vehicle, and weapons recognition. The drone can derive coordinates from its camera using trigonometry and focal length, enabling it to mark drop points on objects it identifies.

Lorica founder and CEO Christopher Dye said the company's software, including a swarm-control system the company calls Hive, is what makes the platform distinct.

"It doesn't matter what the vehicle is, as long as we understand the capabilities and the parameters of the vehicle," Dye said. "We can task the swarm based on what the job needs to get done. Right now, we're working on natural language control, so that you can just talk to the bird and tell it, 'Hey, I want a reconnaissance around this building. I need to know how big that ditch is before we get there, how many steps, how high the windows are.'" Lorica currently fields three Mule 28 prototypes. The company had roughly six weeks to develop the airframe for the Oregon project.

Cushing said that going through a domestic manufacturer to build to specification rather than buying a commercial drone with Chinese components was a deliberate choice that protected the project from electronic warfare and supply-chain vulnerabilities.

"It's been helpful to have contractors that can meet every specification we're asking for and produce a drone that also meets the Army's intent for any sort of technology that we integrate," he said.

Building the safety case The team built safety into the project by stepping up the live-explosive risk in stages. The drone first carried an inert training aid identical in size and weight to the M1A3 Bangalore. Once the platform could reliably deliver an inert charge on target, the team flew an inert Bangalore with only a blasting cap installed, then a blasting cap with a wrap of detonating cord, and finally a live, two-section M1A3 Bangalore torpedo.

Every iteration involving live explosives, including the blasting-cap-only flights, was initiated using a shock tube spooled from the drone to the obstacle. The team deliberately avoided an electronic trigger that could be jammed or prematurely activated.

"Ideally, you would love to be able to remote-detonate this without having to have a spool of shock tube," Lucas said. "But in the LSCO environment, we've seen so many other systems jammed that if you have the ability to, it's not a detriment that we're doing it this way."

The M1A3 Bangalore torpedo demolition kit consists of 10 tube sections, each 2.5 feet long and containing a five-pound Composition B4 main charge. Doctrine permits up to four sections joined together for a single shot. The working group used two-section assemblies on June 22 and added one small departure from the field manual: extra tape around the blasting cap junction to prevent it from pulling loose in flight.

"We're trying to introduce a new TTP here anyway," Cushing said. "We want to see if we can deliver a Bangalore remotely and defeat a wire obstacle. Everything beyond that is something we'll take into consideration as the project evolves."

Mobility and counter-mobility Both working group officers said the broader value of the project lies in giving engineers a tool tailored to their core mission rather than borrowing from the infantry-led drone applications that have dominated the field so far. "Mobility, counter-mobility is the bread and butter of the engineers, so we should focus on leaning into that versus infantry tasks," Lucas said.

Cushing sees the Bangalore breach as a foundation. "The platform they've built, if we got an entire annual training with plenty of explosives, range time, and the ability to make modifications as we go, I think we could be defeating 10, 20 times more obstacles than we're talking about today."

Lucas said the next conceptual step is autonomy. "We're not that far technologically from a drone that has an AI processor on it that could identify where concertina wire is. And you could put in a rough coordinate of, 'Hey, I know the obstacle's there,' and you could send it to autonomously deploy the Bangalore on the wire with near-perfect precision, where there's no possibility of it being jammed, because it's all running off of internal direction."

Dye said the next iteration of the Mule 28 will refine flight controls, dropping mechanisms, and safety systems, with the goal of integrating AI-driven obstacle recognition that could allow the drone to identify a wire obstacle, position itself, and release the charge autonomously. Lorica plans to return to additional inert drops in the coming weeks and is preparing for follow-on demonstrations.

Zimmerman said the successful demonstration reflected more than a new capability; it showcased collaboration across the battalion.

"I'm really proud. We have a true group project that highlights innovation across everything we do is possible," he said. "The Soldiers of Bravo Company took an idea from the battalion staff and applied their expertise to make that idea functional and effective."

For Dye, watching the live Bangalore release and detonate as planned was, in a word, "relief." "It's been very nerve-wracking the last few days," he said.

The 741st BEB plans to capture lessons learned in a battalion white paper and forward the concept to the Engineer Community.