Aurukun fire, 28 September 2024 Aurukun, Cook
The fire started on 28 September 2024 in Aurukun, Australia, and satellites saw it burning for 15 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 7,334 hectares from heat detections, spread across 2 municipalities.
It is the 1103th largest in Queensland since 2016 (of 1737 with a page). Number 388 in Australia in 2024, of 636.
Compare with…
- Burnt area
- 7,334ha
- GWIS perimeter (Copernicus)
- Duration
- 15days
- 28 Sept 2024 – 12 Oct 2024
- Municipalities hit
- 2
- local government areas
- Started on
- 28 Sept
- 2024
- Heat detections
- 242
- in a single hotspot: 99 MW
- Danger at start
- 46
- Very high · FWI index
- Average daily power
- 104MW
- detected power per day, on average
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone more than two months without rain (1 mm or more) when it started.
This area had burned before
93% of the perimeter overlaps earlier fires recorded since 2016: 3,687 ha in 2016, 1,394 ha in 2017, 3,457 ha in 2018, 5,225 ha in 2019, 4,257 ha in 2021, 1,329 ha in 2022, 1,569 ha in 2023. Part of it burned more than once, so the yearly figures add up to more than the 6,789 ha that had burned before.
- 3,107 ha Aurukun fire, September 2021 18,717 ha in total; the hectares shown are those it shares with this fire
- 1,857 ha Aurukun fire, July 2019 5,047 ha in total; the hectares shown are those it shares with this fire
- 76 ha Aurukun fire, October 2016 6,992 ha in total; the hectares shown are those it shares with this fire
- 54 ha Aurukun fire, August 2017 8,636 ha in total; the hectares shown are those it shares with this fire
- 8 ha Aurukun fire, October 2023 17,980 ha in total; the hectares shown are those it shares with this fire
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Aurukun where it started7,364 ha reached on 28 Sept1.0 %
-
1 ha0.0 %
Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance runs from the point marking the centre of each area to the nearest fire: staying a kilometre away does not mean it reached the houses.
People and buildings inside the perimeter
GHSL 2025Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2025, satellite-based estimate).
This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned. The GHSL 2025 epoch is a projection made from 2020 and earlier data.
Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu
The weather day by day
ECMWF ERA5 reanalysis at the fire location, the standard reference for past weather, and the Canadian Fire Weather Index (the same system Copernicus uses), computed by WorldFires from that data. Days after the fire run until the first rain.
Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 23 Sept | 37.2 °C | 21 % | 43 km/h | 0.0 mm | Very high 46 |
| 24 Sept | 35.3 °C | 31 % | 42 km/h | 0.0 mm | Very high 47 |
| 25 Sept | 35.3 °C | 35 % | 41 km/h | 0.0 mm | Very high 42 |
| 26 Sept | 35.9 °C | 37 % | 38 km/h | 0.0 mm | High 38 |
| 27 Sept | 36.6 °C | 37 % | 29 km/h | 0.0 mm | High 34 |
| 28 Sept | 37.1 °C | 31 % | 29 km/h | 0.0 mm | High 36 |
| 29 Sept | 36.4 °C | 35 % | 30 km/h | 0.0 mm | High 38 |
| 30 Sept | 36.6 °C | 33 % | 42 km/h | 0.0 mm | Very high 40 |
| 1 Oct | 36.6 °C | 25 % | 49 km/h | 0.0 mm | Very high 48 |
| 2 Oct | 35.7 °C | 30 % | 49 km/h | 0.0 mm | Very high 49 |
| 3 Oct | 35.0 °C | 30 % | 49 km/h | 0.0 mm | Very high 50 |
| 4 Oct | 34.8 °C | 32 % | 49 km/h | 0.0 mm | Very high 48 |
| 5 Oct | 35.2 °C | 29 % | 44 km/h | 0.0 mm | Very high 45 |
| 6 Oct | 36.1 °C | 30 % | 48 km/h | 0.0 mm | Extreme 51 |
| 7 Oct | 36.3 °C | 39 % | 43 km/h | 0.2 mm | Very high 42 |
| 8 Oct | 36.2 °C | 43 % | 53 km/h | 0.1 mm | Very high 44 |
| 9 Oct | 37.2 °C | 32 % | 42 km/h | 0.0 mm | Very high 41 |
| 10 Oct | 37.9 °C | 31 % | 38 km/h | 0.0 mm | Very high 40 |
| 11 Oct | 35.7 °C | 33 % | 46 km/h | 0.0 mm | Very high 44 |
| 12 Oct | 36.2 °C | 28 % | 48 km/h | 0.0 mm | Very high 47 |
| 13 Oct after | 35.9 °C | 31 % | 44 km/h | 0.0 mm | Very high 42 |
| 14 Oct after | 36.2 °C | 32 % | 37 km/h | 0.0 mm | Very high 39 |
| 15 Oct after | 35.9 °C | 33 % | 34 km/h | 0.0 mm | High 38 |
| 16 Oct after | 36.5 °C | 33 % | 42 km/h | 0.0 mm | Very high 41 |
| 17 Oct after | 35.6 °C | 41 % | 42 km/h | 0.2 mm | Very high 39 |
| 18 Oct after | 36.1 °C | 41 % | 37 km/h | 0.6 mm | High 32 |
| 19 Oct after | 36.4 °C | 39 % | 34 km/h | 0.0 mm | High 32 |
| 20 Oct after | 36.8 °C | 33 % | 28 km/h | 0.0 mm | High 33 |
| 21 Oct after | 36.8 °C | 31 % | 30 km/h | 0.0 mm | High 36 |
| 22 Oct after | 37.7 °C | 30 % | 40 km/h | 0.1 mm | High 38 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.
The smoke
CAMS · CopernicusOn 14 October 2024 the air beside the fire reached 24 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).
Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.
Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)
Detections table · 242Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 49,808 haCook17 July 2026 · 31 days · 22 km away
- 53,850 haAurukun2 July 2026 · 20 days · 29 km away
- 28,131 haAurukun4 August 2023 · 48 days · 31 km away
- 27,363 haCook11 October 2016 · 34 days · 31 km away
- 23,763 haAurukun31 October 2016 · 7 days · 32 km away
- 25,955 haCook24 August 2018 · 37 days · 36 km away
Frequently asked questions
- How long did the Aurukun fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 28 September 2024 to 12 October 2024 (15 days). The perimeter dates it from 30 September 2024 to 12 October 2024.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 7,334 hectares (73.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Aurukun (7,364 ha, 1.0 %); Cook (1 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 37.9 °C, humidity dropped to 21 % and gusts hit 53 km/h. The fire danger index (FWI) reached 51, class Extreme.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Australia (geoBoundaries). It is not an official report.
Where to verify it
A satellite detection is not an official report. Final figures and the fire’s status are published by each country’s emergency service.
Emergency number: 000 · Emergency number and official warnings ›
Satellite cross-check
History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
No changes since 24 October 2026.
Does something look wrong on this page?
This page is built from satellite data and official records, and it sometimes gets things wrong: the wrong dates, the wrong town, two fires merged into one, or something that was not a wildfire at all. If you know this fire first-hand (you live nearby, saw it, fought it or reported on it), tell us what really happened and we will check it.
Report an error
How we know this
- Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 30 September 2024 to 12 October 2024. 242 Suomi-NPP VIIRS detections on those dates.
- We have not matched this page with any official record.
- Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.
- Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2025, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.
Where this data comes from
The perimeter comes from the Copernicus Global Wildfire Information System (GWIS), which rebuilds it from MODIS and VIIRS heat detections and publishes it under CC BY 4.0. It is not measured on imagery as in Europe, so it is an estimate. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. Municipal boundaries come from geoBoundaries ADM2 (Creative Commons Attribution 4.0 International (CC BY 4.0)). The area per municipality is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ from each country’s official figure.