F-35 Joint Strike Fighter: Current Status and UK Implications
Part of my wider series on F-35. As always, views my own - facts can and should be corrected if wrong.
This follows the GAO report.
1/25 The F-35 Joint Strike Fighter remains a critical asset in modern military aviation, blending stealth, advanced sensors, and networked systems to bolster combat prowess for the United States and its allies. As outlined in the U.S. Government Accountability Office (GAO) report just released (and getting lots of attention), the programme has delivered over 1,100 aircraft since production commenced in 2006. However, it continues to face substantial cost overruns and schedule delays. Total acquisition costs now surpass $485 billion, an $89.5 billion rise from the 2012 baseline, primarily due to modernisation efforts. Sustainment costs over the aircraft’s 77-year lifecycle are projected at $1.58 trillion, pushing the overall expense beyond $2 trillion.
For us (United Kingdom), a key (tier 1) partner contributing to development, production, and sustainment, these issues manifest as operational shortfalls and strategic risks. This thread tries to explore the F-35’s status, emphasising UK effects, drawing on the GAO report and other recent developments.
Programme Challenges: Cost Escalations and Delays
2/25 The GAO highlights modernisation as the chief culprit for inefficiencies. The Block 4 effort, a $16.5 billion initiative to enhance hardware and software for capabilities like new weapons and radar improvements, is over $6 billion above original estimates and at least five years delayed, with completion now eyed beyond 2031.
The programme is trimming Block 4 scope to prioritise deliverable elements by 2031.
A critical enabler, Technology Refresh 3 (TR-3)—a $1.9 billion hardware-software suite—has been a major bottleneck, but recent updates indicate completion of software upgrades in June 2025, rendering aircraft combat-capable. Despite this, TR-3 delays contributed to 72 aircraft deliveries in 2025 facing holdbacks.
Production woes persist: Contractors Lockheed Martin and Pratt & Whitney delivered all 110 aircraft and engines late in 2024, averaging 238 days behind schedule.
GAO Recommendations for Improvement
3/25 The GAO critiques incentive structures, noting Lockheed Martin earned millions despite delays, as contracts permitted up to 60 days’ lateness for partial rewards. Recommendations include assessing Lockheed’s delivery capacity, revising incentives for better alignment, and broadening leading practices like iterative design and digital twins.
These systemic issues affect all users, but international partners like the UK bear heightened risks from U.S.-led timelines. The GAO observes that while partner input is sought, delays in shared upgrades impede custom capabilities, often favouring U.S. priorities.
Software Hurdles: Core to Delays and Combat Readiness
4/25 Software remains central to F-35 setbacks, directly impacting usability. The GAO identifies immature TR-3 integrated core processor designs as a primary cause, leading to instability in weapons, sensors, and mission systems. Developmental testing uncovered bugs, prolonged by integration issues, supply chains, and insufficient infrastructure.
Without stable software, aircraft miss full Block 4 features, curtailing sensor fusion, threat detection, and precision strikes—key F-35 strengths. Non-combat-capable deliveries in 2024 limited use to training until 2025 upgrades. The GAO advocates iterative methods and virtual testing for faster resolutions, though adoption is partial.
UK-Specific Ramifications: Dependency on U.S. Timelines
5/25 For the UK, software delays ripple into national initiatives. U.S. prioritisation of its weapons may defer partner needs, given joint governance favours American requirements. As of September 2025, we operate 37 F-35Bs, with “plans” for 138 total (likely 72ish) , including 12 F-35As announced in June 2025 for nuclear and conventional roles. This shift, per the 2025 Strategic Defence Review, supposedly bolsters NATO commitments.
SPEAR 3 Delays: A Critical Gap for UK F-35B
6/25 The UK’s F-35B, flown by the RAF and RN, illustrates U.S.-centric delays’ impact. The MBDA SPEAR 3 package, designed for internal carriage enabling up to eight per aircraft for stealthy suppression of enemy air defences, faces integration postponement to the early 2030s due to supplier issues, shortages, and F-35 software delays. Originally planned for 2025, then 2028, and now early 2030’s - the timeline reflects low confidence.
Why Software Matters for SPEAR 3
7/25 Block 4 and TR-3 updates are essential for SPEAR 3 compatibility with F-35 mission systems for targeting and guidance. Delays stem from U.S. focus on its integrations, like JASSM, (potentially) sidelining partners. Without SPEAR 3, the F-35B lacks deep-strike capability, failing Key User Requirements (KUR) for precision attacks while preserving stealth.
The UK is (potentially) looking at interim solutions like the U.S. StormBreaker bomb to bridge the gap.
Broader F-35B Challenges: ODIN and Maintenance
8/25 Additional hurdles plague the UK F-35B. The ODIN maintenance system, replacing ALIS, has rolled out slowly in 2025, hampered by funding cuts and predictive analytics failures, causing spare parts shortages. A notable incident: A UK F-35B stranded in Thiruvananthapuram, India, since 14 June 2025, due to an unscheduled landing and parts delays (plus some other reasons I’ve covered in other threads on the F-35).
MADL and Availability Issues
9/25 The Multifunction Advanced Data Link (MADL) limits networked operations amid general readiness woes, including corrosion identified in January 2025. Availability stands at one-third fully mission-capable, below targets, due to personnel shortages, infrastructure gaps, and supplier delays, lagging the global fleet average. Temporary boosts occurred for the April 2025 Carrier Strike Group deployment.
Carrier Enabled Power Projection (CEPP) and FOC
10/25 Without SPEAR 3 and full capabilities, the F-35B threatens Full Operating Capability (FOC) for CEPP and the Lightning Force. CEPP, integrating F-35Bs with Queen Elizabeth-class carriers, targets FOC by end-2025, demonstrated via the 2025 CSG deployment with up to 24 aircraft. This two-year delay from original plans undermines carrier strike ambitions. It’s not great - let’s see how they dress this up and get FOC without hitting KUR’s.
Leadership Transition: Sir Rich Knighton as CDS
11/25 Air Chief Marshal (ACM) Sir Rich Knighton assumed the role of Chief of the Defence Staff on the 2nd of September (this week), succeeding Admiral Sir Tony Radakin. As former Senior Responsible Owner for CEPP and Chief of the Air Staff, his engineering expertise potentially equips him to tackle these gaps. We shall see, no NAD as of yet.
Knighton’s Familiarity with CEPP
12/25 Knighton’s prior roles make him intimately aware of CEPP challenges, including F-35B integration delays. Balancing user requirements against fiscal and programmatic realities will be one of his first key tests.
DSEI 2025: Spotlight on Mitigations
13/25 The Defence and Security Equipment International (DSEI) exhibition, running from the 9-12th of September 2025 at ExCeL London, should intensify scrutiny. Commentators, politicians, and industry will expect updates on F-35 mitigations, such as interim weapons and software fixes. The UK continues to explore (RAF driven) options like additional F-35As for nuclear roles, but KUR shortfalls persist.
Complex UK Air Domain: Typhoon Upgrades
14/25 The UK’s air strategy is intricate amid pressures. Typhoon enhancements, including a further £204.6 million for the ECRS Mk2 radar, promise electronic warfare boosts from (earliest) 2028, with flight tests potentially concluding at the end-2025. Unions continually lobby for more Typhoons to sustain jobs and counter F-35 reliance.
GCAP Introduction
15/25 The Global Combat Air Programme (GCAP), partnering the UK, Japan, and Italy, targets a sixth-generation fighter by (optimistically) 2035. A joint venture launched in June 2025, with contracts anticipated by year-end, involves over 1,000 suppliers for economic benefits. Chances of new partners diminish as time goes on but we watch the France/Germany spat, like the Spanish, with interest.
Economic Context
16/25 These initiatives unfold against a UK economic outlook projecting 1.2-1.3% GDP growth in 2025, but with high borrowing costs lack of confidence in the economy, tempered by inflation, weak productivity, and trade tensions. Budget constraints could strain funding, defence isn’t high on the government agenda pressured by the NHS, social care and immigration concerns.
Balancing Priorities in a Downward Outlook
17/25 With steady unemployment but domestic issues stifling growth, the new CDS must navigate these fiscal headwinds while advancing Typhoon, GCAP, and F-35 efforts whilst balancing all the other demands of an MoD that needs investment but also needs to manage obsolescence and potentially make more (visually) painful cuts to allow new investments to happen.
Conclusion: Persistent Issues and UK Vulnerabilities
18/25 The F-35 programme’s challenges—rising costs, software delays, and production issues—underscore concurrency risks, as per the GAO report. For the UK, this means SPEAR 3 postponements to the 2030s, unmet KUR, and a delayed CEPP FOC until those requirements can be met. To declare FOC before the capability has been delivered (this is even before we discuss Crowsnest and a complete lack of organic AAR) would be disingenuous.
19/25 Low availability (one-third mission-capable), ODIN rollout delays, and MADL limitations erode readiness. The 12 F-35A acquisitions for nuclear roles and “training” offer some diversification but also reduce clarity as the RAF seek to regain a solid foothold in the F-35B programme (I expect comments on that one - by design).
20/25 Amid Typhoon ECRS Mk2 upgrades and GCAP progress, economic forecasts of 1.2-1.3% growth in 2025 present funding challenges which will have to be navigated and not ignored or pushed further to the right (the next parliament seems to be the current governments trick at the moment). The nettle has to be grasped - ambition and reality have to be balanced.
Challenges for the New CDS
21/25 ACM Sir Rich Knighton, fresh in post, faces reconciling those user needs with realities—advocating for mitigations at DSEI 2025 (9-12 September) while managing union calls for more Typhoons and GCAP ambitions. Something for the new NAD to understand as well.
22/25 Implementing GAO suggestions via enhanced practices could alleviate issues, but inaction risks diminishing UK air power in a contested world, especially as the delivery of air power changes in a world of “one way effectors) and 1960’s long range ballistic missiles.
23/25 Union lobbying underscores domestic stakes, with Typhoon production halting in July 2025 absent of new UK orders and no GCAP orders for the foreseeable future. Does the UK covert funds from F-35 to Typhoon?
24/25 Interim measures like StormBreaker and F-35A buys provide bridges, but core software and integration delays demand urgent transatlantic collaboration. What happens if the Uk buys Stormbreaker, does that mean SPEAR 3 gets cancelled, where will the money come from to pay for it? Satisfying short term operational needs against longer term strategic outcomes isn’t always the right answer.
Summary
25/25 The F-35’s travails highlight alliance dependencies, urging the UK to press for equitable progress. Knighton’s leadership arrives at a critical juncture—DSEI may reveal paths forward. For the rest of us these facts underscore the need for vigilance on readiness and investment. The GAO report isn’t great as articulated by @FTusa284 and @ValkStrategy and others.
What is the answer to the UK’s OCA and DCA et conundrum @gregbagwell @NavyLookout @WarshipsIFR
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Introduction to the AN/APS-154 Advanced Airborne Sensor
Following the recent Red Sea “interception” of a P-8 and my thread on the system (the airframe is just the platform that gets the sensor where it needs to be) I thought it would be useful to describe what the “sensor” was clipped to the fuselage.
As always, views my own and facts can be corrected. @Raytheon_UK
1/25 The AN/APS-154 Advanced Airborne Sensor (AAS) is a state-of-the-art multifunction radar developed by Raytheon (now RTX Corporation) for the United States Navy’s P-8A Poseidon maritime patrol aircraft. Designed for intelligence, surveillance, reconnaissance, and targeting (ISR&T), the AAS represents a significant advancement in airborne radar technology. This thread attempts to follow its development from conceptualisation to operational deployment, elucidates its functionality, and examines its integration with the P-8A.
Furthermore, it explores opportunities for the United Kingdom and NATO allies—Canada, Norway, and Germany—to enhance their P-8 fleets, addressing capability gaps such as those left by the we retired Sentinel R1 and soon the Shadow R1, and concludes by highlighting its role as a force multiplier.
Conceptual Origins of the AAS
2/25 The AAS was conceived in the late 2000s to counter evolving threats in littoral and maritime environments, where traditional radars struggled to detect low radar cross-section (RCS) targets, such as stealthy vessels, low-flying drones, or submerged submarines. Building on the classified AN/APS-149 Littoral Surveillance Radar System (LSRS), deployed on select P-3C Orion aircraft, the AAS aimed to enhance multi-function capabilities like moving target indication (MTI) and high-resolution mapping, adapting them for modern asymmetric warfare.
Defining Operational Requirements
3/25 The US Navy (USN) established rigorous requirements for the AAS, mandating all-weather, day-and-night operation independent of optical sensors. The system needed to provide near 360-degree coverage, simultaneous scanning, mapping, tracking, and target classification. It was also required to integrate with networked weapons for real-time targeting, serve as a communications relay, and support electronic warfare (EW) functions. Tailored for the P-8A Poseidon, the USN’s successor to the P-3C, the AAS was designed to operate effectively in contested environments, detecting subtle threats at extended ranges.
The Boeing P-8 Poseidon: An Essential Pillar of Contemporary Maritime Patrol and Anti-Submarine Warfare
1/25 In this quickly put together long thread, I shall attempt examine the Boeing P-8 Poseidon. The thread will attempt traverse its developmental trajectory from initial requirements to full operational service, with a particular emphasis on its integration and utilisation within the Royal Air Force (RAF).
Given the resurgence of underwater threats in the North Atlantic, the RAF’s (and others) recent and ongoing deployment of the P-8 underscores its strategic relevance. This thread is tailored for a predominantly British audience, highlighting RAF-specific applications, whilst attempting to remain relevant for other readers. It will follow my standard format and address the aircraft’s concept of operations, its synergies with complementary assets, the geopolitical significance of the Greenland-Iceland-United Kingdom (GIUK) Gap, specifically including recent multinational activities—and detailed analyses of its sensors, armaments, configurations, and comparisons to predecessors and contemporaries. It will explore the RAF’s infrastructure adaptations, procurement decisions, and the platform’s pivotal role in supporting the United Kingdom’s Continuous At Sea Deterrent (CASD).
As always, all views my own and facts can be challenged. This has been written (at pace) to give some context to the recent events other contributors (@TBrit90 @NavyLookout @pegge49 @auonsson)
For additional context I have worked on the RAF P-8 (not as an aviator) Nimrod MR2 and Nimrod MRA4 (the world’s best ASW long range fixed wing aircraft).
Apologies for grammar and any repetition.
The Boeing P-8 Poseidon demonstrates an uplift in maritime patrol capabilities, evolving from the United States Navy’s (USN) need to modernise its fleet in the face of evolving submarine technologies. For the RAF, the P-8 has restored a critical capability absent since the retirement of the Nimrod fleet, enabling robust surveillance over vast oceanic expanses. Its adoption by NATO allies, including the UK , reflects a collective commitment to countering asymmetric threats posed by advanced submarines from potential adversaries (specially Russian). In recent months, the RAF has markedly heightened its operational tempo with the P-8, deploying aircraft for extended missions in contested waters, thereby reinforcing the UK’s maritime security posture and contributing to alliance-wide deterrence efforts but also (in the RAf’s case) if nine aircraft was enough.
Historical Origins and Initial Requirements
2/25 The genesis of the P-8 Poseidon can be traced to the late 1980s, when the USN identified significant operational constraints in its ageing Lockheed P-3 Orion fleet. Issues such as airframe fatigue, escalating maintenance demands, and diminished range and endurance necessitated a successor capable of sustaining prolonged missions in increasingly contested maritime environments. This led to the initiation of the Multimission Maritime Aircraft (MMA) programme in 2000, which aimed to procure a platform excelling in ASW, anti-surface warfare (ASuW), and intelligence, surveillance, and reconnaissance (ISR), all whilst achieving substantial reductions in lifecycle costs through innovative design and manufacturing efficiencies.
Prospective designs included Lockheed Martin’s Orion 21, an evolutionary upgrade of the P-3; Boeing’s innovative proposal predicated on the commercial Boeing 737-800ERX airliner; and briefly, BAE Systems’ Nimrod MRA4, which withdrew from contention in 2002 due to the absence of a viable American industrial partner (sound familiar?)
Boeing’s selection on 14 May 2004, underpinned by a $3.89 billion system development and demonstration contract for at least 108 airframes, was predicated on the platform’s modularity, leveraging mature commercial technologies to expedite development and mitigate risks. This decision not only addressed the USN’s immediate needs but also laid the groundwork for international variants, including those adopted by the RAF to bridge a decade-long gap in long-range maritime patrol capabilities following the contentious cancellation of the Nimrod MRA4 in the 2010 Strategic Defence and Security Review.
Conception and Detailed Design Phase
3/25 At the conceptual stage, Boeing envisioned a hybrid aircraft that amalgamated the reliability and cost-effectiveness of a commercial jetliner with the specialised requirements of military maritime operations. The design philosophy centred on adaptability, incorporating structural reinforcements by Spirit AeroSystems to endure the rigours of low-altitude flight over turbulent seas, a dedicated bomb bay positioned aft of the wing for ASW munitions, and enhanced wings derived from the 737-900 model, featuring raked wingtips to improve aerodynamic efficiency and range.
Further modifications encompassed advanced electro-mechanical expulsion deicing systems to facilitate operations in adverse weather conditions prevalent in northern latitudes, such as those encountered by RAF crews in the North Atlantic. The cockpit was meticulously optimised for tactical ASW manoeuvres, permitting steeper bank angles and incorporating a responsive autothrottle system, whilst eliminating non-essential audible alerts to minimise distractions during high-stakes engagements. Propulsion was upgraded with CFM56-7B27A engines, each equipped with generators providing 180 kVA—twice the capacity of civilian counterparts—necessitating redesigned nacelles and wing mountings to accommodate the increased electrical demands of sophisticated avionics and sensor suites. This fusion of civilian and military engineering principles not only accelerated the development timeline but also ensured the P-8’s versatility, making it an attractive option for the RAF’s urgent re-establishment of
maritime patrol capability.
The UK SPEAR Weapons Programme: From Conception to Contemporary Challenges
As always views are my own and facts can be corrected.
Introduction
1/25 The Selective Precision Effects At Range (SPEAR) programme represents the cornerstone of the United Kingdom’s efforts to modernise out air-launched munitions, ensuring the Royal Air Force (RAF) and Royal Navy (RN) can deliver precise, standoff strikes in an increasingly contested battlespace. Initiated in the early 2000s, SPEAR emerged as a response to evolving threats and operational lessons from conflicts such as the 1999 NATO intervention in Kosovo, where the limitations of existing weapons in engaging time-sensitive targets became evident. The programme is structured around incremental capabilities, each addressing specific requirements for precision, range, and adaptability. Managed under the Ministry of Defence’s (MoD) Complex Weapons Portfolio, SPEAR collaborates with industry primes like MBDA and BAE Systems (BAES), aiming to provide scalable effects from low-collateral damage to high-impact strikes.
2/25 This thread tries to examine the SPEAR programme from its conceptual origins through development and production phases. It details each capability increment—SPEAR 1, 2, 3, and beyond—assessing their conception, requirements, successes, and lessons learned. Particular attention is given to SPEAR 3’s ongoing challenges, including integration issues with the UK’s F-35B Lightning II aircraft, programme slips, and financial implications. The discussion extends to the removal of Brimstone from the AH-64E Apache requirement, the programme’s impact on Carrier Enabled Power Projection (CEPP), multinational complexities in future increments, and the roles of key stakeholders. Finally, it evaluates value for money and concludes with a balanced appraisal, emphasising SPEAR 3’s critical role in preventing the F-35B from becoming an underutilised asset.
SPEAR Capability 1: Conception, Development, and Assessment
3/25 SPEAR Capability 1 (SPEAR Cap 1) centres on the Paveway IV precision-guided bomb, a dual-mode weapon system designed to enhance the our ability to conduct accurate strikes with minimised collateral damage. Conceived in the mid-2000s as part of the broader SPEAR initiative, which itself stemmed from internal MoD studies predating 2005, SPEAR Cap 1 addressed the requirement for a versatile, all-weather precision munition capable of engaging static and semi-static targets at medium ranges. The primary drivers were lessons from operations in Iraq and Afghanistan, where legacy bombs like the Paveway II and III proved inadequate against urban environments and fleeting targets due to their reliance on laser guidance alone.
Introduction to the UK’s Immigration Protest Crisis
Every now and again I like to focus on different parts of Defence and National Security. Views are my own, I’ve tried to stay apolitical.
1/25 The United Kingdom is grappling with a wave of protests centered on immigration, particularly the Home Office’s use of hotels to house asylum seekers. Demonstrations in Epping, Canary Wharf, and other regions have exposed deep community divisions, fueled by specific incidents and broader policy frustrations.
The recent announcement of “online monitoring units” to track social media has intensified concerns about free speech, further complicating an already volatile situation. This thread tries to examine the protests, their management, the role of agitators, and the risks of escalation if unaddressed.
The Epping Protests – A Catalyst for Unrest
2/25 In July 2025, protests erupted outside the Bell Hotel in Epping, Essex, which has housed single male asylum seekers for years. The spark was the arrest of HGK , a 38-year-old Ethiopian asylum seeker, charged with sexual assault after allegedly attempting to kiss a 14-year-old girl. This incident inflamed local tensions, leading to demonstrations that escalated into violence, with significant implications for community cohesion and public safety.
Escalation and Violence in Epping
3/25 The Epping protests saw over 1,000 participants across multiple dates (July 13th, 17th, and 20th). Demonstrators threw bottles, eggs, and smoke flares, damaging police vehicles and injuring eight officers on July 18. Six arrests were made on 20th July for offenses including violent disorder and criminal damage. Two security guards were also attacked at a bus stop, highlighting the growing aggression.
The Ajax Ares Platform: A Comprehensive Analysis of British Army Modernisation, Peer Comparison, Procurement Challenges, and Strategic Missteps
This is a long read (a shorter version will also be published). Views as always my own and facts or statements can be challenged. Source references are available on request. All sources are open. (I have background in this subject, I drafted some of the questions for the Defence Select Committee during their inquiry into AJAX.
For more in-depth information on this, FRES and other land systems check out @thinkdefence and for Army strategic direction and organisation check out @nicholadrummond
Forward
1/20 The Ajax Ares platform, a key component of the British Army’s Ajax family of armoured fighting vehicles (AFVs), is designed to provide protected mobility and overwatch, replacing the ageing Combat Vehicle Reconnaissance (Tracked) (CVR(T)) Spartan. Developed under the Future Rapid Effect System (FRES) programme, the Ajax family has faced significant delays, technical issues, and controversies, collectively termed the “Ajax scandal.” This essay provides an in-depth examination of the Ajax programme’s original requirements, its historical context, and the technical specifications of the Ares variant, including its power plant, transmission, armour, C2 systems (with a focus on the delayed ZODIAC system’s role in intelligence dissemination), and limited weapon systems. It incorporates a recent statement by Defence Procurement Minister (Min DP) Maria Eagle, confirming Ares’ expanded role in infantry formations alongside Boxer, assessing its suitability, number of dismounts, and whether this reflects original requirements or poor strategic planning. The essay compares Ares with peer platforms—the Swedish CV90 and American M2 Bradley—to highlight its capabilities and shortcomings. It explores the MoD’s challenges, including noise and vibration issues, Parliamentary scrutiny, and the cancellation of the Warrior Capability Sustainment Programme (WCSP). It critiques the platform-for-platform approach, contrasts it with the Royal Navy’s Crowsnest programme, and evaluates the implications of emerging threats like First-Person View (FPV) Unmanned Aerial Vehicles (UAVs). Finally, it assesses the MoD’s damaged credibility and its impact on securing Treasury funding, arguing that systemic procurement failures threaten the British Army’s readiness.
Table of Contents
2/20
1. Introduction
2. Historical Context: The Road to Ajax 2.1 Early Requirements and Predecessor Programmes 2.2 The Future Rapid Effect System (FRES) Programme
3. The Ajax Family: Overview and Variants 3.1 Ajax: The Reconnaissance Variant 3.2 Ares: Protected Mobility and Overwatch 3.3 Other Variants: Athena, Argus, Apollo, and Atlas
4. The Ares Platform: Technical Specifications 4.1 Power Plant and Transmission System 4.2 Armour and Protection 4.3 Command and Control (C2) and the ZODIAC System’s Role in Intelligence Dissemination 4.4 Weapon Systems and Limitations
5. Maria Eagle’s Statement and Ares’ Expanded Role 5.1 Ares in Infantry Formations: Statement and Context 5.2 Suitability for the Infantry Role 5.3 Number of Dismounts and Replacement of CVR(T) Spartan 5.4 Original Requirement or Poor Strategic Planning?
6. Comparison with Peer Platforms: CV90 and M2 Bradley 6.1 CV90: Design and Capabilities 6.2 M2 Bradley: Design and Capabilities 6.3 Comparative Analysis: Ares, CV90, and M2 Bradley
7. The Ajax Scandal: Challenges and Controversies 7.1 Noise and Vibration Issues 7.2 Parliamentary Defence Committee Scrutiny 7.3 The Sheldon Review and Lessons Learned
8. The Platform-for-Platform Approach 8.1 Comparison with the Royal Navy’s Crowsnest Programme 8.2 Implications for Capability Development
9. The Warrior IFV: Background, Upgrades, and Cancellation 9.1 Warrior’s Role and Legacy 9.2 The Warrior Capability Sustainment Programme (WCSP) 9.3 The Recce Variant and Strategic Missteps
10. Emerging Threats: FPV UAVs and Ares’ Vulnerabilities 10.1 The Rise of FPV UAVs and Loitering Munitions 10.2 Ares’ Vulnerabilities and Required Upgrades
11. The MoD’s Procurement Challenges and Treasury Relations 11.1 Systemic Issues in UK Defence Procurement 11.2 Impact on MoD and Army Credibility 11.3 Financial Implications and Treasury Scepticism
12. Conclusion
1. Introduction
3/20 The Ajax family of armoured fighting vehicles (AFVs), developed by General Dynamics Land Systems UK (GDLS-UK), represents the British Army’s most significant attempt to modernise its armoured capabilities since the Cold War. Conceived under the Future Rapid Effect System (FRES) programme, the Ajax family aims to replace the Combat Vehicle Reconnaissance (Tracked) (CVR(T)) family, in service since 1971, with a networked, medium-weight capability for reconnaissance, protected mobility, and support roles.
The Ares variant, specifically, is designed to deliver protected mobility and overwatch for specialist troops, such as anti-tank Javelin teams and snipers, within Armoured Brigade Combat Teams (BCTs) and the Deep Recce Strike BCT.
A recent statement by Min DP (Maria Eagle), made this month (July 2025), confirms an expanded role for Ares in infantry formations alongside the Boxer wheeled vehicle, raising questions about its suitability and whether this reflects original requirements or poor strategic planning.
However, the Ajax programme has become synonymous with delays, technical failures, and mismanagement, earning the label “the Ajax scandal.”
With a £5.5 billion firm-price contract for 589 vehicles, the programme’s challenges—ranging from excessive noise and vibration to the cancellation of the Warrior Capability Sustainment Programme (WCSP)—have raised profound questions about the UK Ministry of Defence’s (MoD) procurement processes and the British Army’s ability to deliver modern capabilities. These issues have been compounded by the delay in the ZODIAC command and control (C2) system, critical for moving intelligence across the battlefield, which has limited Ares’ operational effectiveness.
This essay tries to provide a comprehensive analysis of the Ajax Ares platform, tracing its origins to FRES and earlier initiatives, detailing its technical specifications, and assessing Min DP’s statement on its expanded infantry role. It compares Ares with peer platforms—the Swedish CV90 and American M2 Bradley—to highlight its capabilities and shortcomings.
The essay examines the Ajax programme’s controversies, the platform-for-platform replacement strategy, and comparisons with the Royal Navy’s Crowsnest programme. It also addresses the Warrior Infantry Fighting Vehicle (IFV), its cancelled upgrades, and the implications of emerging threats like FPV Unmanned Aerial Vehicles (UAVs). Finally, it evaluates the MoD’s damaged credibility and its impact on securing Treasury funding, arguing that systemic procurement failures threaten the British Army’s readiness in an increasingly complex threat environment. For those involved is should be an uncomfortable read.
1/25 The CAPTOR radar is the beating heart of the Eurofighter Typhoon’s sensor suite, enabling its air superiority and multi-role capabilities. Developed through a multinational effort, it has evolved from a Cold War-era concept to a cutting-edge system. This thread traces its journey from requirement to operational use, its technology, variants, and relevance today, with a focus on the UK’s investment in the ECRS Mk2. As always views are my own and posts can be corrected if errors are found. This is third in series of UK airborne radars (Blue Fox/Vixen, Fox Hunter and now CAPTOR). Larger radars will be covered soon (Search Water etc).
Origins of the CAPTOR Radar
2/25 The CAPTOR, originally the ECR-90, was born in the 1980s under the Future European Fighter Aircraft (FEFA) programme, aimed at countering Soviet aircraft like the MiG-29. Led by the EuroRadar consortium (UK, Germany, Italy, Spain), it built on the Ferranti Blue Vixen radar from the Sea Harrier FA2, leveraging pulse Doppler technology for superior target detection in cluttered environments.
Heritage and Technological Roots
3/25 The CAPTOR’s heritage lies in Cold War radar advancements, particularly pulse Doppler systems used in the Tornado’s Foxhunter radar. These provided robust electronic counter-countermeasures (ECCM) against Soviet jamming. Collaborative expertise from GEC-Marconi (UK), DASA (Germany), FIAR (Italy), and INISEL (Spain) shaped a radar that balanced performance, cost, and NATO interoperability.