Skip to content
worldfires
ZM · Zambia · →

Lavushimanda fire, 26 August 2018 Lavushimanda

Out · last detection 30 Aug 2018, 11:19 UTC

The fire started on 26 August 2018 in Lavushimanda, Zambia, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,113 hectares from heat detections, spread across a single municipality.

It is the 488th largest in Muchinga since 2016 (of 516 with a page). Number 194 in Zambia in 2018, of 204.

Compare with…
Burnt area
3,113ha
GWIS perimeter (Copernicus)
Duration
5days
26 Aug 2018 – 30 Aug 2018
Municipalities hit
1
districts
Started on
26 Aug
2018
Heat detections
83
in a single hotspot: 99 MW
Danger at start
41
Very high · FWI index
Average daily power
452MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 26 Aug30 Aug
30 Aug 2018

How it evolved, day by day

26 Aug 2018 · 115 MW · 4 27 Aug 2018 · 1,632 MW · 34 28 Aug 2018 · 475 MW · 32 29 Aug 2018 · 29 MW · 7 30 Aug 2018 · 10 MW · 2
26 Aug 27 Aug 28 Aug 29 Aug 30 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

31°high
51km/h · peak gust
15%lowest humidity

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

This area had burned before

62% of the perimeter overlaps earlier fires recorded since 2016: 656 ha in 2016, 1,543 ha in 2017. Part of it burned more than once, so the yearly figures add up to more than the 1,941 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. Lavushimanda where it started
    3,126 ha reached on 25 Aug
    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.

People and buildings inside the perimeter

GHSL 2020
Built-up area0.88 ha
Residents≈ 150

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

Day High Min. humidity Peak gust Rain Danger (FWI)
26 Aug 29.5 °C 24 % 34 km/h 0.0 mm Very high 41
27 Aug 30.7 °C 15 % 32 km/h 0.0 mm Very high 45
28 Aug 29.2 °C 18 % 46 km/h 0.0 mm Very high 50
29 Aug 26.6 °C 31 % 51 km/h 0.0 mm Very high 44
30 Aug 27.4 °C 27 % 48 km/h 0.0 mm Very high 43
31 Aug after 27.5 °C 27 % 46 km/h 0.0 mm Very high 43
1 Sept after 28.3 °C 26 % 44 km/h 0.0 mm Very high 42
2 Sept after 30.5 °C 22 % 41 km/h 0.0 mm Very high 41
3 Sept after 31.0 °C 23 % 37 km/h 0.0 mm Very high 43
4 Sept after 30.6 °C 21 % 41 km/h 0.0 mm Very high 44
5 Sept after 30.9 °C 25 % 43 km/h 0.0 mm Very high 45
6 Sept after 30.3 °C 27 % 45 km/h 0.0 mm Very high 44
7 Sept after 32.3 °C 21 % 38 km/h 0.0 mm Very high 43
8 Sept after 31.0 °C 25 % 34 km/h 0.0 mm Very high 43
9 Sept after 31.8 °C 28 % 26 km/h 0.4 mm High 37

Before and after, from space

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

Before · 19 Aug 2018
After · 6 Sept 2018

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 · 83Every 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 Zambia ›

Frequently asked questions

How long did the Lavushimanda fire last?
GWIS (Copernicus) dates it between 26 August 2018 and 30 August 2018: 5 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,113 hectares (31.1 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Lavushimanda (3,126 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 30.7 °C, humidity dropped to 15 % and gusts hit 51 km/h. The fire danger index (FWI) reached 50, class Very high.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Zambia (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. 83 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 4.0 (CC BY 4.0)). 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.