Lavushimanda fire, 15 August 2026 Lavushimanda
The fire started on 15 August 2026 in Lavushimanda, Zambia, and satellites saw it burning for 28 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 26,984 hectares from heat detections, spread across a single municipality.
It is the 25th largest in Muchinga since 2016 (of 518 with a page). Number 29 in Zambia in 2026, of 616.
Compare with…
- Burnt area
- 26,984ha
- GWIS perimeter (Copernicus)
- Duration
- 28days
- 15 Aug 2026 – 11 Sept 2026
- Municipalities hit
- 1
- districts
- Started on
- 15 Aug
- 2026
- Heat detections
- 582
- in a single hotspot: 93 MW
- Danger at start
- 28
- High · FWI index
- Average daily power
- 189MW
- detected power per day, on average
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone more than two months without rain (1 mm or more) when it started.
This area had burned before
74% of the perimeter overlaps earlier fires recorded since 2016: 2,384 ha in 2016, 5,976 ha in 2017, 6,449 ha in 2018, 7,275 ha in 2019, 2,409 ha in 2020, 6,809 ha in 2021, 2,146 ha in 2022, 847 ha in 2023, 4,069 ha in 2024, 4,158 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 19,973 ha that had burned before.
- 2,529 ha Lavushimanda fire, August 2018 3,113 ha in total; the hectares shown are those it shares with this fire
- 2,383 ha Lavushimanda fire, August 2018 3,290 ha in total; the hectares shown are those it shares with this fire
- 1,892 ha Lavushimanda fire, August 2017 8,084 ha in total; the hectares shown are those it shares with this fire
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Lavushimanda where it started27,105 ha reached on 15 Aug1.9 %
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 2025Inside the perimeter there were about 13 hectares of built-up land and about 2,100 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) |
|---|---|---|---|---|---|
| 15 Aug | 24.4 °C | 35 % | 36 km/h | 0.0 mm | High 28 |
| 16 Aug | 24.9 °C | 31 % | 32 km/h | 0.0 mm | High 30 |
| 17 Aug | 25.9 °C | 26 % | 36 km/h | 0.0 mm | High 34 |
| 18 Aug | 26.9 °C | 24 % | 34 km/h | 0.0 mm | High 35 |
| 19 Aug | 26.2 °C | 27 % | 42 km/h | 0.0 mm | Very high 39 |
| 20 Aug | 26.3 °C | 31 % | 40 km/h | 0.0 mm | High 38 |
| 21 Aug | 27.1 °C | 29 % | 42 km/h | 0.0 mm | Very high 39 |
| 22 Aug | 27.4 °C | 32 % | 44 km/h | 0.0 mm | Very high 40 |
| 23 Aug | 28.4 °C | 32 % | 35 km/h | 0.0 mm | High 37 |
| 24 Aug | 28.0 °C | 34 % | 47 km/h | 0.0 mm | Very high 41 |
| 25 Aug | 29.0 °C | 34 % | 33 km/h | 0.0 mm | High 38 |
| 26 Aug | 29.3 °C | 37 % | 35 km/h | 0.0 mm | High 35 |
| 27 Aug | 27.6 °C | 39 % | 47 km/h | 0.0 mm | High 38 |
| 28 Aug | 26.5 °C | 38 % | 39 km/h | 0.0 mm | High 35 |
| 29 Aug | 28.1 °C | 34 % | 41 km/h | 0.0 mm | High 35 |
| 30 Aug | 29.6 °C | 26 % | 37 km/h | 0.0 mm | High 37 |
| 31 Aug | 29.8 °C | 27 % | 37 km/h | 0.0 mm | High 38 |
| 1 Sept | 29.9 °C | 29 % | 38 km/h | 0.0 mm | Very high 40 |
| 2 Sept | 29.4 °C | 31 % | 37 km/h | 0.0 mm | Very high 40 |
| 3 Sept | 30.1 °C | 30 % | 33 km/h | 0.0 mm | Very high 38 |
| 4 Sept | 30.9 °C | 29 % | 31 km/h | 0.0 mm | High 34 |
| 5 Sept | 29.9 °C | 34 % | 28 km/h | 0.0 mm | High 36 |
| 6 Sept | 30.0 °C | 35 % | 37 km/h | 0.0 mm | High 38 |
| 7 Sept | 29.3 °C | 35 % | 45 km/h | 0.0 mm | Very high 40 |
| 8 Sept | 27.0 °C | 36 % | 46 km/h | 0.0 mm | Very high 39 |
| 9 Sept | 25.3 °C | 41 % | 46 km/h | 0.0 mm | High 36 |
| 10 Sept | 28.0 °C | 34 % | 39 km/h | 0.0 mm | High 32 |
| 11 Sept | 29.7 °C | 30 % | 38 km/h | 0.0 mm | High 35 |
| 12 Sept after | 30.8 °C | 26 % | 38 km/h | 0.0 mm | Very high 38 |
| 13 Sept after | 30.3 °C | 29 % | 37 km/h | 0.0 mm | Very high 38 |
| 14 Sept after | 30.7 °C | 28 % | 38 km/h | 0.0 mm | Very high 38 |
| 15 Sept after | 30.9 °C | 25 % | 37 km/h | 0.0 mm | Very high 42 |
| 16 Sept after | 30.6 °C | 21 % | 40 km/h | 0.0 mm | Very high 44 |
| 17 Sept after | 29.7 °C | 27 % | 37 km/h | 0.0 mm | Very high 42 |
| 18 Sept after | 29.7 °C | 26 % | 36 km/h | 0.0 mm | Very high 43 |
| 19 Sept after | 30.3 °C | 31 % | 38 km/h | 0.0 mm | Very high 44 |
| 20 Sept after | 30.0 °C | 33 % | 37 km/h | 0.0 mm | Very high 40 |
| 21 Sept after | 28.2 °C | 40 % | 34 km/h | 0.9 mm | High 26 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
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 · CopernicusOn 5 September 2026 the air beside the fire reached 75 µg/m³ of PM2.5. That day averaged 44: 2.9 times the WHO daily guideline (15).
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 · 582Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Lavushimanda fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 15 August 2026 to 11 September 2026 (28 days). The perimeter dates it from 16 August 2026 to 4 September 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 26,984 hectares (269.8 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Lavushimanda (27,105 ha, 1.9 %).
- What was the weather like?
- During the fire the temperature reached 30.9 °C, humidity dropped to 24 % and gusts hit 47 km/h. The fire danger index (FWI) reached 41, 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.
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
How we know this
- Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery; 4 polygons grouped in this page.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 16 August 2026 to 4 September 2026. 582 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.
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.