Cook fire, 18 July 2026 Cook, Aurukun, Napranum
The fire started on 18 July 2026 in Cook, Australia, and satellites saw it burning for 17 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 12,724 hectares from heat detections, spread across 3 municipalities.
It is the 570th largest in Queensland since 2016 (of 1737 with a page). Number 255 in Australia in 2026, of 876.
Compare with…
- Burnt area
- 12,724ha
- GWIS perimeter (Copernicus)
- Duration
- 17days
- 18 Jul 2026 – 3 Aug 2026
- Municipalities hit
- 3
- local government areas
- Started on
- 18 Jul
- 2026
- Heat detections
- 361
- in a single hotspot: 44 MW
- Danger at start
- 21
- Moderate · FWI index
- Average daily power
- 163MW
- 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 8 days without rain (1 mm or more) when it started.
This area had burned before
99% of the perimeter overlaps earlier fires recorded since 2016: 3,811 ha in 2016, 1,636 ha in 2017, 4,849 ha in 2018, 7,283 ha in 2019, 4,772 ha in 2020, 3,370 ha in 2021, 6,815 ha in 2022, 3,474 ha in 2023, 2,128 ha in 2024, 6,498 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 12,565 ha that had burned before.
- 5,725 ha Aurukun fire, August 2019 14,604 ha in total; the hectares shown are those it shares with this fire
- 2,452 ha Aurukun fire, August 2021 8,592 ha in total; the hectares shown are those it shares with this fire
- 285 ha Aurukun fire, August 2025 8,076 ha in total; the hectares shown are those it shares with this fire
- 1 ha Napranum fire, September 2023 13,387 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
-
Cook where it started9,184 ha reached on 17 Jul0.1 %
-
2,984 ha reached on 17 Jul0.4 %
-
592 ha reached on 23 Jul0.3 %
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) |
|---|---|---|---|---|---|
| 17 Jul | 30.9 °C | 25 % | 19 km/h | 0.0 mm | Moderate 21 |
| 18 Jul | 31.4 °C | 28 % | 22 km/h | 0.0 mm | High 24 |
| 19 Jul | 31.2 °C | 25 % | 20 km/h | 0.0 mm | High 24 |
| 20 Jul | 30.9 °C | 25 % | 19 km/h | 0.0 mm | High 25 |
| 21 Jul | 32.0 °C | 29 % | 18 km/h | 0.0 mm | High 26 |
| 22 Jul | 32.5 °C | 33 % | 23 km/h | 0.0 mm | High 30 |
| 23 Jul | 31.8 °C | 33 % | 16 km/h | 0.0 mm | High 26 |
| 24 Jul | 31.6 °C | 31 % | 18 km/h | 0.0 mm | High 28 |
| 25 Jul | 31.4 °C | 27 % | 20 km/h | 0.0 mm | High 30 |
| 26 Jul | 33.2 °C | 24 % | 16 km/h | 0.0 mm | High 29 |
| 27 Jul | 33.8 °C | 27 % | 18 km/h | 0.0 mm | High 32 |
| 28 Jul | 31.1 °C | 41 % | 27 km/h | 0.1 mm | High 25 |
| 29 Jul | 28.4 °C | 54 % | 40 km/h | 0.0 mm | High 23 |
| 30 Jul | 30.8 °C | 42 % | 40 km/h | 0.0 mm | High 24 |
| 31 Jul | 31.2 °C | 30 % | 42 km/h | 0.0 mm | High 31 |
| 1 Aug | 30.2 °C | 42 % | 42 km/h | 0.0 mm | High 31 |
| 2 Aug | 29.2 °C | 51 % | 53 km/h | 0.0 mm | High 30 |
| 3 Aug | 30.2 °C | 39 % | 46 km/h | 0.0 mm | High 28 |
| 4 Aug after | 29.9 °C | 41 % | 44 km/h | 0.0 mm | High 28 |
| 5 Aug after | 29.8 °C | 41 % | 35 km/h | 0.0 mm | High 25 |
| 6 Aug after | 30.0 °C | 39 % | 37 km/h | 0.0 mm | High 27 |
| 7 Aug after | 31.4 °C | 35 % | 34 km/h | 0.0 mm | High 27 |
| 8 Aug after | 32.0 °C | 37 % | 33 km/h | 0.0 mm | High 28 |
| 9 Aug after | 32.2 °C | 38 % | 21 km/h | 0.1 mm | High 24 |
| 10 Aug after | 32.6 °C | 39 % | 19 km/h | 0.0 mm | High 25 |
| 11 Aug after | 33.6 °C | 36 % | 18 km/h | 0.0 mm | High 24 |
| 12 Aug after | 32.5 °C | 39 % | 24 km/h | 0.0 mm | High 27 |
| 13 Aug after | 33.2 °C | 37 % | 46 km/h | 0.0 mm | High 35 |
| 14 Aug after | 32.5 °C | 37 % | 37 km/h | 0.0 mm | High 33 |
| 15 Aug after | 31.1 °C | 38 % | 38 km/h | 0.0 mm | High 34 |
| 16 Aug after | 30.5 °C | 36 % | 41 km/h | 0.0 mm | High 36 |
| 17 Aug after | 30.8 °C | 36 % | 52 km/h | 0.0 mm | Very high 40 |
| 18 Aug after | 32.0 °C | 31 % | 41 km/h | 0.0 mm | High 36 |
| 19 Aug after | 31.1 °C | 35 % | 45 km/h | 0.0 mm | Very high 40 |
| 20 Aug after | 32.2 °C | 33 % | 44 km/h | 0.0 mm | Very 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 22 July 2026 the air beside the fire reached 56 µg/m³ of PM2.5. That day averaged 21: 1.4 times the WHO daily 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 · 361Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Cook fire last?
- GWIS (Copernicus) dates it between 18 July 2026 and 3 August 2026: 17 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 12,724 hectares (127.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 3 municipalities: Cook (9,184 ha, 0.1 %); Aurukun (2,984 ha, 0.4 %); Napranum (592 ha, 0.3 %).
- What was the weather like?
- During the fire the temperature reached 33.8 °C, humidity dropped to 24 % and gusts hit 53 km/h. The fire danger index (FWI) reached 32, class High.
- 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. 361 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.