Mansa fire, 14 August 2026 Mansa
The fire started on 14 August 2026 in Mansa, Zambia, and satellites saw it burning for 9 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 6,361 hectares from heat detections, spread across a single municipality.
It is the 202th largest in Luapula since 2016 (of 533 with a page). Number 158 in Zambia in 2026, of 610.
Compare with…
Suggestions: Mansa · 2017Mansa · 2020Mansa · 2019Mansa · 2025
- Burnt area
- 6,361ha
- GWIS perimeter (Copernicus)
- Duration
- 9days
- 14 Aug 2026 – 22 Aug 2026
- Municipalities hit
- 1
- districts
- Started on
- 14 Aug
- 2026
- Heat detections
- 156
- in a single hotspot: 52 MW
- Danger at start
- 30
- High · FWI index
- Average daily power
- 82MW
- 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
81% of the perimeter overlaps earlier fires recorded since 2016: 1,261 ha in 2016, 1,230 ha in 2017, 2,379 ha in 2018, 2,399 ha in 2019, 2,869 ha in 2020, 292 ha in 2021, 1,336 ha in 2022, 40 ha in 2023, 111 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 5,152 ha that had burned before.
- 965 ha Mansa fire, August 2017 20,923 ha in total; the hectares shown are those it shares with this fire
- 299 ha Mansa fire, August 2020 3,084 ha in total; the hectares shown are those it shares with this fire
- 179 ha Mansa fire, August 2019 22,056 ha in total; the hectares shown are those it shares with this fire
- 111 ha Mansa fire, July 2025 5,243 ha in total; the hectares shown are those it shares with this fire
- 35 ha Mansa fire, July 2018 13,615 ha in total; the hectares shown are those it shares with this fire
- 23 ha Chembe fire, August 2020 7,320 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
-
Mansa where it started6,407 ha reached on 7 Aug0.8 %
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) |
|---|---|---|---|---|---|
| 7 Aug | 25.9 °C | 41 % | 35 km/h | 0.0 mm | High 30 |
| 8 Aug | 25.5 °C | 42 % | 40 km/h | 0.0 mm | High 32 |
| 9 Aug | 26.4 °C | 42 % | 34 km/h | 0.0 mm | High 29 |
| 10 Aug | 28.6 °C | 35 % | 34 km/h | 0.0 mm | High 30 |
| 11 Aug | 28.3 °C | 32 % | 33 km/h | 0.0 mm | High 30 |
| 12 Aug | 27.2 °C | 33 % | 45 km/h | 0.0 mm | High 35 |
| 13 Aug | 25.0 °C | 42 % | 54 km/h | 0.0 mm | Very high 39 |
| 14 Aug | 23.5 °C | 42 % | 50 km/h | 0.0 mm | High 36 |
| 15 Aug | 23.6 °C | 37 % | 40 km/h | 0.0 mm | High 31 |
| 16 Aug | 23.7 °C | 36 % | 35 km/h | 0.0 mm | High 30 |
| 17 Aug | 24.6 °C | 29 % | 37 km/h | 0.0 mm | High 32 |
| 18 Aug | 25.6 °C | 24 % | 37 km/h | 0.0 mm | High 35 |
| 19 Aug | 25.1 °C | 28 % | 41 km/h | 0.0 mm | High 37 |
| 20 Aug | 25.3 °C | 31 % | 39 km/h | 0.0 mm | High 36 |
| 21 Aug | 25.7 °C | 31 % | 42 km/h | 0.0 mm | High 38 |
| 22 Aug | 27.4 °C | 30 % | 42 km/h | 0.0 mm | Very high 38 |
| 23 Aug after | 27.1 °C | 33 % | 41 km/h | 0.0 mm | High 37 |
| 24 Aug after | 28.5 °C | 34 % | 46 km/h | 0.0 mm | Very high 40 |
| 25 Aug after | 27.7 °C | 38 % | 43 km/h | 0.0 mm | High 37 |
| 26 Aug after | 28.5 °C | 38 % | 40 km/h | 0.0 mm | High 36 |
| 27 Aug after | 27.3 °C | 41 % | 51 km/h | 0.0 mm | Very high 38 |
| 28 Aug after | 25.8 °C | 41 % | 48 km/h | 0.1 mm | High 36 |
| 29 Aug after | 26.3 °C | 39 % | 45 km/h | 0.0 mm | High 35 |
| 30 Aug after | 28.3 °C | 33 % | 42 km/h | 0.0 mm | High 34 |
| 31 Aug after | 28.7 °C | 31 % | 41 km/h | 0.0 mm | High 35 |
| 1 Sept after | 28.7 °C | 33 % | 41 km/h | 0.0 mm | High 35 |
| 2 Sept after | 28.1 °C | 35 % | 41 km/h | 0.0 mm | High 36 |
| 3 Sept after | 28.6 °C | 35 % | 39 km/h | 0.0 mm | High 35 |
| 4 Sept after | 29.8 °C | 33 % | 31 km/h | 0.0 mm | High 31 |
| 5 Sept after | 27.8 °C | 39 % | 31 km/h | 0.0 mm | High 33 |
| 6 Sept after | 28.1 °C | 41 % | 43 km/h | 0.0 mm | High 36 |
| 7 Sept after | 28.3 °C | 39 % | 45 km/h | 0.0 mm | High 37 |
| 8 Sept after | 26.8 °C | 36 % | 52 km/h | 0.0 mm | Very high 40 |
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 16 August 2026 the air beside the fire reached 152 µg/m³ of PM2.5. That day averaged 72: 4.8 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 · 156Every 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 Mansa fire last?
- GWIS (Copernicus) dates it between 14 August 2026 and 22 August 2026: 9 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 6,361 hectares (63.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Mansa (6,407 ha, 0.8 %).
- What was the weather like?
- During the fire the temperature reached 28.6 °C, humidity dropped to 24 % and gusts hit 54 km/h. The fire danger index (FWI) reached 40, 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.
- Dates from the perimeter: the VIIRS detections inside it did not change them. 156 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.