US Navy’s MQ-25 Stingray: Background And Issues For Congress

Eurasia Review  |  Daniel M. Gettinger

The U.S. Navy initiated low-rate initial production for the MQ-25 Stingray in May 2026 following the uncrewed aerial tanker’s first developmental flight in April 2026, targeting an updated initial operational capability date of 2029. Designed to deliver 14,000 pounds of fuel at 500 nautical miles, the Boeing-built Stingray will assume mid-air refueling duties to free carrier-based F/A-18E/F Super Hornets for primary combat missions.

This transition addresses critical carrier air wing reach and operational fatigue, establishing the infrastructure for future uncrewed combat platforms operating via the Lockheed Martin-developed Unmanned Carrier Aviation Mission Control System. However, total acquisition costs have climbed to $19.4 billion—or $255.8 million per aircraft—amid technical risks, schedule delays, and a labor strike that pushed operational fielding four years beyond original timelines. For FY2027, the Navy requested $1.75 billion to procure three aircraft and continue development, despite congressional oversight concerns regarding concurrency risks.

Comment

Integration of the Unmanned Carrier Aviation Mission Control System onto USS Theodore Roosevelt represents a structural shift from platform-centric control to distributed shipboard command architecture. Standardising ship-installed MD-5C consoles decouples uncrewed flight operations from dedicated aircrew stations, embedding drone management directly into carrier strike group command nodes. This software-defined control environment allows real-time tasking across multiple uncrewed vectors without expanding the physical footprint of shipboard launch controls. Consequently, the operational bottleneck shifts from physical flight deck space to electromagnetic spectrum bandwidth and data-link resilience in contested maritime domains.

Strategic Question for Discussion

If electromagnetic jamming or satellite link disruption degrades the Unmanned Carrier Aviation Mission Control System during launch, which command architecture adjustments take precedence — defaulting flight authority to localized automated routines or retaining manual intervention via airborne tactical air controllers?

Share your assessment in the comments below.

To read in details click here