CAMP GRAYLING, MICHIGAN (NADWC) — During Northern Strike, a U.S. Army National Guard soldier used a tablet to command an optionally piloted Black Hawk through a sling-load operation under field conditions. The aircraft carried a load approaching 3,000 pounds while the autonomy stack managed load oscillation, a task that normally requires direct pilot compensation.

By placing a tablet interface in the hands of a non-aviator to plan and execute the mission, the Army has moved flight control authority outside the cockpit. Timing, routing, and task completion are now functions of system design, not pilot-specific proficiency.

The implications carry immediate institutional weight. The Army is addressing a manpower constraint inside aviation without expanding the pilot pipeline. By relocating mission authority outside the aircraft, the UH-60MX reduces reliance on warrant officer availability while sustaining mission output across the force.

The transition introduces a new control burden. The operator becomes part of the aviation command chain, creating a training dependency the force hasn't fully defined. That logic feeds into Future Long Range Assault Aircraft development, where autonomy and control architecture will determine how vertical lift scales across future formations.

The system enabling this shift traces back to DARPA's ALIAS program and now operates through Sikorsky's MATRIX autonomy stack. The UH-60MX's transition to full-authority fly-by-wire is what makes the system executable, replacing mechanical flight control linkages with a digital architecture that MATRIX can directly command.

Sikorsky and DARPA demonstrate autonomy aboard an optionally piloted Black Hawk, showing the early framework behind later MATRIX-enabled flight operations.

Media: Sikorsky / DARPA (2019)

That prerequisite matters. The UH-60L and UH-60M retain mechanical flight control linkages that would require significant structural overhaul before MATRIX could operate at full authority. The MX is the first Army-owned Black Hawk where the digital backbone exists at the level the autonomy stack requires.

In that configuration, the platform functions as a living laboratory for MOSA compliance, validating whether an open architecture can absorb new autonomy capabilities across successive upgrades without airframe redesign. The open architecture aligns with FACE and SOSA standards, the DoD frameworks intended to ensure autonomy capabilities can be integrated, updated, and transferred across platforms without vendor lock-in.

Operators assign routes, manage flight behavior, and execute mission tasks through a tablet interface. Command input becomes aircraft action across pilots, operators, and onboard systems. The UH-60MX expands how rotary-wing aviation can be controlled and tasked. That networked control structure positions the UH-60MX as more than a transport asset.

As the Army expands its use of air-launched effects, small expendable systems released from rotary-wing platforms into contested airspace, an optionally piloted Black Hawk operating within a distributed control architecture becomes a viable control node for those systems, extending reach without extending risk to crew.

"This capability will enhance mission effectiveness and survivability for warfighters today and lay the groundwork for tomorrow's networked systems," said [Rich Benton, Vice President and General Manager, Sikorsky.]

Northern Strike represents the point where autonomy moved from controlled demonstration into operational application. The aircraft still performs the same mission, but the method of control is beginning to change around it. The question of whether the force could execute tablet-directed autonomy under field conditions has now been answered. What follows is determining how broadly that control model can scale across Army aviation.

Technical Analysis: For a deeper look at the MATRIX autonomy stack, fly-by-wire architecture, datalink survivability, and SWaP-C tradeoffs behind the UH-60MX, read Inside the UH-60MX Autonomy Architecture.

Key Takeaways