Umzingwane fire, 5 August 2026 Umzingwane, Insiza
The fire started on 5 August 2026 in Umzingwane, Zimbabwe, and satellites saw it burning for 1 day. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,010 hectares from heat detections, spread across 2 municipalities.
It is the 200th largest in Matabeleland South since 2016 (of 204 with a page). Number 362 in Zimbabwe in 2026, of 377.
Compare with…
- Burnt area
- 1,010ha
- GWIS perimeter (Copernicus)
- Duration
- 1day
- 5 Aug 2026 – 5 Aug 2026
- Municipalities hit
- 2
- districts
- Started on
- 5 Aug
- 2026
- Heat detections
- 18
- in a single hotspot: 195 MW
- Danger at start
- 38
- Very high · FWI index
- Average daily power
- 1.2GW
- detected power per day, on average
Where it burned
How it evolved, day by day
5 Aug 2026 · 1,235 MW · 18
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 44 days without rain (1 mm or more) when it started. Rain came after the fire: 2.3 mm on 13 Aug.
This area had burned before
34% of the perimeter overlaps earlier fires recorded since 2016: 340 ha in 2021.
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
-
Umzingwane where it started988 ha reached on 5 Aug0.4 %
-
25 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.
People and buildings inside the perimeter
GHSL 2025Inside the perimeter there were about 2.2 hectares of built-up land and about 150 residents (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) |
|---|---|---|---|---|---|
| 5 Aug | 24.6 °C | 15 % | 25 km/h | 0.0 mm | Very high 38 |
| 6 Aug after | 24.7 °C | 12 % | 35 km/h | 0.0 mm | Very high 44 |
| 7 Aug after | 22.7 °C | 17 % | 45 km/h | 0.0 mm | Extreme 51 |
| 8 Aug after | 22.2 °C | 29 % | 38 km/h | 0.0 mm | Very high 39 |
| 9 Aug after | 24.4 °C | 25 % | 36 km/h | 0.0 mm | Very high 38 |
| 10 Aug after | 26.4 °C | 21 % | 37 km/h | 0.0 mm | Very high 42 |
| 11 Aug after | 18.7 °C | 46 % | 49 km/h | 0.8 mm | High 27 |
| 12 Aug after | 10.9 °C | 83 % | 50 km/h | 0.1 mm | Moderate 15 |
| 13 Aug after | 11.7 °C | 83 % | 48 km/h | 2.3 mm | Very low 4 |
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 6 August 2026 the air beside the fire reached 16 µg/m³ of PM2.5, but no daily average passed the WHO 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 · 18Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 4,856 haUmzingwaneSeptember 2022 · 3 days · 17 km away
- 4,431 haUmzingwane19 September 2026 · 9 days · 17 km away
- 3,913 haUmzingwane3 September 2026 · 2 days · 17 km away
- 3,862 haInsiza12 September 2026 · 4 days · 18 km away
- 4,920 haInsizaAugust 2026 · 5 days · 24 km away
- 7,113 haInsiza15 September 2018 · 5 days · 40 km away
Frequently asked questions
- How long did the Umzingwane fire last?
- GWIS (Copernicus) dates it between 5 August 2026 and 5 August 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,010 hectares (10.1 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Umzingwane (988 ha, 0.4 %); Insiza (25 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 24.6 °C, humidity dropped to 15 % and gusts hit 25 km/h. The fire danger index (FWI) reached 38, class Very 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
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.
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. 18 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.
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.