The U.S. Army is putting its first optionally piloted Black Hawk helicopter through real-world testing during a large-scale joint exercise now running across northern Michigan. The trial, embedded within the Northern Strike 25-2 exercise that stretches through August 16, 2025, represents the most concrete step yet in the service’s effort to fly its workhorse utility helicopter without a crew on board. For soldiers who depend on Black Hawks for resupply, medevac, and assault missions, the outcome of these tests will shape how the Army balances human judgment against machine autonomy in combat aviation for years to come.
Northern Strike Provides a Live Proving Ground
Northern Strike 25-2 is not a small-scale technology demo. The exercise spans multiple training areas, including Camp Grayling and other Michigan ranges, giving the optionally piloted Black Hawk access to diverse terrain and airspace conditions that a sterile test range cannot replicate. Dense forests, open water, and active joint operations create the kind of friction that separates laboratory success from battlefield readiness.
The exercise runs through August 16, 2025, according to the Michigan Department of Military and Veterans Affairs, and draws participants from multiple service branches and allied nations. That multinational, multi-domain environment matters because an optionally piloted helicopter will eventually need to operate alongside manned aircraft, ground units, and electronic warfare threats simultaneously. Testing the aircraft in isolation would answer engineering questions but leave operational ones wide open.
By embedding the Black Hawk trial inside Northern Strike rather than staging a standalone flight event, the Army gains data on how autonomous flight software handles congested airspace, shifting mission priorities, and communications that degrade under simulated jamming. Those are the conditions that will determine whether pilot-optional helicopters can actually reduce risk or whether they introduce new failure modes that cancel out the benefit.
Exercise planners can script scenarios that push the system beyond comfortable parameters: last-minute changes to landing zones, unexpected weather shifts, or pop-up threats that force rerouting. Observers can then watch how the autonomy stack prioritizes tasks, whether it defers to human controllers quickly enough, and how well it maintains situational awareness when radios are saturated or degraded. For a platform intended to operate in contested environments, these messy, unscripted interactions with other units are as important as any flight envelope chart.
How ALIAS Makes a Pilotless Black Hawk Possible
The technology enabling these tests is the Aircrew Labor In-Cockpit Automation System, known as ALIAS. Developed through a long-running program that paired the Defense Department with Sikorsky, ALIAS replaces some of the cognitive workload that two pilots normally share. An ALIAS-equipped Black Hawk completed its first uninhabited flight in a milestone that proved the software could handle takeoff, navigation, and landing without anyone in the cockpit.
That earlier flight was a controlled demonstration, not a combat scenario. The gap between the two is significant. Flying a helicopter with no one on board in clear weather over a known route is now well within reach for modern avionics. Flying one through contested or cluttered airspace while coordinating with ground troops who need supplies or extraction is a fundamentally harder challenge. Northern Strike 25-2 sits somewhere between those extremes, offering a semi-realistic operational environment where the Army can stress-test ALIAS under conditions that inch closer to actual deployment.
Technically, ALIAS functions as a kind of robotic co-pilot, integrating with flight controls, navigation systems, and sensors to execute pilot commands or, in fully autonomous mode, to follow preplanned mission profiles. It can manage routine tasks such as holding altitude and airspeed, following waypoints, or conducting approach and landing procedures. The more ambitious goal is for the system to recognize abnormal conditions (such as engine anomalies, icing, or unexpected obstacles) and respond in ways that mirror what a trained pilot would do.
For the average soldier, the practical meaning of ALIAS is straightforward: missions that currently require two trained pilots could eventually require one, or none. Resupply runs into hostile landing zones, where the risk of a shoot-down is highest, could be flown without putting aircrew in danger. Medevac flights at night or in degraded visibility, already among the most dangerous tasks in Army aviation, could shift some of that risk from human crews to software. The tradeoff is trust. Pilots and commanders will need to believe the system can handle emergencies, and that confidence can only be built through exercises like Northern Strike, not PowerPoint briefings.
From Test Flights to the H-60Mx Delivery
The Army’s plan does not stop at retrofitting existing Black Hawks with autonomy kits. A next-generation variant, the H-60Mx, has been designed from the start as an optionally piloted vehicle. According to a Defense Department release, the Army recently took delivery of the H-60Mx Black Hawk, described as a next-generation airframe that begins modernizing the helicopter fleet for the future.
That delivery, documented in a March 2026 Defense Department release, signals the transition from experimental testing to procurement. The distinction matters because experimental aircraft often perform well in trials but stall during production due to cost overruns, supply chain problems, or shifting budget priorities. Receiving an actual production airframe suggests the program has cleared at least some of those hurdles and that the Army sees a path to fielding the capability at scale.
The timeline between the current Northern Strike tests in August 2025 and the H-60Mx delivery roughly seven months later also reveals how quickly the Army is trying to move. Military aviation programs historically stretch across decades. The compressed schedule here reflects pressure from two directions: the Pentagon’s stated urgency to field autonomous systems before potential adversaries do, and the practical reality that the existing Black Hawk fleet is aging and needs either replacement or significant upgrades to stay relevant.
In practice, the Army is likely to pursue a mixed fleet for years, with legacy Black Hawks upgraded through kits like ALIAS operating alongside purpose-built H-60Mx helicopters. That approach allows commanders to allocate the newest, most capable aircraft to the most demanding missions while still squeezing additional life out of older airframes. It also buys time for doctrine, training, and maintenance practices to catch up with the technology, rather than forcing an abrupt transition that units may not be ready to absorb.
Why Skepticism About Autonomous Helicopters Is Warranted
Most coverage of optionally piloted military aircraft focuses on capability gains, but the harder question is what happens when the technology fails in ways that engineers did not anticipate. Autonomous ground vehicles have struggled with edge cases for years in the commercial sector, and rotary-wing aircraft operate in a far less forgiving environment. A software glitch that causes a self-driving car to pull over is an inconvenience. A similar failure in a helicopter flying at low altitude over a forest is a crash.
The Army has not publicly released detailed performance metrics from the ALIAS program’s earlier test flights, and no pilot or engineer statements from the Northern Strike 25-2 trials are available as of this writing. That information gap makes it difficult to assess how close the technology is to genuine operational readiness versus a polished demonstration. The service’s willingness to test during a major joint exercise rather than a closed-range event is encouraging, but it does not substitute for transparent reporting on failure rates, software reliability under stress, and the human-machine interface problems that inevitably emerge when crews learn to work with new automation.
There are also unresolved ethical and legal questions. If an optionally piloted helicopter flying autonomously misidentifies a landing zone or collides with another aircraft, responsibility will not rest on a single human pilot in the same way it does today. Commanders, software developers, and acquisition officials may all share some measure of accountability. The military has grappled with similar issues around armed drones, but extending them to rotary-wing aircraft that operate in close proximity to friendly troops and civilians adds new layers of complexity.
Within aviation units, cultural resistance is another hurdle. Pilots who have spent years mastering the nuances of helicopter flight may be reluctant to delegate key tasks to algorithms, especially in situations where instinct and experience have historically made the difference between a close call and a fatal accident. Overcoming that skepticism will require not just successful test flights, but also training pipelines that teach future aviators how to supervise and collaborate with autonomous systems rather than compete with them.
For now, Northern Strike 25-2 offers a snapshot of a transition in progress. The Army is pushing its Black Hawk fleet toward a future where some missions can be flown without a crew, backed by autonomy software that has matured beyond the lab but still faces unanswered questions in the field. Whether that future arrives as quickly as program timelines suggest will depend less on any single exercise and more on the steady accumulation of data, trust, and proven performance under pressure. The Michigan skies this summer are one test, not the final exam, for a technology that could redefine what it means to fly into danger.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
