Skip to content
worldfires
RU · Russia · –

Kalarsky District fire, 10 June 2019 Kalarsky District, Бодайбинский район

Out · last detection

The fire started on in Kalarsky District, Russia, and satellites saw it burning for 10 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,401 hectares from heat detections, spread across 2 municipalities.

It is number 405 by size of the 465 fires with a page that started in Zabaykalsky Krai since 2016. Number 534 in Russia in 2019, of 610.

Burnt area
3,401ha
GWIS perimeter (Copernicus)
Duration
10days
10 Jun 2019 – 19 Jun 2019
Municipalities hit
2
districts
Started on
10 Jun
2019
Heat detections
202
in a single hotspot: 62 MW
Danger at start
4
Very low · FWI index
Average daily power
272MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 10 Jun19 Jun
19 Jun 2019

How it evolved, day by day

10 Jun 2019 · 25 MW · 4 11 Jun 2019 · 771 MW · 41 14 Jun 2019 · 46 MW · 7 15 Jun 2019 · 345 MW · 49 16 Jun 2019 · 247 MW · 29 17 Jun 2019 · 48 MW · 11 18 Jun 2019 · 651 MW · 56 19 Jun 2019 · 42 MW · 5
11 Jun 16 Jun 18 Jun

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

The weather it burned in

29°high
51km/h · peak gust
24%lowest humidity

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

This area had burned before

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

How big is it?

10 km
It burned the equivalent of 2.1% of the area of London (34 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. Kalarsky District where it started
    2,307 ha reached on 10 Jun
    0.0 %
  2. 1,174 ha reached on 11 Jun
    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)
10 Jun 25.2 °C 31 % 21 km/h 0.0 mm Very low 4
11 Jun 29.4 °C 26 % 32 km/h 0.0 mm Moderate 12
12 Jun 18.4 °C 38 % 51 km/h 5.5 mm Very low 1
13 Jun 17.8 °C 35 % 24 km/h 0.0 mm Very low 2
14 Jun 21.6 °C 37 % 24 km/h 0.0 mm Low 6
15 Jun 26.8 °C 35 % 22 km/h 0.0 mm Low 10
16 Jun 27.3 °C 38 % 23 km/h 2.6 mm Moderate 12
17 Jun 27.8 °C 30 % 31 km/h 0.0 mm Low 6
18 Jun 28.3 °C 24 % 27 km/h 0.0 mm Moderate 15
19 Jun 21.9 °C 59 % 30 km/h 0.6 mm Moderate 11
20 Jun after 20.7 °C 64 % 20 km/h 4.6 mm Low 8

Its twins: fires that started in the same weather

It started with an FWI of 3.8, a minimum humidity of 31% and 1 day without rain. Fires in the area that started in weather like this since 2017: 18.

FWI at the start 3.8
Minimum humidity 31 %
Days without rain 1
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Olyokminsky Ulus fire, August 2019
5,341 ha 8 days FWI 4.7 Min. humidity 32 % 202 km away, in 2019

First rain (1 mm or more) after it ended: 2.8 mm on 14 Aug.

What happened to them

14 days
median duration
5,378 ha
median area
28 %
went past 10,000 ha
4.6 mm
rain at the end (median; 18 of 18 had it)

It stayed below its twins: 3,401 ha against a median of 5,378 ha. It lasted 10 days, against 14 days.

All of them had rain in the ten days after the end: the first rainy day brought a median of 4.6 mm.

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

4.6 mmfirst rain
20 Junthe day after it ended
51km/h · max. gust

It was considered over on 19 Jun, and on 20 Jun 4.6 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 18 of 18, with a median of 4.6 mm.

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 2017.
  • 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 · 3 Jun 2019
After · 26 Jun 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 · 202Every 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 Kalarsky District fire last?
GWIS (Copernicus) dates it between 10 June 2019 and 19 June 2019: 10 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,401 hectares (34.0 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Kalarsky District (2,307 ha, 0.0 %); Бодайбинский район (1,174 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 29.4 °C, humidity dropped to 24 % and gusts hit 51 km/h. The fire danger index (FWI) reached 15, class Moderate.
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.
How did the fires that started in similar weather in this area end?
Fires less than 250 km away that started since 2017 with a similar FWI, humidity and dry spell: 18. Their median duration was 14 days and their median area 5,378 ha; 28 % went past 10,000 ha. All of them had rain in the ten days after the end: the first rainy day brought a median of 4.6 mm.

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. 202 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.