Skip to content
worldfires
ZM · Zambia · →

Kanchibiya fire, 23 August 2016 Kanchibiya

Out · last detection 24 Aug 2016, 11:20 UTC

The fire started on 23 August 2016 in Kanchibiya, Zambia, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,205 hectares from heat detections, spread across a single municipality.

It is the 463th largest in Muchinga since 2016 (of 516 with a page). Number 222 in Zambia in 2016, of 246.

Burnt area
3,205ha
GWIS perimeter (Copernicus)
Duration
2days
23 Aug 2016 – 24 Aug 2016
Municipalities hit
1
districts
Started on
23 Aug
2016
Heat detections
94
in a single hotspot: 211 MW
Danger at start
53
Extreme · FWI index
Energy released
941MW
sum of detected power

Where it burned

24 Aug 2016
HOTSPOTS BY DAY 23 Aug24 Aug

How it evolved, day by day

2324

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

The weather it burned in

29°high
64km/h · peak gust
17%lowest humidity

It had gone more than two months without rain (1 mm or more) when it started.

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

What happened to each town

  1. Kanchibiya where it started
    3,222 ha reached on 23 Aug
    0.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)
23 Aug 28.8 °C 17 % 55 km/h 0.0 mm Extreme 53
24 Aug 23.7 °C 36 % 64 km/h 0.0 mm Very high 49
25 Aug after 25.0 °C 31 % 49 km/h 0.0 mm Very high 40
26 Aug after 26.7 °C 28 % 40 km/h 0.0 mm High 37
27 Aug after 25.8 °C 24 % 52 km/h 0.0 mm Very high 43
28 Aug after 25.0 °C 29 % 52 km/h 0.0 mm Very high 43
29 Aug after 26.5 °C 26 % 50 km/h 0.0 mm Very high 43
30 Aug after 26.9 °C 23 % 47 km/h 0.0 mm Very high 42
31 Aug after 27.3 °C 22 % 40 km/h 0.0 mm Very high 43
1 Sept after 26.6 °C 27 % 43 km/h 0.0 mm Very high 44
2 Sept after 26.2 °C 26 % 43 km/h 0.0 mm Very high 43
3 Sept after 26.9 °C 23 % 39 km/h 0.0 mm Very high 42

Before and after, from space

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

Before · 16 Aug 2016
After · 31 Aug 2016

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 · 94Every 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 Kanchibiya fire last?
GWIS (Copernicus) dates it between 23 August 2016 and 24 August 2016: 2 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,205 hectares (32.0 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Kanchibiya (3,222 ha, 0.4 %).
What was the weather like?
During the fire the temperature reached 28.8 °C, humidity dropped to 17 % and gusts hit 64 km/h. The fire danger index (FWI) reached 53, 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.

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.