Skip to content
worldfires
AU · Australia · →

Etheridge fire, 30 September 2019 Croydon, Etheridge

Out · last detection 6 Oct 2019, 03:54 UTC

The fire started on 30 September 2019 in Etheridge, Australia, and satellites saw it burning for 6 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 10,267 hectares from heat detections, spread across 2 municipalities.

It is the 739th largest in Queensland since 2016 (of 1737 with a page). Number 366 in Australia in 2019, of 802.

The power measured by the satellite is low (27.6 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.

Compare with…
Burnt area
10,267ha
GWIS perimeter (Copernicus)
Duration
6days
30 Sept 2019 – 5 Oct 2019
Municipalities hit
2
local government areas
Started on
30 Sept
2019
Heat detections
426
in a single hotspot: 28 MW
Danger at start
54
Extreme · FWI index
Average daily power
373MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 30 Sept5 Oct
6 Oct 2019

How it evolved, day by day

30 Sept 2019 · 913 MW · 106 1 Oct 2019 · 902 MW · 127 2 Oct 2019 · 485 MW · 130 3 Oct 2019 · 256 MW · 41 4 Oct 2019 · 48 MW · 14 5 Oct 2019 · 4 MW · 3 6 Oct 2019 · 2 MW · 1
30 Sept 1 Oct 2 Oct 3 Oct 4 Oct 5 Oct 6 Oct

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

The weather it burned in

40°high
48km/h · peak gust
8%lowest humidity

It had gone more than two months without rain (1 mm or more) when it started.

This area had burned before

40% of the perimeter overlaps earlier fires recorded since 2016: 272 ha in 2016, 3,967 ha in 2017.

How big is it?

10 km
It burned the equivalent of 6.5% of the area of London (103 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. 9,224 ha reached on 30 Sept
    0.3 %
  2. Etheridge where it started
    1,088 ha reached on 29 Sept
    0.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 2020
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2020, 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.

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)
29 Sept 37.5 °C 11 % 33 km/h 0.0 mm Extreme 54
30 Sept 38.8 °C 11 % 28 km/h 0.0 mm Extreme 53
1 Oct 38.9 °C 11 % 34 km/h 0.0 mm Extreme 55
2 Oct 36.0 °C 14 % 39 km/h 0.0 mm Extreme 59
3 Oct 34.5 °C 15 % 45 km/h 0.0 mm Extreme 63
4 Oct 34.6 °C 12 % 45 km/h 0.0 mm Extreme 62
5 Oct 34.8 °C 8 % 48 km/h 0.0 mm Extreme 68
6 Oct after 35.2 °C 12 % 45 km/h 0.0 mm Extreme 67
7 Oct after 37.8 °C 12 % 38 km/h 0.0 mm Extreme 60
8 Oct after 39.2 °C 9 % 34 km/h 0.0 mm Extreme 55
9 Oct after 39.5 °C 8 % 36 km/h 0.0 mm Extreme 66
10 Oct after 37.7 °C 4 % 39 km/h 0.0 mm Very extreme 72
11 Oct after 36.3 °C 2 % 36 km/h 0.0 mm Extreme 66
12 Oct after 37.3 °C 3 % 33 km/h 0.0 mm Extreme 66
13 Oct after 39.3 °C 4 % 45 km/h 0.0 mm Very extreme 73
14 Oct after 38.6 °C 12 % 37 km/h 0.0 mm Extreme 65
15 Oct after 39.4 °C 12 % 35 km/h 0.0 mm Extreme 63
16 Oct after 39.8 °C 13 % 31 km/h 0.0 mm Extreme 60
17 Oct after 38.9 °C 19 % 33 km/h 0.0 mm Extreme 51
18 Oct after 41.4 °C 13 % 35 km/h 0.0 mm Extreme 64
19 Oct after 40.6 °C 4 % 55 km/h 0.0 mm Very extreme 87

Before and after, from space

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

Before · 23 Sept 2019
After · 12 Oct 2019

If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.

Detections table · 426Every 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 Etheridge fire last?
GWIS (Copernicus) dates it between 30 September 2019 and 5 October 2019: 6 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 10,267 hectares (102.7 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Croydon (9,224 ha, 0.3 %); Etheridge (1,088 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 39.5 °C, humidity dropped to 8 % and gusts hit 48 km/h. The fire danger index (FWI) reached 68, 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.

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. 426 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 2020, 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.