Skip to content
worldfires
AU · Australia · →

Yilgarn fire, November 2023 Kondinin, Yilgarn

Out · last detection 4 Dec 2023, 05:31 UTC

The fire started on 30 November 2023 in Yilgarn, Australia, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 8,156 hectares from heat detections, spread across 2 municipalities.

It is the 1368th largest in Western Australia since 2016 (of 2718 with a page). Number 718 in Australia in 2023, of 1235.

Compare with…
Burnt area
8,156ha
GWIS perimeter (Copernicus)
Duration
5days
30 Nov 2023 – 4 Dec 2023
Municipalities hit
2
local government areas
Started on
30 Nov
2023
Heat detections
348
in a single hotspot: 182 MW
Danger at start
31
High · FWI index
Average daily power
1.1GW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 30 Nov4 Dec
4 Dec 2023

How it evolved, day by day

30 Nov 2023 · 217 MW · 19 1 Dec 2023 · 1,380 MW · 95 2 Dec 2023 · 975 MW · 107 3 Dec 2023 · 1,345 MW · 76 4 Dec 2023 · 1,628 MW · 49
30 Nov 1 Dec 2 Dec 3 Dec 4 Dec

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

38°high
55km/h · peak gust
13%lowest humidity

It had gone 16 days without rain (1 mm or more) when it started. Rain came after the fire: 1.3 mm on 7 Dec.

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

How big is it?

10 km
It burned the equivalent of 5.2% of the area of London (82 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each town

  1. 4,713 ha reached on 1 Dec
    0.6 %
  2. Yilgarn where it started
    3,501 ha reached on 30 Nov
    0.1 %

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 2025
Built-up area< 0.1 ha
Residents< 20

Inside 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)
30 Nov 29.3 °C 29 % 45 km/h 0.0 mm High 31
1 Dec 33.1 °C 25 % 35 km/h 0.0 mm High 30
2 Dec 38.5 °C 13 % 55 km/h 0.3 mm Very high 49
3 Dec 31.1 °C 27 % 40 km/h 0.0 mm High 35
4 Dec 33.6 °C 18 % 43 km/h 0.0 mm Very high 38
5 Dec after 31.3 °C 26 % 40 km/h 0.0 mm Very high 39
6 Dec after 33.8 °C 24 % 41 km/h 0.0 mm Very high 40
7 Dec after 31.9 °C 32 % 56 km/h 1.3 mm High 31

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

Before · 23 Nov 2023
After · 11 Dec 2023

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 · Copernicus

On 3 December 2023 the air beside the fire reached 13 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).

PM2.5 peak13 µg/m³
Days over the guideline0 days
PM1019 µg/m³
Optical depth0.19
2829301234567
Good Fair Moderate Poor Very poor Extremely poor

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 · 348Every satellite heat detection, one by one, with time, satellite, power and coordinates.
⬇ Download CSV Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
Date and timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in Australia ›

Frequently asked questions

How long did the Yilgarn fire last?
GWIS (Copernicus) dates it between 30 November 2023 and 4 December 2023: 5 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 8,156 hectares (81.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Kondinin (4,713 ha, 0.6 %); Yilgarn (3,501 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 38.5 °C, humidity dropped to 13 % and gusts hit 55 km/h. The fire danger index (FWI) reached 49, 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 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.

No changes since 24 October 2026.

RSS Changes to this page

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
What do you think is wrong?

We will only use your email to reply about this report. Privacy. This is not an emergency service: if there is a fire now, call 000.

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. 348 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.

How we build fire pages: methodology ›

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.