This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| F-35 Block 4 | |
|---|---|
| Name | F-35 Block 4 |
| Type | Multirole stealth fighter upgrade |
| Manufacturer | Lockheed Martin |
| Primary user | United States Department of Defense |
F-35 Block 4 is a major modernization increment for the F-35 family developed to expand sensor, weapons, and interoperability capabilities. It builds on prior development strands tied to international partners and defense industrial bases, aiming to field enhanced lethality and survivability across USAF, USN, USMC and allied services. The program intersects with Congressional oversight, prime contractor management, and allied procurement decisions that shape timelines and costs.
Block 4 originated as part of the Long Term Evolution roadmap overseen by the Office of the Secretary of Defense and executed by Lockheed Martin, with technical inputs from Northrop Grumman, BAE Systems, Raytheon Technologies, and national partners including United Kingdom, Australia, Italy, Norway, Japan, Netherlands, and Israel. The effort followed earlier increments such as Block 2A/2B and Block 3i/3F, and was constrained by legislative reviews from the United States Congress and program audits by the Government Accountability Office. Certification planning engaged Federal Aviation Administration-style processes, while export controls involved International Traffic in Arms Regulations and partner-level Foreign Military Sales arrangements.
Structural and systems modifications in Block 4 include hardware changes to integrate new avionics modules supplied by BAE Systems and Northrop Grumman, cooling and power upgrades tied to General Electric-affiliated subsystems, and airframe apertures for conformal carriage tested in collaboration with national labs such as Sandia National Laboratories and Lawrence Livermore National Laboratory. Physical changes addressed provisions for directed-energy and electronic warfare growth paths outlined by the Defense Advanced Research Projects Agency and Office of Naval Research. Industrial workshare affected facilities in Palmdale, California, Fort Worth, Texas, Cambridge, UK, and partner assembly sites in Italy and Japan.
Block 4 centers on a major software rearchitecture coordinated by Lockheed Martin and software integrators engaged with the Defense Information Systems Agency and allied test agencies. New mission computing hardware supports advances in sensor fusion analogous to architectures pursued by Northrop Grumman for the Global Hawk and by Raytheon for the E-2D Advanced Hawkeye. Integration of advanced datalinks referenced by programs like Link 16 expansion and coalition interoperability trials with NATO required software builds to meet security reviews from National Security Agency and cryptographic standards aligned with NIST guidance.
Block 4 enables carriage and employment of next-generation munitions developed by Raytheon Technologies, Lockheed Martin Missiles and Fire Control, MBDA, and Kongsberg Defence & Aerospace, including advanced air-to-ground and anti-ship weapons tested alongside cooperative programs such as Joint Strike Missile trials and integration frameworks used for Joint Direct Attack Munition. Mission systems upgrades incorporated sensors influenced by programs like AN/APG-81 evolutions and electronic attack suites paralleling research conducted by DARPA initiatives. The increment planned to support expanded internal and external stores while maintaining signature and survivability parameters reviewed by Defense Science Board studies.
Testing used government flight test squadrons at Edwards Air Force Base and naval trials at NAS Patuxent River, with instrumentation support from Air Force Test Center and Naval Air Systems Command. Certification timelines referenced standards from Department of Defense test and evaluation guidance and involved interoperability trials with partner air forces at ranges in Australia and Norway. Fielding was to follow phased Release-to-Service milestones with sustainment arrangements negotiated under Defense Logistics Agency frameworks and contractor logistics support contracts with performance metrics tied to Performance Based Logistics concepts.
Block 4 attracted scrutiny over cost growth and schedule slips subject to congressional hearings in United States Senate and United States House of Representatives defense committees. Contracts were negotiated via United States Department of Defense procurement authorities with prime subcontracts awarded to Rolls-Royce-accredited firms in United Kingdom and component suppliers across partner nations. Affordability analyses referenced past acquisition reform debates involving the Packard Commission-era reforms and current practices from the Office of Cost Assessment and Program Evaluation.
When fielded, Block 4 was expected to expand mission sets for users including the United States Air Force, United States Marine Corps, United States Navy, Royal Air Force, Royal Australian Air Force, Italian Air Force, Royal Norwegian Air Force, Royal Netherlands Air Force, and other partners engaged through Foreign Military Sales. The upgrade aimed to affect tactics, training, and joint concepts of operations codified in doctrine from the Joint Chiefs of Staff and allied planning processes within NATO and regional coalitions. Logistics and maintenance implications were coordinated with partner sustainment agencies such as Defense Logistics Agency and national ministries of defense.