Fire near Куп’янський район (UA)

49.99°N, 37.95°E · first detected on 12 August at 12:21

What the satellites measured

This fire was tracked from 12 August at 12:21 to 22 August at 13:10, that is 10 days, through 73 satellite detections. The detected extent reaches 1,377 ha.

Detected extent
1,377 ha
Cumulative power
744 MW
Peak power, one pixel
59 MW
VIIRS and MODIS detections
73

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 13 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
22 August at 13:1018 MW2N
22 August at 12:3417 MW3N21
22 August at 11:4929 MW4N20
22 August at 01:411 MW1N
21 August at 14:5915 MW1Aqua
21 August at 13:3034 MW3N
21 August at 13:2188 MW2Aqua
21 August at 12:5367 MW8N21
21 August at 12:0975 MW7N20
21 August at 11:4992 MW6N
21 August at 11:13117 MW10N21
21 August at 09:0118 MW2Terra
20 August at 19:326 MW1Terra
19 August at 01:181 MW1N20
18 August at 14:4431 MW2Aqua
18 August at 13:0447 MW3N20
15 August at 01:371 MW1N21
14 August at 01:562 MW1N21
13 August at 02:163 MW2N21
13 August at 01:293 MW3N20
13 August at 01:092 MW2N
12 August at 19:139 MW1Terra
12 August at 14:127 MW1Aqua
12 August at 12:214 MW1N21

3 other fires near Куп’янський район (UA)

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