Burned area
satellite only15,850ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 23 Aug 2026 – 5 Sept 2026
+− cross-check
No official record is matched to this page to compare it with.
ZM · Zambia · –
Lavushimanda fire, 23 August 2026 Mpika, Lavushimanda
Out · last detection 5 Sept 2026, 11:32 UTC
The fire started on 23 August 2026 in Lavushimanda, Zambia, and satellites saw it burning for 14 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 15,850 hectares from heat detections, spread across 2 municipalities.
Number 50 in Zambia in 2026, of 623.
GWIS near-real-time perimeter, from the layer that changed in August 2025: this fire is not compared with fires from earlier years, because since then the GWIS layer gives more and larger perimeters.
Use this data
Compare with…
Suggestions: Mpika · 2018Mpika · 2016Mpika · 2021Mpika · 2023
Use this data
Fire page data · version 2026-11-15matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only14days
23 Aug 2026 to 5 Sept 2026: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 5 Sept 2026, 11:32 UTC
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only23 Aug 2026
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 23 Aug 2026
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only332
VIIRS detections at 375 m. Most intense hotspot: 56 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 23 Aug 2026 – 5 Sept 2026
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only543MW
Total radiative power on 30 August 2026; hotspots that day: 80.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 30 Aug 2026
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model31.4FWI · high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 60.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 23 Aug 2026, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model34.0°C · 35% RH
High of 34.0 °C and minimum humidity of 35% on 5 September 2026; gusts of 30 km/h on 24 August 2026.
- Source
- weather model at the fire’s grid cell
- Date
- 23 Aug 2026 – 5 Sept 2026
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
logName: Mpika → Lavushimanda.
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
logStart date: 27 August 2026 → 23 August 2026.
Area logged each night
Move the slider to see which area the page published each day.
Versioned permanent link
https://worldfires.org/en/fire/lavushimanda-2026-08-10?v=2026-11-15A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire lavushimanda-2026-08-10.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-08-23 | 1 | 1 | 32.1 | 18.6 | 36 | 8.1 | 23 | 0 | 31.4 | alto | 1 |
| 2026-08-24 | 3 | 8 | 33.1 | 19.3 | 26 | 12.2 | 29.9 | 0 | 41.7 | muy_alto | 1 |
| 2026-08-25 | 8 | 12 | 31.4 | 17.8 | 36 | 10.5 | 23.8 | 0 | 31.8 | alto | 1 |
| 2026-08-26 | 0 | 0 | 32.9 | 18.5 | 34 | 8.5 | 22 | 0 | 32.2 | alto | 1 |
| 2026-08-27 | 3 | 17 | 31.6 | 22.5 | 34 | 13.6 | 29.9 | 0 | 39 | muy_alto | 1 |
| 2026-08-28 | 2 | 16 | 30.2 | 20.8 | 33 | 13 | 29.9 | 0 | 34.5 | alto | 1 |
| 2026-08-29 | 32 | 425 | 31.2 | 18.7 | 33 | 12.1 | 26.3 | 0 | 32.4 | alto | 1 |
| 2026-08-30 | 80 | 543 | 32.5 | 17.5 | 29 | 9.8 | 22.3 | 0 | 33.6 | alto | 1 |
| 2026-08-31 | 50 | 427 | 33.2 | 19 | 29 | 9.4 | 22.7 | 0 | 32.7 | alto | 1 |
| 2026-09-01 | 45 | 210 | 33.7 | 17.8 | 25 | 13.4 | 25.6 | 0 | 32.9 | alto | 1 |
| 2026-09-02 | 22 | 122 | 32.6 | 17.7 | 30 | 8.5 | 21.6 | 0 | 32.9 | alto | 1 |
| 2026-09-03 | 48 | 503 | 32.8 | 18.1 | 29 | 9.6 | 26.3 | 0 | 38.1 | muy_alto | 1 |
| 2026-09-04 | 33 | 146 | 33.1 | 19.5 | 29 | 12 | 29.9 | 0 | 40.8 | muy_alto | 1 |
| 2026-09-05 | 5 | 31 | 34 | 21 | 35 | 10.5 | 18.7 | 0 | 34 | alto | 1 |
| 2026-09-06 | 0 | 0 | 33.6 | 20.4 | 33 | 9.5 | 23 | 0 | 36.5 | alto | 0 |
| 2026-09-07 | 0 | 0 | 33.3 | 19.9 | 30 | 13.4 | 30.6 | 0 | 42.1 | muy_alto | 0 |
| 2026-09-08 | 0 | 0 | 32.1 | 19.6 | 28 | 21.2 | 42.5 | 0 | 47.3 | muy_alto | 0 |
| 2026-09-09 | 0 | 0 | 28.5 | 20.6 | 38 | 15.5 | 31.7 | 0 | 29.6 | alto | 0 |
| 2026-09-10 | 0 | 0 | 30.9 | 18.8 | 35 | 10.7 | 23.8 | 0 | 29.6 | alto | 0 |
| 2026-09-11 | 0 | 0 | 33.5 | 18.7 | 28 | 8.6 | 22.3 | 0 | 31.4 | alto | 0 |
| 2026-09-12 | 0 | 0 | 35.2 | 19 | 23 | 10.2 | 24.1 | 0 | 36.7 | alto | 0 |
| 2026-09-13 | 0 | 0 | 34.6 | 20.4 | 24 | 13.7 | 24.5 | 0 | 39.7 | muy_alto | 0 |
| 2026-09-14 | 0 | 0 | 34.6 | 20.8 | 25 | 9.7 | 21.2 | 0 | 36.6 | alto | 0 |
| 2026-09-15 | 0 | 0 | 34.6 | 19.5 | 24 | 16.8 | 31.3 | 0 | 39.4 | muy_alto | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: GWIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 15,850ha
- GWIS perimeter (Copernicus)
- Duration
- 14days
- 23 Aug 2026 – 5 Sept 2026
- Municipalities hit
- 2
- districts
- Started on
- 23 Aug
- 2026
- Heat detections
- 332
- in a single hotspot: 56 MW
- Danger at start
- 31
- High · FWI index
- Average daily power
- 189MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
23 Aug5 Sept
5 Sept 2026
How it evolved, day by day
23 Aug
27 Aug
30 Aug
2 Sept
5 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
30km/h · peak gust
25%lowest humidity
It had gone more than two months without rain (1 mm or more) when it started.
This area had burned before
82% of the perimeter overlaps earlier fires recorded since 2016: 6,396 ha in 2016, 8,844 ha in 2018, 2,425 ha in 2019, 181 ha in 2020, 2,603 ha in 2021, 2,902 ha in 2022, 2,381 ha in 2023, 39 ha in 2024. Part of it burned more than once, so the yearly figures add up to more than the 12,950 ha that had burned before.
- 8,824 ha Mpika fire, September 2018 18,632 ha in total; the hectares shown are those it shares with this fire
- 5,953 ha Mpika fire, September 2016 8,277 ha in total; the hectares shown are those it shares with this fire
- 2,603 ha Mpika fire, September 2021 4,501 ha in total; the hectares shown are those it shares with this fire
- 243 ha Mpika fire, August 2023 4,638 ha in total; the hectares shown are those it shares with this fire
- 20 ha Mpika fire, September 2018 3,658 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
-
9,274 ha0.5 %
-
Lavushimanda where it started6,708 ha0.5 %
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.
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)
Started with 60 days without rain: 91 % of the area in Zambia
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 23 Aug | 32.1 °C | 36 % | 23 km/h | 0.0 mm | High 31 |
| 24 Aug | 33.1 °C | 26 % | 30 km/h | 0.0 mm | Very high 42 |
| 25 Aug | 31.4 °C | 36 % | 24 km/h | 0.0 mm | High 32 |
| 26 Aug | 32.9 °C | 34 % | 22 km/h | 0.0 mm | High 32 |
| 27 Aug | 31.6 °C | 34 % | 30 km/h | 0.0 mm | Very high 39 |
| 28 Aug | 30.2 °C | 33 % | 30 km/h | 0.0 mm | High 34 |
| 29 Aug | 31.2 °C | 33 % | 26 km/h | 0.0 mm | High 32 |
| 30 Aug | 32.5 °C | 29 % | 22 km/h | 0.0 mm | High 34 |
| 31 Aug | 33.2 °C | 29 % | 23 km/h | 0.0 mm | High 33 |
| 1 Sept | 33.7 °C | 25 % | 26 km/h | 0.0 mm | High 33 |
| 2 Sept | 32.6 °C | 30 % | 22 km/h | 0.0 mm | High 33 |
| 3 Sept | 32.8 °C | 29 % | 26 km/h | 0.0 mm | Very high 38 |
| 4 Sept | 33.1 °C | 29 % | 30 km/h | 0.0 mm | Very high 41 |
| 5 Sept | 34.0 °C | 35 % | 19 km/h | 0.0 mm | High 34 |
| 6 Sept after | 33.6 °C | 33 % | 23 km/h | 0.0 mm | High 36 |
| 7 Sept after | 33.3 °C | 30 % | 31 km/h | 0.0 mm | Very high 42 |
| 8 Sept after | 32.1 °C | 28 % | 42 km/h | 0.0 mm | Very high 47 |
| 9 Sept after | 28.5 °C | 38 % | 32 km/h | 0.0 mm | High 30 |
| 10 Sept after | 30.9 °C | 35 % | 24 km/h | 0.0 mm | High 30 |
| 11 Sept after | 33.5 °C | 28 % | 22 km/h | 0.0 mm | High 31 |
| 12 Sept after | 35.2 °C | 23 % | 24 km/h | 0.0 mm | High 37 |
| 13 Sept after | 34.6 °C | 24 % | 24 km/h | 0.0 mm | Very high 40 |
| 14 Sept after | 34.6 °C | 25 % | 21 km/h | 0.0 mm | High 37 |
| 15 Sept after | 34.6 °C | 24 % | 31 km/h | 0.0 mm | Very high 39 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 16 Aug 2026
After · 12 Sept 2026
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
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 1 September 2026 the air beside the fire reached 58 µg/m³ of PM2.5. That day averaged 44: 2.9 times the WHO daily guideline (15).
PM2.5 peak58 µg/m³
Days over the guideline14 days
PM1060 µg/m³
Optical depth1.07
WHO 15
25 Aug28 Aug31 Aug3 Sept6 Sept
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 · 332Every 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 time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 18,632 haMpika12 September 2018 · 14 days · 2 km away
- 8,277 haMpika12 September 2016 · 11 days · 3 km away
- 8,853 haLavushimanda9 October 2026 · 10 days · 19 km away
- 8,262 haMpika2 October 2020 · 7 days · 23 km away
- 16,544 haLavushimanda11 October 2026 · 19 days · 28 km away
- 15,161 haLavushimanda18 September 2025 · 13 days · 32 km away
Frequently asked questions
- How long did the Lavushimanda fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 23 August 2026 to 5 September 2026 (14 days). The perimeter dates it from 27 August 2026 to 5 September 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 15,850 hectares (158.5 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Mpika (9,274 ha, 0.5 %); Lavushimanda (6,708 ha, 0.5 %).
- What was the weather like?
- During the fire the temperature reached 34.0 °C, humidity dropped to 25 % and gusts hit 30 km/h. The fire danger index (FWI) reached 42, 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 · 2 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Name: Mpika → Lavushimanda.
- Start date: 27 August 2026 → 23 August 2026.
RSS Changes to this page With cross-checks and a citable version
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.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 27 August 2026 to 5 September 2026. 332 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.
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.