Burned area
satellite only5,417ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 19 Feb 2019 – 22 Feb 2019
+− cross-check
No official record is matched to this page to compare it with.
AU · Australia · –
Donnybrook-Balingup fire, February 2019 Donnybrook-Balingup, Nannup
Out · last detection 22 Feb 2019, 17:27 UTC
The fire started on 19 February 2019 in Donnybrook-Balingup, Australia, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 5,417 hectares from heat detections, spread across 2 municipalities.
It is the 396th largest in Western Australia since 2016 (of 427 with a page). Number 276 in Australia in 2019, of 288.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-24matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only4days
19 Feb 2019 to 22 Feb 2019: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 22 Feb 2019, 17:27 UTC
+− cross-check
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.
Start
satellite only19 Feb 2019
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 19 Feb 2019
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only363
VIIRS detections at 375 m. Most intense hotspot: 179 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 19 Feb 2019 – 22 Feb 2019
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only2,259MW
Total radiative power on 19 February 2019; hotspots that day: 154.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 19 Feb 2019
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model37.8FWI · high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 26.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 19 Feb 2019, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model32.1°C · 32% RH
High of 32.1 °C and minimum humidity of 32% on 20 February 2019; gusts of 48 km/h on 19 February 2019.
- Source
- weather model at the fire’s grid cell
- Date
- 19 Feb 2019 – 22 Feb 2019
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
Living inside
model≈ 30people
Estimated residents inside the perimeter and 2.4 ha of built-up area (100 m grid, epoch 2020).
- Source
- GHSL R2023A · JRC
- Date
- calculated on 24 October 2026
+− cross-check
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.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
· reconstructed GHSLPopulation and built-up area computed
What was saved on 24 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 5,417 ha
- Dates
- 19 Feb 2019 – 22 Feb 2019
- Name
- Donnybrook-Balingup
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/donnybrook-balingup-2019-02?v=2026-10-24A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire donnybrook-balingup-2019-02.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2019-02-19 | 154 | 2,259 | 30.6 | 14.3 | 30 | 21.6 | 47.9 | 0 | 37.8 | alto | 1 |
| 2019-02-20 | 186 | 1,721 | 32.1 | 15.5 | 32 | 20.5 | 42.1 | 0 | 33.4 | alto | 1 |
| 2019-02-21 | 21 | 324 | 28.2 | 16 | 48 | 11.9 | 30.2 | 0 | 25.8 | alto | 1 |
| 2019-02-22 | 2 | 9 | 26.3 | 15 | 38 | 14.7 | 35.6 | 0 | 29.5 | alto | 1 |
| 2019-02-23 | 0 | 0 | 26 | 14.6 | 48 | 17.3 | 42.8 | 0 | 33.6 | alto | 0 |
| 2019-02-24 | 0 | 0 | 27.9 | 16.1 | 34 | 23.6 | 49.7 | 0 | 26 | alto | 0 |
| 2019-02-25 | 0 | 0 | 31.9 | 15 | 27 | 21.4 | 46.4 | 0 | 41.8 | muy_alto | 0 |
| 2019-02-26 | 0 | 0 | 34.4 | 17.3 | 26 | 18.1 | 37.8 | 0 | 30.4 | alto | 0 |
| 2019-02-27 | 0 | 0 | 32.5 | 19.2 | 33 | 15.5 | 33.1 | 0 | 35.2 | alto | 0 |
| 2019-02-28 | 0 | 0 | 29 | 17.2 | 43 | 17.9 | 40.3 | 0 | 36 | alto | 0 |
| 2019-03-01 | 0 | 0 | 22.5 | 11 | 33 | 18.7 | 41.4 | 0 | 39.8 | muy_alto | 0 |
| 2019-03-02 | 0 | 0 | 24.8 | 9.1 | 38 | 15 | 35.6 | 0 | 26.8 | alto | 0 |
| 2019-03-03 | 0 | 0 | 30 | 13 | 27 | 18.1 | 38.9 | 0 | 34.8 | alto | 0 |
| 2019-03-04 | 0 | 0 | 31.1 | 15.9 | 34 | 25.8 | 52.9 | 0 | 43.4 | muy_alto | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: GWIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 5,417ha
- GWIS perimeter (Copernicus)
- Duration
- 4days
- 19 Feb 2019 – 22 Feb 2019
- Municipalities hit
- 2
- local government areas
- Started on
- 19 Feb
- 2019
- Heat detections
- 363
- in a single hotspot: 179 MW
- Danger at start
- 38
- High · FWI index
- Average daily power
- 1.1GW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
19 Feb22 Feb
22 Feb 2019
How it evolved, day by day
19 Feb
20 Feb
21 Feb
22 Feb
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
32°high
48km/h · peak gust
30%lowest humidity
It had gone 26 days without rain (1 mm or more) when it started.
This area had burned before
37% of the perimeter overlaps earlier fires recorded since 2016: 1,387 ha in 2016, 154 ha in 2017, 712 ha in 2018. Part of it burned more than once, so the yearly figures add up to more than the 1,993 ha that had burned before.
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
-
Donnybrook-Balingup where it started4,263 ha reached on 19 Feb2.7 %
-
1,172 ha reached on 19 Feb0.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 2020Built-up area2.4 ha
Residents≈ 30
Inside the perimeter there were about 2.4 hectares of built-up land and about 30 residents (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) |
|---|---|---|---|---|---|
| 19 Feb | 30.6 °C | 30 % | 48 km/h | 0.0 mm | High 38 |
| 20 Feb | 32.1 °C | 32 % | 42 km/h | 0.0 mm | High 33 |
| 21 Feb | 28.2 °C | 48 % | 30 km/h | 0.0 mm | High 26 |
| 22 Feb | 26.3 °C | 38 % | 36 km/h | 0.0 mm | High 30 |
| 23 Feb after | 26.0 °C | 48 % | 43 km/h | 0.0 mm | High 34 |
| 24 Feb after | 27.9 °C | 34 % | 50 km/h | 0.0 mm | High 26 |
| 25 Feb after | 31.9 °C | 27 % | 46 km/h | 0.0 mm | Very high 42 |
| 26 Feb after | 34.4 °C | 26 % | 38 km/h | 0.0 mm | High 30 |
| 27 Feb after | 32.5 °C | 33 % | 33 km/h | 0.0 mm | High 35 |
| 28 Feb after | 29.0 °C | 43 % | 40 km/h | 0.0 mm | High 36 |
| 1 Mar after | 22.5 °C | 33 % | 41 km/h | 0.0 mm | Very high 40 |
| 2 Mar after | 24.8 °C | 38 % | 36 km/h | 0.0 mm | High 27 |
| 3 Mar after | 30.0 °C | 27 % | 39 km/h | 0.0 mm | High 35 |
| 4 Mar after | 31.1 °C | 34 % | 53 km/h | 0.0 mm | Very high 43 |
Its twins: fires that started in the same weather
It started with an FWI of 37.8, a minimum humidity of 30% and 26 days without rain. Fires in the area that started in weather like this since 2016: 7.
FWI at the start
37.8
Minimum humidity
30 %
Days without rain
26
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Donnybrook-Balingup fire, February 2019
5,417 ha
4 days
FWI 37.8
Min. humidity 30 %
Boddington fire, January 2016
49,556 ha
12 days
FWI 37.5
Min. humidity 34 %
105 km away, in 2016
First rain (1 mm or more) after it ended: 2.3 mm on 17 Jan.
Murray fire, May 2020
7,743 ha
3 days
FWI 28.9
Min. humidity 29 %
150 km away, in 2020
First rain (1 mm or more) after it ended: 11.2 mm on 4 May.
Donnybrook-Balingup fire, January 2023
7,126 ha
6 days
FWI 50.2
Min. humidity 26 %
35 km away, in 2023
First rain (1 mm or more) after it ended: none in the following ten days.
Wandering fire, May 2024
5,181 ha
2 days
FWI 33.0
Min. humidity 21 %
163 km away, in 2024
First rain (1 mm or more) after it ended: 1.6 mm on 28 May.
York fire, May 2017
5,298 ha
7 days
FWI 31.7
Min. humidity 36 %
205 km away, in 2017
First rain (1 mm or more) after it ended: 3.2 mm on 15 May.
What happened to them
Fires in the area that started in similar weather: 7. With fewer than 15 we give no figures: they would be more noise than signal.
This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it
How it ended
—first rain
—no rain in ten days
48km/h · max. gust
It was considered over on 22 Feb, and not even 1 mm fell in the following ten days: it went out without rain.
Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
How a twin is chosen
- Same area: fires that have already ended, less than 250 km from this one, since 2016.
- Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
- Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
- Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
- They are sorted by similarity, and the outlines of the first five are drawn.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 12 Feb 2019
After · 1 Mar 2019
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
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 · 363Every 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 time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Donnybrook-Balingup fire last?
- GWIS (Copernicus) dates it between 19 February 2019 and 22 February 2019: 4 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 5,417 hectares (54.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Donnybrook-Balingup (4,263 ha, 2.7 %); Nannup (1,172 ha, 0.4 %).
- What was the weather like?
- During the fire the temperature reached 32.1 °C, humidity dropped to 30 % and gusts hit 48 km/h. The fire danger index (FWI) reached 38, 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.
RSS Changes to this page With cross-checks and a citable version
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. 363 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.
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.