Skip to content
worldfires
ZW · Zimbabwe · →

Lupane fire, 26 August 2020 Lupane

Out · last detection 29 Aug 2020, 11:30 UTC

The fire started on 26 August 2020 in Lupane, Zimbabwe, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,090 hectares from heat detections, spread across a single municipality.

It is the 142th largest in Matabeleland North since 2016 (of 487 with a page). Number 16 in Zimbabwe in 2020, of 91.

Compare with…
Burnt area
3,090ha
GWIS perimeter (Copernicus)
Duration
4days
26 Aug 2020 – 29 Aug 2020
Municipalities hit
1
districts
Started on
26 Aug
2020
Heat detections
116
in a single hotspot: 73 MW
Danger at start
38
High · FWI index
Average daily power
235MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 26 Aug29 Aug
29 Aug 2020

How it evolved, day by day

26 Aug 2020 · 232 MW · 38 27 Aug 2020 · 461 MW · 44 28 Aug 2020 · 213 MW · 29 29 Aug 2020 · 34 MW · 5
26 Aug 27 Aug 28 Aug 29 Aug

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

The weather it burned in

34°high
46km/h · peak gust
19%lowest humidity

It had gone more than two months without rain (1 mm or more) when it started. Rain came after the fire: 1.3 mm on 1 Sept.

This area had burned before

70% of the perimeter overlaps earlier fires recorded since 2016: 646 ha in 2016, 1,863 ha in 2017, 324 ha in 2019. Part of it burned more than once, so the yearly figures add up to more than the 2,166 ha that had burned before.

How big is it?

10 km
It burned the equivalent of 2% of the area of London (31 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. Lupane where it started
    3,110 ha reached on 26 Aug
    0.3 %

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)
26 Aug 30.9 °C 19 % 30 km/h 0.0 mm High 38
27 Aug 32.1 °C 21 % 38 km/h 0.0 mm Very high 43
28 Aug 33.1 °C 21 % 41 km/h 0.0 mm Very high 45
29 Aug 33.7 °C 20 % 46 km/h 0.0 mm Very high 48
30 Aug after 30.0 °C 27 % 40 km/h 0.0 mm Very high 50
31 Aug after 22.8 °C 45 % 46 km/h 0.5 mm High 33
1 Sept after 28.5 °C 33 % 46 km/h 1.3 mm High 28

Before and after, from space

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

Before · 19 Aug 2020
After · 5 Sept 2020

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 · 116Every 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 Lupane fire last?
GWIS (Copernicus) dates it between 26 August 2020 and 29 August 2020: 4 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 3,090 hectares (30.9 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Lupane (3,110 ha, 0.3 %).
What was the weather like?
During the fire the temperature reached 33.7 °C, humidity dropped to 19 % and gusts hit 46 km/h. The fire danger index (FWI) reached 48, 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

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

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.