Ben Obese-Jecty

Ben Obese-Jecty

Conservative — Huntingdon

Speaking in the House of Commons on 14 January 2026

Debate

Ajax Programme

Contribution

I beg to move, That this House has considered the future of the Ajax Programme. It is a pleasure to serve under your chairship, Mr Stuart. This debate has been a long time coming. Such is the Kafkaesque procedure for selecting debates that this application was granted only at the eighth time of asking; I had first requested a debate on this subject on 1 September 2025—over four months ago. Since then, the Ajax programme has gone from on track to throwing a track, and the outlook for the programme and our armoured capability, the future of armoured infantry as a concept and the current deployability of 3rd (UK) Division are now all very much under the microscope. In this debate, I am not seeking to apportion blame, point fingers at individuals or orchestrate a witch hunt. It is clear that the Ajax programme has been failing for a number of years, although I will go on to question some of the recent specific decision making regarding the programme. Accountability sits with successive Ministers. The slow progress on delivery appears to be an issue between the Army, the Department and General Dynamics. We can skip over the potted history of the Ajax programme—others will cover that—but, to paraphrase Rodgers and Hammerstein, “How do you solve a problem like Ajax?” Although it was based on an existing General Dynamics platform, the Army made so many additions and revisions to the existing capability that it is now considered to be bespoke technology. We are talking about a staggering 1,200 capability requirements for each of the six vehicle types under the Ajax umbrella. The March 2022 National Audit Office report on the Ajax programme details the fact that neither the Department nor General Dynamics fully understood some component specifications or how they would be integrated on to the Ajax vehicle, leading to consequential changes to the overall design, disputes between the Ministry of Defence and General Dynamics and, inevitably, programme delays. Both the MOD and General Dynamics have been criticised for underestimating the scale of the work, the technical challenge and the sequencing of the work. General Dynamics blamed the MOD for not having fully defined acceptance criteria; the MOD blamed the General Dynamics safety documentation. The contingency within the programme was quickly used up and the programme was suddenly four years behind schedule. Noise and vibration issues were recognised in mid-2020, with a stop notice issued in June 2021. All dynamic movement and transition activity was halted while the programme underwent a significant reset. The Army resumed training on Ajax in 2023, but paused again in November 2025. The programme’s issues from 2020 to 2021 are well documented. Those issues are a failure to establish effective governance, complex assurance arrangements, high turnover of senior staff, an ineffective programme board, weak project controls—the list goes on. The most stark, however, was “an over-emphasis on achieving its IOC”— initial operating capability— “target date, which meant that it prioritised time and cost over capability. As a result, it pressed ahead with the programme without resolving performance issues.” Given what we know now and the issues encountered less than three weeks after IOC was declared, I would like to hear an assessment from the Minister as to whether he believes that that is still an issue today. Initial operating capability for the Ajax programme was declared on 5 November 2025 by the Government; I stress “by the Government”, because several stages to that process were not made public until last month. The Minister for Defence Readiness and Industry confirmed to me: “All criteria for Ajax Initial Operating Capability…were met on 23 July 2025 and following a period of review, IOC was declared by the Army on 15 September 2025.” We know that only because it was written on a cake in a General Dynamics promotional video of the Minister’s visit to Merthyr Tydfil. Additionally, he confirmed: “Before declaring Initial Operating Capability, I received written assurances from the Chief of the General Staff and the acting NAD”— national armaments director— “that the vehicle was safe to operate. Within the letter note AJAX the vehicle was described as ‘demonstrably safe to operate’.” The Minister added that “prior to Ajax Initial Operating Capability being announced, I sought assurances in writing from the Chief of the Defence Staff and the National Armaments Director that the system was safe to operate, which I received.”

More from Ben Obese-Jecty

Other recent Hansard contributions by the same speaker.

About Hansard

Hansard is the official verbatim record of proceedings in the UK Parliament. Every word spoken in the Commons and Lords is recorded and published — this page is a single contribution from that record.

For Ben Obese-Jecty's full parliamentary record including voting history, expenses and all other contributions, see the Ben Obese-Jecty report card.