Skip to content
worldfires
RU · Russia · →

Abansky Rayon fire, 23 May 2017 Abansky Rayon

Out · last detection 30 May 2017, 07:44 UTC

The fire started on 23 May 2017 in Abansky Rayon, Russia, and satellites saw it burning for 8 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,749 hectares from heat detections, spread across a single municipality.

It is the 536th largest in Krasnoyarsk Krai since 2016 (of 656 with a page). Number 271 in Russia in 2017, of 369.

Burnt area
3,749ha
GWIS perimeter (Copernicus)
Duration
8days
23 May 2017 – 30 May 2017
Municipalities hit
1
districts
Started on
23 May
2017
Heat detections
339
in a single hotspot: 128 MW
Danger at start
19
Moderate · FWI index
Energy released
4.3GW
sum of detected power

Where it burned

30 May 2017
HOTSPOTS BY DAY 23 May30 May

How it evolved, day by day

232425282930

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

The weather it burned in

32°high
70km/h · peak gust
18%lowest humidity

It had gone one day without rain (1 mm or more) when it started. Rain came after the fire: 16.5 mm on 31 May.

This area had burned before

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

What happened to each town

  1. Abansky Rayon where it started
    3,773 ha reached on 23 May
    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 May 28.2 °C 18 % 63 km/h 0.1 mm Moderate 19
24 May 31.5 °C 18 % 70 km/h 0.0 mm High 30
25 May 21.5 °C 43 % 64 km/h 2.4 mm Low 6
26 May 15.8 °C 37 % 70 km/h 2.6 mm Very low 4
27 May 11.5 °C 28 % 56 km/h 1.8 mm Very low 3
28 May 19.4 °C 31 % 20 km/h 0.4 mm Low 7
29 May 24.0 °C 24 % 37 km/h 0.0 mm Moderate 14
30 May 24.8 °C 35 % 31 km/h 1.5 mm Low 7
31 May after 17.8 °C 69 % 43 km/h 16.5 mm Very low 0

Before and after, from space

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

Before · 16 May 2017
After · 6 Jun 2017

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 · 339Every 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 Russia ›

Frequently asked questions

How long did the Abansky Rayon fire last?
GWIS (Copernicus) dates it between 23 May 2017 and 30 May 2017: 8 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,749 hectares (37.5 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Abansky Rayon (3,773 ha, 0.4 %).
What was the weather like?
During the fire the temperature reached 31.5 °C, humidity dropped to 18 % and gusts hit 70 km/h. The fire danger index (FWI) reached 30, class High.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Russia (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.

Emergency number: 112

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. This is not an emergency service: if there is a fire now, call 112.

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 (Open Data Commons Open Database License 1.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.