Skip to content
worldfires
ZW · Zimbabwe · →

Lupane fire, 23 July 2016 Lupane, Hwange

Out · last detection 24 Jul 2016, 12:40 UTC

The fire started on 23 July 2016 in Lupane, Zimbabwe, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,687 hectares from heat detections, spread across 2 municipalities.

It is the 123th largest in Matabeleland North since 2016 (of 484 with a page). Number 19 in Zimbabwe in 2016, of 229.

The power measured by the satellite is low (21.4 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
3,687ha
GWIS perimeter (Copernicus)
Duration
2days
23 Jul 2016 – 24 Jul 2016
Municipalities hit
2
districts
Started on
23 Jul
2016
Heat detections
92
in a single hotspot: 21 MW
Danger at start
44
Very high · FWI index
Energy released
616MW
sum of detected power

Where it burned

24 Jul 2016
HOTSPOTS BY DAY 23 Jul24 Jul

How it evolved, day by day

2324

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

The weather it burned in

28°high
36km/h · peak gust
12%lowest humidity

It had gone 57 days 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.

What happened to each town

  1. Lupane where it started
    3,615 ha reached on 23 Jul
    0.4 %
  2. 94 ha reached on 23 Jul
    0.0 %

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)
23 Jul 28.1 °C 12 % 18 km/h 0.0 mm Very high 44
24 Jul 27.5 °C 18 % 36 km/h 0.0 mm Very high 46
25 Jul after 27.3 °C 25 % 48 km/h 0.0 mm Very high 48
26 Jul after 28.3 °C 30 % 46 km/h 0.0 mm Very high 43
27 Jul after 28.6 °C 30 % 30 km/h 0.0 mm High 35
28 Jul after 29.3 °C 10 % 24 km/h 0.0 mm Very high 42
29 Jul after 29.6 °C 2 % 27 km/h 0.0 mm Extreme 53
30 Jul after 29.7 °C 3 % 22 km/h 0.0 mm Extreme 52
31 Jul after 29.4 °C 15 % 33 km/h 0.0 mm Very high 49
1 Aug after 30.2 °C 17 % 27 km/h 0.0 mm Very high 48
2 Aug after 27.4 °C 17 % 30 km/h 0.0 mm Very high 46
3 Aug after 28.2 °C 20 % 25 km/h 0.0 mm Very high 43

Before and after, from space

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

Before · 16 Jul 2016
After · 31 Jul 2016

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 · 92Every 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 23 July 2016 and 24 July 2016: 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 3,687 hectares (36.9 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Lupane (3,615 ha, 0.4 %); Hwange (94 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 28.1 °C, humidity dropped to 12 % and gusts hit 36 km/h. The fire danger index (FWI) reached 46, 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.

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.