The V-22 Osprey and the Impact Force: From Assault Transport to Kill Web Enabler

I have just published Building the Impact Force: Marine Corps Transformation in an Age of Chaos. The book’s central argument is that the Marine Corps is evolving from a crisis-response “inside force” into something fundamentally differen: an impact force whose primary purpose is to generate disproportionate effects for the joint and allied force by sensing, deciding, and enabling kill webs under conditions of sustained chaos, not episodic crisis.

Within that construct, the MV-22B Osprey emerges not merely as a capable assault transport, but as a primary mobility and sustainment engine without which the entire distributed architecture of an impact force cannot function.

What Is an Impact Force?

The impact force concept marks a decisive break from earlier Marine Corps thinking. An impact force is defined less by what Marines shoot themselves and more by how they amplify the lethality, survivability, and decision speed of the wider joint kill web. The older model, the crisis-management paradigm, assumed that forward-postured Marine Air-Ground Task Forces would execute rehearsed playbooks against relatively discrete, bounded problems: embassy reinforcement, noncombatant evacuation, humanitarian assistance, and disaster relief. These were missions with clear beginnings and endings, operating against the clock rather than against a continuously adapting adversary.

The world has moved on.

The chaos-management environment that the impact force must navigate assumes multiple simultaneous threats across domains, pervasive gray-zone activity, and no clean transition from peacetime to wartime. Decision timelines have compressed to the point where human cognitive speed is no longer sufficient. Adversaries contest every domain from the outset, and the boundary between peace and war has been so thoroughly eroded that the concept of a discrete “crisis” requiring a discrete “response” no longer captures operational reality.

Under this new logic, impact is measured differently.

It is not measured by how many targets a MAGTF destroys with its own weapons, but by decision advantage and effects generation: how fast Marines can sense, process, and act in concert with joint and allied partners across theaters. Impact forces function as the lead at scale for the joint force, finding, characterizing, and holding targets at risk for others to engage. A company of Marines that discovers and cues successful joint strikes on ten high-value targets has generated more impact than a battalion that destroys two with organic weapons.

Steel Knight 2025 was the first full-scale rehearsal of impact force operations, and it operationalized this shift in concrete terms. The exercise tasked Marines to fight distributed from the outset, manage signatures, survive under long-range precision strike, and keep feeding kill webs even when parts of the system were degraded. Its campaign design—linking embassy reinforcement, noncombatant evacuation, distributed fires, contested logistics, and Marine Rotational Force-Darwin certification—tested whether I MEF could function as a genuine impact force rather than a self-contained combined-arms team executing a scripted playbook.

Aviation as Connective Tissue

A key argument of Building the Impact Force is that Marine aviation has become the connective tissue of impact operations rather than merely a collection of mission-categorized platforms. The 2026 Marine Aviation Plan’s major constructs, Project Eagle, Digital Aviation Operations, and Decision-Centric Aviation Operations, treat the F-35, MQ-9, MV-22, CH-53K, and H-1 not as discrete shooters with individual mission sets but as networked nodes that sense, relay, and enable effects across kill webs.

The 2026 plan’s elevation of Aviation Ground Support to a formal seventh function of Marine aviation codifies something that had been operationally obvious but doctrinally undervalued: generating and sustaining expeditionary hubs and spokes, fuel, power, maintenance, and basic airfield services in austere and shifting locations, is what allows those networked nodes to exist and move in the first place.

Without AGS, there is no DAO; without DAO, there is no distributed sensing and enabling architecture; and without that architecture, there is no impact force. Aviation is thus central to both the impact logic itself and to the physical infrastructure needed to sustain it under threat.

Steel Knight gave this taxonomy operational form. Third MAW established aviation spokes at Camp Pendleton and a forward arming and refueling point at Sacramento Mather Airport, approximately 400 nautical miles away. MAG-16’s MV-22 and CH-53 squadrons used those nodes to move Marines across a wide battlespace. MAG-11’s F-35Cs operated from Victorville, where MWSS-372 created an expeditionary node capable of rapid hot-refuel and re-arm. Platforms did not fight from fixed bases; they operated across a hub-spoke-node architecture whose geometry was continuously adjusted to complicate adversary targeting.

Why the Osprey Is Central to the Impact Force

Within this architecture, the MV-22 occupies a position that no other platform in the current inventory can fill. The platform case study chapter of the book treats it explicitly alongside the F-35, MQ-9, CH-53K, and H-1 as an impact platform—valuable not for classic troop-lift metrics, not for payload-range charts developed in the 1990s, but for what it enables across the kill web. Several capabilities make the Osprey indispensable to the impact force concept.

The MV-22 gives the impact force unprecedented node-to-node reach and tempo. In the hub-spoke-node taxonomy that emerged from Steel Knight, nodes are transient positions established for specific missions and measured in hours or days rather than weeks. Retired Lieutenant General Hedelund articulated the operating concept succinctly: “Put timestamps on nodes.” Rather than requesting extraction when threatened, nodes should operate with inherent shelf lives—moving before the adversary can complete its kill chain rather than after.

This concept is elegant in doctrine and extraordinarily demanding in execution. Continuous node movement at operationally meaningful scale requires a platform that can insert, displace, and reconstitute dispersed elements on timelines that compress adversary targeting cycles rather than simply keeping pace with them. The Osprey’s combination of fixed-wing cruise speed and range with rotary-wing access to austere, unimproved landing zones makes it the only currently available platform capable of executing this pattern at scale across the distributed geometry the impact force requires. Conventional rotary-wing assets lack the range; conventional fixed-wing assets lack the access. The V-22 bridges that gap.

Building the Impact Force argues that contested logistics is the binding constraint for impact forces, and that distributed operations multiply logistics complexity in ways that are easy to underestimate in planning and painful to discover in execution. Steel Knight 2025 made this painfully clear. Every dispersed site required fuel, ammunition, maintenance capability, and communications infrastructure. Keeping these nodes alive under simulated long-range precision strike threat proved far harder than simply dispersing them on a map. The logistics challenge was not theoretical; it was the central friction of the exercise.

Here the MV-22 functions as a logistics and sustainment workhorse that directly underwrites node viability in ways no other platform can match.

Its operating envelope allows it to move small but operationally critical loads, personnel, high-value spare parts, communications packages, data, forward repair capabilities, across extended ranges and into austere sites that would be marginal or entirely inaccessible for conventional fixed-wing or rotary assets.

This is not a peripheral contribution. Distributed impact nodes are only valuable to the kill web if they remain capable: a node that has expended its ammunition, lost communications, or suffered a critical equipment failure has ceased to generate impact regardless of how well-positioned it is geographically.

The MV-22 is what keeps distributed impact nodes viable over time, not just at the opening salvo. This logistical role is arguably more operationally significant than its assault transport function, and it is precisely the function that traditional platform assessments, focused on payload, range, and speed in isolation—systematically undervalue.

Bridging Aviation and Ground Kill Webs

Impact logic in the book is fundamentally about Marines as a lead element for the joint force, with aviation functioning as the networked layer that binds sensors, shooters, and decision-makers. The MV-22’s role in this is twofold, and both dimensions matter.

First, the Osprey physically connects ground nodes to the aviation enterprise. By rapidly moving command elements, JTAC teams, sensor packages, and liaison officers among distributed hubs and spokes, MV-22s maintain the human and technical connectivity needed to exploit digital interoperability. The technical infrastructure for kill web integration, DIMANGL, digital waveform gateways, AI-enabled decision support tools, only generates operational value if the right people with the right equipment are positioned to use it. The Osprey is the platform that makes those positional requirements achievable across the distributed geometries the impact force demands.

Second, the Osprey supports the Aviation Ground Support function by moving AGS teams and equipment, enabling the rapid opening, closing, and reopening of expeditionary aviation hubs that host F-35s, MQ-9s, and H-1s functioning as kill web nodes. An F-35C cannot generate impact as a sensor-shooter node if the expeditionary site it depends on for fuel, maintenance, and weapons is not viable. The Osprey is what makes those sites viable under contested conditions, and what makes it operationally practical to close a site before it becomes a target and reopen a fresh one before the adversary can readjust.

The V-22’s Evolving Strategic Role

The Force Design shift from a forward “ship-killer” inside force to a sensing, enabling impact force has direct implications for the V-22’s centrality, and they are implications that run counter to some of the most persistent criticisms of the platform. Critics who evaluated the Osprey primarily as a troop-lift replacement for the CH-46 Sea Knight applied a metric, seats per sortie, payload per flight hour, that measured the wrong thing.

The impact force does not need a helicopter that lifts more Marines to a beach. It needs a platform that can move sensing and C2 packages rapidly, reposition enabling functions to support fleeting windows for joint strikes, and keep the distributed nodes of the kill web viable under threat.

As the Corps pivots from measuring success by organic missile salvos to measuring it by how many targets Marines can place into the joint kill web, the operational requirement becomes persistent, repositionable sensing and C2 nodes rather than static missile batteries. The Osprey gives planners the ability to move those sensing and C2 packages on timelines that matter whether that means transporting a small team with F-35 sensor access into a partner airfield, shifting a node that has exhausted its operational timestamp to a fresh location, or rapidly concentrating enabling functions to support a joint strike window that may open and close in minutes.

MV-22s are integral to turning Force Design’s impact logic into a maneuver scheme in both time and space.

The Indo-Pacific Imperative and Allied Architecture

Building the Impact Force emphasizes that the Marine impact force is designed from the outset to operate within joint and allied kill webs, not as an independent, self-contained force. Steel Knight’s MRF-D certification piece and the book’s analysis of Indo-Pacific realities both underscore that allied infrastructure and access shape what is operationally possible and that operating from within allied territory across the First Island Chain creates both opportunities and constraints that have no analogue in the European or Middle Eastern scenarios that dominated earlier force design thinking.

The MV-22 is instrumental in leveraging that allied architecture. It can rapidly connect U.S. Marines operating as impact nodes with Australian, Japanese, Filipino, or other partner sites during a crisis, enabling the kind of coalition presence, sensing, and decision-making that the impact force concept assumes.

This is especially relevant when forward nodes are small, politically sensitive, and must appear and disappear quickly across allied territory—precisely the conditions that characterize realistic Indo-Pacific contingency scenarios. No other platform in the current assault support inventory can execute that function at the range and tempo that distributed operations across the vast maritime geography of the Indo-Pacific demand.

Modernization as Strategic Investment

Understanding the Osprey as an impact force enabler rather than a legacy assault transport reframes the modernization question. Investments in the MV-22B, nacelle improvements, digital interoperability upgrades, survivability enhancements, and extended-range fuel systems, are not platform-specific spending on an aging airframe.

They are investments in the distributed mobility and sustainment architecture that makes the impact force concept executable.

This distinction matters for acquisition strategy. Platform decisions made on the basis of troop-lift metrics underinvest in the capabilities that actually generate impact force effects: range, speed, all-weather reliability in austere environments, and the ability to integrate with digital kill web architectures. Platform decisions made on the basis of impact force logic ask a different question, not “how many Marines can this aircraft move to an objective?” but “how does this platform sustain the distributed node architecture that enables the joint kill web to function under chaos management conditions?”

The answer, as Building the Impact Force argues at length, is that the Osprey is not a candidate for replacement so much as it is a candidate for continuous evolution alongside the broader kill web architecture it enables. The question is not whether to invest in MV-22 modernization, but how to ensure that modernization keeps pace with the digital interoperability, survivability, and logistics integration requirements of the impact force concept as it matures through Steel Knight and beyond.

Conclusion: The Osprey as a Glue of the Kill Web

Building the Impact Force argues that the Marine Corps is undergoing a genuine transformation, visible in Steel Knight’s operational patterns, Force Design’s October 2025 updates, and the 2026 Aviation Plan’s architecture, toward a force optimized for enabling joint kill webs in chaos management conditions. That transformation is real, not rhetorical. But it depends on a set of physical and digital capabilities that must work together for the concept to be executable rather than aspirational.

The MV-22 Osprey is the physical connective tissue of that architecture. It turns the abstract idea of “distributed, constantly moving nodes” into an executable operational pattern by providing the range and speed to reset the geometry of the force before an adversary can complete its kill chain. It sustains those nodes by moving critical personnel, equipment, and supplies across the contested distances that distributed operations require. It bridges ground kill web participants to the aviation enterprise by moving the human connectors that digital interoperability alone cannot place. And it enables the allied access architecture that makes the Indo-Pacific impact force concept operationally coherent rather than geographically notional.

The impact force is real. Whether it proves decisive will depend on choices the Marine Corps and the joint force make in the years ahead about culture, command philosophy, logistics investment, and industrial base capacity.

The Osprey is not a legacy platform in search of a mission.

It is an impact force enabler in search of the investment, modernization, and operational understanding it deserves.