Skip to content
worldfires
ZM · Zambia · →

Lavushimanda fire, 16 September 2025 Lavushimanda

Out · last detection 20 Sept 2025, 12:25 UTC

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

It is the 363th largest in Muchinga since 2016 (of 520 with a page). Number 172 in Zambia in 2025, of 271.

Compare with…

Suggestions: Chitambo · 2025Lunga · 2025

Burnt area
3,753ha
GWIS perimeter (Copernicus)
Duration
5days
16 Sept 2025 – 20 Sept 2025
Municipalities hit
1
districts
Started on
16 Sept
2025
Heat detections
58
in a single hotspot: 62 MW
Danger at start
46
Very high · FWI index
Average daily power
418MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 16 Sept20 Sept
20 Sept 2025

How it evolved, day by day

16 Sept 2025 · 96 MW · 5 18 Sept 2025 · 719 MW · 35 20 Sept 2025 · 440 MW · 18
16 Sept 18 Sept 20 Sept

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
51km/h · peak gust
13%lowest humidity

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

This area had burned before

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

How big is it?

10 km
It burned the equivalent of 2.4% of the area of London (38 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,768 ha reached on 16 Sept
    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 2025
Built-up area0.48 ha
Residents≈ 80

Inside the perimeter there were about 0.48 hectares of built-up land and about 80 residents (GHSL 2025, 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. The GHSL 2025 epoch is a projection made from 2020 and earlier data.

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)
16 Sept 33.5 °C 14 % 26 km/h 0.0 mm Very high 46
17 Sept 34.1 °C 13 % 33 km/h 0.0 mm Extreme 52
18 Sept 32.9 °C 18 % 41 km/h 0.0 mm Extreme 54
19 Sept 33.1 °C 26 % 37 km/h 0.0 mm Very high 47
20 Sept 31.3 °C 28 % 51 km/h 0.0 mm Extreme 51
21 Sept after 30.5 °C 28 % 40 km/h 0.0 mm Very high 44
22 Sept after 32.3 °C 23 % 40 km/h 0.0 mm Very high 44
23 Sept after 33.1 °C 19 % 34 km/h 0.0 mm Very high 46
24 Sept after 33.0 °C 18 % 37 km/h 0.0 mm Very high 49
25 Sept after 33.1 °C 20 % 35 km/h 0.0 mm Very high 50
26 Sept after 32.6 °C 22 % 42 km/h 0.0 mm Extreme 50
27 Sept after 33.2 °C 21 % 38 km/h 0.0 mm Very high 48
28 Sept after 34.5 °C 18 % 28 km/h 0.0 mm Very high 47
29 Sept after 35.5 °C 16 % 26 km/h 0.0 mm Very high 42
30 Sept after 34.3 °C 24 % 37 km/h 0.0 mm Extreme 51

Before and after, from space

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

Before · 9 Sept 2025
After · 27 Sept 2025

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 15 September 2025 the air beside the fire reached 36 µg/m³ of PM2.5. That day averaged 27: 1.8 times the WHO daily guideline (15).

PM2.5 peak36 µg/m³
Days over the guideline8 days
PM1036 µg/m³
Optical depth0.84
14151617181920212223
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 · 58Every 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 16 September 2025 and 20 September 2025: 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,753 hectares (37.5 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Lavushimanda (3,768 ha, 0.3 %).
What was the weather like?
During the fire the temperature reached 34.1 °C, humidity dropped to 13 % and gusts hit 51 km/h. The fire danger index (FWI) reached 54, class Extreme.
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. 58 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 2025, 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.