Skip to content
worldfires
RU · Russia · –

Evenkiysky Rayon fire, 12 July 2019 Evenkiysky Rayon, Katangsky Rayon

Out · last detection 26 Jul 2019, 05:07 UTC

The fire started on 12 July 2019 in Evenkiysky Rayon, Russia, and satellites saw it burning for 15 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 9,865 hectares from heat detections, spread across 2 municipalities.

It is the 171th largest in Krasnoyarsk Krai since 2016 (of 538 with a page). Number 175 in Russia in 2019, of 610.

Burnt area
9,865ha
GWIS perimeter (Copernicus)
Duration
15days
12 Jul 2019 – 26 Jul 2019
Municipalities hit
2
districts
Started on
12 Jul
2019
Heat detections
1,452
in a single hotspot: 151 MW
Danger at start
30
High · FWI index
Average daily power
854MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 12 Jul26 Jul
26 Jul 2019

How it evolved, day by day

12 Jul 2019 · 7 MW · 3 13 Jul 2019 · 131 MW · 25 14 Jul 2019 · 22 MW · 12 15 Jul 2019 · 139 MW · 37 16 Jul 2019 · 325 MW · 51 17 Jul 2019 · 772 MW · 121 18 Jul 2019 · 799 MW · 134 19 Jul 2019 · 2,250 MW · 131 20 Jul 2019 · 4,538 MW · 307 21 Jul 2019 · 1,489 MW · 175 22 Jul 2019 · 1,011 MW · 208 23 Jul 2019 · 990 MW · 139 24 Jul 2019 · 114 MW · 40 25 Jul 2019 · 207 MW · 65 26 Jul 2019 · 14 MW · 4
12 Jul 15 Jul 20 Jul 24 Jul

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

The weather it burned in

31°high
63km/h · peak gust
27%lowest humidity

It had gone 4 days without rain (1 mm or more) when it started. Rain came after the fire: 7.7 mm on 1 Aug.

This area had burned before

29% of the perimeter overlaps earlier fires recorded since 2016: 194 ha in 2016, 2,724 ha in 2017.

How big is it?

10 km
It burned the equivalent of 6.2% of the area of London (99 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each town

  1. Evenkiysky Rayon where it started
    8,092 ha reached on 12 Jul
    0.0 %
  2. 442 ha reached on 18 Jul
    0.0 %

Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance runs from the point marking the centre of each area to the nearest fire: staying a kilometre away does not mean it reached the houses.

People and buildings inside the perimeter

GHSL 2020
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2020, satellite-based estimate).

This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned.

Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu

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)
12 Jul 20.6 °C 49 % 40 km/h 0.0 mm High 30
13 Jul 26.6 °C 33 % 33 km/h 0.0 mm High 31
14 Jul 27.0 °C 38 % 18 km/h 0.0 mm High 22
15 Jul 26.2 °C 41 % 46 km/h 0.0 mm Very high 42
16 Jul 29.2 °C 41 % 37 km/h 0.0 mm High 33
17 Jul 31.1 °C 33 % 34 km/h 0.0 mm High 34
18 Jul 26.6 °C 39 % 42 km/h 0.0 mm High 35
19 Jul 21.1 °C 30 % 52 km/h 0.0 mm Very high 44
20 Jul 20.8 °C 28 % 63 km/h 0.0 mm Extreme 52
21 Jul 23.5 °C 31 % 45 km/h 0.0 mm Very high 41
22 Jul 25.7 °C 27 % 35 km/h 0.0 mm High 37
23 Jul 26.5 °C 27 % 29 km/h 0.0 mm High 37
24 Jul 26.9 °C 33 % 14 km/h 0.0 mm High 25
25 Jul 28.8 °C 35 % 19 km/h 0.0 mm High 30
26 Jul 27.2 °C 44 % 14 km/h 0.0 mm High 25
27 Jul after 27.0 °C 55 % 25 km/h 0.1 mm High 23
28 Jul after 25.6 °C 47 % 36 km/h 0.0 mm High 30
29 Jul after 25.0 °C 42 % 26 km/h 0.0 mm High 26
30 Jul after 26.2 °C 36 % 20 km/h 0.0 mm High 27
31 Jul after 26.1 °C 38 % 23 km/h 0.0 mm High 31
1 Aug after 19.0 °C 80 % 22 km/h 7.7 mm Very low 4

Its twins: fires that started in the same weather

It started with an FWI of 29.8, a minimum humidity of 49% and 4 days without rain. Fires in the area that started in weather like this since 2016: 13.

FWI at the start 29.8
Minimum humidity 49 %
Days without rain 4
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Evenkiysky Rayon fire, July 2016
11,972 ha 21 days FWI 22.3 Min. humidity 48 % 131 km away, in 2016

First rain (1 mm or more) after it ended: 1.9 mm on 27 Jul.

What happened to them

Fires in the area that started in similar weather: 13. With fewer than 15 we give no figures: they would be more noise than signal.

This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it

How it ended

7.7 mmfirst rain
1 Aug6 days after it ended
63km/h · max. gust

It was considered over on 26 Jul, and on 1 Aug 7.7 mm fell. We do not know whether the rain or the firefighters put it out.

Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)

How a twin is chosen

  • Same area: fires that have already ended, less than 250 km from this one, since 2016.
  • Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
  • Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
  • Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
  • They are sorted by similarity, and the outlines of the first five are drawn.

How we calculate it

Before and after, from space

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

Before · 5 Jul 2019
After · 2 Aug 2019

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 · 1,452Every 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 Evenkiysky Rayon fire last?
GWIS (Copernicus) dates it between 12 July 2019 and 26 July 2019: 15 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 9,865 hectares (98.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Evenkiysky Rayon (8,092 ha, 0.0 %); Katangsky Rayon (442 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 31.1 °C, humidity dropped to 27 % and gusts hit 63 km/h. The fire danger index (FWI) reached 52, class Extreme.
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 · Emergency number and official warnings

Satellite cross-check

History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.

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.

How we know this
  • Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
  • Dates from the perimeter: the VIIRS detections inside it did not change them. 1,452 Suomi-NPP VIIRS detections on those dates.
  • We have not matched this page with any official record.
  • Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.
  • Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2020, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.

How we build fire pages: methodology

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.