The U.S. Navy issued a Request for Information on July 14 seeking a family of carrier-based autonomous drones capable of executing eight distinct missions from Ford-class and Nimitz-class nuclear aircraft carriers. The scope is sweeping: surface and land strikes, anti-submarine warfare, air-to-air combat, electronic warfare, intelligence collection, aerial refueling, and resupply operations. The Navy specified no incumbent. No company name appears in the RFI text. Industry has until August 13 to respond, exactly 30 days to demonstrate that a single family of systems, or modular variants of one, can do work that has never been consolidated on carrier unmanned platforms before.
This is not a narrow requirement. The RFI explicitly states the Navy is exploring whether the industrial base can deliver "highly capable, autonomous platforms optimized for operations from Ford-class and Nimitz-class Nuclear Aircraft Carriers." The autonomy bar is precise: platforms must demonstrate "flight autonomy (e.g., carrier pattern, taxiing) and mission autonomy (e.g., dynamic tasking/retasking, threat evasion, automated aerial refueling) maturity." The Navy also requests VTOL variants capable of operating from destroyers and Expeditionary Sea Bases, any air-capable platform, not just carriers. The document says the Navy is "interested in novel concepts," which in procurement language means the field is not predetermined. Single-role platforms are acceptable. Multi-role platforms are preferred. Modular families of systems are invited. No architecture is mandated. That openness is strategic: it forces respondents to prove capability rather than repackage existing programs.
The context matters. The MQ-25 Stingray, now in limited production, covers only aerial refueling, a critical mission but a narrow one. Before MQ-25, the Navy canceled predecessors (UCLASS, CBARS) after years of effort and hundreds of millions in sunk development cost. The new RFI signals that the Navy has learned that lesson: instead of monolithic requirements that lock in a single design, it is asking industry to bid against eight missions simultaneously and prove they can either deliver one family or a modular stack. GA-ASI, Northrop Grumman, Boeing, and Joby all have potential surface area here. So do pure-play autonomy firms like Shield AI and Anduril, which have no legacy carrier programs to defend and can optimize for autonomous control rather than legacy avionics integration. The competitive uncertainty is the point, it keeps the field open.
The real signal embedded in this RFI is architectural. The Navy says it intends to move from fourth-generation carrier air wings to "an air wing composed of fifth- and sixth-generation manned and unmanned aircraft." That language is direct: the future carrier air wing is mixed, not unmanned-only, but unmanned at scale and in multi-domain roles. Eight missions from an autonomous family is not supplementation. It is replacement of manned platforms in defined roles. That shift, if it lands, reshapes the carrier aviation industrial base for a decade. It also answers a question that has hung over autonomous naval systems since the MQ-25 program narrowed: can the Navy buy autonomous platforms at cost-per-effect rates that justify wholesale architectural change, or does it remain committed to manned air as the primary force? This RFI says the Navy is actively hunting for the former.
What matters now is the August 13 response deadline. The quality and diversity of respondents will telegraph whether the field believes this RFI is real or rhetorical. A handful of responses signals skepticism, the Navy is checking the box but not ready to fund. Dozens of responses, particularly from non-traditional contractors and pure-play autonomy firms, signals genuine competitive interest. The next milestone is whether any respondent can actually demo mature flight autonomy in a carrier environment by late 2026 or 2027. Autonomous carrier landing is a solved problem for research platforms; doing it on a production airframe at scale under wartime mission complexity is not. Watch also for consortium bids: whether respondents try to compete as single companies or band together across autonomy, airframe, and integration layers. How the industry structures itself in response to this RFI will reveal whether the competitive field believes it can win alone or whether the Navy's eight-mission requirement forces collaboration.