Cook fire, 21 September 2026 Cook
The fire started on 21 September 2026 in Cook, Australia, and satellites saw it burning for 36 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 37,441 hectares from heat detections, spread across a single municipality.
It is the 143th largest in Queensland since 2016 (of 1742 with a page). Number 59 in Australia in 2026, of 886.
Compare with…
Suggestions: Cook · 2019Cook · 2022Cook · 2025Cook · 2019
Is it still active?
Satellites detected fire on 26 Oct 2026, 14:59 UTC. Everything suggests it is still burning. Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
- Burnt area
- 37,441ha
- GWIS perimeter (Copernicus)
- Duration
- 36days
- 21 Sept 2026 – 26 Oct 2026
- Municipalities hit
- 1
- local government areas
- Started on
- 21 Sept
- 2026
- Heat detections
- 1,684
- in a single hotspot: 80 MW
- Danger at start
- 34
- High · FWI index
- Average daily power
- 236MW
- 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 11 days without rain (1 mm or more) when it started.
This area had burned before
38% of the perimeter overlaps earlier fires recorded since 2016: 115 ha in 2016, 3,075 ha in 2017, 303 ha in 2018, 12,343 ha in 2019, 4,901 ha in 2022, 978 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 14,110 ha that had burned before.
- 7,821 ha Cook fire, December 2019 18,122 ha in total; the hectares shown are those it shares with this fire
- 3,960 ha Cook fire, December 2022 9,274 ha in total; the hectares shown are those it shares with this fire
- 970 ha Cook fire, December 2025 5,235 ha in total; the hectares shown are those it shares with this fire
- 622 ha Cook fire, December 2019 9,280 ha in total; the hectares shown are those it shares with this fire
- 27 ha Cook fire, August 2019 95,928 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 started37,984 ha reached on 21 Sept0.4 %
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) · forecast models, provisional until the ERA5 reanalysis arrives
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 21 Sept | 29.3 °C | 35 % | 41 km/h | 0.0 mm | High 34 |
| 22 Sept | 29.2 °C | 37 % | 43 km/h | 0.0 mm | High 34 |
| 23 Sept | 29.0 °C | 44 % | 49 km/h | 1.2 mm | High 24 |
| 24 Sept | 29.5 °C | 47 % | 45 km/h | 2.0 mm | Moderate 14 |
| 25 Sept | 29.7 °C | 44 % | 49 km/h | 1.1 mm | High 22 |
| 26 Sept | 30.2 °C | 43 % | 49 km/h | 0.3 mm | High 29 |
| 27 Sept | 30.5 °C | 41 % | 45 km/h | 0.3 mm | High 28 |
| 28 Sept | 30.4 °C | 45 % | 48 km/h | 0.4 mm | High 32 |
| 29 Sept | 30.5 °C | 41 % | 51 km/h | 1.1 mm | High 27 |
| 30 Sept | 30.3 °C | 35 % | 48 km/h | 0.0 mm | High 33 |
| 1 Oct | 29.6 °C | 41 % | 53 km/h | 0.4 mm | High 36 |
| 2 Oct | 29.6 °C | 34 % | 52 km/h | 0.0 mm | High 37 |
| 3 Oct | 30.2 °C | 34 % | 46 km/h | 0.0 mm | High 35 |
| 4 Oct | 30.4 °C | 34 % | 40 km/h | 0.0 mm | High 32 |
| 5 Oct | 32.6 °C | 31 % | 40 km/h | 0.0 mm | High 36 |
| 6 Oct | 32.5 °C | 32 % | 46 km/h | 0.0 mm | High 37 |
| 7 Oct | 33.0 °C | 30 % | 36 km/h | 0.0 mm | High 36 |
| 8 Oct | 32.4 °C | 33 % | 39 km/h | 0.0 mm | Very high 38 |
| 9 Oct | 33.1 °C | 38 % | 35 km/h | 0.0 mm | High 36 |
| 10 Oct | 34.0 °C | 35 % | 37 km/h | 0.7 mm | High 33 |
| 11 Oct | 33.7 °C | 33 % | 41 km/h | 0.0 mm | High 36 |
| 12 Oct | 33.2 °C | 37 % | 44 km/h | 0.0 mm | Very high 39 |
| 13 Oct | 33.9 °C | 34 % | 42 km/h | 0.0 mm | High 37 |
| 14 Oct | 33.8 °C | 33 % | 40 km/h | 0.0 mm | High 37 |
| 15 Oct | 33.6 °C | 35 % | 44 km/h | 0.0 mm | Very high 38 |
| 16 Oct | 32.9 °C | 42 % | 45 km/h | 0.8 mm | High 30 |
| 17 Oct | 33.2 °C | 39 % | 46 km/h | 0.4 mm | High 35 |
| 18 Oct | 32.0 °C | 43 % | 36 km/h | 10.5 mm | Low 6 |
| 19 Oct | 32.9 °C | 43 % | 41 km/h | 2.9 mm | Low 11 |
| 20 Oct | 32.9 °C | 42 % | 48 km/h | 0.0 mm | High 24 |
| 21 Oct | 33.0 °C | 41 % | 45 km/h | 0.1 mm | High 26 |
| 22 Oct | 34.5 °C | 34 % | 46 km/h | 0.4 mm | High 29 |
| 23 Oct | 31.8 °C | 45 % | 35 km/h | 2.7 mm | Low 10 |
| 24 Oct | 33.1 °C | 42 % | 35 km/h | 1.4 mm | Moderate 16 |
| 25 Oct | 34.1 °C | 40 % | 39 km/h | 0.0 mm | High 26 |
| 26 Oct | 35.6 °C | 36 % | 38 km/h | 0.2 mm | High 28 |
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 1 October 2026 the air beside the fire reached 20 µ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 · 1,684Every 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?
- According to the heat detections seen by satellite inside the perimeter, it burned from 21 September 2026 to 26 October 2026 (36 days). The perimeter dates it from 28 September 2026 to 25 October 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 37,441 hectares (374.4 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Cook (37,984 ha, 0.4 %).
- Is the Cook fire still active?
- Yes: satellites detected fire on 26 Oct 2026, 14:59 UTC. Check the emergency service for the official status.
- What was the weather like?
- During the fire the temperature reached 35.6 °C, humidity dropped to 30 % and gusts hit 53 km/h. The fire danger index (FWI) reached 39, class Very 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 · 2 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Area: 36,515 → 37,441 ha.
- Start date: 24 September 2026 → 21 September 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 28 September 2026 to 25 October 2026. 1,684 Suomi-NPP VIIRS detections on those dates.
- We have not matched this page with any official record.
- Weather: ECMWF IFS model, provisional until the ERA5 reanalysis arrives.
- 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.