The UK has pumped £708 million into its future fighter jet programme, known as Tempest, according to a source published 23 July. The funding lands alongside a hypersonic target contract and the reveal of BAE's "loyal wingman" drone, the same source indicates.
No further details on the breakdown of the £708 million, the terms of the hypersonic target contract, or the specifications of the loyal wingman drone appear in the source. The items are presented as concurrent announcements without explanation of their interdependence or sequencing.
The source lists the Tempest funding as the lead item on a page that also carries headlines on Google Cloud revenue growth, OpenAI and Hugging Face, sovereign AI commentary, Block's Slack competitor, Russian phishing campaigns, Microsoft SharePoint vulnerabilities, DEF CON infrastructure projects, EQT's acquisition of a majority stake in Acronis at a $3.5 billion-plus valuation, ransomware retrospectives, and various Linux desktop developments. No connective tissue between the defence spending and the other topics is provided.
What the £708 million buys, over what period it is appropriated, and how it relates to prior Tempest commitments are not stated. The source does not attribute the announcement to a specific government department, parliamentary statement, or industry partner beyond the implicit reference to BAE. The hypersonic target contract is unnamed. The loyal wingman drone is described only by its marketing moniker.
Without a budget document, a ministry release, or a contractor disclosure, the £708 million figure stands alone, a headline number without a denominator, a timeline, or a delivery milestone. The loyal wingman reveal is similarly unmoored: no first-flight date, no payload capacity, no integration plan with Tempest or existing platforms.
The only actionable signal is that the UK is putting fresh capital into a sixth-generation fighter effort while simultaneously procuring hypersonic test infrastructure and unveiling an uncrewed teaming asset. Whether the three move on a single schedule or simply share a press cycle is not in the source.
