Bindura fire, July 2026 Bindura
The fire started on 22 July 2026 in Bindura, Zimbabwe, and satellites saw it burning for 1 day. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,054 hectares from heat detections, spread across a single municipality.
It is the 291th largest in Mashonaland Central since 2016 (of 334 with a page). Number 322 in Zimbabwe in 2026, of 377.
- Burnt area
- 1,054ha
- GWIS perimeter (Copernicus)
- Duration
- 1day
- 22 Jul 2026 – 22 Jul 2026
- Municipalities hit
- 1
- districts
- Started on
- 22 Jul
- 2026
- Heat detections
- 7
- in a single hotspot: 40 MW
- Danger at start
- 31
- High · FWI index
- Energy released
- 114MW
- sum of detected power
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 more than two months without rain (1 mm or more) when it started.
This area had burned before
42% of the perimeter overlaps earlier fires recorded since 2016: 446 ha in 2022.
What happened to each town
-
Bindura where it started1,059 ha reached on 22 Jul0.5 %
Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre 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) |
|---|---|---|---|---|---|
| 22 Jul | 24.3 °C | 28 % | 33 km/h | 0.0 mm | High 31 |
| 23 Jul after | 23.0 °C | 37 % | 29 km/h | 0.0 mm | High 28 |
| 24 Jul after | 24.1 °C | 28 % | 26 km/h | 0.0 mm | High 28 |
| 25 Jul after | 22.4 °C | 40 % | 37 km/h | 0.0 mm | High 30 |
| 26 Jul after | 20.5 °C | 40 % | 33 km/h | 0.0 mm | High 27 |
| 27 Jul after | 20.3 °C | 40 % | 26 km/h | 0.0 mm | High 24 |
| 28 Jul after | 22.2 °C | 38 % | 22 km/h | 0.0 mm | High 24 |
| 29 Jul after | 22.3 °C | 39 % | 34 km/h | 0.0 mm | High 28 |
| 30 Jul after | 23.7 °C | 31 % | 24 km/h | 0.0 mm | High 25 |
| 31 Jul after | 22.8 °C | 32 % | 28 km/h | 0.0 mm | High 26 |
| 1 Aug after | 20.5 °C | 41 % | 33 km/h | 0.0 mm | High 27 |
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 24 July 2026 the air beside the fire reached 61 µg/m³ of PM2.5. That day averaged 29: 2.0 times the WHO daily 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 · 7Every 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 Bindura fire last?
- GWIS (Copernicus) dates it between 22 July 2026 and 22 July 2026: 1 day 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 1,054 hectares (10.5 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Bindura (1,059 ha, 0.5 %).
- What was the weather like?
- During the fire the temperature reached 24.3 °C, humidity dropped to 28 % and gusts hit 33 km/h. The fire danger index (FWI) reached 31, class High.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Zimbabwe (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.
Satellite cross-check
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
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 3.0 Intergovernmental Organisations (CC BY 3.0 IGO)). 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.