Skip to content
worldfires
ZW · Zimbabwe ·

Centenary/ Muzarabani fire, 20 August 2019 Centenary/ Muzarabani

Out · last detection 20 Aug 2019, 23:12 UTC

The fire started on 20 August 2019 in Centenary/ Muzarabani, Zimbabwe, and satellites saw it burning for 1 day. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,124 hectares from heat detections, spread across a single municipality.

It is the 193th largest in Mashonaland Central since 2016 (of 255 with a page). Number 214 in Zimbabwe in 2019, of 281.

The power measured by the satellite is low (16.7 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.

Burnt area
1,124ha
GWIS perimeter (Copernicus)
Duration
1day
20 Aug 2019 – 20 Aug 2019
Municipalities hit
1
districts
Started on
20 Aug
2019
Heat detections
23
in a single hotspot: 17 MW
Danger at start
39
Very high · FWI index
Average daily power
224MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 20 Aug20 Aug

How it evolved, day by day

20 Aug 2019 · 224 MW · 23

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

The weather it burned in

26°high
44km/h · peak gust
19%lowest humidity

It had gone more than two months without rain (1 mm or more) when it started.

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

How big is it?

10 km
It burned the equivalent of 0.7% of the area of London (11 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. Centenary/ Muzarabani where it started
    1,132 ha reached on 20 Aug
    0.3 %

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 2020
Built-up area6.0 ha
Residents≈ 800

Inside the perimeter there were about 6.0 hectares of built-up land and about 800 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)

Started with 60 days without rain: 63 % of the area in Zimbabwe

Day High Min. humidity Peak gust Rain Danger (FWI)
20 Aug 26.3 °C 19 % 44 km/h 0.0 mm Very high 39
21 Aug after 22.1 °C 45 % 52 km/h 0.2 mm High 31
22 Aug after 23.2 °C 32 % 37 km/h 0.0 mm High 26
23 Aug after 24.4 °C 24 % 30 km/h 0.0 mm High 28
24 Aug after 24.5 °C 28 % 40 km/h 0.0 mm High 31
25 Aug after 25.6 °C 34 % 39 km/h 0.0 mm High 32
26 Aug after 28.5 °C 34 % 32 km/h 0.0 mm High 29
27 Aug after 30.5 °C 27 % 35 km/h 0.0 mm High 32
28 Aug after 29.9 °C 26 % 36 km/h 0.0 mm High 33
29 Aug after 30.0 °C 26 % 35 km/h 0.0 mm High 34
30 Aug after 29.3 °C 27 % 34 km/h 0.0 mm High 34

Its twins: fires that started in the same weather

It started with an FWI of 38.9, a minimum humidity of 19% and more than two months without rain. Fires in the area that started in weather like this since 2016: 39.

FWI at the start 38.9
Minimum humidity 19 %
Days without rain 60+
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Centenary/ Muzarabani fire, September 2016
1,505 ha 4 days FWI 39.2 Min. humidity 19 % 8 km away, in 2016

First rain (1 mm or more) after it ended: none in the following ten days.

What happened to them

5 days
median duration
1,372 ha
median area
100 %
went past 1,000 ha
2.2 mm
rain at the end (median; 3 of 39 had it)

It burned an area similar to its twins (1,124 ha against a median of 1,372 ha) and lasted 1 day, against 5 days.

In 36 of 39, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 2.2 mm.

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
44km/h · max. gust

It was considered over on 20 Aug, and not even 1 mm fell in the following ten days: it went out without rain. Twins with rain when they ended: 3 of 39, with a median of 2.2 mm.

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.

How we calculate it

Before and after, from space

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

Before · 13 Aug 2019
After · 27 Aug 2019

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 · 23Every 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 Centenary/ Muzarabani fire last?
GWIS (Copernicus) dates it between 20 August 2019 and 20 August 2019: 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,124 hectares (11.2 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Centenary/ Muzarabani (1,132 ha, 0.3 %).
What was the weather like?
During the fire the temperature reached 26.3 °C, humidity dropped to 19 % and gusts hit 44 km/h. The fire danger index (FWI) reached 39, 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.
How did the fires that started in similar weather in this area end?
Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 39. Their median duration was 5 days and their median area 1,372 ha; 100 % went past 1,000 ha. In 36 of 39, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 2.2 mm.

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.

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

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.