Fire near Al Wahat (LY)

28.83°N, 21.32°E · first detected on 8 August at 14:08

What the satellites measured

This fire was tracked from 8 August at 14:08 to 13 August at 14:14, that is 5 days, through 25 satellite detections. The detected extent reaches 163 ha.

Detected extent
163 ha
Cumulative power
78 MW
Peak power, one pixel
16 MW
VIIRS and MODIS detections
25

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 8 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
13 August at 14:143 MW1N
13 August at 02:221 MW1N21
12 August at 14:342 MW1N
12 August at 13:5716 MW1N21
12 August at 03:153 MW2N
12 August at 02:393 MW1N21
12 August at 01:562 MW2N20
12 August at 01:351 MW1N
11 August at 03:002 MW1N21
11 August at 02:133 MW1N20
11 August at 01:562 MW1N
10 August at 21:065 MW1Terra
10 August at 14:344 MW1N21
10 August at 13:495 MW1N20
10 August at 02:353 MW1N20
10 August at 02:132 MW1N
9 August at 02:523 MW1N20
9 August at 02:333 MW2N
9 August at 01:562 MW1N21
8 August at 14:2712 MW2N20
8 August at 14:083 MW1N
7 August at 14:2516 MW1N
7 August at 13:069 MW2N20
7 August at 03:092 MW2N
7 August at 02:354 MW1N21
7 August at 01:502 MW1N20
7 August at 01:291 MW1N
6 August at 14:463 MW2N

5 other fires near Al Wahat (LY)

Separate fires, apart in time or in space, not pieces of this one. A single municipality can have several over one summer, and a forest massif often covers more than a hundred square kilometres.

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