From Red Sea Defense to Epic Fury: How the U.S. Flipped the Drone Cost Equation
When U.S. destroyers first found themselves in the high-tempo contest with Houthi missiles and drones in the Red Sea, the image that dominated public debate was stark: multi-million-dollar interceptors being used to shoot down relatively cheap one-way attack drones. Analyses routinely framed this as a two-million-dollar missile being fired against a two-thousand-dollar drone, and the broader narrative was that the U.S. Navy was winning tactically but losing strategically on cost and magazine depth. The math was visible to everyone watching, and its implications were deeply uncomfortable for planners wrestling with finite munitions stockpiles and constrained production lines.
That calculus has now been inverted in Operation Epic Fury against Iran. Instead of relying primarily on exquisite, small-lot interceptors and strike missiles, U.S. Central Command is using its own massed, low-cost drones, epitomized by the LUCAS system, to impose costs on Iran’s air-defense network and strike complex.
What began as a defensive cost-exchange crisis in the Red Sea has become an offensive cost-imposition strategy over Iran. The U.S. military, in a compressed and urgent adaptation cycle, has moved from absorbing a painful asymmetry to weaponizing it.
This article traces how that shift occurred: from the original Red Sea problem set, through interim adaptations, to LUCAS, Epic Fury, and the emerging industrial base for “cheap mass.” It is a story about more than a single system or a single campaign. It is a story about how the United States military, when confronted with an unsustainable cost exchange, found a structural answer rather than settling for marginal improvements to a failing model.
The Red Sea campaign against Houthi attacks on commercial and naval shipping exposed a fundamental asymmetry between cheap Iranian-supplied drones and missiles and the U.S. Navy’s defensive architecture. Aegis destroyers and other surface combatants leaned heavily on high-end interceptors, SM-2, SM-6, and ESSM, to defeat incoming threats. The ships racked up an impressive kill record, demonstrating that the existing kill-chain architecture could handle the Houthi threat in kinetic terms. But each of those intercepts came at a steep price, and the cumulative cost was generating serious strategic concern.
The problems were interlocking. Interceptors costing in the low-to-mid millions per shot were routinely being used against drones costing orders of magnitude less. Every SM-2 or SM-6 expended on a low-end drone was one less round available for a more stressing contingency, a conventional anti-ship missile salvo, a ballistic threat, a peer competitor’s strike package. And the production lag for replenishing those high-end interceptors runs to years, not weeks or months, placing severe strain on an already constrained munitions industrial base. By mid-2024, senior Navy and Defense officials were openly describing this reliance on top-tier interceptors as “unsustainable” if it continued at scale. Independent analyses estimated that the Navy had already spent the better part of a billion dollars on missile defense in the Red Sea and Israel contexts alone, and the trajectory was deeply unfavorable.
Operationally, the architecture remained a classic linear defensive kill chain: sensors feed a ship’s combat system, which decides on weapons employment, often defaulting to the most capable and expensive interceptors available because threat uncertainty demanded it. The focus was protecting force and shipping, not imposing costs on the adversary. The U.S. Navy was tactically winning engagements while strategically hemorrhaging capability stocks that could not be quickly replenished.
Something had to change.
Before anything resembling LUCAS entered the picture, commanders worked to bend the existing construct toward cheaper engagements. Fighters and other aircraft increasingly employed guided rockets and other relatively low-cost weapons in intercept roles, reducing cost-per-kill compared to air-to-air missiles. Where threat profiles allowed, ships expanded their use of guns and lower-tier interceptors rather than defaulting to SM-2 or SM-6 for every track. Coalition partners were brought in more systematically, contributing additional sensors and shooters to spread the cost and engagement burden across a broader set of forces. These were genuine improvements at the margin, and they helped.
But they remained fundamentally inside the old box.
None of these interim measures overturned the basic cost-exchange dynamic. The U.S. remained largely on the back foot, defending shipping and burning high-end magazines faster than they could be replenished. What was needed was not a cheaper version of the same defensive architecture but a fundamentally different approach that shifted the burden of expensive expenditure onto the adversary. The Red Sea campaign had identified the problem with brutal clarity.
The next phase would provide the structural answer.
The real shift begins with LUCAS, a U.S.-produced low-cost one-way attack drone derived from the Iranian Shahed family. Admiral Brad Cooper’s public description of its origins is deliberately vivid: U.S. forces captured a Shahed, took it apart, shipped it home, reverse-engineered and modified it, then brought back the resulting system, now labeled “Made in America”, and deployed it in combat against Iran’s own defenses. There is something almost poetic about the reversal. Iran’s decision to supply Houthi forces with cheap drones that imposed costs on U.S. naval operations has yielded a direct response: an American copy of the weapon turned back against Iran at scale.
The attributes that make LUCAS strategically significant are straightforward. Unit costs run to roughly thirty to forty thousand dollars per airframe, depending on the variant. The system provides hundreds of kilometers of range with a warhead sufficient to threaten air-defense sites, radar emitters, command nodes, and logistical infrastructure. Critically, LUCAS relies on commercial-grade engines and electronics combined with an open-architecture design for seekers and guidance, enabling multiple vendors to produce compatible variants and supporting parallel production lines at civilian industrial rates rather than the bespoke defense-industry pace typical of high-end munitions.
Conceptually, LUCAS is not an isolated gadget. It is a deliberate structural answer to the cost-exchange problem.
Instead of firing scarce, expensive missiles at cheap Iranian drones, the U.S. now fields cheap American drones that force Iran to expend expensive surface-to-air missiles, expose its air-defense network to detection and targeting, and degrade its layered defenses over time.
In Epic Fury, LUCAS is being employed in large numbers as part of a joint strike complex against Iran’s missile, air-defense, and nuclear-related infrastructure. Hundreds to low thousands of LUCAS rounds are reportedly either planned or already expended, with senior commanders describing the system as indispensable to the campaign’s execution.
The Red Sea fight was dominated by a ship-centric, defensive kill chain. Epic Fury, by contrast, operates more like a distributed kill web in which LUCAS is one node among many. The distinction matters enormously. A kill chain is linear: a specific sensor detects a threat, passes targeting data to a specific platform, which employs a specific weapon.
It is optimized for reliability and predictability but is brittle under stress, dependent on each link functioning correctly, and expensive to maintain when the preferred weapon is a high-end interceptor.
A kill web, by contrast, connects any sensor to any shooter through a theater-wide common picture. Space-based ISR, manned and unmanned aircraft, surface sensors, and cyber and intelligence sources all feed targets into a shared operational architecture rather than into individual platforms. A strike against a given Iranian radar or missile complex might be prosecuted by LUCAS, cruise missiles, stealth aircraft, or other systems; the shooter is chosen based on cost, risk tolerance, and availability at that moment rather than on which asset first detected the target. LUCAS waves probe and saturate Iranian defenses, forcing SAM expenditure and revealing emitters. Higher-end assets then follow against exposed nodes, preserving their limited, expensive munitions for decisive effects rather than attrition grinding.
This represents a genuinely different approach to cost, risk, and mass.
In the Red Sea phase, the dominant logic was “use the most capable weapon available to ensure a kill.” In Epic Fury, the dominant logic is “use the cheapest sufficient weapon first, preserve expensive capacity for what only expensive capacity can do.”
The layering is deliberate and systemic rather than ad hoc. LUCAS serves as the force multiplier that makes the rest of the joint strike complex more efficient and more survivable.
The introduction of LUCAS intersects directly with naval and Marine Corps concepts developed over the past several years under the rubric of Expeditionary Advanced Base Operations and stand-in forces. NAVCENT and its experimentation arm, Task Force 59, have demonstrated shipboard launches of attack drones from surface combatants using deck-edge or modular launch systems. This capability allows distributed strike against coastal radars, missile launch sites, depots, and small-boat concentrations from a wide array of hulls—not only from dedicated strike platforms. Saturation attacks using LUCAS can create windows in adversary point defenses, enabling follow-on strikes by manned aircraft and cruise missiles that would otherwise face more capable and alert air-defense networks.
The logic of the Houthi campaign has been genuinely inverted.
The speed with which LUCAS moved from concept to combat is striking and worth examining in some detail. Reverse-engineering as a design accelerator was central: by starting from captured Shahed airframes and known performance parameters, industry could avoid a from-scratch design cycle and concentrate on adaptation, U.S.-standardization, and production scaling. The usual process of defining requirements, conducting analysis of alternatives, and running a competitive acquisition program which can easily consume five to ten years before fielding a new munition was effectively bypassed by using the adversary’s own solution as the baseline.
Non‑traditional funding and contracting mechanisms complemented an engineering shortcut: LUCAS leveraged reverse‑engineering of the Shahed‑136 and rapid experimentation/production tools such as APFIT to move far faster than a traditional MDAP. It drew on accelerated acquisition authorities and rapid prototyping venues that effectively sidestepped the full JCIDS requirements cycle rather than following a classic program‑of‑record pathway. Equally important was the organizational beachhead provided by Task Force 59, which was already chartered to experiment with and operationalize unmanned systems at sea, allowing LUCAS to be tested and employed from ships in the Fifth Fleet AOR well before any formal program‑of‑record decision.”
The political context mattered as well. The highly visible cost of missile-defense operations against the Houthis, combined with growing concern about interceptor depletion and industrial-base fragility, gave senior leadership strong incentive to accept more technical risk on cheap attritable systems. The tolerance for imperfection that is usually the enemy of rapid military acquisition became an asset. In aggregate, these factors allowed LUCAS to progress from public unveiling to operational employment in Epic Fury in a matter of months, a pace that would have been exceptional, perhaps impossible, for a traditional munitions program.
If Epic Fury represents America’s cheap drone moment, the key question is not only how LUCAS performs in this campaign but how the United States scales such systems industrially on a durable, long-term basis. One-off urgent solutions that exploit a unique reverse-engineering opportunity are not a force design. What is needed is an industrial ecosystem that can produce large numbers of low-cost attritable drones reliably, affordably, and at the surge rates that serious conflict demands.
Recent U.S. policy moves point to a deliberate effort to build exactly that kind of system. A War Department call to industry now seeks capacity for roughly 300,000–340,000 small drones over about two years, with aggressive unit-cost targets in the low thousands of dollars. Under the Drone Dominance initiative, officials aim to qualify a wide range of U.S. drone designs and provide a stable demand signal, with tens of thousands of one-way attack drones entering the force in 2026 and scaling to hundreds of thousands by 2027. LUCAS sits in a somewhat larger and more capable niche than the smallest man-portable kamikaze systems, but it clearly reflects the same strategic logic: shifting away from small, exquisite stocks that are hard to replace toward large, replenishable inventories of cheap drones that can be surged quickly and pre-positioned afloat or ashore.
The design philosophy that supports this ambition is straightforward: commercial-grade components and simplified airframes amenable to parallel production lines, open architectures that allow multiple vendors to produce compatible variants, and modularity that enables seekers and guidance packages to be upgraded without redesigning the entire system. Strategically, this supports what might be called a fundamental shift in magazine policy: away from small, exquisite stocks toward large, replenishable inventories whose cost and production timelines are measured in weeks and months rather than years.
Allied forces are both partners in Epic Fury and likely co‑builders of the emerging cheap‑mass ecosystem. Israel brings deep experience with loitering munitions and AI‑enabled targeting, and its close operational integration with U.S. forces in the campaign creates natural opportunities for exchanging concepts and technologies in seekers, autonomy, and kill‑web integration. Gulf partners are pressing Washington to replenish high‑end interceptors even as they and the Pentagon explore cheaper defensive and offensive unmanned systems, including Ukrainian‑designed interceptor drones, to ease reliance on scarce Patriot and THAAD stocks. These dynamics are already beginning to reshape regional defense relationships and procurement priorities. The lessons of Epic Fury will reverberate across allied force design efforts as well.
In short, the journey from the Red Sea to Epic Fury is a compressed case study in modern military adaptation under operational pressure. The Red Sea and Houthi phase exposed a glaring cost-exchange problem with ruthless clarity: exquisite interceptors being spent on cheap threats, magazines depleting faster than industry could replenish them, and no structural solution in sight within the existing force design. Interim measures tried to cheapen the defensive kill chain at the margin but could not fundamentally reverse the asymmetry. The problem demanded a structural pivot, not incremental optimization.
LUCAS and Epic Fury represent that pivot. By employing cheap American drones derived directly from Iranian designs to impose costs on Iran’s own defenses, the United States has turned the original asymmetry on its head. Embedded in a distributed kill web that connects any sensor to any shooter, LUCAS is not a standalone system but an architectural element in a fundamentally different approach to strike, cost, and mass. Rapid acquisition mechanisms, organizational innovation through TF-59, and political acceptance of higher risk on attritable systems allowed this pivot to occur in months rather than years.
The industrial-base response, plans for hundreds of thousands of small attack drones, Drone Dominance initiatives, and open-architecture production ecosystems, signals that cheap unmanned mass is being normalized as a central element of U.S. and allied force design, not treated as a one-off emergency expedient.
Whether Epic Fury achieves its strategic objectives against Iran remains to be seen. What is already clear is that it has validated a new logic for how the United States and its allies will think about cost, mass, and force design in contested operations for the decade ahead.
The Red Sea exposed the problem. Operation Epic Fury and LUCAS are the opening chapter of the answer.
Also see:
The Admiral at the Helm: How Brad Cooper’s Years in Bahrain Are Shaping the Iran War
BIDEC 2019: A Window into Bahraini Perspectives on Defense and Security
For my just released book which addresses many of the issues discussed in this article, see the following:
Lessons From the Drone Wars: Maritime Autonomous Systems and Maritime Operations
Sources
“U.S. Navy in Middle East Employs Attack Drone at Sea for First Time.” U.S. Navy, December 17, 2025. https://www.navy.mil/Press-Office/News-Stories/display-news/Article/4363707/us-navy-in-middle-east-employs-attack-drone-at-sea-for-first-time.
“U.S. Forces Launch Operation Epic Fury.” U.S. Central Command, February 27, 2026. https://www.centcom.mil/MEDIA/PRESS-RELEASES/Press-Release-View/Article/4418396/us-forces-launch-operation-epic-fury/.
“US CENTCOM Confirms First Combat Use of LUCAS Drones.” Airforce‑Technology, March 1, 2026. https://www.airforce-technology.com/news/us-centcom-lucas-drone-iran/.
“CENTCOM Confirms LUCAS Drone Debut in Operation Epic Fury.” EurAsian Times, February 28, 2026. https://www.eurasiantimes.com/u-s-bombs-iran-with-shahed-136-clones-centcom-confirms-lucas-drone-debut-in-operation-epic-fury/.
“U.S. ‘Indispensable’ Drones Give Iran a Taste of Its Own Medicine: Why LUCAS Is Invaluable in Op Epic Fury.” EurAsian Times, March 6, 2026. https://www.eurasiantimes.com/u-s-indispensable-drones-give-iran-a-taste-of-its-own-medicine-why-lucas-is-invaluable-in-op-epic-fury/.
“Operation Epic Fury Is the United States’ Cheap Drone Moment.” Defense Security Monitor – Forecast International, March 4, 2026. https://dsm.forecastinternational.com/2026/03/04/operation-epic-fury-is-the-united-states-cheap-drone-moment/.
“Iran’s One‑Way Attack Drone Launches Drop as U.S. Prepares to Revamp Drone Strategy.” DefenseScoop, March 3, 2026. https://defensescoop.com/2026/03/04/iranian-attack-drone-launches-decrease-operation-epic-fury/.
“Epic Fury: The Campaign Against Iran’s Missile & Nuclear Infrastructure.” Center for Strategic and International Studies, March 4, 2026. https://www.csis.org/analysis/epic-fury-campaign-against-irans-missile-nuclear-infrastructure.
“What We Know About Drone Use in the Iran War.” Carnegie Endowment for International Peace, March 2, 2026. https://carnegieendowment.org/emissary/2026/03/iran-drones-shahed-us-lessons.
“How LUCAS Delivered Epic Fury.” TechWars (Substack), March 1, 2026. https://techwars.substack.com/p/how-lucas-delivered-epic-fury.
“US Deploys Iranian‑Derived Strike Drones in Operation Epic Fury.” FlightGlobal, February 28, 2026. https://www.flightglobal.com/military-uavs/us-deploys-iranian-derived-strike-drones-in-operation-epic-fury/166480.article.
“New US Attack Drones Make First Operational Appearance.” The Jerusalem Post, February 27, 2026. https://www.jpost.com/defense-and-tech/article-888313.
“US Fields Suicide Drones Based on Shahed Design in Strikes on Iran.” Interesting Engineering, March 2, 2026. https://interestingengineering.com/military/operation-epic-fury-us-deploys-cheap-attack-drones.
“US Navy in Middle East Successfully Launches One‑Way Attack Drone from a Ship at Sea for the First Time.” The Aviation Geek Club, December 18, 2025. https://theaviationgeekclub.com/us-navy-in-middle-east-successfully-launches-one-way-attack-drone-from-a-ship-at-sea-for-the-first-time/.
“U.S Navy Fires One‑Way Attack Drone From Warship at Sea for the First Time.” Marine Insight, January 22, 2026. https://www.marineinsight.com/shipping-news/u-s-navy-fires-one-way-attack-drone-from-warship-at-sea-for-the-first-time/.
“US Missile Depletion from Houthi, Israel Conflicts May Shock You.” Responsible Statecraft, August 6, 2025. https://responsiblestatecraft.org/missile-depletion-us-navy/.
“Mideast Missile Duels Have Cost US Navy Nearly $1B, Secretary Says.” Defense One, April 15, 2024. https://www.defenseone.com/threats/2024/04/mideast-missile-duels-have-cost-us-navy-nearly-1b-secretary-says/395791/.
“A $2M Missile vs. a $2,000 Drone: Pentagon Worried over Cost of Missile Defense.” Politico, December 19, 2023. https://www.politico.com/news/2023/12/19/missile-drone-pentagon-houthi-attacks-iran-00132480.
“Cheap Houthi Drones Are Draining the Pentagon’s Coffers.” New Lines Magazine, July 29, 2024. https://newlinesmag.com/argument/cheap-houthi-drones-are-draining-the-pentagons-coffers/.
Cancian, Mark F., and others. “Cost and Value in Air and Missile Defense Intercepts.” Center for Strategic and International Studies, February 12, 2024. https://www.csis.org/analysis/cost-and-value-air-and-missile-defense-intercepts.
“The Cost of US Fighting Houthis in the Red Sea Just Went Up.” Responsible Statecraft, December 18, 2023. https://responsiblestatecraft.org/operation-prosperity-guardian/.
“Drone Dominance: Pentagon to Order 30,000 One‑Way Drones in Next Few Days.” Breaking Defense, March 4, 2026. https://breakingdefense.com/2026/03/drone-dominance-pentagon-to-order-30000-one-way-drones-in-next-few-days/.
“War Department Asks Industry to Make More Than 300K Drones Quickly, Cheaply.” Joint Base San Antonio News, December 2, 2025. https://www.jbsa.mil/News/News/Article/4347112/war-department-asks-industry-to-make-more-than-300k-drones-quickly-cheaply/.
“Pentagon Taps 25 Firms for Small, Cheap Attack Drone Competition.” Defense News, February 2, 2026. https://www.defensenews.com/air/2026/02/03/pentagon-taps-25-firms-for-small-cheap-attack-drone-competition/.
“Chairman Wicker Leads SASC Hearing on the American Small Drone Industrial Base.” U.S. Senate Armed Services Committee, March 4, 2026. https://www.wicker.senate.gov/2026/3/chairman-wicker-leads-sasc-hearing-on-the-american-small-drone-industrial-base.