Skip to content
worldfires
ZM · Zambia · →

Kasempa fire, October 2017 Kasempa

Out · last detection 23 Oct 2017, 22:59 UTC

The fire started on 19 October 2017 in Kasempa, Zambia, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,894 hectares from heat detections, spread across a single municipality.

It is the 153th largest in North-Western since 2016 (of 286 with a page). Number 142 in Zambia in 2017, of 230.

Compare with…
Burnt area
3,894ha
GWIS perimeter (Copernicus)
Duration
5days
19 Oct 2017 – 23 Oct 2017
Municipalities hit
1
districts
Started on
19 Oct
2017
Heat detections
114
in a single hotspot: 108 MW
Danger at start
42
Very high · FWI index
Average daily power
197MW
detected power per day, on average

Where it burned

23 Oct 2017
HOTSPOTS BY DAY 19 Oct23 Oct

How it evolved, day by day

19 Oct 2017 · 452 MW · 21 20 Oct 2017 · 118 MW · 23 21 Oct 2017 · 342 MW · 42 22 Oct 2017 · 44 MW · 14 23 Oct 2017 · 30 MW · 11
19 Oct 20 Oct 21 Oct 22 Oct 23 Oct

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

36°high
53km/h · peak gust
17%lowest humidity

It had gone 6 days without rain (1 mm or more) when it started. Rain came after the fire: 5.2 mm on 28 Oct.

This area had burned before

24% of the perimeter overlaps earlier fires recorded since 2016: 925 ha in 2016.

How big is it?

10 km
It burned the equivalent of 2.5% of the area of London (39 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each town

  1. Kasempa where it started
    3,923 ha reached on 17 Oct
    0.2 %

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)
19 Oct 36.1 °C 19 % 37 km/h 0.0 mm Very high 42
20 Oct 36.3 °C 18 % 36 km/h 0.0 mm Very high 43
21 Oct 34.8 °C 19 % 42 km/h 0.0 mm Very high 45
22 Oct 34.9 °C 17 % 52 km/h 0.0 mm Extreme 52
23 Oct 33.2 °C 24 % 53 km/h 0.0 mm Very high 43
24 Oct after 34.3 °C 24 % 46 km/h 0.0 mm Very high 43
25 Oct after 34.8 °C 22 % 37 km/h 0.0 mm Very high 41
26 Oct after 35.8 °C 20 % 26 km/h 0.0 mm Very high 40
27 Oct after 32.6 °C 32 % 35 km/h 0.2 mm High 37
28 Oct after 27.7 °C 51 % 44 km/h 5.2 mm Low 6

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

Before · 12 Oct 2017
After · 30 Oct 2017

If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.

Detections table · 114Every 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 timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in Zambia ›

Frequently asked questions

How long did the Kasempa fire last?
GWIS (Copernicus) dates it between 19 October 2017 and 23 October 2017: 5 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 3,894 hectares (38.9 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Kasempa (3,923 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 36.3 °C, humidity dropped to 17 % and gusts hit 53 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

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
What do you think is wrong?

We will only use your email to reply about this report. Privacy.

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. 114 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.

How we build fire pages: methodology ›

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.