The U.S. Navy’s F-35C Lightning II stealth fighter has fired a Long Range Anti-Ship Missile for the first time, according to recent reporting on the weapon’s integration across carrier-based aircraft. The test shot pairs the service’s most advanced stealth jet with a stealthy, precision-guided cruise missile designed to strike enemy warships well beyond radar detection range. The event arrives as the Navy accelerates efforts to arm multiple airframes with the LRASM, a weapon originally developed for the F/A-18E/F Super Hornet, and as tensions over contested waters in the western Pacific sharpen the demand for long-range anti-ship firepower.
Why the F-35C LRASM pairing changes carrier strike planning
Carrier air wings have long relied on the Harpoon missile for anti-ship missions, a weapon with a flight profile and range that increasingly expose launch aircraft to enemy air defenses. The LRASM was built to solve that problem. It flies at low altitude, uses autonomous targeting to avoid jamming, and can reach targets at distances that keep the launching jet outside the engagement envelope of most shipborne surface-to-air systems. Pairing that weapon with the F-35C, which already carries a reduced radar signature, creates a combination that is harder for adversary fleets to detect at any stage of the kill chain.
The practical effect for fleet commanders is straightforward. A carrier strike group equipped with F-35Cs carrying LRASMs can threaten enemy surface combatants without first fighting through layered air defenses to get within Harpoon range. That changes the math for any navy operating large surface formations near contested straits or island chains, because the strike aircraft can launch from a position where it is difficult to track and the missile itself is designed to evade shipboard defenses during its terminal approach.
Until now, the Navy’s publicly documented LRASM integration work has focused on the Super Hornet. Federal procurement records posted on the main SAM.gov portal show multiple contract opportunities tied to LRASM testing, software updates, and aircraft modifications for the F/A-18 platform. Those listings confirm that the service has been investing steadily in making the Super Hornet a reliable LRASM carrier. The F-35C firing represents an expansion of that effort to a second, stealthier airframe, one that could eventually carry the missile as a standard loadout on deployed squadrons.
Procurement records and the gap between public contracts and classified testing
The strongest publicly available evidence of the Navy’s LRASM program sits in federal contracting databases. At least three separate solicitation records on SAM.gov outline work packages for LRASM integration on the Super Hornet. One detailed integration notice lays out requirements for test support and milestones associated with bringing the missile onto the F/A-18. Another technical solicitation document addresses software and hardware modifications needed to make the aircraft compatible with the missile’s guidance and launch systems. A third opportunity, referenced in program summaries, covers additional testing phases and support. All of the visible records name the Navy and LRASM explicitly and focus on the Super Hornet airframe.
None of these publicly posted records reference the F-35C. That absence is significant but not surprising. Weapons integration on the F-35 program often runs through separate program elements, and test activities involving the jet’s stealth characteristics or sensor fusion architecture frequently carry classification restrictions that keep them off open procurement portals. The most plausible reading of the available record is that F-35C LRASM testing is being conducted under a different funding line or classification level than the F/A-18 work visible on SAM.gov. That structure would allow the Navy to push ahead on multi-platform deployment without updating existing Super Hornet solicitations to reflect a second airframe.
This parallel-track approach is consistent with how the Department of Defense has handled other advanced weapons integrations on the F-35. The Joint Program Office manages integration schedules through Block upgrade cycles, and new weapon certifications are often announced only after successful test shots, not during the contracting phase. The public record, in other words, tends to lag the actual state of testing by months or even years. In that context, a first LRASM launch from the F-35C fits a pattern in which operational milestones emerge in limited reporting before they are fully reflected in procurement paperwork or formal capability declarations.
Open questions after the first F-35C LRASM shot
Several pieces of the story are still missing from the public record. No official Navy press release, test report, or program office statement has provided details on the F-35C firing, including the date, location, range conditions, or whether the missile successfully tracked and hit a target. No video or imagery from the test has been released. No statements from test pilots or program managers have appeared in official channels. The absence of that documentation means the specific performance of the LRASM when launched from the F-35C’s internal weapons bay or external pylons has not been independently confirmed through primary sources.
The distinction matters because the F-35C’s weapons bay dimensions and release sequences differ from the Super Hornet’s wing-mounted pylons. A missile that works reliably when dropped from an F/A-18 must still be cleared for safe separation, ignition, and guidance when carried inside the F-35C or hung from its underwing stations. Engineering teams must validate that the missile leaves the bay cleanly, avoids contact with the aircraft, and transitions to powered flight without compromising the jet’s low observable profile more than expected. Those details, including whether the first test used internal carriage, external carriage, or both, remain unaddressed in publicly available material.
There are also unanswered questions about how many LRASM-capable F-35Cs the Navy intends to field in the near term. The service could choose to certify only a subset of squadrons for the mission, treating the missile as a niche capability reserved for specific strike packages, or it could move toward broader fleet-wide integration as production ramps up. Without budget justifications or program briefings that break out LRASM funding by platform, it is difficult to gauge how quickly the F-35C community will receive the hardware and software updates required for routine carriage.
Operational concepts are similarly opaque. The Navy has not publicly described how it plans to mix F-35Cs and Super Hornets in a combined LRASM strike, or whether the stealth jets will be tasked primarily as first-day-of-war shooters, scouts, or targeting nodes. The F-35C’s sensor suite and data links could allow it to cue LRASMs launched from other aircraft, or from surface ships and submarines, without always firing its own missiles. Conversely, commanders might prefer to reserve the limited number of stealth fighters for high-priority targets, using their survivability to get within optimal launch geometries while legacy aircraft remain farther from the threat.
What the first test implies for future carrier air wings
Even with these gaps, the first LRASM shot from an F-35C points toward a carrier air wing built around longer-range, networked anti-ship fires. If the missile is eventually cleared for both internal and external carriage, a single F-35C could carry multiple weapons while retaining some degree of stealth, especially during the opening stages of a conflict when penetrating air defenses is critical. As integration matures, the Navy could field strike packages in which stealth fighters silently approach the edge of contested zones, launch LRASMs from outside most shipboard engagement ranges, and then pass targeting updates to other platforms as the missiles close on their targets.
For potential adversaries, that evolution complicates planning. Surface action groups would have to assume that any carrier operating within several hundred miles of a contested region might be able to deliver low-observable, autonomous anti-ship salvos without providing clear warning through radar signatures or radio emissions. Defending against such attacks would require more capable sensors, denser air defenses, or a shift toward more dispersed maritime formations. None of those adaptations are quick or cheap.
For the Navy, the combination of the F-35C and LRASM offers a way to extend the relevance of large-deck carriers in an era of long-range anti-ship threats. By pushing the effective reach of carrier-based aviation farther seaward, the service can keep its capital ships at greater standoff distances while still holding enemy fleets at risk. The first test firing does not, by itself, deliver that full capability. But it marks a concrete step toward a carrier air wing in which stealth aircraft and stealthy missiles work together to restore the carrier strike group’s ability to operate near contested waters without unacceptable risk.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
