Fire near Muchinga (ZM)

11.68°S, 31.02°E · first detected on 6 September at 10:23

What the satellites measured

This fire was tracked from 6 September at 10:23 to 6 September at 15:01, through 169 satellite detections. The detected extent reaches 2,639 ha.

Detected extent
2,639 ha
Cumulative power
2,009 MW
Peak power, one pixel
60 MW
VIIRS and MODIS detections
169

These four figures cover the polar orbits alone, the ones that measure an area. The pass table below also counts geostationary detections, more frequent but too coarse for geometry, and its power column sums a whole pass where the peak above is that of a single pixel.

“Detected extent” is not “burned area”: it is the union of the ground footprints of the satellite pixels, and a 375 m pixel counts in full even when only a forest edge is burning. Compared with press figures it is in practice one and a half to three times the area reported. Detections taken at the edge of the scan swath, too coarse to measure anything at all, are excluded. These figures come from thermal detection and are not an official assessment: only the emergency services and the competent authorities are authoritative.

Replay how the fire spread

The map is framed on this fire and loads only its detections. The timeline below covers the whole known life of the fire, from the first trace, satellite or report, to the last announcement from emergency services, and the ticks on the bar mark those announcements. Detections often stop before containment: a fire stops radiating once it stops spreading, which is exactly when it is declared contained. “1 h” shows what is burning within an hour of the chosen moment : the map then follows the power curve below and empties when it falls. “12 h” stacks twelve hours , as the home map does, where stacking avoids an empty screen between two satellite passes. Both are true, but they say different things.

How the radiative power evolved

One point per satellite pass: the sum of the fire radiative power measured over the fire. This is the curve that says whether the fire eased off or picked up again, which no cumulative figure shows. The window covers 3 days; beyond that, clustering would merge two successive fires in the same place.

Fire dynamics

Loading history…

Satellite passes in detail

PassPower summed over the passDetectionsSensor
6 September at 18:0310 MW1Met12
6 September at 17:2016 MW1Met9
6 September at 17:2022 MW1Met10
6 September at 17:1311 MW1Met12
6 September at 17:0533 MW2Met9
6 September at 17:0425 MW1Met10
6 September at 16:5019 MW1Met9
6 September at 16:4924 MW1Met10
6 September at 16:3567 MW3Met9
6 September at 16:3435 MW1Met10
6 September at 16:2076 MW3Met9
6 September at 16:1938 MW1Met10
6 September at 16:0486 MW2Met10
6 September at 16:04103 MW3Met9
6 September at 15:49207 MW7Met9
6 September at 15:49103 MW2Met10
6 September at 15:4318 MW1Met12
6 September at 15:34127 MW2Met10
6 September at 15:34214 MW6Met9
6 September at 15:3326 MW2Met12
6 September at 15:2312 MW1Met12
6 September at 15:19211 MW5Met9
6 September at 15:19126 MW2Met10
6 September at 15:1312 MW1Met12
6 September at 15:04139 MW2Met10
6 September at 15:04279 MW6Met9
6 September at 15:01110 MW2Aqua
6 September at 14:5320 MW1Met12
6 September at 14:49139 MW2Met10
6 September at 14:49255 MW6Met9
6 September at 14:4333 MW3Met12
6 September at 14:34156 MW2Met10
6 September at 14:34299 MW6Met9
6 September at 14:3358 MW4Met12
6 September at 14:23152 MW8Met12
6 September at 14:19408 MW8Met9
6 September at 14:19289 MW4Met10
6 September at 14:17402 MW21N21
6 September at 14:13112 MW6Met12
6 September at 14:04205 MW4Met9
6 September at 14:0485 MW1Met10
6 September at 14:0397 MW6Met12
6 September at 13:5390 MW4Met12
6 September at 13:49167 MW2Met10
6 September at 13:49297 MW5Met9
6 September at 13:43144 MW8Met12
6 September at 13:34286 MW5Met9
6 September at 13:34160 MW2Met10
6 September at 13:3392 MW6Met12
6 September at 13:32539 MW83N20
6 September at 13:23186 MW9Met12
6 September at 13:19368 MW4Met10
6 September at 13:19553 MW8Met9
6 September at 13:15563 MW60N
6 September at 13:13114 MW5Met12
6 September at 13:04274 MW3Met10
6 September at 13:04410 MW6Met9
6 September at 13:03125 MW5Met12
6 September at 12:53372 MW11Met12
6 September at 12:49818 MW10Met9
6 September at 12:49460 MW4Met10
6 September at 12:43616 MW15Met12
6 September at 12:361,201 MW46N21
6 September at 12:34448 MW5Met10
6 September at 12:34657 MW8Met9
6 September at 12:33369 MW10Met12
6 September at 12:23289 MW9Met12
6 September at 12:19243 MW3Met10
6 September at 12:19243 MW3Met9
6 September at 12:13152 MW7Met12
6 September at 12:04108 MW1Met10
6 September at 12:04279 MW4Met9
6 September at 12:03157 MW7Met12
6 September at 11:5351 MW3Met12
6 September at 11:49347 MW5Met9
6 September at 11:49420 MW6Met10
6 September at 11:43104 MW5Met12
6 September at 11:34318 MW4Met10
6 September at 11:34309 MW4Met9
6 September at 11:33188 MW6Met12
6 September at 11:2344 MW3Met12
6 September at 11:1364 MW5Met12
6 September at 11:03101 MW5Met12
6 September at 10:5368 MW5Met12
6 September at 10:4342 MW3Met12
6 September at 10:33102 MW4Met12
6 September at 10:2314 MW1Met12

Follow live

The map shows active fires in 3D, with smoke plumes, forecast wind, drop zones and the live position of water bombers tracked by ADS-B, anywhere in the world.

Open the fire map

Get the alert instead of looking for it

GISFire Pro watches the zones you draw, anywhere in the world, and warns you by email, SMS or webhook from the first satellite detection: fire in the zone, fire closing in, smoke announced before it arrives, lightning nearby. A GeoJSON and CSV API, exports and history come with it.

From €8.25 a month, 14-day trial, no commitment. The public map stays free.

Discover GISFire Pro

© 2026 SARO · Gistin. All rights reserved. The interface, its presentation and the contents of GISFire are protected; reproducing or imitating them requires written permission. The source data remain the property of their respective producers, see the credits.

Legal notice · Privacy policy