Skip to content
worldfires
RU · Russia · →

Kalgansky District fire, May 2018 Gazimuro-Zavodsky District, Kalgansky District

Out · last detection 4 May 2018, 05:04 UTC

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

It is the 343th largest in Zabaykalsky Krai since 2016 (of 470 with a page). Number 423 in Russia in 2018, of 540.

Burnt area
3,921ha
GWIS perimeter (Copernicus)
Duration
3days
2 May 2018 – 4 May 2018
Municipalities hit
2
districts
Started on
2 May
2018
Heat detections
233
in a single hotspot: 58 MW
Danger at start
16
Moderate · FWI index
Energy released
2.6GW
sum of detected power

Where it burned

4 May 2018
HOTSPOTS BY DAY 2 May4 May

How it evolved, day by day

234

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

The weather it burned in

20°high
59km/h · peak gust
10%lowest humidity

It had gone 3 days without rain (1 mm or more) when it started. Rain came after the fire: 7.1 mm on 5 May.

This area had burned before

4% of the perimeter overlaps earlier fires recorded since 2016: 144 ha in 2016.

What happened to each town

  1. Gazimuro-Zavodsky District
    2,488 ha reached on 2 May
    0.2 %
  2. Kalgansky District where it started
    1,387 ha reached on 1 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)
1 May 9.6 °C 15 % 30 km/h 0.0 mm Moderate 16
2 May 13.9 °C 13 % 24 km/h 0.0 mm Moderate 16
3 May 18.8 °C 10 % 32 km/h 0.0 mm High 22
4 May 20.2 °C 13 % 59 km/h 0.0 mm High 32
5 May after 11.3 °C 21 % 63 km/h 7.1 mm Very low 2

Before and after, from space

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

Before · 25 Apr 2018
After · 11 May 2018

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 · 233Every 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 Kalgansky District fire last?
GWIS (Copernicus) dates it between 2 May 2018 and 4 May 2018: 3 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,921 hectares (39.2 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Gazimuro-Zavodsky District (2,488 ha, 0.2 %); Kalgansky District (1,387 ha, 0.4 %).
What was the weather like?
During the fire the temperature reached 20.2 °C, humidity dropped to 10 % and gusts hit 59 km/h. The fire danger index (FWI) reached 32, 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.