Mpika fire, 14 October 2026 Mpika
The fire started on 14 October 2026 in Mpika, Zambia, and satellites saw it burning for 11 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 4,100 hectares from heat detections, spread across a single municipality.
It is the 312th largest in Muchinga since 2016 (of 517 with a page). Number 328 in Zambia in 2026, of 613.
The power measured by the satellite is low (29.6 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Compare with…
Suggestions: Mpika · 2026Mpika · 2026Lavushimanda · 2026
Is it still active?
No detections since 24 Oct 2026, 23:24 UTC. That usually means no flame is visible from space any more, although hotspots may remain. 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.
- Burnt area
- 4,100ha
- GWIS perimeter (Copernicus)
- Duration
- 11days
- 14 Oct 2026 – 24 Oct 2026
- Municipalities hit
- 1
- districts
- Started on
- 14 Oct
- 2026
- Heat detections
- 75
- in a single hotspot: 30 MW
- Danger at start
- 37
- High · FWI index
- Average daily power
- 64MW
- 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 8 days without rain (1 mm or more) when it started.
This area had burned before
5% of the perimeter overlaps earlier fires recorded since 2016: 189 ha in 2025.
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
-
Mpika where it started4,129 ha reached on 14 Oct0.2 %
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 was no noticeable built-up land and almost nobody lived there (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) · forecast models, provisional until the ERA5 reanalysis arrives
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 14 Oct | 29.5 °C | 23 % | 45 km/h | 0.0 mm | High 37 |
| 15 Oct | 29.1 °C | 23 % | 53 km/h | 0.0 mm | Very high 40 |
| 16 Oct | 29.1 °C | 22 % | 48 km/h | 0.0 mm | Very high 39 |
| 17 Oct | 28.9 °C | 22 % | 49 km/h | 0.0 mm | Very high 41 |
| 18 Oct | 29.8 °C | 25 % | 41 km/h | 0.0 mm | High 38 |
| 19 Oct | 32.3 °C | 21 % | 34 km/h | 0.0 mm | High 37 |
| 20 Oct | 33.2 °C | 17 % | 39 km/h | 0.0 mm | Very high 41 |
| 21 Oct | 32.5 °C | 18 % | 47 km/h | 0.0 mm | Very high 46 |
| 22 Oct | 33.5 °C | 13 % | 47 km/h | 0.0 mm | Extreme 51 |
| 23 Oct | 33.7 °C | 15 % | 49 km/h | 0.0 mm | Extreme 52 |
| 24 Oct | 32.2 °C | 21 % | 54 km/h | 0.1 mm | Extreme 52 |
| 25 Oct after | 29.4 °C | 31 % | 54 km/h | 0.3 mm | Very high 45 |
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 20 October 2026 the air beside the fire reached 44 µg/m³ of PM2.5. That day averaged 32: 2.2 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 · 75Every 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 Mpika fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 14 October 2026 to 24 October 2026 (11 days). The perimeter dates it from 16 October 2026 to 24 October 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 4,100 hectares (41.0 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Mpika (4,129 ha, 0.2 %).
- Is the Mpika fire still active?
- No fire detections since 24 Oct 2026, 23:24 UTC. A lack of detections is not an official extinction.
- What was the weather like?
- During the fire the temperature reached 33.7 °C, humidity dropped to 13 % and gusts hit 54 km/h. The fire danger index (FWI) reached 52, 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.
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 16 October 2026 to 24 October 2026. 75 Suomi-NPP VIIRS detections on those dates.
- We have not matched this page with any official record.
- Weather: ECMWF IFS model, provisional until the ERA5 reanalysis arrives.
- 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.