Drone warfare: doctrine, evidence, and theater map

What drone warfare means on this site

Drone warfare on this site means documented military and security use of unmanned aircraft across roles, not a how-to for operating weapons.

Readers arrive with theater questions (Ukraine, Iran, Gaza) and product questions (loitering munitions, armed ISR, interceptors). This hub separates doctrine language from conflict evidence and from equity research.

Continue into named systems only when a primary or high-quality official source names the model. Generic “a drone struck” reports are not model attribution and should not be reshaped into product pages.

How this hub differs from adjacent drone hubs

Drone warfare is the doctrine and evidence hub. It is not the theater tracker and not the equity screen.

Theater evidence lives under drones by war, where each conflict page lists only systems with cited sources. Product taxonomy without theater claims sits at types of military drones, and program-and-fleet views live at Iran drones, Russian drones, and US military drones.

Equity research lives at military drone stocks and publicly traded drone companies. Read the warfare hub for language, then descend into a war page or company page instead of blending doctrine with ticker speculation.

Drone warfare roles, not a single platform class

Evidence standards for drone warfare claims

Evidence standards for drone warfare claims require a named system, a named conflict or theater, and a citeable official or manufacturer source when possible.

The DIA Iranian UAV comparison book, CENTCOM Operation Epic Fury materials, Ukraine Ministry of Defence procurement updates, and U.S. Army Russia–Ukraine observations illustrate the quality bar used across this cluster.

When attribution is open-source only, pages mark status as reported or uncertain rather than inventing a model name. This applies equally to sortie counts, unit costs, and casualty claims.

Attribution failure modes in drone warfare reporting

Attribution failures in drone warfare reporting cluster into recurring patterns. The most common are unnamed models, mistranslated designations, and manufacturer marketing recycled as capability confirmation.

The Shahed-136 to Geran-2 designation split is the canonical named-system example; the DIA UAV Book anchors that mapping. Orlan-10 confusions arise when analysts blend variants listed on the FSMTC catalog with unrelated Russian ISR airframes seen in imagery.

When a claim lacks a service fact sheet, sanctions filing, or ministry statement, this site treats model attribution as reported rather than confirmed. Readers should apply the same rule when scanning news coverage and social-media clips.

Conflict maps: where drone warfare evidence lives

Conflict maps on this site live under drones by war, with theater pages that list only systems backed by cited evidence.

Start with Ukraine–Russia for industrial-scale mixed fleets, Iran war for CENTCOM-named U.S. assets and Shahed-class strike context, and other theater pages for narrower inventories.

Named war-drone profiles sit at Shahed-136 / Geran-2 (profile), Orlan-10 (profile), ZALA Lancet (profile), and related entries.

Doctrine language from public U.S. sources

Public U.S. doctrine language treats small UAS and drone munitions as company-and-below tools that change reconnaissance and strike tempo, not as a single “drone war” platform. That framing matters when a reader tries to translate a viral clip into a program-of-record thesis.

The Army’s family of drone munitions framing and integrating sUAS and loitering munitions guidance show how U.S. ground forces discuss roles at unclassified level.

Defense Department Drone Dominance messaging and Replicator progress reporting describe industrial-base and attritable-autonomy priorities without publishing employment checklists.

A named coalition structure, not just a headline: CENTCOM's multinational attack-drone task force

A drone warfare headline sometimes names a new institution rather than a new weapon, and that is a distinct research category on its own. In August 2026, CENTCOM announced the establishment of its first multinational, multi-domain attack-drone task force, reported in trade press as Task Force Falcon Strike, combining U.S. and regional-partner staff under U.S. Special Operations Command Central to coordinate one-way attack drone capability across the air, surface, and subsurface domains.

The task force follows the December 2025 stand-up of Task Force Scorpion Strike, the U.S. military's first dedicated one-way attack drone squadron in the region, which CENTCOM credits with the first-ever aerial attack-drone launch from a U.S. Navy warship and later strikes on Iranian port facilities using unmanned surface vessels. Falcon Strike is described as expanding that model to include named regional partners rather than U.S. forces alone.

The information-gain point for this hub's evidence rule: a task-force announcement is an organizational and doctrinal event, not itself a named-system claim or a contract. It tells a reader which command structure will field attack drones and with which partners, not which airframe or munition wins funding as a result. Treat "multinational task force" and "new production award" as two different categories of news, the same way this hub already separates a program of record from a prototype.

What this page will not do

This page will not provide employment, build, or engagement instructions for weapons or counter-weapons.

It will not invent prices, unit costs, or ticker-level forecasts from theater headlines.

For taxonomy without theater claims, use types of military drones; for equities, use military drone stocks.

Counter-UAS and industrial-base stack layers for research

A drone warfare research screen separates five stack layers: airframe, munition, autonomy, sensors, and counter-UAS. Each layer has different demand drivers and different public-source anchors.

Drone Dominance and Replicator progress materials frame attritable-airframe scale, while DIU Blue UAS frames trusted small UAS supply. Army drone munitions messaging frames the effects layer at company and below.

Counter-UAS demand tracks air-defense saturation, as reflected in DoD Small Drones, Big Problems and CENTCOM Epic Fury materials. Continue to counter UAS for layer-specific reading.

Investor research bridge after drone warfare headlines

Investors should treat drone warfare headlines as demand and industrial-base signals, not as buy or sell instructions.

Ask which stack layer is actually exposed: long-endurance airframes, tactical UAS, loitering munitions, autonomy software, or counter-UAS. Ask whether the named beneficiary is public, private, or a small unit inside a much larger prime.

Map from this hub to military drone stocks, AeroVironment (profile), General Atomics (profile), and drone ETFs.

Research workflow for a drone warfare headline

A durable research workflow starts with the claim, not the ticker. Identify the named system, the named theater, and the source type before doing any equity work.

Confirm the model against a primary reference: DIA UAV Book for Iranian classes, FSMTC or ZALA for Russian systems, or Air Force MQ-9 and GA-ASI materials for U.S. long-endurance RPA. Then check drones by war for the correct theater page.

Only after the model and theater are verified should the reader open military drone stocks or a company page. This ordering prevents theater-headline over-reading.

If the headline names a role but not a model—armed ISR, one-way attack, or interceptor—route through this hub’s role table first, then into the matching taxonomy page such as loitering munitions or counter UAS. Role-first routing stops readers from inventing a product name to fill a gap the source left empty.