publicdata.au publicdata.au on GitHub

Road casualties, Queensland

live
Publisher Department of Transport and Main RoadsUpdated about twice a yearLicence CC BY 4.0Latest 2026-04-24As at 30 June 2025Rows 38,893Fields 7

Aggregate counts of people killed or injured in reported Queensland road crashes from 1 January 2001. Each row is one combination of year, police region, casualty severity, age group, gender and road user type, with the number of casualties.

Also called: Queensland road crash casualties, Queensland road injuries and deaths by year, TMR casualty data.

Part of Crash data from Queensland roads, 6 tables the publisher releases together: Road crash locations, Queensland, Driver demographics in road crashes, Queensland, Seatbelt and helmet use in road crash casualties, Queensland, Vehicle types in road crashes, Queensland, Factors in road crashes, Queensland.

Before you use it
What does one row count?
The number of people killed or injured in one combination of year, police region, severity, age group, gender and road user type. Add rows to get a total. A crash with three injured people appears as three casualties, not one.
38,893rows
2001 to 2024years drawn
7fields
9formats
1version
05k10k15k20k25k2001 Fatality: 3242001 Hospitalised: 5,3092001 Medically treated: 7,8932001 Minor injury: 4,8352002 Fatality: 3222002 Hospitalised: 5,6002002 Medically treated: 7,6922002 Minor injury: 4,7862003 Fatality: 3102003 Hospitalised: 5,7992003 Medically treated: 7,3692003 Minor injury: 4,67120032004 Fatality: 3112004 Hospitalised: 6,2282004 Medically treated: 7,3582004 Minor injury: 4,5892005 Fatality: 3302005 Hospitalised: 6,3072005 Medically treated: 7,3012005 Minor injury: 4,3832006 Fatality: 3352006 Hospitalised: 5,8852006 Medically treated: 7,4122006 Minor injury: 4,90720062007 Fatality: 3602007 Hospitalised: 6,0542007 Medically treated: 7,5482007 Minor injury: 6,0892008 Fatality: 3282008 Hospitalised: 6,8382008 Medically treated: 8,0042008 Minor injury: 5,1502009 Fatality: 3312009 Hospitalised: 6,6742009 Medically treated: 7,9622009 Minor injury: 4,07420092010 Fatality: 2492010 Hospitalised: 6,4992010 Medically treated: 7,2932010 Minor injury: 3,8932011 Fatality: 2692011 Hospitalised: 6,3882011 Medically treated: 6,9022011 Minor injury: 3,4372012 Fatality: 2802012 Hospitalised: 6,5292012 Medically treated: 7,2152012 Minor injury: 3,04120122013 Fatality: 2712013 Hospitalised: 6,8982013 Medically treated: 7,3222013 Minor injury: 2,4642014 Fatality: 2232014 Hospitalised: 6,6302014 Medically treated: 7,2212014 Minor injury: 2,6272015 Fatality: 2442015 Hospitalised: 6,2012015 Medically treated: 7,7342015 Minor injury: 2,02920152016 Fatality: 2512016 Hospitalised: 6,3282016 Medically treated: 7,7032016 Minor injury: 2,4072017 Fatality: 2462017 Hospitalised: 6,5182017 Medically treated: 6,9302017 Minor injury: 3,1452018 Fatality: 2442018 Hospitalised: 6,8262018 Medically treated: 6,8402018 Minor injury: 3,35120182019 Fatality: 2222019 Hospitalised: 7,0202019 Medically treated: 6,7132019 Minor injury: 3,2292020 Fatality: 2782020 Hospitalised: 7,0152020 Medically treated: 5,7492020 Minor injury: 3,0292021 Fatality: 2752021 Hospitalised: 7,9092021 Medically treated: 6,2892021 Minor injury: 3,56620212022 Fatality: 2962022 Hospitalised: 7,6732022 Medically treated: 5,8382022 Minor injury: 3,6902023 Fatality: 2732023 Hospitalised: 8,2562023 Medically treated: 5,8502023 Minor injury: 3,7462024 Fatality: 3022024 Hospitalised: 8,6412024 Medically treated: 5,6812024 Minor injury: 4,2532024
FatalityHospitalisedMedically treatedMinor injury
Casualties per year by severity, 2001 to 2024. 2025 is not drawn because the file runs to 30 June 2025. The figure is a sum of the casualties column from version 2026-04-24, worked out in the build. Nothing else is added.

Made for agents

Connect your AI agent

Any agent that connects to publicdata.au/mcp can find this dataset, read its 7 fields, count and filter across all 38,893 rows and diff its versions. Every answer names the version and carries Transport and Main Roads's attribution. No key.

Then ask it: What does Road casualties, Queensland hold, and what changed in the newest version?

claude mcp add --transport http publicdata https://publicdata.au/mcp

One command. No key, no account, no sign-up.

Download it as Excel, CSV, JSON and 6 more formats

Pick a format and a version. Excel is picked first because it opens in the tools most offices have. The URL is yours to keep. A dated version keeps its content.

Format
"Latest" redirects to the newest version and will change when the publisher releases again. A dated version keeps its content.
https://publicdata.au/d/qld-road-casualties/latest/data.xlsx
Download this file

One workbook with a records sheet of 38,893 typed rows, a fields sheet and a publicdata sheet with the provenance. Dates are real Excel dates. Opens in Excel, Numbers, LibreOffice and Sheets.

In your own tools

Use it in Excel, R, Python and more

Excel and Power BI read the CSV from its address and refresh from it. The R and Python packages take any dataset on this site by its slug, so a new dataset needs no new release. The DuckDB file attaches read-only over HTTPS, and a query reads only the blocks it touches.

The dated URL in the code never changes. https://publicdata.au/d/qld-road-casualties/latest/ redirects to the newest version.

https://publicdata.au/d/qld-road-casualties/latest/data.csv

In Excel choose Data, then From Web, and paste this address. Excel keeps it, so Refresh All reads the newest version. A sheet holds about a million rows; past that, load the query to the Data Model.

What is in it

Column names are made snake_case and the publisher's original header is kept beside each one. Blank cells are null. Nothing is added, removed, ranked or summarised.

FieldTypePublisher's headerNote
crash_yearintegerCrash_Year
crash_police_regionstringCrash_Police_RegionQueensland Police Service region, or Unknown.
casualty_severitystringCasualty_SeverityFatality, Hospitalised, Medically treated or Minor injury.
casualty_age_groupstringCasualty_AgeGroupAge band such as 17 to 24.
casualty_genderstringCasualty_GenderFemale, Male or Unknown.
casualty_road_user_typestringCasualty_RoadUserTypeDriver, Passenger, Motorcyclist, Bicyclist, Pedestrian or Other.
casualty_countintegerCasualty_CountNumber of casualties in this group.

Download this table as a data dictionary (Excel), or read it as a Frictionless Table Schema at schema.json. The key is crash_year, crash_police_region, casualty_severity, casualty_age_group, casualty_gender, casualty_road_user_type.

A sample of 10 rows

From the latest version, newest first by year, then in the publisher's order, with every field. A blank cell is shown as null.

crash_yearcrash_police_regioncasualty_severitycasualty_age_groupcasualty_gendercasualty_road_user_typecasualty_count
2025SouthernHospitalised30 to 39FemaleDriver31
2025NorthernHospitalised30 to 39FemaleDriver9
2025BrisbaneMedically treated17 to 24FemaleDriver46
2025North CoastMinor injury0 to 16MaleOther4
2025North CoastMedically treated17 to 24FemaleDriver29
2025Far NorthernHospitalised17 to 24FemaleOther1
2025Far NorthernHospitalised30 to 39MaleDriver13
2025BrisbaneHospitalised30 to 39FemaleDriver36
2025North CoastMedically treated40 to 49FemaleDriver26
2025South EasternMedically treated30 to 39MaleDriver52
The first row as JSON

As it appears in data.json.

GET https://publicdata.au/d/qld-road-casualties/latest/data.json
{
  "crash_year": 2004,
  "crash_police_region": "Brisbane",
  "casualty_severity": "Minor injury",
  "casualty_age_group": "40 to 49",
  "casualty_gender": "Male",
  "casualty_road_user_type": "Driver",
  "casualty_count": 81
}

Query it without downloading

The query API returns only the rows you ask for, as JSON, NDJSON or CSV, from the same typed rows as the files. It needs no key. Build a query here and run it, then copy the URL or the code into your own work.

Try rows or aggregate for this dataset. The query builder needs JavaScript.

How filters work

Each filter is field=operator.value in the query string, and every filter must match. A number or date field compares as a number or date, and a text field compares as text. Values are case-sensitive, except that like and ilike ignore case in the ASCII letters A to Z. Prefix not. to negate a filter, as not.eq.value.

OperatorWhat it matches
eq.valueEqual to the value.
neq.valueNot equal to the value. A blank cell does not match.
gt.valueGreater than the value.
gte.valueGreater than or equal to the value.
lt.valueLess than the value.
lte.valueLess than or equal to the value.
like.*text*Matches a pattern where * stands for any run of characters, ignoring case in the ASCII letters A to Z.
ilike.*text*The same as like. Both ignore case in ASCII letters only, so É and é differ.
in.(a,b,c)Equal to any value in the list. A value cannot contain a comma.
is.nullBlank in the source, or suppressed by the publisher.
ParameterWhat it does
selectFields to return, comma-separated. Every field when absent.
orderfield.asc or field.desc, comma-separated. When absent, rows come in the order of the file they are read from. For the newest versions that is the version's own data.parquet, which keeps the publisher's order unless the dataset sorted it. Any other version is read from the Parquet file the answer names in file, and when that file is sorted the answer names its sort in order, which ties follow too.
limitRows per page, 1 to 10,000. 100 when absent.
offsetRows to skip. The next URL in each answer sets it for you.
groupOn aggregate, fields to group by, comma-separated.
metricOn aggregate, count, sum.field, avg.field, min.field or max.field, comma-separated. count when absent.
formatjson, ndjson or csv. JSON carries the provenance header, and the others carry it in response headers.

Without a version the API answers from the newest version, and that answer changes when the publisher releases again. Put versions/<date>/ before rows or aggregate for an answer from that version alone. Every version with a table can be queried, and /api/v1/datasets/<slug>/versions lists them. A query on a version the database does not hold is read from its Parquet file, and one that would read too much of it is refused with DuckDB SQL that answers it from the file. The 1 newest version is loaded; versions lists them.

The API allows 60 requests in 10 seconds from one address. Above that it answers 429 for 10 seconds with a Retry-After header, a RateLimit-Policy header and a JSON body that gives the limit. Every API answer carries the same RateLimit-Policy. A client should wait the Retry-After seconds, or read the files, which have no limit. openapi.json describes this dataset's query paths for client generators and agents.

https://publicdata.au/mcp is a remote MCP server over Streamable HTTP with the same tools, defined in the same place, so a tool added to the pages is added here too. It needs no key and no account. Its row tools and the query API answer every version through one query path, so a tool's answer and the query URL it cites give the same rows. A query that would read too much of a file is refused with DuckDB SQL that answers it from the file. It also has search and fetch, the two tools ChatGPT's deep research and company knowledge call by name, which run search_datasets and read a dataset's record in the shapes those features expect. The row tools are held to the query API's limit of 60 queries in 10 seconds from one address, and each call is two queries because it also counts the matching rows. Add it to Claude Code with claude mcp add --transport http publicdata https://publicdata.au/mcp, add the URL in Claude as a custom connector, connect the publicdata.au plugin in ChatGPT, or give it to any client that connects to remote MCP servers. Each dataset with a table is also a resource at https://publicdata.au/d/<slug>/fields.json, which lists its fields with their types, the publisher's descriptions, their ranges and the values they hold, so an agent can read a dataset's shape before it writes a query.

Smaller files

The same rows split by a field, one JSON file each. Each file carries the same provenance header.

By crash_year (25 files)

by/crash_year/index.json lists every file with its row count.

What changed

One version for every release the publisher has made since this site started following the dataset. The date is the day the file changed on the portal. The "as at" date is the publisher's own.

  • 2026-04-24as at 30 June 2025
    38,893 rows7 fieldsutf-8-sigbc9de78b77cc

    Files rebuilt on 25 September 2026 so every one carries the operator and a ready-made cite string in its provenance header, and to add the Excel, Arrow, GeoPackage, gzipped CSV, SQL and CSVW files. Rows unchanged.

versions.json · changes.json · history.tar.zst (105 KB, every version's Parquet and manifest)

Questions

How do I download Road casualties as a CSV file?

Open https://publicdata.au/d/qld-road-casualties/latest/data.csv. It redirects to the newest dated version, which is https://publicdata.au/d/qld-road-casualties/v/2026-04-24/data.csv today. The same path serves Excel, JSON, Parquet, SQLite, DuckDB, NDJSON, Arrow. A dated URL never changes, so use it when the file must stay the same.

Can I open Road casualties in Excel?

Yes. https://publicdata.au/d/qld-road-casualties/v/2026-04-24/data.xlsx is a workbook with the 38,893 rows on a records sheet, the field list on a second sheet and the provenance on a third. The CSV also opens in Excel. https://publicdata.au/d/qld-road-casualties/v/2026-04-24/data.csv.gz is the CSV at about a tenth of the size.

What years does Road casualties cover?

The current version covers 2001 to 2025, as at 30 June 2025. Each release from Transport and Main Roads becomes a new dated version here, and earlier versions stay online.

How often is Road casualties updated?

Transport and Main Roads releases it about twice a year. This site checks the portal every week and adds a dated version when the file changes.

Can I use Road casualties commercially?

Yes. CC BY 4.0 allows commercial use, redistribution and derived works as long as the attribution is kept. The attribution string is in this page's side column and inside every file.

Is this the official source for Road casualties?

No. The publisher is Department of Transport and Main Roads, and its page is https://www.data.qld.gov.au/dataset/crash-data-from-queensland-roads. National Digital converted the publisher's file to other formats. It renamed and typed the columns and kept only those the schema lists. National Digital made these changes, and the publisher is not responsible for them. The original sits beside every version as source.csv with its SHA-256, so the two can be compared.

How do I get only the rows for one crash year?

Every version has one JSON file per value of crash_year, 25 files in the current version, listed with row counts at https://publicdata.au/d/qld-road-casualties/v/2026-04-24/by/crash_year/index.json. For example https://publicdata.au/d/qld-road-casualties/v/2026-04-24/by/crash_year/2024.json holds the 1,756 rows where crash_year is 2024.

What this site did to the data. Cells were typed, headers were renamed and the encoding was made UTF-8. Rows were left alone. The publisher's file sits beside every version as source.csv so the change can be checked.

The publisher releases Crash data from Queensland roads as 6 files at once, so all 6 tables here share a version date.

Attribution and citation

The licence requires the publisher's attribution. We ask that you also name publicdata.au and link to the version you used.

Department of Transport and Main Roads, Queensland Government, Crash data from Queensland roads, sourced 24 September 2026, https://www.data.qld.gov.au/dataset/crash-data-from-queensland-roads, licensed under CC BY 4.0. Serialised and versioned by National Digital at publicdata.au, https://publicdata.au/d/qld-road-casualties/v/2026-04-24/

The attribution alone is inside every file. Harvard is the author-date form a report or a brief asks for. Paste the HTML on a web page so the links carry.

Licence record

Department of Transport and Main Roads states the licence, CC BY 4.0, on its own page, which was read and recorded here on 25 September 2026.

Every fetch reads the licence again and stops when it has changed. The fetch that made version 2026-04-24 read it on 24 September 2026.

Also published on
  • Hugging Faceload_dataset("National-Digital/qld-road-casualties")
  • Kagglewith a starter notebook
  • ZenodoDOI 10.5281/zenodo.23076539

Each copy carries the same attribution and links back to this page.

For agents and tools

This page carries a schema.org Dataset record and is listed in /.well-known/ard.json and /catalog.json.

Source

Department of Transport and Main Roads publishes this table on www.data.qld.gov.au. Questions about the content go to the publisher. Questions about the files here go to corrections.

Fetched 24 September 2026. Source SHA-256 bc9de78b77cc67ba…

Improve this dataset

This page is built from register/qld-road-casualties.yaml on GitHub. Anyone can propose a fix to it, such as a clearer description or a field the publisher renamed, as a pull request.

Report a file that differs from the publisher's · How to contribute