ORCHARD COMBAT TRAINING CENTER, Idaho \u2014 A heavy-lift drone climbed into 25 mph gusts above the high desert June 22, carrying a live Bangalore torpedo toward a wire obstacle.<\/p>\n<\/p>\n

For combat engineers, breaching that kind of obstacle is one of the most dangerous missions on the battlefield. Army doctrine accounts for that risk with a 50 percent casualty planning factor for a deliberate breach.<\/p>\n

This time, no Soldier had to sprint forward to place the charge.<\/p>\n

Soldiers from Bravo Company, 741st Brigade Engineer Battalion, 41st Infantry Brigade Combat Team, Oregon Army National Guard, used a drone-delivered Bangalore torpedo to breach the wire obstacle on Range 22. The drone released the charge, shock tube unspooled behind it and the Soldiers took cover before the Bangalore detonated, opening a lane through the wire.<\/p>\n

<\/p>\n

The proof of concept marked the close of a months-long innovation effort by the 741st BEB\u2019s drone working group. Battalion commander Lt. Col. Eric Zimmerman established the group with a directive to defeat a wire obstacle using a commercial off-the-shelf or similar drone during the battalion\u2019s annual training. The working group\u2019s research found no precedent for the tactic in the U.S. Army.<\/p>\n

\u201cMostly Ukraine,\u201d Zimmerman said when asked what drove the concept. \u201cWatching what was going on in Ukraine, and how innovative they are, it inspires you to get better and think bigger.\u201d<\/p>\n

<\/p>\n

The doctrinal cost of a breach added urgency to the effort.<\/p>\n

\u201cThe most casualty-producing thing that Army engineers do is the breach,\u201d said 1st Lt. Andrew Lucas, who co-led the working group from the battalion S-3 operations section. \u201cExpect 50 percent casualties. If you can deliver something to clear the breach with a $40,000 drone, instead of putting Soldiers in harm\u2019s way, that\u2019s worth experimenting with.\u201d<\/p>\n

<\/p>\n

Innovation surrounded by doctrine<\/strong><\/p>\n

Zimmerman said his intent was to apply emerging technology to a problem engineers already know how to solve.<\/p>\n

\u201cI want us to talk about drones around something we already do really well, which is defeating obstacles,\u201d he said. \u201cSo let\u2019s do this non-doctrinal thing, but surround it with doctrine.\u201d<\/p>\n

The working group was led by Lucas and Capt. Samuel Cushing, the battalion\u2019s plans officer, with input from senior noncommissioned officers, including 1st Sgt. Joshua Martin. The team first studied commercially available drones priced from $2,000 to $40,000.<\/p>\n

After funding for a commercial purchase did not come through, the team turned to the Oregon Army National Guard\u2019s 249th Regional Training Institute. The RTI\u2019s existing drone-build program could not produce an airframe with the lift capacity required by the mission. Lt. Col. Mark Timmons, the 249th RTI commander, told the working group his program could not meet the requirement within the available timeline.<\/p>\n

Rather than abandon the effort, the battalion operations section continued pursuing alternatives. Working from specifications developed by the drone working group, Maj. Harvey, the battalion S-3, and Martin, the battalion operations noncommissioned officer, vetted industry partners before determining Lorica Technologies could meet the requirement.<\/p>\n

When Lucas arrived for annual training, he believed the search had come up short.<\/p>\n

\u201cWe\u2019d been told no, it\u2019s not going to happen, we\u2019re not going to get a drone,\u201d he said. \u201cAnd that\u2019s when Maj. Harvey said, \u2018Oh, we actually got a drone.\u2019 So, full speed ahead.\u201d<\/p>\n

<\/p>\n

The Mule 28<\/strong><\/p>\n

Lorica\u2019s contribution was the Mule 28, a heavy-lift, multi-mission unmanned aerial system designed and built in-house at the company\u2019s Ashland facility.<\/p>\n

The airframe weighs about 45 pounds, can lift about 200 pounds and is powered by eight motors turning eight 28-inch bi-blade propellers. It carries onboard artificial intelligence processing, software-defined radios and a sensor package designed to support recognition and targeting functions. The drone can also derive coordinates from its camera using trigonometry and focal length, allowing it to mark drop points on objects it identifies.<\/p>\n

<\/p>\n

Lorica founder and CEO Christopher Dye said the company\u2019s software, including a swarm-control system called Hive, is what makes the platform distinct.<\/p>\n

\u201cIt doesn\u2019t matter what the vehicle is, as long as we understand the capabilities and the parameters of the vehicle,\u201d Dye said. \u201cWe can task the swarm based on what the job needs to get done. Right now, we\u2019re working on natural language control, so that you can just talk to the bird and tell it, \u2018Hey, 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.’\u201d<\/p>\n

Lorica currently fields three Mule 28 prototypes. The company had about six weeks to develop the airframe for the Oregon project.<\/p>\n

Cushing said working with a domestic manufacturer to build to specification, rather than buying a commercial drone with Chinese components, was a deliberate choice that helped reduce electronic warfare and supply chain vulnerabilities.<\/p>\n

\u201cIt\u2019s been helpful to have contractors that can meet every specification we\u2019re asking for and produce a drone that also meets the Army\u2019s intent for any sort of technology that we integrate,\u201d he said.<\/p>\n

Soldiers with Bravo Company, 741st Brigade Engineer Battalion, 41st Infantry Brigade Combat Team, conducted a proof-of-concept drone-delivered breach against a wire obstacle June 22, 2026, on Range 22 at Orchard Combat Training Center, Idaho. U.S. Army video by Maj. W. Chris Clyne, Oregon National Guard Public Affairs.<\/p>\n

Building the safety case<\/strong><\/p>\n

The team built safety into the project by increasing 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 progressed through limited live-fire iterations before flying a live, two-section M1A3 Bangalore torpedo.<\/p>\n

Every iteration involving live explosives 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.<\/p>\n

\u201cIdeally, you would love to be able to remote-detonate this without having to have a spool of shock tube,\u201d Lucas said. \u201cBut in the LSCO environment, we\u2019ve seen so many other systems jammed that if you have the ability to, it\u2019s not a detriment that we\u2019re doing it this way.\u201d<\/p>\n

The M1A3 Bangalore torpedo demolition kit consists of 10 tube sections, each 2.5 feet long and containing a 5-pound composition B4 main explosive charge. Doctrine permits up to four sections joined together for a single shot. The working group used two-section assemblies June 22 and made one small adjustment to prevent the blasting cap junction from pulling loose in flight.<\/p>\n

\u201cWe\u2019re trying to introduce a new TTP here anyway,\u201d Cushing said. \u201cWe want to see if we can deliver a Bangalore remotely and defeat a wire obstacle. Everything beyond that is something we\u2019ll take into consideration as the project evolves.\u201d<\/p>\n

<\/p>\n

Both working group officers said the broader value of the project is giving engineers a tool tailored to their core mission rather than relying only on infantry-focused drone applications that have dominated the field.<\/p>\n

\u201cMobility, counter-mobility is the bread and butter of the engineers, so we should focus on leaning into that versus infantry tasks,\u201d Lucas said.<\/p>\n

Cushing said the Bangalore breach could become a foundation for broader experimentation.<\/p>\n

<\/p>\n

\u201cThe platform they\u2019ve 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\u2019re talking about today.\u201d<\/p>\n

Lucas said the next conceptual step is autonomy.<\/p>\n

\u201cWe\u2019re 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, \u2018Hey, I know the obstacle\u2019s there,\u2019 and you could send it to autonomously deploy the Bangalore on the wire with near-perfect precision, where there\u2019s no possibility of it being jammed, because it\u2019s all running off of internal direction.\u201d<\/p>\n

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.<\/p>\n

Zimmerman said the successful demonstration reflected more than a new capability. It showed collaboration across the battalion.<\/p>\n

\u201cI\u2019m really proud. We have a true group project that highlights innovation across everything we do is possible,\u201d he said. \u201cThe Soldiers of Bravo Company took an idea from the battalion staff and applied their expertise to make that idea functional and effective.\u201d<\/p>\n

For Dye, watching the live Bangalore release and detonate as planned was, in a word, \u201crelief.\u201d<\/p>\n

\u201cIt\u2019s been very nerve-wracking the last few days,\u201d he said.<\/p>\n

The 741st BEB plans to capture lessons learned in a battalion white paper and forward the concept to the engineer community.<\/p>\n

By MAJ Wayne Clyne<\/em><\/p>\n

\n\t\t\t\t\t
\n\t\t\t\t\t\tThis entry was posted
\n\t\t\t\t\t\t\t\t\t\t\t\ton Tuesday, June 30th, 2026 at 00:00\t\t\t\t\t\tand is filed under Army<\/a>, Breaching<\/a>, Guest Post<\/a>.
\n\t\t\t\t\t\tYou can follow any responses to this entry through the RSS 2.0<\/a> feed.<\/p>\n

\t\t\t\t\t\t\t\t\t\t\t\t\tYou can skip to the end and leave a response. Pinging is currently not allowed.<\/p>\n

\t\t\t\t\t<\/small>\n\t\t\t\t<\/p>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"