Brontanax — BX
News · Weekly brief

Open-source intelligence on Brontanax, briefed every Wednesday.

A long-form open-source brief on the UK's Collaborative Combat Aircraft programme, emailed to subscribers once a week on Wednesdays while new information on the programme remains scarce, plus a rotating long-form feature on the wider drone-warfare story — from Ukraine to the Pacific to the ethics of autonomous combat air.

Brief · Sunday, 13 September 2026
Entry #3

The engine question BAE has not yet answered.

BAE Systems has named Rolls-Royce as the propulsion partner for Brontanax without naming an engine. That silence is deliberate and worth reading carefully. The propulsion decision shapes almost every other parameter of the aircraft: unit cost, range, payload fraction, infrared signature, sustainment burden and, critically, exportability.

There are three plausible paths. The first is a derivative of an existing regional or business-jet core, similar to the way the F-124 was derived from the AlliedSignal TFE731. This route minimises development risk, keeps unit cost low and offers a mature global supply chain for spares. It is the fastest way to first flight in the second half of 2027 and the easiest story to sell to export customers.

The second path is a bespoke small combat engine, optimised for low observability and high-altitude cruise. This delivers a better tactical aircraft but adds years and hundreds of millions of pounds to the programme, and locks Brontanax into a UK-only sustainment model that some export customers will resist. It is the option that best fits the Defence Investment Plan's language about "sovereign, world-leading propulsion", but it is the hardest to fund.

The third path — quietly discussed but rarely written down — is a hybrid arrangement in which the demonstrator flies with a mature derivative engine while a bespoke variant is developed in parallel for a production tranche. This de-risks the airframe schedule while preserving the sovereign propulsion narrative, at the cost of committing to two engine variants across the fleet.

The choice will not be announced in a single press release. It will leak out through supplier notices, wind-tunnel photographs, and eventually through a discreet Rolls-Royce line in an investor presentation. Whichever path BAE and the MoD take, the answer will be visible in the airframe itself: intake geometry, exhaust shrouding and the depth of the spine behind the wing all change with the core inside. Read the next official model or wind-tunnel image closely; the engine will be described there before it is named anywhere.

Briefs are editorial analysis, not BAE Systems or MoD statements. New editions are emailed to subscribers weekly, every Wednesday.

Read every previous brief in the archive
Feature · Sustainment
Rotates every 4 days

The part of Brontanax nobody photographs: the ground segment.

Almost every published image of Brontanax to date has been of the airframe. That is understandable — an aircraft is what airshows sell. But the airframe is arguably the least interesting part of the programme from an operational point of view. The part that will actually determine whether Brontanax works as a fielded capability is the ground segment, and it is the part that receives almost no public attention.

The ground segment for a modern Collaborative Combat Aircraft is a substantial system in its own right. It includes the ground stations from which the aircraft is commanded, the secure data-links that carry that command traffic, the mission planning tools that build the tasks the aircraft executes, the intelligence feeds that populate its target picture, the maintenance and diagnostic infrastructure that keeps it flyable, and the training environment that builds the operator cadre. Each of those elements is a programme in miniature.

The cost distribution is instructive. In many uncrewed aircraft programmes, ground segment and sustainment together account for more than half of the total lifetime cost of the capability. Underestimating that portion is one of the classic failure modes of unmanned aviation acquisition, and it has bitten every major Western programme at some point.

For Brontanax specifically, three ground-segment questions matter most. The first is data-link resilience. A CCA operating in a contested electromagnetic environment cannot assume continuous, high-bandwidth connectivity to its ground station or its crewed teammate. The ground segment has to handle intermittent, low-bandwidth or fully denied conditions gracefully, and the aircraft has to remain safe and useful under all of them.

The second is mission planning integration. Brontanax will only deliver on the teaming promise if its mission plans are built inside the same tools that plan Typhoon and, eventually, Tempest missions. Building a bespoke Brontanax planning environment that later has to be integrated with the rest of the RAF's planning infrastructure would be a costly and predictable mistake.

The third is training. Operating a CCA formation is a new skill set, and the simulators, courseware and exercise infrastructure to build that skill set at scale do not yet exist in the RAF. Standing them up in parallel with the aircraft, rather than after it, is a well-known best practice that programmes rarely fund adequately. Whether StormFighter does so will be visible in the next planning round rather than in the next airshow.

Feature essays step back from the day-to-day Brontanax story to examine the wider evolution of drone warfare — the lessons of Ukraine, the shape of the next decade, the industrial base, doctrine, geopolitics and ethics. A new feature rotates in every few days.

Weekly briefing · Wednesdays

Get the Brontanax brief in your inbox every Wednesday.

One long-form edition a week: original editorial analysis of the BAE Systems Brontanax programme, GCAP and the wider CCA landscape. Grounded in open-source sources cited across this site.

Unsubscribe any time. We only use your email to send the briefing.

Primary sources

The reveal, as it was reported.

A fixed record of the original open-source reporting from the Farnborough International Airshow reveal on 22 July 2026. These dates are the publication dates of the source articles and do not change; day-to-day analysis appears in the daily brief above and in the brief archive.