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

Alaska DNR wildfire aircraft billing records

Alaska's Department of Natural Resources Wildfire Suppression Aircraft Hourly Billing Records provide a transaction-level view of aviation work used in wildfire suppression. They expose the commercial mechanics behind emergency flying: contractor and aircraft details, service periods, billable hours, agreed rates and invoiced amounts. That granular view sits beneath broad budget totals, showing how money moves from a suppression contract to a particular aircraft on a particular operation.

For Australian readers, the records offer a useful way to test assumptions about bushfire aviation costs. They do not reveal whether a fire was contained, whether an aircraft was needed, or whether the operational outcome justified the expenditure. They do show what the public authority paid for flight and related aviation services, giving researchers and communities a factual basis for comparing contracts, spotting spending patterns and asking sharper questions of budget papers.

What the Alaska records reveal

Alaska’s geography makes aviation especially relevant to wildfire management in a state where fires can occur far from staffed bases, roads and towns. The records place a financial trail beside operational activity: a contracted plane or helicopter, hours attributable to its service, and the rate used to produce the invoice. For public agencies, that trail matters because a season total can conceal very different combinations of aircraft, flying time and supporting services.

At their most useful, the entries connect an invoice or payment to an aircraft type, contractor, date or period, number of hours, rate and amount. Some lines may also carry mission, location or service descriptions. Fixed-wing air tankers, helicopters and other aviation resources can therefore be separated rather than blended into one undifferentiated wildfire line. Where a field is absent, however, researchers should treat it as unknown rather than assume it was zero.

The billing view is also narrower than the full cost of fire management. It may exclude aircraft purchased or crewed directly by government, retardant, fuel, command, logistics and restoration. Its strength is specificity rather than completeness. Used with contracts and incident records, it can establish what an agency paid for contracted aviation and whether reported payment totals reconcile with the underlying invoices.

How hourly aviation charges work

An hourly charge normally begins with a contracted rate multiplied by billable time. The rate may cover an aircraft and crew, with the invoice multiplying it by hours flown, hours on standby or another defined unit. A researcher should reproduce that arithmetic line by line, then account for credits, taxes, amendments and adjustments. If the total does not reconcile, the row may combine services or use a different unit, which is a reason to inspect the source rather than force a formula.

A headline rate is not the whole economic cost of an operation. Positioning a contracted aircraft at a fire, a minimum call-out, daily availability, ferry flights and support charges can all affect the amount ultimately paid. Those items may appear in separate rows or be bundled into the contractual rate. This is where Alaska’s records can support a more realistic comparison than treating every flying hour as identical.

Timing also matters. Payments can be dated later than the flight, and a suppression season can cross financial years. Alaska’s fiscal year runs from 1 July to 30 June, while the publication’s standardisation may organise records by payment or invoice date. Comparisons should state the date field, preserve the original dates and, where possible, align both operational and fiscal periods. Otherwise a June flight paid in July can look like two separate spending peaks or disappear from one year’s totals.

Patterns worth testing in the data

Aggregating individual invoices turns them into evidence about public spending. Month-by-month totals can expose the concentration of aviation demand around particular fire periods, while averages by aircraft class can show whether the cost base rests on a few large tankers, helicopter support or a broader mix. Rates should be read as contracted prices rather than market-wide prices: a quoted figure may reflect aircraft capability, remoteness, operating rules, insurance or the scarcity of suitable crews.

Vendor concentration is another useful signal, but it is not evidence of misconduct by itself. A limited number of certified operators may be necessary for remote firefighting, and long-standby contracts can create high annual totals without indicating poor value. The productive questions concern resilience and use: Are multiple aircraft available? Are standby hours concentrated in a few contracts? Do billed hours align with incident activity? Those questions turn a spreadsheet into a subject for public analysis.

Researchers should also avoid turning expenditure into a score of firefighting success. A costly flight may prevent a larger loss, while a cheaper one may be dispatched to a less severe incident. The records can measure cost, activity and contractual structure; they cannot alone establish benefit. Pairing them with incident dates, fire size, weather and operational outcomes produces a fairer analysis and keeps the strongest claims tied to what the evidence can actually support.

Comparing jurisdictions without false equivalence

For a European benchmark, Greece’s fire service procurement records sit alongside Alaska’s operating payments. The Greek material focuses on equipment and vehicle replacement, while Alaska’s dataset follows recurrent aviation services. Read together, they distinguish capital renewal from operational expenditure. A jurisdiction buying fire appliances or ground vehicles is doing something different from a jurisdiction paying aircraft to remain available and fly suppression missions.

That distinction also prevents misleading comparisons based on one total figure. A ranking of wildfire expenditure would mix replacement purchases, aircraft operating costs, crews, retardant and broader emergency management. Currency conversion alone will not solve the problem. Researchers need separate categories for assets, aviation hours, personnel and consumables, then note differences in government structures and the stage of each aircraft’s life cycle.

Cross-jurisdiction work becomes stronger when rates are normalised without erasing context. One option is to index costs to a common price year while retaining the original nominal values for audit trails. Another is to compare a defined measure, such as the published cost per contracted aviation hour or per non-mission standby hour. Federal systems, local labour costs and operating environments still differ, so the output should be a carefully framed comparison rather than a universal ranking.

What Australian buyers can learn

Australian readers already recognise the pressure created by bushfire seasons and the uneven reach of aircraft across a large, hot continent. The local institutional map also matters: the NSW Rural Fire Service, Victoria’s Country Fire Authority, Queensland Fire and Emergency Services and the Tasmanian Fire Service each lead suppression responsibilities within their own jurisdictions, with Commonwealth assistance available for major emergencies. That arrangement differs from Alaska’s statewide landscape, so agency scale and responsibilities belong in every comparison.

Terms used by crews and operators can guide the search for useful fields. Australian operations commonly describe waterbombers, retardant runs and aircraft operating from regional hubs such as Mildura. NSW crews also use “smoke more” for a period when fire danger is extreme. These expressions are not accounting categories, but they reveal practical distinctions that a clean dataset can encode: air tanker versus helicopter, operating versus positioning, and mission versus standby.

Contract design is another lesson. An Australian tender might separate the aircraft hourly rate from call-out, mobilisation, standby, fuel, retardant, hangar and inspection charges. Publishing each element in a consistent machine-readable field would let councils, fire agencies and auditors compare like with like. It would also support value-for-money checks without forcing every market into a single headline figure.

Open procurement rules provide the practical route to those checks. AusTender and state e-tendering systems create a familiar public record, but published notices are not always the same thing as paid invoices. Publishing invoice-level aviation usage alongside the tender, rate card and amendments would close that gap. For Australian agencies, the goal is not to copy Alaska’s file structure blindly; it is to preserve the same chain from negotiated price to flight hour to public payment.

From raw payments to public evidence

PublicSpending.net is an independent, self-funded research initiative that makes government expenditure data openly accessible. Its datasets, tables, statistics, graphs and bulk downloads present standardised public payment records for study and reuse. The SPARQL endpoint lets researchers ask structured questions across collections, while ontology-based tools help relate concepts that may be worded differently in source systems. For Alaska, those capabilities can separate aircraft classes, rates and dates without relying on a single hand-built summary.

A sound workflow starts with the original dataset and preserves vendor names, invoice references, source dates and currencies. Researchers can calculate weighted hourly costs, medians by aircraft class and changes over time, then record every exclusion or transformation. Coverage checks are essential. A missing payment may reflect an absent extract rather than no spending, and different records may encode rates, totals or adjustments in incompatible ways.


Readers can begin with the Alaska aircraft billing material in the PublicSpending.net catalogue, download the bulk files and test a narrow question such as the distribution of billed hours by aircraft class. Using the dataset’s table or graph views can validate a first result before moving to more complex queries. Keeping source identifiers with every calculation makes the work traceable and suitable for publication.

Agencies and watchdogs can use the same evidence to review rate changes, contract concentration and standby patterns, then place those findings beside incident and budget records. Publish the query or method with the result, link each claim to its source rows, and update the analysis when a new extract arrives. That turns public aviation invoices into a durable audit trail that citizens, journalists and researchers can test for themselves.