Aurukun fire, 6 September 2026 Aurukun
The fire started on 6 September 2026 in Aurukun, Australia, and satellites saw it burning for 40 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 14,355 hectares from heat detections, spread across a single municipality.
It is the 491th largest in Queensland since 2016 (of 1737 with a page). Number 210 in Australia in 2026, of 876.
Compare with…
- Burnt area
- 14,355ha
- GWIS perimeter (Copernicus)
- Duration
- 40days
- 6 Sept 2026 – 15 Oct 2026
- Municipalities hit
- 1
- local government areas
- Started on
- 6 Sept
- 2026
- Heat detections
- 575
- in a single hotspot: 49 MW
- Danger at start
- 39
- Very high · FWI index
- Average daily power
- 69MW
- 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 59 days without rain (1 mm or more) when it started.
This area had burned before
55% of the perimeter overlaps earlier fires recorded since 2016: 3,160 ha in 2016, 4,316 ha in 2017, 6,268 ha in 2018, 5,610 ha in 2019, 1,498 ha in 2020, 4,018 ha in 2021, 4,502 ha in 2022, 5,099 ha in 2023, 3,057 ha in 2024, 3,276 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 7,878 ha that had burned before.
- 5,648 ha Aurukun fire, September 2018 11,248 ha in total; the hectares shown are those it shares with this fire
- 4,361 ha Aurukun fire, October 2023 17,980 ha in total; the hectares shown are those it shares with this fire
- 3,423 ha Aurukun fire, September 2021 18,717 ha in total; the hectares shown are those it shares with this fire
- 701 ha Aurukun fire, September 2025 5,827 ha in total; the hectares shown are those it shares with this fire
- 409 ha Aurukun fire, September 2024 7,334 ha in total; the hectares shown are those it shares with this fire
- 106 ha Aurukun fire, September 2024 14,067 ha in total; the hectares shown are those it shares with this fire
- 22 ha Aurukun fire, August 2023 11,298 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 started14,415 ha reached on 7 Sept1.9 %
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) |
|---|---|---|---|---|---|
| 6 Sept | 33.3 °C | 32 % | 32 km/h | 0.0 mm | Very high 39 |
| 7 Sept | 34.0 °C | 29 % | 34 km/h | 0.0 mm | Very high 40 |
| 8 Sept | 33.8 °C | 36 % | 41 km/h | 0.0 mm | Very high 44 |
| 9 Sept | 33.5 °C | 35 % | 40 km/h | 0.0 mm | Very high 43 |
| 10 Sept | 32.5 °C | 37 % | 49 km/h | 0.0 mm | Very high 46 |
| 11 Sept | 31.3 °C | 35 % | 55 km/h | 0.0 mm | Very high 49 |
| 12 Sept | 31.6 °C | 37 % | 50 km/h | 0.0 mm | Very high 45 |
| 13 Sept | 32.7 °C | 35 % | 40 km/h | 0.0 mm | Very high 40 |
| 14 Sept | 33.4 °C | 30 % | 43 km/h | 0.0 mm | Very high 42 |
| 15 Sept | 33.5 °C | 31 % | 41 km/h | 0.0 mm | Very high 41 |
| 16 Sept | 33.6 °C | 28 % | 36 km/h | 0.0 mm | Very high 40 |
| 17 Sept | 34.3 °C | 18 % | 43 km/h | 0.0 mm | Extreme 53 |
| 18 Sept | 32.5 °C | 32 % | 57 km/h | 0.0 mm | Extreme 54 |
| 19 Sept | 31.8 °C | 33 % | 50 km/h | 0.0 mm | Very high 48 |
| 20 Sept | 32.9 °C | 32 % | 41 km/h | 0.0 mm | Very high 44 |
| 21 Sept | 33.0 °C | 32 % | 36 km/h | 0.0 mm | Very high 42 |
| 22 Sept | 32.8 °C | 33 % | 39 km/h | 0.0 mm | Very high 44 |
| 23 Sept | 32.8 °C | 32 % | 37 km/h | 0.0 mm | Very high 43 |
| 24 Sept | 33.0 °C | 34 % | 39 km/h | 0.0 mm | Very high 42 |
| 25 Sept | 32.8 °C | 33 % | 41 km/h | 0.0 mm | Very high 44 |
| 26 Sept | 33.0 °C | 35 % | 48 km/h | 0.0 mm | Very high 47 |
| 27 Sept | 33.7 °C | 33 % | 40 km/h | 0.0 mm | Very high 43 |
| 28 Sept | 34.0 °C | 33 % | 43 km/h | 0.0 mm | Very high 44 |
| 29 Sept | 32.5 °C | 40 % | 51 km/h | 0.0 mm | Very high 44 |
| 30 Sept | 32.5 °C | 39 % | 45 km/h | 0.0 mm | Very high 41 |
| 1 Oct | 34.2 °C | 31 % | 46 km/h | 0.0 mm | Very high 42 |
| 2 Oct | 33.5 °C | 31 % | 40 km/h | 0.0 mm | Very high 40 |
| 3 Oct | 32.8 °C | 35 % | 42 km/h | 0.0 mm | Very high 40 |
| 4 Oct | 33.8 °C | 33 % | 37 km/h | 0.0 mm | Very high 39 |
| 5 Oct | 34.8 °C | 27 % | 33 km/h | 0.0 mm | Very high 39 |
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 21 September 2026 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 · 575Every 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 haCook18 July 2026 · 23 days · 17 km away
- 27,363 haCook11 October 2016 · 34 days · 26 km away
- 28,131 haAurukun5 August 2023 · 46 days · 32 km away
- 25,955 haCook24 August 2018 · 37 days · 32 km away
- 23,763 haAurukun31 October 2016 · 7 days · 33 km away
- 53,850 haAurukun2 July 2026 · 13 days · 34 km away
Frequently asked questions
- How long did the Aurukun fire last?
- GWIS (Copernicus) dates it between 6 September 2026 and 15 October 2026: 40 days between the first and last heat detection of the perimeter.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 14,355 hectares (143.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Aurukun (14,415 ha, 1.9 %).
- Is the Aurukun fire still active?
- No fire detections since 15 Oct 2026, 16:05 UTC. A lack of detections is not an official extinction.
- What was the weather like?
- During the fire the temperature reached 34.3 °C, humidity dropped to 18 % and gusts hit 57 km/h. The fire danger index (FWI) reached 54, 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 from the perimeter: the VIIRS detections inside it did not change them. 575 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.