Open data on public expenditure — datasets, categories and a SPARQL endpoint for research and analysis

UK Defence Fuel and Armoured Fleet Logistics Spending

Budget lines for personnel, land systems and bases often hide a recurring question: how much of the Ministry of Defence budget goes into keeping tracked and protected vehicles moving, and how much is consumed by the support activity around them. Fuel can look like a small operational line, yet tankers, generators, recovery trucks, spare parts and movement between depots sit within a wider logistics cost. PublicSpending.net makes the underlying payment record available for closer inspection rather than asking readers to accept a headline figure.

For an Australian audience, the comparison is immediately useful. The Australian Army operates vehicles such as the Abrams, Bushmaster, ASOV and NLAV, while installations around Darwin, northern Queensland and Western Australia create long supply chains shaped by distance, fuel prices and freight. Australians often speak plainly about where “defence dollars” go, but defence accounting can be just as opaque in Canberra as it is in London. The relevant figures also require care: British financial years end on 31 March, Australian financial years run from 1 July to 30 June, and a payment for fuel does not automatically reveal how many litres a particular vehicle consumed.

What public spending records reveal

PublicSpending.net is an independent, self-funded research initiative that gathers and standardises public payment records. Its UK coverage can be examined through datasets, tables, statistics, graphs and bulk downloads. The associated SPARQL endpoint and ontology-based tools allow users to trace relationships between government bodies, suppliers, transaction dates, amounts and spending types. These features make it possible to search beyond a single annual total and identify the organisations connected to a Ministry of Defence payment.

A payment record is not the same thing as a consumption record. An invoice may describe diesel, but it may combine fuel with delivery, storage or emergency services. Other transactions may include fleet maintenance without showing which vehicle received the work. The accounting basis also matters: records may reflect cash movements, accrued liabilities, purchase orders or expenses reported for a particular period. A £ amount therefore establishes that a transaction was recorded, not that the equivalent number of litres entered a particular armoured vehicle.

The most reliable approach is to preserve these distinctions in the data itself. Each result should identify the supplier, payment date, amount, reporting period and source record, while also separating direct fuel purchases from broader transport or maintenance expenditure. Ontologies and consistent category labels help prevent an energy contract from being mistaken for operational fuel consumption, while a SPARQL query can expose related suppliers that a keyword search might overlook.

Fuel, vehicles and the logistics chain

The UK armoured fleet is not a single vehicle type. Programmes involving Challenger 2, Warrior and Ajax, together with deliveries of Boxer, cover different engine sizes, loads, operating environments and readiness requirements. Their fuel use cannot be reduced to a common kilometres-per-litre figure. Armoured vehicles spend much of their time stationary, operate with heavy loads, train under tactical conditions and travel at speeds that offer little useful economy. Fuel use during idling, towing, movement between bases and participation in exercises may therefore be more informative than published road-consumption figures.

Fleet consumption also depends on how fuel reaches the vehicle. Some purchases enter through central supply arrangements, while others may appear under logistics, fuel services or general energy contracts. Meaningful analysis requires several measures: litres delivered, litres per vehicle, litres per 100 kilometres, engine hours and the share of consumption connected to training, deployment or routine movement. Where the public records do not contain these measures, they should be marked as unavailable rather than estimated from expenditure alone.

Logistics extends well beyond the fuel placed in a tank. It includes spare parts, tyres, recovery equipment, routine and corrective maintenance, trained technicians, workshops, warehousing, road transport, rail movement and shipping. Support vehicles and portable generators consume fuel as well. Adding every Ministry of Defence logistics payment to the fuel total would risk double counting, so the analysis needs to distinguish platform consumption from the systems that sustain those platforms.

Comparing the UK figures responsibly

A defensible estimate begins with observable payments to fuel and energy suppliers connected to defence activities. Those records can be grouped, checked against relevant contracts and tested for duplicate transactions. A second layer may identify transport operators, maintenance providers and depot services whose invoices include fuel-related components. Contract descriptions and supplier relationships are especially useful where payment descriptions are brief, while the SPARQL endpoint allows those relationships to be tested across different datasets.

Comparisons then require a common measurement period. A full UK financial year should not be compared directly with a partial year, and nominal amounts should not be treated as real changes in consumption. Exchange-rate treatment requires an explicit choice: a transaction-date rate, an annual average rate or a purchasing-power adjustment. Currency conversion is particularly important for Australian readers because defence contracts, diesel prices and support costs can move differently in sterling and Australian dollars.

The public spending figures should also be labelled by evidence strength. Direct fuel payments form one category; contracts that combine fuel with delivery form another; estimated vehicle consumption forms a third. Presenting these categories together without qualification would give a false impression of precision. A transparent table can still answer useful questions, such as whether fuel-related payments are concentrated in a small group of suppliers, whether logistics costs rise with major fleet activity, or which categories require a detailed contract check.

Lessons from an Australian defence context

Australia offers a useful operational contrast because its armoured fleet combines tracked and wheeled vehicles and serves widely dispersed locations. An Abrams operating near Darwin, a Bushmaster or NLAV supporting forces across northern Australia, and an ASOV used for specialised roles do not share the same fuel profile. The phrase “down south” may describe the move of personnel and equipment toward southern logistics hubs, but the fuel consumed during that repositioning remains part of the force’s operational footprint.

Geography also changes the economics of support. Remote bases can depend on road, sea or air resupply, with freight charges adding to the cost of every delivered component. Fuel bought in bulk through commercial arrangements may benefit from lower wholesale prices, yet delivery, storage and shortage risks can offset those gains. Australian diesel excise, regional fuel markets and the cost of holding stocks far from major depots therefore belong in any comparison with the United Kingdom. These local realities show why a national fuel total alone is an incomplete measure of fleet efficiency.

Australian procurement provides another useful lens. AusTender notices, standing supply panels and contract schedules can be examined alongside UK payment records, while GST treatment and the Australian dollar must be handled explicitly. The purpose is not to transfer a UK figure directly into an Australian budget. It is to build a comparable chain from litres purchased to vehicles supplied, distance travelled and logistics support delivered. That chain can explain why one country’s spending per vehicle differs from another’s without assuming that one fleet is inefficient.

Turning expenditure data into scrutiny

PublicSpending.net’s UK tables and downloads provide the starting point for reproducible analysis. A user can isolate Ministry of Defence records, filter them by supplier or period, inspect the underlying transactions and export the results. The SPARQL endpoint adds a way to test relationships between organisations and categories, while ontology-based tools can help distinguish a direct fuel payment from a mixed logistics invoice. Keeping the query, filters and classification notes alongside the output makes the exercise more useful than publishing a graph without its method.

The evidence should feed a structured assessment of efficiency rather than a simplistic campaign against fuel use. A rise in expenditure might reflect more training, a larger deployed force, longer supply routes or higher diesel prices. Lower expenditure might result from reduced activity rather than better vehicle management. A credible assessment would publish the baseline, identify which costs are directly observed, and measure operational outcomes such as vehicle availability, fuel consumed per engine hour and logistics cost per supported unit.

Public participation can add value, provided the process is as transparent as the underlying data. If local panels are invited to rank defence priorities or infrastructure needs, voting procedures should be made explicit; a Czech civic association’s polling room guidance provides a practical example of why clear participation rules matter whenever public preferences are formally recorded. The same principle applies to spending analysis: readers should know which figures are official, which have been classified and how any recommendation was reached.

Begin with PublicSpending.net’s UK Ministry of Defence coverage, download the relevant records and save the exact query used to isolate them. Compare fuel payments with logistics and maintenance transactions, then label every calculated figure according to its evidential basis. Publish the findings with their source data, methodology and currency assumptions intact. Start with the raw records, preserve the distinction between spending and consumption, and make the resulting analysis available for Australians to test for themselves.