Burned area
satellite only7,390ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 1 May 2026 – 7 May 2026
+− cross-check
No official record is matched to this page to compare it with.
AU · Australia · –
Broome fire, 1 May 2026 Derby-West Kimberley, Broome
Out · last detection 8 May 2026, 17:00 UTC
The fire started on 1 May 2026 in Broome, Australia, and satellites saw it burning for 7 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 7,390 hectares from heat detections, spread across 2 municipalities.
This entry is probably a savanna fire in Australia’s tropical north, not a bushfire like those in the south of the country. Millions of hectares of northern savanna and grassland burn every year: much of it in burns lit on purpose early in the dry season (traditional fire management, parks and cattle stations), the rest in grass fires that return to the same ground every few years. This is our assumption, based on the location; it is not confirmed. That is why it is left out of the wildfire rankings.
GWIS near-real-time perimeter, from the layer that changed in October 2025: this fire is not compared with fires from earlier years, because since then the GWIS layer gives more and larger perimeters.
Use this data
Compare with…
Use this data
Fire page data · version 2026-11-15matches 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 only7days
1 May 2026 to 7 May 2026: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 8 May 2026, 17:00 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 only1 May 2026
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 1 May 2026
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only166
VIIRS detections at 375 m. Most intense hotspot: 268 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP + NOAA-20)
- Date
- 1 May 2026 – 7 May 2026
+− 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 only495MW
Total radiative power on 3 May 2026; hotspots that day: 33.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 3 May 2026
+− 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
model36.0FWI · high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 36.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 1 May 2026, 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
model35.5°C · 22% RH
High of 35.5 °C and minimum humidity of 22% on 3 May 2026; gusts of 53 km/h on 7 May 2026.
- Source
- weather model at the fire’s grid cell
- Date
- 1 May 2026 – 7 May 2026
- 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.
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
-
logName: Derby-West Kimberley → Broome.
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
What was saved on 15 November 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
- 7,390 ha
- Dates
- 1 May 2026 – 7 May 2026
- Name
- Broome
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/broome-2026-05-8?v=2026-11-15A 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 broome-2026-05-8.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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-05-01 | 6 | 139 | 33.9 | 19.9 | 33 | 13.2 | 20.5 | 0 | 36 | alto | 1 |
| 2026-05-02 | 3 | 15 | 35.1 | 21.3 | 28 | 14.8 | 22 | 0 | 37 | alto | 1 |
| 2026-05-03 | 33 | 495 | 35.5 | 23.1 | 22 | 27 | 43.2 | 0 | 62.5 | extremo | 1 |
| 2026-05-04 | 84 | 382 | 35.2 | 22.3 | 15 | 29.3 | 46.8 | 0 | 90 | muy_extremo | 1 |
| 2026-05-05 | 27 | 208 | 34.5 | 20.1 | 19 | 25.8 | 42.5 | 0 | 66.6 | extremo | 1 |
| 2026-05-06 | 4 | 39 | 33.3 | 21.7 | 35 | 19.3 | 36 | 7.4 | 44.3 | muy_alto | 1 |
| 2026-05-07 | 5 | 19 | 30 | 21 | 30 | 32.2 | 52.6 | 0.7 | 32.1 | alto | 1 |
| 2026-05-08 | 4 | 16 | 28.6 | 17.2 | 23 | 33.5 | 53.3 | 0 | 64.7 | extremo | 0 |
| 2026-05-09 | 0 | 0 | 30.4 | 15.8 | 24 | 28.4 | 48.2 | 0 | 52.2 | extremo | 0 |
| 2026-05-10 | 0 | 0 | 31.9 | 17.4 | 24 | 24.7 | 43.2 | 0 | 48.9 | muy_alto | 0 |
| 2026-05-11 | 0 | 0 | 34 | 19 | 23 | 21.8 | 38.2 | 0 | 48.2 | muy_alto | 0 |
| 2026-05-12 | 0 | 0 | 34.2 | 21.1 | 31 | 27.3 | 46.8 | 0 | 56.6 | extremo | 0 |
| 2026-05-13 | 0 | 0 | 34.9 | 22 | 24 | 23.7 | 43.6 | 0 | 54.5 | extremo | 0 |
| 2026-05-14 | 0 | 0 | 34.3 | 22 | 30 | 23.6 | 40.7 | 0 | 48.3 | muy_alto | 0 |
| 2026-05-15 | 0 | 0 | 34.5 | 21.1 | 28 | 19.4 | 29.9 | 0 | 36.5 | alto | 0 |
| 2026-05-16 | 0 | 0 | 33.8 | 19.6 | 36 | 19.1 | 33.5 | 0 | 46.4 | muy_alto | 0 |
| 2026-05-17 | 0 | 0 | 31.3 | 21.8 | 39 | 32.6 | 49.7 | 0 | 36.8 | 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). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 7,390ha
- GWIS perimeter (Copernicus)
- Duration
- 7days
- 1 May 2026 – 7 May 2026
- Municipalities hit
- 2
- local government areas
- Started on
- 1 May
- 2026
- Heat detections
- 166
- in a single hotspot: 268 MW
- Danger at start
- 36
- High · FWI index
- Average daily power
- 164MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
1 May7 May
8 May 2026
How it evolved, day by day
1 May
3 May
5 May
7 May
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
36°high
53km/h · peak gust
15%lowest humidity
It had gone 36 days without rain (1 mm or more) when it started.
This area had burned before
94% of the perimeter overlaps earlier fires recorded since 2016: 20 ha in 2016, 172 ha in 2017, 115 ha in 2018, 2,418 ha in 2019, 1,884 ha in 2020, 4,927 ha in 2021, 13 ha in 2022, 3,377 ha in 2023, 733 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 6,971 ha that had burned before.
- 3,380 ha Derby-West Kimberley fire, November 2021 5,680 ha in total; the hectares shown are those it shares with this fire
- 733 ha Derby-West Kimberley fire, September 2025 174,214 ha in total; the hectares shown are those it shares with this fire
- 472 ha Derby-West Kimberley fire, August 2020 29,574 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
-
6,912 ha0.1 %
-
Broome where it started528 ha0.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.
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) |
|---|---|---|---|---|---|
| 1 May | 33.9 °C | 33 % | 20 km/h | 0.0 mm | High 36 |
| 2 May | 35.1 °C | 28 % | 22 km/h | 0.0 mm | High 37 |
| 3 May | 35.5 °C | 22 % | 43 km/h | 0.0 mm | Extreme 62 |
| 4 May | 35.2 °C | 15 % | 47 km/h | 0.0 mm | Very extreme 90 |
| 5 May | 34.5 °C | 19 % | 42 km/h | 0.0 mm | Extreme 67 |
| 6 May | 33.3 °C | 35 % | 36 km/h | 7.4 mm | Very high 44 |
| 7 May | 30.0 °C | 30 % | 53 km/h | 0.7 mm | High 32 |
| 8 May after | 28.6 °C | 23 % | 53 km/h | 0.0 mm | Extreme 65 |
| 9 May after | 30.4 °C | 24 % | 48 km/h | 0.0 mm | Extreme 52 |
| 10 May after | 31.9 °C | 24 % | 43 km/h | 0.0 mm | Very high 49 |
| 11 May after | 34.0 °C | 23 % | 38 km/h | 0.0 mm | Very high 48 |
| 12 May after | 34.2 °C | 31 % | 47 km/h | 0.0 mm | Extreme 57 |
| 13 May after | 34.9 °C | 24 % | 44 km/h | 0.0 mm | Extreme 54 |
| 14 May after | 34.3 °C | 30 % | 41 km/h | 0.0 mm | Very high 48 |
| 15 May after | 34.5 °C | 28 % | 30 km/h | 0.0 mm | High 36 |
| 16 May after | 33.8 °C | 36 % | 34 km/h | 0.0 mm | Very high 46 |
| 17 May after | 31.3 °C | 39 % | 50 km/h | 0.0 mm | High 37 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 24 Apr 2026
After · 14 May 2026
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.
The smoke
CAMS · CopernicusOn 1 May 2026 the air beside the fire reached 30 µg/m³ of PM2.5. That day averaged 16: 1.1 times the WHO daily guideline (15).
PM2.5 peak30 µg/m³
Days over the guideline1 day
PM1032 µg/m³
Optical depth0.34
WHO 15
29 Apr2 May5 May8 May
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 · 166Every 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 Broome fire last?
- GWIS (Copernicus) dates it between 1 May 2026 and 7 May 2026: 7 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 7,390 hectares (73.9 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Derby-West Kimberley (6,912 ha, 0.1 %); Broome (528 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 35.5 °C, humidity dropped to 15 % and gusts hit 53 km/h. The fire danger index (FWI) reached 90, class Very 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 · 1 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Name: Derby-West Kimberley → Broome.
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. 166 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.
- Probably a vegetation burn: not counted in the totals.
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.