Skip to content
worldfires
ZW · Zimbabwe · →

Mbire fire, 5 September 2023 Mbire

Out · last detection 7 Sept 2023, 11:32 UTC

The fire started on 5 September 2023 in Mbire, Zimbabwe, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,480 hectares from heat detections, spread across a single municipality.

It is the 108th largest in Mashonaland Central since 2016 (of 334 with a page). Number 66 in Zimbabwe in 2023, of 173.

Compare with…
Burnt area
1,480ha
GWIS perimeter (Copernicus)
Duration
2days
5 Sept 2023 – 6 Sept 2023
Municipalities hit
1
districts
Started on
5 Sept
2023
Heat detections
37
in a single hotspot: 41 MW
Average daily power
91MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 5 Sept6 Sept
7 Sept 2023

How it evolved, day by day

5 Sept 2023 · 103 MW · 27 6 Sept 2023 · 164 MW · 9 7 Sept 2023 · 6 MW · 1
5 Sept 6 Sept 7 Sept

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

This area had burned before

74% of the perimeter overlaps earlier fires recorded since 2016: 585 ha in 2019, 643 ha in 2022. Part of it burned more than once, so the yearly figures add up to more than the 1,102 ha that had burned before.

How big is it?

10 km
It burned the equivalent of 0.9% of the area of London (15 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. Mbire where it started
    1,168 ha reached on 5 Sept
    0.2 %

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.

Before and after, from space

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

Before · 29 Aug 2023
After · 13 Sept 2023

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 · Copernicus

On 7 September 2023 the air beside the fire reached 27 µg/m³ of PM2.5. That day averaged 23: 1.5 times the WHO daily guideline (15).

PM2.5 peak27 µg/m³
Days over the guideline5 days
PM1039 µg/m³
Optical depth0.58
3456789
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 · 37Every 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 Zimbabwe ›

Frequently asked questions

How long did the Mbire fire last?
GWIS (Copernicus) dates it between 5 September 2023 and 6 September 2023: 2 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 1,480 hectares (14.8 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Mbire (1,168 ha, 0.2 %).
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.

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.

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. 37 Suomi-NPP VIIRS detections on those dates.
  • We have not matched this page with any official record.

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 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.