By Robbin Laird

In the early 2000s, a billion-dollar Predator drone circled over a combat zone, its high-definition cameras capturing perfect imagery of enemy positions below. On the ground, a Special Forces operator—weighted down with 80 pounds of gear and under enemy fire—was effectively blind. He knew the drone was overhead, but he couldn’t see what it saw. Instead, he relied on shouted radio coordinates, trying to construct a mental picture of the battlefield while bullets snapped overhead. It was a perfect encapsulation of military dysfunction: 21st-century technology in the sky, World War II communications on the ground.

The solution didn’t emerge from a defense contractor’s engineering lab after years of development and billions in procurement funding. Instead, it came from a Chief Warrant Officer named Manuel who asked the most dangerous question possible in military bureaucracy: “If the drone can see it, why can’t I?”

Rather than wait for the official answer—which would have involved submitting requirements, waiting perhaps a decade for a properly encrypted secure system, and navigating endless procurement reviews—a major named Greg Robbins went to his local Radio Shack. He bought analog TV parts, jury-rigged a receiver using a Panasonic Toughbook laptop, pinned some antennas to his tactical vest, and hacked the drone’s video feed. It worked immediately. Ground operators could suddenly see what the Predator saw, cutting out the deadly middleman of verbal descriptions. This improvised system became ROVER (Remotely Operated Video Enhanced Receiver), a crucial capability that spread throughout the force.

This story, detailed in my new book “Lessons in Military Transformation,” captures something fundamental about how real innovation happens in military organizations and why it so often doesn’t. My work isn’t standard military history written from archives and official documents. It is a ongoing set of field reports, the product of decades spent visiting air bases, aircraft carriers, and maintenance hangars, talking to the practitioners who turn wrenches and fly missions rather than the theorists who populate Washington conference rooms.

The Innovation Protector

The Radio Shack hack reveals grassroots ingenuity, but there is another crucial element: what one might call the “innovation protector.” Brilliant ideas from the field routinely get crushed by bureaucratic antibodies unless someone with real authority shields them. In this book, that protector is former Air Force Secretary Michael Wynne, whose tenure from 2005 to 2008 became a case study in both the necessity and the fragility of disruptive leadership.

Wynne operated with a personal intensity rare among Pentagon officials. His brother Patrick, a pilot, had been shot down in Vietnam, not just by “the enemy” in some abstract sense, but specifically by a sophisticated Russian surface-to-air missile sold to North Vietnam. That detail shaped Wynne’s entire worldview. While the defense establishment in the mid-2000s focused obsessively on counterinsurgency, fighting enemies without air forces in places like Iraq and Afghanistan, Wynne fixated on peer competitors. He understood that even when America wasn’t directly fighting sophisticated adversaries, their technology was what killed American personnel. He tried to pivot the Air Force back toward high-end warfare preparation when the entire apparatus wanted more armor on Humvees.

One incident defines Wynne’s approach. He walked into a briefing on the Joint Unmanned Combat Air System (J-UCAS), a revolutionary concept for a stealthy autonomous combat drone designed to penetrate sophisticated air defenses. The program managers announced they wanted to pause development to integrate mid-air refueling capabilities. On its face, this seemed reasonable, range matters. But Wynne recognized it for what it was: requirements creep, the number one killer of military innovation.

The prototype hadn’t even proven it could fly autonomously in combat. Mandating refueling capability at that stage meant adding enormous weight, complex fuel systems, extensive new software, and fundamental structural changes. They were gold-plating a concept to death before it could even get off the whiteboard, prioritizing a peripheral process over core capability.

Wynne picked up the briefing binder and threw it across the table. It slid down and hit one of the principals. He said simply, “Come back when you have something to say about the airframe,” and walked out.

Nonetheless or perhaps because he was a protector of innovation, Wynne was eventually fired by Defense Secretary Gates, ostensibly for complex reasons but fundamentally for speaking truth to power. He kept insisting on preparing for great power conflict and building more F-22s when leadership wanted every dollar focused on the immediate wars. He was right, but right too early, the classic tragedy of visionary leadership in sclerotic institutions.

From Crisis Management to Chaos Management

Traditional military thinking assumes peace as the baseline state. Crises erupt, you surge forces to fix the problem, then return to stability. This worldview implies that stability is the natural order of things.

Those days are over. We’ve entered an era requiring chaos management and accepting that the environment is permanently turbulent. You’re not trying to fix it and return to some imagined stable state. You’re trying to operate effectively within persistent instability.

The V-22 Osprey exemplifies this shift. When it emerged, the press savaged it. It crashed in testing. It cost enormous sums. Critics asked why the Marines needed this complicated tilt-rotor aircraft when helicopters were cheaper. They saw it as just a faster helicopter, a marginally improved truck.

But that wasn’t the point. When Marines actually deployed it to the Pacific, they realized it wasn’t a truck at all: it was connective tissue. Its speed and range fundamentally changed battlefield geometry. Captain Medlin, an officer I interviewed last year at 2^nd Marine Air Wing, offers a vivid comparison: old warfare resembles a Walmart Supercenter, while distributed operations resemble mom-and-pop stores.

The Walmart model means building massive bases like Bagram in Afghanistan, everything in one place, incredibly efficient, with fuel, ammunition, communications, even fast food franchises. But against a peer competitor like China or Russia, such bases are giant targets. One missile volley ends your operation.

The alternative distributes everything: fuel on this island, ammunition on that one, a temporary runway on a third. If the enemy hits one node, the network survives. This is wildly inefficient in the traditional sense—which is precisely why it’s called chaos management, not efficiency management. You deliberately trade efficiency for survivability.

This only works if personnel can think independently. You cannot run a distributed network with rigid, top-down rulebooks. Which brings us to the cowbells.

Major General Swan, then commanding 2^nd Marine Air Wing, actually handed out physical cowbells, literal clanging bells, I know for I have one, to reward improvisation. If a maintainer ignored the manual to get a jet operational faster, he received a cowbell. It was both humorous and deadly serious: a tangible signal from leadership that output mattered more than bureaucratic process. In chaotic environments, people waiting for permission to act are already dead. You need a culture actively incentivizing intelligent rule-breaking.

Training for Failure

But you can’t just declare that chaos is acceptable and expect success. Marines at Marine Aviation Weapons and Tactics Squadron One (MAWTS-1) in Yuma, Arizona, created “the innovation triangle.” In most military organizations, testers work in Maryland, the schoolhouse operates in Florida, and operational pilots fly from Virginia. The feedback loop takes years.

At MAWTS-1, they’re neighbors. The school, testers, and operational squadrons co-locate. If a tactic fails on a morning flight, the instructor knows by lunch and testers are working on fixes by dinner. They train for what they call “the physics of combat”, not PowerPoint scenarios, but actively practicing failure. They assume radios will be jammed, logistics won’t arrive, and plans will collapse on contact with the enemy. In chaos management, the plan never survives that contact.

The Digital Revolution and the Rise of Purple Shirts

Parallel to cultural transformation runs technological revolution. Squadron HMLA-267 took H-1 platforms, Hueys and Cobras with DNA from Vietnam, and gave them digital brain transplants. They look like old helicopters but function as flying server nodes, sharing targeting data and seeing what F-35s see. The pilot isn’t just a shooter anymore; he’s an information manager.

This crystallizes in the kill web. Traditional warfare relied on the “kill chain” with find, fix, track, target, engage. Linear, sequential, like old Christmas lights: if one bulb burns out, the whole string goes dark. If your forward radar gets jammed, you can’t shoot.

The kill web is a mesh network. If your radar fails, the shooter instantly pulls targeting data from a drone, ship, or satellite. The path to target changes dynamically. You can’t break the chain because there isn’t a single chain to break. The F-35 serves as quarterback, sucking up data from everywhere and distributing it to everyone.

In an Israeli operation called Operation Rising Lion, Israeli pilots among the world’s best refused to fly into contested airspace without F-35s leading, not because they needed its weapons but its sensors. The F-35 managed the web, making older F-15s lethal by telling them exactly where to look without activating their own radars.

But this creates cultural upheaval. If the network is the real weapon, the pilot pulling the trigger isn’t necessarily the most important person anymore. Vice Admiral Miller noted when I visited him at the Navy Air Boss that next war will be won or lost by “purple shirts” or the MISR (Maritime Intelligence, Surveillance and Reconnaissance) officers.

On aircraft carriers, purple shirts are traditionally fuel handlers, not the personnel who receive medals. But MISR officers are “warrior solution architects.” We’re shifting from the right side of the kill chain (target and engage, the Top Gun stuff) to the left side (find, fix, track). In modern warfare, finding the enemy is far harder than killing them. If you can find a Chinese carrier, you can sink it. The challenge is finding it in a massive ocean while they jam your sensors and hide in noise.

This completely inverts traditional hierarchies. Fighter pilots who’ve spent careers as gods of the air wing must accept they’re nodes on a network. The intelligence officer who isn’t even airborne might be calling plays. This isn’t a software problem: it’s a status problem. If pilots don’t trust Intel officers to guide the fight, the F-35 becomes an expensive paperweight.

The Synthesis

Bringing it together: from thrown binders to Radio Shack hacks to Pacific mom-and-pop stores to the rise of purple shirts, technology proves almost secondary to behavior. Transformation isn’t a destination you reach or a product you buy. It’s an evolutionary behavior, not a revolutionary event.

You can purchase F-35s, but running them with a Walmart mindset ensures defeat. As one deep dive participant noted, you can buy the world’s best electric guitar, but if you don’t know jazz, you can’t improvise. We’re entering a jazz era of warfare. Crisis management was classical music, perfectly following written notes. Chaos management is jazz: know your instrument, listen to the team, improvise when the rhythm changes.

This circles back to the Radio Shack moment. We spend millions on platforms and argue endlessly about defense budgets. But the most dangerous weapon system discussed here wasn’t the stealth fighter. It was the mindset of a major with a Radio Shack receipt and the audacity to fix a billion-dollar failure with a soldering iron.

The ultimate question isn’t whether we can build better technology. It’s whether we’re building systems that allow that major to exist and thrive, or bureaucracies that ensure he gets fired for trying.

By spending decades with practitioners rather than theorists, it is clear to me that there is a persistent gap between Washington’s elegant plans and operational reality. The Radio Shack hack, the thrown briefing binder, the cowbells, the refusal of Israeli pilots to fly without F-35 sensor coverage, these aren’t anomalies to be dismissed. They’re data points revealing fundamental truths about how complex organizations actually innovate under pressure.

The tragedy is that we already know what works. We’ve seen it demonstrated repeatedly. The challenge is that what works often violates established protocols, threatens existing hierarchies, and makes people uncomfortable. Michael Wynne got fired. The ROVER system was developed outside official channels. The digital transformation of old Huey helicopters happened because maintainers and pilots refused to accept that legacy platforms were obsolete.

Military transformation isn’t simply about buying the next generation of technology. It’s about creating conditions where the people closest to problems have authority to solve them creatively. It’s about leaders willing to throw binders and award cowbells. It’s about accepting that permanent turbulence is the new normal, not an aberration from peacetime stability.

The next war won’t be won by whoever has the best PowerPoint presentations. It will be won by whoever can manage the chaos. And managing chaos requires jazz musicians, not orchestra players following a score. It requires Radio Shack majors with soldering irons, not procurement specialists with five-year timelines. The technology will follow. The question is whether the culture can evolve fast enough to use it.

By Robbin Laird

In the clear desert night over Arizona, a CH-53K King Stallion slid into position behind the tanker, its rotors biting into thin air as the crew prepared to take the hose once more. Below, the Sonoran Desert stretched away in darkness. Above and around, the aircraft was alone with its mission. The long-range raid during WTI 2-26 was still in its opening movements, but the key enabler was already on stage: a heavy-lift helicopter whose foundational design premise is to make distance, weight, and temperature less decisive as constraints on Marine assault support.

It was not a dramatic moment in the Hollywood sense. There were no enemy surface-to-air threats pressing in, no emergency that required heroic improvisation. What made it significant was precisely its matter-of-fact quality: the plug was planned, expected, and executed as a routine element of an already-complex tactical evolution. That normalization, the King Stallion on the hose as a standard instrument of Marine Corps assault support, not an exception or a demonstration, is among the most important things WTI 2-26 produced.

MAWTS-1 and the Logic of the Long-Range Raid

Weapons and Tactics Instructor (WTI) courses at MAWTS-1 are built on a straightforward but demanding premise: force real crews and real platforms to solve operational problems that look uncomfortably like the ones the Corps expects to face in the next fight, not the last. The scenarios are not scripted for success. They are designed to surface gaps, expose friction, and generate learning under conditions of meaningful operational pressure. For decades, the long-range raid has been one of the signature evolutions of that curriculum, a way of stretching assault support aviation across range, threat, and integration challenges that go well beyond a standard workup.

In WTI 2-26, the CH-53 community brought a different aircraft to that enduring problem. The CH-53K King Stallion, now entering fleet service as the Marines’ premier heavy-lift and distributed logistics asset, took the lead role in the long-range raid evolution. Its presence was not incidental. MAWTS-1 and the heavy-lift community have been deliberately integrating the Kilo into progressively more demanding WTI scenarios, using the training environment to validate a new concept of operations and to build the institutional knowledge that will carry into fleet practice.

The scenario itself was classic MAWTS-1 in its construction. A force had to project combat power and sustainment across significant distance under the assumption that fixed infrastructure was either absent, degraded, or under threat. The answer was not a single aircraft or a single tactic, but a composite of platforms, fuel planning, routing, and timing, all orchestrated by WTI students and instructors who were simultaneously executing the mission and being evaluated on how they solved it. The CH-53K’s role within that framework was at once straightforward and demanding: move Marines and critical cargo long-range, on time, and in condition to fight, operating at or near the edge of the performance envelope throughout.

Air-to-Air Refueling as a Concept of Operations, Not a Workaround

Air-to-air refueling was central to the raid’s execution. Imagery from the evolution shows the CH-53K on the hose in flight, taking fuel to extend its reach deeper into the exercise battlespace. The significance of this detail is easy to understate.

In the emerging CH-53K concept of operations, the ability to plug into a tanker and push further is part of the planned architecture. The King Stallion is not envisioned as a shuttle running loads between known forward operating bases; it is envisioned as a roaming logistics and assault support node, one that can operate across a much wider area of the battlespace because aerial refueling is baked into the mission planning rather than treated as exceptional. This matters enormously in a Pacific or Indo-Pacific context, where distances between suitable landing sites can be prohibitive, where fixed basing is contested or unavailable, and where the ability to sustain stand-in forces depends on a logistics chain that does not require infrastructure the adversary can target and destroy.

The Kilo’s aerial refueling capability is complemented by the power margins its new engines and drivetrain provide. The difference in available power compared to the legacy CH-53E is substantial, particularly in hot-and-high conditions of the kind routinely encountered at Yuma and at many of the expeditionary sites that feature in Pacific planning. Greater power margins translate directly into operational options: heavier loads at range, more margin in degraded environmental or combat conditions, and the ability to treat high-density altitude as a planning factor rather than a mission-limiting constraint. For a force building its logistics around distributed operations and expeditionary advanced base concepts, those margins are not marginal improvements. They are the difference between a mission that works and one that doesn’t.

Fly-by-Wire and the Cognitive Dimension of Heavy Lift

For the crews executing the raid, the CH-53K’s full-authority digital fly-by-wire system is perhaps the most immediately tangible improvement over the legacy platform. Fly-by-wire gives the Kilo a level of stability and handling precision that is especially valuable during the most demanding phases of a long-range raid: formation flight at night, refueling joins under pressure, approaches to austere and unprepared landing zones, and external lift operations when the aircraft is at or near maximum gross weight.

MAWTS-1 leadership has been explicit that fly-by-wire’s value is not primarily about pilot comfort. It is about cognitive bandwidth. In the most demanding phases of a complex tactical evolution, crews face simultaneous demands from the aircraft itself, from the tactical situation, from the threat picture, and from the joint network they are supporting. Every increment of workload reduction that fly-by-wire provides, every moment when the aircraft handles an unwanted excursion automatically rather than requiring the pilot to intervene, is cognitive bandwidth available for the tactical problem. At scale, across a fleet of aircraft and many missions, that difference accumulates into lower risk, better decisions, and more successful mission execution.

This is not an abstract engineering point. Pilots who have transitioned from the Echo to the Kilo have described the difference in handling as qualitatively significant. Night formation flying in the Kilo is described as meaningfully less demanding than in the Echo. External lift at heavy weights, always among the most workload-intensive tasks in rotary-wing aviation, benefits from the Kilo’s stability augmentation in ways crews notice immediately. For a platform whose mission profile regularly stacks multiple high-workload evolutions in sequence, a refueling join followed by a low-level approach to an austere LZ followed by a precision external load delivery, those handling qualities represent a genuine operational advantage.

The Triple-Hook System and the Meaning of Distributed Logistics

The CH-53K’s triple-hook external lift system underpins another dimension of what the WTI long-range raid was demonstrating. The raid was not simply about moving people; it was about moving meaningful combat sustainment under contested or austere conditions. With the ability to carry significant fuel loads externally on the order of tens of thousands of pounds, the Kilo can deliver fuel and heavy cargo without necessarily landing and offloading. That distinction matters. A helicopter that must land to deliver a load is a helicopter that must accept the exposure, time, and vulnerability that come with being on the ground in a forward or hostile environment. A helicopter that can deliver externally, from a hover or a low approach, shortens its time in the objective area and fundamentally changes its risk calculus.

In a raid context, this enables a range of concepts that MAWTS-1 has been exploring across multiple WTI iterations. Bulk fuel delivery to an expeditionary F-35B operating site. Critical equipment delivery to a forward element that cannot afford to wait for a ground resupply chain that may not exist. Recovery of a downed rotorcraft from a location too remote or too contested for a surface recovery. All of these missions fall within the broad heavy-lift design space that WTI repeatedly stresses and the triple-hook system, combined with the K’s power margins and aerial refueling capability, makes the aircraft more capable in all of them than its predecessor.

The connection to Expeditionary Advanced Base Operations (EABO) and distributed maritime operations is direct and intentional. The Marine Corps has been building a strategic concept around the idea of small, dispersed, difficult-to-target forces operating from a network of austere sites across a contested maritime environment. That concept requires logistics. Specifically, it requires logistics that can function without the fixed infrastructure those austere sites, by definition, do not have. The CH-53K’s combination of range, payload, aerial refueling, and external lift capability is not incidental to that concept. It is close to indispensable to it.

Col Purcell and the Institutional Argument

WTI 2-26 did not occur in an institutional vacuum. As a recent MAWTS-1’s commanding officer, Col Eric Purcell, himself a CH-53 pilot with deep experience in the platform, has been explicit and consistent in his argument about what the King Stallion represents and how it should be integrated into Marine Corps thinking. His position is not that the Kilo is a better CH-53E, it is that the Kilo is a different proposition entirely, one that enables different concepts of operations and should be treated as a unique enabler for distributed logistics and force mobility rather than simply a like-for-like replacement for aging 53Es.

That argument has implications that extend beyond the heavy-lift community. If the Kilo is not a replacement but an enabler of new concepts, then the force design and planning work that proceeds from its introduction needs to reflect that distinction. Raid planning, logistics architecture, EABO site selection, tanker support requirements, and the integration of heavy lift with stand-in force concepts all potentially look different when the heavy-lift asset available is a King Stallion rather than a Super Stallion. MAWTS-1’s sustained effort to use WTI as a laboratory for that rethinking, rather than simply substituting the Kilo into existing CH-53E roles and planning assumptions is one of the more consequential things the schoolhouse is doing.

Earlier WTI iterations had already begun integrating multiple CH-53Ks into broader mobility and support packages, exploring how the aircraft performs in composite operations alongside MV-22s, F-35Bs, and other elements of the Marine aviation enterprise. WTI 2-26’s long-range raid represents a continuation and deepening of that trajectory. The King Stallion is now treated as a routine, expected instrument for solving long-range assault support problems, not a guest appearance, not a proof-of-concept demonstration, but a platform the students plan around and the instructors evaluate against.

What Normalization Actually Means

The most important product of the WTI 2-26 long-range raid may not be any specific technical validation or any particular tactic, technique, or procedure. It may be the normalization itself. When WTI students plan a long-range raid and the CH-53K is simply “the heavy-lift aircraft they have”, an asset whose performance they design around rather than an exceptional capability they have to carefully justify using, something significant has shifted in how the Corps thinks and plans.

Normalization in a training environment is not automatic. It requires sustained institutional commitment to integrating a new platform into scenarios where its performance genuinely matters, where the planning assumptions change if it is or is not available, and where students develop the intuition and the habit of mind that will carry into fleet operations. MAWTS-1’s progressive integration of the Kilo across multiple WTI cohorts, in increasingly complex scenarios, with leadership that has articulated a clear operational rationale, represents exactly that kind of sustained commitment.

For the students who planned and executed the WTI 2-26 raid, the experience produces something that classroom instruction cannot replicate: the embodied knowledge of what the King Stallion can do, of where its limits lie, of how it integrates with the other elements of the air-ground task force, and of the planning factors that change when a CH-53K is available instead of an Echo. That knowledge will carry into fleet squadrons, into deployment planning, into pre-mission planning for real-world operations. It represents a form of institutional learning that is difficult to generate outside of a demanding, operationally relevant training environment.

The Heavylift Piece of the Distributed Operations Puzzle

By the time the CH-53K turned back toward Yuma at the conclusion of the raid, the students and instructors had accumulated something more than another set of WTI sorties. They had validated, in a concrete and operationally meaningful way, that the King Stallion’s claims as a revolutionary advance in long-range heavy lift are not abstract promises but capabilities the fleet can plan against today. The aircraft performed. The concept of operations worked. The crews adapted to the platform’s characteristics in the ways that MAWTS-1 needs to see before it can confidently say that a new way of thinking about heavy-lift assault support is taking root.

The broader message for the Marine Corps and for the joint force audience that watches MAWTS-1 closely is pointed and timely. The long-range raid is no longer a theoretical Pacific vignette on a briefing slide. It is an event flown with operational crews in an aircraft designed from the outset to make that kind of mission routine. The distributed operations concepts that animate Force Design 2030 and its successors require a logistics architecture that can function without fixed infrastructure at the forward edge. The CH-53K’s combination of payload, range, aerial refueling, fly-by-wire handling, and external lift capability places it at the center of that architecture.

In the years to come, as more King Stallions flow to fleet squadrons and WTI scenarios grow more complex and more joint, the long-range raid will continue to evolve. New tanker integrations, new external load concepts, new coordination with autonomous logistics platforms, new interfaces with the joint network, all of these will add layers to what WTI is building. But the WTI 2-26 iteration marks an early and significant moment: the moment when the Marine Corps began to act, not just to argue, as if the heavy-lift piece of its distributed operations puzzle is finally in place.

Fifteen photographs from April 13, 2026, at the Chocolate Mountain Aerial Gunnery Range in California document the most operationally complex exercise in the WTI 2-26 series: Assault Support Tactics 1. The photographs span the full operational picture from contractor technicians assembling threat-representative UAS at a mountain observation point, through ground teams climbing to their positions on the ridgeline, to terminal control teams coordinating aviation on the objective, to the large-scale assault itself as helicopters raise dust clouds across the desert floor beside a mock city target complex.

This is the exercise that integrates everything the WTI course has been building toward.

AST-1 is the first major combined-arms integration exercise in the WTI assault support sequence. It brings together assault aviation, terminal attack control, OPFOR UAS threat simulation, ground observer teams, and a realistic objective area into a single scenario that demands coordination across every function simultaneously. The prospective WTI who can plan, execute, and debrief AST-1 has demonstrated the integration competency that the entire first half of the course has been building.

The OPFOR UAS: Contractors and Threat Replication

Images 1 and 2 show contractors Emanuel Puerta and Bradley Romeher at Observation Point 4, assembling and balance-checking medium fixed-wing pusher-prop UAS on the rocky desert floor at the base of the Chocolate Mountain range. The aircraft are commercial-military hybrid designs consistent with the threat-representative UAS profiles used across the WTI UAS threat simulation program. They will fly profiles replicating adversary ISR drones or loitering munitions against the assault force operating in the valley below.

The use of contractors for the OPFOR UAS role is analytically significant. MAWTS-1 has built a threat simulation capability that replicates the specific flight characteristics, sensor packages, and employment patterns of adversary UAS systems using purpose-configured commercial platforms operated by specialist contractors. This is not a nominal threat marker. It is a realistic replication of the aerial threat environment that Marine assault aviation will face in actual operations.

The balance-point check visible in Image 2 with two operators checking the center of gravity of the airframe is the kind of precision pre-launch procedure that distinguishes a professionally operated threat simulation program from an improvised substitute. A UAS whose center of gravity is off will fly erratically and fail to replicate the threat profile the exercise requires. The contractors are doing the job to standard. The exercise depends on it.

The Climb: Ground Teams Moving to Position

Images 3, 4, and 5 document the approach march of mixed Marine and civilian teams ascending the Chocolate Mountain ridgeline to their observation positions. The terrain is demanding: loose rock, steep grade, no trail, full equipment loads including radios, antennas, and weapons.

Image 5 is the most visually striking of the three: five figures spread across the skyline of the ridgeline, each separated by intervals, all moving toward the crest. The scale of the mountain above them, the hard blue sky behind them, and the spacing of the figures give the image a quality that is simultaneously tactical and austere. This is the physical reality of the terminal controller’s approach march: there is no road to the observation point. The team walks up.

The civilian figure visible in Image 3, blue jeans among the camouflage, is the contractor UAS operator ascending to OP4 alongside the Marine terminal control team. The integration of contractor and military personnel on the same approach march to the same observation point captures the operational reality of how WTI’s threat simulation program actually works: the UAS operator and the terminal controller need to be at the same location, with line of sight to the same objective area, coordinating in real time.

The UH-1Y Insertion: Assault Support Into the Objective Area

Images 6 and 7 show UH-1Y aircraft 17 and 07 conducting assault support insertions at a rocky desert landing zone below the ridgeline. In Image 6, three Marines are moving away from aircraft 17 as it lifts off: the insertion complete, the aircraft transitioning to its escort or overwatching role while the ground element moves to its position. In Image 7, aircraft 07 is on the ground with three Marines approaching, the crew chief visible at the door.

These are not clean airfield landings. The UH-1Y is on unimproved rocky terrain at the base of a mountain, in a confined space between ridgelines, with rotor wash kicking up dust across the desert scrub. The pilots are flying to the ground element’s position rather than to a prepared landing zone. This is the realistic insertion geometry that AST-1 is designed to train: the aircraft goes where the mission requires, not where the infrastructure permits.

The Terminal Control Team: Three People, One Node

Image 8 is the analytical centerpiece of the ground element photographs. Three personnel are at a rocky ridgeline position: a Marine standing with a full radio kit, NVGs mounted on his helmet, speaking into a handset while scanning; a second Marine crouched and writing on a kneeboard, tracking the control sequence; and an Army soldier in OCP operating a separate radio at the right. A MAWTS-1 patch is visible on one of the Marines.

This is the terminal attack control node  which is the human interface between the aircraft in the air and the target on the ground. The standing Marine is the JTAC or FAC(A) in the ground role, controlling the aviation through the radio. The crouching Marine is tracking the control sequence, maintaining the log, and managing the data that feeds the debrief. The Army soldier’s presence reflects the joint integration that runs throughout this WTI series: the terminal control mission in a real contingency may involve Army, Air Force, or partner-force controllers working alongside Marine aviation.

Image 9 shows a single Marine at the ridgeline crest, seated with a notebook, a radio mast deployed beside him, looking out over the desert floor below. The view from his position encompasses the entire objective area — the mock city, the landing zones, the approach routes for the assault aircraft. This is the observer’s vantage point: elevated, unobstructed, with communications and the entire battlefield spread out below. The photograph captures the spatial relationship between the terminal controller and the fight in a way that no other image in the series does.

The UAS Threat Over the Range

Images 12 and 14 document the OPFOR UAS element in operation. Image 12 shows the contractor at OP4 operating an EO/IR spotting or UAS control device on a tripod — a Marine beside him checking a tablet — while the mock city target complex is visible across the desert below. Image 14 shows two Marines from behind, watching a fixed-wing aircraft, one of the contractor-operated threat UAS, flying at altitude over the range.

The two figures watching the UAS in Image 14 capture the essential tactical problem that AST-1 is training. The aircraft is small, fast-moving, and at altitude. It could be conducting ISR on the assault force, providing targeting data for a notional adversary fires system, or itself be a loitering munition. The assault aviation package, the UH-1Ys inserting the ground element, the heavy assault helicopters approaching the mock city, is operating in an airspace that includes this threat.

The integration of a realistic OPFOR UAS into AST-1 is what distinguishes this exercise from the assault support training of the previous generation. In past WTI iterations, the dominant threat to assault aviation was fixed-wing fighters, surface-to-air missiles, and anti-aircraft artillery. Those threats remain. But the UAS threat, small, cheap, numerous, increasingly capable, now shapes the planning, the routing, the timing, and the self-protection calculus of every assault support mission. AST-1 builds that threat into the exercise from the ground up.

The Mock City and the Large-Scale Assault

Images 11 and 15 show the objective area at scale. The Chocolate Mountain Aerial Gunnery Range’s mock city complex is a substantial installation, dozens of building facades of varying heights across a wide front, designed to replicate the visual and tactical geometry of an urban objective. Image 11 shows a helicopter visible far left of the city complex with a dust cloud rising from the objective area — the assault has begun. Image 15 shows the full assault at its peak: multiple helicopters which is identifiable by their large rotor diameter and fuselage mass as CH-53 series aircraft landing near the city complex, raising a massive brown dust cloud that extends across the entire width of the frame.

The scale of Image 15 is the visual argument for why AST-1 matters as a training event. The mock city is in the right frame. The dust cloud from multiple heavy helicopter landings fills the center. The Chocolate Mountain range rises behind it all. The individual elements that have been documented throughout this photographic series, the UAS assembled at OP4, the terminal controllers on the ridge, the UH-1Ys at the rocky LZ, the observer with his radio mast, are all converging on this moment.

What AST-1 Integrates

The fifteen photographs from April 13 at Chocolate Mountain document an exercise that is qualitatively different from every other event in the WTI 2-26 photographic series. The earlier articles in the series — the matting and FARP practical applications, the UAS tactics exercise, the night HIMARS off-load, the UH-1Y rappelling and door gun day —focused on  a specific function or platform in relative isolation. AST-1 runs them all simultaneously.

The contractor UAS flying threat profiles over the range feeds the threat picture that the terminal controllers must account for. The UH-1Ys inserting the ground element must route to avoid the UAS threat while getting their passengers to the right position on time. The terminal control team must manage the aviation package against the objective while tracking the UAS overhead. The heavy assault helicopters must execute their approach and landing at the mock city in an airspace that is simultaneously contested and coordinated.

This is the kill web made kinetic: multiple nodes, sensors, assault aircraft, fire support, terminal controllers, threat simulators, working in a shared operational environment, each dependent on the others functioning correctly, the whole producing a combat outcome that none could generate alone.

The prospective WTI who planned and executed AST-1 at Chocolate Mountain on April 13, 2026, and then sat through the debrief that followed, carried something back to their squadron that could not be generated any other way: the experience of having run the integrated fight, with all of its friction, from the rocky climb to the observation point through the last helicopter lifting off the objective.

That is what WTI certifies. These photographs document why.