Congress wants to ‘unlock’ the F-35s software to break dependence on Lockheed Martin
September 17, 2025
The Senate’s draft National Defense Authorization Act (NDAA) includes a new provision aimed at breaking the F-35’s dependence on Lockheed Martin by opening up its tightly controlled software environment.
Section 135, titled “Plan for open mission systems of F-35 aircraft”, directs the Air Force to establish an “open mission systems computing environment” so that avionics, sensors, and mission software can be upgraded more quickly, at lower cost, and by a wider pool of suppliers.
New NDAA requires F-35 open mission systems
The Senate’s proposal calls for the F-35’s software to be re-architected around open interfaces and common standards.
The goal is to allow plug-and-play upgrades with minimal integration work, enabling new applications or modifications without waiting for Lockheed to re-certify the entire system.
Crucially, the legislation states that the new architecture must be controlled by the United States government, not the prime contractor.
The system is expected to support rapid processor upgrades, connect with all relevant aircraft apertures, and include cockpit Ethernet connectivity. It must also leverage modern commercial software languages and techniques to support “reliable, high-throughput, and low-latency use-cases.”
Importantly, the new environment would apply across all F-35 variants and blocks.
Networking F-35 with other advanced fighter jets
Congress also wants to ensure portability of software applications between the F-35, the F-22, and future sixth-generation platforms under the Next Generation Air Dominance (NGAD) programme — including the manned fighter and its Collaborative Combat Aircraft (CCA) drones.
This reflects the Pentagon’s broader “open mission systems” push, where future aircraft share digital backbones and can swap applications more like smartphones than locked-down weapons platforms.
While Lockheed Martin remains the F-35’s prime contractor and systems integrator, Congress has grown increasingly frustrated with the slow pace and high cost of upgrades under the current proprietary model.
Subcontractors such as Northrop Grumman (radar and mission systems) and BAE Systems (electronic warfare suite) provide critical components, but Lockheed’s control of the overall Operational Flight Programme has given it a near-monopoly on integration.
By mandating open architecture, lawmakers are effectively trying to “unlock” the jet’s software. That could allow more companies — including smaller firms — to compete to deliver mission apps, break Lockheed’s exclusive grip on upgrades, and give the Pentagon greater control over costs and timelines.
Aerospace Global News reached out to Lockheed Martin for comment, but no response was provided before publication.
Challenge of balancing security and rapidly updating the F-35
The challenge remains security. The F-35’s software and mission systems are highly classified, and export customers are barred from modifying them or integrating unapproved weapons.
Opening up the architecture creates new risks, but advocates argue the benefits outweigh them: faster upgrades, a more agile jet, and the ability to keep pace with adversaries.
The debate comes as the F-35 undergoes its most significant upgrade cycle in years. The Technology Refresh 3 (TR-3) package has caused major delivery delays but also dramatically improves onboard processing power. Congress now wants to ensure that future refreshes are faster, cheaper, and less dependent on a single company.
