AeroVironment to co-design three autonomous helicopters for NASA's SkyFall Mars mission

AeroVironment’s MacCready Works unit has been awarded a contract to co-design and co-manufacture three autonomous helicopters for NASA’s SkyFall mission to Mars, a rare case where “multi-unit” autonomy is the headline, not an afterthought. The company said Aug. 27 that it is partnering with NASA’s Jet Propulsion Laboratory (JPL) and that the work moves SkyFall from concept into a formally funded Mars science mission with a path toward a late-2028 launch.

For enterprise operators, the Mars angle is the wrapper. The operational lesson is that highly autonomous aircraft are starting to be specified like fleets: multiple air vehicles, shared interfaces, payload accommodation, and a deployment concept built around repeatability and risk retirement. Even in space exploration, the program language is drifting toward something that looks like product lines and production readiness, not bespoke prototypes.

A three-helicopter mission forces fleet-style engineering decisions

According to AeroVironment’s announcement, SkyFall is the first mission planned to fly a team of three instrument-carrying helicopters on Mars, with a system design that supports autonomous atmospheric entry and powered descent. That matters because “three” changes the engineering center of gravity: configuration management, interchangeability, and fault isolation become daily work, not paperwork reserved for later phases.

AeroVironment and JPL are building off their prior Ingenuity collaboration, which completed 72 flights at Jezero Crater, according to the same release. Ingenuity proved powered flight could work in Martian conditions. SkyFall’s premise is different: the aircraft are intended to be instrument carriers, operating as a set, with a mission architecture that assumes distributed coverage and repeatable deployment.

The “SkyFall maneuver” shifts risk to interfaces and verification

The standout operational detail is the planned deployment method. AeroVironment said SkyFall will use a “SkyFall maneuver” in which three helicopters are released from the carrier spacecraft into the Martian atmosphere, then separate, deploy, descend, and land using their own power.

The company framed it as eliminating reliance on a dedicated, single-use lander stage or a host rover, and as reducing the technical and financial risk associated with reaching the surface. In practice, that shifts program risk into a narrower set of verification tasks: carrier-to-air-vehicle interfaces, separation dynamics, autonomous sequence validation, and environmental qualification for the entire deploy-and-start chain. For anyone who has worked through aircraft or robotics programs, it is the familiar pattern where integration ends up driving the schedule.

What AV is responsible for, and what that signals for suppliers

AeroVironment said it is leading design and production of key elements, such as rotor systems, airframes, structures, avionics integration, and provisions for multiple science payloads. JPL is leading the power system, electronics, algorithms and software, according to the release.

That split is a useful map for suppliers and integrators. Mechanical systems and avionics integration sit with an industrial manufacturer that already runs defense programs, while the power, autonomy algorithms, and mission software sit with the lab that has to close the loop on mission assurance. For procurement teams, the message is that the “autonomy stack” is being treated as a system-of-systems, with clear ownership boundaries and an emphasis on qualification-ready integration artifacts (interfaces, harnessing, EMI/EMC plans, and software verification evidence) as deliverables, not internal documents.

The payload also points at how autonomy programs justify themselves operationally. AeroVironment said the helicopters will carry a JPL-designed ground-penetrating radar to map shallow subsurface ice at fine spatial resolution, alongside atmospheric and dust-focused instruments. Multi-payload accommodation means mass, power, thermal, and data budgets become the hard constraints that drive airframe and avionics tradeoffs.

Next public checkpoint: Jefferies talk, Sept. 10

AeroVironment separately said CEO Wahid Nawabi and CFO Sean Woodward will appear in a webcast fireside chat at the Jefferies Global Industrials Conference on Sept. 10. While that notice is investor-facing, it is still a practical milestone for operators tracking how AV is scaling production and software across its portfolio, which the company describes as spanning autonomous systems and an AI-powered software suite it brands AV_Halo, according to Business Wire.

The schedule detail to watch is the one NASA has already placed on the table: a launch window planned for November 2028, according to AeroVironment. If that date stays firm, supplier conversations about long-lead components, qualification capacity, and acceptance test throughput should get concrete fast, because aerospace timelines rarely leave much slack once environmental testing and integration start consuming calendar.

Questions to take into supplier and integrator calls for multi-unit autonomy programs

• What is the program’s configuration strategy across multiple vehicles, including which parts are truly interchangeable and which are serialized by test data or calibration?
• How will the carrier-release or deployment interface be validated end-to-end, and what evidence is required at each gate (analysis, ground test, hardware-in-the-loop, environmental test)?
• Which integration artifacts are contractual deliverables (ICDs, verification matrices, software assurance packages), and who is accountable for closing each verification thread across organizations?
• If a late-2028 milestone is fixed, what are the long-lead items and qualification fixtures that must be reserved in 2026, 2027 to avoid test-lab bottlenecks?