Kaputa fire, 7 August 2026 Kaputa
The fire started on 7 August 2026 in Kaputa, Zambia, and satellites saw it burning for 12 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 9,093 hectares from heat detections, spread across a single municipality.
It is the 95th largest in Northern since 2016 (of 628 with a page). Number 93 in Zambia in 2026, of 610.
- Burnt area
- 9,093ha
- GWIS perimeter (Copernicus)
- Duration
- 12days
- 7 Aug 2026 – 18 Aug 2026
- Municipalities hit
- 1
- districts
- Started on
- 7 Aug
- 2026
- Heat detections
- 230
- in a single hotspot: 243 MW
- Danger at start
- 26
- High · FWI index
- Energy released
- 5.2GW
- sum of detected power
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
62% of the perimeter overlaps earlier fires recorded since 2016: 779 ha in 2016, 879 ha in 2018, 2,325 ha in 2019, 1,220 ha in 2020, 424 ha in 2021, 16 ha in 2022, 115 ha in 2023, 1,594 ha in 2024, 1,627 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 5,640 ha that had burned before.
What happened to each town
-
Kaputa where it started7,100 ha reached on 6 Aug1.4 %
Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre 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)
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 7 Aug | 30.2 °C | 42 % | 25 km/h | 0.0 mm | High 26 |
| 8 Aug | 30.4 °C | 38 % | 30 km/h | 0.0 mm | High 28 |
| 9 Aug | 30.2 °C | 36 % | 26 km/h | 0.0 mm | High 27 |
| 10 Aug | 32.1 °C | 31 % | 27 km/h | 0.0 mm | High 29 |
| 11 Aug | 32.0 °C | 28 % | 24 km/h | 0.0 mm | High 30 |
| 12 Aug | 31.9 °C | 22 % | 27 km/h | 0.0 mm | High 35 |
| 13 Aug | 30.3 °C | 27 % | 33 km/h | 0.0 mm | Very high 38 |
| 14 Aug | 28.6 °C | 40 % | 29 km/h | 0.0 mm | High 31 |
| 15 Aug | 27.9 °C | 39 % | 26 km/h | 0.0 mm | High 28 |
| 16 Aug | 28.5 °C | 35 % | 25 km/h | 0.0 mm | High 28 |
| 17 Aug | 29.2 °C | 34 % | 26 km/h | 0.0 mm | High 28 |
| 18 Aug | 30.0 °C | 31 % | 25 km/h | 0.0 mm | High 28 |
| 19 Aug after | 29.8 °C | 28 % | 26 km/h | 0.0 mm | High 30 |
| 20 Aug after | 29.4 °C | 32 % | 26 km/h | 0.0 mm | High 30 |
| 21 Aug after | 29.9 °C | 32 % | 29 km/h | 0.0 mm | High 31 |
| 22 Aug after | 30.5 °C | 32 % | 27 km/h | 0.0 mm | High 31 |
| 23 Aug after | 30.4 °C | 36 % | 25 km/h | 0.0 mm | High 30 |
| 24 Aug after | 31.5 °C | 34 % | 31 km/h | 0.0 mm | High 33 |
| 25 Aug after | 31.3 °C | 35 % | 29 km/h | 0.0 mm | High 32 |
| 26 Aug after | 32.1 °C | 30 % | 28 km/h | 0.0 mm | High 32 |
| 27 Aug after | 32.1 °C | 32 % | 34 km/h | 0.0 mm | High 34 |
| 28 Aug after | 30.8 °C | 34 % | 33 km/h | 0.0 mm | High 34 |
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 21 August 2026 the air beside the fire reached 192 µg/m³ of PM2.5. That day averaged 103: 6.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 · 230Every 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 Kaputa fire last?
- GWIS (Copernicus) dates it between 7 August 2026 and 18 August 2026: 12 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 9,093 hectares (90.9 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Kaputa (7,100 ha, 1.4 %).
- What was the weather like?
- During the fire the temperature reached 32.1 °C, humidity dropped to 22 % and gusts hit 33 km/h. The fire danger index (FWI) reached 38, 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
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
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.