Fire near Singida (TZ)

6.65°S, 34.50°E · first detected on 6 September at 00:37

What the satellites measured

This fire was tracked from 6 September at 00:37 to 6 September at 15:04, through 66 satellite detections. The detected extent reaches 1,040 ha.

Detected extent
1,040 ha
Cumulative power
462 MW
Peak power, one pixel
30 MW
VIIRS and MODIS detections
66

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 20:3013 MW2Terra
6 September at 19:3641 MW2Met9
6 September at 19:3432 MW2Met12
6 September at 19:2413 MW1Met12
6 September at 19:2123 MW1Met9
6 September at 17:2434 MW3Met12
6 September at 16:5023 MW1Met9
6 September at 16:3564 MW2Met9
6 September at 16:3543 MW1Met10
6 September at 16:34120 MW3Met12
6 September at 16:2413 MW1Met12
6 September at 16:2035 MW1Met10
6 September at 16:2052 MW2Met9
6 September at 16:1440 MW2Met12
6 September at 16:0532 MW1Met10
6 September at 16:0548 MW2Met9
6 September at 15:5453 MW3Met12
6 September at 15:5032 MW1Met9
6 September at 15:5037 MW1Met10
6 September at 15:4427 MW2Met12
6 September at 15:3537 MW1Met10
6 September at 15:3534 MW1Met9
6 September at 15:2418 MW1Met12
6 September at 15:2044 MW1Met10
6 September at 15:2066 MW2Met9
6 September at 15:0571 MW2Met9
6 September at 15:0547 MW1Met10
6 September at 15:0444 MW2Aqua
6 September at 14:50117 MW2Met9
6 September at 14:50136 MW2Met10
6 September at 14:35119 MW2Met9
6 September at 14:3589 MW1Met10
6 September at 14:3412 MW1Met12
6 September at 14:24407 MW10Met12
6 September at 14:2099 MW2Met9
6 September at 14:1441 MW2Met12
6 September at 14:05104 MW2Met9
6 September at 14:0565 MW1Met10
6 September at 14:0480 MW3Met12
6 September at 13:5457 MW3Met12
6 September at 13:5093 MW2Met9
6 September at 13:5059 MW1Met10
6 September at 13:3553 MW1Met10
6 September at 13:3581 MW2Met9
6 September at 13:3493 MW14N20
6 September at 13:2416 MW1Met12
6 September at 13:2082 MW2Met9
6 September at 13:2052 MW1Met10
6 September at 13:15133 MW20N
6 September at 13:1451 MW3Met12
6 September at 13:0567 MW1Met10
6 September at 13:05117 MW2Met9
6 September at 13:0438 MW2Met12
6 September at 12:5452 MW3Met12
6 September at 12:50120 MW2Met9
6 September at 12:50132 MW2Met10
6 September at 12:4415 MW1Met12
6 September at 12:38195 MW26N21
6 September at 12:35176 MW2Met9
6 September at 12:35154 MW2Met10
6 September at 12:3470 MW3Met12
6 September at 12:24213 MW5Met12
6 September at 12:20214 MW2Met10
6 September at 12:20175 MW2Met9
6 September at 12:1432 MW2Met12
6 September at 12:05177 MW2Met10
6 September at 12:05142 MW2Met9
6 September at 12:0481 MW3Met12
6 September at 11:5461 MW2Met12
6 September at 11:50105 MW2Met9
6 September at 11:50115 MW2Met10
6 September at 11:44127 MW5Met12
6 September at 11:35285 MW3Met10
6 September at 11:35192 MW3Met9
6 September at 11:34106 MW3Met12
6 September at 11:2448 MW2Met12
6 September at 11:20383 MW3Met9
6 September at 11:20711 MW5Met10
6 September at 11:14210 MW6Met12
6 September at 11:05103 MW1Met9
6 September at 11:05464 MW4Met10
6 September at 11:04192 MW5Met12
6 September at 10:5477 MW3Met12
6 September at 10:44340 MW6Met12
6 September at 10:3582 MW1Met10
6 September at 10:34133 MW3Met12
6 September at 10:24140 MW3Met12
6 September at 08:1420 MW2Terra
6 September at 01:392 MW3N21
6 September at 00:572 MW2N20
6 September at 00:374 MW6N

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